Method and apparatus for dynamically indicating spatial parameters in a wireless communication system

Abstract

A method and apparatus for dynamically indicating and applying spatial parameters in a wireless communication system are disclosed. The method for applying spatial parameters by a terminal in a wireless communication system according to one embodiment of the disclosure includes the steps of receiving, from a base station, downlink control information (DCI) including first information about one or more spatial parameters, second information about time domain resource allocation, and third information about whether a data channel is scheduled, indicating that the data channel is not scheduled based on the third information, transmitting hybrid automatic repeat request-acknowledgement (HARQ-ACK) information to the base station based on the second information, and performing uplink transmission to the base station or downlink reception from the base station based on the one or more spatial parameters based on the first information after transmitting the HARQ-ACK information.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for dynamically indicating spatial parameters in wireless communication systems. Background Technology

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

[0003] The overall requirements for next-generation mobile communication systems should be able to support the capacity for explosive data traffic, significantly increased per-user transmission rates, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies have been investigated, including dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking. Summary of the Invention

[0004] Technical issues

[0005] The technical objective of this disclosure is to provide a method and apparatus for dynamically indicating spatial parameters from a base station to a terminal and for the terminal to dynamically apply the indicated spatial parameters in a wireless communication system.

[0006] The additional technical objective of this disclosure is to provide a method and apparatus for dynamically indicating and applying spatial parameters in a wireless communication system without scheduling data transmission or reception.

[0007] The additional technical objective of this disclosure is to provide a method and apparatus for minimizing the overhead and latency of indicating and applying spatial parameters in a wireless communication system.

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

[0009] Technical solution

[0010] According to one aspect of this disclosure, a method for a terminal to apply spatial parameters in a wireless communication system may include: receiving downlink control information (DCI) from a base station, the DCI including first information related to at least one spatial parameter, second information related to time-domain resource allocation, and third information related to whether a data channel is scheduled; indicating based on the third information that the data channel is not scheduled; sending hybrid automatic repeat request-acknowledge (HARQ-ACK) information to the base station based on the second information; and after sending the HARQ-ACK information, performing uplink transmission to the base station or downlink reception from the base station based on at least one spatial parameter based on the first information.

[0011] According to another aspect of this disclosure, a method for indicating spatial parameters by a base station in a wireless communication system includes: sending downlink control information (DCI) to a terminal, the DCI including first information related to at least one spatial parameter, second information related to time-domain resource allocation, and third information related to whether a data channel is scheduled; indicating that the data channel is not scheduled based on the third information; receiving hybrid automatic repeat request-acknowledge (HARQ-ACK) information from the terminal based on the second information; and, after receiving the HARQ-ACK information, performing uplink transmission from the terminal or downlink reception to the terminal based on at least one spatial parameter based on the first information.

[0012] Beneficial effects

[0013] According to this disclosure, a method and apparatus can be provided in which a base station dynamically indicates spatial parameters to a terminal in a wireless communication system and the terminal dynamically applies the indicated spatial parameters.

[0014] According to this disclosure, a method and apparatus for dynamically indicating and applying spatial parameters in a wireless communication system without scheduling data transmission or reception can be provided.

[0015] According to this disclosure, a method and apparatus may be provided for minimizing the overhead and delay of indicating and applying spatial parameters in a wireless communication system.

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

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

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

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

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

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

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

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

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

[0025] Figure 8 This is a diagram illustrating the downlink beam management process using SSB in a wireless communication system to which this disclosure may be applied.

[0026] Figure 9 This is a diagram illustrating downlink beam management operation using CSI-RS in a wireless communication system to which this disclosure may be applied.

[0027] Figure 10 This is a diagram illustrating the Rx beam determination process of a terminal in a wireless communication system to which the present disclosure can be applied.

[0028] Figure 11 This is a diagram illustrating the Tx beam determination process of a base station in a wireless communication system to which the present disclosure can be applied.

[0029] Figure 12 This is a diagram illustrating the allocation of resources in the time and frequency domains in relation to downlink beam management operations in a wireless communication system to which this disclosure may be applied.

[0030] Figure 13 This is a diagram illustrating uplink beam management operation using SRS in a wireless communication system to which this disclosure can be applied.

[0031] Figure 14 This is a diagram illustrating the uplink beam management process in a wireless communication system to which the present disclosure can be applied.

[0032] Figure 15 It is a flowchart illustrating a method for dynamically indicating and applying spatial parameters according to this disclosure.

[0033] Figure 16 This is a diagram illustrating a signaling process according to an embodiment of the present disclosure.

[0034] Figure 17 This is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. Detailed Implementation

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

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

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

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

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

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

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

[0042] In the following text, downlink (DL) refers to communication from a base station to a terminal, while uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. A base station (BS) can be replaced by terms such as fixed station, Node B, eNB (evolved Node B), gNB (next-generation Node B), BTS (Base Transceiver System), Access Point (AP), Network (5G network), AI (Artificial Intelligence) system / module, RSU (Roadside Unit), robot, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, terminals can be fixed or mobile, and can be replaced by terms such as UE (User Equipment), MS (Mobile Station), UT (User Terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless Terminal), MTC (Machine-Type Communication) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicles, RSU (Roadside Unit), robots, AI (Artificial Intelligence) modules, drones (UAVs), AR (Augmented Reality) equipment, VR (Virtual Reality) equipment, etc.

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

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

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

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

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

[0048] -BM: Beam Management

[0049] -CQI: Channel Quality Indicator

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

[0051] -CSI: Channel State Information

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

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

[0054] -DMRS: Demodulation Reference Signal

[0055] -FDM: Frequency Division Multiplexing

[0056] -FFT: Fast Fourier Transform

[0057] -IFDMA: Interleaved Frequency Division Multiple Access

[0058] -IFFT: Inverse Fast Fourier Transform

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

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

[0061] -MAC: Media Access Control

[0062] -NZP: Non-zero power

[0063] -OFDM: Orthogonal Frequency Division Multiplexing

[0064] -PDCCH: Physical Downlink Control Channel

[0065] -PDSCH: Physical Downlink Shared Channel

[0066] -PMI: Precoding Matrix Indicator

[0067] -RE: Resource Elements

[0068] -RI: Rank indicator

[0069] -RRC: Radio Resource Control

[0070] -RSSI: Received Signal Strength Indicator

[0071] -Rx: Receive

[0072] -QCL: Quasi-co-location

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

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

[0075] -TDM: Time Division Multiplexing

[0076] -TRP: Sending and Receiving Point

[0077] -TRS: Tracking Reference Signal

[0078] -Tx: Send

[0079] -UE: User Equipment

[0080] -ZP: Zero Power

[0081] Overall System

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

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

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

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

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

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

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

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

[0090] [Table 1]

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

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

[0093] [Table 2]

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

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

[0096] [Table 3]

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

[0098] [Table 4]

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

[0100] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3. One subframe can include 4 time slots. Figure 2 The subframe = {1, 2, 4} slots shown are examples; the number of slots that can be included in a subframe is defined in Table 3 or Table 4. Additionally, micro-slots can include 2, 4, or 7 symbols, or more or fewer symbols. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier portions, etc., can be considered. The physical resources that can be considered in an NR system will be described in detail below.

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

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

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

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

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

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

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

[0108] [Equation 1]

[0109]

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

[0111] [Equation 2]

[0112]

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

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

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

[0116] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Component) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication can be performed through active BWPs, and only one BWP can be active for a given terminal. In the resource grid, each element is called a resource element (RE) and can be mapped to a complex number of symbols.

[0117] In NR systems, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip for the entire CC always on, terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different sets of parameters (e.g., subcarrier spacing, etc.) can be supported in each band of the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. With this in mind, the base station can instruct the terminal to operate only in a portion of the bandwidth, rather than the full bandwidth of the wideband CC, and for convenience, the corresponding portion of the bandwidth is defined as the bandwidth portion (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

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

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

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

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

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

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

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

[0125] Meanwhile, control information sent by the terminal to the base station via the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgment / non-acknowledgment) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. For 3GPP LTE systems, the terminal can send the aforementioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

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

[0127] [Table 5]

[0128]

[0129] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 can include resource information (e.g., UL / SUL (Supplemental UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to transport blocks (TBs) (e.g., MCS (Modulation and Compilation Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), information related to HARQ (Hybrid Automatic Repeat and Request) (e.g., procedure number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and control information included in each DCI format can be predefined. DCI format 0_0 is used to schedule PUSCHs within a cell. The information included in DCI format 0_0 is scrambled by CRC (Cyclic Redundancy Check) and transmitted using C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Compilation Scheme Cell RNTI).

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

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

[0132] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (Virtual Resource Block) - PRB (Physical Resource Block) mapping, etc.), information related to transport blocks (TB) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna port, TCI (Transmission Configuration Indicator), SRS (Sound Reference Signal) request, etc.), information related to PUCCH scheduling regarding PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

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

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

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

[0136] Beam management (BM)

[0137] The BM process is an L1 (Layer 1) / L2 (Layer 2) process for obtaining and maintaining a set of beams that can be used for downlink (DL) and uplink (UL) transmission / reception from base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams, and it may include the following processes and terms.

[0138] - Beam measurement: The operation by which a base station or UE measures the properties of the received beamformed signal.

[0139] - Beam determination: The operation of the base station or UE selecting its Tx beam / Rx beam.

[0140] - Beam scanning: The operation of covering a spatial region within a specific time interval using Tx and / or Rx beams in a predetermined manner.

[0141] - Beam Reporting: The UE's operation of reporting beamforming signal information based on beam measurements.

[0142] BM processes can be classified as (1) DL BM processes using SS (synchronization signal) / PBCH (physical broadcast channel) blocks or CSI-RS and (2) UL BM processes using SRS (sound reference signal).

[0143] In addition, each BM process may include a Tx beam scan for determining the Tx beam and an Rx beam scan for determining the Rx beam.

[0144] The DL BM process will be described below.

[0145] The DL BM process may include (1) the transmission of the DL RS (reference signal) (e.g., CSI-RS or SS block (SSB)) of the base station beamforming and (2) the beam reporting of the terminal.

[0146] Here, the beam report may include the preferred DL RS ID (identifier) ​​and the corresponding L1-RSRP (reference signal received power).

[0147] The DL RS ID can be either SSBRI (SSB Resource Indicator) or CRI (CSI-RS Resource Indicator).

[0148] The DL BM process using SSB will be described below.

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

[0150] refer to Figure 7 SSB and CSI-RS beams can be used for beam measurements. The measurement metric is the L1-RSRP per resource / block. SSB can be used for coarse beam measurements, and CSI-RS can be used for fine beam measurements. SSB can be used for both Tx and Rx beam scans.

[0151] An Rx beam scan using an SSB can be performed when the UE changes the Rx beam used for the same SSBRI across multiple SSB bursts. In this case, an SS burst includes one or more SSBs, and an SS burst set includes one or more SSB bursts.

[0152] Figure 8 This is a diagram illustrating the downlink beam management process using SSB in a wireless communication system to which this disclosure may be applied.

[0153] Configure beam reporting using SSB in the CSI / beam configuration in RRC connection state (or RRC connection mode).

[0154] refer to Figure 8 The terminal receives from the base station a CSI-ResourceConfig IE (S410) which includes a CSI-SSB-ResourceSetList of SSB resources for BM.

[0155] Table 6 shows an example of a CSI-ResourceConfig IE, and as shown in Table 6, the BM configuration using SSB configures SSB like a CSI-RS resource without separate definition.

[0156] [Table 6]

[0157]

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

[0159] When configuring CSI-RSreportConfig related to reports on SSBRI and L1-RSRP, the terminal performs a (beam) report of the optimal SSBRI and corresponding L1-RSRP to the base station (S430).

[0160] The DL BM process using CSI-RS will be described below.

[0161] The usage of CSI-RS is described as follows: i) Configure repetition parameters for a specific CSI-RS resource set, and when TRS_info is not configured, CSI-RS is used for beam management. ii) When repetition parameters are not configured and TRS_info is configured, CSI-RS is used for TRS (Tracking Reference Signal). iii) When neither repetition parameters nor TRS_info are configured, CSI-RS is used for CSI acquisition.

[0162] Such repeated parameters can be configured only for CSI-RS resource sets associated with CSI-ReportConfig that have L1 RSRP or "no report (or none)".

[0163] If the terminal is configured with a CSI-ReportConfig in which reportQuantity is configured as "cri-RSRP" or "none", and the CSI-ResourceConfig for channel measurement (higher-layer parameter resourcesForChannelMeasurement) does not include the higher-layer parameter "trs-Info" but includes an NZP-CSI-RS-ResourceSet in which the higher-layer parameter "repetition" is configured, the terminal can configure only the ports (port 1 or port 2) with the same number as the higher-layer parameter "nrofPorts" for all CSI-RS resources in the NZP-CSI-RS-ResourceSet.

[0164] When (higher-layer parameters) are repeatedly configured to "on", it relates to the terminal's Rx beam scanning process. In this case, when the terminal is configured with an NZP-CSI-RS-ResourceSet, the terminal can assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted using the same downlink spatial transmission filter. In other words, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through the same Tx beam. Here, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet can be transmitted in different OFDM symbols. Furthermore, the terminal does not expect to receive different periodicities in periodityAndOffset across all CSI-RS resources in the NZP-CSI-RS-ResourceSet.

[0165] Meanwhile, when repetition is configured to "off," it relates to the base station's Tx beam scanning process. In this case, when repetition is configured to "off," the terminal does not assume that at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted in the same downlink spatial transmission filter. In other words, at least one CSI-RS resource in the NZP-CSI-RS-ResourceSet is transmitted through different Tx beams.

[0166] In other words, when the reportQuantity of CSI-RS reportConfig IE is configured as "ssb-Index-RSRP", the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station.

[0167] Additionally, when CSI-RS resources can be configured in the same OFDM symbol as SSB (SS / PBCH block) and "QCL-TypeD" is applicable, the terminal may assume that CSI-RS and SSB are quasi-co-configured with respect to "QCL-TypeD".

[0168] Here, QCL Type D can mean that the antenna ports are quasi-co-located with respect to the spatial Rx parameter. When the terminal receives multiple DL antenna ports with a QCL Type D relationship, the same Rx beam can be applied. Additionally, the terminal does not expect the CSI-RS to be configured in an RE overlapping with the SSB's RE.

[0169] Figure 9 This is a diagram illustrating downlink beam management operation using CSI-RS in a wireless communication system to which this disclosure may be applied.

[0170] Figure 9 (a) indicates the Rx beamforming (or refinement) process of the terminal and Figure 9 (b) shows the Tx beam scanning process of the base station. Furthermore, Figure 9 (a) is the case when the repeat parameter is configured to "on", and Figure 9 (b) is the case when the repeat parameter is configured to "off".

[0171] Figure 10 This is a diagram illustrating the Rx beam determination process of a terminal in a wireless communication system to which the present disclosure can be applied.

[0172] refer to Figure 9 (a) and Figure 10 This describes the Rx beam determination process of the terminal.

[0173] The terminal receives the NZP CSI-RS resource set IE (S610) including the repetition of higher-layer parameters via RRC signaling from the base station. Here, the repetition parameter is configured to be "enabled".

[0174] The terminal repeatedly receives resources from the CSI-RS resource set configured to be repeatedly "on" in different OFDM symbols through the same Tx beam (or DL ​​spatial domain transmission filter) of the base station (S620).

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

[0176] The terminal omits the CSI report (S640). In this case, the reportQuantity of the CSI report configuration can be configured as "No report (or none)".

[0177] In other words, the terminal can omit CSI reporting when it is configured to repeatedly "on".

[0178] Figure 11 This is a diagram illustrating the Tx beam determination process of a base station in a wireless communication system to which the present disclosure can be applied.

[0179] refer to Figure 9 (b) and Figure 11 This describes the Tx beam determination process of a base station.

[0180] The terminal receives the NZP CSI-RS resource set IE (S710) including the repetition of higher-level parameters via RRC signaling from the base station. Here, the repetition parameter is configured to "off" and it is related to the base station's Tx beam scanning process.

[0181] The terminal receives resources from the CSI-RS resource set configured to be repeatedly "off" through different Tx beams (or DL ​​spatial domain transmission filters) of the base station (S720).

[0182] The terminal selects (or determines) the optimal beam (S740).

[0183] The terminal reports the selected beam ID and related quality information (e.g., L1-RSRP) to the base station (S740). In this case, the reportQuantity configured in the CSI report can be set to "CRI+L1-RSRP".

[0184] In other words, when sending CSI-RS for BM, the terminal reports CRI and the associated L1-RSRP.

[0185] Figure 12 This is a diagram illustrating the allocation of resources in the time and frequency domains in relation to downlink beam management operations in a wireless communication system to which this disclosure may be applied.

[0186] refer to Figure 12 This demonstrates how multiple CSI-RS resources are reused by applying the same Tx beam when the CSI-RS resource set is configured to be repeatedly "on", and how different CSI-RS resources are transmitted in different Tx beams when the CSI-RS resource set is configured to be repeatedly "off".

[0187] The beam indication method associated with the downlink BM will be described below.

[0188] At least for the purpose of QCL (Quasi-Co-location) indication, the terminal can be configured by RRC with a list of up to M candidate Transport Configuration Indication (TCI) states. Here, M may be 64.

[0189] Each TCI state can be configured as a set of RS. Each ID of a DL RS in the RS set that is used for at least the spatial QCL purpose (QCL type D) can refer to one of the DL RS types, such as SSB, P (periodic)-CSI RS, SP (semi-persistent)-CSI RS, A (aperiodic)-CSI RS, etc.

[0190] The ID of the DL RS in the RS set used for space QCL purposes can be initialized / updated at least by explicit signaling.

[0191] Table 7 illustrates the TCI status information elements (IE).

[0192] The TCI state IE is associated with a quasi-common address (QCL) type corresponding to one or two DL reference signals (RS).

[0193] [Table 7]

[0194]

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

[0196] Uplink beam management will be described below.

[0197] For UL BM, beam reciprocity (or beam correspondence) between Tx and Rx beams may or may not be valid, depending on the terminal implementation. If reciprocity between Tx and Rx beams is valid in both the base station and the terminal, the UL beam pair can be matched with the DL beam pair. However, when reciprocity between Tx and Rx beams is invalid in either the base station or the terminal, the process for determining the UL beam pair needs to be performed separately from the DL beam pair determination.

[0198] Furthermore, although both the base station and the terminal maintain beam correspondence, the base station can use the UL BM process to determine the DLTx beam without requesting the terminal to report the preferred beam.

[0199] UL BM can be performed via beamforming UL SRS transmission, and whether UL BM is applied to an SRS resource set can be configured via usage (a higher-level parameter). When the usage is configured as "BeamManagement (BM)," only one SRS resource can be transmitted in each of multiple SRS resource sets at a given time.

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

[0201] Similar to DL BM, the UL BM process can also be classified into Tx beam scanning at the terminal and Rx beam scanning at the base station.

[0202] Figure 13 This is a diagram illustrating uplink beam management operation using SRS in a wireless communication system to which this disclosure can be applied.

[0203] Figure 13 (a) The illustrated base station's Rx beam determination operation and Figure 13 (b) Tx beam scanning operation of the terminal shown in the figure.

[0204] Figure 14 This is a diagram illustrating the uplink beam management process in a wireless communication system to which the present disclosure can be applied.

[0205] The terminal receives RRC signaling (e.g., SRS-Config IE) from the base station, which includes usage parameters configured as “beam management” (higher-layer parameters) (S1010).

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

[0207] The network can trigger the transmission of SRS resource sets by using the configured aperiodicSRS-ResourceTrigger (L1 DCI).

[0208] [Table 8]

[0209]

[0210]

[0211] In Table 8, usage represents a higher-level parameter that indicates 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 representing the spatial relationship configuration between the reference RS and the target SRS. Here, the reference RS can be an SSB, CSI-RS, or SRS corresponding to the L1 parameter "SRS-SpatialRelationInfo". The usage is configured per SRS resource set. The terminal determines the Tx beam of the SRS resource to be transmitted (S1020) based on the SRS-SpatialRelation Info included in the SRS-Config IE. Here, SRS-SpatialRelation Info is configured per SRS resource and indicates whether the same beam used in the SSB, CSI-RS, or SRS will be applied per SRS resource. Furthermore, SRS-SpatialRelationInfo can be configured or not configured for each SRS resource.

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

[0213] More specifically, for P-SRS where "SRS-ResourceConfigType" is configured as "Periodic":

[0214] i) When SRS-SpatialRelationInfo is configured as "SSB / PBCH", the UE transmits the corresponding SRS resources by applying the same spatial domain transmission filter (or generated by the corresponding filter) as the spatial domain Rx filter used for SSB / PBCH reception; or

[0215] ii) When SRS-SpatialRelationInfo is configured as "CSI-RS", the UE transmits SRS resources by applying the same spatial domain transmission filter used for periodic CSI-RS or SP (semi-persistent) CSI-RS reception; or

[0216] iii) When SRS-SpatialRelationInfo is configured as “SRS”, the UE transmits the corresponding SRS resources by applying the same spatial domain transmission filter used for periodic SRS transmission.

[0217] Although “SRS-ResourceConfigType” is configured as “SP (Semi-Persistent)-SRS” or “AP (Aperiodic)-SRS”, beamforming and transmission operations can be applied in a similar manner to those described above.

[0218] In addition, the terminal may or may not receive feedback about SRS from the base station, as in the following three cases (S1040).

[0219] i) When Spatial_Relation_Info is configured for all SRS resources in the SRS resource set, the terminal uses the beam indicated by the base station to transmit SRS. For example, when Spatial_Relation_Info indicates all the same SSB, CRI, or SRI, the terminal uses the same beam to repeatedly transmit SRS. This situation corresponds to Figure 13 (a) Use of Rx beams as a base station selection method.

[0220] ii) Spatial_Relation_Info may not be configured for all SRS resources in the SRS resource set. In this case, the terminal can transmit with freely changing SRS beams. In other words, this situation corresponds to Figure 13 (b) As a use for terminal scanning Tx beams.

[0221] iii) Spatial_Relation_Info can be configured only for a subset of SRS resources in the SRS resource set. In this case, for the configured SRS resources, SRS can be transmitted via the indicated beam, and for SRS resources without Spatial_Relation_Info configured, SRS can be transmitted via a terminal randomly applying a Tx beam.

[0222] CSI related operations

[0223] In NR (New Radio) systems, CSI-RS (Channel State Information-Reference Signal) is used for time and / or frequency tracking, CSI calculation, L1 (Layer 1)-RSRP (Reference Signal Received Power) calculation, and mobility. Here, CSI calculation is related to CSI acquisition, and L1-RSRP calculation is related to beam management (BM).

[0224] CSI (Channel State Information) is a general term for information that can represent the quality of the radio channel (or link) formed between the terminal and the antenna port.

[0225] - In order to perform one of the uses of CSI-RS, the terminal (e.g., user equipment UE) receives configuration information related to CSI from the base station (e.g., general node B gNB) via RRC (radio resource control) signaling.

[0226] The configuration information related to CSI may include at least one of the following: information related to CSI-IM (Interference Management) resources, information related to CSI measurement configuration, information related to CSI resource configuration, information related to CSI-RS resources, or information related to CSI reporting configuration.

[0227] i) Information related to CSI-IM resources may include CSI-IM resource information, CSI-IM resource set information, etc. A CSI-IM resource set is identified by a CSI-IM resource set ID (identifier), and a resource set includes at least one CSI-IM resource. Each CSI-IM resource is identified by a CSI-IM resource ID.

[0228] ii) Information related to CSI resource configuration can be expressed as a CSI-ResourceConfig IE. Information related to CSI resource configuration defines a group that includes at least one of the NZP (Non-Zero Power) CSI-RS resource sets, CSI-IM resource sets, or CSI-SSB resource sets. In other words, information related to CSI resource configuration can include a list of CSI-RS resource sets, and the list of CSI-RS resource sets can include at least one of the NZP CSI-RS resource set list, the CSI-IM resource set list, or the CSI-SSB resource set list. A CSI-RS resource set is identified by a CSI-RS resource set ID, and a resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID.

[0229] Parameters indicating the usage of CSI-RS (e.g., the "repeat" parameter related to BM, the "trs-Info" parameter related to tracking) can be configured per NZP CSI-RS resource set.

[0230] iii) Information related to CSI report configuration includes the report configuration type (reportConfigType) parameter, which indicates the time-domain behavior, and the report quantity parameter, which indicates the number of CSI-related data used for reporting. The time-domain behavior can be periodic, non-periodic, or semi-persistent.

[0231] - The terminal measures CSI based on configuration information related to CSI.

[0232] CSI measurement may include (1) the process in which the terminal receives the CSI-RS and (2) the process in which the CSI is calculated from the received CSI-RS, and is described in detail below.

[0233] For CSI-RS, the RE (resource element) mapping of CSI-RS resources in the time and frequency domains is configured by the higher-level parameter CSI-RS-ResourceMapping.

[0234] The terminal reports the measured CSI to the base station.

[0235] Here, when the CSI-ReportConfig quantity is configured to "None (or No Report)," the terminal can omit reporting. However, even when the quantity is configured to "None (or No Report)," the terminal can still report to the base station. When the quantity is configured to "None," aperiodic TRS or configuration repetition is triggered. In this case, reporting by the terminal can only be omitted if repetition is configured to "On."

[0236] CSI measurement

[0237] The NR system supports more flexible and dynamic CSI measurement and reporting. Here, CSI measurement can include the process of receiving CSI-RS and obtaining CSI by calculating the received CSI-RS.

[0238] As a time-domain behavior for CSI measurement and reporting, it supports aperiodic / semi-persistent / periodic CM (channel measurement) and IM (interference measurement). A 4-port NZP CSI-RS RE pattern is used for CSI-IM configuration.

[0239] NR's CSI-IM-based IMR has a design similar to LTE's CSI-IM and is configured independently of the ZP CSI-RS resources used for PDSCH rate matching. Additionally, each port simulates an interference layer with (desirable channels and) pre-compiled NZP CSI-RS in its NZP-IMR-based interference layer. Since this concerns intra-cell interference measurements in a multi-user scenario, it primarily targets MU interference.

[0240] The base station sends a pre-compiled NZP CSI-RS to the terminal in each port of the configured NZP CSI-RS-based IMR.

[0241] The terminal assumes a channel / interference layer and measures interference concentrated on each port.

[0242] When there is no PMI and RI feedback for the channel, multiple resources are configured in the set and the base station or network indicates a subset of NZP CSI-RS resources via DCI for channel / interference measurement.

[0243] Provide a more detailed description of resource settings and resource configuration.

[0244] Resource settings

[0245] Each CSI resource setting, "CSI-ResourceConfig," includes the configuration for S ≥ 1 CSI resource sets (given by the higher-level parameter csi-RS-ResourceSetList). The CSI resource setting corresponds to CSI-RS-resourcesetlist. Here, S represents the number of configured CSI-RS resource sets. The configuration for S ≥ 1 CSI resource sets includes each CSI resource set, which comprises CSI-RS resources (configured with NZP CSI-RS or CSI-IM) and SS / PBCH block (SSB) resources for L1-RSRP computation.

[0246] Each CSI resource setting is located at the DL BWP (bandwidth portion) identified by the higher-level parameter bwp-id. Furthermore, all CSI resource settings linked to the CSI reporting setting have the same DL BWP.

[0247] The temporal behavior of CSI-RS resources in the CSI resource settings included in the CSI-ResourceConfig IE can be indicated by the higher-level parameter resourceType and can be configured as aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI resource settings, the number (S) of configured CSI-RS resource sets is limited to "1". For periodic and semi-persistent CSI resource settings, the configured periodicity and slot offset are given by the parameter set of the associated DLBWP via bwp-id.

[0248] When a UE is configured with multiple CSI-ResourceConfigs that include the same CSI-IM resource ID, configure the same time-domain behavior for the CSI-ResourceConfigs.

[0249] When a UE is configured with multiple CSI-ResourceConfigs that include the same CSI-IM resource ID, configure the same time-domain behavior for the CSI-ResourceConfigs.

[0250] One or more CSI resource settings for channel measurement (CM) and interference measurement (IM) are configured via higher-level signaling as follows.

[0251] - CSI-IM resources for interference measurement

[0252] - NZP CSI-RS resources for interference measurement

[0253] NZP CSI-RS resources for channel measurements

[0254] In other words, CMR (Channel Measurement Resource) can be NZP CSI-RS for CSI acquisition, and IMR (Interference Measurement Resource) can be NZP CSI-RS for CSI-IM and IM.

[0255] In this case, CSI-IM (or ZP CSI-RS for IM) is mainly used for inter-cell interference measurement.

[0256] In addition, the NZP CSI-RS for IM is mainly used for intra-cell interference measurements from multiple users.

[0257] The UE may assume that the CSI-RS resource configured for channel measurement and the CSI-IM / NZP CSI-RS resource configured for interference measurement for a CSI report are “QCL-TypeD” per resource.

[0258] Resource settings configuration

[0259] As described, resource settings can refer to a list of resource sets.

[0260] For aperiodic CSI, each trigger state configured using the higher-level parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs linked to periodic, semi-persistent, or aperiodic resource settings for each CSI-ReportConfig.

[0261] A report setting can be connected to up to three resource settings.

[0262] - When a resource setting is configured, the resource setting (given by the higher-level parameter resourcesForChannelMeasurement) is about the channel measurements used for L1-RSRP calculation.

[0263] - When two resource settings are configured, the first resource setting (given by the higher-level parameter resourcesForChannelMeasurement) is used for channel measurements, and the second resource setting (given by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference) is used for interference measurements performed in CSI-IM or NZP CSI-RS.

[0264] When the three resource settings are configured, the first resource setting (given by resourcesForChannelMeasurement) is used for channel measurements, the second resource setting (given by csi-IM-ResourcesForInterference) is used for CSI-IM-based interference measurements, and the third resource setting (given by nzp-CSI-RS-ResourcesForInterference) is used for NZP-CSI-RS-based interference measurements.

[0265] For semi-persistent or periodic CSI, each CSI-ReportConfig is linked to a periodic or semi-persistent resource setting.

[0266] - When a resource setting (given by resourcesForChannelMeasurement) is configured, that resource setting is about the channel measurements used for L1-RSRP calculation.

[0267] - When two resource settings are configured, the first resource setting (given by resourcesForChannelMeasurement) is used for channel measurements, and the second resource setting (given by the higher-level parameter csi-IM-ResourcesForInterference) is used for interference measurements performed in CSI-IM.

[0268] CSI Calculation

[0269] When interference measurements are performed in CSI-IM, each CSI-RS resource used for channel measurements is associated with a CSI-IM resource in the corresponding resource set, in the order of CSI-RS resources and CSI-IM resources. The number of CSI-RS resources used for channel measurements is the same as the number of CSI-IM resources.

[0270] Furthermore, when performing interference measurements in NZP CSI-RS, the UE does not expect one or more NZP CSI-RS resources to be configured in the relevant resource set in the resource settings used for channel measurements.

[0271] Terminals configured with the higher-level parameter nzp-CSI-RS-ResourcesForInterference are not expected to have 18 or more NZP CSI-RS ports configured in the NZP CSI-RS resource set.

[0272] For CSI measurements, the terminal assumes the following.

[0273] - Each NZP CSI-RS port configured for interference measurement corresponds to the interference transmission layer.

[0274] - All interference transmission layers of the NZP CSI-RS port used for interference measurement consider the EPRE (Energy Per Resource Element) ratio.

[0275] - Different interference signals in the REs of NZP CSI-RS resources for channel measurement, NZP CSI-RS resources for interference measurement, or CSI-IM resources for interference measurement.

[0276] CSI Report

[0277] For CSI reports, the time and frequency resources available to the UE are controlled by the base station.

[0278] CSI (Channel State Information) may include at least one of the following: Channel Quality Indicator (CQI), Precompiled Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), or L1-RSRP.

[0279] For CQI, PMI, CRI, SSBRI, LI, RI, and L1-RSRP, the terminal is configured by a higher layer with N ≥ 1 CSI-ReportConfig settings, M ≥ 1 CSI-ResourceConfig settings, and one or two trigger states (provided by aperiodicTriggerStateList and semiPersistentOnPUSCH-TriggerStateList). Each trigger state in aperiodicTriggerStateList includes an associated list of CSI-ReportConfigs indicating the channel and optional resource set ID used for interference. In semiPersistentOnPUSCH-TriggerStateList, each trigger state includes an associated CSI-ReportConfig.

[0280] In addition, the time-domain behavior of the CSI report supports periodicity, semi-persistence, and non-periodicity.

[0281] i) Perform periodic CSI reporting in both short and long PUCCH. The periodicity and slot offset of periodic CSI reporting can be configured by RRC and refer to CSI-ReportConfig IE.

[0282] ii) SP (half-cycle) CSI reports are executed in short PUCCH, long PUCCH, or PUSCH.

[0283] For SP CSI in short / long PUCCH, periodicity and slot offset are configured by RRC, and CSI reporting is activated / deactivated by separate MAC CE / DCI.

[0284] For SP CSI in PUSCH, the periodicity of SP CSI reports is configured by RRC, but the slot offset is not configured by RRC, and SP CSI reports are activated / deactivated by DCI (format 0_1). For SP CSI reports in PUSCH, separate RNTIs (SP-CSI C-RNTI) are used.

[0285] The initial CSI report timing follows the PUSCH time-domain allocation value indicated by the DCI, and subsequent CSI report timing follows the periodicity configured by the RRC.

[0286] DCI format 0_1 ​​can include a CSI request field and activate / deactivate a specific configured SP-CSI trigger state. SPCSI reports have an activation / deactivation mechanism equivalent to or similar to that used in SPS PUSCH for data transfer.

[0287] iii) Non-periodic CSI reporting is performed in PUSCH and triggered by DCI. In this case, information related to triggering non-periodic CSI reporting can be delivered / instructed / configured via MAC-CE.

[0288] For AP CSI with AP CSI-RS, the timing of AP CSI-RS is configured by RRC, and the timing used for AP CSI reporting is dynamically controlled by DCI.

[0289] In NR, the method of partitioning and reporting CSI across multiple report instances applied to PUCCH-based CSI reports in LTE (e.g., transmitted in the order of RI, WB PMI / CQI, SB PMI / CQI) is not applied. Instead, in NR, there is a restriction that specific CSI reports are not configured in short / long PUCCHs, and CSI omission rules are defined. Additionally, regarding AP CSI report timing, the PUSCH symbol / slot position is dynamically indicated by the DCI. Furthermore, candidate slot offsets are configured by RRC. For CSI reporting, a slot offset (Y) is configured for each report setting. For UL-SCH, the slot offset K2 is configured separately.

[0290] Two CSI latency levels (low latency level and high latency level) are defined with respect to CSI computational complexity. Low latency CSI is WB CSI, which includes up to 4 port type I codebooks or up to 4 port non-PMI feedback CSI. High latency CSI refers to CSI other than low latency CSI. For a normal terminal, (Z, Z') is defined in OFDM symbols. Here, Z represents the minimum CSI processing time from receiving an aperiodic CSI trigger DCI until executing a CSI report. Furthermore, Z' refers to the minimum CSI processing time from receiving a CSI-RS for channel / interference until executing a CSI report.

[0291] In addition, the terminal report can calculate the number of CSIs simultaneously.

[0292] Quasi-co-located (QCL)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0335] Dynamic indication of spatial parameters

[0336] In the following sections, various examples of this disclosure for dynamically indicating and applying spatial parameters will be described.

[0337] Spatial parameters (or beam-related parameters) associated with downlink transmission / reception may include physical channels used for transmitting and receiving downlink control information or data, or QCL information assumed by the terminal. This QCL information may include QCL reference signal (RS) information, and QCL RS information may be configured for each QCL type (e.g., QCL types A / B / C / D). For example, downlink control information (DCI) can be transmitted and received via a PDCCH, and spatial parameters associated with DCI transmission / reception may include QCL reference information, TCI status information, etc., for the PDCCH DMRS antenna port. Similarly, downlink data can be transmitted and received via a PDSCH, and spatial parameters associated with downlink data transmission / reception may include QCL reference information, TCI status information, etc., for the PDSCH DMRS antenna port.

[0338] However, in this disclosure, the term "spatial parameter" is not limited to QCL information and may include spatial parameters applied to uplink transmissions (e.g., spatial relationship information related to uplink transmission beams). For example, uplink control information (UCI) can be transmitted / received via PUCCH and / or PUSCH, and spatial parameters related to UCI transmission / reception may include PRI (PUCCH Resource Indicator), SRI, spatial relationship information, UL TCI status related to PUCCH / PUSCH transmission / reception, or the associated QCL reference RS, etc.

[0339] Alternatively, spatial parameters can be set separately for the downlink or uplink, or spatial parameters can be configured as a whole for both the downlink and uplink.

[0340] Alternatively, spatial parameters can be defined or configured as a set of spatial parameters that includes at least one spatial parameter. In the following text, for simplicity, at least one spatial parameter will be collectively referred to as a spatial parameter.

[0341] In the following description, spatial parameters or spatial relation information may mean including spatially related assumed RS information / QCL related (or reference) RS information / QCL parameters, TCI status, or similar information for data / signals transmitted / received via UL channel / DL channel (hereinafter, DL / UL channel / signal), or may be expressed by mixing with / replacing the above terms.

[0342] In the following examples, using / applying / mapping a specific spatial parameter (or TCI state or TCI) when transmitting / receiving data / DCI / UCI for a specific frequency / time / space resource means that in the case of DL, the QCL type and QCL RS indicated by the corresponding spatial parameter are used in the corresponding frequency / time / space resource to estimate the channel from the DMRS and receive / demodulate data / DCI (e.g., PDSCH / PDCCH) with the estimated channel, and in the case of UL, the transmission beam and / or transmission power indicated by the corresponding spatial parameter are used in the corresponding frequency / time / space resource to transmit / modulate the DMRS and data / UCI (e.g., PUSCH / PUCCH).

[0343] Figure 15 It is a flowchart illustrating a method for dynamically indicating and applying spatial parameters according to this disclosure.

[0344] In step S1510, the terminal can receive downlink control information (DCI) from the base station.

[0345] For the DCI format of dynamic indication of spatial parameters, the DCI format for DL ​​assignment (hereinafter, DL DCI) (e.g., DCI format series 1) or the DCI format for UL licensing (hereinafter, UL DCI) (e.g., DCI format series 0) can be used. Alternatively, the DCI of dynamic indication of spatial parameters can be transmitted via PDCCH.

[0346] The dynamic indication of spatial parameters in the DCI may include first information related to at least one spatial parameter, second information related to time-domain resource allocation (TDRA), and third information related to whether a data channel (e.g., PDSCH or PUSCH) is scheduled.

[0347] For example, when the third information indicates that a data channel is scheduled, spatial parameters based on the first information can be applied to the channel carrying the scheduled data (e.g., PDSCH or PUSCH). This DCI may correspond to a conventional DL assigning DCI or UL licensed DCI that involves the scheduling of the data channel and indicates the spatial parameters of the data channel, but may not correspond to the spatial parameter indication DCI in this disclosure.

[0348] For example, when the third information indicates that the data channel is not scheduled, the terminal can apply or update the spatial parameters based on the first information, and can apply the updated spatial parameters to the UL / DL channel / signal transmission / reception subsequently executed after the corresponding DCI. Here, the UL / DL channel / signal immediately following the DCI is distinguished from the data channel scheduled by the DCI.

[0349] In addition, the spatial parameters based on the first information may include at least one of the spatial parameters directly indicated by the first information or spatial parameters that are linked to the spatial parameters directly indicated by the first information.

[0350] In other words, according to the Spatial Parameter Indication (DCI) in this disclosure, modified (or updated) spatial parameters can be applied to the terminal without scheduling the data channel. Therefore, since it is not necessary to perform data channel scheduling and transmission / reception for changing / updating spatial parameters for the terminal, the overhead and latency required for data channel transmission / reception can be reduced.

[0351] Here, third information can be indicated by one or more fields in the DCI. For example, third information can be indicated by a combination of two or more fields in the DCI.

[0352] For example, a specific value in at least one of the fields in the DCI—Frequency Domain Resource Assignment (FDRA), RV, MCS, NDI, or HARQ Procedure Number (HPN)—can indicate that the data channel is not scheduled. For example, a specific value in the FDRA field can indicate that the data channel is not scheduled. For example, in addition to the FDRA field having a specific value, at least one of the RV, MCS, NDI, or HPN fields having a specific value can indicate that the data channel is not scheduled. For example, when FDRA, RV, MCS, and NDI (or FDRA, RV, MCS, NDI, and HPN) have corresponding (i.e., the same or different) specific values, their combination can indicate that the data channel is not scheduled. Other fields or combinations of fields in the DCI besides the FDRA, RV, MCS, NDI, and HPN fields can indicate whether the data channel is scheduled.

[0353] In step S1520, the terminal may send HARQ-ACK information to the base station.

[0354] When the third information indicates that a data channel has been scheduled, the HARQ-ACK information can be information indicating that the data channel scheduled by the DCI (e.g., PDSCH) has been successfully decoded. In this case, the second information associated with TDRA can indicate the timing of the scheduled PDSCH. Additionally, the position of the ACK information for the PDSCH in the HARQ-ACK codebook related to the format of the HARQ-ACK transmission can be determined by the time interval between the PDSCH and the HARQ feedback, indicated by separate indication information (e.g., dl-Data-ToUL-ACK or PDSCH-to-HARQ feedback timing indicator).

[0355] When the third information indicates that the data channel is not scheduled, the HARQ-ACK information can be information indicating that the spatial parameter indicating DCI (or the PDCCH carrying the spatial parameter indicating DCI) has been successfully decoded. Here, the position of the ACK information for DCI / PDCCH in the HARQ-ACK codebook can be determined based on the second information (i.e., TDRA).

[0356] Meanwhile, for the case of SPS (semi-persistent) PDSCH release via DCI, HARQ-ACK for DCI / PDCCH can be sent. However, the position of the ACK information for DCI / PDCCH for the purpose of SPS PDSCH release in the HARQ-ACK codebook is not determined based on TDRA, and similar to HARQ ACK transmission for PDSCH, it can be determined by the time interval between PDSCH and HARQ feedback indicated by separate indication information (e.g., dl-Data-ToUL-ACK or PDSCH-to-HARQ feedback timing indicator).

[0357] In other words, when the third information indicates that the data channel is not scheduled, the second information related to the TDRA indicating the time position of the data channel when the data channel is scheduled can be used for the time position of HARQ-ACK transmission for DCI / PDCCH, or for the position of the ACK information in the HARQ-ACK codebook (especially the type-1 (or semi-static) HARQ-ACK codebook).

[0358] After sending the HARQ-ACK information in step S1530, the terminal can perform UL / DL transmission / reception based on at least one spatial parameter based on the first information. After the terminal sends a HARQ-ACK message indicating that it has successfully received the spatial parameter indication DCI, at least one spatial parameter based on the first information can be applied (or modified or updated). UL / DL transmission / reception can be performed based on at least one spatial parameter based on the first information after the point in time when the at least one spatial parameter based on the first information is applied (unless there is an additional indication of the spatial parameter).

[0359] As described in step S1510, when the third information in the spatial parameter indicating DCI indicates that the data channel is not scheduled, the terminal can apply or update the spatial parameters based on the first information in DCI, and can apply the updated spatial parameters to UL / DL channel / signal transmission / reception performed after the reception of DCI (or after the transmission of HARQ-ACK information for the corresponding DCI). Here, UL / DL channels / signals are not limited to data channels (e.g., terminal-specific PDSCH, dynamically licensed PUSCH) and various channels transmitted / received by the terminal (e.g., non-terminal-specific PDSCH, non-terminal-specific PDCCH, configuration-licensed PUSCH, PUCCH, etc.) and / or various signals (e.g., CSI-RS, SRS, etc.).

[0360] In addition, the interval between the time when the terminal sends a HARQ-ACK for the spatial parameter indication DCI and the time when the application changes or updates the spatial parameters can be predefined or configured / indicated by the base station.

[0361] The following sections will describe detailed examples of the spatial parameter indication (DCI) related to this disclosure.

[0362] First, the update scheme for the DL spatial parameters (or DL ​​TCI status) of the DCI in regular NR beam management operations will be described.

[0363] For up to 128 candidate TCI states configured by RRC, eight of them can be activated (or downselected) by MAC-CE and can be mapped to code points in the TCI field of the DL DCI. In this regard, one of the TCI states activated by MAC-CE can be dynamically indicated via the TCI field of the DL DCI used for scheduling subsequent PDSCHs. For PUSCH beam indication via UL DCI, the base station can indicate to the terminal using the DCI format 0_1 ​​used for PUSCH scheduling, and can indicate the SRS resource as a reference via the SRI field in the UL DCI to configure / indicate the corresponding PUSCH transmission beam.

[0364] Next, the UL space parameter (or UL TCI) framework will be described.

[0365] Essentially, spatialRelationInfo can be used to allow a base station to indicate to a terminal the transmission beam to be used when the terminal transmits a UL channel. The base station can configure / indicate DL RS (e.g., SSB-RI (Resource Indicator), (Periodic / Semi-Persistent / Aperiodic) CRI (CSI-RS Resource Indicator)) or SRS resources to the terminal as a reference RS for the target UL channel and / or target RS via RRC configuration. This allows the base station to indicate which UL transmission beam to use when the corresponding terminal transmits PUCCH and / or SRS. Additionally, when the base station schedules PUSCH to the terminal, the SRS transmission beam indicated by the base station can be specified as the transmission beam for PUSCH transmission via the SRI field, and the SRS transmission beam can be used as the terminal's PUSCH transmission beam.

[0366] In addition, two UL MIMO transmission schemes can be considered for PUSCH transmission: one is a codebook-based (CB) UL transmission scheme, and the other is a non-codebook-based (NCB or non-CB) UL transmission scheme.

[0367] In the following description, "send SRS resource set" can be used with the same meaning as "send SRS based on information configured in SRS resource set", and "send SRS resource" or "send multiple SRS resources" can be used with the same meaning as "send SRS based on information configured in SRS resource".

[0368] In the case of a CB UL transmission scheme, the base station can first configure and / or indicate the SRS resource set for the CB purpose (e.g., usage) to the terminal, and the terminal can transmit SRS based on the specific n-port SRS resources in the corresponding SRS resource set. The base station can obtain UL channel-related information based on the corresponding SRS transmission and can use the UL channel-related information for PUSCH scheduling for the terminal.

[0369] Subsequently, the base station can perform PUSCH scheduling via the UL DCI, and can indicate the SRS resources previously used for SRS transmissions of the terminal to the CB via the SRI field of the DCI. Therefore, the base station can instruct the terminal's PUSCH transmission beam. Additionally, the base station can indicate the UL codebook by sending the Precoding Matrix Indicator (TPMI) field, and thus, the base station can instruct the terminal on the UL rank and UL precoder. The corresponding terminal can then perform PUSCH transmissions as instructed by the base station.

[0370] In the case of an NCB UL transmission scheme, the base station can first configure and / or indicate a set of SRS resources for non-CB purposes (e.g., usage) to the terminal, and the terminal can determine the precoder to be applied to the SRS resources (up to 4 resources, 1 port per resource) in the corresponding SRS resource set based on the reception of NZP CSI-RS linked to the corresponding resource set. The terminal can then simultaneously transmit SRS based on the determined precoder and the corresponding SRS resources. Subsequently, the base station can perform PUSCH scheduling via the UL DCI, and can indicate some non-CB SRS resources previously used for the terminal's SRS transmission via the SRI field of the DCI, thus instructing the terminal's PUSCH transmission beam. Additionally, the base station can simultaneously indicate the UL rank and UL precoder via the SRI field. The terminal can then perform PUSCH transmission as instructed by the base station.

[0371] The method for indicating the terminal's panel and / or beam in uplink transmission is as follows.

[0372] The base station can configure / indicate panel-specific transmissions for UL transmissions. For this purpose, a UL-TCI framework can be introduced, and UL-TCI-based signaling can be performed similarly to DL beam indication. For example, a new panel ID can be introduced. Panel-specific signaling can be performed using UL-TCI states. UL-TCI states can be defined as shown in Table 9 below.

[0373] [Table 9]

[0374]

[0375] Alternatively or additionally, a new panel ID may be introduced, which can be implicitly / explicitly applied to transmissions for a target RS resource or resource set for PUCCH resources, SRS resources, PRACH, etc. The new panel ID can be used implicitly (e.g., via DL beam reporting) or explicitly to perform panel-specific signaling. When explicitly signaled, the ID can be configured in the target RS / channel or reference RS (e.g., in DL RS resource configuration or spatial relationship information). A new MAC CE may not be specified for the purpose of introducing the ID.

[0376] As shown in Table 9, a unified framework can be considered so that the base station can configure and / or indicate the transmission panel / beam for the terminal's UL channel and / or UL RS. As an example, such a framework can be referred to as the UL-TCI framework for ease of description. The UL-TCI framework can be an extension of the DL-TCI framework considered in conventional schemes (e.g., Rel-15 NR systems) to the UL. When based on the UL-TCI framework, the base station can configure the DL RS (e.g., SSB-RI, CRI) and / or UL RS (e.g., SRS) to the terminal as reference RSs or source RSs to be used / applied as transmission beams for the target UL channel (e.g., PUCCH, PUSCH, PRACH) and / or target UL RS (e.g., SRS) via higher-level signaling (e.g., RRC configuration). The corresponding terminal can use the transmission beams of the reference RS or source RS configured by the base station when transmitting the target UL channel and / or target UL RS.

[0377] When applying the UL-TCI framework, compared to the conventional 'SRI-based PUSCH scheduling and PUSCH beam indication' scheme, which requires sending SRS for CB or non-CB purposes before the SRI indication for PUSCH transmission, it is advantageous because it reduces overhead and latency when configuring and / or indicating PUSCH transmission beams. Furthermore, the UL-TCI framework-based scheme has the advantage of being universally applicable to all UL channels / RS such as PUCCH / PUSCH / PRACH / SRS.

[0378] As shown in Table 9, a unified signaling scheme for UL channel / RS and / or DL ​​channel / RS receiving panels / beam configuration / indication transmission panels / beams for base station terminals can be considered. As one approach, when indicating or updating beam / panel RS (e.g., QCL type D RS, spatial relationship RS) using DCI for PDSCH or PUSCH, not only the beam / panel RS for the corresponding PDSCH or PUSCH, but also the QCL (type D) RS for other DL channels / signals (associated with the corresponding channel) and / or the spatial relationship RS for other UL channels / signals (associated with the corresponding channel) can be simultaneously (or after a specific time) updated to the indicated beam / panel RS.

[0379] Here, updating the DL / UL TCI via the UL / DL DCI requires data scheduling for the DL / UL. That is, even if there is no transmitted / received data from the DL / UL perspective, PDSCH / PUSCH scheduling is still required for dynamic beam indication / updates, leading to degradation in overhead, latency, and overall system performance. This disclosure describes a dynamic beam indication / update method that reduces signaling overhead (e.g., PDSCH / PUSCH scheduling) and latency involved when updating beams via the DL DCI or UL DCI (when there is no UL / DL data).

[0380] In the following description, Dynamic Beam Indication / Update DCI refers to a DCI that indicates / updates DL / UL beams (or DL / UL spatial parameters) without data channel (e.g., PDSCH or PUSCH) scheduling.

[0381] Example 1

[0382] This embodiment relates to UL DCI for dynamic beam indication / update. The base station can configure and send UL DCI to the terminal according to the following embodiment. The terminal can apply beam indication or perform beam update based on the indication via the corresponding DCI without PUSCH scheduling / transmission.

[0383] In the following description, configuring / indicating UL-SCH includes scheduling PUSCH, which is the physical channel carrying UL-SCH. Additionally, configuring / indicating aperiodic (AP) CSI triggering includes triggering AP CSI-RS and / or AP CSI reports.

[0384] Example 1-1: In UL DCI, UL-SCH and AP CSI triggering may not need to be configured / indicated.

[0385] Example 1-2: In UL DCI, UL-SCH may not be configured / indicated, and the amount of reports for CSI reports triggered by AP CSI may not be configured / indicated.

[0386] Examples 1-3: UL TCI code points can be defined / configured for not performing PUSCH scheduling, or the corresponding information can be jointly encoded.

[0387] According to the above embodiments, the terminal can update the UL / DL beam (for a specific UL / DL channel / signal) together with the (specific) RS indicated by the SRI or UL TCI field of the corresponding UL DCI.

[0388] The proposed method is for configuring and setting UL DCI parameters for dynamic beam indication / update rather than general PUSCH scheduling. Upon receiving the corresponding UL DCI, the terminal can perform beam indication application / beam update based on the SRI / UL TCI field information of the corresponding DCI without performing PUSCH transmission.

[0389] Terminals receiving Dynamic Beam Indication (DCI) can ignore the PUSCH resource allocation information in the UL DCI. Alternatively, the base station can indicate a specifically defined / conventional value (e.g., reserved code points) in the PUSCH resource allocation related field of the DCI.

[0390] For configuring / setting the UL DCI parameters used to perform such operations, firstly, the UL-SCH for UL data transmission can be left unconfigured / disclosed, and the CSI request field for AP CSI reporting can be set to a value indicating "no trigger" (Example 1-1). Therefore, since PUSCH scheduling is not performed for either UL data or CSI reporting, the terminal can understand that the corresponding UL DCI indication is indicated for the purpose of dynamic beam indication / update.

[0391] Alternatively or additionally, UL-SCH may not be configured / indicated, and the reporting amount may be set to none for CSI triggered by the CSI request field (Examples 1-2). Therefore, since PUSCH scheduling is not performed for UL data and because there is no content to report on the AP CSI report, the terminal can understand that the corresponding ULDCI indication is for the purpose of dynamic beam indication / update. Similar to the case of aperiodic TRS (Tracking RS) and CSI-RS where repetition is set to ON, setting the reporting amount to none means that although a CSI report is triggered, there is no object to report, and this may correspond to the case where AP TRS is triggered or where repetition is set to ON.

[0392] Alternatively or additionally, specific code points indicating no PUSCH scheduling can be defined / configured in the SRI / UL TCI field, or this information can be jointly encoded with the SRI / UL TCI (Examples 1-3). For example, the first N TCI code points can be configured to correspond to 'no PUSCH scheduling'. Alternatively, as an example of joint encoding, the value of the TCI code point can indicate a specific combination of elements of the set {spatial relation, PL RS, 'PUSCH scheduling or not'}. For example, when the TCI code point value is 000, it can indicate the first spatial relation, the first PL RS, and no PUSCH scheduling. Alternatively, when the TCI code point value is 001, it can indicate the first spatial relation, the first PL RS, and the presence of PUSCH scheduling. Here, each bit value of the TCI code point may not correspond to every element.

[0393] Example 1.1

[0394] In embodiments 1-2, where a CSI report is triggered but no content (or quantity) is to be reported, the terminal may perform a CSI-RS-based measurement. Since Dynamic Beam Indication (DCI) is used for UE beam updates, CSI-RS-based measurements may be unnecessary. To prevent the terminal from performing such unnecessary measurements, the associated CSI-RS resource set can be disabled, as in the following embodiments.

[0395] Example 1.1-1: A 1-bit indicator for disabling the relevant CSI resource set can be introduced into the DCI.

[0396] Example 1.1-2: UL TCI code points indicating non-measurement CSI-RS (resources) can be defined / configured, or the corresponding information can be jointly encoded.

[0397] For example, the first N TCI code points of the TCI field can be defined / configured to correspond to no CSI-RS or ignoring CSI-RS. Alternatively, as an example of joint encoding, the value of the TCI code point can indicate a specific combination of elements of the set {Spatial Relationship, PL RS, CSI-RS / CSI Report (Triggered) or Not}. For example, when the TCI code point value is 000, it can indicate that the first spatial relationship, the first PL RS, and no CSI-RS / CSI report are triggered. Alternatively, when the TCI code point value is 001, it can indicate that the first spatial relationship, the first PL RS, and CSI-RS / CSI report are triggered. Here, each bit value of the TCI code point may not correspond to every element.

[0398] Examples 1.1-3: A separate RRC configuration can be provided so that there is no association between CSI-RS resources and CSI reporting settings, or an RRC configuration can be provided so that CSI resource sets are not included in CSI resource settings associated with CSI reporting settings.

[0399] In the above embodiments 1 and 1.1 and their detailed examples for UL DCI used for dynamic beam indication / update, the terminal can change / update the beam without PUSCH transmission. In this case, the base station may not know whether the terminal has successfully received the corresponding DCI, and the terminal can be configured to send ACK ( / NACK) information for the corresponding DCI / PDCCH to the base station.

[0400] As a method for sending ACK / NACK (A / N) or HARQ-ACK information for DCI / PDCCH, SRS transmission can be used / applied. That is, based on the SRS sent from the terminal by the terminal through the SRS request included in the Dynamic Beam Indication UL DCI, the base station can know whether the Dynamic Beam Indication UL DCI has been successfully decoded by the terminal.

[0401] For example, when UL-SCH is not configured / indicated and the CSI Request field in UL-DCI is non-zero (or not configured / indicated) (and / or the CSI reporting setting corresponding to no reporting volume is triggered), the base station can trigger a specific aperiodic SRS transmission via the SRS Request field. The terminal can send information to the base station that the UL DCI for beam indication / update has been successfully received by sending a specific aperiodic SRS triggered by SRS.

[0402] Alternatively, for aperiodic SRS triggered by UL DCI, an ACK indicating that the UL DCI has been successfully received can be sent to the base station by transmitting SRS for a portion of the configured SRS bandwidth (e.g., the lowest half-bandwidth). Conversely, a NACK indicating that the UL DCI has not yet been successfully received can be sent to the base station by transmitting SRS for the remaining bandwidth (e.g., the highest half-bandwidth).

[0403] Alternatively or concurrently, CSI reports triggered by dynamic beamforming / updating the UL DCI can be used for A / N purposes against the UL DCI. In this case, when a new report value with a small overhead, such as a 1-bit indicator, can be defined, and when the corresponding report value is received as a CSI report value, the base station can know that the UE has successfully decoded the UL DCI.

[0404] Example 2

[0405] This embodiment relates to DL DCI for dynamic beam indication / update. The base station can configure the DL DCI according to the example below and send it to the terminal. The terminal can apply beam indication or perform beam update based on the indication via the corresponding DCI without PDSCH scheduling / reception.

[0406] For example, in the case of DL DCI used for dynamic beam (or TCI status) indication / update, PDSCH scheduling can be disabled or PDSCH scheduling information can be ignored.

[0407] Example 2-1: Values ​​corresponding to no resource allocation (no RA) or empty can be defined in the Time Domain Resource Allocation (TDRA) field and / or Frequency Domain Resource Allocation (FDRA) field in the DCI, and these values ​​can be activated.

[0408] Example 2-2: A value corresponding to no resource allocation (no RA) or empty can be defined in the TCI field of DCI, and this value can be configured / indicated.

[0409] Example 2-3: When the TCI field in the DCI indicates a reserved or inactive code point, the terminal can interpret that as no PDSCH scheduling.

[0410] Example 2-4: For a TCI status code point activated via MAC-CE for PDSCH, a specific TCI status code point corresponding to no PDSCH scheduling can be defined, and when a specific TCI status code point is indicated via DCI, the UE can interpret that as no PDSCH scheduling.

[0411] For Embodiment 2 and the detailed example, in order for the base station to check whether the terminal has successfully received the Dynamic Beam Indicator (DL) DCI, the terminal can send A / N information for the DL DCI (or for the PDCCH carrying the DCI). Here, the A / N for the DCI / PDCCH is distinguished from the A / N for the PDSCH. That is, even though there is no PDSCH scheduled via the DCI, the terminal can send an A / N for the DCI / PDCCH instead of the PDSCH. The corresponding A / N information can be generated as HARQ-ACK bits. The generated HARQ-ACK bits can be sent from the terminal to the base station in the form of a HARQ-ACK codebook.

[0412] When a PUCCH resource indicated by the PRI field in the DL DCI exists, HARQ-ACK bits for the DCI / PDCCH can be reported to the base station via the PUCCH resource. Here, the PUCCH transmission timing may not be based on the PDSCH reception timing (e.g., the last received slot of the PDSCH), but rather on the timing of receiving the PDCCH carrying the dynamic beam indication DL DCI. For example, based on the end of slot n of the PDCCH carrying the dynamic beam indication DL DCI, HARQ-ACK information can be sent to the base station in slot n+k (on the PUCCH resource).

[0413] As described above, for HARQ-ACK information transmission in Dynamic Beam Indication DL DCI, a specific HARQ procedure ID can be assigned for this purpose. The field indicating the HARQ procedure ID (or HARQ processor number (HPN)) can be included in the DL DCI. For example, a new HARQ procedure ID, in addition to the IDs of existing HARQ procedures, can be assigned for ACK information transmission in Dynamic Beam Indication DL DCI. For instance, one or more of the existing HARQ procedure ID candidates can be assigned for HARQ-ACK information transmission in Dynamic Beam Indication DL DCI.

[0414] To send A / N or HARQ-ACK information for the DCI / PDCCH, SRS transmission can be used / applied. That is, based on the SRS sent from the terminal according to the SRS request included in the Dynamic Beam Indication (DL) DCI, the base station can know whether the DL DCI has been successfully decoded by the terminal.

[0415] For example, the SRS request field included in the Dynamic Beam Indication / Update DL DCI can trigger a specific aperiodic SRS transmission. By sending a specific aperiodic SRS, the terminal can send information to the base station indicating that it has successfully received (or decoded) the DL DCI used for Dynamic Beam Indication / Update.

[0416] Alternatively or concurrently, for aperiodic SRS triggered by DL DCI, an ACK indicating that the DL DCI has been successfully received can be sent to the base station by transmitting SRS for a portion of the configured SRS bandwidth (e.g., the lowest half-bandwidth). Alternatively, SRS can be transmitted for the remaining bandwidth (e.g., the highest half-bandwidth), and a NACK indicating that the DL DCI has not yet been successfully received can be sent to the base station.

[0417] SRS transmitted in response to the A / N indication of the Dynamic Beam Indicator (DCI / PDCCH) can be transmitted based on SRS timing or based on A / N PUCCH timing. SRS timing can refer to a pre-configured periodic / semi-persistent / aperiodic SRS transmission timing. SRS transmission based on A / N PUCCH timing can mean that, at the time when the A / N PUCCH is transmitted, the SRS is multiplexed with and transmitted along with the A / N PUCCH, or the SRS is transmitted in place of the A / N PUCCH (or with a higher priority than the A / N PUCCH).

[0418] As in Embodiment 2-1 above, for the resource allocation type indicated by TDRA and / or FDRA in the DL DCI, in addition to the existing resource allocation types, no resource allocation (no RA) or empty can also be defined. When the value of the TDRA and / or FDRA field in the DL DCI indicates no RA or empty, the DL DCI indicates that the DL DCI is a DCI used for indicating / updating dynamic beam (or TCI state), and the UE can identify it. That is, when at least one of the TDRA or FDRA in the DL DCI indicates a predefined state (e.g., corresponding to a state of no RA or empty), the UE can disable / ignore PDSCH scheduling based on the corresponding DL DCI.

[0419] Regarding the TDRA field in the DL DCI, when the HARQ-ACK codebook is configured as semi-static or type-1, the position of the ACK information bits in the HARQ-ACK codebook can be determined based on the TDRA. Therefore, the HARQ-ACK feedback scheme may be affected when the TDRA indicates no RA or is empty. Consequently, the state indicating dynamic beamforming / updating of the DL DCI (or indicating that the PDSCH is not scheduled) may not be defined for the TDRA. Therefore, in the HARQ-ACK feedback scheme, the position of the ACK information for the DL DCI in the HARQ-ACK codebook can be determined based on the TDRA in the DL DCI. For example, if the TDRA in the DL DCI indicates a specific resource, but at least one other field in the DL DCI indicates that the DL DCI is dynamic beamforming / updating (or indicates that the PDSCH is not scheduled), it can be interpreted as the PDSCH not actually existing at the position indicated by the TDRA (or a virtual PDSCH existing).

[0420] Examples will be described that form the DCI parameters (or the values ​​of fields in the DCI) that indicate the Dynamic Beam Indication / Update DL DCI (or indicate that the PDSCH is not scheduled). One of the following examples may be applied, or a combination of two or more examples may be applied.

[0421] For example, when the FDRA in the DCI has a specific value indicating a state with no RA or empty, the DCI can correspond to a DCI indicating that it is a Dynamic Beam Indicator / Update DL DCI (or indicating that the PDSCH is not scheduled).

[0422] Alternatively or additionally, when the MCS indicator in the DCI has a specific value, the DCI may correspond to a DCI that indicates it is a Dynamic Beam Indicator / Update DL DCI (or indicates that the PDSCH is not scheduled).

[0423] Alternatively or additionally, when the RV indicator in the DCI has a specific value, the DCI may correspond to a DCI that indicates it is a Dynamic Beam Indicator / Update DL DCI (or indicates that the PDSCH is not scheduled).

[0424] For example, when the MCS indicator (e.g., I_MCS) value is 26 and the RV ID is 1, it can indicate that a transport block (TB) allocated by the corresponding DCI is disabled. One TB or two TBs can be allocated by a DCI. When one or two TBs allocated by a DCI are disabled, the DCI can correspond to the DCI that indicates it is a Dynamic Beam Indicator / Update DL DCI (or indicates that the PDSCH is not scheduled).

[0425] Alternatively or additionally, when the NDI field in the DCI has a specific value, the DCI may correspond to a DCI that indicates it is a dynamic beam indication / update DL DCI (or indicates that the PDSCH is not scheduled).

[0426] For example, when the NDI in the DCI indicates the transmission or reception of new data (i.e., the NDI is switched compared to the previous value), and the MCS indicates a reservation state corresponding to a retransmission, the DCI can correspond to a DCI indicating that it is a Dynamic Beam Indication / Update DL DCI (or indicating that the PDSCH is not scheduled).

[0427] As described above, a DCI can correspond to a DCI indicating that it is a Dynamic Beam Indication / Update DL DCI (or indicating that the PDSCH is not scheduled) when each of at least one of the fields FDRA, RV, MCS, NDI, or HPN in the DCI has a specific (e.g., the same or different) value. Additionally, a DCI can correspond to a DCI indicating that it is a Dynamic Beam Indication / Update DL DCI (or indicating that the PDSCH is not scheduled) by combining the FDRA, RV, MCS, and NDI (or FDRA, RV, MCS, NDI, and HPN) fields in the DCI with one or more other fields in the DCI.

[0428] As described above, the method of indicating that the corresponding DL DCI is a Dynamic Beam Indicator / Updated DLDCI (or indicating that the PDSCH is not scheduled) based on various fields in the DL DCI can also be applied to UL DCI. For example, based on at least one of the FDRA, RV, MCS, NDI, HPN or other fields in the UL DCI, the UL DCI can be indicated as a Dynamic Beam Indicator / Updated ULDCI (or the PUSCH is not scheduled).

[0429] Alternatively or additionally, when a new TCI state pool associated with a beam indication field (e.g., TCI field) in the DCI is activated, the DCI can be indicated as a dynamic beam indication / updated DCI (or as a data channel not scheduled). In this case, instead of indicating the beam to be changed / updated through the state of an existing TCI field in the DCI, X bits of another field in the DCI (e.g., antenna port field) can be used / interpreted as indicating a specific TCI state of the new TCI state pool. For example, an additional new TCI state pool in addition to the existing 128 TCI state pools can be RRC configured and activated by the MAC CE. When the new TCI state pool is activated, the antenna port field in the DCI can indicate the TCI state in the new TCI state pool. Alternatively, when the new TCI state pool is not activated, the TCI state field in the DCI can indicate the TCI state in an existing TCI state pool.

[0430] Alternatively or additionally, when multiple CORESET pool indexes are configured, a new TCI state pool can be configured for each CORESET pool index.

[0431] Alternatively or additionally, a specific state of the TCI field in the DCI can indicate that the DCI is a dynamic beamforming / updating DCI (or indicate that the data channel is not scheduled). When the TCI field indicates a specific state, the terminal can apply dynamic beamforming or updating beamforming without data channel transmission / reception (Example 2-2). Alternatively, it can be configured such that for TCI code points mapped to a specific state indicated by the TCI field, the data channel is not scheduled (Example 2-3).

[0432] For example, the first N TCI code points of the TCI field can be defined / configured to correspond to a no-data channel (e.g., no PDSCH) or to omit RA. Alternatively, as an example of joint coding, the value of the TCI code point can indicate a specific combination of elements of the set {spatial relation, PL RS, PDSCH scheduling or not}. For example, when the TCI code point value is 000, it can indicate the first spatial relation, the first PL RS, and no PDSCH scheduling. Alternatively, when the TCI code point value is 001, it can indicate the first spatial relation, the first PL RS, and PDSCH scheduling. Here, each bit value of the TCI code point may not correspond to every element.

[0433] According to embodiments 2-4, dynamic beam indication / update can be supported by updating / activating TCI status code points via MAC CE. For example, a specific TCI status code point indicating dynamic beam indication / update can be activated via MAC CE. Before the MAC CE for activating a specific TCI code point is configured / indicated to the terminal, the beams used for PDSCH scheduling and corresponding PDSCH reception can be indicated to the terminal based on DCI. When the MAC CE for activating a specific TCI code point is configured / indicated to the terminal, the terminal can dynamically change / update the beams for (all) UL / DL channels / signals of the terminal without performing PDSCH scheduling based on DCI.

[0434] According to Embodiment 2-2, the DCI can be continuously indicated as a dynamic beam indication / updating DL DCI (or indicating that the PDSCH is not scheduled) by a specific state of one or more fields in the DL DCI. However, according to Embodiment 2-4, existing operations (i.e., the DCI indicates PDSCH scheduling and the TCI state for receiving the corresponding PDSCH) and new operations according to this disclosure (i.e., the DCI does not schedule the PDSCH and dynamically indicates the beam) can be distinguished and applied by the MAC CE used to activate a specific TCI code point. Additionally, flexibility can be supported, such as guaranteeing a greater number of available code points in the TCI state field for PDSCH beam indication before receiving the MAC CE used to activate a specific TCI code point.

[0435] Example 3

[0436] According to this embodiment, DL DCI can schedule PDSCH for dynamic beam indication / update, but can transmit specific sequences (or data) instead of TB through the scheduled PDSCH. Specific sequences can be pre-configured / pre-indicated between the base station and the terminal, or can be predefined without signaling between the base station and the terminal.

[0437] The terminal can send HARQ-ACK information for a PDSCH that includes a specific sequence, and apply dynamic beam indication or update the beam based on the beam indicator (e.g., TCI state) included in the DLDCI that schedules the PDSCH.

[0438] For HARQ-ACK information transmissions for PDSCHs (i.e., PDSCHs including a specific sequence) scheduled by the Dynamic Beam Indication DL DCI as described above, a specific HARQ procedure ID can be assigned for this purpose. For example, a field indicating the HARQ procedure ID or HARQ procedure number (HPN) can be included in the DL DCI. For example, in addition to the IDs of existing HARQ procedures, new HARQ procedure IDs can be assigned for the transmission of HARQ-ACK information for PDSCHs scheduled by the Dynamic Beam Indication DL DCI. For example, one or more of the existing HARQ procedure ID candidates can be assigned for the transmission of HARQ-ACK information for PDSCHs scheduled by the Dynamic Beam Indication DL DCI.

[0439] Unlike Embodiments 1 and 2, where the DL / UL DCI for Dynamic Beam Indication / Update does not schedule PDSCH / PUSCH, in Embodiment 3, the DL DCI for Dynamic Beam Indication / Update can schedule PDSCH. Here, unlike the PDSCH scheduled by the general DL DCI carrying data (or TB) delivered to the terminal, the PDSCH scheduled by the DL DCI for Dynamic Beam Indication / Update can carry only a specific sequence, or include a specific sequence (i.e., carrying a specific sequence and other data). The specific sequence can be a sequence with a predetermined size (e.g., length L) (e.g., a sequence of length L where all bits are 0). When the terminal receives a PDSCH including a specific sequence, the terminal can send a HARQ A / N for the corresponding PDSCH.

[0440] In Embodiment 3, there is no need to redesign the HARQ-ACK feedback scheme for the DCI / PDCCH used for dynamic beam indication / update, and the existing HARQ-ACK feedback scheme based on the PDSCH receive timing can be applied as is. However, in Embodiment 3, due to the involvement of PDSCH scheduling / allocation, the overhead and latency may be greater than in Embodiments 1 and 2, which do not involve PDSCH / PUSCH scheduling / allocation.

[0441] In addition to a specific sequence, the PDSCH scheduled by the DL DCI for dynamic beam indication / update can also include beam indication information. Therefore, dynamic beam indication / update can be performed using a backoff DCI (e.g., DCI format 1_0) that does not include a beam indication field (e.g., TCI field) and a non-backoff DCI format (e.g., DCI formats 1_1, 1_2, etc.) that includes a beam indication field (e.g., TCI field).

[0442] For example, by using a specific HARQ procedure ID (e.g., when the HPN field in the DL DCI has a specific value), the terminal can be informed that the fallback DL DCI is for dynamic beam indication / update purposes. Additionally or alternatively, instead of (or in addition to) the HARQ procedure ID or HARQ procedure number, by combining other fields such as FDRA, RV, MCS, NDI, etc., with specific values, the terminal can be informed that the corresponding DL DCI is for dynamic beam indication / update purposes. Dynamic beam indication can be applied to the UE by including a specific sequence and beam indication information in the PDSCH scheduled by the fallback DL DCI.

[0443] For example, a specific sequence can be 8 bits long, and within an active TCI state, that specific TCI state can be indicated by the bit value of that specific sequence. In other words, the mapping between the bit value of a specific sequence and TCI state candidates can be configured. For instance, when the bit value of a specific sequence is 00000001, the lowest TCI state among the active DL TCI states can be indicated, and dynamic beam indication application or beam updates can be performed at the terminal based on the indicated lowest TCI state, and HARQ-ACK feedback for the PDSCH can be sent.

[0444] Figure 16 This is a diagram illustrating a signaling process according to an embodiment of the present disclosure.

[0445] Figure 16 Examples show that can be applied Figure 15 Examples of signaling between a base station and a terminal (UE) as described in Examples 1, 2, 3, and / or their detailed examples. Here, the UE / base station is merely an example, and it can be used as follows: Figure 17 The various devices described herein will be replaced. A base station may correspond to a base station comprising multiple TRPs or a cell comprising multiple TRPs. Figure 16 This is for the sake of convenience of description and does not limit the scope of this disclosure. Additionally, omissions may be made depending on the circumstances and / or settings. Figure 16 Some of the steps are shown. Additionally, in Figure 16 In the operation of the base station / UE, the above beam management and uplink / downlink transmission / reception operations can be referenced / used.

[0446] The UE can receive configuration information from the base station (S105). The configuration may include system information (SI), scheduling information, beam management (BM) related settings (e.g., DL BM-related CSI-ResourceConfig IE, NZP CSI-RS resource set IE, etc.) and / or base station-related configuration information (e.g., TRP configuration). For example, the configuration may include information related to the reconfiguration / update of RS information used for spatial relationship (e.g., QCL relationship) assumptions (e.g., information related to whether an instruction / timing for reconfiguration / update is performed, etc.). The configuration can be sent through a higher layer (e.g., RRC or MAC CE). Alternatively, if the configuration information is predefined or preconfigured, the corresponding steps can be omitted.

[0447] For example, based on Figure 15 In the examples described above, such as Embodiments 1, 2, 3, and / or their detailed examples, the configuration may include information about the TCI state, QCL RS, and / or DMRS ports. For example, the TCI state may include RS information for spatial relationship (e.g., QCL relationship) assumptions. For example, the configuration may include QCL-related configuration information for DL ​​channels (e.g., PDCCH / PDSCH) / UL channels (e.g., PUSCH / PUCCH). For example, the configuration may include information indicating changes / updates to QCL-related information (or RS information for spatial relationship assumptions, etc.) for downlink channels (e.g., PDCCH / PDSCH).

[0448] For example, in step S105 above, by UE ( Figure 17 100 / 200 in the base station ( Figure 17 The operation of receiving configuration in 200 / 100 can be described below. Figure 17 This is achieved through a device. For example, refer to... Figure 17 One or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc., to receive configurations, and one or more transceivers 106 can receive configurations from the base station.

[0449] The UE can receive control information from the base station (S110). Control information can be received via a control channel (e.g., PDCCH). For example, the control information can be DL DCI / UL DCI. For example, the control information may include scheduling information for downlink data channels (e.g., PDSCH) / uplink channels (e.g., PUCCH / PUSCH), etc. For example, based on... Figure 15In the examples described above, such as Embodiments 1, 2, 3, and / or their detailed examples, the control information may include information about TCI states, QCL RS, and / or DMRS ports. For example, one or more TCI states may be configured in the TCI state field of the control information (e.g., DCI) for DMRS ports associated with DL data channels (e.g., PDSCH) / UL channels (e.g., PUCCH / PUSCH). For example, the TCI state may include RS information for spatial relationship (e.g., QCL relationship) assumptions.

[0450] For example, in step S110 above, by UE ( Figure 17 100 / 200 in the base station ( Figure 17 The operation of receiving control information (200 / 100) can be described below. Figure 17 This is achieved through a device. For example, refer to... Figure 17 One or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc., to receive control information, and one or more transceivers 106 can receive control information from the base station.

[0451] Despite Figure 16 Not shown, but the UE can send HARQ-ACK information for control information (DL DCI / UL DCI) or channels carrying control information (e.g., PDCCH). For example, when the control information is a DCI used for dynamic space parameter indication (e.g., in... Figure 15 In the example where the third information indicates no data channel scheduling), after sending the HARQ-ACK information for the corresponding DCI (e.g., according to the... Figure 15 In the example, after sending the HARQ-ACK information based on the position of the ACK information in the HARQ-ACK codebook determined by the second information, after a predetermined time, the UE can, based on the spatial parameters indicated by the corresponding DCI (e.g., in...), send the HARQ-ACK information. Figure 15 The example uses spatial parameters determined based on the first information to perform data transmission / reception (S115), which will be described later. That is, the UE can report to the base station whether the spatial parameters of the UL / DL channel / signal have been changed / updated by the DCI based on the dynamic spatial parameters.

[0452] The UE can receive data from or send data to the base station (S115). Data can be received via a downlink channel (e.g., PDCCH / PDSCH) or sent via an uplink channel (e.g., PUCCH / PUSCH). For example, data can be scheduled based on control information or based on... Figure 16 Separate control information, not shown, is used to schedule data.

[0453] Additionally, data can be sent / received based on the information configured / indicated in steps S105 / S110. For example, based on the information configured / indicated in steps S105 / S110, the UE can perform channel estimation / compensation and can send / receive data. Figure 15 The above examples of embodiments 1, 2, 3 and / or their detailed examples can be configured to receive spatial relational RS (e.g., QCL type D RS).

[0454] For example, based on the spatial relationship information of the uplink channel (e.g., PUCCH / PUSCH) transmitted by the UE, the spatial relationship-related RS (e.g., QCL type D RS) used for receiving data (downlink channel) can be configured / changed. For example, based on the usage / content of the uplink channel (e.g., SR / HARQ-ACK / CSI, etc.), the spatial relationship-related RS (e.g., QCL type D RS) used for receiving data (downlink channel) can be configured (e.g., QCL type D RS). For example, the spatial relationship-related RS (e.g., QCL type D RS) used for receiving data (downlink channel) can be configured / updated / changed for each CORESET / SS. For example, based on whether the TCI field is included / present in the DCI, it can be determined whether to apply the QCL RS indicated by the TCI or follow the spatial relationship information of the uplink channel.

[0455] For example, based on the spatial relationship information of the uplink channel (e.g., PDCCH / PDSCH) transmitted by the UE, the spatial relationship-related RS (e.g., QCL type D RS) used for receiving (downlink channel) data can be configured / changed. For example, based on the usage / content of the downlink channel (e.g., SR / HARQ-ACK / CSI, etc.), the spatial relationship-related RS (e.g., QCL type D RS) used for transmitting (uplink channel) data can be configured (e.g., QCL type D RS). For example, the spatial relationship-related RS (e.g., QCL type D RS) used for transmitting (uplink channel) data can be configured / updated / changed for each CORESET / SS. For example, based on whether the TCI field is included / present in the DCI, it can be determined whether to apply the QCL RS indicated by the TCI or follow the spatial relationship information of the downlink channel.

[0456] For example, in step S115 above, by UE ( Figure 17 100 / 200 in the middle) to the base station ( Figure 17 (200 / 100) Sending data / From base station ( Figure 17 The operation of receiving data (200 / 100) can be described below. Figure 17 This is achieved through a device. For example, refer to... Figure 17One or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc., to send / receive data, and one or more transceivers 106 can send data to / receive data from the base station.

[0457] As mentioned above, the signaling and operations of the aforementioned base station / UE (e.g., Figure 15 Examples of embodiments 1, 2, 3 and / or detailed examples thereof may be provided by the examples to be described below. Figure 17 This can be achieved through a device. For example, a base station (e.g., TRP1 / TRP2) may correspond to a first wireless device, and a UE may correspond to a second wireless device, and in some cases, the reverse may also be considered.

[0458] For example, the signaling and operations of the aforementioned base station / UE (e.g., Figure 15 Examples of embodiments 1, 2, 3 and / or detailed examples thereof can be derived from... Figure 17 One or more processors (e.g., 102, 202) process, and the signaling and operations of the aforementioned base station / UE (e.g., Figure 15 Examples of embodiments 1, 2, 3 and / or their detailed examples) can be used to drive Figure 17 The instructions / program (e.g., instructions, executable code) of at least one processor (e.g., 102 and 202) are stored in memory (e.g., Figure 17 In one or more memories (104 and 204).

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

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

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

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

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

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

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

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

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

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

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

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

[0471] Here, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include narrowband Internet of Things (IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. Here, in examples, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (Enhanced Machine-Type Communication). For example, LTE-M technology may be implemented in at least any of the following standards: 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and is not limited to the aforementioned names. Alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of this disclosure may include at least any one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and it is not limited to the aforementioned names. In the example, ZigBee technology can generate a PAN (Personal Area Network) associated with small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0472] Industrial applicability

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

Claims

1.A communication method, comprising: receiving, by a terminal from a base station, a downlink control information (DCI) for transmission configuration indication (TCI) state update without scheduling a physical downlink shared channel (PDSCH) reception, wherein the DCI includes information related to time domain resource assignment; based on the information related to time domain resource assignment, transmitting, by the terminal to the base station, hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the DCI for TCI state update without scheduling the PDSCH reception; and after transmitting the HARQ-ACK information, applying, by the terminal, at least one TCI state indicated by the DCI for TCI state update without scheduling the PDSCH reception. 2.The method of claim 1, wherein: a location of the HARQ-ACK information in a HARQ-ACK codebook is based on the information related to time domain resource assignment included in the DCI for TCI state update without scheduling the PDSCH reception. 3.The method of claim 2, wherein: the HARQ-ACK codebook is configured as type-1 or semi-static. 4.The method of claim 1, wherein: at least one of a frequency domain resource assignment (FDRA) field, a redundancy version (RV) field, a modulation and coding scheme (MCS) field, or a new data indicator (NDI) field is set to a specific value for the DCI for TCI state update without scheduling the PDSCH reception. 5.The method of claim 4, wherein: each of the at least one of the FDRA field, the RV field, the MCS field, or the NDI field is set to a specific value, respectively, for the DCI for TCI state update without scheduling the PDSCH reception. 6.The method of claim 1, wherein: the DCI for TCI state update without scheduling the PDSCH reception indicates at least one of at least one TCI state or at least one downlink TCI state. 7.The method of claim 1, wherein: the DCI is based on a DCI format 1_1 or 1_2. 8.A terminal, comprising: at least one transceiver; and at least one processor connected to the at least one transceiver, wherein the at least one processor is configured to: receive, by the transceiver from a base station, a downlink control information (DCI) for transmission configuration indication (TCI) state update without scheduling a physical downlink shared channel (PDSCH) reception, wherein the DCI includes information related to time domain resource assignment; based on the information related to time domain resource assignment, transmit, by the transceiver to the base station, hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the DCI for TCI state update without scheduling the PDSCH reception; and after transmitting the HARQ-ACK information, apply, by the terminal, at least one TCI state indicated by the DCI for TCI state update without scheduling the PDSCH reception. At least one TCI state indicated by the DCI for TCI state update without scheduling the PDSCH reception is applied after transmitting the HARQ-ACK information. 9.A base station comprising: at least one transceiver; and at least one processor connected to the at least one transceiver, wherein the at least one processor is configured to: transmit, by the transceiver, a downlink control information (DCI) for transmission configuration indication (TCI) state update without scheduling a physical downlink shared channel (PDSCH) reception to a terminal, the DCI including information related to time domain resource assignment; and receive, by the transceiver, a hybrid automatic repeat request-acknowledgement (HARQ-ACK) information for the DCI for TCI state update without scheduling the PDSCH reception from the terminal based on the information related to time domain resource assignment; wherein at least one TCI state indicated by the DCI for TCI state update without scheduling the PDSCH reception is applied to the terminal after transmitting the HARQ-ACK information from the terminal.

Images