Method and apparatus for transmitting or receiving demodulation reference signal bundling-based uplink channel in a wireless communication system

Abstract

A method and apparatus for transmitting or receiving an uplink channel based on demodulation reference signal (DMRS) bundling in a wireless communication system. [Solution] A method for a terminal to transmit an uplink channel in a wireless communication system according to one embodiment of the present disclosure includes receiving configuration information related to DMRS bundling for the uplink channel from a network; and transmitting the uplink channel to the network at a first actual TDW within a configured time domain window (TDW), or at the first actual TDW and a second actual TDW within the configured TDW, wherein the first actual TDW ends in connection with an event, and whether to generate the second actual TDW in response to the event based on the event being a first type event may be based on the capability of the terminal.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems, and more particularly to a method and apparatus for transmitting or receiving an uplink channel based on demodulation reference signal bundling in a wireless communication system. [Background technology]

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

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

[0004] A technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving a demodulation reference signal (DMRS)-based uplink channel in a wireless communication system.

[0005] A further technical problem of the present disclosure is to provide a method and apparatus for starting or ending a time domain window associated with the application of DMRS bundling in a wireless communication system.

[0006] A further technical problem of the present disclosure is to provide a method and apparatus for event-based opening or closing of a time domain window associated with the application of DMRS bundling in a wireless communication system.

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

[0008] A method for a terminal transmitting an uplink channel in a wireless communication system according to one embodiment of the present disclosure includes receiving configuration information related to demodulation reference signal (DMRS) bundling for the uplink channel from a network, and transmitting the uplink channel to the network at a first actual time domain window (TDW) within a configured TDW, or at the first actual TDW and a second actual TDW within the configured TDW, wherein the first actual TDW ends in connection with an event, and whether to generate the second actual TDW in response to the event based on the event being a first type event may be based on the capability of the terminal.

[0009] A method for a base station to receive an uplink channel in a wireless communication system according to a further aspect of the present disclosure includes transmitting configuration information related to demodulation reference signal (DMRS) bundling for the uplink channel to a terminal, and receiving the uplink channel from the terminal at a first actual time domain window (TDW) within a configured TDW, or at the first actual TDW and a second actual TDW within the configured TDW, wherein the first actual TDW ends in connection with an event, and whether to generate the second actual TDW in response to the event based on the event being a first type event may be based on the capability of the terminal. [Effects of the Invention]

[0010] According to an embodiment of the present disclosure, a method and apparatus for transmitting or receiving a demodulation reference signal (DMRS)-based uplink channel in a wireless communication system can be provided.

[0011] According to an embodiment of the present disclosure, a method and apparatus for opening or closing a time domain window associated with applying DMRS bundling in a wireless communication system can be provided.

[0012] According to an embodiment of the present disclosure, a method and apparatus can be provided for event-based opening or closing of a time domain window associated with applying DMRS bundling in a wireless communication system.

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

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

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

[0016] [Figure 2] 1 illustrates an example of a frame structure in a wireless communication system to which the present disclosure can be applied.

[0017] [Figure 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied.

[0018] [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied.

[0019] [Figure 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied.

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

[0021] [Figure 7] FIG. 10 is a diagram for explaining an example of PUSCH repeated transmission to which the present disclosure can be applied.

[0022] [Figure 8] 10A and 10B are diagrams illustrating examples of DMRS symbol positions to which the present disclosure can be applied.

[0023] [Figure 9]10 is a diagram illustrating an example of an uplink channel transmission method for a terminal according to the present disclosure. FIG.

[0024] [Figure 10] 10 is a diagram illustrating an example of an uplink channel reception method of a base station according to the present disclosure. FIG.

[0025] [Figure 11] FIG. 1 is a diagram illustrating an example of a TDW to which the present disclosure can be applied.

[0026] [Figure 12] 1 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0027] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it will be understood by those skilled in the art that the present disclosure can be implemented without such specific details.

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

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

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

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

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

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

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

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

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

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

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

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

[0040] - BM: Beam management

[0041] - CQI: Channel Quality Indicator

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

[0043] - CSI: Channel State Information

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

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

[0046] - DMRS: Demodulation Reference Signal

[0047] - FDM: Frequency Division Multiplexing

[0048] - FFT: Fast Fourier transform

[0049] - IFDMA: Interleaved frequency division multiple access

[0050] - IFFT: Inverse fast Fourier transform

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

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

[0053] - MAC: Medium Access Control

[0054] - NZP: Non-zero power

[0055] - OFDM: Orthogonal frequency division multiplexing

[0056] - PDCCH: Physical downlink control channel

[0057] - PDSCH: Physical downlink shared channel

[0058] - PMI: Precoding matrix indicator

[0059] - RE: resource element

[0060] - RI: Rank indicator

[0061] - RRC: Radio resource control

[0062] - RSSI: received signal strength indicator

[0063] - Rx: Reception

[0064] - QCL: quasi co-location

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

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

[0067] - TDM: time division multiplexing

[0068] - TRP: transmission and reception point

[0069] - TRS: Tracking reference signal

[0070] - Tx: transmission

[0071] - UE: User equipment

[0072] - ZP: Zero power

[0073] System in general

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

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

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

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

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

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

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

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

[0082] [Table 1]

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

[0084] [Table 2]

[0085] In relation to the frame structure in an NR system, the size of the various fields in the time domain is T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and N f= 4096. Downlink and uplink transmission is T f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T = 10 ms. sf =(Δf max N f / 1000)·T c It consists of 10 subframes with a duration of 1 ms.

[0086] In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Also, transmission from a terminal in uplink frame number i begins T TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols, symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used.

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

[0088] [Table 3]

[0089] [Table 4]

[0090] FIG. 2 shows an example where μ=2 (SCS is 60 kHz), and referring to Table 3, one subframe may include four slots. One subframe = {1, 2, 4} slots shown in FIG. 2 is an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot may include 2, 4, or 7 symbols, or may include more or fewer symbols. In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered.

[0091] The physical resources that can be considered in an NR system will now be described in detail. First, with regard to antenna ports, the antenna ports are defined so that the channel on which symbols on an antenna port are carried can be inferred from the channel on which other symbols on the same antenna port are carried. If the large-scale properties of the channel on which symbols on one antenna port are carried can be inferred from the channel on which symbols on the other antenna port are carried, the two antenna ports are said to have a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing. Figure 3 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied.

[0092] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB It consists of subcarriers, and one subframe is 14.2 μ In the NR system, a transmitted signal is composed of N OFDM symbols. RB μ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RB μ ≦N RB max,μ The above N RB max,μrepresents the maximum transmission bandwidth, which may vary between uplink and downlink as well as with numerology.

[0093] In this case, one resource grid may be configured for μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and the index pair JPEG2026042869000006.jpg9129, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG2026042869000007.jpg9132,...,2 μ N symb (μ) -1 represents the position of the symbol within the subframe. When referring to resource elements in a slot, the index pair (k, l) is used, where l = 0,...,N symb μ μ and the resource element for antenna port p. JPEG2026042869000008.jpg9121 is a complex value JPEG2026042869000009.jpg10126. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indices p and μ may be dropped, so that the complex value is JPEG2026042869000010.jpg12128. Also, a resource block (RB) is a set of N sc RB = 12 consecutive subcarriers.

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

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

[0096] - absoluteFrequencyPointA denotes the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number). Common resource blocks are numbered from 0 upwards in the frequency domain for subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between the resource elements (k, l) for the subcarrier spacing setting μ is given by the following equation 1.

[0097]

number

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

[0099]

number

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

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

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

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

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

[0105] Meanwhile, the base station can configure multiple BWPs within one CC configured for the terminal. For example, a BWP occupying a relatively small frequency domain is configured in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH may be scheduled on a larger BWP.

[0106] Alternatively, when UEs are concentrated in a specific BWP, other BWPs may be configured for some UEs for load balancing. Alternatively, taking into consideration frequency domain inter-cell interference cancellation between adjacent cells, a central portion of the spectrum from the entire bandwidth may be excluded and both BWPs may be configured within the same slot. In other words, the base station can configure at least one DL / UL BWP for UEs associated with a wideband CC.

[0107] The base station can activate at least one DL / UL BWP among the DL / UL BWPs configured at a specific time (through L1 signaling, MAC CE (Control Element), RRC signaling, etc.). The base station can also instruct switching to another configured DL / UL BWP (through L1 signaling, MAC CE, RRC signaling, etc.). Alternatively, the base station can switch to a predetermined DL / UL BWP when a timer value expires on a timer basis. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP.

[0108] However, in situations where the UE is performing an initial access process or before the RRC connection is set up, the DL / UL BWP configuration may not be received. Therefore, the DL / UL BWP assumed by the UE in such situations is defined as the initially active DL / UL BWP.

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

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

[0111] When a terminal is powered on or newly enters a cell, it performs an initial cell search, such as synchronizing with a base station (S601). To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and acquire information such as a cell identifier (ID). The terminal then receives a physical broadcast channel (PBCH) from the base station to acquire broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.

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

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

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

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

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

[0117] [Table 5]

[0118] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB)-related information (e.g., Modulation Coding and Scheme (MCS), New Data Indicator (NDI), Redundancy Version (RV), etc.), hybrid-automatic repeat and request (HARQ)-related information (e.g., process number, Downlink Assignment Index (DAI), PDSCH-HARQ feedback timing, etc.), multiple antenna-related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for PUSCH scheduling in one cell. The information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled using C-RNTI (Cell Radio Network Temporary Identifier, Cell RNTI), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and then transmitted.

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

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

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

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

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

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

[0125] PUCCH configuration and repetition transmission method

[0126] The PUCCH can carry uplink control information (UCI). The UCI may include at least one of hybrid automatic request (HARQ)-ACK information, scheduling request (SR), or CSI information. The UCI type (or usage, payload type), transmission duration, etc. that can be transmitted may differ depending on the PUCCH format. For example, as shown in Table 6 below, the PUCCH can be classified into five formats.

[0127] [Table 6]

[0128] PUCCHs of formats 0 and 2 may be referred to as short duration PUCCHs, and PUCCHs of formats 1, 3, and 4 may be referred to as long duration PUCCHs. PUCCHs of formats 0, 1, and 4 may be multiplexed in the frequency / time domain, but PUCCHs of formats 2 and 3 may not be multiplexed in the frequency / time domain. To improve PUCCH coverage, schemes such as a sequence-based DMRS-less PUCCH configuration, higher DMRS density, dynamic PUCCH repetition factor indication, or DMRS bundling for PUCCH, improved frequency hopping, improved power control, and increased number of allowed repetitions may be utilized.

[0129] Furthermore, PUCCH repetition transmission may be performed to improve PUCCH coverage. Here, only PUCCHs with formats 1, 3, and 4 (i.e., long duration PUCCHs) may be repeatedly transmitted. The number of repetitions of PUCCH may be configured by higher layer signaling (e.g., 'nrofSlots' included in 'PUCCH-FormatConfig') and may be set to 2, 4, or 8.

[0130] The position of the repeatedly transmitted PUCCH may be the same in each slot. That is, the first symbol and the number of consecutive symbols of the repeatedly transmitted PUCCH may be the same in each slot. When frequency hopping is configured for the repeatedly transmitted PUCCH by higher layer signaling (e.g., 'interslotFrequencyHopping' included in 'PUCCH-FormatConfig'), the position of the PUCCH in even-numbered slots may be defined by the 'startPRB' information element, and the position of the PUCCH in odd-numbered slots may be defined by the 'secondHopPRB' information element.

[0131] The higher layer signaling ("PUCCH-FormatConfig") including information related to the number of repetitions and frequency hopping of the PUCCH may be configured as shown in Table 7 below.

[0132] [Table 7]

[0133] Furthermore, the UE does not need to multiplex different UCI types of repeated PUCCHs. Therefore, when different PUCCHs overlap in a slot interval, the UE can transmit only one PUCCH according to a priority rule and drop the remaining PUCCHs, or can transmit an earliest starting PUCCH having the same priority. As an example of the priority rule, the highest priority may be HARQ-ACK, followed by SR and CSI. That is, only PUCCHs having a long duration format may be repeatedly transmitted in the same position of each slot, and the actual number of repetitions may be smaller than the number set by higher layer signaling. In addition, it may be difficult to perform PUCCH repeated transmission in a specific slot (e.g., a special slot) that includes all downlink, uplink, and flexible symbols. In this case, the above-mentioned scheme can be used to improve PUCCH coverage.

[0134] Also, PUCCH repetition transmission may be performed in the specific slot by UCI splitting (e.g., dividing the UCI payload into a short duration PUCCH and a long duration PUCCH). However, the above-mentioned method has a limitation in that it has a higher gain in terms of latency reduction than in terms of coverage improvement.

[0135] To improve coverage, as an example of a PUCCH repetition transmission method, instead of setting repetition by specifying the start symbol and length within a slot as in the existing PUSCH repetition type B, it is also possible to repeatedly transmit the PUCCH using consecutive symbols.

[0136] PUSCH repetitions

[0137] The terminal may transmit the same PUSCH multiple times. For example, the same PUSCH may refer to a PUSCH scheduled by one uplink grant (e.g., an uplink grant provided in DCI or a configured grant by RRC signaling). Alternatively, the same PUSCH may refer to a PUSCH carrying the same data (e.g., a transport block (TB)).

[0138] FIG. 7 is a diagram illustrating an example of PUSCH repeated transmission to which the present disclosure can be applied.

[0139] Two types of PUSCH repetition types, Type A and Type B, may be defined.

[0140] PUSCH repetition type A is slot-based repetition, and the example of FIG. 7(a) shows that three repetitions T0, T1, and T2 are performed in three slots, respectively. In PUSCH repetition type A, the same transmission start symbol position and the same number of transmission symbols (or length) may be applied to each of multiple slots.

[0141] If there is an invalid symbol that cannot be used for PUSCH transmission among the symbol resources constituting a specific PUSCH repetition, the transmission of the PUSCH repetition may be dropped and not performed. For example, when a total of four PUSCH repetitions, Rep0, Rep1, Rep2, and Rep3, are transmitted, if an invalid symbol is included in the symbol resource constituting Rep1, the transmission of Rep1 may be dropped, and only the transmissions of Rep0, Rep2, and Rep3 may be performed. Therefore, the number of repetitions actually performed may be less than the set number of repetitions.

[0142] For PUSCH repetition type A, frequency hopping may be configured for the UE by higher layer parameters. In PUSCH repetition type A, one of two frequency hopping modes, i.e., intra-slot frequency hopping and inter-slot frequency hopping, may be configured for the UE. Intra-slot frequency hopping may be applied to single-slot PUSCH transmission or multi-slot PUSCH transmission, and inter-slot frequency hopping may be applied to multi-slot PUSCH transmission. In inter-slot frequency hopping, frequency hopping occurs at slot boundaries. In intra-slot frequency hopping, the number of symbols in the first hop and the number of symbols in the second hop are configured by the base station, and frequency hopping occurs at the configured symbol boundaries.

[0143] In PUSCH repetition type B, repetition may be performed in units of the symbol length in which the actual PUSCH is transmitted. For example, as shown in FIG. 7(b), if the symbol length in which the PUSCH is transmitted is 10 symbols, PUSCH repetition may be performed in units of 10 consecutive symbols. A transmission time unit of PUSCH repetition that does not consider slot boundaries, ineffective symbols, etc. may be referred to as a nominal repetition. In the example of FIG. 7(b), N0, N1, and N2 represent three nominal repetitions.

[0144] In actual PUSCH repetitions, one PUSCH cannot be transmitted at a slot boundary. Therefore, when a PUSCH transmission includes a slot boundary, two actual repetitions may be distinguished at the slot boundary, as illustrated in FIG. 7(c). For example, two actual repetitions A0 and A1 corresponding to nominal repetition N0 may be distinguished at the slot boundary. That is, seven symbols before N0 may correspond to A0, and three symbols after N0 may correspond to A1.

[0145] One PUSCH transmission may be performed only with consecutive symbols. Therefore, if an invalid symbol exists in the time resource where a PUSCH repetition is to be transmitted, an actual repetition may be configured using consecutive symbols with the invalid symbol as a boundary. For example, if the time length of one PUSCH repetition is 10 symbols, among the 14 symbols in one slot, symbol indexes #0 to #9 correspond to one nominal repetition, but if symbol indexes #3 to #5 are invalid symbols, the remaining symbol indexes #0 to #2 and symbol indexes #6 to #9 may each configure one actual repetition. If a symbol that cannot be used for PUSCH transmission (e.g., a DL symbol indicated by DCI format 2_0) is included in the resource of one actual repetition, the actual repetition may be dropped and not transmitted.

[0146] For PUSCH repetition type B, frequency hopping may be configured in the UE according to higher layer parameters. For the configured grant-based PUSCH transmission, the frequency hopping mode may follow the configuration in the DCI format that activates it. For PUSCH repetition type B, inter-repetition frequency hopping or inter-slot frequency hopping may be configured. In inter-repetition frequency hopping, frequency hopping is applied according to the nominal repetition number. Here, the nominal repetition number refers to the number of repetitions indicated by RRC signaling, etc. If one nominal repetition passes through (including) a slot boundary (or DL / UL switching point), it is divided into two actual repetitions, one before and one after the slot boundary (or DL / UL switching point), so the actual repetition number may be greater than the nominal repetition number. In inter-slot frequency hopping, frequency hopping may occur at slot boundaries.

[0147] DMRS

[0148] The DMRS associated with a data channel (eg, PDSCH, PUSCH, etc.) may be configured with a front load DMRS and an additional DMRS.

[0149] The transmission time resource location of the frontloaded DMRS may be determined based on the mapping type of the data channel, the starting symbol location of the data channel, the number of DMRS symbols, and the like.

[0150] The mapping type of the data channel (e.g., PDSCH mapping type, PUSCH mapping type, etc.) may be set to Type A or Type B (e.g., slot-based or non-slot-based). For example, the mapping type of the data channel may be set by RRC signaling.

[0151] In slot-based transmission, the transmission start symbol position of the frontloaded DMRS may be the third or fourth symbol within the transmission resource of the data channel, and information indicating whether the transmission start symbol position of the DMRS is the third or fourth transmission symbol of the data channel may be provided in the PBCH.

[0152] The frontloaded DMRS may consist of one or two consecutive symbols (i.e., single-symbol DMRS or double-symbol DMRS), and information regarding the number of symbols may be provided by RRC signaling.

[0153] The symbol mapping type within the transmission resource of the frontloaded DMRS may be configured into two types (e.g., Type 1 or Type 2), and configuration information regarding this may be provided by RRC signaling. Type 1 can support four or eight antenna ports using F-CDM (i.e., code division multiplexing (CDM) in the frequency domain), T-CDM (i.e., CDM in the time domain), and / or FDM, depending on whether the DMRS symbol length is one or two. Type 2 can support six or twelve antenna ports using F-CDM, T-CDM, and / or FDM, depending on whether the DMRS symbol length is one or two.

[0154] The number of additional DMRSs may be any one of 0, 1, 2, or 3. The maximum number of additional DMRSs to be transmitted may be determined by RRC signaling, and the number of additional DMRSs actually transmitted within each maximum number of DMRSs and the transmission symbol positions may be determined by the length of the OFDM symbol in which the data channel is transmitted.

[0155] The number of symbols and mapping type of each additional DMRS may be determined to be the same as the number of symbols and mapping type of the frontloaded DMRS.

[0156] 8A and 8B are diagrams showing examples of DMRS symbol positions to which the present disclosure can be applied. Fig. 8A shows an example of mapping type A, where the starting symbol position (l0)=2, and may be defined as a symbol position relative to a slot boundary. Fig. 8B shows an example of mapping type B, where the symbol position may be defined as a symbol position relative to the start of transmission.

[0157] The position and number of PUSCH DMRS symbols may vary depending on the number of symbols used to transmit the PUSCH. For example, when PUSCH repetition type B is applied, the position and number of DMRS symbols may be determined based on the actual repetition length of the PUSCH. In this case, the position of the DMRS within a slot may change for each PUSCH repetition.

[0158] Start and end of time domain window for uplink channel

[0159] For transmission of uplink channels such as PUCCH and PUSCH, various transmission parameters (or transmission characteristic values) such as transmission power, phase, MCS, frequency resource (e.g., PRB) position, bandwidth (BW), etc. may be set / instructed, thereby enabling the terminal to transmit uplink channels based on the set / instructed transmission parameters.

[0160] In the uplink channel repeated transmission, the terminal can maintain some or all of the transmission parameters applied to the uplink channel transmission for a predetermined time period (e.g., a time domain window). For example, joint channel estimation may be introduced to improve the receiving end performance of the base station. The joint channel estimation at the base station may require that the transmission parameters (e.g., phase, power, etc.) applied to the transmission operation of the terminal be maintained constant.

[0161] In the following examples, joint channel estimation may be interpreted as having the same meaning as DMRS bundling. That is, joint channel estimation / DMRS bundling may include configuring / instructing a terminal to maintain and transmit transmission parameters (e.g., some or all of power, phase, MCS, PRB position, BW, etc.) applied by the terminal in order to perform joint estimation in the time domain for improving the performance of channel estimation, decoding, etc. of the base station, and the terminal performing uplink transmission accordingly.

[0162] In the following examples, the time domain window for joint channel estimation or DMRS bundling may also be simply referred to as the "time domain window (TDW)" to the extent that there is no risk of confusion.

[0163] One of the goals of discussions for improving wireless communication systems is to alleviate the imbalance between uplink and downlink coverage. This imbalance is fundamentally caused by the maximum transmit power of a terminal (e.g., UE) being lower than the maximum transmit power of a base station (e.g., gNB). One solution to address this imbalance is to apply uplink transmission repetition for coverage enhancement (CE). Repetition of uplink transmission, for example, involves repeatedly transmitting the same signal / channel over multiple time units. The performance of such repetitive transmission is highly dependent on the performance of DMRS-based channel estimation. For example, when a signal received at a base station falls in a low signal-to-noise ratio (SNR) region, the accuracy of channel estimation decreases, and poor performance of the repetitive channel estimation can result in degradation of performance gain. To prevent this, DMRS bundling, as described above, can be applied to uplink channels (e.g., PUCCH, PUSCH, etc.) where repetitive transmission is configured / applied. This allows for improved channel estimation performance, and improved performance gains can be expected from repeated channel estimation with improved performance.

[0164] Here, DMRS bundling requires the assumption that various elements defining a channel, such as power consistency, timing advance (TA) command, and spatial filter, are the same between the UE and the BS, and the expected effect can only be achieved by setting / applying the size of the DMRS bundling (or the aforementioned time domain window (TDW)) based on this assumption. In other words, to achieve the effect of improving channel estimation performance through DMRS bundling, the UE and the BS need to have a consistent understanding of the start and end points of the DMRS bundling (or TDW).

[0165] For various reasons, the UE may be unable to maintain / apply the DMRS bundling (or TDW) size set / instructed by the base station. For example, the UE may be unable to directly apply the DMRS bundling (or TDW) size expected by the base station due to differences in the capability to perform uplink transmissions other than DMRS bundling-based uplink transmissions, perform downlink monitoring / reception, or maintain power / phase continuity. The UE needs to divide the DMRS bundling (or TDW) size set / instructed by the base station into smaller sizes, change the start point or end point, or request or notify the base station of such a change.

[0166] The TDW will be explained in more detail below.

[0167] A bundle of time units (e.g., slots) for uplink transmission, which fixes / maintains the transmission characteristics of the terminal to improve the reception performance of the base station for uplink transmission from the terminal, is called a DMRS bundle, and the DMRS bundle may be configured in TDW units. The terminal can perform uplink transmission while ensuring phase continuity, power consistency, etc. within the TDW for joint channel estimation by the base station. That is, within the configured TDW, the terminal may be configured / instructed not to perform operations that violate phase continuity, power consistency, etc. Such a TDW may be configured simultaneously when joint channel estimation is enabled by higher layer (e.g., RRC) signaling.

[0168] For joint channel estimation for uplink repeated transmissions, all repetitions may be covered by one or more consecutive / non-consecutive TDWs. Each configured TDW may include one or more consecutive physical slots. The length of the configured TDW may be explicitly set within a predetermined maximum length L. The start of the first configured TDW may correspond to the first uplink channel transmission. The start of other configured TDWs may be implicitly determined before the first repetition. The end of the last configured TDW may correspond to the end of the last uplink channel transmission. Within one "configured TDW (or nominal TDW)," one or more "actual TDWs" may be implicitly determined. The start of the first actual TDW may correspond to the first uplink channel transmission within the configured TDW. After one actual TDW begins, the UE is expected to maintain power constancy and phase continuity until certain conditions are met, at which point the actual TDW may end. The certain conditions may include the occurrence of an event that violates power constancy and phase continuity (e.g., a DL slot, the actual TDW reaching its maximum duration, DL reception / monitoring, high priority transmission, frequency hopping, precoder cycling, etc.). Whether a new actual TDW is generated when power constancy and phase continuity are violated due to an event may depend on the UE's capability of supporting DMRS bundling resumption. For example, for a UE that supports DMRS bundling resumption, a new actual TDW may be generated after the event, whereas for a UE that does not support DMRS bundling resumption, a new actual TDW may not be generated until the end of the configured TDW.

[0169] In this way, the TDW may be defined based on a hierarchy of configured TDW and actual TDW. After receiving RRC signaling for the configured TDW, the UE may determine / apply one or more actual TDWs within the configured TDW. Such actual TDWs may be implicitly determined / indicated based on an event.

[0170] Here, the decision on the start / end / restart of the actual TDW may be changed depending on the type or characteristics of the event (e.g., whether the UE can predict the event, or the dynamic or semi-static characteristics of the event). If a common rule / understanding on the actual TDW-related operation according to the event type / characteristics between the base station and the UE is not applied, the base station and the UE may operate based on different boundaries of the start / end of the actual TDW (e.g., boundaries where power / phase, etc. are changed). Such inconsistencies may accumulate within the set TDW, causing error propagation problems. Therefore, a method for setting / determining the actual TDW according to the event type / characteristics needs to be specifically defined, but there is currently no clear definition of this.

[0171] This disclosure describes various examples of methods for clearly setting / determining / defining the terminal's behavior related to the start / end / restart of the actual TDW based on an event within the set TDW (or nominal TDW).

[0172] FIG. 9 is a diagram for explaining an example of an uplink channel transmission method of a terminal according to the present disclosure.

[0173] In step S910, the terminal may receive information related to DMRS bundling for an uplink channel from the network.

[0174] The information related to DMRS bundling may be information that explicitly indicates whether DMRS bundling is enabled or disabled by higher layer signaling. DMRS bundling and the time domain window (TDW) may be jointly enabled or disabled.

[0175] For example, information related to DMRS bundling may be provided by higher layer (e.g., RRC) signaling. For example, the uplink channels may include one or more of a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0176] In step S920, the terminal can transmit an uplink channel to the network at one or more actual TDWs within the set TDW.

[0177] Uplink channel transmission within the set TDW may include repeated transmissions.

[0178] For example, one or more actual TDWs included in the set TDW may include a first actual TDW or first and second actual TDWs, and power consistency and phase continuity may be maintained across repeated transmissions of the uplink channel within each actual TDW.

[0179] For example, the first TDW may terminate in connection with an event, and if an event occurs in which power constancy and phase continuity are not maintained over repeated transmissions of the uplink channel, the first actual TDW may terminate before the event.

[0180] Whether to start / generate / resume the second actual TDW may be determined by the terminal based on at least the type of event. Whether to start / generate / resume the second actual TDW may be determined by the terminal based on the terminal capability for a particular event type.

[0181] The event type may be classified as a first type or a second type, or as a dynamic type or a semi-static type, or as a type triggered by DCI / MAC-CE that does not include frequency hopping or the like, or as a type that includes frequency hopping or the like.

[0182] For example, when a first type of event causes a first actual TDW to terminate, whether to generate / restart a second actual TDW in response to the event may be determined based on the capabilities of the terminal. For example, if the terminal's capabilities support DMRS bundling or TDW resumption, the second actual TDW may be generated / restarted in response to the first type of event. Alternatively, if the terminal's capabilities do not support DMRS bundling or TDW resumption, the second actual TDW may not be generated / restarted in response to the first type of event.

[0183] For example, if the first actual TDW is terminated by a second type event, a second actual TDW may be generated / restarted in response to the event. More specifically, if the first actual TDW is terminated by a second type event, a second actual TDW may be generated / restarted regardless of terminal capabilities or always.

[0184] FIG. 10 is a diagram illustrating an example of an uplink channel reception method of a base station according to the present disclosure.

[0185] In step S1010, the base station may transmit information related to DMRS bundling for an uplink channel to the terminal.

[0186] In step S1020, the base station may receive an uplink channel from the terminal at one or more actual TDWs within the set TDW.

[0187] In the example described with reference to FIG. 10, the contents relating to information related to DMRS bundling, the configured TDW, the actual TDW, event type and / or terminal capability-based actual TDW generation / resumption, and the maintenance of power constancy and phase continuity for repeated uplink channel transmissions thereby are the same as those described with reference to FIG. 9, and therefore, redundant description will be omitted.

[0188] The following describes various examples of the present disclosure for actual TDW setting / determination based on event characteristics / type, terminal capabilities, etc.

[0189] Although the DMRS bundles described below will be described for PUSCH and PUCCH with repetition, examples of the present disclosure may be similarly applied to other uplink channels / signals and / or downlink channels / signals.

[0190] The following examples may be applied to the DMRS bundling configuration, or various other methods may be applied. Regardless of the manner in which DMRS bundling is configured for a terminal, the terminal may not apply DMRS bundling and may perform uplink transmission at an individual transmission occasion. For resources corresponding to such individual transmission occasions, the base station may perform joint channel estimation or joint decoding, expecting that DMRS bundling will be applied. That is, if a situation / event occurs in which the terminal cannot apply DMRS bundling, contrary to the base station configuration, and the terminal drops transmission or performs transmission that does not satisfy the conditions for DMRS bundling / joint channel estimation (e.g., maintaining power constancy / phase continuity), the channel estimation / decoding performance of the base station for uplink transmission may be significantly degraded.

[0191] If a DMRS bundle is configured / instructed to a terminal (by prior agreement or signaling) but the terminal cannot apply it, the terminal may report the corresponding slot index, DMRS bundle index, etc. to the base station, or a rule may be defined in advance so that the base station can grasp it. Among the solutions described below, examples of indications in the DMRS resource configured by prior agreement between the base station and the terminal in the terminal's report on the start and / or end of the actual TDW may include the following.

[0192] For example, an example of reporting the start and / or end of the actual TDW may include a case where a plurality of (e.g., two) DMRS resources (e.g., ports, phases, etc.) are configured in advance for the UE, and the UE uses the same DMRS resource within the actual TDW, and uses another DMRS resource based on the start and / or end of the actual TDW. For example, a case may be assumed in which DMRS port 0 and DMRS port 2 are configured for the UE by the base station. When reporting the start of the actual TDW, if the UE used DMRS port 0 in the previous actual TDW, the UE may consider transmitting using DMRS port 2 at the start (slot) of the new actual TDW. Alternatively, when reporting the end of the actual TDW, the UE may report using DMRS port 0 for the last slot of the actual TDW.

[0193] For example, among multiple DMRS resources configured for a terminal, a specific DMRS resource may be configured to indicate the start or end of the actual TDW by prior agreement. For example, a case may be assumed in which DMRS port 0 and DMRS port 2 are configured for the terminal by the base station. In this case, the terminal may indicate / report the start (or end) of the actual TDW based on a slot transmitted using a DMRS with a lower (or higher) DMRS port number by prior agreement. For example, a slot transmitted using DMRS port 0 may indicate / report the start of the actual TDW.

[0194] The following describes an example of setting / determining the actual TDW based on an event.

[0195] The UE may actually set / determine the TDW differently depending on whether the event is predictable or unpredictable. Examples of events that may affect the phase continuity or power constancy of uplink transmission are shown in Table 8 below.

[0196] [Table 8]

[0197] In addition to the above-mentioned exemplary events, a new setting of the actual TDW is required for cases where the maintenance of phase continuity and power constancy of continuous uplink transmissions of a UE is impossible or limited. For example, depending on the type of event, it can be classified into event type 1 (or first type event) and event type 2 (or second type event), and the start time of the actual TDW, whether it is started, etc. can be distinguished depending on the event type. Figure 11 is a diagram showing an example of a TDW to which the present disclosure can be applied.

[0198] In the example of Figure 11, it is assumed that the maximum duration of the actual TDW (i.e., the maximum time length for which the UE can maintain phase continuity and power constancy) is 10 slots based on the UE capability. It is also assumed that the TDW (or nominal TDW) configured for the UE is 16 slots, and the UE performs 16 PUSCH repetitions. In Figure 11, U represents the slot unit.

[0199] In the example of Figure 11(a), the terminal reaches its maximum duration and the actual TDW ends. The terminal can start a new actual TDW (second actual TDW) in the slot immediately adjacent to the end of the first actual TDW.

[0200] 11(b), when event type 1 occurs in the first actual TDW (or before the event occurs), the first actual TDW may end, and after the event ends, a new second actual TDW may be created / restarted.

[0201] For example, event type 1 may correspond to a case where uplink transmission for CE such as joint channel estimation / DMRS bundling is not possible for a time period of one or more slots due to downlink reception, downlink monitoring, other uplink transmission, etc.

[0202] The example in Figure 11(c) shows that when event type 2 occurs in the first actual TDW (or before the event occurs), the first actual TDW is terminated and a new second actual TDW is set immediately after the event ends.

[0203] For example, event type 2 may correspond to a case where a transmission characteristic such as application of a TPC command, application of a timing advance (TA) adjustment, terminal-autonomous TA, frequency hopping, etc. may change, but a new actual TDW can be configured and transmitted in an adjacent slot immediately after the actual TDW that ended due to the event. Such event type 2 may include reaching the maximum duration.

[0204] For example, as shown in Figure 11, event type 1 corresponds to an event in which PUSCH transmission is not possible for one or more slots, and event type 2 corresponds to an event in which a new actual TDW can start in an immediately adjacent slot after the end of the actual TDW. Distinguishing events in this manner corresponds to an example of the present disclosure, and events can be distinguished based on various criteria as described below.

[0205] Example 1

[0206] This embodiment includes an example for the creation / restart of a new actual TDW according to the time duration of an event.

[0207] The terminal and the base station can set / define / indicate a time duration for each event by prior agreement. That is, a specific time duration may be mapped to each event. If the time duration of an event is one slot or more (or more), the terminal can determine that after the end of the actual TDW related to the event occurrence, a new actual TDW starts from a slot not included in the time duration of the event. Alternatively, if the time duration of such an event is 0, the terminal can determine that after the end of the actual TDW related to the event occurrence, a new actual TDW starts from the immediately adjacent (or next) slot (because the time duration of the event is 0). To this end, specifically, the base station and the terminal can consider the following operations.

[0208] Example 1-1

[0209] The base station and terminal determine that any event that is not otherwise set / instructed has a time duration of 0 (i.e., the default time duration of the event = 0), and for an event that has a time duration set / instructed to a value other than 0, the terminal can either instruct the start of a new actual TDW or report the time duration of the event to the base station.

[0210] For example, the base station assumes that the time duration of all events is 0 and that the UE is capable of starting a new actual TDW after the event ends. Here, whether a new actual TDW can be started due to the end of an event may depend on the UE's capability. The UE's capability is reported to the base station in advance, and the base station can be assumed to know the UE's capability in advance. If the UE's capability allows the start of a new actual TDW, the base station can expect the start of a new actual TDW in an adjacent slot if the UE does not immediately report / indicate another TDW after ending the actual TDW due to an event. If the UE is unable to transmit for CE, such as joint channel estimation / DMRS bundling, for one or more slots after the end of the actual TDW due to an event, the UE can report to the base station whether a new actual TDW can be started (or the start position).

[0211] For example, assume that the UE has the capability to generate / resume the actual TDW in response to an event. In this case, the UE reports the capability information / signaling to the base station in advance, and it is assumed that the base station already knows the capability of the UE. For example, if the actual TDW ends in the nth slot due to an event, the UE can start a new actual TDW in the n+1th slot without separately reporting / instructing the base station.

[0212] Alternatively, an event may cause the actual TDW to end in the nth slot, and such an event may make transmission for CE such as joint channel estimation / DMRS bundling impossible in one or more slots. Such an event may correspond to, for example, the above-mentioned event type 1. If k slots are required for such an event and transmission for CE such as joint channel estimation / DMRS bundling is impossible in the kth slot, the terminal may start and transmit a new actual TDW in the (n+k)th slot or a subsequent slot, and in such a case, may report / instruct the base station that the new actual TDW will start (or has started) in the (n+k)th slot or a subsequent slot.

[0213] Such reporting / instruction may be performed using specific DMRS resources etc. according to prior agreement, or the actual start point of the TDW may be notified later using UCI, MAC-CE etc.

[0214] Example 1-2

[0215] The base station and the terminal determine that the time duration of all events not otherwise specified is X slots (i.e., the default time duration of an event = X), and for an event having a time duration set / specified to a value other than X, the terminal can specify the start of a new actual TDW or report the time duration of the event to the base station. Here, the value of X may be a value determined by prior agreement between the base station and the terminal, or may be a value set / specified by the base station to the terminal via RRC / MAC-CE / DCI, etc., or may be defined as 1 slot. This takes into consideration that the time duration of most events whose time duration is not 0 is 1 slot.

[0216] For example, the base station may assume that the time duration of all events is X slots, and that the terminal can start a new actual TDW X slots after the event ends, corresponding to the event's time duration. In this case, the time duration of the event, X slots, may be a value designated by the base station and provided to the terminal in advance, and may be configured / indicated to the terminal via RRC, MAC-CE, DCI, etc. In addition, a default value (e.g., 1 slot) for the X value may be considered to be determined by prior agreement, and may be defined as a value used when the base station does not configure / indicate a value for X slots to the terminal. The X value may be periodically updated or may be defined as valid for a certain time interval after being configured / indicated. For example, when the X value is indicated along with PUSCH / PUCCH scheduling for CE such as joint channel estimation / DMRS bundling, the value may be validly applied only to the scheduled PUSCH / PUCCH transmission. For example, when the X value is set / indicated by MAC-CE, RRC signaling, etc., the value may be validly applied for a pre-agreed time interval. When the X value is set / indicated by RRC signaling, whether CE transmission such as joint channel estimation / DMRS bundling is enabled and the time duration of the event may be set / indicated to the terminal simultaneously (or together, or jointly).

[0217] Here, whether a new actual TDW is generated / restarted due to the end of an event may depend on the capability of the terminal. The capability of such a terminal is reported to the base station in advance, and it can be assumed that the base station already knows the capability of such a terminal. If the start of a new actual TDW is possible due to the capability of the terminal, the base station can expect the start of a new actual TDW after X slots unless the terminal issues another report / instruction after terminating the actual TDW due to an event. If the terminal terminates the actual TDW due to an event and starts a new actual TDW at another slot other than after X slots, the terminal can report the start of such actual TDW to the base station.

[0218] For example, assume that the UE has the UE capability to start the actual TDW due to an event. In this case, the UE reports the capability information / signaling to the base station in advance, and the base station is assumed to know the UE's capability in advance. For example, if the actual TDW ends in the nth slot due to an event, the UE may generate / restart a new actual TDW in the (n+X)th slot without separately reporting / instructing the base station.

[0219] Alternatively, the UE may assume that the actual TDW ends in the nth slot due to an event, and the event ends within X slots, allowing the UE to start a new actual TDW before n+X slots, or that the event ends after X slots, allowing the UE to start a new actual TDW after n+X slots. That is, if an event requires k slots and transmission for CE such as joint channel estimation / DMRS bundling is not possible during k slots (k>X), the UE may start and transmit a new actual TDW in the n+kth slot or a subsequent slot. In this case, the UE may report / indicate to the base station that a new actual TDW will start (or has started) in a slot after the n+kth slot.

[0220] Alternatively, if event type 2 among the above-mentioned event types occurs and the actual TDW ends in the nth slot, the UE may generate / restart a new actual TDW after the n+1th slot. In this case, the UE may report / instruct the base station that a new actual TDW will start (or has started) in the n+1th slot.

[0221] Such reporting / instruction may be performed by a specific DMRS resource or the like according to a prior agreement, or the actual start point of the TDW may be notified later using UCI, MAC-CE, or the like.

[0222] In the above example, the UE may report the start of the actual TDW and / or the end of the actual TDW by prior agreement with the base station. If the operation to report the start / end of the actual TDW is configured / defined by prior agreement, and the UE does not report the start / end of the actual TDW, the base station may assume that the UE does not configure and transmit the actual TDW, and may perform operations such as estimation / decoding for uplink transmission accordingly.

[0223] Example 2

[0224] This embodiment includes an example of generating / resuming a new actual TDW according to the type of event. In this embodiment, the event type is classified into a semi-static type and a dynamic type.

[0225] The UE can consider that the actual TDW (i.e., the first actual TDW) ends due to an event within the set TDW, and the base station and the UE must have the same understanding regarding whether to start a new actual TDW (i.e., the second actual TDW) after such an event. If the base station and the UE do not agree on whether to start or the boundary of the actual TDW due to such an event, it may lead to a degradation of the reception performance of the base station. Therefore, the UE can operate according to the following example regarding whether to generate / restart a new actual TDW depending on the event type.

[0226] Example 2-1

[0227] If the first actual TDW ends within the TDW set by any type of event, the terminal may expect to start (or generate / restart) a new second actual TDW after the event.

[0228] For example, the base station can be expected to start (or generate / restart) a new second actual TDW after a first actual TDW ends for all types of events, regardless of the capabilities of the terminal (or always). If the first actual TDW ends due to a terminal event within the set TDW, the base station can assume that transmissions after the terminal event within the set TDW are the start of a new second actual TDW.

[0229] Since the base station expects the terminal to start the second actual TDW for transmissions after the end of the first actual TDW due to an event within the configured TDW, the terminal may not report / instruct the base station to start (or generate / restart) the second actual TDW, which may be agreed upon in advance (by signaling between the base station and the terminal) or may be predefined (without signaling between the base station and the terminal). In this case, the terminal may start the second actual TDW for transmissions after the end of the first actual TDW due to an event within the configured TDW, and therefore may report only the end point of the first actual TDW to the base station.

[0230] Alternatively, the terminal may report / instruct the base station to start (or generate / resume) the actual TDW by prior agreement or predefinition. Therefore, if the terminal does not start the actual TDW in a transmission after the end of the actual TDW due to an event within the set TDW, the terminal may not report / instruct the base station to start such an actual TDW, but may report / instruct the base station to start the actual TDW if the terminal's transmission within the set TDW is the start of the actual TDW.

[0231] The above-mentioned report / instruction regarding the start / end of the actual TDW may be performed by a DMRS resource or a UCI / MAC-C, etc., according to a prior agreement.

[0232] Example 2-2

[0233] Depending on the capabilities of the terminal, a distinction may be made between terminals that can start a new second actual TDW for transmission after the first actual TDW that is terminated due to an event within the set TDW and terminals that cannot.

[0234] If the terminal's capability supports it, the terminal may be expected to start (or generate / restart) a new second actual TDW after an event when the first actual TDW in the TDW set by all types of events has expired. If the terminal's capability does not support it, the terminal may be expected not to start (or generate / restart) a new second actual TDW after an event when the first actual TDW in the TDW set by all types of events has expired.

[0235] For example, the basic operation of a terminal understood by a base station is that whether or not to generate / restart an actual TDW is determined by the terminal capability. A capable terminal can understand that after the end of a first actual TDW due to an event within the configured TDW, transmission within the configured TDW means the start of a second actual TDW. A non-capable terminal can understand that after the end of a first actual TDW due to an event within the configured TDW, transmission within the configured TDW does not mean the start of a second actual TDW.

[0236] The UE may report its capability of generating / resuming a new actual TDW after an event in the set TDW to the base station in advance via RRC / UCI, etc. This allows the base station and the UE to assume a common understanding of such UE capabilities.

[0237] Based on this, for a capable terminal, the base station can assume that after the first actual TDW ends due to an event within the configured TDW, transmission within the configured TDW is the start (or generation / restart) of a new second actual TDW. In this case, the terminal can report / instruct the base station on the end point of the first actual TDW without separately reporting / instructing the base station on the start point of the second actual TDW.

[0238] For a terminal that does not have the capability, the base station may expect that the actual TDW does not exist for transmission within the set TDW after the first actual TDW ends due to an event within the set TDW. If the terminal starts the second actual TDW contrary to the base station's expectations, the terminal may report / indicate the start of the second actual TDW.

[0239] The above-mentioned report / instruction regarding the start / end of the actual TDW may be performed by a DMRS resource or a UCI / MAC-CE according to a prior agreement.

[0240] Example 2-3

[0241] Whether a new second actual TDW can be started (or generated / restarted) after a first actual TDW has ended due to an event within the set TDW may be set / determined depending on the type of the event and / or the capabilities of the terminal.

[0242] For example, for a first type event, whether to generate / restart the second actual TDW may be determined depending on the terminal capability, and for a second type event, whether to generate / restart the second actual TDW may be determined regardless of (or always) the terminal capability.

[0243] The types of events may be distinguished by various criteria. For example, the first type may be a dynamic type, and the second type may be a semi-static type. The dynamic type may correspond to an event in which the UE / BS has no or low predictability for the occurrence / end of the event. The semi-static type may correspond to an event in which the UE / BS has high or high predictability for the occurrence / end of the event. For example, a dynamic type event may correspond to an event in which the BS cannot predict the end of the actual TDW of the UE in advance, or in which the BS cannot predict the end time of the actual TDW or the prediction accuracy is low. For example, a semi-static type event may correspond to an event in which the BS can predict the end of the actual TDW of the UE in advance. For example, frequency hopping operates according to a preset / defined pattern, making it easy or possible for the UE / BS to predict, and therefore may correspond to a semi-static type or second type event. Events triggered by dynamic instructions other than frequency hopping (e.g., methods in which the terminal applies relatively quickly, such as DCI / MAC-CE, other than methods in which the terminal applies relatively late, such as RRC signaling) are difficult for the terminal to predict and may therefore be classified as dynamic or type 1 events.

[0244] The terminal and the base station can distinguish between types of events (e.g., between a first type and a second type, or between a semi-static event and a dynamic event) and determine / expect whether a new TDW will actually start. Possible events can be distinguished between a first type and a second type, or between a semi-static event and a dynamic event, by prior agreement or pre-definition between the base station and the terminal. The terminal operation can be defined / determined / expected depending on the type of event.

[0245] According to the above exemplary criteria for distinguishing event types, the example events in Table 8 can be distinguished into a first type (eg, dynamic type) and a second type (eg, semi-static type) as follows:

[0246] [Table 9]

[0247] Alternatively, events can be classified as semi-static or dynamic events based on their time duration. For example, an event that consumes a time duration of one or more slots and is not expected to be able to generate / restart a new actual TDW in the immediately adjacent slot after the actual TDW ends may be classified as a semi-static event. An event that consumes a time duration of less than one slot and is expected to be able to generate / restart a new actual TDW in the immediately adjacent slot after the actual TDW ends may be classified as a dynamic event. According to the above exemplary criteria for distinguishing event types, the example events in Table 8 can be classified as a first type (e.g., dynamic type) and a second type (e.g., semi-static type) as follows:

[0248] [Table 10]

[0249] In addition to the above-mentioned examples of events, the types of all possible events may be distinguished, and the events to which the present disclosure applies are not limited to the above-mentioned examples. Furthermore, events to be distinguished may be assumed to belong to either the first type or the second type (or either the dynamic type or the semi-static type), and no assumption is made if an event falls into multiple types. Alternatively, events that are pre-agreed upon or pre-defined between the base station and the terminal may be assumed to be the first type, and the remaining events may all be assumed to be the second type.

[0250] According to this embodiment, when a first actual TDW is terminated by a semi-static event (or a second type event) within a set TDW, the terminal may be expected to start a new second actual TDW after the event, regardless of its capability. Also, when a first actual TDW is terminated by a dynamic event (or a first type event) within a set TDW, whether the terminal starts a new second actual TDW after the event may be determined depending on the terminal capability. That is, when a first actual TDW is terminated by a dynamic / first type event within a set TDW, a terminal with capability may be expected to start a new second actual TDW, and conversely, a terminal without capability may be expected not to start a new second actual TDW.

[0251] After the first actual TDW ends due to a semi-static (or second type) event within the set TDW, the base station can determine that the UE's transmission within the set TDW is the start of a new second actual TDW. Therefore, the UE does not need to separately report / instruct the base station about the start of the actual TDW. The UE can also report / instruct the base station only about the end point of the actual TDW.

[0252] When a first actual TDW ends due to a dynamic (or first type) event within a set TDW, the base station can determine that a transmission from a capable terminal after the event within the set TDW is the start (or generation / resumption) of a second actual TDW. Therefore, a capable terminal does not need to separately report / instruct the base station about the start of the actual TDW. A capable terminal can also report / instruct the base station only about the end point of the actual TDW.

[0253] When a first actual TDW ends due to a dynamic (or first type) event within a set TDW, the base station can determine that transmission from a terminal that does not have the capability after the event within the set TDW does not mean the start (or generation / resumption) of a second actual TDW. Therefore, when a terminal that does not have the capability generates / restarts a second actual TDW and transmits after a dynamic (or first type) event within the set TDW, the terminal can report / instruct the base station about the start point of such second actual TDW. The terminal that does not have the capability can also report / instruct the base station about the end point of the actual TDW.

[0254] The above-mentioned report / instruction regarding the start / end of the actual TDW may be performed by a DMRS resource or a UCI / MAC-CE according to a prior agreement.

[0255] The above-described criteria for distinguishing event types are merely exemplary, and event types may be distinguished by other criteria depending on the characteristics / attributes of the events. That is, the scope of the present disclosure includes whether the generation / resumption of a new actual TDW within the set TDW is based on terminal capabilities (e.g., in the case of a first type event) or operates regardless of terminal capabilities (e.g., in the case of a second type event) depending on the type of event related to the termination of the actual TDW within the set TDW, and the scope of the present disclosure is not limited to examples of events belonging to the type.

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

[0257] FIG. 12 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0258] Referring to FIG. 12, the first device 100 and the second device 200 can transmit and receive wireless signals using various wireless connection technologies (e.g., LTE, NR).

[0259] The first device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in this disclosure.

[0260] For example, the processor 102 may process information in the memory 104 to generate first information / signal and then transmit a wireless signal including the first information / signal from the transceiver 106. Additionally, the processor 102 may receive a wireless signal including second information / signal from the transceiver 106 and then store information obtained from signal processing of the second information / signal in the memory 104.

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

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

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

[0264] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions, and / or collections of instructions.

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

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

[0267] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented without being combined with other components or features. It is also possible to combine some components and / or features to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to form embodiments, or may be included as new claims by amendment after filing.

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

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

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

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

Claims

1. A method performed by a terminal, comprising: receiving configuration information related to demodulation reference signal (DMRS) bundling for an uplink channel; transmitting the uplink channel in a first actual TDW and a second actual TDW within a time domain window (TDW); the first actual TDW ends before an event in which power constancy and phase continuity are not maintained across repeated transmissions of the uplink channel; The method of claim 1, wherein the second actual TDW is produced in response to the event being a first type event, depending on a capability of the terminal related to whether the terminal supports resumption of the DMRS bundling.

2. The method of claim 1 , wherein the first type event includes an event triggered by downlink control information (DCI) other than frequency hopping or by medium access control-control element (MAC-CE).

3. The method of claim 1 , wherein the second actual TDW is produced in response to the event being a second type event.

4. The method of claim 3 , wherein the second type event includes frequency hopping or an event not triggered by DCI or by MAC-CE.

5. 2. The method of claim 1, wherein the second actual TDW is produced in response to the event being a second type event regardless of the capabilities of the terminal.

6. The method of claim 1 , wherein the configuration information related to the DMRS bundling is provided by higher layer signaling.

7. The method of claim 1 , wherein the uplink channel comprises at least one of a physical uplink shared channel (PUCCH) or a physical uplink control channel (PUSCH).

8. A terminal, at least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor receiving configuration information related to demodulation reference signal (DMRS) bundling for uplink channels from a network via the at least one transceiver; and transmitting the uplink channel to the network via the at least one transceiver in a first actual TDW and a second actual TDW within a time domain window (TDW); the first actual TDW ends before an event in which power constancy and phase continuity are not maintained across repeated transmissions of the uplink channel; The terminal, wherein the second actual TDW is created in response to the event being a first type event, depending on a capability of the terminal related to whether the terminal supports resumption of the DMRS bundling.

9. transmitting configuration information related to demodulation reference signal (DMRS) bundling for uplink channels from a base station to a terminal; receiving the uplink channel from the terminal by the base station in a first actual TDW and a second actual TDW within a time domain window (TDW); the first actual TDW ends before an event in which power constancy and phase continuity are not maintained across repeated transmissions of the uplink channel; The method of claim 1, wherein the second actual TDW is produced in response to the event being a first type event, depending on a capability of the terminal related to whether the terminal supports resumption of the DMRS bundling.

10. at least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor transmitting configuration information related to demodulation reference signal (DMRS) bundling for uplink channels to a terminal via the at least one transceiver; The uplink channel is received from the terminal via the at least one transceiver in a first actual TDW and a second actual TDW within a time domain window (TDW); the first actual TDW ends before an event in which power constancy and phase continuity are not maintained across repeated transmissions of the uplink channel; The base station, wherein the second actual TDW is created in response to the event being a first type event, depending on the capability of the terminal related to whether the terminal supports resumption of the DMRS bundling.

11. at least one processor; and at least one computer memory operably coupled to said at least one processor and storing instructions for performing the method of any one of claims 1 to 7 when executed by said at least one processor.

12. At least one non-transitory computer-readable medium storing at least one instruction, A non-transitory computer readable medium, the at least one instruction being executed by at least one processor to control an apparatus to perform the method of any one of claims 1 to 7.

Images