Uplink / downlink transmission and reception method and device based on beam linkage state in a wireless communication system

The method addresses uplink/downlink challenges in wireless communication systems by utilizing beam linkage states for efficient transmission and reception, improving data rates and latency in multi-cell environments.

KR103046020B1Active Publication Date: 2026-11-10LG ELECTRONICS INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
KR1020227039887
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-08-04
Filing Date
2021-08-04
Publication Date
2026-11-10
Estimated Expiration
2041-08-04

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing uplink and downlink transmissions and receptions, particularly in environments with multiple cell/bandwidth portions, requiring advanced methods to accommodate increasing data traffic, higher transmission rates, and low latency.

Method used

A method and apparatus for performing uplink/downlink transmission and reception based on beam linkage states, involving configuration information and spatial parameter determination for terminals and base stations, utilizing reference and target transmissions and receptions.

Benefits of technology

Enables efficient uplink/downlink operations in wireless communication systems with multiple cells/bandwidth portions, enhancing data transmission rates and reducing latency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112022121324113-PCT00003_ABST
    Figure 112022121324113-PCT00003_ABST
Patent Text Reader

Abstract

A method and apparatus for performing uplink / downlink transmission and reception based on a beam linkage state in a wireless communication system are disclosed. A method for a terminal to perform uplink transmission or downlink reception in a wireless communication system according to one embodiment of the present disclosure comprises: receiving from a base station configuration information regarding a first beam linkage state (BLS) for a first resource and a second BLS for a second resource, wherein each of the first and second BLS includes information regarding a mapping relationship between a reference transmission and reception and one or more target transmissions and receptions; receiving from the base station reference spatial parameter instruction information for the reference transmission and reception for the first resource; and performing uplink transmission or downlink reception on the second resource based on a target spatial parameter for a specific target transmission and reception among the one or more target transmissions and receptions, wherein the target spatial parameter may be determined based on the reference spatial parameter.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for performing uplink / downlink transmission and reception based on a beam linkage state in a wireless communication system. Background Technology

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

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

[0004] The technical problem of the present disclosure is to provide a method and apparatus for performing uplink / downlink transmission and reception based on a beam linkage state in a wireless communication system.

[0005] An additional technical objective of the present disclosure is to provide an uplink / downlink transmission and reception method and apparatus based on a beam linkage state for a terminal in a wireless communication system in which multiple cell / bandwidth portions are configured.

[0006] An additional technical objective of the present disclosure is to provide a method and apparatus for determining spatial parameters to be applied to a target transmission and reception associated with a reference transmission and reception by a beam linkage state for a terminal in a wireless communication system in which multiple cell / bandwidth portions are configured.

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

[0008] A method for a terminal to perform uplink transmission or downlink reception in a wireless communication system according to one aspect of the present disclosure comprises: receiving from a base station configuration information for a first beam linkage state (BLS) for a first resource and a second BLS for a second resource, wherein each of the first and second BLS includes information regarding a mapping relationship between a reference transmission and reception and one or more target transmissions and receptions; receiving from the base station reference spatial parameter instruction information for the reference transmission and reception for the first resource; and performing uplink transmission or downlink reception on the second resource based on a target spatial parameter for a specific target transmission and reception among the one or more target transmissions and receptions, wherein the target spatial parameter may be determined based on the reference spatial parameter.

[0009] A method for performing downlink transmission or uplink reception by a base station in a wireless communication system according to an additional aspect of the present disclosure comprises: transmitting to a terminal configuration information for a first beam linkage state (BLS) for a first resource and a second BLS for a second resource, wherein each of the first and second BLS includes information regarding a mapping relationship between a reference transmission and reception and one or more target transmissions and receptions; transmitting to the terminal reference spatial parameter indication information for the reference transmission and reception for the first resource; and performing downlink transmission or uplink reception on the second resource, wherein the downlink transmission or uplink reception on the second resource is received or transmitted by the terminal based on a target spatial parameter for a specific target transmission and reception among the one or more target transmissions and receptions, and the target spatial parameter may be determined based on the reference spatial parameter. Effects of the invention

[0010] According to the present disclosure, a method and apparatus for performing uplink / downlink transmission and reception based on a beam linkage state in a wireless communication system may be provided.

[0011] According to the present disclosure, a method and apparatus for uplink / downlink transmission and reception based on a beam linkage state may be provided for a terminal in a wireless communication system in which multiple cells / bandwidth portions are configured.

[0012] According to the present disclosure, a method and apparatus are provided for determining spatial parameters to be applied to a target transmission and reception associated with a reference transmission and reception by a beam linkage state for a terminal in a wireless communication system in which multiple cell / bandwidth portions are configured.

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

[0014] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description. FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied. FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure may be applied. FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure may be applied. FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure may be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure may be applied. FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure may be applied, and a general method of transmitting and receiving signals using these channels. FIG. 7 is a diagram illustrating downlink beam management operations in a wireless communication system to which the present disclosure may be applied. FIG. 8 is a diagram illustrating a downlink beam management procedure using an SSB in a wireless communication system to which the present disclosure may be applied. FIG. 9 is a diagram illustrating downlink beam management operation using CSI-RS in a wireless communication system to which the present disclosure may be applied. FIG. 10 is a diagram illustrating the process of determining the receiving beam of a terminal in a wireless communication system to which the present disclosure may be applied. FIG. 11 is a diagram illustrating the transmission beam determination process of a base station in a wireless communication system to which the present disclosure may be applied. FIG. 12 is a diagram illustrating resource allocation in the time and frequency domains related to the operation of downlink beam management in a wireless communication system to which the present disclosure may be applied. FIG. 13 is a diagram illustrating an uplink beam management operation using an SRS in a wireless communication system to which the present disclosure may be applied. FIG. 14 is a diagram illustrating an uplink beam management procedure in a wireless communication system to which the present disclosure may be applied. FIG. 15 is a flowchart illustrating a method for a terminal to perform uplink transmission or downlink reception based on a beam linkage state according to the present disclosure. FIG. 16 is a flowchart illustrating a method for a base station to perform uplink reception or downlink transmission based on a beam linkage state according to the present disclosure. FIG. 17 is a drawing for explaining a signaling process according to one embodiment of the present disclosure. FIG. 18 is a drawing illustrating a block diagram of a wireless communication device according to one embodiment of the present disclosure. Specific details for implementing the invention

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

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

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

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

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

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

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

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

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

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

[0025] For 3GPP LTE, refer to TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

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

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

[0028] - BM: Beam management

[0029] - CQI: Channel quality indicator

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

[0031] - CSI: Channel state information

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

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

[0034] - DMRS: demodulation reference signal

[0035] - FDM: Frequency Division Multiplexing

[0036] - FFT: Fast Fourier Transform

[0037] - IFDMA: Interleaved frequency division multiple access

[0038] - IFFT: Inverse Fast Fourier Transform

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

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

[0041] - MAC: Medium Access Control

[0042] - NZP: Non-zero power

[0043] - OFDM: Orthogonal Frequency Division Multiplexing

[0044] - PDCCH: Physical downlink control channel

[0045] - PDSCH: Physical downlink shared channel

[0046] - PMI: Precoding Matrix Indicator

[0047] - RE: resource element

[0048] - RI: Rank indicator

[0049] - RRC: Radio Resource Control

[0050] - RSSI: Received signal strength indicator

[0051] - Rx: Reception

[0052] - QCL: quasi co-location

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

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

[0055] - TDM: Time Division Multiplexing

[0056] - TRP: transmission and reception point

[0057] - TRS: Tracking Reference Signal

[0058] - Tx: transmission

[0059] - UE: User equipment

[0060] - ZP: Zero Power

[0061] General System

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0077] First, regarding antenna ports, an antenna port is defined such that the channel carrying a symbol on the antenna port can be inferred from the channel carrying another symbol on the same antenna port. If the large-scale property of the channel carrying a symbol on one antenna port can be inferred from the channel carrying a symbol on another antenna port, the two antenna ports can be said to be in a QC / QCL (quasi-co-located or quasi-co-location) relationship. Here, the large-scale property includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0078] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure may be applied.

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

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

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

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

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

[0084]

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

[0086]

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

[0088] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure may be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure may be applied.

[0089] Referring to FIGS. 4 and 5, a slot contains multiple symbols in the time domain. For example, in the case of a standard CP, one slot contains 7 symbols, but in the case of an extended CP, one slot contains 6 symbols.

[0090] A carrier includes multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed through the active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is referred to as a Resource Element (RE) and can be mapped to a single complex symbol.

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

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

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

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

[0095] When the terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S601). To this end, the terminal receives a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID). Subsequently, the terminal receives a Physical Broadcast Channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, during the initial cell search phase, the terminal receives a Downlink Reference Signal (DL RS) to check the downlink channel status.

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

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

[0098] A terminal that has performed the procedure described above may subsequently perform PDCCH / PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission procedure. In particular, the terminal receives Downlink Control Information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its purpose of use.

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

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

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

[0102] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), Transport Block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for PUSCH scheduling in a single cell. The information contained in DCI format 0_0 is transmitted after being scrambled with a cyclic redundancy check (CRC) by a C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), a CS-RNTI (Configured Scheduling RNTI), or a MCS-C-RNTI (Modulation Coding Scheme Cell RNTI).

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

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

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

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

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

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

[0109] Beam management (BM)

[0110] BM procedures are L1 (layer 1) / L2 (layer 2) procedures for acquiring and maintaining a set of base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams that can be used for downlink (DL) and uplink (UL) transmission / reception, and may include the following procedures and terms.

[0111] - Beam measurement: An operation in which a base station or UE measures the characteristics of a received beamforming signal.

[0112] - Beam determination: The operation in which a base station or UE selects its transmit beam (Tx beam) / receive beam (Rx beam).

[0113] - Beam sweeping: An operation that covers a spatial area using transmitting and / or receiving beams for a set time interval in a predetermined manner.

[0114] - Beam report: An operation in which the UE reports information about the beam-formed signal based on beam measurements.

[0115] The BM procedure can be divided into (1) a DL BM procedure using an SS (synchronization signal) / PBCH (physical broadcast channel) Block or CSI-RS, and (2) a UL BM procedure using an SRS (sounding reference signal).

[0116] In addition, each BM procedure may include transmission beam sweeping to determine the transmission beam (Tx beam) and reception beam sweeping to determine the reception beam (Rx beam).

[0117] The DL BM procedure is described below.

[0118] The DL BM procedure may include (1) transmission to beamformed DL RS (reference signals) of the base station (e.g., CSI-RS or SS Block (SSB)) and (2) beam reporting of the terminal.

[0119] Here, beam reporting may include preferred DL RS ID(identifier)(s) and the corresponding L1-RSRP(Reference Signal Received Power).

[0120] The above DL RS ID may be SSBRI (SSB Resource Indicator) or CRI (CSI-RS Resource Indicator).

[0121] The following describes the DL BM procedure using SSB.

[0122] FIG. 7 is a diagram illustrating downlink beam management operations in a wireless communication system to which the present disclosure may be applied.

[0123] Referring to Fig. 7, the SSB beam and the CSI-RS beam can be used for beam measurement. The measurement metric is L1-RSRP per resource / block. The SSB is used for coarse beam measurement, while the CSI-RS can be used for fine beam measurement. The SSB can be used for both Tx beam sweeping and Rx beam sweeping.

[0124] Rx beam sweeping using SSBs can be performed as the UE changes the Rx beam across multiple SSB bursts for the same SSBRI. Here, one SS burst includes one or more SSBs, and one SS burst set includes one or more SSB bursts.

[0125] FIG. 8 is a diagram illustrating a downlink beam management procedure using an SSB in a wireless communication system to which the present disclosure may be applied.

[0126] Configuration for beam reporting using SSB is performed during CSI / beam configuration in the RRC connected state (or RRC connected mode).

[0127] Referring to FIG. 8, the terminal receives a CSI-ResourceConfig IE from the base station that includes a CSI-SSB-ResourceSetList containing SSB resources used for BM (S410).

[0128] Table 6 shows an example of CSI-ResourceConfig IE. As shown in Table 6, BM configuration using SSB is not defined separately, and SSB is configured like a CSI-RS resource.

[0129] -- ASN1START-- TAG-CSI-RESOURCECONFIG-STARTCSI-ResourceConfig ::= SEQUENCE { csi-ResourceConfigId CSI-ResourceConfigId, csi-RS-ResourceSetList CHOICE { nzp-CSI-RS-SSB SEQUENCE { nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL}, csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId}, bwp-Id BWP-Id, resourceType ENUMERATED { aperiodic, semiPersistent, periodic}, ...}-- TAG-CSI-RESOURCECONFIGTOADDMOD-STOP-- ASN1STOP

[0130] In Table 6, the csi-SSB-ResourceSetList parameter represents a list of SSB resources used for beam management and reporting in a single resource set. Here, the SSB resource set can be set to {SSBx1, SSBx2, SSBx3, SSBx4, ...}. The SSB index can be defined from 0 to 63. The terminal receives SSB resources from the base station based on the CSI-SSB-ResourceSetList (S420).

[0131] When a CSI-RS reportConfig related to reporting on SSBRI and L1-RSRP is configured, the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station (beam) (S430).

[0132] The DL BM procedure using CSI-RS is described below.

[0133] Regarding the uses of CSI-RS, i) if the repetition parameter is set for a specific CSI-RS resource set and TRS_info is not set, CSI-RS is used for beam management. ii) if the repetition parameter is not set and TRS_info is set, CSI-RS is used for the tracking reference signal (TRS). iii) if the repetition parameter is not set and TRS_info is not set, CSI-RS is used for CSI acquisition.

[0134] These repetition parameters can only be set for CSI-RS resource sets associated with a CSI-ReportConfig that has an L1 RSRP or a 'No Report (or None)' report.

[0135] If a terminal receives a CSI-ReportConfig in which reportQuantity is set to 'cri-RSRP' or 'none', and includes an NZP-CSI-RS-ResourceSet in which the upper layer parameter 'repetition' is set and the CSI-ResourceConfig (upper layer parameter resourcesForChannelMeasurement) for channel measurement does not include the upper layer parameter 'trs-Info', then the terminal may be configured with only ports of the same number (1-port or 2-port) having the upper layer parameter 'nrofPorts' for all CSI-RS resources within the NZP-CSI-RS-ResourceSet.

[0136] (Upper layer parameter) When repetition is set to 'ON', it relates to the terminal's Rx beam sweeping procedure. In this case, when the terminal is configured with NZP-CSI-RS-ResourceSet, the terminal can assume that at least one CSI-RS resource within NZP-CSI-RS-ResourceSet is transmitted through the same downlink spatial domain transmission filter. That is, at least one CSI-RS resource within NZP-CSI-RS-ResourceSet is transmitted through the same Tx beam. Here, at least one CSI-RS resource within NZP-CSI-RS-ResourceSet may be transmitted with different OFDM symbols. Additionally, the terminal does not expect to receive different periodicities in periodicityAndOffset from all CSI-RS resources within NZP-CSI-RS-ResourceSet.

[0137] On the other hand, when Repetition is set to 'OFF', it relates to the base station's Tx beam sweeping procedure. In this case, when repetition is set to 'OFF', the terminal does not assume that at least one CSI-RS resource within NZP-CSI-RS-ResourceSet is transmitted through the same downlink spatial domain transmission filter. That is, at least one CSI-RS resource within NZP-CSI-RS-ResourceSet is transmitted through different Tx beams.

[0138] That is, if the reportQuantity of the above CSI-RS reportConfig IE is set to 'ssb-Index-RSRP', the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station.

[0139] And, if the terminal has a CSI-RS resource configured at the same OFDM symbol(s) as the SSB (SS / PBCH Block) and 'QCL-TypeD' is applicable, the terminal can assume that the CSI-RS and the SSB are quasi-co-located in terms of 'QCL-TypeD'.

[0140] Here, the above QCL Type D may mean that antenna ports are QCL-connected in terms of spatial reception parameters. When a terminal receives multiple DL antenna ports that are in a QCL Type D relationship, it is acceptable to apply the same reception beam. Additionally, the terminal does not expect CSI-RS to be established in an RE that overlaps with the RE of the SSB.

[0141] FIG. 9 is a diagram illustrating downlink beam management operation using CSI-RS in a wireless communication system to which the present disclosure may be applied.

[0142] FIG. 9(a) illustrates the Rx beam determination (or refinement) procedure of a terminal, and FIG. 9(b) illustrates the Tx beam sweeping procedure of a base station. Additionally, FIG. 9(a) is the case where the repetition parameter is set to 'ON', and FIG. 9(b) is the case where the repetition parameter is set to 'OFF'.

[0143] FIG. 10 is a diagram illustrating the process of determining the receiving beam of a terminal in a wireless communication system to which the present disclosure may be applied.

[0144] Referring to Figures 9(a) and 10, we will examine the Rx beam determination process of the terminal.

[0145] The terminal receives an NZP CSI-RS resource set IE containing an upper layer parameter repetition from the base station via RRC signaling (S610). Here, the repetition parameter is set to 'ON'.

[0146] The terminal repeatedly receives resource(s) within a CSI-RS resource set set to repetition 'ON' in different OFDM symbols through the same Tx beam (or DL ​​spatial domain transmission filter) of the base station (S620).

[0147] The terminal determines its own Rx beam (S630).

[0148] The terminal omits the CSI report (S640). In this case, the reportQuantity of the CSI report settings can be set to 'No report (or None)'.

[0149] That is, if the above terminal is set to repetition 'ON', CSI reporting can be omitted.

[0150] FIG. 11 is a diagram illustrating the transmission beam determination process of a base station in a wireless communication system to which the present disclosure may be applied.

[0151] Referring to Fig. 9(b) and Fig. 11, we will examine the Tx beam determination process of the base station.

[0152] The terminal receives an NZP CSI-RS resource set IE containing an upper layer parameter repetition from the base station via RRC signaling (S710). Here, the repetition parameter is set to 'OFF' and is related to the base station's Tx beam sweeping procedure.

[0153] The terminal receives resources within the CSI-RS resource set set to repetition 'OFF' through different Tx beams (DL spatial domain transmission filters) of the base station (S720).

[0154] The terminal selects (or determines) the best beam (S740)

[0155] The terminal reports the ID and associated quality information (e.g., L1-RSRP) for the selected beam to the base station (S740). In this case, the reportQuantity of the CSI reporting settings can be set to 'CRI + L1-RSRP'.

[0156] That is, the terminal reports the CRI and the L1-RSRP for it to the base station when the CSI-RS is transmitted for BM.

[0157] FIG. 12 is a diagram illustrating resource allocation in the time and frequency domains related to the operation of downlink beam management in a wireless communication system to which the present disclosure may be applied.

[0158] Referring to Fig. 12, when repetition 'ON' is set in the CSI-RS resource set, multiple CSI-RS resources are used repeatedly by applying the same transmission beam, and when repetition 'OFF' is set in the CSI-RS resource set, different CSI-RS resources are transmitted to different transmission beams.

[0159] Below, a beam indication method related to downlink BM is described.

[0160] The terminal may receive a list of up to M candidate Transmission Configuration Indication (TCI) states for the purpose of at least Quasi Co-location (QCL) instructions in RRC configuration. Here, M can be 64.

[0161] Each TCI state can be configured as one RS set. Each ID of a DL RS for spatial QCL purposes (QCL Type D) within at least one RS set may refer to one of the DL RS types, such as SSB, P(periodic)-CSI RS, SP(semi-persistent)-CSI RS, A(aperiodic)-CSI RS.

[0162] At least the initialization / update of the IDs of the DL RS(s) within the RS set used for spatial QCL purposes can be performed through at least explicit signaling.

[0163] Table 7 shows an example of a TCI-State information element (IE: information element).

[0164] TCI-State IE associates one or two DL reference signals (RS) with corresponding quasi-co-location (QCL) types.

[0165] -- ASN1START-- TAG-TCI-STATE-STARTTCI-State ::= SEQUENCE { tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info OPTIONAL, -- Need R ...}QCL-Info ::= SEQUENCE { cell ServCellIndex OPTIONAL, -- Need R bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index}, qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ...}-- TAG-TCI-STATE-STOP-- ASN1STOP

[0166] In Table 7, the bwp-Id parameter represents the DL BWP (bandwidth part) where the RS is located, the cell parameter represents the carrier where the RS is located, and the referencesignal parameter represents the reference antenna port(s) or a reference signal containing them that serves as the source of quasi-co-location for the corresponding target antenna port(s). The target antenna port(s) may be a CSI-RS, PDCCH DMRS, or PDSCH DMRS. For example, to indicate QCL reference RS information for a non-zero power (NZP) CSI-RS, the corresponding TCI state ID (identifier) ​​may be indicated in the NZP CSI-RS resource configuration information. As another example, to indicate QCL reference information for a PDCCH DMRS antenna port(s), the TCI state ID may be indicated in each CORESET configuration. As another example, the TCI state ID can be indicated via DCI to indicate QCL reference information for PDSCH DMRS antenna port(s).

[0167] The following describes uplink beam management.

[0168] Depending on the terminal implementation, beam reciprocity (or beam correspondence) between the Tx beam and Rx beam may or may not be established in the UL BM. If reciprocity between the Tx beam and Rx beam is established at both the base station and the terminal, the UL beam pair can be matched through the DL beam pair. However, if reciprocity between the Tx beam and Rx beam is not established at either the base station or the terminal, a process for determining the UL beam pair is required separately from the determination of the DL beam pair.

[0169] In addition, even when both the base station and the terminal maintain beam correspondence, the base station can use the UL BM procedure to determine the DL Tx beam without the terminal requesting a report of the preferred beam.

[0170] UL BM can be performed via beamformed UL SRS transmission, and whether UL BM is applied to an SRS resource set is set by usage (upper layer parameter). If usage is set to 'BeamManagement(BM)', only one SRS resource can be transmitted to each of multiple SRS resource sets in a given time instant.

[0171] The terminal may receive one or more SRS (Sounding Reference Symbol) resource sets configured by the (upper layer parameter) SRS-ResourceSet (via upper layer signaling, RRC signaling, etc.). For each SRS resource set, the UE may be configured with K≥1 SRS resources (upper layer parameter SRS-resource). Here, K is a natural number, and the maximum value of K is indicated by SRS_capability.

[0172] Similar to DL BM, the UL BM procedure can also be divided into the terminal's Tx beam sweeping and the base station's Rx beam sweeping.

[0173] FIG. 13 is a diagram illustrating an uplink beam management operation using an SRS in a wireless communication system to which the present disclosure may be applied.

[0174] FIG. 13(a) illustrates the Rx beam determination operation of a base station, and FIG. 13(b) illustrates the Tx beam sweeping operation of a terminal.

[0175] FIG. 14 is a diagram illustrating an uplink beam management procedure in a wireless communication system to which the present disclosure may be applied.

[0176] The terminal receives RRC signaling (e.g., SRS-Config IE) from the base station, which includes usage parameters (upper layer parameters) set to 'beam management' (S1010).

[0177] Table 8 shows an example of an SRS-Config IE (Information Element), which is used for SRS transmission configuration. An SRS-Config IE includes a list of SRS-Resources and a list of SRS-ResourceSets. Each SRS resource set represents a set of SRS-resources.

[0178] The network can trigger the transmission of an SRS resource set using the configured aperiodicSRS-ResourceTrigger (L1 DCI).

[0179] -- ASN1START-- TAG-MAC-CELL-GROUP-CONFIG-STARTSRS-Config ::= SEQUENCE { srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N srs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N srs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need N srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need N tpc-Accumulation ENUMERATED {disabled} OPTIONAL, -- Need S ...}SRS-ResourceSet ::= SEQUENCE { srs-ResourceSetId SRS-ResourceSetId, srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond Setup resourceType CHOICE { aperiodic SEQUENCE { aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1), csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook slotOffset INTEGER (1..32) OPTIONAL, -- Need S ...}, semi-persistent SEQUENCE { associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook ...}, periodic SEQUENCE { associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook ...}},. usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching} , alpha Alpha OPTIONAL, -- Need S p0 INTEGER (-202..24) OPTIONAL, -- Cond Setup pathlossReferenceRS CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceIdSRS-SpatialRelationInfo ::= SEQUENCE { servingCellId ServCellIndex OPTIONAL, -- Need S referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs SEQUENCE { resourceId SRS-ResourceId, uplinkBWP BWP-Id}}}SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1)

[0180] In Table 8, 'usage' represents a higher-level parameter indicating whether the SRS resource set is used for beam management, or for codebook-based or non-codebook-based transmission. The 'usage' parameter corresponds to the L1 parameter 'SRS-SetUse'. 'spatialRelationInfo' is a parameter indicating the setting of the spatial relation between the reference RS and the target SRS. Here, the reference RS can be an SSB, CSI-RS, or SRS corresponding to the L1 parameter 'SRS-SpatialRelationInfo'. The above 'usage' is set per SRS resource set. The terminal determines the Tx beam for the SRS resource to be transmitted based on the SRS-SpatialRelation Info included in the SRS-Config IE (S1020). Here, the SRS-SpatialRelation Info is set per SRS resource and indicates whether to apply the same beam used in the SSB, CSI-RS, or SRS for each SRS resource. In addition, SRS-SpatialRelationInfo may or may not be set for each SRS resource.

[0181] If SRS-SpatialRelationInfo is set in the SRS resource, the same beam used in the SSB, CSI-RS, or SRS is applied and transmitted. However, if SRS-SpatialRelationInfo is not set in the SRS resource, the terminal arbitrarily determines a Tx beam and transmits the SRS through the determined Tx beam (S1030).

[0182] More specifically, for a P-SRS where 'SRS-ResourceConfigType' is set to 'periodic':

[0183] i) If SRS-SpatialRelationInfo is set to 'SSB / PBCH', the UE transmits the SRS resource by applying a spatial domain transmission filter that is identical to (or generated from) the spatial domain Rx filter used for receiving SSB / PBCH; or

[0184] ii) If SRS-SpatialRelationInfo is set to 'CSI-RS', the UE transmits the SRS resource by applying the same spatial domain transmission filter used for receiving periodic CSI-RS or SP (semi-persistent) CSI-RS; or

[0185] iii) When SRS-SpatialRelationInfo is set to 'SRS', the UE transmits the SRS resource by applying the same spatial domain transmission filter used for the transmission of periodic SRS.

[0186] Even when 'SRS-ResourceConfigType' is set to 'SP(semi-persistent)-SRS' or 'AP(aperiodic)-SRS', beam determination and transmission operations can be applied similarly to the above.

[0187] Additionally, the terminal may receive or not receive feedback on the SRS from the base station in the following three cases (S1040).

[0188] i) When Spatial_Relation_Info is set for all SRS resources within the SRS resource set, the terminal transmits SRS to the beam designated by the base station. For example, if Spatial_Relation_Info all designate the same SSB, CRI, or SRI, the terminal repeatedly transmits SRS to the same beam. This case corresponds to FIG. 13(a) for the purpose of the base station selecting the Rx beam.

[0189] ii) Spatial_Relation_Info may not be set for all SRS resources within the SRS resource set. In this case, the terminal can freely switch SRS beams and transmit. That is, this case corresponds to FIG. 13(b) for the purpose of sweeping the Tx beam by the terminal.

[0190] iii) Spatial_Relation_Info may be set for only some SRS resources within an SRS resource set. In this case, SRS is transmitted via the specified beam for the configured SRS resources, and for SRS resources for which Spatial_Relation_Info is not set, the terminal may arbitrarily apply a Tx beam to transmit.

[0191] quasi-co location (QCL)

[0192] An antenna port is defined such that the channel carrying a symbol on the antenna port can be inferred from the channel carrying another symbol on the same antenna port. If the property of the channel carrying a symbol on one antenna port can be inferred from the channel carrying a symbol on another antenna port, the two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship.

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

[0194] To decode the PDSCH according to the detected PDCCH having the DCI intended for the terminal and the given serving cell, a list of up to M TCI-State configurations within the upper-level parameter PDSCH-Config may be configured. The said M depends on the UE capability.

[0195] Each TCI-State includes parameters for establishing a quasi-co-location relationship between one or two DL reference signals and the DM-RS (demodulation reference signal) port of the PDSCH.

[0196] The quasi co-location relationship is established by the upper-level parameter qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if set). For two DL RSs, the QCL types are not the same regardless of whether the reference is the same DL RS or different DL RSs.

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

[0198] - 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

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

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

[0201] - 'QCL-TypeD': {Spatial Rx parameter}

[0202] For example, if the target antenna port is a specific NZP CSI-RS, the NZP CSI-RS antenna port may be indicated / configured to be QCLed with a specific TRS from the perspective of QCL-Type A and with a specific SSB from the perspective of QCL-Type D. A terminal that receives such indication / configuration can receive the NZP CSI-RS using the Doppler and delay values ​​measured at the QCL-Type A TRS, and can apply the receiving beam used for receiving the QCL-Type D SSB to receiving the NZP CSI-RS.

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

[0204] If a HARQ-ACK corresponding to a PDSCH carrying an active command is transmitted in slot n, the specified mapping between the TCI status and the code point of the DCI field 'Transmission Configuration Indication' is in slot n+3N slot subframe,μIt can be applied starting from +1. After receiving the initial upper layer configuration for the TCI states before the UE receives the activation command, for QCL-TypeA, and for QCL-TypeD if applicable, the UE may assume that the DMRS port of the serving cell's PDSCH is QCLed with the SS / PBCH block determined during the initial access process.

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

[0206] When the parameter tci-PresentInDCI is set to Enable, the TCI field within the DCI in the scheduling CC (component carrier) may indicate the active TCI state of the scheduling CC or DL ​​BWP. When a PDSCH is scheduled by DCI format 1_1, the UE may use the TCI state according to the value of the 'Transmission Configuration Indication' field of the detected PDCCH having the DCI to determine the PDSCH antenna port QCL.

[0207] If the time offset between the reception of DL DCI and the corresponding PDSCH is greater than a predetermined threshold (e.g., timeDurationForQCL), the UE may assume that the DMRS port of the PDSCH of the serving cell is QCLed with the RS(s) of the TCI state for the QCL type parameter(s) given by the indicated TCI state.

[0208] When a single slot PDSCH is configured for a UE, the indicated TCI state may be based on the active TCI state of the slot containing the scheduled PDSCH.

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

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

[0211] For both cases where the parameter tci-PresentInDCI is set to enable and where tci-PresentInDCI is not set in RRC connection mode, if the time offset between the reception of DL DCI and the corresponding PDSCH is less than a predetermined threshold (e.g., timeDurationForQCL), the UE may assume that the DMRS port of the PDSCH of the serving cell is QCL-controlled with the RS(s) for the QCL parameter(s) used for the PDCCH QCL indication of the CORESET associated with the monitored search space having the lowest CORESET-ID in the latest slot monitored by the UE, where one or more CORESETs within the active BWP of the serving cell.

[0212] In this case, if the QCL-TypeD of the PDSCH DMRS is different from the QCL-TypeD of the PDCCH DMRS and they overlap in at least one symbol, the UE can expect the reception of the PDCCH associated with the corresponding CORESET to be prioritized. This may also apply to intra-band carrier aggregation (where the PDSCH and CORESET are in different CCs). If none of the configured TCI states contain a QCL-TypeD, a different QCL assumption among the indicated TCI states can be obtained for the scheduled PDSCH, regardless of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0213] For periodic CSI-RS resources of an NZP-CSI-RS-ResourceSet configured with the upper layer parameter trs-Info, the UE can expect the TCI status to indicate one of the following QCL type(s):

[0214] - QCL-TypeC with SS / PBCH blocks, and, if applicable, QCL-TypeD with the same SS / PBCH blocks, or

[0215] - QCL-TypeC with SS / PBCH blocks, and QCL-TypeD with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including upper-level parameter repetition, if applicable.

[0216] For a non-periodic CSI-RS resource of NZP-CSI-RS-ResourceSet configured with upper layer parameter trs-Info, the UE can expect the TCI status to indicate QCL-TypeA with the periodic CSI-RS resource of NZP-CSI-RS-ResourceSet configured with upper layer parameter trs-Info, and, if applicable, QCL-TypeD with the same periodic CSI-RS resource.

[0217] For a CSI-RS resource of an NZP-CSI-RS-ResourceSet configured without the upper-level parameter trs-Info and without the upper-level parameter repetition, the UE can expect the TCI status to indicate one of the following QCL type(s):

[0218] - QCL-TypeA with the CSI-RS resource of the NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with the same CSI-RS resource, or

[0219] - QCL-TypeA with CSI-RS resources of an NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and QCL-TypeD with SS / PBCH blocks if applicable, or

[0220] - QCL-TypeA with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter repetition, or

[0221] - If QCL-TypeD is not applicable, QCL-TypeB with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured including the upper layer parameter trs-Info.

[0222] For a CSI-RS resource of an NZP-CSI-RS-ResourceSet configured with the upper-level parameter repetition, the UE can expect the TCI state to indicate one of the following QCL type(s):

[0223] - QCL-TypeA with the CSI-RS resource of the NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with the same CSI-RS resource, or

[0224] - QCL-TypeA with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter repetition, or

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

[0226] Regarding the DMRS of the PDCCH, the UE can expect the TCI state to indicate one of the following QCL type(s):

[0227] - QCL-TypeA with the CSI-RS resource of the NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with the same CSI-RS resource, or

[0228] - QCL-TypeA with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter repetition, or

[0229] - QCL-TypeA with CSI-RS resources of NZP-CSI-RS-ResourceSet configured without upper-level parameter trs-Info and without upper-level parameter repetition, and, if applicable, QCL-TypeD with the same CSI-RS resources.

[0230] For the DMRS of PDSCH, the UE can expect the TCI state to indicate one of the following QCL type(s):

[0231] - QCL-TypeA with the CSI-RS resource of the NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with the same CSI-RS resource, or

[0232] - QCL-TypeA with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter trs-Info, and, if applicable, QCL-TypeD with CSI-RS resources in an NZP-CSI-RS-ResourceSet configured including the upper-level parameter repetition, or

[0233] - QCL-TypeA with CSI-RS resources of NZP-CSI-RS-ResourceSet configured without upper-level parameter trs-Info and without upper-level parameter repetition, and, if applicable, QCL-TypeD with the same CSI-RS resources.

[0234] Beam linkage status-based uplink / downlink transmission and reception

[0235] Hereinafter, various examples of the present disclosure regarding uplink / downlink (UL / DL) transmission and reception based on a beam linkage state (BLS) will be described.

[0236] Spatial parameters related to downlink transmission and reception (or beam transmission and reception parameters) may include QCL information applied to or assumed by the terminal for the physical channel where downlink control information or data is transmitted or received. QCL information may include QCL RS (reference signal) information, and QCL RS information may be configured for each QCL type (e.g., QCL type A / B / C / D). For example, downlink control information (DCI) may 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 the PDCCH DMRS antenna port(s). Additionally, downlink data may 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 the PDSCH DMRS antenna port(s).

[0237] However, the term spatial parameter in this disclosure is not limited to QCL information and may include spatial parameters applied to uplink transmission (e.g., spatial relation info related to the uplink transmission beam). For example, uplink control information (UCI) may be transmitted and received via PUCCH and / or PUSCH, and spatial parameters related to UCI transmission and reception may include resource indicators (PRI) related to PUCCH / PUSCH transmission and reception, spatial relation info, or related QCL reference RS.

[0238] In addition, spatial parameters may be set separately for downlinks or uplinks, or they may be set integrally for downlinks and uplinks.

[0239] Additionally, a spatial parameter may be defined or set as a set of spatial parameters including one or more spatial parameters. For the sake of simplicity in the following description, one or more spatial parameters are collectively referred to as spatial parameters.

[0240] In order for a base station to set / indicate the terminal's PDCCH reception space parameters (or reception beam), it may set / update a TCI state ID for each of one or more CORESETs. The TCI state set for a CORESET may indicate QCL reference information (e.g., information related to QCL type D) for the PDCCH DMRS antenna port(s) transmitted through the corresponding CORESET. That is, the QCL reference information (e.g., QCL type D information) of the TCI state ID set / updated for each CORESET may correspond to the terminal's PDCCH reception beam.

[0241] For the setting / instruction of spatial parameters (or receive beams) for PDSCH reception, a TCI field may be included within the PDCCH DCI scheduling the PDSCH. The TCI status ID (or TCI code point) indicated by the TCI field within the DCI may indicate QCL reference information (e.g., information related to QCL type D) for the PDSCH DMRS antenna port(s).

[0242] Although the setting or instruction of spatial parameters for PDSCH reception can be performed dynamically via DCI, the spatial parameters indicated through DCI are limited to candidates for spatial parameters pre-configured via upper-layer signaling (e.g., RRC / MAC CE); therefore, upper-layer signaling is required to change or update spatial parameters for PDSCH reception. Since the spatial parameters for PDSCH reception are based on CORESET settings, setting or instruction of spatial parameters for PDSCH reception requires RRC resetting or the transmission of MAC CE messages for CORESET settings or updates. Additionally, if the DCI scheduling the PDSCH does not include spatial parameter information (e.g., TCI fields), the spatial parameters for PDSCH reception can be applied based on the spatial parameters configured for the CORESET being monitored by that DCI. Furthermore, even if spatial parameter information (e.g., TCI fields) is included within the DCI scheduling the PDSCH, if the time interval (or scheduling offset) between the time when the DCI / PDCCH scheduling the PDSCH is received and the time when the PDSCH is received is below a predetermined threshold, spatial parameters for PDSCH reception can be applied based on default spatial parameters (e.g., the TCI state associated with the CORESET or SS set having the lowest identifier in the latest slot monitored by the terminal). In this way, performing changes / updates to PDCCH / PDSCH spatial parameters / receive beams via upper-layer signaling (e.g., RRC / MAC CE) has the disadvantage of reducing flexibility as well as incurring unnecessary signaling overhead associated with such changes / updates.

[0243] To address this problem, the following examples describe UL / DL transmission and reception based on Beam Linked State (BLS) while minimizing signaling overhead.

[0244] In the following description, spatial parameters or spatial relation info may include RS information / QCL-related (or reference) RS information / QCL parameters, etc., for spatial relation assumptions for data / signals transmitted / received through UL channels / DL channels, or may be expressed by using or substituting the above terms.

[0245] In the following examples, the meaning of using / applying / mapping specific spatial parameters (or TCI state or TCI) when transmitting / receiving data / DCI / UCI for a certain frequency / time / space resource may mean, in the case of DL, that a channel is estimated from DMRS using the QCL type and QCL RS indicated by the spatial parameter in the frequency / time / space resource and data / DCI (e.g., PDSCH / PDCCH) is received / demodulated to the estimated channel, and in the case of UL, that DMRS and data / UCI (e.g., PUSCH / PUCCH) are transmitted / modulated using the transmit beam and / or transmit power indicated by the spatial parameter in the frequency / time / space resource.

[0246] Various examples of the present disclosure regarding UL / DL transmission and reception based on BLS in cases where multiple cells (or serving cells) are configured for a terminal (e.g., for a terminal where Carrier Aggregation (CA) is configured). A cell may consist of one or more downlink component carriers (DL CC) and zero or more uplink CCs (UL CC). For example, a cell may consist of multiple DL CCs and zero or more UL CCs. Additionally, one or more BWPs may be configured for a cell, and one BWP may be simultaneously activated for a terminal, but the scope of the present disclosure does not exclude cases where multiple BWPs are simultaneously activated for a terminal. For simplicity of explanation in the following examples, the term "cell" may be expressed as CC / BWP, but the scope of the present disclosure is not limited to cases where a cell contains only one CC or where only one BWP is activated for a cell.

[0247] As previously explained regarding downlink beam management and PDCCH receive beam setup / update, RRC resetting or MAC-CE message transmission is required to update the TCI state information of the CORESET setting or to set / update the PDSCH receive beam. Additionally, as previously explained regarding uplink beam management and PUCCH / PUSCH beam setup / update, RRC resetting of the spatial relation or MAC-CE message transmission is required for uplink beam setup / update. In other words, to set / update spatial parameters (i.e., transmit / receive parameters (Tx / Rx parameters) in the spatial domain) for beam management and the terminal's reference signal (RS) / channel (CH) transmission / reception, RRC resetting of the TCI state or spatial relation info, or MAC-CE messages, are required. Consequently, there is a problem in that not only is the flexibility for updating uplink and downlink transmit / receive beams reduced, but unnecessary signaling overhead is also caused by these updates.

[0248] To reduce the overhead of uplink beam changes / updates of terminals, a default spatial relation may be defined as an example of an operation to link the uplink beam RS to the downlink beam RS in the spatial relation info of PUCCH / PUSCH / SRS.

[0249] For example, if a CORESET is set in the active BWP of the corresponding DL CC, the terminal may set the QCL Type-D RS corresponding to the lowest CORESET ID as the default spatial relation. If no CORESET is set in the corresponding DL BWP, the terminal may set the QCL Type-D RS indicated by the TCI state corresponding to the lowest ID among the active PDSCH TCI state(s) as the default spatial relation.

[0250] If PUCCH exists in a UL CC / BWP, there will be at least one CORESET in the corresponding DL CC / BWP; therefore, for PUCCH, the QCL Type-D RS corresponding to the lowest CORESET ID can be set as the default spatial relation, and the default spatial relation setting based on TCI state(s) for PDSCH may not be applied. In the case of PUSCH, the default spatial relation may be applied to the PUSCH scheduled with a fallback DCI (e.g., DCI format 0_0). Additionally, if there is no PUCCH configured in the corresponding UL BWP (e.g., SCell UL), or if a default beam for PUCCH is enabled even though a PUCCH is configured but no spatial relation for the PUCCH is configured (e.g., when the RRC parameter enableDefaultBeamPlForPUCCH based on the UplinkConfig information element is set to enable), the default spatial relation operation may be performed. In this case, the terminal can set the TCI state / QCL assumption corresponding to the lowest CORESET ID of the DL CC / BWP scheduling PUSCH as the default spatial relation.

[0251] Regarding these default beam-related operations, since the transmission beam is restricted to connecting only to the TCI with the lowest CORESET ID or the lowest ID among the TCI states for PDSCH, there is a problem in that it is difficult to flexibly specify UL / DL integrated spatial parameters. In particular, when multiple CC / BWPs are configured, the flexibility of spatial parameter setting / updating is low, and there is a problem in that signaling overhead increases for setting / updating various spatial parameters.

[0252] For example, when a spatial parameter setting / update / activation is instructed for one of multiple CC / BWPs, the setting / update / activation of the said spatial parameter may also be applied to other CC / BWPs. This operation is referred to as simultaneous spatial parameter update below. According to this operation, a single spatial parameter can be applied commonly to multiple CC / BWPs to prevent the repetitive transmission of control signals based on CC-specific settings; however, independent operations must be performed for each transmit / receive spatial parameter instruction, and integrated spatial parameter changes / updates for RS(s) and / or channel(s) other than the target CH / RS are not supported. Therefore, as the number of configured CC / BWPs increases (for example, up to 32 CCs can be configured for a single terminal), it becomes problematic in terms of signaling overhead and flexibility regarding uplink / downlink spatial parameter changes. In addition, when spatial parameters for a specific RS / CH are indicated through the UL / DL DCI, there is a problem that the size of the spatial parameter indication field of the DCI must be increased and the payload size of the DCI increases.

[0253] To resolve this, according to the present disclosure, the transmission and reception spatial parameters that are changed / updated during the simultaneous spatial parameter update process for multiple CC / BWPs are defined as spatial parameters for reference transmission and reception (hereinafter, reference spatial parameters), and spatial parameters for target transmission and reception (e.g., RS / CH) in one or more of the multiple CC / BWPs (i.e., target spatial parameters) can be changed / updated based on BLS. That is, based on the reference spatial parameters, the spatial parameters for target transmission and reception can be changed / updated based on the BLS set for the corresponding CC / BWP.

[0254] In addition, a BLS defining the spatial parameter linkage relationship between the reference transmitter / receiver and the target transmitter / receiver can be established for each CC / BWP or for each CC / BWP group. Based on the BLS, the linkage relationship and range of spatial parameters between the reference transmitter / receiver and the target transmitter / receiver can be dynamically indicated.

[0255] A configuration for a BLS may include a configuration for one or more candidates for a BLS, and instructions for a specific BLS among the one or more BLS candidates. The configuration for the BLS candidates may be provided from a base station to a terminal via upper layer (e.g., RRC) signaling. Instructions for a specific BLS among the BLS candidates may be provided from a base station to a terminal via MAC-CE or DCI.

[0256] A BLS may include information regarding mapping relationships between one or more reference transmitters and one or more target transmitters. For example, each BLS candidate may define a mapping relationship between one reference transmitter and one or more target transmitters. A BLS may define a relationship in which a first spatial parameter for a reference transmitter is linked to a second spatial parameter for a target transmitter (for example, the second spatial parameter changes in accordance with a change in the first spatial parameter).

[0257] Here, the second spatial parameter may be identical to the first spatial parameter or may be a spatial parameter corresponding to the first spatial parameter. For example, the receiving spatial parameter (or receiving beam) of the terminal and the transmitting spatial parameter (or transmitting beam) of the terminal may have a corresponding relationship depending on the implementation of the terminal's transmitting and receiving filter. Alternatively, the first receiving spatial parameter (or receiving beam) of the terminal may have a corresponding relationship with the second receiving spatial parameter (or receiving beam), and the first transmitting spatial parameter (or transmitting beam) of the terminal may have a corresponding relationship with the second transmitting spatial parameter (or transmitting beam).

[0258] For example, the correspondence between these first and second spatial parameters may be predetermined according to a predetermined rule, predetermined by signaling exchange between a base station and a terminal, or predetermined according to the implementation of the terminal. Accordingly, the specific correspondence between spatial parameters is not defined in this disclosure, and various arbitrary correspondences may be applied. That is, in the examples of this disclosure, the correspondence between the first and second spatial parameters is assumed to be known in advance to the terminal and / or base station.

[0259] In addition, the terminal can receive information from the base station regarding a specific BLS that is active or valid among one or more candidates for BLS.

[0260] For example, information regarding a specific BLS can be indicated to the terminal through upper layer (e.g., MAC CE) or lower layer (e.g., DCI) signaling.

[0261] Accordingly, the terminal can determine target transmit / receive(s) mapped to reference transmit / receive based on a specific BLS. For example, the reference transmit / receive may be a first UL / DL reference signal (RS) / channel (CH), and the target transmit / receive may be a second UL / DL RS / CH. For example, the DL RS / CH may be a PDCCH, PDSCH, SSB, CSI-RS, etc., and the UL RS / CH may be a PUCCH, PUSCH, SRS, etc.

[0262] Accordingly, as spatial relation information as well as TCI state can be utilized as a reference spatial parameter, association flexibility for determining transmit and receive spatial parameters can be enhanced. Furthermore, since dynamic transmit and receive spatial parameter indication is possible through spatial parameter changes and updates based on association relationships, signaling overhead is reduced compared to spatial parameter / beam indication methods performed independently; additionally, there is the advantage of being able to omit fields related to spatial parameter / beam setup / indication within the DCI based on specific association relationships.

[0263] In order to prevent conflicts between the simultaneous spatial parameter update / activation operation in addition to the existing transmit / receive spatial parameter / beam setting / update and the spatial parameter setting / update operation based on BLS for multiple CC / BWP according to the present disclosure, an enabler for the spatial parameter setting / update operation based on BLS for multiple CC / BWP according to the present disclosure may be defined. That is, the examples of the present disclosure may be applied when the enabler parameter indicates that it is enabled. For example, a parameter (e.g., beam_linkage_multiCC_enabler) regarding whether the spatial parameter / beam setting / update operation is enabled through the application of BLS information considering multiple CC / BWP in the RRC setting may be set, and if the enabler is 'ON', the examples of the present disclosure (e.g., Examples 1 / 2 / 3) may be activated. If the enabler is 'OFF', the existing operation may be followed.

[0264] FIG. 15 is a flowchart illustrating a method for a terminal to perform uplink transmission or downlink reception based on a beam linkage state according to the present disclosure.

[0265] In step S1510, the terminal can receive configuration information from the base station regarding the first beam linkage status (BLS) for the first resource and the second BLS for the second resource.

[0266] Each of the first and second BLS may include information regarding the mapping relationship between a reference transmit / receive and one or more target transmit / receive. Additionally, the first BLS and the second BLS may be configured to be the same or different. The first BLS or the second BLS may not be configured directly, or may be configured based on a BLS configured for a third resource within the resource group to which the first resource or the second resource belongs.

[0267] Here, the resource may be configured based on one or more of the component carrier (CC), CC list, bandwidth portion (BWP), or band configured for the terminal.

[0268] In addition, information (e.g., an enabler) regarding whether uplink transmission by the terminal or downlink reception is performed based on the BLS may be provided from the base station.

[0269] In step S1520, the terminal can receive reference space parameter instruction information for reference transmission and reception for the first resource from the base station.

[0270] For example, the instruction information may indicate a reference spatial parameter that is applied simultaneously to the first resource and the second resource. That is, the instruction information may include information about a reference spatial parameter that is changed / updated according to a simultaneous spatial parameter update operation. The reference spatial parameter may be a spatial parameter applied to a reference transmission / reception set by the BLS.

[0271] If the reference transmission is a downlink reception, the reference spatial parameter may be indicated by the TCI state. If the reference transmission is an uplink transmission, the reference spatial parameter may be indicated by spatial relation info.

[0272] In step S1530, the terminal can perform uplink transmission or downlink reception on a second resource based on target space parameters for specific target transmission and reception.

[0273] A specific target transmission / reception may be one of one or more target transmissions / receptions that are mapped to the reference transmission / reception based on the second BLS.

[0274] A target spatial parameter may be determined based on a reference spatial parameter. For example, the target spatial parameter may be a spatial parameter corresponding to the reference spatial parameter for a second resource. More specifically, one or more target spatial parameter candidates corresponding to the reference spatial parameter may be determined, and a specific target spatial parameter may be determined from among the one or more target spatial parameter candidates. For example, the specific target spatial parameter may be determined as a spatial parameter according to a predefined rule (e.g., corresponding to the lowest or highest identifier), or as a spatial parameter indicated by downlink control information (DCI) related to uplink transmission or downlink transmission. Additionally, the correspondence relationship between the reference spatial parameter and the target spatial parameter may be predetermined.

[0275] FIG. 16 is a flowchart illustrating a method for a base station to perform uplink reception or downlink transmission based on a beam linkage state according to the present disclosure.

[0276] In step S1610, the base station can transmit configuration information for the first beam linkage state (BLS) for the first resource and the second BLS for the second resource to the terminal.

[0277] The same applies to resource and BLS settings as described in step S1510 of Fig. 15.

[0278] In step S1620, the base station can transmit reference space parameter instruction information for reference transmission and reception to the terminal for the first resource.

[0279] The same applies to reference transmission and reception and reference space parameter instructions as described in relation to step S1520 of FIG. 15.

[0280] In step S1630, the base station can perform uplink reception from the terminal or downlink transmission to the terminal on the second resource.

[0281] Here, the base station may expect the terminal to apply target spatial parameters based on simultaneous spatial parameter update operations for multiple resources (e.g., multiple CC / BWP) and BLS. For example, a downlink transmission by the base station on a second resource may be received by the terminal based on target spatial parameters for a specific target transmission among one or more target transmissions. An uplink reception by the base station on a second resource may be transmitted by the terminal based on target spatial parameters for a specific target transmission among one or more target transmissions.

[0282] The same applies to the target transmission / reception and target space parameters as described in relation to step S1530 of FIG. 15.

[0283] In the examples of FIGS. 15 and 16, the reference transmission or target transmission may be set to a predetermined UL / DL RS / CH or set based on a UL / DL RS / CH type. For example, the reference transmission or target transmission, or the type of the UL / DL RS / CH, may be defined based on one or more of the use, content, format, type, or time domain characteristics of the UL / DL RS / CH.

[0284] Various examples of the present disclosure regarding BLS-based UL / DL transmission and reception for multiple CC / BWPs are described below.

[0285] Example 1

[0286] This embodiment relates to a method for a base station to set BLS information for multiple CC / BWPs for a terminal. For example, the base station may set BLS information for multiple CC / BWPs through upper layer (e.g., RRC) signaling.

[0287] For example, a BLS can be configured as one or more units of a CC, a CC group, or a band. Additionally, the same or different BLS information may be configured for one or more of different CCs, CC groups, or bands.

[0288] First, an example of BLS being configured in CC units is explained. In the following description, CC as the unit for BLS configuration can be replaced with CC groups, bands, or a combination thereof.

[0289] For example, if a BLS setting for a specific CC is not signaled by the base station, BLS information set for other CCs associated with the specific CC (e.g., CCs included in the same CC group (or list or set)) may be defined to be applied to the specific CC. This can be described as a common BLS being applied across multiple CCs. If there are multiple other CCs associated with the specific CC, the BLS of a specific one among the CCs for which a BLS is set (e.g., the CC with the lowest or highest CC index) may be applied to the specific CC.

[0290] As an additional example, if a BLS setting is not signaled by the base station for a specific CC, it may be defined that a predefined BLS is applied. The predefined BLS may be a BLS with a BLS ID (or BLS candidate ID) of 0, or it may correspond to no beam linkage.

[0291] As an additional example, if the target transmit / receive (i.e., target RS / CH) indicated by the BLS set for the DL-only CC includes UL RS(s) / CH(s), the BLS may be applied only to the remaining RS(s) / CH(s) (e.g., DL RS(s) / CH(s)) excluding the UL RS(s) / CH(s). That is, the terminal may not expect to be set / instructed to a BLS that includes UL target transmit / receive in the DL-only CC.

[0292] Similarly, if the target transmit / receive (i.e., target RS / CH) indicated by the BLS set for the UL only CC includes DL RS(s) / CH(s), the BLS may be applied only to the remaining RS(s) / CH(s) (e.g., UL RS(s) / CH(s)) excluding the DL RS(s) / CH(s). That is, the terminal may not expect to be set / instructed by the UL only CC to have a BLS that includes DL target transmit / receive.

[0293] In addition, spatial parameters for target transmission and reception in the corresponding CC / BWP may be changed or updated based on reference spatial parameters that are changed or updated by simultaneous spatial parameter updates for multiple CCs. Here, the correlation between the reference spatial parameters and the target spatial parameters in the corresponding CC / BWP may follow the BLS set for the corresponding CC / BWP.

[0294] For example, the BLS based on changes / updates to DL spatial parameters and the BLS based on changes / updates to UL spatial parameters may be set independently or integrated. For the sake of simplicity of explanation, the following examples assume that the BLS is applied independently to DL / UL, but the scope of the present disclosure is not limited thereto and may include cases where the BLS is applied integratedly to DL / UL.

[0295] Information regarding the PDSCH receiving beam and the ACK / NACK PUCCH transmitting beam for the corresponding PDSCH can be indicated, respectively, through the TCI (transmission configuration indication) field and the PRI (PUCCH resource indicator) field of the existing DCI format 1_1. When BLS is applied, the PUCCH transmitting beam can be determined by applying spatial Tx parameters corresponding to the spatial Rx parameters used when receiving the PDSCH. Therefore, for each state, BLS can apply the transmitting and receiving beam indications of other RS(s) / CH(s) based on the reference change / update transmitting / receiving beam, and it is also possible to set the range for such application. For example, when the TCI state ID for CORESET#1 in a specific CC is changed / updated via MAC-CE, the BLS can be configured to change all CORESET beams to the corresponding TCI state ID, or to apply it to the PDSCH receive beam and / or specific PUCCH (e.g., SR PUCCH / A / N PUCCH / CSI PUCCH, etc.) / PUSCH, etc. As an example of the configuration for the BLS, BLS #1 can be configured as {PDCCH, A / N PUCCH, PUSCH}. In other words, reference spatial parameter information (e.g., reference TCI state ID) that serves as the basis for change / update based on upper layer signaling (e.g., RRC / MAC-CE, etc.) is configured, and target spatial parameters (associated with the reference spatial parameters) can be applied to the target transmit / receive (RS / CH) determined by the BLS (i.e., associated with the reference transmit / receive).

[0296] For example, a BLS defining the spatial parameter linkage relationship between a reference transmitter / receiver and a target transmitter / receiver can be defined as shown in the example in Table 9. Table 9 is merely an example and does not limit the technical scope of the present disclosure. Accordingly, a BLS may be defined by a rule of a different form than the example in Table 9.

[0297] Referring to Table 9, the spatial parameter linkage between the transmitters and receivers (PDSCH, ACK / NACK PUCCH, all configured PUCCH, PUSCH, PDCCH) can be expressed as 0 (i.e., not linked) and 1 (i.e., linked).

[0298] BLS PDSCH ACK / NACK PUCCH All configured PUCCH PUSCH PDCCH #1 1 1 0 0 0 #2 0 0 1 0 0 #3 1 0 0 1 0 #4 0 0 0 0 1 #5 1 1 0 1 0 #6 0 1 0 0 1 #7 1 0 1 1 0 #8 0 0 1 0 1 #9 1 1 0 1 1 #10 0 0 1 1 1

[0299] In relation to BLS, reference spatial parameters (e.g., reference TCI state ID, reference spatial relation info ID) can be pre-configured / instructed through upper-layer signaling (e.g., RRC / MAC-CE, etc.).

[0300] For example, in the example of Table 9, when BLS #6 is set / instructed, spatial parameters between ACK / NACK PUCCH and PDCCH can be linked. For example, PDCCH is the reference transmission / reception and the target transmission / reception is ACK / NACK PUCCH, and the reference spatial parameter (e.g., reference TCI state ID) for the reference transmission / reception PDCCH can be set / instructed in advance. When a simultaneous spatial parameter update operation is performed, the spatial Rx parameter for PDCCH reception is changed / updated to the spatial Rx parameter of the TCI state ID set according to the simultaneous spatial parameter update, and the spatial Tx parameter for ACK / NACK PUCCH can be changed / updated to the spatial Tx parameter corresponding to the spatial Rx parameter of the said TCI state ID.

[0301] Although ACK / NACK PUCCH was used as an example in Table 9, since there are various types of PUCCH depending on their purpose / use, the PUCCH for which the linkage relationship is defined by BLS is not limited to ACK / NACK PUCCH. For example, the linkage relationship for PUCCH type A and PUCCH type B may be defined by BLS. PUCCH type(s) may be predefined according to certain criteria or set to be explicitly distinguished. For example, PUCCH types may be distinguished based on the purpose / content / format / whether it is a dedicated PUCCH, etc.

[0302] For example, when distinguishing types based on the purpose of the PUCCH, Type A corresponds to a PUCCH for SR (scheduling request) / HARQ-ACK / CSI transmission, and Type B corresponds to a PUCCH for BFRQ (beam failure recovery request).

[0303] For example, when distinguishing types based on the PUCCH format, Type A corresponds to short PUCCH (e.g., PUCCH format 0, 2) and Type B corresponds to long PUCCH (e.g., PUCCH format 1, 3, 4).

[0304] For example, when distinguishing types based on whether they are dedicated PUCCH, Type A corresponds to a terminal-shared (or non-dedicated) PUCCH for HARQ-ACK purposes for Msg4 (i.e., a contention resolution message) during the RACH procedure, and Type B corresponds to a dedicated PUCCH (or terminal-specific) PUCCH.

[0305] In other words, the reference transmission and target transmission defined by BLS may be distinguished at the RS / CH level, and additionally, may be distinguished at the RS / CH type level.

[0306] As an additional example, the transmit / receive connections that can be linked by BLS (i.e., reference transmit / receive or target transmit / receive) may include PRACH, SRS, CSI-RS, etc., in addition to PUCCH, PUSCH, PDCCH, and PDSCH. In this case, BLS may be configured for one or more of PRACH, SRS, or CSI-RS, for one or more of RS units, resource type units, or RS resource units.

[0307] The aforementioned examples may include BLS being set identically or differently for multiple CC / BWPs.

[0308] The fact that BLS is configured differently for each CC may imply that mapping to BLS is possible for each CC among multiple CCs. That is, one BLS corresponding to one CC can be indicated / configured. For example, a pair of CC index and BLS index can be indicated / configured. For example, in a situation where 10 CCs are considered, {CC index, beam linkage state index} can be configured in the form of {(1, 1), (2, 2), (3, 4), _, (9, 5), (10, 7)}.

[0309] The fact that BLS is configured differently for each CC list (or group or set) may imply that mapping to BLS is possible for CC lists (e.g., a single CC list contains one or more CCs). For example, for sets of up to two CC(s) used in concurrent spatial parameter updates, a BLS may be associated / mapped to each. For example, a pair of CC list index and BLS index may be indicated / configured. For example, in a situation considering 10 CCs, CC list#1 = {CC1, CC3, CC5, CC7, CC9}, CC list#2 = {CC2, CC4, CC6, CC8, CC10}, and {CC list index, beam linkage state index} = {(1, 5), (2, 7)}, etc. In this case, all CCs belonging to each CC list may follow the corresponding (same) BLS configuration / instruction. Additionally, different CC lists may contain different CCs, and some or all of the CCs in different CC lists may be duplicated.

[0310] The fact that BLS is configured differently by band may correspond to implicitly considering CC(s) belonging to the same band as a single CC group based on the frequency band (e.g., NR band) applied to the CC(s) configured on the terminal. That is, CC(s) belonging to the same band can be interpreted as intra-band Carrier Aggregation (CA), while those between different bands can be interpreted as inter-band CA. Therefore, not only can the CC list be determined through the CC specified via the MAC-CE message, but the band to which the CC belongs and the band to which it does not belong can also be distinguished. Accordingly, other CC(s) within the band containing the changed / updated CC may be subject to a BLS with a wider coupling range for common beam operation, while CCs outside that band may be subject to only simultaneous spatial parameter update operations or a BLS with a relatively reduced coupling range. In this way, different BLS configurations can be applied by band.

[0311] For example, it can be assumed that BLS #1 is configured for intra-band CA and BLS #2 is configured for inter-band CA. In this case, when a spatial parameter update for CC#3 is configured / instructed in the MAC-CE for simultaneous spatial parameter updates, it may be determined that a simultaneous spatial parameter update is performed for CC list #1 containing CC#3 among a set of CC lists (e.g., CC list #1 = {CC1, CC3, CC5, CC7, CC9}, CC list #2 = {CC2, CC4, CC6, CC8, CC10}). At this time, if there exists an implicit CC group in which CC indices 1, 3, and 5 belong to band #1 and CC indices 7 and 9 belong to band #2, then for CC#3 of the MAC-CE, BLS #1 may be applied to CC indices 1, 3, and 5 belonging to the intra-band, and BLS #2 may be applied to CC indices 7 and 9. If a spatial parameter update for CC#9 is set / instructed in MAC-CE, a simultaneous spatial parameter update is performed for the CCs in CC list #1, and among the CCs in CC list #1, BLS#1 is applied to CC index 7 and 9, and BLS#2 is applied to CC index 1, 3, and 5.

[0312] As an additional example, the BLS configuration information may include a list of applicable CC / BWPs and / or CORESET ID(s). That is, when a BLS is configured / instructed, the CC(s) / BWP(s) to which the BLS applies can be configured separately for each BLS. Additionally, the CORESET ID(s) of the BWP(s) within the CC used for the PDCCH receiving beam can be configured separately for each BLS. In this case, if a specific CORESET ID(s) do not exist in the BWP(s) within the CC to which the BLS is configured, or if a CORESET configuration does not exist, spatial parameter (e.g., TCI state) updates may not be applied to the BWP(s). Alternatively, the terminal may not expect CORESET IDs other than those commonly configured for all BWP(s) within the CC to be configured as targets for spatial parameter updates or included in the BLS configuration.

[0313] For example, the aforementioned examples can be performed through BLS configuration / instruction via MAC-CE. That is, a specific ID for BLS can be specified via MAC-CE along with TCI state activation or spatial relation update. Accordingly, spatial parameters can be changed / updated according to the specified method from a specific point in time (e.g., applicable timing, etc.) until the next instruction via MAC-CE. Additionally, specific fields of DCI (e.g., TCI field, PRI field, etc.) may be omitted depending on the specific BLS.

[0314] Example 2

[0315] This embodiment relates to a method for determining target spatial parameters based on BLS for multiple CC / BWPs when the reference spatial parameters are TCI state(s).

[0316] For example, the terminal can modify / activate / instruct RS information to derive spatial Tx / Rx parameters for multiple CC / BWPs by utilizing TCI state(s) activated through simultaneous spatial parameter updates (e.g., TCI state). That is, when a specific TCI state ID(s) is activated by the base station instructing the terminal to update simultaneous spatial parameters via MAC-CE, the terminal can determine transmit / receive spatial parameters for target RS(s) / CH(s) using (or based on) the activated TCI state(s).

[0317] The TCI state (i.e., reference spatial parameter) that is the target of simultaneous spatial parameter updates for multiple CC / BWPs can be determined to be the same or different for each CC / BWP.

[0318] As a first example, both QCL Type-A and Type-D RS can be changed to the RS included in the directed / activated TCI state ID.

[0319] As a second example, only QCL Type-D RS can be changed to the RS included in the TCI state ID that is directed / activated.

[0320] As a third example, the same TCI state ID can be enabled / directed in the corresponding CC(s).

[0321] When the TCI state for PDCCH / PDSCH is indicated / activated via MAC-CE and / or DCI, the QCL Type-D RS or spatial relation RS for the target RS(s) / CH(s) indicated by the BLS pre-configured via RRC is applied as the corresponding indicated / activated TCI state (i.e., the TCI state indicated / activated via MAC-CE / DCI). This may mean that the TCI state (or spatial parameters or QCL information) indicated / activated via MAC-CE / DCI takes precedence over the TCI state (or spatial parameters or QCL information) of the BLS configured via RRC. Alternatively, a separate indicator may be used to additionally configure / indicate whether the indicated / activated TCI state is applied only to the target RS / CH corresponding to the indication / activation message.

[0322] The simultaneous spatial parameter update operation may include TCI state activation for the receiving beam and spatial relation update for the transmitting beam. In the case of receiving beam change / update from a downlink perspective, a TCI state set for PDSCH (e.g., consisting of up to 8 TCI state IDs) or a TCI state ID for CORESET may be specified via MAC-CE. Specific examples of beam change / update methods based on this are described below.

[0323] Example 2-1

[0324] According to the simultaneous spatial parameter update operation, when a set of TCI-state IDs for PDSCH is activated via MAC-CE for a specific CC, the set of TCI-state IDs for PDSCH may be activated not only for the specific CC but also for other CC(s) belonging to the CC list containing the specific CC. Here, for the specific CC and the other CC(s), information related to Tx / Rx spatial parameters for (other) target RS(s) / CH(s) pre-configured by BLS, as well as the set of TCI-state IDs for PDSCH, may be changed / updated together. That is, the set of TCI-state IDs for PDSCH activated / directed by the simultaneous spatial parameter update corresponds to the aforementioned reference spatial parameter, and the target spatial parameter of the target RS / CH linked by BLS to the reference transmission / reception to which the reference spatial parameter applies may also be changed / updated based on the reference spatial parameter.

[0325] With respect to the activation of TCI state candidate sets, all or part of the set of TCI state IDs (or QCL Type-D RS(s) indicated by the set of TCI state IDs) may be activated as candidate(s) for QCL Type-D RS(s) / spatial relations RS(s) (i.e., target spatial parameters) for the target RS(s) / CH(s) of the BLS. In this case, the QCL Type-D RS / spatial relation RS to be applied to each target RS / CH transmission / reception may be specified separately. Similarly, candidate(s) for target spatial parameters may be activated for other RS(s) / CH(s) associated by the BLS.

[0326] In relation to the indication of a specific TCI state, an RS(e.g., QCL Type-D RS)(e.g., QCL Type-D RS)(e.g., QCL Type-D RS(e.g., QCL Type-D RS(e.g., DL RS(e.g., DL RS(e.g., QCL Type-D RS(e.g., UL RS(e.g., UL RS(e.g., DL RS(e.g., DL RS(e.g., UL

[0327] For example, the above specific TCI state can be determined as a TCI state corresponding to a predefined rule (e.g., the lowest or highest TCI state ID) among the TCI state candidate(s).

[0328] As an additional example, the specific TCI state mentioned above may be determined as a TCI state corresponding to a TCI codepoint indicated by a TCI field included in a DCI (e.g., DCI format 1_1).

[0329] With respect to the coverage of TCI states, where all or part of the set of TCI state IDs is separately designated as a spatial parameter to be applied to target RS / CH transmission and reception, or where a specific single TCI state is determined, the coverage of the RS(s) for that TCI state (i.e., the TCI state as a reference spatial parameter) may follow the following examples.

[0330] If the target RS / CH includes PUCCH (or SR PUCCH, ACK / NACK PUCCH, CSI PUCCH), spatial parameters based on the RS(s) of the corresponding reference TCI state can be applied to the spatial relation RS for all PUCCH resources. Alternatively, spatial parameters based on the RS(s) of the corresponding reference TCI state can be applied to the spatial relation RS for the PUCCH resource group for SR PUCCH, ACK / NACK PUCCH, and CSI PUCCH, depending on the use of the target PUCCH.

[0331] If the target RS / CH includes an SRS, spatial parameters based on the RS(s) of the corresponding reference TCI state may be applied to the spatial relation RS for the SRS resource according to the use of the SRS (e.g., beam management (BM), codebook-based (CB), non-codebook-based (non-CB), antenna switching (AS)) and / or the time domain characteristics of the SRS (e.g., periodic / semi-static / non-periodic). For example, the use / time domain characteristics of the SRS may be set based on upper-layer signaling (e.g., the SRS-Resourceset parameter of the SRS-Config information element).

[0332] If the target RS / CH includes CSI-RS, spatial parameters based on the RS(s) of the corresponding reference TCI state may be applied to the spatial relation RS for the CSI-RS resource for each use of CSI-RS (e.g., BM, TRS, CSI acquisition) and / or time domain characteristics of CSI-RS (e.g., periodic / semi-static / non-periodic). For example, the use of CSI-RS may be set based on upper-level signaling (e.g., CSI report config), and the time domain characteristics of CSI-RS may be set based on upper-level signaling (e.g., CSI-ResourceConfig or CSI report config).

[0333] The examples of Example 2-1 correspond to a method of changing / updating the spatial parameters of target RS(s) / CH(s) according to BLS based on up to 8 TCI state ID(s) activated per CC / BWP via MAC-CE among up to 128 TCI states set by the upper layer. Here, the method of indicating reference spatial parameter information is described below.

[0334] First, all or part of the set of activated TCI state IDs may be used as candidate QCL Type-D RS or candidate spatial relation RS for determining the spatial parameters of the target RS(s) / CH(s) set by the BLS. Here, the QCL Type-D RS / spatial relation RS to be applied to each target RS / CH may be specified separately.

[0335] For example, if a target RS / CH in a configured BLS includes PUSCH, the spatial relation RS to be applied to the actual PUSCH transmission can be specified separately via DCI in the case of a grant-based PUSCH, or via RRC / MAC-CE / DCI in the case of a configured grant-based PUSCH.

[0336] For example, if the target RS / CH in the configured BLS includes a PDCCH, the QCL Type-D RS to be applied to the actual PDCCH reception can be indicated via the DCI of the grant-based PDSCH.

[0337] As an additional example, if a set of TCI state IDs is enabled for a specific CC, the TCI state IDs of the CORESETs of the BWP(s) of said specific CC can be changed / updated. For example, the application of an enabled TCI state to multiple CORESETs can be based on a one-to-one correspondence between a CORESET ID and a set of TCI state IDs, or TCI state(s) can be applied to one or more CORESET(s) according to a predefined rule.

[0338] As an additional example, a specific TCI state can be indicated through a predefined rule for a set of activated TCI state IDs, and then BLS-based operations can be performed using the received beam information at said specific TCI state as a reference. Here, the predefined rule may be a TCI state ID mapped to the lowest or highest TCI codepoint. If there are multiple TCI state IDs associated with a specific (e.g., lowest / highest) TCI codepoint, the QCL / spatial relation information indicated by the lowest or highest TCI state ID among them can be determined as the reference spatial parameter. Additionally, to support more dynamic spatial parameter indication, the spatial parameter of the TCI state ID corresponding to the TCI codepoint indicated in the TCI field included in DCI format 1_1 can be determined as the reference spatial parameter.

[0339] As described above, if all or part of a specific set of TCI state IDs is separately specified as a QCL Type-D RS / spatial relation RS to be applied to the target RS / CH, or if a specific single TCI state is specified, the scope of application according to the BLS of the RS(s) for the corresponding TCI state can be set implicitly or explicitly.

[0340] For example, a scheduling request (SR) means that a terminal requests a UL grant (e.g., DCI format 0 series) from a base station for PUSCH transmission. In this case, the terminal uses an SR PUCCH (e.g., PUCCH format 0 or PUCCH format 1), and the corresponding PUCCH resource can be configured by an upper layer parameter (e.g., the PUCCH-ResourceID (PRI) parameter of the SchedulingRequestResourceConfig information element of the RRC). Therefore, a transmit beam change / instruction for an SR PUCCH based on BLS can be applied to the PUCCH resource(s) configured for SR use. Alternatively, a transmit beam change / instruction based on BLS can be applied to all resources configured for PUCCH use.

[0341] For example, for ACK / NACK PUCCH, in the case of DCI format 1_1, the transmit beam may be determined according to the 3-bit PRI field within the DCI field. BLS-based transmit beam change / instruction may be applied to the resource(s) for the corresponding ACK / NACK PUCCH. Or BLS-based transmit beam change / instruction may be applied to all resources for PUCCH.

[0342] For example, for PUCCHs used for periodic (P) / semi-static (SP) CSI reporting, BLS-based transmit beam changing / direction may be applied to the resource(s) used for P / SP CSI reporting. Alternatively, BLS-based transmit beam changing / direction may be applied to all resources used for PUCCH.

[0343] Accordingly, when setting up PUCCH-related configurations based on BLS, if a PUCCH for a specific use (e.g., SR PUCCH / A / N PUCCH / CSI PUCCH) is configured, the terminal can expect that the transmission beam will be changed / directed to the PUCCH resource(s) for that use. Alternatively, if all PUCCH use resource(s) are configured, the terminal can expect that the transmission beam will be changed / directed to the PUCCH based on BLS.

[0344] As an additional example, for SRS or CSI-RS, transmit beam changes / updates according to BLS can be applied based on the reference TCI state for resource(s) according to their respective uses, for resource(s) according to time domain characteristics (P / SP / aperiodic (AP)), or for resource(s) that consider both use and time domain characteristics simultaneously.

[0345] As described above, among the TCI state candidate groups, the DL reference RS and QCL assumptions / information of a specific TCI state ID can be determined, and the terminal can change / update the reference RS of spatial relation info applied to the transmission of target UL RS(s) / CH(s) based on the DL reference RS and QCL assumptions / information based on BLS. Additionally, the reference RS and QCL assumptions / information of the TCI state applied to the reception of target DL RS(s) / CH(s) can be changed / updated based on the DL reference RS and QCL assumptions / information based on BLS.

[0346] Example 2-2

[0347] According to the simultaneous spatial parameter update operation, when a TCI state ID for a CORESET is indicated via MAC-CE for a specific CC, the TCI state ID for the CORESET may be activated not only for the specific CC but also for other CC(s) belonging to the CC list containing the specific CC. Here, for the specific CC and the other CC(s), information related to Tx / Rx spatial parameters for (other) target RS(s) / CH(s) pre-configured by BLS, as well as the TCI state ID for the CORESET, may be changed / updated together. That is, the TCI state ID for the CORESET activated / indicated by the simultaneous spatial parameter update corresponds to the aforementioned reference spatial parameter, and the target spatial parameter of the target RS / CH linked by BLS to the reference transmission / reception to which the reference spatial parameter applies may also be changed / updated based on the reference spatial parameter.

[0348] The TCI state (i.e., reference spatial parameter) that is the target of simultaneous spatial parameter updates for multiple CC / BWPs can be determined to be the same or different for each CC / BWP.

[0349] As a first example, both QCL Type-A and Type-D RS can be changed to RS included in the specified TCI state ID.

[0350] As a second example, only QCL Type-D RS can be changed to the RS included in the specified TCI state ID.

[0351] As a third example, the same TCI state ID can be activated / directed in the corresponding CC(s) where the TCI state ID is directed.

[0352] As a fourth example, the TCI state indicated in the CC(s) other than the CC(s) indicated in the TCI state ID can be activated by including the indicated TCI state as a candidate TCI state for the CORESET.

[0353] For a CC / BWP for which a CORESET setting does not exist (e.g., a SCell having a DL CC scheduled in cross-carrier scheduling), if the target RS / CH indicated by the BLS includes a PDCCH, the BLS may be applied only to the remaining RS(s) / CH(s) excluding the PDCCH. Alternatively, the terminal may not expect to be indicated by a BLS including a PDCCH for a CC / BWP for which a CORESET setting does not exist.

[0354] For BWP(s) of a specific CC(s) within a CC list (or group or set), if there is no CORESET ID indicated by MAC-CE and the target RS / CH indicated by BLS does not include PDCCH, TCI state updates may not be applied to the BWP(s), or CORESET ID(s) may be selected according to a predefined rule (e.g., the lowest or highest CORESET ID). Alternatively, the terminal may not expect a CORESET ID other than the CORESET ID(s) commonly set for all BWP(s) within the CC to be set by MAC-CE.

[0355] The scope of application of the TCI state can be determined as follows.

[0356] If the target RS / CH includes PUCCH (or SR PUCCH, ACK / NACK PUCCH, CSI PUCCH), spatial parameters based on the RS(s) of the corresponding reference TCI state can be applied to the spatial relation RS for all PUCCH resources. Alternatively, spatial parameters based on the RS(s) of the corresponding reference TCI state can be applied to the spatial relation RS for the PUCCH resource group for SR PUCCH, ACK / NACK PUCCH, and CSI PUCCH, depending on the use of the target PUCCH.

[0357] If the target RS / CH includes an SRS, spatial parameters based on the RS(s) of the corresponding reference TCI state can be applied to the spatial relation RS for the SRS resource according to the use of the SRS (e.g., beam management (BM), codebook-based (CB), non-codebook-based (non-CB), antenna switching (AS)) and / or the time domain characteristics of the SRS (e.g., periodic / semi-static / non-periodic).

[0358] If the target RS / CH includes CSI-RS, spatial parameters based on the RS(s) of the corresponding reference TCI state can be applied to the spatial relation RS for the CSI-RS resource according to the use of CSI-RS (e.g., BM, TRS, CSI acquisition) and / or the time domain characteristics of CSI-RS (e.g., periodic / semi-static / non-periodic).

[0359] The examples of Example 2-2 correspond to a method of changing / updating the spatial parameters of the target RS(s) / CH(s) according to BLS based on the indicated TCI state when the TCI state is indicated for the CORESET ID for a specific CC via MAC-CE. In this case, similar to Example 2-1, the UL / DL transmit / receive beam (i.e., spatial parameters) for the target transmit / receive can be determined according to the BLS settings based on the indicated TCI state.

[0360] If a PDCCH is included in the target RS / CH of the configured BLS, the activated TCI state(s) of all CORESET ID(s) including the CORESET ID indicated by the MAC-CE as described above may be changed / updated based on the QCL Type-D RS of the TCI state (i.e., reference spatial parameter) that is changed / updated through the MAC-CE. Alternatively, even if the indicated CORESET ID does not exist in a specific BWP(s) of a specific CC, the application of common spatial parameters may be configured so that the activated TCI state(s) of the remaining CORESET ID(s) are changed / updated based on the TCI state that is the reference spatial parameter. Alternatively, if the indicated CORESET ID does not exist in a specific BWP(s) of a specific CC, the change / update of the TCI state for the CORESET may not be applied to the BWP(s).

[0361] In the configured BLS, if the target RS / CH does not include a PDCCH and the BWP(s) of a specific CC(s) have a CORESET ID indicated by MAC-CE, the transmit / receive beams (i.e., target space parameters) for the UL / DL RS(s) / CH(s) can be updated according to the BLS by changing / updating the TCI state for the CORESET ID that is the same as the CORESET ID in the CC(s) within the CC list (or group or set).

[0362] If the target RS / CH in the configured BLS does not include a PDCCH and the BWP(s) of a specific CC(s) do not have a CORESET ID specified by MAC-CE, the TCI state update may not be applied to the BWP(s). Alternatively, the TCI state specified by MAC-CE may be applied according to a predefined rule to the remaining CORESET ID(s), excluding the lowest / highest CORESET ID or CORESET 0. Alternatively, the terminal may not expect a CORESET ID other than the CORESET ID(s) commonly configured for all BWP(s) within the CC to be configured through MAC-CE, and may operate accordingly.

[0363] Example 3

[0364] This embodiment relates to a method for determining target spatial parameters based on BLS for multiple CC / BWPs when the reference spatial parameter is spatial relation info.

[0365] For example, the terminal can modify / activate / instruct RS information to derive spatial Tx / Rx parameters for target RS(s) / CH(s) pre-configured by BLS for other CC(s) belonging to a CC list (or group or set) that includes the specific CC, by utilizing spatial relation info activated for a specific CC through a simultaneous spatial parameter update (e.g., spatial relation info) for a non-periodic (AP) / semi-static (SP) SRS. That is, when a specific spatial relation info is activated by the base station to the terminal through a simultaneous spatial parameter update, the terminal can determine the transmit / receive spatial parameters for the target RS(s) / CH(s) using (or based on) the activated TCI state(s).

[0366] The spatial relation info (i.e., reference spatial parameter) that is the target of simultaneous spatial parameter updates for multiple CC / BWPs can be determined to be the same or different for each CC / BWP.

[0367] As a first example, the spatial parameters for the target RS / CH can be changed using the RS included in the specified spatial relation info.

[0368] As a second example, the same spatial relation ID can be enabled / directed in the corresponding CC(s).

[0369] With regard to the activation of spatial relation candidate groups, all or part of the spatial relation info (or the spatial relation RS of the spatial relation info) may be activated as candidate(s) of QCL Type-D RS(s) / spatial relations RS(s) (i.e., target spatial parameters) for the target RS(s) / CH(s) of the BLS. In this case, the QCL Type-D RS / spatial relation RS to be applied to each target RS / CH transmission / reception may be specified separately. Similarly, candidate(s) of target spatial parameters may also be activated for other RS(s) / CH(s) associated by the BLS.

[0370] In relation to the indication of a specific spatial relation, an RS (e.g., spatial relation RS) corresponding to a specific spatial relation info among the activated spatial relation info(s) may be used as an RS for deriving spatial Tx / Rx parameters for a target RS / CH (e.g., QCL Type-D RS for DL ​​RS / CH, spatial relation RS for UL RS / CH). The specific spatial relation info may be determined based on predefined rules. Once the specific spatial relation info is determined, the method of applying the RS or indicator accordingly may follow the aforementioned examples of changing the spatial parameters for the target RS / CH with the RS included in the indicated spatial relation info, or activating / indicating the same spatial relation ID in the corresponding CC(s).

[0371] For example, the aforementioned specific spatial relation info can be determined through a predefined rule (e.g., as the spatial relation info having the lowest or highest ID).

[0372] As an additional example, the aforementioned specific spatial relation info may be determined as a spatial relation info having a specific ID (e.g., an ID indicated via MAC-CE) among the activated spatial relation info(s).

[0373] As an additional example, when concurrent spatial parameter updates using BLS are enabled, the spatial relation RS(s) may be determined identically to the aforementioned specific spatial relation info in each CC / BWP, depending on the number of resources within the CC / BWP set to which the concurrent spatial parameter updates are applied.

[0374] With respect to the scope of spatial relation, if all or part of the activated spatial relation info(s) are separately designated as spatial parameters to be applied to target RS / CH transmission and reception, or if a specific TCI state is determined, the scope of the RS(s) for the said spatial relation info (i.e., spatial relation info as a reference spatial parameter) may follow the following examples.

[0375] If the target RS / CH includes PUCCH (or SR PUCCH, ACK / NACK PUCCH, CSI PUCCH), spatial parameters based on the corresponding reference spatial relation RS(s) can be applied to the spatial relation RS for all PUCCH resources. Alternatively, spatial parameters based on the corresponding reference spatial relation RS(s) can be applied to the spatial relation RS for the PUCCH resource group for SR PUCCH, ACK / NACK PUCCH, and CSI PUCCH, depending on the use of the target PUCCH.

[0376] If the target RS / CH includes an SRS, spatial parameters based on the corresponding reference spatial relation RS(s) can be applied to the spatial relation RS for the SRS resource according to the use of the SRS (e.g., BM, CB, non-CB, AS) and / or the time domain characteristics of the SRS (e.g., P / SP / AP). Alternatively, if spatial relation info is enabled through MAC-CE, the time domain characteristics of the SRS may be limited to SP or AP SRS.

[0377] If the target RS / CH includes CSI-RS, spatial parameters based on the corresponding reference spatial relation RS(s) may be applied to the spatial relation RS for the CSI-RS resource according to the use of the CSI-RS (e.g., BM, TRS, CSI acquisition) and / or the time domain characteristics of the CSI-RS (e.g., periodic / semi-static / non-periodic). Alternatively, if spatial relation info is enabled via MAC-CE, the time domain characteristics of the CSI-RS may be limited to SP or AP CSI-RS.

[0378] For a CC / BWP for which a CORESET setting does not exist (e.g., a SCell having a DL CC scheduled in cross-carrier scheduling), if the target RS / CH indicated by the BLS includes a PDCCH, the BLS may be applied only to the remaining RS(s) / CH(s) excluding the PDCCH. Alternatively, the terminal may not expect to be indicated by a BLS including a PDCCH for a CC / BWP for which a CORESET setting does not exist.

[0379] For BWP(s) of a specific CC(s) within a CC list (or group or set), if there is no CORESET ID indicated by MAC-CE and the target RS / CH indicated by BLS does not include PDCCH, TCI state updates may not be applied to the BWP(s), or CORESET ID(s) may be selected according to a predefined rule (e.g., the lowest or highest CORESET ID). Alternatively, the terminal may not expect a CORESET ID other than the CORESET ID(s) commonly set for all BWP(s) within the CC to be set by MAC-CE.

[0380] The examples of Example 3 can be applied when changing / updating spatial relation information for SP / AP SRS resources simultaneously for multiple CCs / BWPs via MAC-CE. For example, spatial relation information for SP SRS can be included in an activation command for the SRS resource indicated via MAC-CE. For example, spatial relation information for AP SRS can be included in a spatial relation update command indicated via MAC-CE. In this case, the SP / AP SRS resource set ID of a specific CC can be indicated via MAC-CE, and UL-based RS(s) can be set according to the number of resources within that set.

[0381] First, all or part of the activated spatial relation info(s) may be used as candidate QCL Type-D RS or candidate spatial relation RS for determining the spatial parameters of the target RS(s) / CH(s) set by the BLS. Here, the QCL Type-D RS / spatial relation RS to be applied to each target RS / CH may be specified separately.

[0382] For example, if a target RS / CH in a configured BLS includes PUSCH, the spatial relation RS to be applied to the actual PUSCH transmission can be specified separately via DCI in the case of a grant-based PUSCH, or via RRC / MAC-CE / DCI in the case of a configured grant-based PUSCH.

[0383] As an additional example, after indicating a specific spatial relation info through a predefined rule for the activated spatial relation info(s), BLS-based operations can be performed using the transmit beam information at said specific spatial relation info as a reference. Here, the predefined rule may be the spatial relation info having the lowest or highest ID. Additionally, to support more dynamic spatial parameter indication, the spatial parameter of the spatial relation info associated with the SRS resource indicated by the SRI field included in the DCI may be determined as the reference spatial parameter.

[0384] When a specific CC's SP / AP SRS resource set ID is indicated via MAC-CE and UL reference RS(s) are indicated separately according to the number of resources within the set, spatial relation info for the UL reference RS is set as a reference spatial parameter for the BLS according to a predefined rule based on the resource index (e.g., lowest / highest index), and a change / update to the target spatial parameter can be performed accordingly.

[0385] As an additional example, based on explicit rules, among the UL reference RS(s) enabled by MAC-CE, an RS index to be used as a reference space parameter in BLS-based operation may be indicated.

[0386] As an additional example, when the enabler for BLS-based operation is set to 'ON', the terminal may expect the settings of the UL standard RS(s) to be the same according to the number of resources in the SRS resource set indicated by MAC-CE.

[0387] As mentioned above, if all or part of specific spatial relation info(s) are separately specified as QCL Type-D RS / spatial relation RS to be applied to the target RS / CH, or if a specific single spatial relation info is specified, the scope of application according to the RS's BLS for said spatial relation info can be implicitly or explicitly set.

[0388] For example, a scheduling request (SR) means that a terminal requests a UL grant (e.g., DCI format 0 series) from a base station for PUSCH transmission. In this case, the terminal uses an SR PUCCH (e.g., PUCCH format 0 or PUCCH format 1), and the corresponding PUCCH resource can be configured by an upper layer parameter (e.g., the PUCCH-ResourceID (PRI) parameter of the SchedulingRequestResourceConfig information element of the RRC). Therefore, a transmit beam change / instruction for an SR PUCCH based on BLS can be applied to the PUCCH resource(s) configured for SR use. Alternatively, a transmit beam change / instruction based on BLS can be applied to all resources configured for PUCCH use.

[0389] For example, for ACK / NACK PUCCH, in the case of DCI format 1_1, the transmit beam may be determined according to the 3-bit PRI field within the DCI field. BLS-based transmit beam change / instruction may be applied to the resource(s) for the corresponding ACK / NACK PUCCH. Or BLS-based transmit beam change / instruction may be applied to all resources for PUCCH.

[0390] For example, for PUCCHs used for periodic (P) / semi-static (SP) CSI reporting, BLS-based transmit beam changing / direction may be applied to the resource(s) used for P / SP CSI reporting. Alternatively, BLS-based transmit beam changing / direction may be applied to all resources used for PUCCH.

[0391] Accordingly, when setting up PUCCH-related configurations based on BLS, if a PUCCH for a specific use (e.g., SR PUCCH / A / N PUCCH / CSI PUCCH) is configured, the terminal can expect that the transmission beam will be changed / directed to the PUCCH resource(s) for that use. Alternatively, if all PUCCH use resource(s) are configured, the terminal can expect that the transmission beam will be changed / directed to the PUCCH based on BLS.

[0392] As an additional example, for SRS or CSI-RS, transmit beam changes / updates according to BLS can be applied based on reference spatial relation info for resource(s) according to their respective uses, for resource(s) according to time domain characteristics (P / SP / aperiodic (AP)), or for resource(s) that consider both use and time domain characteristics simultaneously.

[0393] In the case of updating a PUCCH spatial relation through MAC-CE, since the corresponding resource ID and the UL reference RS for the spatial relation info in a specific CC are indicated, the spatial parameters of the RS(s) / CH(s) can be changed / updated according to BLS based on the spatial relation RS of the indicated PUCCH spatial relation info, similar to the BLS-based operation of applying the TCI state for the CORESET of Example 2-2 as a reference spatial parameter.

[0394] For example, if a PDCCH is included in the target RS / CH of the configured BLS, the activated TCI state(s) of all CORESET ID(s) of the CC indicated by the MAC-CE as described above may be changed / updated to spatial reception parameters corresponding to spatial transmission parameters via the spatial relation RS of the spatial relation info (i.e., reference spatial parameters) that is changed / updated through the MAC-CE. Alternatively, even if the indicated CORESET ID does not exist in a specific BWP(s) of a specific CC, the application of common spatial parameters may be configured so that the activated TCI state(s) of the remaining CORESET ID(s) are changed / updated based on the spatial relation info, which is the reference spatial parameter. Alternatively, if the indicated CORESET ID does not exist in a specific BWP(s) of a specific CC, the change / update of the TCI state for the CORESET may not be applied to the corresponding BWP(s).

[0395] FIG. 17 is a drawing for explaining a signaling process according to one embodiment of the present disclosure.

[0396] An example of the signaling operation of a base station and a terminal for the aforementioned embodiments may be as shown in FIG. 17. Here, the terminal / base station is merely an example and may be replaced with various devices as described in FIG. 18. The base station may correspond to a single base station comprising a plurality of TRPs or a single cell comprising a plurality of TRPs. FIG. 17 is for convenience of explanation and does not limit the scope of the present disclosure. Furthermore, some of the steps described in FIG. 17 may be merged or omitted. Additionally, in performing the procedures described below, the aforementioned downlink transmission / reception operation, uplink transmission / reception operation, or beam management operation may be applied, but the scope of the present disclosure is not limited thereto and may be applied to various downlink reception or uplink transmission operations.

[0397] A base station may refer collectively to an object that performs data transmission and reception with a terminal. For example, the base station may be a concept that includes one or more Transmission Points (TPs), one or more Transmission and Reception Points (TRPs), etc. Additionally, TPs and / or TRPs may include the base station's panel, transmission and reception unit, etc. Furthermore, "TRP" may be replaced and applied with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), TP (transmission point), base station (gNB, etc.). As described above, TRPs may be distinguished according to information (e.g., index, ID) regarding a CORESET group (or CORESET pool). For example, if a single terminal is configured to perform transmission and reception with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for a single terminal. Configuration for such a CORESET group (or CORESET pool) can be performed through upper-level signaling (e.g., RRC signaling, etc.).

[0398] The UE can receive configuration information from the base station (S105). The configuration may include system information (SI), scheduling information, beam management (BM) related settings (e.g., DL BM related CSI-ResourceConfig IE, NZP CSI-RS resource set IE, etc.), and base station configuration information (e.g., TRP configuration). Additionally, the configuration may include one or more of CC / BWP related settings, CORESET related settings, and default beam related settings (e.g., default TCI state, default spatial relation, etc.). For example, the configuration may include information related to the resetting / updating of RS information for spatial (e.g., QCL related) assumptions (e.g., information related to whether the resetting / updating is performed, the method of execution, the timing, etc.). Additionally, the configuration may include beam linkage state (BLS) related setting information. The configuration may be transmitted via upper layer (e.g., RRC or MAC CE) signaling. Additionally, if the above configuration is predefined or set, the corresponding step may be omitted.

[0399] For example, based on the embodiments described above, the Configuration may include information regarding one or more of TCI state(s), QCL RS(s), or DMRS port(s). For example, the TCI state may include RS information for assuming a spatial relation (e.g., QCL relation). For example, the Configuration may include spatial relation information / QCL relation configuration information for a DL channel (e.g., PDCCH / PDSCH) and / or a UL channel (e.g., PUSCH / PUCCH). For example, as described in the embodiments described above, the Configuration may include a linkage relationship setting (e.g., BLS information) between a reference RS / CH and a target RS / CH. For example, the above Configuration may include information instructing changes / updates to QCL-related information of downlink channels (e.g., PDCCH / PDSCH) (e.g., RS information for spatial relation assumptions, etc.) and / or linkage relationship settings (e.g., BLS). For example, the above Configuration may include beam linkage status (BLS) information (e.g., relationship / range / setting between reference spatial parameters and target spatial parameters, etc.), information enabling simultaneous spatial parameter update operations for multiple CC / BWPs (e.g., enabler), etc.

[0400] For example, the operation of the UE (100 / 200 of FIG. 18) of step S105 described above receiving the Configuration from the base station (200 / 100 of FIG. 18) can be implemented by the device of FIG. 18 to be described below. For example, referring to FIG. 18, one or more processors (102) can control one or more transceivers (106) and / or one or more memories (104), etc. to receive the Configuration, and one or more transceivers (106) can receive the Configuration from the base station.

[0401] The UE can receive control information from the base station (S110). The control information may be received via a control channel (e.g., PDCCH). For example, the control information may be DCI / UCI. For example, the control information may include scheduling information for a downlink data channel (e.g., PDSCH) and / or an uplink channel (e.g., PUCCH / PUSCH). For example, based on the embodiments described above, the control information may include information regarding one or more of TCI state(s), QCL RS(s), or DMRS port(s). For example, one or more TCI states may be indicated for DMRS port(s) associated with a DL data channel (e.g., PDSCH) / UL channel (e.g., PUCCH / PUSCH) by the TCI state field within the control information (e.g., DCI). For example, the TCI state may include RS information for spatial (e.g., QCL-related) assumptions.

[0402] For example, the operation of the UE (100 / 200 of FIG. 18) of step S110 described above receiving the control information from the base station (200 / 100 of FIG. 18) can be implemented by the device of FIG. 18 to be described below. For example, referring to FIG. 18, one or more processors (102) can control one or more transceivers (106) and / or one or more memories (104), etc. to receive the control information, and one or more transceivers (106) can receive the control information from the base station.

[0403] The UE can receive data from a base station or transmit data to a base station (S115). The data may be received via a downlink channel (e.g., PDCCH / PDSCH) or transmitted via an uplink channel (e.g., PUCCH / PUSCH / PRACH). Additionally, the data may be a downlink signal (e.g., SSB / CSI-RS) or an uplink signal (e.g., SRS). For example, the data may be scheduled based on the control information. Additionally, the data may be received based on the information set / instructed in steps S105 / S110. For example, based on the information set / instructed in steps S105 / S110, the UE may perform channel estimation / compensation and receive the data. For example, based on the embodiments described above, a spatial relation-related RS (e.g., QCL type D RS) for receiving the data may be set. For example, a spatial relation RS (e.g., QCL type D RS) for receiving said data (of a downlink channel) may be set / changed based on spatial relation information of an uplink channel (e.g., PUCCH / PUSCH) transmitted by the UE. For example, a spatial relation RS (e.g., QCL type D RS) for receiving said data (of a downlink channel) may be set based on the use / content of said uplink channel (e.g., SR, HARQ-ACK / NACK, CSI, etc.).

[0404] For example, the spatial relation RS (e.g., QCL type D RS) for receiving the above data (of the downlink channel) can be configured, updated, or changed per CORESET / search space (SS). For example, based on whether the TCI field is included or present in the DCI, it may be determined whether to apply the QCL RS indicated by the TCI or to follow the spatial relation information of the uplink channel. For example, based on the above configuration / control information, reference spatial parameter information (e.g., reference TCI state ID) serving as the basis for change / update is configured or indicated, and transmission and reception can be performed by applying target spatial parameter information corresponding to the reference spatial parameter to the target RS / CH / Data associated with the reference transmission and reception, which is configured via BLS.

[0405] For example, the operation of the UE (100 / 200 of FIG. 18) of step S115 described above receiving the Data from the base station (200 / 100 of FIG. 18) can be implemented by the device of FIG. 18 to be described below. For example, referring to FIG. 18, one or more processors (102) can control one or more transceivers (106) and / or one or more memories (104), etc. to receive the Data, and one or more transceivers (106) can receive the Data from the base station.

[0406] Although not shown in FIG. 17, the UE may report to the base station whether it has changed / updated the QCL reference RS of the DL channel (e.g., PDCCH / PDSCH) based on the transmit beam ( / QCL relation RS) of the UL channel.

[0407] It goes without saying that the examples of the present disclosure (e.g., Example 1, Example 2, Example 3, etc.) in the example of FIG. 17 can also be applied to uplink transmission operations. For example, uplink data transmission can be performed through an uplink channel (e.g., PUCCH / PUSCH). For example, uplink data may include SRS / CSI reports / HARQ-ACK / SR, etc. For example, based on the configuration / control information, a reference spatial parameter (e.g., reference TCI state ID) that serves as a criterion for change / update is set and instructed to be configured, and uplink data can be transmitted by applying target spatial parameter information corresponding to the reference spatial parameter to the target RS / CH / Data linked to the reference transmission / reception, which is set by BLS, i.e., reference transmission / reception. For example, regarding BLS information pre-configured through upper layer signaling, the spatial TX / RX parameter to be applied to uplink transmission can be changed / updated based on update information instructed / configured via MAC-CE / DCI, etc. For example, the update information directed / configured through the above MAC-CE / DCI, etc., may be spatial relation update information for AP / SP SRS.

[0408] As previously mentioned, the above-described base station / UE signaling and operation (e.g., Example 1, Example 2, Example 3, FIG. 15, FIG. 16, FIG. 17, etc.) can be implemented by a device to be described below (e.g., FIG. 18). For example, the base station may correspond to the first wireless device and the UE may correspond to the second wireless device, and in some cases, the opposite case may also be considered.

[0409] For example, the base station / UE signaling and operation described above (e.g., Example 1, Example 2, Example 3, FIG. 15, FIG. 16, FIG. 17, etc.) may be processed by one or more processors of FIG. 18 (e.g., 102, 202), and the base station / UE signaling and operation described above (e.g., Example 1, Example 2, Example 3, FIG. 15, FIG. 16, FIG. 17, etc.) may be stored in memory (e.g., one or more memories of FIG. 18 (e.g., 104, 204)) in the form of an instruction / program (e.g., instruction, executable code) for driving at least one processor of FIG. 18 (e.g., 102, 202).

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

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

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

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

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

[0415] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation included in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation included in the present disclosure. One or more processors (102, 202) may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., a baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation included in the present disclosure.

[0416] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). Descriptions, functions, procedures, proposals, methods, and / or flowcharts of operations included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences included in the present disclosure may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences included in the present disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

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

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

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

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

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

[0422] Here, the wireless communication technology implemented in the wireless device (100, 200) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device (100, 200) of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat S1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (100, 200) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names. Industrial applicability

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

Claims

Claim 1 A method comprising: receiving from a base station by a terminal setting information regarding a list of transmission configuration indicator states (TCI states) for a reference signal that is applied together to one or more target transmissions and receptions for a first bandwidth portion (BWP) of a first cell; receiving from the base station by the terminal instruction information regarding one or more TCI states among the list of TCI states; and applying by the terminal the one or more TCI states indicated for the first BWP of the first cell to the second BWP of the second cell based on the absence of a TCI state-related setting in the second BWP of the second cell. Claim 2 A method according to claim 1, wherein the instruction information includes information regarding a TCI state that is simultaneously updated for the first BWP of the first cell and the second BWP of the second cell. Claim 3 delete Claim 4 delete Claim 5 delete Claim 6 delete Claim 7 A method according to claim 1, wherein a specific TCI state among the one or more TCI states is determined. Claim 8 In claim 7, the method wherein the specific one TCI state corresponds to a TCI state corresponding to the lowest or highest identifier, or a TCI state indicated by downlink control information (DCI) related to uplink transmission or downlink reception. Claim 9 delete Claim 10 delete Claim 11 A method according to claim 1, wherein the uplink transmission or downlink reception at the second BWP of the second cell comprises a predetermined uplink reference signal (RS) or downlink RS, a predetermined uplink physical channel or downlink physical channel, and a predetermined uplink signal or downlink signal. Claim 12 delete Claim 13 A method according to claim 1, wherein information related to uplink transmission or downlink reception on the second BWP of the second cell being performed based on the TCI status for the first BWP of the first cell is provided from the base station. Claim 14 delete Claim 15 delete Claim 16 A terminal comprising: one or more transceivers; and one or more processors connected to the one or more transceivers, wherein the one or more processors: receive from a base station via the one or more transceivers configuration information regarding a list of transmission configuration indicator states (TCI states) for a reference signal that is applied together to one or more target transmissions and receptions for a first bandwidth portion (BWP) of a first cell; receive from the base station via the one or more transceivers instruction information regarding one or more TCI states among the list of TCI states; and, based on the absence of a TCI state-related configuration in a second BWP of a second cell, the one or more TCI states indicated for the first BWP of the first cell are configured to apply to the second BWP of the second cell the TCI state indicated for the first BWP of the first cell. Claim 17 A method comprising: a step of transmitting to a terminal by a base station configuration information regarding a list of transmission configuration indicator states (TCI states) for a reference signal that is applied together to one or more target transmissions and receptions for a first bandwidth portion (BWP) of a first cell; a step of transmitting to the terminal by the base station instruction information regarding one or more TCI states among the list of TCI states; and a step of performing uplink reception or downlink transmission by the base station, wherein the one or more TCI states indicated for the first BWP of the first cell are applied by the terminal to the second BWP of the second cell based on the absence of a TCI state-related configuration in the second BWP of the second cell. Claim 18 A base station comprising: one or more transceivers; and one or more processors connected to the one or more transceivers, wherein the one or more processors: transmit to a terminal via the one or more transceivers configuration information regarding a list of transmission configuration indicator states for a reference signal that is applied together to one or more target transmissions and receptions for a first bandwidth portion (BWP) of a first cell; transmit to the terminal via the one or more transceivers instruction information regarding one or more TCI states among the list of TCI states; and, based on the absence of a TCI state-related configuration in a second BWP of a second cell, the one or more TCI states indicated for the first BWP of the first cell for the second BWP of the second cell are configured to perform uplink reception or downlink transmission applied by the terminal via the one or more transceivers. Claim 19 A processing device comprising: one or more processors; and one or more computer memories operably connected to the one or more processors and storing instructions for performing operations based on execution by the one or more processors, wherein the operations include: receiving configuration information for a list of transmission configuration indicator states (TCI states) for a reference signal that is applied together to one or more target transmissions and receptions for a first bandwidth portion (BWP) of a first cell; receiving instruction information for one or more TCI states among the list of TCI states; and applying the one or more TCI states indicated for the first BWP of the first cell to the second BWP of the second cell based on the absence of a TCI state-related configuration in the second BWP of the second cell. Claim 20 One or more non-transitory computer-readable media storing one or more instructions, wherein the one or more instructions are executed by one or more processors, and the device receives setting information for a list of transmission configuration indicator (TCI) states for a reference signal that is applied together for one or more target transmissions and receptions for a first bandwidth portion (BWP) of a first cell; receives instruction information for one or more TCI states among the list of TCI states; and controls the application of the one or more TCI states indicated for the first BWP of the first cell to the second BWP of the second cell based on the absence of a TCI state-related setting in the second BWP of the second cell.

Citation Information

Patent Citations

  • Method for transmitting and receiving an uplink channel in a wireless communication system and device therefor

    KR1020200003196A