Method and apparatus for transmitting and receiving uplink / downlink signals based on beam alignment status in a wireless communication system

Abstract

A method and apparatus for performing uplink / downlink transmission and reception based on a beam alignment state in a wireless communication system are provided. [Solution] 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 includes a BLS reception step of receiving information regarding a beam link status (BLS) from a base station, the BLS including information regarding a mapping relationship between a reference transmission / reception and one or more target transmission / reception; a BLS reception step of receiving information regarding a first spatial parameter for the reference transmission / reception associated with a specific BLS from the base station; and a step of performing the uplink transmission or the downlink reception for a specific target transmission / reception among the one or more target transmissions / receptions mapped to the reference transmission / reception associated with the specific BLS based on a second spatial parameter corresponding to the first spatial parameter.

Description

[Technical Field]

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

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

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

[0004] The technical problem of the present disclosure is to provide a method and apparatus for performing uplink / downlink transmission and reception based on beam alignment status.

[0005] A further technical problem of the present disclosure is to provide a method and apparatus for setting beam linkage state candidates and activating or indicating beam linkage states.

[0006] A further technical problem of the present disclosure is to provide a method and apparatus for determining spatial parameters to be applied to a target transmission / reception that is related to a reference transmission / reception by a beam alignment state.

[0007] A further technical problem of the present disclosure is to provide a method and apparatus for determining when to apply spatial parameters to a target transmission / reception that is related to a reference transmission / reception by a beam alignment state.

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

[0009] 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 includes a BLS reception step of receiving information regarding a beam link status (BLS) from a base station, the BLS including information regarding a mapping relationship between a reference transmission / reception and one or more target transmission / receptions; a BLS reception step of receiving information regarding a first spatial parameter for the reference transmission / reception associated with a specific BLS from the base station; and a step of performing the uplink transmission or the downlink reception for a specific target transmission / reception among the one or more target transmissions / receptions mapped to the reference transmission / reception associated with the specific BLS based on a second spatial parameter corresponding to the first spatial parameter.

[0010] A method for performing downlink transmission or uplink reception by a base station in a wireless communication system according to a further aspect of the present disclosure may include a BLS transmission step of transmitting information regarding a beam link status (BLS) to a terminal, the BLS including information regarding a mapping relationship between a reference transmission / reception and one or more target transmission / reception; a BLS transmission step of transmitting information regarding a first spatial parameter for the reference transmission / reception associated with a specific BLS to the terminal; and a step of performing the downlink transmission or the uplink reception for a specific target transmission / reception among the one or more target transmissions / receptions mapped to the reference transmission / reception associated with the specific BLS based on a second spatial parameter corresponding to the first spatial parameter. [Effects of the Invention]

[0011] According to the present disclosure, a method and apparatus can be provided for performing uplink / downlink transmission and reception based on beam alignment status.

[0012] According to the present disclosure, methods and apparatus can be provided for setting beam linkage state candidates and activating or indicating beam linkage states.

[0013] According to the present disclosure, a method and apparatus can be provided for determining spatial parameters to be applied to a target transmission / reception relative to a reference transmission / reception depending on the beam alignment state.

[0014] According to the present disclosure, a method and apparatus can be provided in which the beam alignment state determines when to apply spatial parameters to a target transmission / reception relative to a reference transmission / reception.

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

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

[0017] [Figure 1] 1 illustrates the structure of a wireless communication system to which the present disclosure is applicable.

[0018] [Figure 2] 1 illustrates a frame structure in a wireless communication system to which the present disclosure is applicable.

[0019] [Figure 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure is applicable.

[0020] [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure is applicable.

[0021] [Figure 5] 1 illustrates an example slot structure in a wireless communication system to which the present disclosure is applicable.

[0022] [Figure 6] 1 illustrates examples of physical channels used in a wireless communication system to which the present disclosure is applicable, and a general signal transmission / reception method using the physical channels.

[0023] [Figure 7] A diagram illustrating downlink beam management operations in a wireless communication system to which the present disclosure can be applied.

[0024] [Figure 8] A diagram illustrating a downlink beam management procedure using SSB in a wireless communication system to which the present disclosure can be applied.

[0025] [Figure 9]A diagram illustrating downlink beam management operations using CSI-RS in a wireless communication system to which the present disclosure can be applied.

[0026] [Figure 10] A diagram illustrating the receiving beam determination process of a terminal in a wireless communication system to which the present disclosure can be applied.

[0027] [Figure 11] A diagram illustrating the transmission beam determination process of a base station in a wireless communication system to which the present disclosure can be applied.

[0028] [Figure 12] A diagram illustrating resource allocation in the time and frequency domains associated with downlink beam management operations in a wireless communication system to which the present disclosure is applicable.

[0029] [Figure 13] A diagram illustrating an uplink beam management operation using SRS in a wireless communication system to which the present disclosure can be applied.

[0030] [Figure 14] A diagram illustrating an uplink beam management procedure in a wireless communication system to which the present disclosure can be applied.

[0031] [Figure 15] A flowchart for explaining a method in which a terminal performs uplink transmission or downlink reception based on a beam association status according to the present disclosure.

[0032] [Figure 16] FIG. 10 is a diagram illustrating a signaling process according to one embodiment of the present disclosure.

[0033] [Figure 17] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0034] Preferred embodiments of the present disclosure will be described in detail below 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 embodiments in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it will be understood by those skilled in the art that the present disclosure can be implemented without such specific details.

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

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

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

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

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

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

[0041] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In the downlink, a transmitter may be part of the base station, and a receiver may be part of the terminal. In the uplink, a transmitter may be part of the terminal, and a receiver may be part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, evolved-Node B (eNB), Next Generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), artificial intelligence (AI) system / module, road side unit (RSU), robot, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc. Furthermore, a 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, etc.

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

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

[0044] In 3GPP LTE, reference can be made to TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

[0045] For 3GPP NR, reference can be made to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Standard).

[0046] The terminology abbreviations that may be used in this disclosure are defined as follows:

[0047] - BM: Beam management

[0048] - CQI: Channel Quality Indicator

[0049] - CRI: Channel state information-reference signal resource indicator

[0050] - CSI: Channel State Information

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

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

[0053] - DMRS: Demodulation Reference Signal

[0054] - FDM: Frequency Division Multiplexing

[0055] - FFT: Fast Fourier transform

[0056] - IFDMA: Interleaved frequency division multiple access

[0057] - IFFT: Inverse fast Fourier transform

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

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

[0060] - MAC: Medium Access Control

[0061] - NZP: Non-zero power

[0062] - OFDM: Orthogonal frequency division multiplexing

[0063] - PDCCH: Physical downlink control channel

[0064] - PDSCH: Physical downlink shared channel

[0065] - PMI: Precoding matrix indicator

[0066] - RE: resource element

[0067] - RI: Rank indicator

[0068] - RRC: Radio resource control

[0069] - RSSI: received signal strength indicator

[0070] - Rx: Reception

[0071] - QCL: quasi co-location

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

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

[0074] - TDM: time division multiplexing

[0075] - TRP: transmission and reception point

[0076] - TRS: Tracking reference signal

[0077] - Tx: transmission

[0078] - UE: User equipment

[0079] - ZP: Zero power

[0080] System in general

[0081] As more communication devices require greater communication capacity, there is a growing need for improved mobile broadband communication compared to existing radio access technologies (RATs). Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide a variety of services anytime, anywhere, is also one of the key issues being considered for next-generation communications. In addition, communication system designs that take into account reliability- and latency-sensitive services / terminals are also being discussed. Thus, the introduction of next-generation RATs that take into account technologies such as enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, these technologies will be referred to as NR in this disclosure. NR is an example of a 5G RAT.

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

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

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

[0085] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide the 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 termination for the UE. The gNBs are interconnected via an Xn interface. The gNBs are also connected to an NGC (New Generation Core) via an NG interface. More specifically, the gNBs are connected to an AMF (Access and Mobility Management Function) via an N2 interface and to a UPF (User Plane Function) via an N3 interface.

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

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

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

[0089] [Table 1]

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

[0091] [Table 2]

[0092] In relation to the frame structure in an NR system, the size of the various fields in the time domain is T c =1 / (Δf max N f ) where Δ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 The radio frame is organized into radio frames each having a duration of T = 10 ms. sf =(Δf max N f / 1000)·T c In this case, there may be one set of frames for the uplink and one set of frames for the downlink. In addition, transmission from a terminal in uplink frame number i begins T TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols, symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or an uplink slot can be used. Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), the number of slots per subframe (N slot subframe,μ ) and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0093] [Table 3]

[0094] [Table 4]

[0095] FIG. 2 shows an example where μ=2 (SCS is 60 kHz), and referring to Table 3, one subframe can include four slots. The {1, 2, 4} slots shown in FIG. 2 are an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. A mini-slot can include 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, and the like may be considered. Hereinafter, the physical resources that can be considered in an NR system will be described in detail.

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

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

[0098] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB It consists of subcarriers, and one subframe is 14.2 μ In the NR system, a transmitted signal is composed of N OFDM symbols. RB μ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RB μ ≦N RB max,μ The above N RB max,μrepresents the maximum transmission bandwidth, which may vary not only depending on the numerology but also between the uplink and downlink. In this case, one resource grid may be configured for μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element and is represented by an index pair (k, JPEG0007748381000005.jpg53), where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG0007748381000006.jpg53=0,...,2 μ N symb (μ) -1 represents the position of the symbol within the subframe. When referring to resource elements in a slot, the index pair (k, l) is used, where l = 0,...,N symb μ μ and the resource element (k, JPEG0007748381000007.jpg54) is a complex value JPEG0007748381000008.jpg811. 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, so that the complex value is JPEG0007748381000009.jpg912 or JPEG0007748381000010.jpg912. Also, a resource block (RB) is a set of N sc RB = 12 consecutive subcarriers.

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

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

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

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

[0103]

number

[0104] In Equation 1, k is defined relative to point A so that k=0 corresponds to the subcarrier centered at point A. The physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ Physical resource block n in BWP i is numbered from -1 to i. PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0105]

number

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

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

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

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

[0110] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC keeps the radio frequency (RF) chip for the entire CC on at all times, battery consumption may increase. Considering various application cases (e.g., eMBB, URLLC, MMTc, V2X, etc.) operating within a single wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Each terminal may have different capabilities for maximum bandwidth. In consideration of this, a base station may instruct a terminal to operate only with a portion of the bandwidth of a wideband CC, rather than the entire bandwidth. For convenience, this portion of the bandwidth is defined as a bandwidth part (BWP). A BWP may consist of contiguous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot duration).

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

[0112] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure is applicable, and a general signal transmission / reception method using the physical channels.

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

[0114] When a terminal is powered on or newly enters a cell, it performs an initial cell search, such as synchronizing with a base station (S601). To do this, 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 acquire information such as a cell identifier (ID). The terminal then receives a physical broadcast channel (PBCH) from the base station to acquire broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0115] After completing the initial cell search, the terminal receives a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) based on the information carried on the PDCCH, thereby obtaining more specific system information (S602).

[0116] Meanwhile, when the terminal first connects to the base station or when there are no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) with the base station (steps S603 to S606). To this end, the terminal transmits a specific sequence as a preamble on a physical random access channel (PRACH) (steps S603 and S605) and can receive a response message to the preamble on a PDCCH and a corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure can also be performed.

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

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

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

[0120] [Table 5]

[0121] 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., Modulation Coding and Scheme (MCS), New Data Indicator (NDI), Redundancy Version (RV), etc.), hybrid-automatic repeat and request (HARQ)-related information (e.g., process number, downlink assignment index (DAI), PDSCH-HARQ feedback timing, etc.), multiple antenna-related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for PUSCH scheduling in one cell. The information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled using C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and then transmitted.

[0122] DCI format 0_1 ​​is used to indicate scheduling of one or more PUSCHs in one cell or downlink feedback information of configured grants (CGs) to a terminal. The information included in DCI format 0_1 ​​is CRC-scrambled using C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI and then transmitted.

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

[0124] 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.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be pre-defined.

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

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

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

[0128] Beam management (BM)

[0129] The BM procedure is an L1 (layer 1) / L2 (layer 2) procedure for acquiring and maintaining a set of base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams available for downlink (DL) and uplink (UL) transmission / reception, and may include the following procedures and terms:

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

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

[0132] Beam sweeping: The operation of covering a spatial region using transmit and / or receive beams in a predetermined manner for a certain time period.

[0133] - Beam report: An operation in which a UE reports information about beamformed signals based on beam measurements.

[0134] BM procedures can be divided into (1) DL BM procedures using SS (synchronization signal) / PBCH (physical broadcast channel) blocks or CSI-RS, and (2) UL BM procedures using SRS (sounding reference signal).

[0135] Each BM procedure may also include transmit beam sweeping (Tx beam sweeping) to determine a transmit beam (Tx beam) and receive beam sweeping (Rx beam sweeping) to determine a receive beam (Rx beam).

[0136] The DL BM procedure is described below.

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

[0138] Here, the beam report may include a preferred DL RS ID (identifier) ​​and its corresponding L1-RSRP (Reference Signal Received Power).

[0139] The DL RS ID may be an SSB Resource Indicator (SSBRI) or a CSI-RS Resource Indicator (CRI).

[0140] The DL BM procedure using SSB is described below.

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

[0142] Referring to Figure 7, SSB beams and CSI-RS beams may be used for beam measurement. The measurement metric is L1-RSRP per resource / block. SSB may be used for coarse beam measurement, and CSI-RS may be used for fine beam measurement. SSB may be used for both transmit beam sweeping and receive beam sweeping.

[0143] Receive beam sweeping using SSBs may be performed by the UE changing the receive beam for the same SSBRI across multiple SSB bursts, where one SS burst includes one or more SSBs and one SS burst set includes one or more SSB bursts.

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

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

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

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

[0148] [Table 6]

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

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

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

[0152] Regarding CSI-RS usage, i) when 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) when the repetition parameter is not set and TRS_info is set, CSI-RS is used for tracking reference signal (TRS), and iii) when the repetition parameter is not set and TRS_info is not set, CSI-RS is used for CSI acquisition.

[0153] Such a repetition parameter may be set only for CSI-RS resource sets associated with a CSI-ReportConfig having a report of L1 RSRP or 'No Report (or None)'.

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

[0155] This is related to the receive beam sweeping procedure of the UE when the (higher layer parameter) repetition is set to 'ON'. In this case, when an NZP-CSI-RS-ResourceSet is configured in the UE, the UE can assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same downlink spatial domain transmission filter. That is, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same transmission beam. Here, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet may be transmitted in a different OFDM symbol. In addition, the UE does not expect all CSI-RS resources in the NZP-CSI-RS-ResourceSet to receive different periodicities from each other in periodicityAndOffset.

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

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

[0158] Furthermore, if a CSI-RS resource is configured in the same OFDM symbol as an SSB (SS / PBCH Block) and 'QCL-Type D' is applicable, the terminal can assume that the CSI-RS and SSB are quasi-colocated from the perspective of 'QCL-Type D'.

[0159] Here, the QCL Type D may mean that a QCL is established between antenna ports in terms of spatial Rx parameters. When a terminal receives from multiple DL antenna ports in a QCL Type D relationship, the same reception beam may be applied. In addition, the terminal does not expect CSI-RS to be configured in REs overlapping with SSB REs.

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

[0161] 9(a) shows a receive beam determination (or refinement) procedure of a terminal, and FIG. 9(b) shows a transmit beam sweeping procedure of a base station. Also, FIG. 9(a) shows the case where the repetition parameter is set to 'ON', and FIG. 9(b) shows the case where the repetition parameter is set to 'OFF'.

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

[0163] The process of determining a receiving beam in a terminal will be described with reference to FIG. 9(a) and FIG.

[0164] The terminal receives an NZP CSI-RS resource set IE including a higher layer parameter repetition from the base station via RRC signaling (S610), where the repetition parameter is set to 'ON'.

[0165] The terminal repeatedly receives resources in the CSI-RS resource set with repetition 'ON' using different OFDM symbols through the same transmission beam (or DL ​​spatial domain transmission filter) of the base station (S620).

[0166] The terminal determines its own receiving beam (S630).

[0167] The UE omits CSI reporting (S640). In this case, the reportQuantity in the CSI reporting configuration may be set to 'No report (or None)'.

[0168] That is, the terminal may omit CSI reporting when repetition is set to 'ON'.

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

[0170] The transmission beam determination process of the base station will be described with reference to FIG. 9(b) and FIG.

[0171] The terminal receives an NZP CSI-RS resource set IE including an upper layer parameter repetition from the base station via RRC signaling (S710), where the repetition parameter is set to 'OFF' and is associated with the transmit beam sweeping procedure of the base station.

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

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

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

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

[0176] FIG. 12 is a diagram illustrating resource allocation in the time and frequency domains associated with downlink beam management operations in a wireless communication system to which the present disclosure is applicable.

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

[0178] Below, a downlink BM-related beam indication method is described.

[0179] A terminal may be RRC configured with a list of up to M candidate Transmission Configuration Indication (TCI) states, where M may be 64, at least for the purpose of Quasi Co-location (QCL) indication.

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

[0181] Initialization / update of IDs of DL RSs in the set of RSs used at least for spatial QCL purposes may be done at least by explicit signaling.

[0182] Table 7 illustrates the TCI-State information element (IE).

[0183] The TCI-State IE associates a quasi co-location (QCL) type corresponding to one or two DL reference signals (RS).

[0184] [Table 7]

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

[0186] The following describes uplink beam management.

[0187] Depending on the terminal implementation, the UL BM may or may not have beam reciprocity (or beam correspondence) between the transmit beam and the receive beam. If transmit beam-receive beam reciprocity is established in both the base station and the terminal, the UL beam pair can be matched through the DL beam pair. However, if transmit beam-receive beam reciprocity is not established in either the base station or the terminal, a UL beam pair determination process is required separately from the DL beam pair determination.

[0188] In addition, even if both the base station and the terminal maintain beam correspondence, the base station can use the UL BM procedure to determine the DL transmission beam even if the terminal does not request a preferred beam report.

[0189] UL BM may be performed by beamformed UL SRS transmission, and the application of UL BM to an SRS resource set is configured by the usage (higher layer parameter). When usage is set to 'BeamManagement (BM)', only one SRS resource may be transmitted in each of multiple SRS resource sets at a given time instant.

[0190] A terminal may be configured (by higher layer signaling, RRC signaling, etc.) with one or more Sounding Reference Symbol (SRS) resource sets configured by (higher layer parameter) SRS-ResourceSet. For each SRS resource set, the UE may be configured with K≧1 SRS resources (higher layer parameter SRS-resource), where K is a natural number and the maximum value of K is indicated by SRS_capability.

[0191] Similar to DL BM, the UL BM procedure may be divided into transmit beam sweeping by the terminal and receive beam sweeping by the base station.

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

[0193] FIG. 13(a) illustrates the receiving beam determination operation of the base station, and FIG. 13(b) illustrates the transmitting beam sweeping operation of the terminal.

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

[0195] The terminal receives RRC signaling (eg, SRS-Config IE) including usage parameters (higher layer parameters) set to 'beam management' from the base station (S1010).

[0196] Table 8 shows an example of an SRS-Config IE (Information Element), which is used for SRS transmission configuration. The 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.

[0197] The network can trigger the transmission of the SRS resource set using a configured aperiodic SRS-ResourceTrigger (L1 DCI).

[0198] [Table 8-1] [Table 8-2]

[0199] In Table 8, "usage" represents a higher layer 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 may be the SSB, CSI-RS, or SRS corresponding to the L1 parameter 'SRS-SpatialRelationInfo'. The "usage" is set for each SRS resource set. The UE determines a transmission beam for the SRS resource to be transmitted based on the SRS-SpatialRelation Info included in the SRS-Config IE (S1020). Here, SRS-SpatialRelation Info is configured for each SRS resource and indicates whether the same beam as that used in SSB, CSI-RS, or SRS is applied for each SRS resource. Also, SRS-SpatialRelationInfo may or may not be configured for each SRS resource.

[0200] If SRS-SpatialRelationInfo is set for the SRS resource, the same beam as that used for SSB, CSI-RS, or SRS is applied for transmission. However, if SRS-SpatialRelationInfo is not set for the SRS resource, the terminal arbitrarily determines a transmission beam and transmits the SRS through the determined transmission beam (S1030).

[0201] More specifically, for a P-SRS with 'SRS-ResourceConfigType' set to 'periodic':

[0202] i) if SRS-SpatialRelationInfo is set to 'SSB / PBCH', the UE transmits the SRS resource using a spatial domain transmission filter that is the same as (or is generated from) the spatial domain Rx filter used to receive SSB / PBCH; or

[0203] ii) if SRS-SpatialRelationInfo is set to 'CSI-RS', the UE transmits the SRS resource using the same spatial domain transmission filter used for receiving periodic CSI-RS or semi-persistent CSI-RS; or

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

[0205] Even when 'SRS-ResourceConfigType' is set to 'SP (semi-persistent)-SRS' or 'AP (aperiodic)-SRS', the beam determination and transmission operations may be applied in a similar manner to the above.

[0206] Furthermore, the terminal may or may not receive feedback for the SRS from the base station in the following three cases (S1040).

[0207] i) When Spatial_Relation_Info is configured for all SRS resources in the SRS resource set, the terminal transmits the SRS using the beam specified by the base station. For example, when Spatial_Relation_Info specifies the same SSB, CRI, or SRI, the terminal repeatedly transmits the SRS using the same beam. In this case, the base station selects the receiving beam, which corresponds to Figure 13(a).

[0208] ii) Spatial_Relation_Info does not need to be configured for all SRS resources in the SRS resource set. In this case, the terminal can freely change the SRS beam while transmitting. In other words, this is an application in which the terminal sweeps the transmission beam, and corresponds to FIG. 13(b).

[0209] iii) Spatial_Relation_Info may be configured for only some SRS resources in the SRS resource set. In this case, the SRS is transmitted using the specified beam for the configured SRS resources, and the terminal can arbitrarily apply a transmission beam to the SRS resources for which Spatial_Relation_Info is not configured.

[0210] quasi-co location (QCL)

[0211] Antenna ports are defined such that the channel carried by symbols on an antenna port can be inferred from the channel carried by other symbols on the same antenna port. Two antenna ports are said to be quasi-colocated (QC / QCL) if the properties of the channel carried by symbols on one antenna port can be inferred from the channel carried by symbols on the other antenna port.

[0212] 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, where the spatial RX parameters refer to spatial (reception) channel characteristic parameters such as the angle of arrival.

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

[0214] Each TCI-State includes parameters for setting a quasi-coordinate relationship between one or two DL reference signals and a demodulation reference signal (DM-RS) port of a PDSCH.

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

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

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

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

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

[0220] -'QCL-TypeD':{Spatial receiving parameters}

[0221] For example, if a target antenna port is a specific NZP CSI-RS, the NZP CSI-RS antenna port may be instructed / configured to be QCL-connected to a specific TRS from the perspective of QCL-Type A, and to a specific SSB from the perspective of QCL-Type D. A terminal that receives such an instruction / configuration can receive the NZP CSI-RS using the Doppler and delay values ​​measured from the QCL-TypeA TRS, and apply the receive beam used for QCL-TypeD SSB reception to the NZP CSI-RS reception.

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

[0223] If the HARQ-ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n, the indicated mapping between the TCI state and the codepoint of the DCI field 'Transmission Configuration Indication' is slot subframe,μThe application may start from +1. After the UE receives an initial higher layer configuration for the TCI state before receiving an activation command, for QCL-Type A, and if applicable, for QCL-Type D, the UE may assume that the DMRS port of the PDSCH of the serving cell is QCLed with the SS / PBCH block determined during the initial access process.

[0224] When a higher layer parameter (e.g., tci-PresentInDCI) indicating whether a TCI field is present in the DCI configured for the UE is set as enabled for the CORESET scheduling the PDSCH, the UE may assume that a TCI field is present in DCI format 1_1 of the PDCCH transmitted on the CORESET. If tci-PresentInDCI is not configured for the CORESET scheduling the PDSCH, or if the PDSCH is scheduled using DCI format 1_0 and the time offset between reception of the DL DCI and the corresponding PDSCH is equal to or greater than a predetermined threshold value (e.g., timeDurationForQCL), 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 PDCCH transmission in order to determine the PDSCH antenna port QCL. Here, the predetermined threshold value may be based on the reported UE capability.

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

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

[0227] If a single-slot PDSCH is configured for the UE, the indicated TCI state may be based on the activated TCI state of the slot in which the scheduled PDSCH resides.

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

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

[0230] For both cases where the parameter tci-PresentInDCI is set to enabled and where tci-PresentInDCI is not set in RRC connected mode, if the time offset between the reception of DL DCI and its corresponding PDSCH is less than a predetermined critical value (e.g., timeDurationForQCL), the UE can assume that the DMRS port of the PDSCH of the serving cell is QCL'd with the RS for the QCL parameter used for the PDCCH QCL indication of the CORESET associated with the monitored search space with the lowest CORESET-ID in the latest slot in which one or more CORESETs in the active BWP of the serving cell are monitored by the UE.

[0231] In this case, if the QCL Type D of the PDSCH DMRS differs from the QCL Type D of the PDCCH DMRS and they overlap by at least one symbol, the UE can expect to prioritize reception of the PDCCH associated with that CORESET. This may also apply to intra-band carrier aggregation (CA) (when the PDSCH and CORESET are on different CCs). If none of the configured TCI states includes QCL Type D, the UE can obtain other QCL assumptions from the TCI states indicated for the scheduled PDSCH, regardless of the time offset between reception of the DL DCI and its corresponding PDSCH.

[0232] For periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE can expect the TCI state to indicate one of the following QCL types:

[0233] - QCL-Type C with SS / PBCH blocks and, if applicable, QCL-Type D with the same SS / PBCH blocks, or

[0234] - QCL-Type C with the SS / PBCH block and, if applicable, QCL-Type D with the CSI-RS resources in the configured NZP-CSI-RS-ResourceSet including the higher layer parameter repetition.

[0235] For aperiodic CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE can expect the TCI state to indicate QCL-TypeA with periodic CSI-RS resources in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info, and, if applicable, QCL-TypeD with the same periodic CSI-RS resources.

[0236] For CSI-RS resources in an NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, the UE can expect the TCI state to indicate one of the following QCL types:

[0237] - QCL-Type A with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-Type D with the same CSI-RS resources, or

[0238] - QCL-Type A with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-Type D with the SS / PBCH blocks, or

[0239] - QCL-TypeA with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-TypeD with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

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

[0241] For CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, the UE can expect the TCI state to indicate one of the following QCL types:

[0242] - QCL-Type A with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-Type D with the same CSI-RS resources, or

[0243] - QCL-TypeA with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-TypeD with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0244] - QCL-Type C with SS / PBCH blocks and, if applicable, QCL-Type D with the same SS / PBCH blocks.

[0245] For DMRS on PDCCH, the UE can expect the TCI state to indicate one of the following QCL types:

[0246] - QCL-Type A with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-Type D with the same CSI-RS resources, or

[0247] - QCL-TypeA with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-TypeD with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0248] - QCL-Type A with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, and, if applicable, QCL-Type D with the same CSI-RS resources.

[0249] For DMRS on PDSCH, the UE can expect the TCI state to indicate one of the following QCL types:

[0250] - QCL-Type A with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-Type D with the same CSI-RS resources, or

[0251] - QCL-TypeA with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, if applicable, QCL-TypeD with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0252] - QCL-Type A with the CSI-RS resources of the NZP-CSI-RS-ResourceSet configured without the higher layer parameter trs-Info and without the higher layer parameter repetition, and, if applicable, QCL-Type D with the same CSI-RS resources.

[0253] Beam alignment status-based uplink / downlink transmission and reception

[0254] The following describes various examples of the present disclosure for uplink / downlink (UL / DL) transmission and reception based on beam linkage state (BLS).

[0255] Spatial parameters related to downlink transmission and reception (or beam transmission and reception related parameters) may be applied to a physical channel through which downlink control information or data is transmitted or received, or may include QCL information assumed by a terminal. The QCL information may include QCL reference signal (RS) information, and the 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 or received on a PDCCH, and spatial parameters related to DCI transmission and reception may include QCL reference information for a PDCCH DMRS antenna port, TCI status information, etc. Furthermore, downlink data may be transmitted or received on a PDSCH, and spatial parameters related to downlink data transmission and reception may include QCL reference information for a PDSCH DMRS antenna port, TCI status information, etc.

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

[0257] Furthermore, the spatial parameters may be set separately for the downlink or the uplink, or may be set jointly for the downlink and the uplink.

[0258] Furthermore, the spatial parameters may be defined or set as a spatial parameter set including one or more spatial parameters. Hereinafter, for simplicity of explanation, one or more spatial parameters will be collectively referred to as a spatial parameter.

[0259] In order for the base station to set / indicate the PDCCH reception spatial parameters (or reception beam) of the terminal, it can set / update a TCI state ID for each of one or more CORESETs. The TCI state set for a CORESET can indicate QCL reference information (e.g., QCL type D related information) for the PDCCH DMRS antenna port transmitted in 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 PDCCH reception beam of the terminal.

[0260] In the case of setting / indicating spatial parameters (or receive beams) for PDSCH reception, a TCI field may be included in the PDCCH DCI that schedules the PDSCH. The TCI state ID (or TCI codepoint) indicated by the TCI field in the DCI may indicate QCL reference information (e.g., QCL type D-related information) for the PDSCH DMRS antenna port.

[0261] Although the spatial parameters for PDSCH reception may be dynamically configured / indicated by DCI, the spatial parameters indicated by DCI are limited to spatial parameter candidates preset by higher layer signaling (e.g., RRC / MAC CE), and therefore higher layer signaling is required to change / update the spatial parameters for PDSCH reception. Since the spatial parameters for PDCCH reception are based on the CORESET configuration, RRC reconfiguration for CORESET configuration / update or MAC CE message transmission, etc., is required to configure / indicate the spatial parameters for PDCCH reception. Furthermore, when spatial parameter information (e.g., TCI field) is not included in the DCI scheduling the PDSCH, the spatial parameters for PDSCH reception can be applied based on the spatial parameters configured for the CORESET in which the DCI is monitored. Furthermore, even if spatial parameter information (e.g., a TCI field) is included in 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 equal to or less than a predetermined threshold, the 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 last slot monitored by the UE). As described above, if the PDCCH / PDSCH spatial parameters / reception beam are changed / updated using higher layer signaling (e.g., RRC / MAC CE), not only does flexibility decrease, but unnecessary signaling overhead occurs due to the change / update.

[0262] To solve this problem, the following example describes UL / DL transmission and reception based on beam link status (BLS) while minimizing signaling overhead.

[0263] In the following description, spatial parameters or spatial relation information (spatial relation info) may mean RS information / QCL-related (or reference) RS information / QCL parameters, etc. for spatial relation hypotheses for data / signals transmitted / received on UL channels / DL channels, or may be expressed in terms / alternatives to these terms.

[0264] In the following examples, using / applying / mapping a specific spatial parameter (or TCI state or TCI) when transmitting / receiving data / DCI / UCI for a certain frequency / time / space resource can mean, in DL, estimating a channel from a DMRS using the QCL type and QCL RS indicated by the spatial parameter in that frequency / time / space resource and receiving / demodulating data / DCI (e.g., PDSCH / PDCCH) using the estimated channel, and in UL, transmitting / modulating a DMRS and data / UCI (e.g., PUSCH / PUCCH) using the transmit beam and / or transmit power indicated by the spatial parameter in that frequency / time / space resource.

[0265] FIG. 15 is a flowchart illustrating a method in which a terminal performs uplink transmission or downlink reception based on a beam association status according to the present disclosure.

[0266] In step S1510, the terminal may receive information regarding beam link status (BLS) from the base station.

[0267] For example, the terminal may receive configuration information regarding one or more candidates for BLS from the base station, which may be configured for the terminal by higher layer (e.g., RRC) signaling.

[0268] The BLS may include information regarding a mapping relationship between one or more reference transceivers and one or more target transceivers. For example, each BLS candidate may define a mapping relationship between one reference transceiver and one or more target transceivers. The BLS may define a relationship in which a first spatial parameter for the reference transceiver and a second spatial parameter for the target transceiver are linked (e.g., a change in the first spatial parameter causes a change in the second spatial parameter).

[0269] Here, the second spatial parameter may be the same as the first spatial parameter or a spatial parameter corresponding to the first spatial parameter. For example, the reception spatial parameter (or reception beam) of the terminal and the transmission spatial parameter (or transmission beam) of the terminal may have a correspondence relationship according to the implementation of the transmission / reception filter of the terminal. Alternatively, the first reception spatial parameter (or reception beam) of the terminal may have a correspondence relationship with the second reception spatial parameter (or reception beam), and the first transmission spatial parameter (or transmission beam) of the terminal may have a correspondence relationship with the second transmission spatial parameter (or transmission beam).

[0270] For example, the correspondence between the first and second spatial parameters may be predefined / determined according to a predetermined rule, predefined through signaling exchange between a base station and a terminal, or predefined according to the implementation of the terminal. Therefore, a specific correspondence between the spatial parameters is not defined in the present disclosure, and various arbitrary correspondences may be applied. That is, in the examples of the present disclosure, it is assumed that the correspondence between the first and second spatial parameters is known in advance to the terminal and / or the base station.

[0271] The terminal may also receive information from the base station regarding a specific BLS that is activated or valid among one or more candidate BLSs.

[0272] For example, information regarding a specific BLS may be indicated to a terminal by higher layer (e.g., MAC CE) or lower layer (e.g., DCI) signaling.

[0273] This allows the terminal to determine a target transmission / reception that is mapped to the reference transmission / reception based on a specific BLS. For example, the reference transmission / reception may be a first UL / DL reference signal (RS) / channel (CH), and the target transmission / reception 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.

[0274] In step S1520, the UE may receive information about a first spatial parameter for the reference transmission / reception included in the specific BLS from the base station. The first spatial parameter may be indicated to the UE by higher layer / lower layer signaling. Alternatively, the first spatial parameter may be configured / indicated to the UE in advance.

[0275] In step S1530, the terminal may perform UL transmission or DL ​​reception for the target transmission / reception based on the second spatial parameter.

[0276] For example, the terminal can determine a target transmission / reception associated with a reference transmission / reception based on a particular BLS, and can determine a second spatial parameter corresponding to the first spatial parameter for the reference transmission / reception based on a correspondence between the spatial parameters.

[0277] As illustrated in Figure 15, unlike the existing method of separately indicating DL / UL spatial parameters using RRC reconfiguration / MAC CE message / TCI status using DCI / spatial relation info, spatial parameters applied to UL / DL transmission and reception can be indicated in a mutually coordinated manner, thereby reducing signaling overhead while improving the efficiency and flexibility of spatial parameter setting / indication.

[0278] Specifically, according to the above-mentioned DL BM and UE PDCCH reception beam setting / update method, RRC reconfiguration / MAC CE message transmission is required to update TCI state information of CORESET setting, and similar operations are required for the purpose of PDSCH reception beam setting / update. In addition, the PUCCH / PUSCH beam indication method also requires RRC reconfiguration / MAC CE message transmission to update spatial relation info for beam change. Such existing beam change procedure has problems such as reduced flexibility in changing uplink / downlink transmission / reception beams and high signaling overhead for beam update.

[0279] In order to solve such problems, this disclosure describes various methods for dynamically changing the transmitting and receiving beams of the target UL / DL RS / CH while minimizing signaling overhead based on reference DL receiving beam information (e.g., QCL-related information) or UL transmitting beam information.

[0280] That is, a linkage relationship between a reference RS / CH and a target RS(s) / CH(s) can be established, and the linkage relationship and linkage range can be dynamically indicated by DCI. This means that by indicating information about the beam (or spatial parameters) used for UL / DL transmission and reception using TCI state / spatial relation info, association flexibility for determining the beam for transmission and reception can be increased. In addition, based on the UL / DL beam association, dynamic beam instruction / determination for transmission and reception can be performed by changing / updating the beam using DCI. In addition, the effect of reducing the DCI payload can be achieved by omitting beam setting / instruction-related fields in DCI according to specific beam association.

[0281] To avoid conflicts with existing non-BLS-based UL / DL transmit / receive beam setting / update schemes, an enabler can be defined to indicate whether the BLS-based scheme is applied. That is, if explicitly indicated by the enabler, the examples of the present disclosure are applied; otherwise, the existing non-BLS-based scheme may be applied.

[0282] For example, 'beam_linkage_enabler' can be set as an RRC parameter to indicate whether or not BLS-based beam setting / update operations are applied. When the enabler is 'OFF', existing (i.e., non-BLS-based) operations can be followed, and when the enabler is 'ON', examples of the present disclosure (i.e., BLS-based Examples 1 / 2 / 3 / 4, etc.) can be activated.

[0283] Various examples of the present disclosure for BLS-based UL / DL transmission and reception are described below.

[0284] Example 1

[0285] The base station can set BLS information in the terminal by higher layer (e.g., RRC) signaling.

[0286] The BLS can include a link between the spatial parameters (i.e., beam) of a reference transmission / reception (i.e., a specific reference RS / CH) and the spatial parameters (i.e., beam) of a target transmission / reception (i.e., target RS(s) / CH(s)) that are changed based on the reference transmission / reception. This allows the spatial domain filter or beam applied / used for reception or transmission of other (i.e., target) RS(s) / CH(s) to be changed / updated based on the spatial domain filter or beam applied / used for reception or transmission of the specific reference RS / CH.

[0287] For example, in operations not based on BLS, the TCI field and PRI field of DCI format 1_1 can be used to indicate the PDSCH reception beam and the ACK / NACK PUCCH transmission beam related information for the PDSCH, respectively. In contrast, based on BLS, a linkage based on the PDSCH reception beam indication can be set / indicated for the ACK / NACK PUCCH transmission beam determination. This allows the spatial domain transmission filter (spatial domain Tx filter) corresponding to the spatial domain reception filter (spatial domain Rx filter) used when receiving the PDSCH to be applied to the ACK / NACK PUCCH transmission.

[0288] Therefore, the BLS can set the range in which spatial parameters / beams for the target transmission / reception are indicated / applied based on the spatial parameters / beams for the reference transmission / reception for each state. Also, the application stage can be set in detail for a specific RS / CH. For example, in the case of PUCCH, the spatial parameter / beam change / update can be applied to all PUCCHs that are set, or the BLS can be configured to be applied only to a specific PUCCH (e.g., SR PUCCH / ACK / NACK PUCCH / CSI PUCCH, etc.). Specific examples of this will be described in detail in Examples 2 and 3.

[0289] As a further example, in the method of configuring the BLS, it is also possible to configure only the set for the target transceiver (without specifying the reference transceiver).

[0290] As a further example, a linkage relationship for a target transmission / reception set may be set for each spatial parameter / spatial domain filter / beam applied / used for reference transmission / reception. For example, assuming that two sets for target transmission / reception, 'target set A' and 'target set B', are set, the BLS may be expressed as shown in the example of Table 9 below. In the example of Table 9, for clarity of explanation, two target sets are set, but this does not limit the technical scope of the present disclosure, and the examples of the present disclosure may also be applied when three or more target sets are set.

[0291] [Table 9]

[0292] In the example of Table 9, Target set A may be {PUSCH, CSI PUCCH, PDCCH} and Target set B may be {SR PUCCH}. For example, when BLS #1 is activated / instructed among BLS #1 and BLS #2, which are BLS candidates, a second spatial parameter for PUSCH / CSI PUCCH / PDCCH, which are target transmission / reception, may be determined based on a first spatial parameter for PUCCH, which is reference transmission / reception, and a second spatial parameter for SR PUCCH, which is target transmission / reception, may be determined based on a first spatial parameter for PDSCH, which is reference transmission / reception. In the above example, BLS configuration / instruction may be performed by a MAC CE. For example, a specific ID (or index) for a BLS among one or more BLS candidates may be indicated using a MAC CE message. A specific BLS indicated by a MAC CE can change / update spatial parameters / beams for UL / DL transmission / reception based on the BLS indicated by the MAC CE from a predetermined time (e.g., after applicable timing) until a BLS update is indicated by a new MAC CE. For example, the predetermined time may be defined as 3 msec after transmitting an ACK, and a specific example of this will be described in Example 4.

[0293] In this way, when BLS is indicated by the MAC CE, the beam alignment field of the DCI may be deactivated, or the DCI may be configured by omitting specific fields in the DCI format according to the beam alignment method.

[0294] As a further example, the BLS configuration / instruction may be performed dynamically by the DCI, specific examples of which are described in Examples 2 and 3.

[0295] Example 2

[0296] This embodiment relates to an example of modifying / updating second spatial parameters (e.g., spatial domain transmission parameters / spatial domain reception parameters) for one or more UL / DL RS / CHs that are target transmission / reception when the reference transmission / reception is a DL RS / CH (e.g., PDCCH or PDSCH) and the first spatial parameters are indicated by the TCI state.

[0297] As a specific example, based on the PDCCH / PDSCH receiving beam indication, the transmitting / receiving beams of other RS(s) / CH(s) can be changed / updated according to the BLS. Unlike the MAC CE-based BLS setting / indication operation described in the first embodiment, the example of the second embodiment can indicate the BLS ID as a code point in the BLS field of the DCI when 'beam_linkage_enabler' is ON. That is, the BLS field of the DCI can indicate whether a specific BLS is activated.

[0298] For example, the TCI state indicated by the DCI for PDSCH scheduling may indicate a specific TCI state ID associated with the TCI codepoint indicated by the TCI field of DCI format 1_1. Using the DL reference RS and QCL information of the specific TCI state ID (i.e., the TCI state ID associated with the PDSCH), the UE can change / update the reference RS of the spatial relation info applied to the transmission of specific (target) UL RS(s) / CH(s) to the DL reference RS (of the TCI state ID associated with the PDSCH) (or a reference RS corresponding to the DL reference RS) based on the BLS. In addition, the UE can change / update the TCI state / spatial Rx parameters of specific (target) DL RS(s) / CH(s) to conform to the DL reference RS / QCL assumption (of the TCI state ID associated with the PDSCH) based on the BLS.

[0299] For example, the BLS for determining the transmit / receive beam for an RS / CH based on the PDSCH receive beam may be defined as shown in Table 10. The example in Table 10 is provided merely for clarity of explanation and does not limit the technical scope of the present disclosure. Therefore, the BLS may be defined using rules different from those shown in Table 10.

[0300] Referring to Table 10, the association between the PDSCH, which is the reference transmission / reception, and the PUCCH / PUSCH / PDCCH, which is the target transmission / reception, may be expressed as 0 (i.e., not associated) or 1 (i.e., associated).

[0301] [Table 10]

[0302] For example, when BLS #5 is indicated using a specific field (e.g., BLS field) of DCI (e.g., DCI format 1_1), a spatial domain transmit filter corresponding to the spatial domain transmit filter (spatial domain Rx filter) (i.e., the first spatial parameter for reference transmission and reception) according to beam indication information for PDSCH reception (e.g., TCI field) may be applied to the transmit beam of the ACK / NACK PUCCH and the transmit beam of the PUSCH (i.e., the second spatial parameter for target transmission and reception). Here, the PRI field for indicating the spatial parameter for the ACK / NACK PUCCH in the DCI (e.g., DCI format 1_1) may be omitted. As a result, it is possible to expect improvement in the efficiency of the uplink data channel and the reliability of the ACK / NACK PUCCH by utilizing the high channel quality of the PDSCH reception beam direction.

[0303] Since the target transmission / reception linked to the reference transmission / reception differs for each BLS, the degree and effect of payload reduction may differ. On the other hand, the spatial parameter / beam indication operation for the target transmission / reception is simplified, and both TCI state and spatial relation info can be used without distinguishing between UL / DL for the target transmission / reception, which greatly improves association flexibility.

[0304] Although Table 10 has been described with reference to the ACK / NACK PUCCH, various types of PUCCHs exist depending on their purpose / use, and therefore the PUCCHs for which the association relationship is defined by the BLS are not limited to the ACK / NACK PUCCH. For example, the association relationship between PUCCH type A and PUCCH type B may be defined by the BLS. The PUCCH type may be predefined according to a predetermined criterion or may be explicitly distinguished. For example, the PUCCH type may be distinguished based on the use / content / format of the PUCCH, whether it is a dedicated PUCCH, etc.

[0305] For example, when differentiating types based on PUCCH use, Type A may correspond to a PUCCH used for SR (scheduling request) / HARQ-ACK / CSI transmission, and Type B may correspond to a PUCCH used for BFRQ (beam failure recovery request).

[0306] For example, when types are distinguished based on the PUCCH format, Type A may correspond to a short PUCCH (eg, PUCCH formats 0 and 2), and Type B may correspond to a long PUCCH (eg, PUCCH formats 1, 3, and 4).

[0307] For example, when distinguishing types based on whether or not it is a dedicated PUCCH, Type A may correspond to a terminal-shared (or non-dedicated) PUCCH for HARQ-ACK purposes for Msg4 (i.e., a contention resolution message) during a RACH procedure, and Type B may correspond to a dedicated PUCCH (or terminal-specific) PUCCH.

[0308] Such a criterion for distinguishing PUCCHs can also be applied to the BLS of a third embodiment described later.

[0309] That is, the reference transmission / reception and the target transmission / reception defined by the BLS may be distinguished on an RS / CH basis, or may be distinguished on an RS / CH type basis.

[0310] Example 3

[0311] This embodiment relates to an example of changing / updating second spatial parameters (e.g., spatial domain transmission parameters / spatial domain reception parameters) for one or more UL / DL RS / CHs that are target transmission / reception when the reference transmission / reception is an UL RS / CH (e.g., PUCCH or PUSCH) and the first spatial parameters are indicated by spatial relation info.

[0312] As a specific example, the transmitting / receiving beams of other RS(s) / CH(s) can be changed / updated by the BLS based on the PUCCH / PUSCH transmitting beam indication. Unlike the MAC CE-based BLS setting / indication operation described in the first embodiment, the example of the third embodiment can indicate the BLS ID as a code point in the BLS field of the DCI when 'beam_linkage_enabler' is ON. That is, the BLS field of the DCI can indicate whether a specific BLS is activated.

[0313] For example, an SRS resource indicator (SRI) indicated by a DCI for PUSCH scheduling may be defined on a codebook (CB) basis or a non-codebook basis. For example, in a CB-based scheme, a PUSCH is transmitted based on a 1-bit SRI, a transmit precoding matrix indicator (TPMI), and a transmit rank indicator (TRI) field in DCI format 0_1. In addition, in a non-CB-based scheme, up to four 1-port SRS resources are transmitted to a base station on beams corresponding to the respective spatial relation info, and the base station receiving the SRI can indicate to a terminal an SRI to be applied to PUSCH transmission using DCI. Therefore, in a non-CB-based scheme, when a beam to be applied / used for target transmission / reception based on BLS is selected as a beam corresponding to the SRI from among multiple SRIs, a beam corresponding to the SRI may be selected based on a rule agreed upon between the base station and the terminal, or a beam corresponding to a specific SRI (e.g., the first SRI or the last SRI) indicated by the base station using DCI may be selected.

[0314] For example, the BLS for determining the transmitting and receiving beams of an RS / CH based on the PUSCH receiving beam may be defined as shown in Table 11. The example in Table 11 is provided merely for clarity of explanation and does not limit the technical scope of the present disclosure. Therefore, the BLS may be defined using rules different from those shown in Table 11.

[0315] Referring to Table 11, the presence or absence of correlation between the PUSCH, which is the reference transmission / reception, and the PUCCH / PDSCH / PDCCH, which is the target transmission / reception, may be expressed as 0 (i.e., not correlated) and 1 (i.e., correlated).

[0316] [Table 11]

[0317] For example, when BLS #6 is indicated in a specific field (e.g., BLS field) of DCI (e.g., DCI format 0_1), a spatial domain transmit filter and a spatial domain receive filter (spatial domain Rx filter) corresponding to a spatial domain transmit filter (i.e., a first spatial parameter for reference transmission and reception) according to beam indication information (e.g., spatial relation info) for PUSCH transmission may be applied to the SR PUCCH transmit beam and the PDCCH receive beam (i.e., a second spatial parameter for target transmission and reception), respectively. This can be expected to utilize the high channel quality of the PUSCH transmit beam direction and improve the efficiency of subsequent uplink scheduling requests and downlink data reception.

[0318] Although the SR PUCCH is described in Table 11, the PUCCH for which the association relationship is defined by the BLS is not limited to the SR PUCCH. As described in the second embodiment, the BLS may be configured for various PUCCH types that are distinguished based on the PUCCH purpose, content, format, whether or not it is a dedicated PUCCH, etc.

[0319] Furthermore, in the examples of Examples 2 and 3, an example is described in which the BLS defines the association between PUCCH / PUSCH / PDCCH / PDSCH (and their types), but the scope of the present disclosure is not limited thereto, and the reference / target transmission / reception for which the BLS defines the association may further include PRACH / SRS / CSI-RS / SSB.

[0320] Example 4

[0321] As described above, when the BLS changes / updates the second spatial parameters of the target transmission / reception linked to the reference transmission / reception based on the change / update of the first spatial parameters of the reference transmission / reception, the application time of the changed / updated second spatial parameters needs to be defined.

[0322] Example 1) In Example 2, the modified / updated second spatial parameters for the target transmission / reception may be applied a predetermined time unit (e.g., x msec) after the HARQ-ACK for the PDSCH, which is the reference transmission / reception, is transmitted.

[0323] Example 2) In Example 3, the modified / updated second spatial parameters for the target transmission / reception may be applied a predetermined time unit (eg, x msec) after the PUSCH, which is the reference transmission / reception, is transmitted.

[0324] Example 3) When a specific BLS is configured / indicated on a MAC CE basis in Example 1, the modified / updated second spatial parameters for the target transmission / reception may be applied a predetermined time unit (e.g., x msec) after the HARQ-ACK for the PDSCH carrying the MAC CE is transmitted.

[0325] In the above examples, the predetermined time unit may be defined as an absolute time unit such as x msec, or as an SCS-dependent time unit such as a symbol / slot / slot group / subframe / frame. Furthermore, the value of x may be a fixed value, or may be a variable value that can be set by the base station in a terminal-specific, terminal-wide (i.e., cell-specific), or terminal group-specific manner. For example, when the predetermined time unit is defined as x msec, the value of x may be 0 or 3.

[0326] In this way, a time point at which the second spatial parameter for the target transmission / reception is changed / updated based on the BLS may be defined, which may be defined as a time point after a sufficient time has elapsed for the base station to confirm that the terminal will change / update the spatial parameter based on the BLS.

[0327] In example 1, the beam for the target transmission / reception may be changed based on the BLS at a specific time (e.g., x msec) after the terminal transmits a PUCCH / PUSCH carrying a HARQ-ACK (i.e., ACK / NACK) for the PDSCH. Here, transmission of the HARQ-ACK for the PDSCH means that the DCI including a field indicating the BLS for the PDSCH, which is the reference transmission / reception, has been successfully decoded by the terminal. Therefore, the base station can confirm that the beam setting / update for the target transmission / reception has been applied by the terminal by receiving the HARQ-ACK for the PDSCH without any additional signaling regarding whether the terminal correctly applies the BLS indicated by the base station.

[0328] In example 2, the beam for the target transmission / reception may also be changed based on the BLS at a specific time (e.g., x msec) after the UE transmits the PUSCH. Here, the transmission of the PUSCH means that the DCI including a field indicating the BLS for the PUSCH, which is the reference transmission / reception, has been successfully decoded by the UE. Therefore, the BS can confirm that the beam setting / update for the target transmission / reception has been applied by the UE by receiving the PUSCH, without any additional signaling regarding whether the UE correctly applies the BLS indicated by the BS.

[0329] In Example 3, unlike the operation in which BLS is instructed based on DCI in Examples 1 and 2, BLS change / configuration may be instructed by the MAC CE. Therefore, the applicable / application timing (e.g., 3 msec after HARQ-ACK transmission to the MAC CE) defined for updating a general MAC CE-based terminal operation configuration may also be applied to Example 3. Alternatively, considering the additional time required for changing the spatial parameters (or spatial domain filter) of the terminal, the value of x may be separately defined / configured as a value greater than the general MAC CE application timing (i.e., 3 or more).

[0330] FIG. 16 is a diagram illustrating a signaling process according to one embodiment of the present disclosure.

[0331] An example of signaling operations between a base station and a terminal for the above-described embodiment is shown in FIG. 16. Here, the terminal / base station is merely an example, and may be substituted with various devices as described in FIG. 17. The base station may correspond to one base station including multiple TRPs or one cell including multiple TRPs. FIG. 16 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps described in FIG. 16 may be combined or omitted. In addition, when performing the procedures described below, the above-described downlink transmission / reception operations or uplink transmission / reception operations or beam management operations 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.

[0332] The UE may receive configuration information from the base station (S105). The configuration information may include system information (SI), scheduling information, beam management (BM)-related configuration (e.g., DL BM-related CSI-ResourceConfig IE, NZP CSI-RS resource set IE, etc.), base station configuration (e.g., TRP configuration) information, etc. For example, the configuration may include information related to reconfiguration / update of RS information for spatial-related (e.g., QCL-related) assumptions (e.g., information related to whether, how, and when reconfiguration / update is performed). The configuration may also include information related to beam link status (BLS) candidates and / or whether BLS is activated. The configuration may be transmitted by higher layer (e.g., RRC or MAC CE) signaling. If the configuration is predefined or preconfigured, this step may be omitted.

[0333] For example, based on the above-described embodiment, the configuration may include information on one or more of a TCI state, a QCL RS, or a DMRS port. For example, the TCI state may include RS information for spatial relation (e.g., QCL relation) assumption. For example, the configuration may include spatial relation information / QCL relation setting information for a DL channel (e.g., PDCCH / PDSCH) and / or an UL channel (e.g., PUSCH / PUCCH). For example, as described in the above-described embodiment, the configuration may include association relationship settings (e.g., BLS information) between a reference transceiver (e.g., reference RS / CH) and a target transceiver (e.g., target RS / CH). For example, the target transceivers may be grouped and configured as one or more sets. For example, the configuration may include information instructing a change / update to QCL-related information (e.g., RS information for spatial relation assumption) and / or association relationship settings (e.g., BLS) of a downlink channel (e.g., PDCCH / PDSCH).

[0334] For example, the operation of the UE (100 / 200 in FIG. 17) receiving the configuration from the base station (200 / 100 in FIG. 17) in step S105 described above may be implemented by the apparatus of FIG. 17 described below. For example, referring to FIG. 17, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104 to receive the configuration, and one or more transceivers 106 can receive the configuration from the base station.

[0335] The UE may receive control information from the base station (S110). The control information may be received on a control channel (e.g., PDCCH). As an example, the control information may be DCI / UCI. For example, the control information may include scheduling information related to a downlink data channel (e.g., PDSCH) and / or an uplink channel (e.g., PUCCH / PUSCH). For example, based on the above-described embodiment, the control information may include information related to one or more of a TCI state, a QCL RS, or a DMRS port. For example, a TCI state field in the control information (e.g., DCI) may indicate one or more TCI states for a DMRS port associated with a DL data channel (e.g., PDSCH) / UL channel (e.g., PUCCH / PUSCH). For example, the TCI state may include RS information for spatially related (e.g., QCL-related) assumptions.

[0336] For example, as described in the above examples, the control information may include an association setting (e.g., BLS information) between a reference transceiver (e.g., a reference CH / RS) and a target transceiver (e.g., a target CH / RS) and / or a BLS activation-related field, etc. For example, when the target transceiver is a PUCCH, a beam association may be set for each PUCCH type, which can be distinguished based on the purpose / content / format of the PUCCH, whether it is a dedicated PUCCH, etc.

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

[0338] The UE may receive data from the base station or transmit data to the base station (S115). The data may be received on a downlink channel (e.g., PDCCH / PDSCH) or transmitted on an uplink channel (e.g., PUCCH / PUSCH / PRACH). 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. The data may be received based on information set / instructed in steps S105 / S110. For example, the UE may perform channel estimation / compensation and receive the data based on the information set / instructed in steps S105 / S110. For example, based on the information set / instructed in steps S105 / S110, a spatially related RS (e.g., QCL type D RS) for receiving the data may be configured based on the above-described embodiment. For example, a spatial relation-related RS (e.g., QCL type D RS) (of a downlink channel) for data reception may be configured / changed based on spatial relation information of an uplink channel (e.g., PUCCH / PUSCH) transmitted by a UE. For example, a spatial relation-related RS (e.g., QCL type D RS) (of a downlink channel) for data reception may be configured based on the purpose / content (e.g., SR, HARQ-ACK / NACK, CSI, etc.) of the uplink channel.

[0339] For example, as described in the above example, the data may be transmitted or received based on spatial association information of a reference transmission / reception channel (e.g., target channel / RS) associated with the data based on the association relationship and BLS. For example, the reference transmission / reception channel (TPCCH / PUSCH / PDCCH / PDSCH) may be used.

[0340] For example, the terminal may receive a DL channel / RS from a base station, and may receive the DL channel / RS based on spatially related information of reference transmission and reception based on a configured BLS.

[0341] For example, the terminal can transmit an UL channel / RS to the base station, and can transmit the UL channel / RS based on spatially related information of reference transmission and reception based on the configured BLS.

[0342] For example, the operation of the UE (100 / 200 in FIG. 17) receiving the data from the base station (200 / 100 in FIG. 17) in step S115 described above may be implemented by the apparatus of FIG. 17 described below. For example, referring to FIG. 17, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104 to receive the data, and the one or more transceivers 106 can receive the data from the base station.

[0343] As mentioned above, the above-described base station / UE signaling and operations (e.g., Example 1, Example 2, Example 3, Example 4, FIGS. 15, 16, etc.) may be implemented by the apparatus described below (e.g., FIG. 17). For example, the base station may correspond to the first wireless device and the UE may correspond to the second wireless device, and vice versa may also be considered in some cases.

[0344] For example, the above-described base station / UE signaling and operations (e.g., Example 1, Example 2, Example 3, Example 4, Figures 15 and 16, etc.) may be processed by one or more processors (e.g., 102, 202) of Figure 17, and the above-described base station / UE signaling and operations (e.g., Example 1, Example 2, Example 3, Example 4, Figures 15 and 16, etc.) may be stored in a memory (e.g., one or more memories (e.g., 104, 204) of Figure 17) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 102, 202) of Figure 17.

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

[0346] FIG. 17 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.

[0347] Referring to FIG. 17, a first device / wireless device 100 and a second device / wireless device 200 can transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR).

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

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

[0350] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) in accordance with the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams contained herein. The one or more processors 102, 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams contained herein. The one or more processors 102, 202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods included in this disclosure and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts included in this disclosure.

[0351] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include 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). The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams contained in this disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams contained in this disclosure may be embodied by firmware or software in the form of code, instructions, and / or collections of instructions.

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

[0353] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flowcharts 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 referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, 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. Also, 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. Furthermore, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts contained in this disclosure, via the one or more antennas 108, 208. In this disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received user data, control information, wireless signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0354] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented without being combined with other components or features. It is also possible to combine some components and / or features to form embodiments of the present disclosure. 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 clear that claims that do not have an explicit reference relationship in the claims may be combined to form embodiments, or may be included as new claims by amendment after filing.

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

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

[0357] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present specification may include LTE, NR, 6G, and also Narrowband Internet of Things (NB-IoT) for low-power communication. Here, for example, the NB-IoT technology may be an example of a Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present specification may perform communication based on the LTE-M technology. Here, for example, the LTE-M technology may be an example of an LPWAN technology and may be referred to by various names such as enhanced Machine Type Communication (eMTC). For example, LTE-M technology may be embodied by 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 above names. Additionally or alternatively, wireless communication technologies embodied in wireless devices 100 and 200 herein may include at least one of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which consider low-power communication, and are not limited to the above names. 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]

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

Claims

1. A step of receiving linkage information included in PDSCH (physical downlink shared channel) related information, said linkage information being based on a TCI (transmission configuration indicator) state for reference spatial parameters for downlink reception and relating to a mapping relationship between said reference spatial parameters and target spatial parameters; and performing an uplink transmission based on the target spatial parameters.

2. The method of claim 1 , wherein the coordination information is associated with at least one reference transmission / reception and at least one target transmission / reception.

3. The step of receiving the link information comprises: receiving configuration information regarding at least one candidate link information; and receiving information regarding the linkage information of the at least one linkage information candidate.

4. The configuration information regarding at least one candidate link information is provided by higher layer signaling; The link information is designated to be activated among the at least one link information candidate; The method of claim 3 , wherein the indication for activation of the association information is provided by higher layer signaling or lower layer signaling.

5. The method of claim 1 , wherein the correspondence between the reference spatial parameters and the target spatial parameters is predetermined.

6. At least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor receiving, via the at least one transceiver, link information included in PDSCH (physical downlink shared channel)-related information, the link information being based on a transmission configuration indicator (TCI) state for reference spatial parameters for downlink reception and relating to a mapping relationship between the reference spatial parameters and target spatial parameters; An apparatus configured to perform uplink transmission via the at least one transceiver based on the target spatial parameters.

7. A step of transmitting linkage information included in PDSCH (physical downlink shared channel) related information, said linkage information being based on a TCI (transmission configuration indicator) state for reference spatial parameters for downlink transmission and relating to a mapping relationship between said reference spatial parameters and target spatial parameters; and performing uplink reception based on the target spatial parameters.

8. 10. A computer readable storage medium storing at least one computer program comprising instructions that, when executed by at least one processor, cause said at least one processor to perform the method of claim 1.

9. The method of claim 1 , wherein the spatial Tx filter for the uplink transmission is determined based on the TCI state corresponding to the reference spatial parameter.

10. The method of claim 1 , further comprising receiving information regarding whether an action based on the linkage information is valid.

11. The method of claim 1 , wherein the association information is configured via higher layer signaling.

12. The method of claim 1 , wherein the PDSCH-related information corresponds to a TCI field included in downlink control information for scheduling a PDSCH.

13. The apparatus of claim 6 , wherein the coordination information is associated with at least one reference transmission / reception and at least one target transmission / reception.

14. The at least one processor receiving setting information regarding at least one link information candidate; The device of claim 6 , configured to receive information regarding the linkage information of the at least one linkage information candidate.

15. the configuration information regarding the at least one association information candidate is provided by higher layer signaling; The link information is designated to be activated among the at least one link information candidate; The apparatus of claim 14 , wherein the indication for activation of the association information is provided by higher layer signaling or lower layer signaling.

16. The apparatus of claim 6 , wherein the correspondence between the reference spatial parameters and the target spatial parameters is predetermined.

17. The apparatus of claim 6 , wherein the spatial Tx filter for the uplink transmission is determined based on the TCI state corresponding to the reference spatial parameter.

18. The apparatus of claim 6 , wherein the at least one processor is configured to receive information regarding whether an action based on the linkage information is valid.

19. The apparatus of claim 6 , wherein the association information is configured via higher layer signaling.

20. The apparatus of claim 6 , wherein the PDSCH-related information corresponds to a TCI field included in downlink control information for scheduling a PDSCH.

Images