Methods and apparatus for uplink transmission and reception in wireless communication systems

Abstract

Methods and apparatus for uplink transmission and reception in a wireless communication system are disclosed. A method for performing a terminal-initiated uplink transmission in a wireless communication system according to embodiments of this disclosure may include the steps of: receiving configuration information from a base station including one or more of a plurality of spatial parameter candidates or a plurality of path loss reference signal (PLRS) candidates, wherein the candidates are associated with each of one or more transmission opportunities for uplink transmission; and performing uplink transmission to the base station at each of the one or more transmission opportunities based on a triggering event for uplink transmission and based on one spatial parameter from the plurality of spatial parameter candidates and one or more of one PLRS from the plurality of PLRS candidates, wherein the plurality of spatial parameter candidates or one or more of the plurality of PLRS candidates are configured to map to an uplink transmission resource of the triggering event, or are configured to map to a plurality of uplink transmission resources of the triggering event.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for transmitting and receiving uplinks in wireless communication systems. Background Technology

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

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

[0004] Technical issues

[0005] The technical problem of this disclosure is to provide a method and apparatus for uplink transmission and reception initiated by a terminal in a wireless communication system.

[0006] An additional technical problem of this disclosure is to provide a method and apparatus for configuring spatial parameters and / or path loss reference signals for UE-initiated uplink transmissions in a wireless communication system.

[0007] An additional technical problem of this disclosure is to provide a method and apparatus for configuring multiple spatial parameter candidates and / or multiple path loss reference signal candidates in a wireless communication system for uplink transmission initiated by a UE at a specific transmission timing, and for performing uplink transmission and reception at the specific transmission timing by applying one of the spatial parameters and / or one path loss reference signal.

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

[0009] Technical solution

[0010] According to one aspect of this disclosure, a method for performing a terminal-initiated uplink transmission in a wireless communication system includes: receiving configuration information from a base station, the configuration information including at least one of a plurality of spatial parameter candidates or a plurality of path loss reference signal (PLRS) candidates associated with each of at least one transmission timing for uplink transmission; and performing uplink transmission to the base station at each of the at least one transmission timing based on a triggering event for uplink transmission, based on at least one of a spatial parameter among the plurality of spatial parameter candidates or a PLRS among the plurality of PLRS candidates, and at least one of the plurality of spatial parameter candidates or the plurality of PLRS candidates can be configured to map to an uplink transmission resource of the triggering event, or can be configured to map to a plurality of uplink transmission resources of the triggering event.

[0011] According to another aspect of this disclosure, a method for a base station to receive an uplink transmission initiated by a terminal in a wireless communication system includes: sending configuration information to the terminal, the configuration information including at least one of a plurality of spatial parameter candidates or a plurality of path loss reference signal (PLRS) candidates associated with each of at least one transmission timing for uplink transmission; and receiving the uplink transmission from the terminal at each of the at least one transmission timing based on a triggering event for uplink transmission, based on at least one of a spatial parameter among the plurality of spatial parameter candidates or a PLRS among the plurality of PLRS candidates, and the plurality of spatial parameter candidates or at least one of the plurality of PLRS candidates can be configured to map to an uplink transmission resource of the triggering event, or can be configured to map to a plurality of uplink transmission resources of the triggering event.

[0012] Beneficial effects

[0013] According to this disclosure, in addressing the technical problem of this disclosure, a method and apparatus for uplink transmission and reception initiated by a terminal in a wireless communication system can be provided.

[0014] According to this disclosure, a method and apparatus for configuring spatial parameters and / or path loss reference signals for UE-initiated uplink transmissions in a wireless communication system can be provided.

[0015] According to this disclosure, a method and apparatus may be provided for configuring multiple spatial parameter candidates and / or multiple path loss reference signal candidates in a wireless communication system for uplink transmission initiated by a UE at a specific transmission timing, and for performing uplink transmission and reception at a specific transmission timing by applying one of the spatial parameters and / or one path loss reference signal.

[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, together with the detailed description, describe the technical features of the disclosure.

[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 The diagram illustrates a method for transmitting multiple TRPs in a wireless communication system to which this disclosure can be applied.

[0025] Figure 8 This diagram illustrates beam fault recovery operations of a Pcell in a wireless communication system to which the present disclosure can be applied.

[0026] Figure 9 This is a flowchart describing an uplink transmission method initiated by a UE according to embodiments of the present disclosure.

[0027] Figure 10 This is a flowchart describing an uplink reception method initiated by a UE according to embodiments of the present disclosure.

[0028] Figure 11 It is a diagram used to describe the transmission configuration for UE-initiated uplink transmissions according to this disclosure.

[0029] Figure 12 This is a diagram illustrating the signaling process between a base station and a terminal in an uplink transmission and reception method according to an embodiment of the present disclosure.

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

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

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

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

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

[0035] 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”.

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

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

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

[0039] The following descriptions can be used for 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, 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.

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

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

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

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

[0044] - BM: Beam Management

[0045] - CQI: Channel Quality Indicator

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

[0047] - CSI: Channel State Information

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

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

[0050] - DMRS: Demodulation Reference Signal

[0051] -FDM: Frequency Division Multiplexing

[0052] - FFT: Fast Fourier Transform

[0053] - IFDMA: Interleaved Frequency Division Multiple Access

[0054] - IFFT: Inverse Fast Fourier Transform

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

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

[0057] - MAC: Media Access Control

[0058] - NZP: Non-zero power

[0059] - OFDM: Orthogonal Frequency Division Multiplexing

[0060] - PDCCH: Physical Downlink Control Channel

[0061] - PDSCH: Physical Downlink Shared Channel

[0062] - PMI: Precoding Matrix Indicator

[0063] - RE: Resource Elements

[0064] - RI: Rank Indicator

[0065] - RRC: Radio Resource Control

[0066] - RSSI: Received Signal Strength Indicator

[0067] - Rx: Receive

[0068] - QCL: Quasi-co-location

[0069] - SINR: Signal-to-Interference-Noise Ratio

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

[0071] - TDM: Time Division Multiplexing

[0072] - TRP: Transmitting and Receiving Point

[0073] - TRS: Tracking Reference Signal

[0074] - Tx: Send

[0075] - UE: User Equipment

[0076] - ZP: Zero Power

[0077] Overall System

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

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

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

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

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

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

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

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

[0086] [Table 1]

[0087]

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

[0089] [Table 2]

[0090]

[0091] 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 10ms. 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 start 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.

[0092] [Table 3]

[0093]

[0094] [Table 4]

[0095]

[0096] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3. One subframe can include 4 time slots. For example... 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.

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

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

[0099] refer to Figure 3 The diagram illustrates the resource grid configuration with N in the frequency domain. RB μ N sc RB There are 14.2 subcarriers, and one subframe is configured with 14.2 μ The number of OFDM symbols is not limited to this. In an NR system, the transmitted signal consists of 2 OFDM symbols. μ N symb （μ） Each OFDM symbol and configuration has N RB μ N sc RB It is described by one or more resource grids of N subcarriers. Here, N RB μ ≤ N RB max,μ N RB max,μ This represents the maximum transmission bandwidth, which may differ between uplink and downlink, and between parameter sets. In this case, each μ and antenna port p can be configured with a resource grid. Each element of the resource grid used for μ and antenna port p is called a resource element and is 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, index pairs (k, l) are 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.

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

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

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

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

[0104] [Equation 1]

[0105]

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

[0107] [Equation 2]

[0108]

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

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

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

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

[0113] In NR systems, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip for the entire CC 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 Part (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

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

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

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

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

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

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

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

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

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

[0123] [Table 5]

[0124]

[0125] 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, Coding, and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), information related to HARQ (Hybrid Automatic Repeat and Request) (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and control information included in each DCI format can be predefined. 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 Coding Scheme Cell RNTI).

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

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

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

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

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

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

[0132] Operations related to multiple TRPs

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

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

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

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

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

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

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

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

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

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

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

[0144] Alternatively, the UE can be indicated via separate signaling whether it is an MTRP scheme based on a single DCI or an MTRP scheme based on multiple DCIs. In the example, for a serving cell, multiple CRS (Cell Reference Signal) patterns can be indicated to the UE for MTRP operation. In this case, the PDSCH rate matching for CRS can differ depending on whether the MTRP scheme is based on a single DCI or an MTRP scheme based on multiple DCIs (because the CRS patterns are different).

[0145] In the following, the CORESET group ID described / mentioned in this disclosure may refer to index / identification information (e.g., ID, etc.) used to distinguish CORESETs for each TRP / panel. Alternatively, a CORESET group may be a group / union of CORESETs distinguished by index / identification information (e.g., ID) / CORESET group ID, etc., used to distinguish CORESETs for each TRP / panel. In the example, the CORESET group ID may be specific index information defined in the CORESET configuration. In this case, the CORESET group can be configured / indicated / defined by an index defined in the CORESET configuration for each CORESET. Additionally / alternatively, the CORESET group ID may refer to index / identification information / indicators, etc., used to distinguish / identify CORESETs associated with each TRP / panel configuration. In the following, the CORESET group ID described / mentioned in this disclosure may be replaced by a specific index / specific identification information / specific indicator used to distinguish / identify CORESETs associated with each TRP / panel configuration. The CORESET group ID can be configured / indicated to the terminal via higher-level signaling (e.g., RRC signaling) / L2 signaling (e.g., MAC-CE) / L1 signaling (e.g., DCI), i.e., a specific index / specific identification information / specific indicator used to distinguish / identify CORESETs configured / associated with each TRP / panel. In the example, it can be configured / indicated that PDCCH detection will be performed on a per-TRP / panel basis (i.e., per TRP / panel belonging to the same CORESET group) at the corresponding CORESET group level. Additionally / alternatively, it can be configured / indicated that uplink control information (e.g., CSI, HARQ-A / N (ACK / NACK), SR (scheduling request)) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) are separated and managed / controlled on a per-TRP / panel basis (i.e., per TRP / panel belonging to the same CORESET group) at the corresponding CORESET group level (i.e., per TRP / panel belonging to the same CORESET group). Additional / alternative locations can manage HARQ A / N (processing / retransmission) for PDSCH / PUSCH, etc., scheduled per TRP / panel, according to the corresponding CORESET group (i.e., by TRP / panel belonging to the same CORESET group).

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

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

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

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

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

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

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

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

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

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

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

[0157] 1-a) Method 1a

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

[0159] - Use a single codeword with one RV across all spatial layers or all layer sets. Regarding UEs, map different coded bits to different layers or layer sets using the same mapping rules.

[0160] 1-b) Method 1b

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

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

[0163] 1-c) Method 1c

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

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

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

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

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

[0169] 2-a) Method 2a

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

[0171] 2-b) Method 2b

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

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

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

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

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

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

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

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

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

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

[0182] The MTRP URLLC is described below.

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

[0184] Furthermore, in this disclosure, UL MTRP-URLLC refers to multiple TRPs receiving the same data / UCI (uplink control information) from any UE using different layer / time / frequency resources. For example, TRP 1 receives the same data / DCI from the UE in resource 1, and TRP 2 receives the same data / DCI from the UE in resource 2, sharing the received data / DCI via a backhaul link connected between the TRPs. UEs configured with the UL MTRP-URLLC transmission method transmit the same data / UCI using different layer / time / frequency resources. In this case, the base station configures the UE for which Tx beam and which Tx power (i.e., UL TCI state) should be used in the layer / time / frequency resources for transmitting the same data / DCI. For example, when transmitting the same data / UCI in resource 1 and resource 2, the UL TCI state used in resource 1 and the UL TCI state used in resource 2 can be configured. This UL MTRP URLLC can be applied to PUSCH / PUCCH.

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

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

[0187] The MTRP eMBB is described below.

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

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

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

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

[0192] Furthermore, in this disclosure, when multiple base stations (i.e., MTRPs) repeatedly transmit the same PDCCH, this can refer to transmitting the same DCI through multiple PDCCH candidates, and it can also refer to multiple base stations repeatedly transmitting the same DCI. Here, the same DCI can refer to two DCIs with the same DCI format / size / payload. Alternatively, although two DCIs have different payloads, they can be considered the same DCI when the scheduling result is the same. For example, the TDRA (Time Domain Resource Allocation) field of the DCI determines the time slot / symbol position of the data and the time slot / symbol position of A / N (ACK / NACK) relatively based on the timing of the DCI reception. Therefore, if a DCI received at n timings and a DCI received at n+1 timings notify the UE of the same scheduling result, the TDRA fields of the two DCIs are different, and therefore, the DCI payloads are different. The number of repetitions R can be directly indicated by the base station or mutually agreed upon by them to the UE. Alternatively, even though two DCIs have different payloads and different scheduling results, they can be considered the same DCI if the scheduling result of one DCI is a subset of the scheduling result of the other DCI. For example, when the same data is repeatedly transmitted N times via TDM, DCI 1, received before the first data, indicates N data repetitions, and DCI 2, received after the first data and before the second data, indicates N-1 data repetitions. The scheduled data of DCI 2 becomes a subset of the scheduled data of DCI 1, and since the two DCIs are scheduling the same data, they can be considered the same DCI in this case.

[0193] Additionally, in this disclosure, when multiple base stations (i.e., MTRPs) partially transmit the same PDCCH, it means that a DCI is transmitted through a PDCCH candidate, but TRP 1 transmits some resources that define such a PDCCH candidate, and TRP 2 transmits the remaining resources.

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

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

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

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

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

[0199] Uplink power control

[0200] In wireless communication systems, it may be necessary to increase or decrease the transmission power of terminals (e.g., user equipment (UE)) and / or mobile devices as needed. Therefore, controlling the transmission power of terminals and / or mobile devices can be referred to as uplink power control. In the example, transmission power control methods can be applied to meet the requirements of the base station (e.g., gNB, eNB, etc.) (e.g., SNR (signal-to-noise ratio), BER (bit error rate), BLER (block error rate), etc.).

[0201] As described above, power control can be performed using both open-loop and closed-loop power control methods.

[0202] Specifically, open-loop power control refers to a method of controlling transmission power without feedback from the transmitting device (e.g., base station, etc.) to the receiving device (e.g., terminal, etc.) and / or from the receiving device to the transmitting device. In the example, the terminal can receive a specific channel / signal (pilot channel / signal) from the base station and use it to estimate the strength of the received power. Subsequently, the terminal can control the transmission power by using the estimated strength of the received power.

[0203] In contrast, closed-loop power control refers to a method of controlling transmission power based on feedback from the transmitting device to the receiving device and / or from the receiving device to the transmitting device. In the example, the base station receives a specific channel / signal from the terminal and determines the optimal power level for the terminal based on power levels, SNR, BER, BLER, etc., measured by the received specific channel / signal. The base station delivers information about the determined optimal power level (i.e., feedback) to the terminal via a control channel, etc., and the corresponding terminal can control its transmission power using the feedback provided by the base station.

[0204] For ease of description, the power control method will be described below based on the case where the terminal performs PUCCH transmission. Of course, the corresponding method can also be extended and applied to other uplink channels supported by the wireless communication system.

[0205] Specifically, by using the PUCCH power control adjustment state based on index 1, for PUCCH transmission in the active uplink bandwidth portion (UL BWP) of carrier index f of serving cell (e.g., PCell or SCell) index c, the terminal can determine the PUCCH transmission timing index i's PUCCH transmission power P based on the following Equation 3. PUCCH,b,f,c (i,q u ,q d ,l)(dBm)。

[0206] [Equation 3]

[0207]

[0208] In equation 3, q u This represents the index used for open-loop power control parameters (e.g., Po, etc.), and each cell can be configured with up to eight parameter values. Index q -d An index representing the DL RS resources used for path loss (PL) measurement (e.g., PL b,f,c (q d Each cell can be configured with up to four measurements. Index l represents the index used for the closed-loop power control process, and each cell can be configured with up to two processes.

[0209] Specifically, due to Po (e.g., P) O_PUCCH,b,f,c (q u The Po value is a parameter broadcast as part of system information and can therefore represent the target received power on the receiving side. The appropriate Po value can be configured by considering factors such as terminal throughput, cell capacity, noise, and / or interference. Additionally, P... CMAX,f,c (i) can represent the configured terminal transmission power. In the example, the configured terminal transmission power can correspond to "the configured maximum UE output power". Additionally, M PUCCH RB,b,f,c (i) can represent the bandwidth of PUCCH resource allocation, which is expressed as the number of resource blocks (RBs) based on the PUCCH transmission timing at subcarrier intervals (μ). Additionally, the increment function (e.g., Δ) can be configured by considering the PUCCH format (e.g., PUCCH formats 0, 1, 2, 3, 4, etc.). P_PUCCH (F), Δ TF,b,f,c (i) Additionally, g related to the PUCCH power control adjustment state can be configured or indicated based on the TPC command field of the DCI detected or received by the terminal (e.g., DCI format 1_0, 1_1, 2_2, etc.). b,f,c (i,l) .

[0210] In this case, specific RRC parameters (such as PUCCH-SpatialRelationInfo) and / or specific MAC-CE commands (such as PUCCH spatial relation activation / deactivation) can be used to activate or deactivate the PUCCH resource with the aforementioned index q. u q d The connection between and l. In the example, the PUCCH spatial relationship activation / deactivation command in MAC-CE can activate or deactivate the PUCCH resource and the aforementioned index q based on the RRC parameter (PUCCH-SpatialRelationInfo). u q d The connection between q and l. In other words, the above index q u q d The PUCCH transmission power control, etc., can be associated with beams, panels, and / or spatial domain transmission filters based on specific information. This allows for PUCCH transmission power control at the beam, panel, and / or spatial domain transmission filter level.

[0211] The parameters and / or information for the PUCCH power control described above can be configured individually (i.e., independently) for each BWP. In this case, the corresponding parameters and / or information can be configured or indicated via higher-level signaling (e.g., RRC signaling, MAC-CE, etc.) and / or DCI, etc. In the example, the parameters and / or information for PUCCH power control can be sent via RRC signaling PUCCH-ConfigCommon, PUCCH-PowerControl, etc., and PUCCH-ConfigCommon and PUCCH-PowerControl can be configured as shown in Table 6 below.

[0212] [Table 6]

[0213]

[0214] Using the method described above, the terminal can determine or calculate the PUCCH transmission power and transmit the PUCCH by using the determined or calculated PUCCH transmission power.

[0215] The example above concerns uplink power control for PUCCH, and power control for PUSCH, SRS, and PRACH can be performed in a different but similar manner.

[0216] Additionally, in NR MIMO Rel-15, for the terminal's uplink (UL channel) / RS (e.g., PUSCH, PUCCH, SRS), the base station can configure DL RS (i.e., Path Loss Reference RS, or simply Path Loss RS or PL RS) using open-loop power control parameters for path loss compensation. Furthermore, only for PUCCH, the path loss RS can be updated via updating the PUCCH Spatial Relation Information Id via the MAC Control Element (CE) message for each PUCCH resource.

[0217] Additionally, the path loss RS can be updated for PUSCH / SRS via a separate MAC CE message.

[0218] Beam fault recovery

[0219] During DL / UL beam management, beam mismatch issues may occur depending on the configured beam management cycle. Specifically, the optimal DL / UL beam pair may change when the terminal moves or rotates, or when the wireless channel environment changes due to the movement of surrounding objects (e.g., beams are blocked to change a LosS (Line of Sight) environment to a non-LoS environment). Due to such changes, a beam failure event can be considered to have occurred when tracking fails during beam management, which is typically performed by the network. The terminal can determine whether such a beam failure event has occurred by checking the received quality of the downlink reference signal (RS). Furthermore, the terminal should send a report message for this situation or a message requesting beam recovery (called a BFRQ (Beam Failure Recovery Request) message). The base station receiving such a BFRQ message can perform beam recovery for beam recovery through various processes such as beam RS transmission and beam report requests. This series of beam recovery processes is called Beam Failure Recovery (BFR). Version 15 NR standardizes the Beam Fault Recovery (BFR) procedure for primary cells (PCells) or primary-secondary cells (PScells) (collectively referred to as special cells (SpCells)) where contention-based PRACH resources are consistently available. As an operation within the serving cell, the corresponding BFR procedure is configured as follows: the terminal's Beam Fault Detection (BFD) procedure, the BFRQ procedure, and the process by which the terminal monitors the base station's response to the BFRQ.

[0220] Figure 8 This diagram illustrates beam fault recovery operations for Pcells that can be applied in a wireless communication system according to this disclosure.

[0221] The following is for reference. Figure 8 This describes the beam fault recovery operation.

[0222] 1) BFD (Beam Fault Detection)

[0223] A beam failure instance can be considered to have occurred when all PDCCH beams fall below a predetermined quality value (Q_out). Here, quality is based on the hypothetical block error rate (BLER). In other words, this represents the probability that demodulation of the corresponding information will fail when the control information is assumed to be sent to the corresponding PDCCH.

[0224] Here, one or more search spaces for monitoring the PDCCH can be configured for the terminal. The beams can be configured differently for each search space. In this case, it means that all PDCCH beams in all search spaces are below the BLER threshold. The following two methods are supported as methods for the terminal to determine BFD RS.

[0225] Implicit configuration of BFD RS: A CORESET (Control Resource Set) ID (identifier) ​​(the resource area from which PDCCH can be transmitted) is configured in each search space. Furthermore, RS information for the QCL (quasi-co-location) used for spatial RX parameters (e.g., CSI-RS resource ID, SSB ID) can be indicated / configured for each CORESET ID. For example, the RS for the QCL is indicated / configured by the TCI (Transmission Configuration Information) in the NR standard. Here, the RS for the QCL used for spatial RX parameters (e.g., QCL type D in TS38.214) means that the base station informs the terminal that when receiving the corresponding PDCCH DMRS, it will also use (or be able to use) the beam used to receive the corresponding spatial QCL RS (i.e., use the same spatial domain filter for reception). Finally, from the base station's perspective, it is a method of informing the terminal that transmission between the antenna ports of the spatial QCL will be performed by applying the same or similar transmission beams (e.g., when the beam directions are the same / similar, but the beamwidths are different). In other words, as described above, the terminal can determine the RS of the QCL (quasi-co-configuration) of the spatial RX parameters of the CORESET configured for PDCCH reception as the BFD RS (i.e., considered as "all PDCCH beams").

[0226] Explicit configuration of BFD RS: The base station can explicitly configure the beam RS to the terminal for a purpose (beam fault detection). In this case, the corresponding configured beam RS corresponds to "all PDCCH beams".

[0227] Whenever an event occurs where the hypothetical BLER degradation based on BFD RS measurements exceeds a specific threshold, the terminal's physical layer notifies the MAC sublayer of a beam failure instance (BFI). Within the terminal's MAC sublayer, when a certain number of BFIs occur within a given time period (i.e., within the BFD timer) (e.g., the value of a higher-level parameter, beamFailureInstanceMaxCount), a beam failure is determined to have occurred, and the associated RACH operation is initiated.

[0228] MAC object operations are as follows:

[0229] 1> If BFI is received from a lower layer (e.g., the physical layer):

[0230] 2> Start or restart the BFD timer (beamFailureDetectionTimer);

[0231] 2> Increment the BFI counter (BFI_COUNTER) by 1;

[0232] 2> If the BFI counter (BFI_COUNTER) is equal to or greater than the maximum count (number of times) of BFI (beamFailureInstanceMaxCount):

[0233] 3> Initiate a random access procedure in SpCell (refer to the above-mentioned random access related procedures).

[0234] 1> If the BFD timer (beamFailureDetectionTimer) expires; or

[0235] 1> If the BFD timer (beamFailureDetectionTimer), the maximum count (number of times) of BFI (beamFailureInstanceMaxCount), or any reference signal used for beam failure detection is reconfigured by a higher layer (e.g., the RRC layer):

[0236] 2> Set the BFI counter (BFI_COUNTER) to 0.

[0237] 1> If the random access procedure completes successfully:

[0238] 2> Set the BFI counter (BFI_COUNTER) to 0;

[0239] 2> If configured, stop the beamfailureRecoveryTimer.

[0240] 2> It is believed that the beam fault recovery process has been successfully completed.

[0241] 2) Beam Fault Recovery Request (BFRQ) (PRACH-based): New beam identifier + PRACH transmission

[0242] As described in section 1) Beam Failure Detection (BFD), when a certain number or more BFIs occur, the terminal can determine that a beam failure has occurred and perform a beam failure recovery operation. As an example of a beam failure recovery operation, a Beam Failure Recovery Request (BFRQ) operation based on the RACH procedure (i.e., PRACH) can be performed. The corresponding BFRQ procedure is described in detail below.

[0243] The base station can configure a list of candidate beams (e.g., candidateBeamRSList) that can be replaced in the event of a beam failure (BF) via higher-layer signaling (e.g., RRC) for the corresponding terminal. Furthermore, dedicated PRACH resources can be configured for the corresponding candidate beams. These dedicated PRACH resources are based on non-contention PRACH (also known as contention-free PRACH) resources. If the terminal does not find a (suitable) beam in the corresponding list, it selects a contention-based PRACH from the pre-configured SSB resources and sends it to the base station. The specific process is as follows.

[0244] Step 1) The terminal finds a beam with a quality value greater than the predetermined quality value (Q_in) in the RS configured by the base station as a candidate beam RS set.

[0245] - If a beam RS exceeds the threshold, the terminal selects the corresponding beam RS.

[0246] - If multiple beam RS exceed the threshold, the terminal selects any one of the corresponding beam RS.

[0247] -If no beam exceeds the threshold, the terminal performs the following step 2.

[0248] Here, beam quality can be based on RSRP.

[0249] In addition, the RS beamset configured for the base station can include the following three scenarios. For example, all beams in the RS beamset can be configured with SSBs. Alternatively, all beams in the RS beamset can be configured with CSI-RS resources. Alternatively, beams in the RS beamset can be configured with both SSBs and CSI-RS resources.

[0250] Step 2) The terminal finds a beam with a quality value (Q_in) or higher in the SSB (associated with a contention-based PRACH resource).

[0251] - If an SSB exceeds the threshold, the terminal selects the corresponding beam RS.

[0252] - If multiple SSBs exceed the threshold, the terminal selects any one of the corresponding beam RS.

[0253] - If no beam exceeds the threshold, the terminal executes step 3.

[0254] Step 3) The terminal selects any SSB among the SSBs (associated with contention-based PRACH resources).

[0255] The terminal sends PRACH resources and preambles to the base station that are directly or indirectly associated with and configured with the beam RS (CSI-RS or SSB) selected in the process.

[0256] - Here, direct association configuration is used in the following cases.

[0257] When configuring non-contending PRACH resources and preambles for specific RSs in a candidate beam RS set for BFR,

[0258] When configuring (contention-based) PRACH resources and preambles that are mapped one-to-one with SSBs, these SSBs are typically configured for other purposes such as random access.

[0259] - Alternatively, indirect association configuration may be used in the following cases.

[0260] When no contention-free PRACH resources and preambles are configured for a specific CSI-RS in a candidate beam RS set configured separately for BFR

[0261] Here, the terminal selects the (contention-free) PRACH resource and preamble associated with the SSB (i.e., with respect to the spatial Rx parameter QCL (quasi-co-located)), which is designated to be receivable using the same Rx beam as the corresponding CSI-RS.

[0262] 3) Monitor the base station's response to BFRQ.

[0263] - The terminal monitoring base station (gNB) responds to the corresponding PRACH transmission.

[0264] Here, responses to uncontested PRACH resources and preambles are sent to the PDCCH masked by C-RNTI, and responses are received in the search space (SS) separately configured by RRC for BFR.

[0265] Here, the search space is configured for a specific CORESET (for BFR).

[0266] In response to a contention PRACH, the search space and CORESET (e.g., CORESET 0 or CORESET 1) configured for a random access procedure based on a general contention PRACH are reused as is.

[0267] - If there is no response within a certain period of time, repeat the process of identifying and selecting a new beam, and the process of monitoring the response of the base station and BFRQ.

[0268] This process can be performed until the PRACH transmission reaches the pre-configured maximum number of times (N_max) or the configured timer (BFR timer) expires.

[0269] If the timer expires, the terminal stops contention-free PRACH transmission, but can choose to perform contention-based PRACH transmission via SSB until N_max is reached.

[0270] UE-initiated uplink transmission

[0271] This disclosure describes a method for providing / indicating to a terminal a transmission configuration that can be applied to uplink transmissions initiated by the terminal (i.e., uplink transmissions initiated by the UE).

[0272] UE-initiated uplink transmissions can be distinguished from uplink transmissions scheduled by the network / base station. For example, UE-initiated uplink transmissions can include event-based (or event-triggered) uplink transmissions. Events can include, for example, scheduling requests (SRs), beam fault recovery requests (BFRQs), or persistent LBT (listen-before-speak) faults. Here, LBT refers to a method in which, in an unlicensed band, if the radio medium is not occupied within a predetermined time after checking (i.e., listening) whether it can be occupied by other entities, the terminal initiates (i.e., speaks) a transmission, and for persistent LBT faults, the terminal can send a scheduling request for uplink transmissions to the base station.

[0273] The transmission configuration for UE-initiated uplink transmissions may include configurations for at least one of spatial parameters or path loss reference RS (PL reference RS or PL RS).

[0274] In the following examples, the term "spatial parameters" may refer to beam transmission and reception parameters referenced for downlink reception or uplink transmission of a terminal.

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

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

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

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

[0279] In the following description, the terms used for spatial parameters of uplink transmission can be replaced by various terms such as uplink spatial relationship, uplink transmission beam, uplink beam, uplink TCI state, etc., and in some examples, these terms may be used instead of spatial parameters for descriptive purposes. Additionally, the default configuration content among the spatial parameters used for uplink transmission is referred to as default spatial parameters, which can be replaced by terms such as default spatial relationship, default transmission beam, default beam, default TCI state, etc., and in some examples, these terms may be used instead of default spatial parameters for descriptive purposes.

[0280] In the following description, uplink transmissions may include the transmission of various uplink channels or uplink signals. For example, uplink transmissions may correspond to PUSCH / PUCCH / PRACH / SRS transmissions, but are not limited thereto, and the examples of this disclosure can also be applied to various uplink transmissions other than PUSCH / PUCCH / PRACH / SRS.

[0281] Additionally, in this disclosure, reference signal (RS) is used as a term that includes physical layer signals / channels such as synchronization signals and / or SS / PBCH blocks, as well as various types of RS as defined in the standard.

[0282] Additionally, in this disclosure, the path loss RS (PL RS) associated with uplink transmission can be configured independently / separately, or configured together / in association with spatial parameters (e.g., spatial relationship information) used for uplink transmission.

[0283] In the examples of this disclosure, the transmission configuration for UE-initiated uplink transmissions is described primarily by considering the configuration of spatial parameters and / or PL RS. However, the scope of this disclosure is not limited thereto, and the examples of this disclosure can be applied equivalently or similarly to configurations for various purposes of uplink transmissions.

[0284] In currently defined wireless communication systems (e.g., NR Rel-16), for UE-initiated uplink transmissions (e.g., uplink transmissions based on events such as SR, BFRQ for SCell, persistent LBT failure, etc.), up to four SR PUCCH resources can be configured for the terminal. Each SR PUCCH resource can be connected to a unique SR ID. Each SR ID can be connected to at least one logical channel and / or BFRQ. Each logical channel and BFRQ can be connected to up to one SR ID and its corresponding SR PUCCH resource.

[0285] Specifically, a scheduling request (SR) can be used to request uplink shared channel (UL-SCH) resources for a new transmission.

[0286] 0, 1, or multiple SR configurations can be configured for a MAC entity. SR configurations can include a set of PUCCH resources for SRs across different BWPs and cells. For logical channels, SCell beam fault recovery (BFR), and persistent LBT faults, up to one PUCCH resource can be configured per BWP for SRs.

[0287] Each SR configuration can correspond to at least one logical channel and / or SCell beam fault recovery and / or persistent LBT fault. Each logical channel, each SCell BFR, and each persistent LBT fault can be mapped to 0 or 1 SR configurations that can be configured by RRC. A persistent LBT fault, or SCell BFR, or logical channel SR configuration triggered by a BSR other than a preemptive BSR (Buffer Status Report) can be considered to correspond to the SR configuration used for triggering the SR (if such a configuration exists). Any SR configuration can be used for an SR triggered by a preemptive BSR.

[0288] As described above, a normal SR can be triggered by a BSR for the logical channel, and a BFRQ can be triggered by a BFD (beamfailure detection). For example, the base station can configure / allocate a total of two SR PUCCH resources to the terminal for a normal SR, such as SR PUCCH resource #0 connected to the logical channel and SR PUCCH resource #1 for BFRQ. Therefore, when data to be transmitted by the terminal occurs, uplink transmission can be performed on SR PUCCH resource #0, and when BFD occurs, uplink transmission can be performed on SR PUCCH resource #1.

[0289] To improve the reliability of PUCCH transmission in multi-TRP / panel environments, a method is considered for transmitting PUCCH or UCI via PUCCH at multiple transmission times (TOs) (partially or repeatedly). TOs can be configured with resources differentiated in at least one of time / frequency / space (or layer). For example, a PUCCH can be repeatedly transmitted across multiple time resources (e.g., time slots).

[0290] Based on the existing PUCCH resource configuration, for each PUCCH resource, only one spatial relationship information (or beam RS) can be configured, and only one path loss reference RS (PL reference RS or PL RS) can be configured for uplink transmission power control. Additionally, based on the existing SR configuration, only one (up to) one PUCCH resource is allocated for predetermined events (e.g., logical channel / BSR, BFRQ, persistent LBT failure, etc.). Therefore, only one spatial relationship information and PL RS are configured for the terminal for the corresponding PUCCH resource. In this case, in a multi-TRP / panel environment, there is uncertainty regarding which TRP / panel configures the transmission beam and performs uplink power control for the SR PUCCH transmission. More specifically, in multi-TRP / panel (or single-cell multi-TRP / panel) transmission environments, it is desirable for terminals to selectively send SR PUCCHs to specific TRPs / panels for the same purpose (e.g., SR, BFRQ, and persistent LBT failure). However, in existing methods, only one spatial relationship information and one PL RS can be configured / indicated for each PUCCH resource, thus failing to adequately support multi-TRP / panel transmissions. Therefore, to improve this, a new transmission configuration method for UE-initiated uplink transmissions is needed.

[0291] Figure 9 This is a flowchart describing an uplink transmission method initiated by a UE according to embodiments of the present disclosure.

[0292] In S910, the terminal can receive configuration information from the base station for at least one of multiple spatial parameter candidates or multiple PLRS candidates for uplink transmission. The configuration information may include multiple spatial parameter candidates associated with each of the at least one transmission timings for uplink transmission. Alternatively, the configuration information may include multiple path loss reference signal (PLRS) candidates associated with each of the at least one transmission timings for uplink transmission. Alternatively, the configuration information may include multiple spatial parameter candidates and multiple PLRS candidates associated with each of the at least one transmission timings for uplink transmission. In other words, at least one of multiple spatial parameter candidates or multiple PLRS candidates can be configured for the terminal at a single transmission timing. Furthermore, spatial parameters can be configured to be the same as PLRS, or a connection between spatial parameters and PLRS can be configured. Additionally, at least one transmission timing can be mapped to each of at least one CORESET pool index, or can be mapped to each of at least one TRP, or can be mapped to each of at least one RS set.

[0293] In S920, the terminal can perform uplink transmission based on at least one of a spatial parameter or a PL RS. A spatial parameter can be selected / determined from multiple spatial parameter candidates. A PL RS can be selected / determined from multiple PL RS candidates. At least one of a spatial parameter or a PL RS can be applied to uplink transmissions based on trigger events of uplink transmissions at each of at least one transmission timing.

[0294] The configuration information in S910 allows for the configuration of at least one of multiple spatial parameter candidates or multiple PL RS candidates for an uplink transmission resource mapped to a triggering event. (Refer to Example 1) Figure 11 (a) describes a specific example.

[0295] Using the configuration information in S910, at least one of multiple spatial parameter candidates or multiple PL RS candidates can be configured for multiple uplink transmission resources mapped to trigger events. In this case, each of the multiple uplink transmission resources can be mapped to at least one spatial parameter or one PL RS. For example, an uplink transmission resource (e.g., an SR PUCCH resource) can be configured for a configuration identifier (e.g., an SR ID), and multiple configuration identifiers can be mapped to trigger events. For example, multiple uplink transmission resources (e.g., SR PUCCH resources) can be configured for a configuration identifier (e.g., an SR ID), and a configuration identifier can be mapped to a trigger event. Refer to Embodiment 2. Figure 11 (b) describes a specific example.

[0296] In S920, a predetermined criterion can be applied when selecting / determining a spatial parameter for a specific transmission timing from multiple spatial parameter candidates or when selecting / determining a PL RS for a specific transmission timing from multiple PL RS candidates. The predetermined criterion may include at least one of quality, sequence, group, or BFD. Specific examples are described in Embodiments 1 and 2 below.

[0297] In S920, the triggering event can include at least one of logical channel, buffer status report (BSR), beam fault recovery request (BFRQ), or persistent LBT (listen-before-tell) fault. Additionally, similar to BFRQ based on predetermined quality determination for BFD RS, events such as radio link failure (RLF) events based on timer expiration for radio problem / measurement reporting, random access procedure failures, RLC failures, and persistent LBT failures can also be included in the predetermined triggering events.

[0298] UE-initiated uplink transmissions in S920 can include the transmission of various uplink information / signals / data, such as SR, HARQ-ACK, CSI, random access preamble, SRS, and configuration-based permission transmissions. Additionally, UE-initiated uplink transmissions can be sent through various uplink channels such as PUCCH, PUSCH, and PRACH.

[0299] Figure 10 This is a flowchart describing an uplink reception method initiated by a UE according to embodiments of the present disclosure.

[0300] In S1010, the base station can send configuration information to the terminal regarding at least one of multiple spatial parameter candidates or multiple PL RS candidates for uplink transmission. The configuration information may include... Figure 9 The same information described in S910.

[0301] In S1020, the base station can receive uplink transmissions from the terminal based on at least one of a spatial parameter or a PL RS. The spatial parameter / PL RS selected / determined by the terminal and... Figure 9 It is the same as that described in S920.

[0302] The following description is based on a reference. Figure 9 A specific example of an uplink transmission method initiated by a UE according to this disclosure is described.

[0303] In the following description, for clarity, SR PUCCH transmission is assumed to be an example of a UE-initiated uplink transmission, at least one of Logical Channel / BSR, BFRQ, or persistent LBT failure is assumed to be an event triggering a UE-initiated uplink transmission, and SR PUCCH resources and SR IDs are assumed to be identifiers of resources pre-configured for UE-initiated uplink transmissions and corresponding resources. The scope of this disclosure is not limited to such examples and includes various examples of pre-configuring uplink transmission resources and resource identifiers for predetermined UE-initiated uplink transmissions triggered by predetermined events. For example, in the following description, the term SR PUCCH resource may refer to a PUCCH resource configured for an SR ID configured for various purposes (such as BFRQ or persistent LBT failure) and for SR purposes related to data transmission.

[0304] Example 1

[0305] Figure 11 It is a diagram according to this disclosure used to describe the transmission configuration for uplink transmissions initiated by a UE.

[0306] like Figure 11According to this disclosure, for uplink transmissions initiated by a UE, multiple spatial parameters and / or multiple PL RS (hereinafter, multiple spatial parameters / PL RS) can be configured for the terminal for an uplink transmission triggering event initiated by a UE. Therefore, in this embodiment, multiple spatial parameters / PL RS can be configured for uplink transmission resources initiated by a UE, such as... Figure 11 As shown in (a). In Figure 11 In example (a), only one triggering event is shown, but additional triggering events (one or more) can be further configured for the terminal. Additionally, in Figure 11 In example (a), only one SR PUCCH resource is configured for a trigger event, but the terminal can be further configured with one or more additional trigger events, each additional SR PUCCH resource for each of the additional trigger events, and at least one spatial parameter / PL RS for each of the additional SR PUCCH resources (however, different trigger events can be mapped to the same SR PUCCH resource).

[0307] Specifically, a base station can configure multiple spatial parameters and / or multiple PL reference RSs for an SR PUCCH resource. In other words, unlike existing methods where only one spatial parameter / PL RS is configured for an SR PUCCH resource, multiple spatial parameters / PL RSs can be configured for an SR PUCCH resource. Furthermore, at least one SR PUCCH resource can be configured for a terminal, and multiple spatial parameters / PL RSs can be configured for each of all or some of the at least one SR PUCCH resource. Here, the PL RS can be configured to be the same as the spatial parameter, and although the PL RS and the spatial parameter are different, the connection / mapping relationship between them can be configured. The multiple spatial parameters / PL RS configured for such an SR PUCCH resource can be configured for the terminal via higher-layer signaling (e.g., RRC and / or MAC CE signaling).

[0308] Additionally, an SR PUCCH resource can be configured for an SR ID, and at least one triggering event (e.g., logical channel / BSR, BFRQ, persistent LBT failure, etc.) can be configured for an SR ID (or an SR PUCCH resource). Furthermore, up to an SR ID (or an SR PUCCH resource) can be configured for a triggering event. Therefore, when a specific triggering event occurs, an SR ID and an SR PUCCH resource can be specified.

[0309] Therefore, when a specific triggering event occurs (e.g., an SR event), an SR ID and an SRPUCCH resource can be specified, and one of multiple spatial parameters / PLRS configured for the corresponding SR PUCCH resource can be applied in a specific TO. If PUCCH transmission is performed in multiple TOs, one of multiple spatial parameters / PLRS can be applied in each TO. A spatial parameter / PLRS applied to each of at least one TO can be selected / determined according to a predetermined method.

[0310] According to Embodiment 1, multiple RSs (e.g., DL RS, UL RS, or DL ​​RS and UL RS) for multiple TRPs / panels can be pre-configured as beam RS (or spatial parameters) and / or PL RS for a single SR PUCCH resource, and one (same or different) of the multiple RSs can be selectively or alternately applied in at least one TO.

[0311] Various examples of standards for selecting / determining the spatial parameter / PL RS applied to each of at least one TO can be applied. For example, the spatial parameter / PL RS to be applied to a particular TO can be defined based on at least one of mass, sequence, group, or BFD. Specific examples are as follows.

[0312] For example, the terminal can select / determine the spatial parameter / PL RS with a higher (L1 or L3) -RSRP.

[0313] Additionally or alternatively, the terminal may select / determine a spatial parameter / PLRS with a higher (L1 or L3)-SINR.

[0314] Additionally or alternatively, the terminal may alternately select / determine spatial parameters / PL RS according to the order configured by the base station or according to the rules determined for each TO. For example, multiple spatial parameters / PL RS may be applied / mapped to multiple TOs in a cyclic shift manner. For example, a first spatial parameter / PL RS may be selected / applied in odd-numbered TOs, while a second spatial parameter / PL RS may be selected / applied in even-numbered TOs. For example, specific spatial parameters / PL RS may be selected / applied in ascending or descending order of their IDs / indices, according to the order of the TOs.

[0315] Additionally or alternatively, when performing BFD for each TRP (or CORESET pool / set), the SRPUCCH resource can be connected / configured to use the spatial parameters / PL RS (or spatial parameter set / PL RS set) for each TRP (or CORESET pool / set). Therefore, when BFD occurs in a particular TRP (or CORESET pool / set), it can be defined as applying the spatial parameters / PL RS (or spatial parameter set / PL RS set) connected / configured for the corresponding TRP (or CORESET pool / set), or selectively / alternately applying one of them. For example, when BFD occurs in a particular CORESET, the spatial parameters / PL RS (or spatial parameter set / PL RS set) can be selectively connected / corresponding to the CORESET pool / set index to which the corresponding CORESET belongs. Alternatively, the TRP / CORESET where BFD occurs may also have poor uplink quality, so the spatial parameters / PL RS (or spatial parameter set / PL RS set) corresponding to the TRP / CORESET to which BFD did not occur can be selectively connected.

[0316] Here, the occurrence of BFD in a particular TRP / CORESET can be determined based on the quality of the BFD RS rather than the spatial parameter / PL RS. For example, BFD can be determined to have occurred when the assumed BLER based on the BFD RS measurement associated with a particular TRP / CORESET (or associated with one or more spatial parameters / PL RS corresponding to the TRP / CORESET) is equal to or greater than a predetermined threshold, and when it is less than the predetermined threshold, BFD can be determined not to have occurred.

[0317] Additionally or alternatively, the TRP / CORESET in which BFD occurs or does not occur can be determined relatively. For example, when a first mass (e.g., a first hypothetical BLER) measured based on a first BFD RS associated with a first TRP / CORESET (or associated with one or more first spatial parameters / PL RS corresponding to the first TRP / CORESET) is higher than a second mass (e.g., a second hypothetical BLER) measured based on a second BFD RS associated with a second TRP / CORESET (or associated with one or more second spatial parameters / PL RS corresponding to the second TRP / CORESET), one or more spatial parameters / PL RS corresponding to the corresponding TRP / CORESET can be selected based on the first TRP / CORESET; otherwise, one or more spatial parameters / PL RS corresponding to the corresponding TRP / CORESET are selected based on the second TRP / CORESET.

[0318] In the example above, the TRP / CORESET pool can also be replaced by a CORESET or a CORESET set. In other words, when BFD occurs only in at least one CORESET of all CORESETs, an SR PUCCH can be sent to notify the base station of the occurrence of the corresponding event. In this case, the spatial parameters / PL RS (or spatial parameter sets / PL RS sets) to be used can be pre-configured / connected for each CORESET or CORESET set. Therefore, when a particular CORESET / CORESET set is in a BFD situation, spatial parameters / PL RS (or spatial parameter sets / PL RS sets) can be selected to be connected / configured for the corresponding CORESET / CORESET set (or other CORESET / CORESET sets besides the corresponding CORESET / CORESET set). When multiple spatial parameters / PL RS are selected, it is possible to define the selective or alternating use of any of them.

[0319] Example 2

[0320] like Figure 11 As described in this disclosure, for uplink transmissions initiated by a UE, multiple spatial parameters and / or multiple PL RS (hereinafter, multiple spatial parameters / PL RS) can be configured for the terminal for an uplink transmission triggering event initiated by a single UE. Therefore, in this embodiment, uplink transmission resources initiated by multiple UEs can be configured for an uplink transmission triggering event initiated by a single UE, and a spatial parameter / PL RS can be configured for uplink transmission resources initiated by each UE, such as... Figure 11 As shown in (b). In Figure 11 The example in (b) shows only one triggering event, but the terminal can be further configured with one or more additional triggering events, at least one additional SR PUCCH resource for each of the one or more additional triggering events, and a spatial parameter / PL RS for each of the at least one additional SR PUCCH resource (however, different triggering events can be mapped to at least one of the same SR PUCCH resources).

[0321] Specifically, a base station can configure multiple SR PUCCH resources for an uplink transmission triggering event initiated by a UE (e.g., logical channel / BSR, BFRQ, or persistent LBT failure). In other words, unlike existing methods that configure up to one SR PUCCH resource for a single triggering event, multiple SR PUCCH resources can be configured for a single triggering event. Furthermore, at least one uplink transmission triggering event initiated by a UE can be configured for the terminal, and multiple SR PUCCH resources can be configured for each of all or some events within at least one triggering event. The multiple SR PUCCH resources configured for such a single triggering event can be configured for the terminal via higher-layer signaling (e.g., RRC and / or MAC CE signaling).

[0322] Additionally, a spatial parameter / PL RS can be configured for an SR PUCCH resource. Here, the PL RS can be configured to be the same as the spatial parameter, and although the PL RS and the spatial parameter are different, the connection / mapping relationship between them can be configured.

[0323] As an example of configuring multiple SR PUCCH resources for a single trigger event, one SR PUCCH resource can be configured for one SR ID, and at least one trigger event can be configured for one SR ID. Alternatively, multiple SR IDs (i.e., multiple SR PUCCH resources) can be configured for a single trigger event.

[0324] Alternatively or additionally, multiple SR PUCCH resources can be configured for one SR ID, and at least one trigger event can be configured for one SR ID. Alternatively, one SR ID (i.e., multiple SR PUCCH resources) can be configured for one trigger event.

[0325] Therefore, when a specific triggering event occurs (e.g., an SR event), multiple SR PUCCH resources configured for the corresponding triggering event can be specified. Here, a spatial parameter / PL RS is configured for each of the multiple SR PUCCH resources, so if any of the multiple SR PUCCH resources are specified, a spatial parameter / PL RS can be specified, and therefore, a spatial parameter / PL RS can be applied in a specific TO. If PUCCH transmission is performed in multiple TOs, one of the multiple SR PUCCH resources (correspondingly, a spatial parameter / PL RS) can be applied in each TO. An SR PUCCH resource (i.e., a spatial parameter / PL RS) applied to each of at least one TO can be selected / determined according to a predetermined method.

[0326] According to Embodiment 2, multiple SR PUCCH resources can be configured for each triggering event. One RS (e.g., DL RS or UL RS) for a TRP / panel can be pre-configured as a beam RS (or spatial parameter) and / or PL RS for each of the multiple SR PUCCH resources. One SR PUCCH resource (one resulting spatial parameter / PL RS) from the multiple SR PUCCH resources can be selectively or alternately applied in at least one TO.

[0327] Various examples of standards for terminal selection / determination of SR PUCCH resources applied to each of at least one TO can be applied. For example, the spatial parameter / PL_RS to be applied to a particular TO can be defined based on at least one of quality, order, group, or BFD. Specific examples are as follows.

[0328] For example, the terminal can select / determine the SR PUCCH resource corresponding to the spatial parameter / PL RS with a higher (L1 or L3) -RSRP.

[0329] Additionally or alternatively, the terminal may select / determine the SR PUCCH resource corresponding to the spatial parameter / PL RS with a higher (L1 or L3)-SINR.

[0330] Additionally or alternatively, the terminal may alternately select / determine SR PUCCH resources according to the order configured by the base station or according to the rules determined by the TO. For example, multiple SR PUCCH resources may be applied / mapped to multiple TOs in a cyclic shift manner. For example, a first SR PUCCH resource may be selected / applied in an odd-numbered TO, and a second SR PUCCH resource may be selected / applied in an even-numbered TO. For example, a specific SR PUCCH resource may be selected / applied according to the order of the TOs, in ascending or descending order of the SR PUCCH resource ID / index.

[0331] Additionally or alternatively, when performing BFD for each TRP (or CORESET pool / set), one or more SR PUCCH resources can be connected / configured for each TRP (or CORESET pool / set). Therefore, when BFD occurs in a particular TRP (or CORESET pool / set), it can be defined as applying one or more SR PUCCH resources connected / configured for the corresponding TRP (or CORESET pool / set), or selectively / alternately applying one of them. For example, when BFD occurs in a particular CORESET, one or more SR PUCCH resources can be selectively connected / corresponding to the CORESET pool / set index to which the corresponding CORESET belongs. Alternatively, the TRP / CORESET where BFD occurs may also have poor uplink quality, so one or more SR PUCCH resources corresponding to TRPs / CORESETs where BFD has not occurred can be selectively connected / corresponding to.

[0332] Here, the occurrence of BFD in a particular TRP / CORESET can be determined based on the quality of the BFD RS rather than the spatial parameter / PL RS. For example, BFD can be determined to have occurred when the assumed BLER of the BFD RS measurement associated with a particular TRP / CORESET (or associated with one or more SR PUCCH resources for the TRP / CORESET) is equal to or greater than a predetermined threshold, and when it is less than the predetermined threshold, BFD can be determined not to have occurred.

[0333] Additionally or alternatively, the TRP / CORESET in which BFD has occurred or not can be determined relatively. For example, when a first quality (e.g., a first hypothetical BLER) measured based on a first BFD RS associated with a first TRP / CORESET (or associated with one or more SR PUCCH resources corresponding to the first TRP / CORESET) is higher than a second quality (e.g., a second hypothetical BLER) measured based on a second BFD RS associated with a second TRP / CORESET (or associated with one or more second SR PUCCH resources corresponding to the second TRP / CORESET), one or more SR PUCCH resources corresponding to the corresponding TRP / CORESET can be selected based on the first TRP / CORESET; otherwise, one or more SR PUCCH resources corresponding to the corresponding TRP / CORESET are selected based on the second TRP / CORESET.

[0334] In the example above, the TRP / CORESET pool can also be replaced by a CORESET or a CORESET set. In other words, when BFD occurs only in at least one CORESET of all CORESETs, an SR PUCCH can be sent to notify the base station of the occurrence of the corresponding event, and in this case, one or more SR PUCCH resources to be used can be pre-configured / connected for each CORESET or CORESET set. Therefore, when a particular CORESET / CORESET set is in a BFD situation, one or more SR PUCCH resources can be selected to be connected / configured for the corresponding CORESET / CORESET set (or other CORESET / CORESET sets besides the corresponding CORESET / CORESET set). When multiple SR PUCCH resources are selected, it can be defined that any one of them can be used selectively or alternately.

[0335] In contrast to Embodiment 1, Embodiment 2 allows for individual configuration of the PE location / PUCCH format, etc., of the PUCCH resources to be received by each TRP. Therefore, Embodiment 2 can support more flexible PUCCH transmission than Embodiment 1 for various MTRP environments, while requiring more PUCCH resources to be pre-configured. However, in a single-cell, multi-TRP / panel environment, it may be irrelevant which TRP / panel receives the corresponding PUCCH, and in such an environment, it is permissible to repeatedly configure PUCCHs with the same RE location / symbol location / PUCCH format, etc., to reduce the overhead of PUCCH resource configuration. For example, multiple PUCCH resources can be configured for a specific triggering event (e.g., logical channel / BSR, BFRQ, persistent LBT failure, etc.), but at least one of the RE location / symbol location / PUCCH format, etc., is the same for the multiple PUCCH resources, and it is permissible to configure the spatial parameters / PL RS differently.

[0336] The above embodiments 1 and 2 can also be applied to a TO or a single TRP. In this case, the terminal can select one of the multiple spatial parameters / PL RS or multiple PUCCH resources configured for the terminal according to predetermined criteria, and apply it to PUCCH transmission in the corresponding TO.

[0337] In embodiments 1 and 2 above, the method of configuring multiple spatial parameters / PL RS for a triggering event can be applied only to spatial parameters or PL RS. For example, multiple spatial parameters can be configured for a triggering event, and the terminal may not be provided with configuration for PL RS. Alternatively, multiple PL RS can be configured for a triggering event, and the terminal may not be provided with configuration for spatial parameters. In this case, based on the relationship between spatial parameters and PL RS (e.g., spatial parameters and PL RS can be predefined / pre-configured as the same DL RS), the terminal can determine the other based on the configuration for either spatial parameter or PL RS. For example, when embodiment 1 or embodiment 2 applies only to PL RS and no spatial parameters are configured for the corresponding SR PUCCH resource, additional rules can be defined based on the PL RS selected / determined by the terminal to apply (the same DL RS) as the spatial parameter. In contrast, that is, when embodiment 1 or embodiment 2 applies only to spatial parameters and no PL RS is configured for the corresponding SR PUCCH resource, additional rules can be defined based on the spatial parameters selected / determined by the terminal to apply (the same DL RS) as the PL RS.

[0338] In Embodiments 1 and 2 above, for clarity, the description assumes an SR PUCCH. However, according to the examples above, the spatial parameter / PL RS can also be applied to PUCCH resources for other purposes (e.g., HARQ-ACKPUCC / CSI PUCCH, etc.) or other UL channels / resources / signals besides PUCCH (e.g., SRS / PRACH / PUSCH, etc.). For example, in a multi-TRP / panel environment, multiple spatial parameters / PL RS can be configured for each PRACH resource for BFRQ purposes, and the terminal can select a specific parameter / PL RS from them according to predetermined criteria and apply it to PRACH transmission in a specific TO.

[0339] The above examples can be applied to various UE-initiated uplink transmissions that occur when a specific triggering event occurs in the terminal (e.g., BFR PRACH, configuration grant PUSCH, SR / BFR PUCCH). Additionally, the above examples can be applied to uplink transmissions sent via base station indication / control / scheduling, and to cases where spatial parameters / PL RS are not explicitly configured / indicated to be applied to uplink transmissions in a specific TO.

[0340] Figure 12 This is a diagram illustrating the signaling process between a base station and a terminal in an uplink transmission and reception method according to an embodiment of the present disclosure.

[0341] Figure 12This indicates that signaling between a base station (BS) and a terminal (UE) according to Embodiment 1 / 2 of this disclosure can be applied. Here, the UE / base station is merely an example, and can be implemented using methods such as... Figure 13 Various devices in the system are replaced for application. Figure 12 This is merely for ease of description and does not limit the scope of this disclosure. Additionally, details may be omitted depending on the circumstances and / or configuration, etc. Figure 12 Some of the steps shown.

[0342] A base station can generally refer to an entity that performs data transmission and reception with a terminal. For example, a base station can be a concept that includes at least one TP (transmission point) and at least one TRP (transmit and receive point). In addition, TP and / or TRP can also include the base station's panel, transmission and reception units, etc.

[0343] Additionally, TRPs can be applied by replacing them with expressions such as panels, antenna arrays, cells (e.g., macro cells / small cells / pecimens, etc.), TPs (transmission points), base stations (gNBs, etc.). As mentioned above, TRPs can be categorized based on information about CORESET groups (or CORESET pools) (e.g., indexes, IDs). In the example, when a terminal is configured to perform transmission and reception using multiple TRPs (or cells), this might refer to configuring multiple CORESET groups (or CORESET pools) for a single terminal. This configuration of CORESET groups (or CORESET pools) can be performed via higher-level signaling (e.g., RRC signaling, etc.).

[0344] The UE can receive configuration information from the base station (S105). In other words, the base station can send configuration information to the UE. Configuration information can be sent via higher-layer signaling (e.g., RRC signaling, MAC-CE, etc.). Furthermore, when the configuration information is predefined or pre-configured, the corresponding steps can be omitted.

[0345] For example, the configuration information may include configuration information related to MTRP transmissions described in Embodiment 1 / Embodiment 2 above. For example, the configuration information may include configuration information for CORESET / CORESET group / CORESET pool / TCI state-related configuration information for multi-TRP transmission and reception. For example, the configuration information may include SR configuration (or transmission configuration for UE-initiated uplink transmissions) described in Embodiment 1 / Embodiment 2 above.

[0346] For example, SR configuration (or transmission configuration for UE-initiated uplink transmissions) may include SR PUCCH resource configuration as described in Embodiment 1 / Embodiment 2 above. For example, multiple spatial parameters / PL RS can be configured corresponding to SR PUCCH resources. For example, multiple SR PUCCH resources can be configured according to SR purpose / target (or triggering events, such as logical channel / BSR, BFRQ, persistent LBT failure, etc.).

[0347] For example, in S105, UE ( Figure 13 100 / 200 in the base station ( Figure 13 The above operation of receiving configuration information (200 / 100) can be described below. Figure 13 This is achieved using the devices described. For example, refer to... Figure 13 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104, etc., to receive configuration information, and at least one transceiver 106 can receive configuration information from the base station.

[0348] The UE can receive control information from the base station (S110). In other words, the base station can send control information to the UE. For example, control information can be sent through a control channel (e.g., PDCCH, etc.). For example, the control information may include (indication) information about the TCI status (e.g., TCI field) / resource allocation information about the TCI status (e.g., bandwidth) / resource allocation information for uplink channel (e.g., PUCCH / PUSCH) transmission and reception (i.e., space / frequency / time resources), etc.

[0349] For example, in S110, UE ( Figure 13 100 / 200 in the base station ( Figure 13 The above operation of receiving control information (200 / 100) can be described below. Figure 13 This is achieved using the devices described. For example, refer to... Figure 13 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104, etc., to receive control information, and at least one transceiver 106 can receive control information from the base station.

[0350] The UE can perform uplink transmissions to the base station (e.g., PUCCH / PUSCH transmissions) (S115). In other words, the base station can receive uplink transmissions (e.g., PUCCH / PUSCH) from the UE. For example, uplink transmissions can be repeatedly sent in multiple TOs (transmission times).

[0351] For example, as described in Embodiment 1 / Embodiment 2 above, a PUCCH can be transmitted when a specific triggering event (e.g., an SR event) occurs in the terminal. For example, the specific triggering event (e.g., an SR event) may include logical channel / BSR, BFRQ, persistent LBT failure, etc. For example, based on Embodiment 1 / Embodiment 2 above, PUCCH resources / spatial parameters / PL RS for PUCCH transmission can be determined. For example, one of multiple spatial parameters / PL RS / PUCCH resources can be selected based on quality (e.g., L1 / L3-RSRP / SINR), or the PUCCH can be transmitted based on multiple spatial parameters / PL RS / PUCCH resources selected in the corresponding TO. For example, the spatial parameters / PL RS to be applied in the PUCCH TO can be determined sequentially based on a predetermined order (e.g., ascending / descending order of the ID / index associated with the PUCCH resource / spatial parameter / PL RS). For example, one of multiple SR PUCCH resources / spatial parameters / PL RS can be selected based on group / BFD. For example, you can select the PUCCH resource / space parameter / PLRS corresponding to the CORESET pool / group index associated with the occurrence of a specific triggering event.

[0352] For example, in S115, UE ( Figure 13 The 100 / 200 in the middle is executed to the base station ( Figure 13 The above operations for uplink transmission of 200 / 100 in the above method can be described below. Figure 13 This is achieved using the devices described. For example, refer to... Figure 13 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104, etc., to transmit uplink channels, and at least one transceiver 106 can transmit uplink channels to the base station.

[0353] As described above, the base station / UE signaling and operations (e.g., Example 1 / Example 2 / ) Figure 12 (etc.) can be made by the devices described below (e.g., Figure 13 This can be achieved through devices within the network. For example, the base station may correspond to the first wireless device, while the UE may correspond to the second wireless device, and in some cases, the reverse can be considered.

[0354] For example, the base station / UE signaling and operations described above (e.g., Example 1 / Example 2 / ) Figure 12 (etc.) can be made by Figure 13 At least one processor (e.g., 102, 202) processes the above-mentioned base station / UE signaling and operations (e.g., Embodiment 1 / Embodiment 2 / Figure 12 (etc.) can be used for driving Figure 13At least one processor (e.g., 102, 202) has its commands / programs (e.g., instructions, executable code) stored in memory (e.g., ...). Figure 13 In at least one of the memories 104, 204).

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

[0356] Figure 13 This is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0357] refer to Figure 13 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).

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

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

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

[0361] 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 perform 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.

[0362] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store 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.

[0363] 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 description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein through 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.

[0364] 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 may 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.

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

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

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

[0368] [Industrial Availability]

[0369] The method presented in this disclosure is primarily described based on examples applied to 3GPP LTE / LTE-A and 5G systems, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method for uplink transmission performed in a wireless communication system, comprising: The system receives configuration information from the base station for multiple uplink transmission resources, including a first uplink transmission resource for triggering events related to a first control resource set (CORESET) group of the serving cell and a second uplink transmission resource for triggering events related to a second CORESET group of the serving cell. Based on the triggering event associated with the first CORESET group of the serving cell, uplink transmission to the base station is performed on the first uplink transmission resource; as well as Based on a triggering event associated with the second CORESET group of the serving cell, uplink transmission to the base station is performed on the second uplink transmission resources.

2. The method according to claim 1, wherein: The configuration information further includes at least one of multiple spatial parameter candidates or multiple path loss reference signal (PLRS) candidates related to the multiple uplink transmission resources. Each of the plurality of uplink transmission resources is mapped to at least one of the spatial parameters or PL RS.

3. The method according to claim 2, wherein: Uplink transmission resources are configured to configure identifiers, and multiple configuration identifiers are mapped to the triggering event.

4. The method according to claim 1, wherein: The triggering event is related to beam fault recovery. The uplink transmission based on the first uplink transmission resource is triggered by the beam fault recovery for the first CORESET group, and The uplink transmission based on the second uplink transmission resources is triggered by the beam fault recovery for the second CORESET group.

5. The method according to claim 1, wherein: The triggering event includes at least one of the following: logical channel, buffer status report (BSR), beam fault recovery request (BFRQ), or persistent talk-before-you-talk (LBT) fault.

6. The method according to claim 2, wherein: The spatial parameters include at least one of the following: spatial relationship information for the uplink transmission, spatial relationship reference signal RS, uplink transmission configuration indicator TCI status, beam RS, or quasi-co-located QCL reference RS.

7. The method according to claim 1, wherein: The uplink transmission includes the transmission of at least one of the following: Scheduling Request (SR), Hybrid Automatic Repeat Request / Acknowledgement (HARQ-ACK), Channel State Information (CSI), Random Access Preamble, Sound Reference Signal (SRS), configured license-based data, Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), or Physical Random Access Channel (PRACH).

8. A terminal, comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: The at least one transceiver receives configuration information from the base station for multiple uplink transmission resources, the multiple uplink transmission resources including a first uplink transmission resource for triggering events related to a first control resource set (CORESET) group of the serving cell and a second uplink transmission resource for triggering events related to a second CORESET group of the serving cell. Based on a triggering event associated with the first CORESET group of the serving cell, uplink transmission to the base station is performed on the first uplink transmission resource via the at least one transceiver. Based on a triggering event associated with the second CORESET group of the serving cell, uplink transmission to the base station is performed on the second uplink transmission resources via the at least one transceiver.

9. A base station, comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: The at least one transceiver sends configuration information for multiple uplink transmission resources to the terminal, the multiple uplink transmission resources including a first uplink transmission resource for triggering events related to a first control resource set CORESET group of the serving cell and a second uplink transmission resource for triggering events related to a second CORESET group of the serving cell; Based on a triggering event associated with the first CORESET group of the serving cell, uplink transmission is received from the terminal via the at least one transceiver on the first uplink transmission resource. Based on the triggering event associated with the second CORESET group of the serving cell, uplink transmission to the base station is performed on the second uplink transmission resources.

Images