Method and apparatus for transmitting or receiving configured licensed PUSCH in wireless communication system

By using the HARQ process and packet delay budget value to control the retransmission of CG PUSCH in the wireless communication system, the problems of packet delay and multi-logical channel support in CG PUSCH transmission are solved, and efficient and low-power wireless communication is achieved.

CN119032619APending Publication Date: 2024-11-26LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036372.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-28
Filing Date
2023-04-27
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The existing wireless communication system is difficult to effectively manage packet delay requirements when sending and receiving CG PUSCH, resulting in increased service delays and difficult to support CG PUSCH transmissions of multiple logical channels, affecting user experience and system efficiency.

Method used

By transmitting configuration information between the user equipment and the base station, the CG timer of the hybrid automatic repeat request (HARQ) process is started, and the CG PUSCH is retransmitted before the timer stops, and the number of retransmissions is controlled based on the packet delay budget value to achieve effective CG PUSCH transmission and supports CG PUSCH transmission of multiple logical channels.

Benefits of technology

Effectively manage packet delays, improve CG PUSCH transmission efficiency, support the transmission of multiple logical channels, is suitable for high-efficiency XR operation, reduces power consumption and improves the energy efficiency of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032619A_ABST
    Figure CN119032619A_ABST
Patent Text Reader

Abstract

A method and apparatus for transmitting or receiving a configuration grant PUSCH in a wireless communication system are disclosed. A method according to an embodiment of the present disclosure may comprise the steps of: receiving configuration information related to a CG configuration from a base station; transmitting an initial CG PUSCH for the first TB to the base station on the basis of the configuration information, in which a CG timer for an HARQ process is started during transmission of the initial CG PUSCH; and after the initial CG PUSCH transmission to the base station, repeatedly transmitting the CG PUSCH for the retransmission of the first TB until the CG timer is stopped.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting and receiving a configured grant (CG) PUSCH (Physical Uplink Shared Channel) in a wireless communication system. Background Art

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, the mobile communication system has been extended to data services as well as voice services, and currently, the explosive growth of services has led to resource shortages, and users have demanded faster services, thus requiring more advanced mobile communication systems.

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

[0004] Technical issues

[0005] The technical objective of the present disclosure is to provide a method and apparatus for sending and receiving CG PUSCH for CG configuration while considering service delay requirements.

[0006] In addition, an additional technical objective of the present disclosure is to provide a method and apparatus for sending and receiving CG PUSCH for multiple logical channels using one or more CG configurations.

[0007] The technical objectives achieved by the present disclosure are not limited to the above-mentioned technical objectives, and other technical objectives not described herein will be clearly understood by those skilled in the relevant art from the following description.

[0008] Technical Solution

[0009] According to an aspect of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system may include: receiving configuration information related to a configured grant (CG) configuration from a base station; based on the configuration information, sending an initial CG PUSCH (physical uplink shared channel) for a first transport block (TB) to the base station, wherein a CG timer for a hybrid automatic repeat request (HARQ) process is started at the time of transmission of the initial CG PUSCH; and after the transmission of the initial CG PUSCH, repeatedly sending a CG PUSCH for retransmission of the first TB to the base station until the CG timer stops. Based on a packet delay budget (PDB) value related to the first TB, the retransmission of the first TB may be stopped as the CG timer stops.

[0010] According to an additional aspect of the present disclosure, a method performed by a base station in a wireless communication system may include: sending configuration information related to a configured grant (CG) configuration to a user equipment (UE); based on the configuration information, receiving an initial CG PUSCH (physical uplink shared channel) for a first transport block (TB) from the UE, wherein a CG timer for a hybrid automatic repeat request (HARQ) process is started at the time of transmission of the initial CG PUSCH; and after reception of the initial CG PUSCH, repeatedly receiving a CG PUSCH for retransmission of the first TB from the UE until the CG timer is stopped. Based on a packet delay budget (PDB) value related to the first TB, the retransmission of the first TB may be stopped as the CG timer stops.

[0011] Technical Effects

[0012] According to an embodiment of the present disclosure, efficient CG PUSCH transmission is possible according to services by considering packet delay requirements.

[0013] In addition, according to an embodiment of the present disclosure, it is possible to use one or more CG configurations to send and receive CG PUSCH for multiple logical channels.

[0014] In addition, according to the embodiments of the present disclosure, CG resources can be efficiently operated to support XR (Extended Reality) operations.

[0015] Effects achievable by the present disclosure are not limited to the above-described effects, and other effects not described herein may be clearly understood by those skilled in the art through the following description.

[0016] BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0019] Figure 2 The figure illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0020] Figure 3 The diagram illustrates a resource grid in a wireless communication system to which the present disclosure may be applied.

[0021] Figure 4 The figure illustrates physical resource blocks in a wireless communication system to which the present disclosure can be applied.

[0022] Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which the present disclosure can be applied.

[0023] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0024] Figure 7 The diagram illustrates a scheme for multiple TRP transmissions in a wireless communication system to which the present disclosure can be applied.

[0025] Figure 8 Illustrate the structure / pattern of the group of pictures.

[0026] Fig. 9 A licensing configuration of multiple configurations according to an embodiment of the present disclosure is illustrated.

[0027] Fig.10 A licensing configuration of a single configuration according to an embodiment of the present disclosure is illustrated.

[0028] Fig.11 A signaling process between a network and a UE for a method of transmitting and receiving a configured grant PUSCH according to an embodiment of the present disclosure is illustrated.

[0029] Fig.12 is a diagram illustrating operation of a UE for a method of transmitting and receiving a configured grant PUSCH according to an embodiment of the present disclosure.

[0030] Fig.13 is a diagram illustrating an operation of a base station for a method of transmitting and receiving a configured grant PUSCH according to an embodiment of the present disclosure.

[0031] Fig.14 A block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION

[0032] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description to be disclosed by the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, rather than to represent the only embodiment in which the present disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the relevant art will appreciate that the present disclosure can be implemented without these specific details.

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

[0034] In the present disclosure, when an element is referred to as being "connected", "combined" or "linked" to another element, it may include an indirect connection relationship between another element and a direct connection relationship. In addition, in the present disclosure, the term "comprising" or "having" specifies the presence of the mentioned features, steps, operations, components and / or elements, but does not exclude the presence or addition of one or more other features, stages, operations, components, elements and / or groups thereof.

[0035] In the present invention, terms such as "first", "second", etc. are only used to distinguish one element from another element and are not used to limit the elements, and unless otherwise specified, they do not limit the order or importance between the elements. Therefore, within the scope of the present disclosure, the first element in an embodiment may be referred to as the second element in another embodiment, and similarly, the second element in an embodiment may be referred to as the first element in another embodiment.

[0036] The terms used in this disclosure are intended to describe specific embodiments rather than to limit the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term "and / or" used in this disclosure may refer to one of the related enumerated items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise stated, the " / " between words in the present invention has the same meaning as "and / or".

[0037] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the wireless communication network may be performed in a process in which a device (e.g., a base station) controlling the corresponding wireless communication network controls the network and sends or receives signals, or may be performed in a process in which a terminal associated with the corresponding wireless network sends or receives signals between the network or the terminal.

[0038] In the present disclosure, sending or receiving a channel includes the meaning of sending or receiving information or signals through the corresponding channel. For example, sending a control channel means sending control information or control signals through the control channel. Similarly, sending a data channel means sending data information or data signals through the data channel.

[0039] Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, the transmitter may be a part of a base station, and the receiver may be a part of a terminal. In the uplink, the transmitter may be a part of a terminal, and the receiver may be a part of a base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. The base station (BS) may be replaced by terms such as a fixed station, a node B, an eNB (evolved node B), a gNB (next generation node B), a BTS (base station transceiver system), an access point (AP), a network (5G network), an AI (artificial intelligence) system / module, an RSU (roadside unit), a robot, a drone (UAV: unmanned aerial vehicle), an AR (augmented reality) device, a VR (virtual reality) device, and the like. In addition, the terminal may be fixed or mobile, and may be replaced by terms such as UE (user equipment), MS (mobile station), UT (user terminal), MSS (mobile subscriber station), SS (subscriber station), AMS (advanced mobile station), WT (wireless terminal), MTC (machine type communication) device, M2M (machine to machine) device, D2D (device to device) device, vehicle, RSU (roadside unit), robot, AI (artificial intelligence) module, drone (UAV: unmanned aerial vehicle), AR (augmented reality) device, VR (virtual reality) device, etc.

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

[0041] In order to make the description clearer, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited to this. LTE means the technology after 3GPP TS (Technical Specification) 36.xxx version 8. Specifically, the LTE technology in or after 3GPP TS 36.xxx version 10 is called LTE-A, and the LTE technology in or after 3GPP TS 36.xxx version 13 is called LTE-A pro. 3GPP NR means the technology in or after TS 38.xxx version 15. LTE / NR can be referred to as a 3GPP system. "xxx" means the detailed number of the standard document. LTE / NR can generally be referred to as a 3GPP system. For the background technology, terms, abbreviations, etc. used to describe the present disclosure, reference can be made to the matters described in the standard documents disclosed before the present disclosure. For example, reference can be made to the following documents.

[0042] For 3GPP LTE, reference may 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 (Overall Description), and TS 36.331 (Radio Resource Control).

[0043] For 3GPP NR, you can refer to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (NR and NG-RAN (Next Generation Radio Access Network) overall description), and TS 38.331 (Radio Resource Control Protocol Specification).

[0044] Abbreviations of terms that may be used in the present disclosure are defined as follows.

[0045] -BM: Beam Management

[0046] -CQI: Channel Quality Indicator

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

[0048] -CSI: Channel State Information

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

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

[0051] -DMRS: Demodulation Reference Signal

[0052] -FDM: Frequency Division Multiplexing

[0053] - FFT: Fast Fourier Transform

[0054] -IFDMA: Interleaved Frequency Division Multiple Access

[0055] -IFFT: Inverse Fast Fourier Transform

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

[0057] -L1-RSRQ: Layer 1 reference signal reception quality

[0058] -MAC: Media Access Control

[0059] -NZP: Non-Zero Power

[0060] - OFDM: Orthogonal Frequency Division Multiplexing

[0061] -PDCCH: Physical Downlink Control Channel

[0062] -PDSCH: Physical Downlink Shared Channel

[0063] -PMI: Precoding matrix indicator

[0064] -RE: Resource Element

[0065] -RI: Rank Indicator

[0066] -RRC: Radio Resource Control

[0067] -RSSI: Received Signal Strength Indicator

[0068] - Rx: Receive

[0069] - QCL: Quasi Co-sited

[0070] -SINR: Signal to Interference and Noise Ratio

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

[0072] -TDM: Time Division Multiplexing

[0073] -TRP: Transmit and Receive Point

[0074] -TRS: Tracking Reference Signal

[0075] -Tx: Send

[0076] -UE: User Equipment

[0077] -ZP: Zero Power

[0078] Overall system

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

[0080] The new RAT system including NR uses an OFDM transmission method or a transmission method similar thereto. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system follows the parameters of the existing LTE / LTE-A as is, but may support a wider system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets may coexist in one cell.

[0081] A parameter set corresponds to one subcarrier spacing in the frequency domain. As the reference subcarrier spacing is scaled by an integer N, different parameter sets can be defined.

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

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

[0084] Figure 2 The diagram illustrates a frame structure in a wireless communication system to which the present disclosure may be applied.

[0085] The NR system may support multiple parameter sets. Here, the parameter set may be defined by subcarrier spacing and cyclic prefix (CP) overhead. Here, multiple subcarrier spacings may be derived by scaling the basic (reference) subcarrier spacing by an integer N (or, μ). In addition, although it is assumed that very low subcarrier spacings are not used in very high carrier frequencies, the parameter set used may be selected independently of the frequency band. In addition, various frame structures according to multiple parameter sets may be supported in the NR system.

[0086] In the following, OFDM parameter sets and frame structures that can be considered in the NR system are described. Multiple OFDM parameter sets supported in the NR system can be defined as shown in Table 1 below.

[0087] [Table 1]

[0088]

[0089] NR supports multiple parameter sets (or subcarrier spacing (SCS)) for supporting various 5G services. For example, when the SCS is 15kHz, it supports wide areas of traditional cellular bands; when the SCS is 30kHz / 60kHz, it supports dense cities, lower latency and wider carrier bandwidth; and when the SCS is 60kHz or higher, it supports bandwidths exceeding 24.25GHz to overcome phase noise.

[0090] The NR band is defined as two types of frequency ranges (FR1, FR2). FR1, FR2 can be configured as shown in Table 2 below. In addition, FR2 may mean millimeter wave (mmW).

[0091] [Table 2]

[0092]

[0093] Regarding the frame structure in the NR system, the sizes of various fields in the time domain are expressed as T c =1 / (Δf max ·N f ) is a multiple of the time unit. Here, Δf max i is 480·10 3 Hz, and N f is 4096. Downlink and uplink transmissions are configured (organized) to have duration T f= 1 / (Δf max N f / 100)·T c =10ms radio frame. Here, the radio frame is configured with 10 subframes, each of which has T sf =(Δf max N f / 1000)·T c In this case, there may be one frame set for the uplink and one frame set for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should start T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c For subcarrier spacing configuration μ, the time slots are arranged in n subframes. s μ ∈{0,..., N slot subframe,μ -1} and in the radio frame the number is incremented by n s,f μ ∈{0,..., N slot frame,μ -1}. A time slot is configured with Nsymb slot consecutive OFDM symbols, and N symb slot Determined according to CP. Time slot n in a subframe s μ The beginning of the OFDM symbol n in the same subframe s μ N symb slot All terminals may not perform transmission and reception at the same time, which means that all OFDM symbols of a downlink time slot or an uplink time slot may not be used.

[0094] Table 3 shows the number of OFDM symbols per time slot in a normal CP (N symb slot ), the number of time slots per radio frame (N slot frame,μ ) and the number of time slots per subframe (N slot subframe,μ ), and Table 4 represents 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.

[0095] [Table 3]

[0096]

[0097] [Table 4]

[0098]

[0099] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3, 1 subframe can include 4 time slots. Figure 2 1 subframe = {1, 2, 4} shown in is an example, and the number of slots that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot may include 2, 4, or 7 symbols or more or less symbols.

[0100] Regarding the physical resources in the NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered. Hereinafter, the physical resources that can be considered in the NR system will be described in detail.

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

[0102] Figure 3 A resource grid in a wireless communication system to which the present disclosure may be applied is illustrated.

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

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

[0105] -OffsetToPointA for the primary cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block, which is used by the terminal for initial cell selection. Assuming a subcarrier spacing of 15kHz for FR1 and a subcarrier spacing of 60kHz for FR2, it is expressed in resource blocks.

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

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

[0108] [Formula 1]

[0109]

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

[0111] [Formula 2]

[0112]

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

[0114] Figure 4 The figure illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied. Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which the present disclosure may be applied.

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

[0116] A carrier includes multiple subcarriers in the frequency domain. An RB (resource block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (bandwidth part) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to one parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed through activated BWPs, and only one BWP may be activated for one terminal. In a resource grid, each element is called a resource element (RE) and may map one complex symbol.

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

[0118] At the same time, even in one CC configured to the terminal, the base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring time slot, and the PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when the UE is congested in a specific BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering the frequency domain inter-cell interference elimination between adjacent cells, etc., some full-bandwidth middle spectrums can be excluded, and BWPs on two edges can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP to a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP in the configured DL / UL BWP at a specific time (through L1 signaling or MAC CE (control element) or RRC signaling, etc.). In addition, the base station can indicate switching to other configured DL / UL BWPs (through L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when the timer value expires, it can switch to the determined DL / UL BWP. Here, the activated DL / UL BWP is defined as the active DL / UL BWP. However, when the terminal performs the initial access procedure or sets up the RRC connection, the configuration on the DL / UL BWP may not be received, so the DL / UL BWP assumed by the terminal in these cases is defined as the initial active DL / UL BWP.

[0119] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0120] In a wireless communication system, a terminal receives information from a base station via a downlink and transmits information to the base station via an uplink. The information transmitted and received by the base station and the terminal includes data and various control information, and there are various physical channels according to the type / usage of the information they transmit and receive.

[0121] When the terminal is turned on or newly enters a cell, it performs an initial cell search including synchronization with a base station (S601). For the initial cell search, the terminal can synchronize with the base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station, and obtain information such as a cell identifier (ID). Then, the terminal can obtain broadcast information in the cell by receiving a physical broadcast channel (PBCH) from the base station. At the same time, the terminal can check the downlink channel status by receiving a downlink reference signal (DL RS) in the initial cell search phase.

[0122] The terminal that has completed the initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).

[0123] Meanwhile, when the terminal accesses the base station for the first time or has no radio resources for signal transmission, it may perform a random access (RACH) procedure on the base station (S603 to S606). For the random access procedure, the terminal may send a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605), and may receive a response message to the preamble through a PDCCH and a corresponding PDSCH (S604 and S606). The contention-based RACH may additionally perform a contention resolution procedure.

[0124] The terminal that subsequently performs the above process may perform PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) through the PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and the format varies according to its purpose of use.

[0125] At the same time, the control information sent by the terminal to the base station through the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgement / non-acknowledgement) signal, CQI (channel instruction indicator), PMI (precoding matrix indicator), RI (rank indicator), etc. For the 3GPP LTE system, the terminal can send the above-mentioned CQI / PMI / RI and other control information through PUSCH and / or PUCCH.

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

[0127] [Table 5]

[0128]

[0129] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information (e.g., UL / SUL (supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to a transport block (TB) (e.g., MCS (modulation coding and scheme), NDI (new data indicator), RV (redundancy version), etc.), information related to HARQ (hybrid-automatic repeat and request) (e.g., process number, DAI (downlink assignment index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information related to scheduling of PUSCH (e.g., PUSCH power control, etc.), and control information included in each DCI format may be predefined.

[0130] DCI format 0_0 is used to schedule PUSCH in one cell. Information included in DCI format 0_0 is CRC (Cyclic Redundancy Check) scrambled by C-RNTI (Cell Radio Network Temporary Identifier) ​​or CS-RNTI (Configured Scheduling RNTI) or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0131] DCI format 0_1 ​​is used to indicate the scheduling of one or more PUSCHs or to configure grant (CG) downlink feedback information to a terminal in one cell. The information included in DCI format 0_1 ​​is scrambled and transmitted by C-RNTI or CS-RNTI or SP-CSI-RNTI (semi-persistent CSI RNTI) or MCS-C-RNTI.

[0132] DCI format 0_2 is used to schedule PUSCH in one cell. Information included in DCI format 0_2 is scrambled and transmitted by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

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

[0134] DCI format 1_0 is used to schedule PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled and transmitted by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0135] DCI format 1_1 is used to schedule PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled and transmitted by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0136] DCI format 1_2 is used to schedule PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0137] Quasi-co-located (QCL)

[0138] The antenna port is defined so that the channel of the symbol transmitted in the antenna port can be inferred from the channels of other symbols transmitted in the same antenna port. When the properties of the channel of the symbol carried in one antenna port can be inferred from the channels of the symbols carried in other antenna ports, the two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-sited) relationship.

[0139] Here, the channel properties include at least one of delay spread, Doppler spread, frequency / Doppler shift, average received power, receive timing / average delay, or spatial RX parameters. Here, the spatial Rx parameters mean spatial (Rx) channel property parameters such as arrival angle.

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

[0141] Each TCI-state includes parameters for configuring a quasi co-location relationship between one or two ports of a DL reference signal and a DM-RS of a PDSCH.

[0142] The quasi co-location relationship is configured by a higher layer parameter qcl-type 1 for the first DL RS and qcl-type 2 for the second DL RS (if configured). For two DL RSs, the QCL type is different whether the reference is the same DL RS or different DL RSs.

[0143] The quasi co-location type corresponding to each DL RS is given by the higher layer parameter qcl-type of QCL-Info and can take one of the following values.

[0144] - 'QCL-Type A': {Doppler shift, Doppler spread, average delay, delay spread}

[0145] - 'QCL-Type-B': {Doppler shift, Doppler spread}

[0146] - 'QCL-Type-C': {Doppler shift, average delay}

[0147] - 'QCL-Type D': {Spatial Rx parameters}

[0148] For example, when the target antenna port is a specific NZP CSI-RS, the corresponding NZP CSI-RS antenna port may be indicated / configured to be quasi-colocated with a specific TRS with respect to QCL-type A, and quasi-colocated with a specific SSB with respect to QCL-type D. The terminal receiving such an indication / configuration may receive the corresponding NZP CSI-RS by using the Doppler and delay values ​​measured in the QCL-type A TRS and applying an Rx beam for receiving the QCL-type D SSB to receive the corresponding NZP CSI-RS.

[0149] The UE may receive the activation command via MAC CE signaling for mapping up to 8 TCI states to code points of the DCI field "Transmission Configuration Indication".

[0150] Operations related to multiple TRPs

[0151] The coordinated multi-point (CoMP) scheme refers to a scheme in which multiple base stations exchange or utilize channel information (e.g., RI / CQI / PMI / LI (layer indicator), etc.) fed back by a terminal (e.g., using an X2 interface) and cooperatively send it to the terminal to effectively control interference. Depending on the scheme used, CoMP can be classified into joint transmission (JT), coordinated scheduling (CS), coordinated beamforming (CB), dynamic point selection (DPS), dynamic point blocking (DPB), etc.

[0152] The M-TRP transmission scheme in which M TRPs send data to one terminal can be mainly classified into i) eMBB M-TRP transmission, a scheme for improving the transmission rate, and ii) URLLC M-TRP transmission, a scheme for increasing the reception success rate and reducing the delay.

[0153] In addition, regarding DCI transmission, the M-TRP transmission scheme can be classified into i) M-TRP transmission based on M-DCI (multiple DCIs), where each TRP transmits different DCIs, and ii) M-TRP transmission based on S-DCI (single DCI), where one TRP transmits DCI. For example, for M-TRP transmission based on S-DCI, all scheduling information about data transmitted by M TRPs should be delivered to the terminal through one DCI, which can be used in an ideal backhaul (ideal BH) environment, where dynamic cooperation between two TRPs is possible.

[0154] The UE may recognize a PUSCH (or PUCCH) scheduled by a DCI received in different control resource sets (CORESETs) (or CORESETs belonging to different CORESET groups) as a PUSCH (or PUCCH) sent to a different TRP, or may recognize a PDSCH (or PDCCH) from a different TRP. In addition, the method described below for UL transmissions (e.g., PUSCH / PUCCH) sent to different TRPs may be equivalently applied to UL transmissions (e.g., PUSCH / PUCCH) sent to different panels belonging to the same TRP.

[0155] Hereinafter, the CORESET group ID described / mentioned in the present disclosure may refer to an index / identification information (e.g., ID, etc.) of a CORESET distinguished for each TRP / panel. In addition, a CORESET group may be a group / union of CORESETs distinguished by an index / identification information (e.g., ID) / CORESET group ID, etc., for distinguishing a CORESET for each TRP / panel. In an example, the CORESET group ID may be specific index information defined in a CORESET configuration. In this case, a CORESET group may be configured / indicated / defined by an index defined in a CORESET configuration for each CORESET. Additionally / alternatively, a CORESET group ID may refer to an index / identification information / indicator, etc., for distinguishing / identifying between CORESETs configured / associated with each TRP / panel. Hereinafter, the CORESET group ID described / mentioned in the present disclosure may be represented by being replaced with a specific index / specific identification information / specific indicator, which is used to distinguish / identify between CORESETs configured / associated with each TRP / panel. The CORESET group ID, i.e., a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs configured / associated with each TRP / panel, may be configured / indicated to the terminal through higher layer signaling (e.g., RRC signaling) / L2 signaling (e.g., MAC-CE) / L1 signaling (e.g., DCI), etc. In an example, it may be configured / indicated so that PDCCH detection will be performed per TRP / panel (i.e., per TRP / panel belonging to the same CORESET group) in units of the corresponding CORESET group. Additionally / alternatively, it may be configured / indicated so that uplink control information (e.g., CSI, HARQ-A / N (ACK / NACK), SR (scheduling request)) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) are separated and managed / controlled per TRP / panel (i.e., per TRP / panel belonging to the same CORESET group) in units of the corresponding CORESET group. Additionally / alternatively, HARQ A / N (processing / retransmission) for PDSCH / PUSCH, etc. scheduled per TRP / panel may be managed per corresponding CORESET group (ie, per TRP / panel belonging to the same CORESET group).

[0156] For example, a higher layer parameter ControlResourceSet information element (IE) is used to configure a time / frequency control resource set (CORESET). In an example, a control resource set (CORESET) may be associated with detection and reception of downlink control information. The ControlResourceSet IE may include a CORESET-related ID (e.g., controlResourceSetID) / an index of a CORESET pool for a CORESET (e.g., CORESETPoolIndex) / a time / frequency resource configuration of a CORESET / TCI information associated with a CORESET, etc. In an example, an index of a CORESET pool (e.g., CORESETPoolIndex) may be configured as 0 or 1. In the description, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex).

[0157] Hereinafter, a method for improving reliability in multi-TRP will be described.

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

[0159] Figure 7 The diagram illustrates a method for multi-TRP transmission in a wireless communication system to which the present disclosure can be applied.

[0160] refer to Figure 7 (a) shows a case where layer groups that transmit the same codeword (CW) / transport block (TB) correspond to different TRPs. Here, the layer group may refer to a predetermined set of layers including one or more layers. In this case, there are the following advantages: the amount of transmission resources increases due to the number of multiple layers, so that robust channel coding with a low coding rate can be used for TBs, and additionally, because multiple TRPs have different channels, it can be expected that the reliability of the received signal can be improved based on diversity gain.

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

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

[0163] In addition, the above content related to multiple TRPs is described based on the SDM (spatial division multiplexing) method using different layers, but it can be naturally extended and applied to the FDM (frequency division multiplexing) method based on different frequency domain resources (e.g., RB / PRB (sets), etc.) and / or the TDM (time division multiplexing) method based on different time domain resources (e.g., time slots, symbols, sub-symbols, etc.).

[0164] Multiple TRPs scheduled by at least one DCI may be performed as follows:

[0165] i) Scheme 1 (SDM): n (n is a natural number) TCI states in a single time slot in overlapping time and frequency resource allocation

[0166] - Scheme 1a: Each transmission opportunity is a layer or a set of layers of the same TB, and each layer or a set of layers is associated with a TCI and a set of DMRS ports. A single codeword with one redundancy version (RV) is used for all layers or sets of layers. For the UE, different coded bits are mapped to different layers or sets of layers using specific mapping rules.

[0167] - Scheme 1b: Each transmission opportunity is a layer or a set of layers of the same TB, and each layer or a set of layers is associated with a TCI and a set of DMRS ports. A single codeword with one RV is used for each spatial layer or a set of layers. The RV corresponding to each spatial layer or a set of layers can be the same or different.

[0168] - Scheme 1c: Each transmission opportunity is a layer of the same TB having one DMRS port associated with multiple TCI state indexes or a layer of the same TB having multiple DMRS ports associated with multiple TCI state indexes sequentially (one by one).

[0169] In the above schemes 1a and 1c, the same MCS is applied to all layers or a set of layers.

[0170] ii) Scheme 2 (FDM): n (n is a natural number) TCI states in a single time slot in non-overlapping frequency resource allocations. Each non-overlapping frequency resource allocation is associated with one TCI state. The same single / multiple DMRS ports are associated with all non-overlapping frequency resource allocations.

[0171] - Scheme 2a: Use a single codeword with one RV across the entire resource allocation. For the UE, a common RB mapping (codeword to layer mapping) is applied across all resource allocations.

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

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

[0174] iii) Scheme 3 (TDM): n (n is a natural number) TCI states in a single time slot in non-overlapping time resource allocation. Each transmission opportunity of a TB has one TCI and one RV with a time granularity of a micro-time slot. All transmission opportunities in a time slot use a common MCS with the same single or multiple DMRS ports. The RV / TCI states can be the same or different among transmission opportunities.

[0175] iv) Scheme 4 (TDM): n (n is a natural number) TCI states in K (n<=K, K is a natural number) different time slots. Each transmission opportunity of a TB has one TCI and one RV. All transmission opportunities across K time slots use a common MCS with the same single or multiple DMRS ports. The RV / TCI states can be the same or different among transmission opportunities.

[0176] Hereinafter, in the present disclosure, DL MTRP-URLLC means that M-TRP sends the same data (e.g., transport block, TB) / DCI by using different layer / time / frequency resources. For example, TRP 1 sends the same data / DCI in resource 1, and TRP 2 sends the same data / DCI in resource 2. A UE configured with a DL MTRP-URLLC transmission method receives the same data / DCI by using different layer / time / frequency resources. Here, the UE is indicated which QCL RS / type (i.e., DL TCI (state)) should be used in the layer / time / frequency resource receiving the same data / DCI from the base station. For example, when the same data / DCI is received in resource 1 and resource 2, the DL TCI state used in resource 1 and the DL TCI state used in resource 2 may be indicated. Because the UE receives the same data / DCI through resource 1 and resource 2, the UE can achieve high reliability. Such DL MTRP URLLC can be applied to PDSCH / PDCCH.

[0177] In contrast, UL MTRP-URLLC means that the M-TRP receives the same data / UCI from the UE by using different layer / time / frequency resources. For example, TRP 1 receives the same data / UCI from the UE in resource 1, and TRP 2 receives the same data / UCI from the UE in resource 2, and shares the received data / UCI through the backhaul link connected between the TRPs. A UE configured with the ULMTRP-URLLC transmission method sends the same data / UCI by using different layer / time / frequency resources. Here, the UE is indicated which Tx beam and which Tx power (ie, UL TCI state) should be used in the layer / time / frequency resource in which the same data / DCI is sent from the base station. For example, when the same data / UCI is received in resource 1 and resource 2, the UL TCI state used in resource 1 and the UL TCI state used in resource 2 can be indicated. Such UL MTRPURLLC can be applied to PUSCH / PUCCH.

[0178] In addition, in the method proposed in the present disclosure, when a specific TCI state (or TCI) is used ( / mapped) to receive data / DCI / UCI for any frequency / time / space resource, it may mean that DL estimates a channel from DMRS by using the QCL type and QCL RS indicated by the corresponding TCI state in the frequency / time / space resource, and receives / demodulates data / DCI to the estimated channel. It may mean that UL transmits / modulates DMRS and data / UCI by using the Tx beam and / or Tw power indicated by the corresponding TCI state in the frequency / time / space resource.

[0179] The UL TCI state has the UE's Tx beam and / or Tx power information and spatial relationship information, etc., which can be configured to the UE by other parameters instead of the TCI state. The UL TCI state can be directly indicated to the UL grant DCI or can mean the spatial relationship information of the SRS resource indicated by the SRI (SRS resource indicator) field of the UL grant DCI. Alternatively, it can mean the OL (open loop) Tx power control parameters connected to the value indicated by the SRI field of the UL grant DCI (j: index for open loop parameters Po and alpha (α) (up to 32 parameter value sets per cell), q_d: index of DLRS resources for PL (path loss) measurement (up to 3 measurements per cell), l: closed loop power control process index (up to 2 processes per cell)).

[0180] On the other hand, assuming that MTRP-eMBB means M-TRP to send other data by using different layers / times / frequencies, a UE configured with the MTRP-eMBB transmission method is indicated with multiple TCI states of DCI, and the data received by using the QCL RS of each TCI state is different data.

[0181] In addition, the UE can understand whether it is MTRP URLLC transmission / reception or MTRP eMBB transmission / reception by separately classifying the RNTI for MTRP-URLLC and the RNTI for MTRP-eMBB and using them. In other words, when the CRC mask of DCI is performed by using the RNTI for URLLC, it is considered to be URLLC transmission, and when the CRC mask of DCI is performed by using the RNTI for eMBB, it is considered to be eMBB transmission. Alternatively, the base station can configure MTRP URLLC transmission / reception to the UE through other new signaling or can configure MTRP eMBB transmission / reception.

[0182] In the present disclosure, for the convenience of description, the proposal is applied by assuming cooperative transmission / reception between 2 TRPs, but it can be extended and applied in 3 or more multi-TRP environments, and it can also be extended and applied in a multi-panel environment. Different TRPs can be recognized by the UE as different transmission configuration indication (TCI) states. That is, when the UE receives / sends data / DCI / UCI by using TCI state 1, it means receiving / sending data / DCI / UCI from TRP 1 / to TRP1.

[0183] The proposals of the present disclosure may be utilized in the case where MTRP cooperatively transmits PDCCH (repeatedly or partially transmits the same PDCCH), and some proposals may even be utilized in the case where MTRP cooperatively transmits PDSCH or cooperatively receives PUSCH / PUCCH.

[0184] In addition, in the present disclosure below, the meaning of multiple base stations (ie, MTRP) repeatedly sending the same PDCCH may mean that the same DCI is sent by multiple PDCCH candidates, and it is equivalent to meaning that multiple base stations repeatedly send the same DCI. The same DCI may mean two DCIs with the same DCI format / size / payload. Alternatively, although the two DCIs have different payloads, they can also be considered to be the same DCI when the scheduling results are the same. For example, based on the reception time of the DCI, the TDRA (time domain resource allocation) field of the DCI relatively determines the time slot / symbol position of the data and the time slot / symbol position of the A / N (ACK / NACK). Here, if the DCI received at time n and the DCI received at time n+1 indicate the same scheduling result to the UE, the TDRA fields of the two DCIs are different, and therefore, the DCI payloads are different. R (the number of repetitions) can be directly indicated by the base station to the UE or promised to each other. Alternatively, although the payloads of the two DCIs are different and the scheduling results are not the same, when the scheduling result of one DCI is a subset of the scheduling result of the other DCI, it can be considered to be the same DCI. For example, when the same data is repeatedly sent N times through TDM, DCI 1 received before the first data indicates N data repetitions, and DCI 2 received after the first data and before the second data indicates N-1 data repetitions. The scheduling data of DCI 2 becomes a subset of the scheduling data of DCI 1, and the two DCIs are scheduling for the same data, so in this case, it can be considered to be the same DCI.

[0185] In addition, in the present disclosure below, when a plurality of base stations (ie, MTRPs) divide and transmit the same PDCCH, it may mean that one DCI is transmitted through one PDCCH candidate, but TRP 1 transmits some resources in which the PDCCH candidates are defined and TRP 2 transmits the remaining resources. For example, when TRP 1 and TRP 2 divide and transmit PDCCH candidates corresponding to aggregation level m1+m2, the PDCCH candidates are divided into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate 2 corresponding to aggregation level m2, and TRP 1 transmits PDCCH candidate 1 using different time / frequency resources and TRP 2 transmits PDCCH candidate 2. After receiving PDCCH candidate 1 and PDCCH candidate 2, the UE generates a PDCCH candidate corresponding to aggregation level m1+m2 and attempts DCI decoding.

[0186] When the same DCI is divided and transmitted to a plurality of candidate PDCCHs, there may be two implementation methods.

[0187] First, the DCI payload (control information bits + CRC) can be encoded by one channel encoder (e.g., a polar encoder), and the coded bits obtained as a result can be divided into two TRPs and transmitted. In this case, the entire DCI payload can be decoded in the coded bits transmitted by each TRP, or only a portion of the DCI payload is encoded. Second, the DCI payload (control information bits + CRC) can be divided into two (DCI 1 and DCI 2) and each can be encoded by a channel encoder (e.g., a polar encoder). Thereafter, the two TRPs can transmit the coded bits corresponding to DCI 1 and the coded bits corresponding to DCI 2, respectively.

[0188] In summary, multiple base stations (ie, MTRPs) divide / repeat the same PDCCH and transmit on multiple monitoring occasions (MOs) as follows.

[0189] i) it may mean that each base station (ie, STRP) repeatedly transmits coded DCI bits obtained by encoding all DCI contents of a corresponding PDCCH through each MO; or,

[0190] ii) it may mean that the coded DCI bits obtained by encoding all DCI contents of the corresponding PDCCH are divided into a plurality of parts, and each base station (ie, STRP) transmits a different part through each MO; or

[0191] iii) It may mean that the DCI content of the corresponding PDCCH is divided into multiple parts, and each base station (ie, STRP) encodes different parts separately and transmits them through each MO.

[0192] That is, it can be understood that whether it is repeated transmission or divided transmission of PDCCH, PDCCH is sent multiple times on multiple transmission opportunities (TO). Here, TO means a specific time / frequency resource unit in which PDCCH is sent. For example, if PDCCH is sent multiple times on time slots 1, 2, 3 and 4 (in a specific resource block (RB)), TO can mean each time slot, or if PDCCH is sent multiple times on RB sets 1, 2, 3 and 4 (in a specific time slot), TO can mean each RB set, or if PDCCH is sent multiple times at different times and frequencies, TO can mean each time / frequency resource. In addition, the TCI state for DMRS channel estimation for each TO can be configured differently, and it can be assumed that the TO in which the TCI state is configured differently is sent by different TRP / panels. When multiple base stations repeatedly send or send PDCCH separately, it means that PDCCH is sent on multiple TOs, and the union of the TCI states configured in the corresponding TOs is configured with two or more TCI states. For example, if PDCCH is sent on TO 1, 2, 3, 4, TCI states 1, 2, 3, 4 can be configured in each of TO 1, 2, 3, 4 respectively, which means that TRP i cooperates to send PDCCH in TO i.

[0193] For multiple TOs that instruct the UE to repeatedly send or separately send PDCCH / PDSCH / PUSCH / PUCCH, UL sends to a specific TRP or DL ​​receives from a specific TRP in each TO. Here, the UL TO sent to TRP 1 (or TO of TRP 1) means a TO that uses the first value among the two spatial relationships, two UL TCIs, two UL power control parameters and / or two path loss reference signals (PLRS) indicated to the UE, and the UL TO sent to TRP 2 (or TO of TRP 2) means a TO that uses the second value among the two spatial relationships, two UL TCIs, two UL power control parameters and / or two PLRS indicated to the UE. Similarly, for DL ​​transmission, the DL TO sent by TRP 1 (or the TO of TRP 1) means the TO using the first value among the two DL TCI states (e.g., when the two TCI states are configured in the CORESET) indicated to the UE, and the DL TO sent by TRP 2 (or the TO of TRP 2) means the TO using the second value among the two DL TCI states (e.g., when the two TCI states are configured in the CORESET) indicated to the UE.

[0194] The proposal of the present disclosure can be extended and applied to various channels such as PUSCH / PUCCH / PDSCH / PDCCH.

[0195] The proposal of the present disclosure can be extended and applied to both the case of repeated transmission and the case of dividing the transmission channels on different time / frequency / space resources.

[0196] Permission for uplink configuration

[0197] Configured grants (CGs) for PUSCH are divided into CG type 1 and CG type 2.

[0198] Using RRC signaling, CG Type 1 is fully configured or released for resource allocation. When CG Type 1 is configured, the UE is allocated a set of resources capable of periodically sending PUSCH. PDCCH is requested only when retransmission is required. When a higher layer parameter configuredGrantConfig including rrc-ConfiguredUplinkGrant is received, CG Type 1 PUSCH transmission is semi-statically configured to operate without detecting UL grants in the DCI. The UE is able to perform PUSCH transmission according to the configured CG Type 1 until additional RRC signaling is re-established for the UE.

[0199] CG Type 2 is partially configured with resource allocation using RRC signaling and activated / deactivated using PDCCH transmissions. Since PDCCH also provides time and frequency resource allocations, the resource allocations can change each time it is activated. Following reception of the higher layer parameter configuredGrantConfig (which does not include rrc-ConfiguredUplinkGrant), CG Type 2 PUSCH transmissions can be semi-persistently scheduled by validly activating the UL grant in the DCI.

[0200] One or more CG configurations of CG type 1 and / or CG type 2 can be activated simultaneously on the activated BWP of the serving cell.

[0201] For PUSCH transmission corresponding to CG type 1 or CG type 2, parameters for PUSCH transmission can be provided through configuredGrantConfig.

[0202] Table 6 shows an example of configuredGrantConfig IE. ConfiguredGrantConfig IE is used to configure uplink transmission without dynamic grant through DCI. The actual uplink grant can be configured by RRC (CG type 1) or can be provided via PDCCH (through CS-RNTI) (CG type 2). Multi-CG configuration can be configured within one BWP of the serving cell.

[0203] [Table 6]

[0204]

[0205] In Table 6, periodicity represents the period for uplink CG transmission, which means the duration between consecutive persistent resource allocations. PeriodicityExt is used to calculate the period of uplink CG, and if this parameter is not present, periodicity is ignored. The uplink CG period has different supported values ​​depending on the configured subcarrier spacing.

[0206] nrofHARQ-Processes indicates the number of HARQ processes configured for the uplink CG. In case of dynamic resource allocation, the HARQ process identifier is specified in the DCI associated with each resource allocation. However, in the uplink CG, the identifier of the HARQ process is determined based on the nrofHARQ-Processes value and the periodicity value.

[0207] repK indicates the number of repetitions, that is, indicates the repetition level used for each PUSCH transmission. RepK can have one of the values ​​of {1,2,4,8}. For CG type 1, if the pusch-Rep Type Indicator in the rrc-ConfiguredUplinkGrant indicates "pusch-Rep Type B", PUSCH repetition type B is applied, otherwise PUSCH repetition type A is applied. For CG type 2, the PUSCH repetition type is determined by the UL grant of the DCI. The UE repeatedly sends uplink TBs with the configured number of repetitions (depending on the configured PUSCH repetition type A or B).

[0208] repK-RV indicates a redundancy version sequence. repK-RV is configured when repetition is used (ie, when repK is set to one of {2, 4, 8}).

[0209] resourceAllocation indicates the configuration of bitmap-based resource allocation type 0 or resource indication value (RIV)-based resource allocation type 1.

[0210] mcs-Table indicates the MCS table used by the UE for PUSCH not using transform precoding, and mcs-TableTransformPrecoder indicates the MCS table used by the UE for PUSCH using transform precoding. transformPrecoder indicates whether transform precoding is enabled for PUSCH.

[0211] rrc-ConfiguredUplinkGrant is the configuration for CG type 1 transmission. If this field is not present, the UE uses the UL grant configured by CS-RNTI through DCI (i.e., CG type 2). timeDomainAllocation indicates the starting symbol and length of the PUSCH and the PUSCH mapping type. timeDomainOffset indicates the offset with respect to the reference SFN (system frame number) indicated by timeReferenceSFN. timeReferenceSFN indicates the SFN used to determine the offset of resources in the time domain. The UE uses the SFN closest to the indicated number prior to reception of the configured grant configuration, and if this field is not present, the reference SFN is 0.

[0212] After configuring the uplink grant for CG type 1, the MAC entity considers the Nth (N≥0) uplink grant to occur within one symbol in order according to the following equation 3. That is, when CG type 1 is used, the CG PUSCH can be transmitted at the transmission timing / opportunity satisfying the following equation 3.

[0213] [Equation 3]

[0214]

[0215] In addition, after configuring the uplink grant for CG type 2, the MAC entity considers the Nth (N≥0) uplink grant to occur within one symbol in order according to the following equation 4. That is, when CG type 2 is used, CG PUSCH can be transmitted at the transmission timing / opportunity that satisfies the following equation 4.

[0216] [Equation 4]

[0217]

[0218] In Equation 3 and Equation 4, numberOfSlotsPerFrame represents the number of consecutive slots per frame, and numberOfSymbolsPerSlot represents the number of consecutive symbols per slot.

[0219] In addition, timeReferenceSFN is used to determine the offset of resources in the time domain, and the UE can use the SFN with the closest indicated number before receiving the configured CG. timeDomainOffset indicates the offset relative to the reference SFN indicated by timeReferenceSFN. periodicity indicates the periodicity of UL transmission for CG type 1. timeReferenceSFN, timeDomainOffset and periodicity can be configured by configuredGrantConfig (see Table 6). In addition, S corresponds to the starting symbol derived from timeDomainAllocation (see Table 6), and N is an integer value corresponding to the Nth transmission opportunity.

[0220] Additionally, SFN 开始时间 、slot 开始时间 and symbol 开始时间 Represents the SFN, timeslot and symbol, respectively, of the first transmission occasion / opportunity of the PUSCH where the CG is (re)initialized (i.e., the PUSCH transmission occurring according to the resource allocation in the active PDCCH).

[0221] Meanwhile, in the case of dynamic resource allocation on PDCCH, the HARQ process identifier (HARQ process ID) is specified in the DCI, however in the case of CG, since DCI is not received before each PUSCH transmission, the HARQ process is calculated according to the following equation 5 or equation 6. The base station is able to configure the number of HARQ processes (e.g., nrofHARQ-Processes) and the offset (e.g., harq-ProcID-Offset2) used to derive the HARQ process ID.

[0222] If the offset (e.g., harq-ProcID-Offset2) and the retransmission timer (cg-RetransmissionTimer) for deriving the HARQ process ID are not configured, the UE derives the HARQ process ID associated with the time slot (where the uplink transmission starts from the following equation 5). Alternatively, if the offset (e.g., harq-ProcID-Offset2) for deriving the HARQ process ID is configured, the UE derives the HARQ process ID associated with the time slot (where the uplink transmission starts from the following equation 6).

[0223] [Equation 5]

[0224]

[0225] [Equation 6]

[0226]

[0227] In Equation 5 and Equation 6, nrofHARQ-Processes defines the number of uplink HARQ processes and can have a value from 1 to 16 (see Table 6). nrofHARQ-Processes is used to identify the HARQ process ID for a specific PUSCH transmission.

[0228] In addition, in Equation 5 and Equation 6, CURRENT_symbol=(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+number of slots in frame×numberOfSymbolsPerSlot+number of symbols in slot). numberOfSlotsPerFrame and numberOfSymbolsPerSlot mean the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively.

[0229] Meanwhile, in Table 6, configuredGrantTimer indicates the initial value of the CG timer as a multiple of periodicity. That is, configuredGrantTimer defines the duration (period) for the UE to wait for a retransmission request after sending an uplink packet. The CG timer is operated independently for each HARQ process.

[0230] More specifically, the MAC entity includes a HARQ entity for each serving cell with a configured uplink, which maintains multiple parallel HARQ processes. The number of parallel HARQ processes for each HARQ entity is determined according to the standard specification. Each HARQ process supports one TB. Each HARQ process is associated with a HARQ process identifier (ID). When a TB is repeated in multiple CGPUSCHs (i.e., in multiple CG PUSCH TOs), the same HARQ process can be used for the repeated CG PUSCHs.

[0231] For an uplink grant, the HARQ entity identifies a HARQ process associated with the grant. For the identified HARQ process, if the uplink grant is a configured uplink grant and is used for an initial transmission for the configured uplink grant, the HARQ entity may start a CG timer (i.e., configuredGrantTimer) by an initial CG PUSCH transmission for the identified HARQ process according to Equation 5 or Equation 6. Here, the CG timer (i.e., configuredGrantTimer) may be started at the beginning of the first symbol of the initial CG PUSCH transmission.

[0232] When the timer expires, the UE can assume a positive acknowledgment. If this timer expires (i.e., if no retransmission request is received until the timer expires), the UE assumes a positive acknowledgment. This allows the UE to subsequently send new uplink data using the same HARQ process.

[0233] This CG timer should be configured long enough to ensure that the base station has time to receive the uplink packet and schedule the retransmission request, but if this CG timer is configured too long, delays may occur because the UE cannot reuse the HARQ process for a new transmission until it has a positive confirmation for the previous transmission hypothesis.

[0234] Method for transmitting and receiving PUSCH using configured grant (CG)

[0235] In the present disclosure, a method is proposed for reducing power consumption and increasing wireless resource efficiency while ensuring the availability and reliability of transmission resources when sending video information of an extended reality (XR) service using pre-configured resources (such as a configured grant (CG) of an NR wireless communication system).

[0236] In NR, one or more CG PUSCHs can be configured for a UE for periodic transmission and reception or for low latency and PDCCH overhead. Each CG configuration has a period, and the configured / indicated resources can be repeated. That is, the initially configured / indicated resource allocation is repeated with the configured period, and the UE can perform uplink transmission on the corresponding resources without a separate PDCCH reception process.

[0237] At the same time, the types of data that can be generated in XR are diverse. Among these data, sensor and location information of the UE and video data transmission that is usually reported using a specific cycle are being considered to be sent and received from CG resources. These data may not always have a fixed data generation time (service arrival time) and may have jitter due to reasons such as video encoding time, sensor measurement time, higher layer operation, or routing changes of the transmitted network.

[0238] If resources are allocated to a location far enough away from the expected business occurrence time considering jitter, etc., resource availability can be guaranteed, but delays may occur. On the other hand, if CG resources with a fixed cycle are allocated to the expected data occurrence time, when jitter occurs, a greater delay may occur due to the waiting time until the next available resource.

[0239] In addition, since some data is generated based on events, it is impossible to accurately identify the actual data generation time, but the use of CG resources for such data is being considered to reduce the delay time caused by scheduling. In this case, a skip method has been discussed in the past, in which sufficient resources are allocated in a short cycle to prepare for the generation of data, and the UE or base station selectively uses these resources and does not actually use other resources. However, in order to use the method of skipping transmission and reception, it is necessary to consider the response signal between the UE and the base station to determine whether to receive and send. If the UE sends a response signal even for a transmission that has not yet been received, the base station needs to always prepare resources for the UE to send a response signal. In addition, considering that the skip method is based on setting sufficient resources in the radio resources, this may act as a huge uplink burden. In addition, considering that these resources can be multiplexed between UEs, the burden of uplink resources should be given more attention.

[0240] Since ensuring low latency is critical to XR service quality, it is necessary to consider a method to minimize the impact of latency while reducing the impact of jitter. In the present disclosure, in order to solve this problem, a method is discussed to selectively use some of the multiple CG resources configured between the UE and the base station, and simplify and send the response to the used CG resources to a predetermined location.

[0241] A group of pictures (GOP) of video coding may include the following picture types.

[0242] An I picture or I frame (i.e., intra-coded picture) (also called a key frame or i-frame) is a picture that is coded independently of all other pictures. Each GOP starts with a picture of this type (in decoding order).

[0243] A P picture or P frame (i.e., a predictively coded picture) contains motion compensated difference information relative to a previously decoded picture. For example, in previous designs such as H.262 / MPEG-2 and H.263, each P picture can only reference one picture, which must precede the P picture in display order and decoding order, and which must be an I picture or a P picture. These restrictions do not apply to the new standards H.264 / MPEG-4 AVC and HEVC.

[0244] B pictures or B frames (bidirectionally predicted coded pictures) contain motion compensated difference information compared to the previously decoded picture. For example, in previous designs such as MPEG-1 and H.262 / MPEG-2, each B picture can only reference two pictures, one before the B picture in the display order, and one after the B picture, and all referenced pictures must be I pictures or P pictures. This restriction does not apply to the new standards H.264 / MPEG-4 AVC and HEVC.

[0245] D pictures or D frames (directly coded (DC) pictures) are used as fast access representation of pictures for loss robustness or fast forward. D pictures are only used in MPEG-1 video.

[0246] Figure 8 Illustrate the structure / pattern of the group of pictures.

[0247] refer to Figure 8 , an I frame indicates the start of a GOP. It is followed by several P frames and B frames. In previous designs, the allowed ordering and reference structures were relatively limited.

[0248] The GOP structure is often represented by two numbers, for example, M=3, N=12. The first number (M) indicates the distance between two anchor frames (I or P). The second number (N) is the GOP size, which indicates the distance between two complete images (I frames). For example, for M=3, N=12, the GOP structure is IBBPBBPBBPBBI. It is also possible to use the maximum number of B frames between two consecutive anchor frames instead of the M parameter.

[0249] For example, in a sequence with IBBBBBBBBBPBBBBBI pattern, the GOP size (N value) is 15 (the length between two I frames), and the distance between two anchor frames (M value) is 5 (the length between an I frame and a P frame or the length between two consecutive P frames).

[0250] An I frame contains a complete image and no additional information is needed to reconstruct it. Typically, encoders use a GOP structure to ensure that each I frame is a "clean random access point". Thus, decoding can start cleanly from an I frame, and any errors within the GOP structure are corrected after processing the correct I frame.

[0251] In the following disclosure, the proposed method is described based on the semi-statically configured uplink CG radio resources, but this is only for convenience of explanation, and the method proposed in the present disclosure is not limited to this. Therefore, those skilled in the art can understand that the method proposed in the present disclosure can be extended and applied to radio resources allocated by dynamic scheduling received by the UE. For example, a method for determining a HARQ-ACK timing for multiple downlink radio resources allocated to the UE can be applied regardless of the SPS PDSCH and the PDSCH indicated by the dynamic scheduling. In addition, when multiple radio resources are not semi-statically configured but are configured by dynamic instructions, for example, when multiple radio resources are configured at once by DCI, the method proposed in the present disclosure can be applied. Therefore, the method proposed in the present disclosure can be applied to all types of transmission and reception methods expected by the base station and the UE, as long as the principle of the proposed method is not violated, even without a separate explanation. hereinafter, in the present disclosure, for convenience of explanation, semi-persistent scheduling (SPS) can be used as a general concept to collectively refer to semi-statically configured radio resources (e.g., DL / UL SPS, CG).

[0252] In addition, in the present disclosure, a transmission opportunity (TO) means a radio resource configured for CG use (e.g., CG PUSCH). In one transmission opportunity, a subject performing transmission (i.e., a base station in the case of a downlink and a UE in the case of an uplink) can attempt to send in a TO, and a receiving party (i.e., a UE in the case of a downlink and a base station in the case of an uplink) can expect transmission in each TO and attempt to receive it.

[0253] In the following, in order to explain the principle of the proposed method, the present disclosure provides an example based on the NR system, but, unless otherwise specified, the proposed method does not specifically limit the transmission and reception form of NR. In addition, in order to explain the principle of the proposed method, the present disclosure provides an example based on the features and structure of the XR service, but, unless otherwise specified, the proposed method does not specifically limit the support for the XR service. Therefore, even without a separate explanation, the method proposed in the present disclosure can be applied to all wireless communication transmission and reception structures and services as long as it does not violate the principle of the proposed method.

[0254] Hereinafter, the present disclosure proposes a grant resource allocation and transmission method considering configuration of a GOP pattern and a packet delay requirement.

[0255] For this purpose, the method proposed in the present disclosure may include a method for the base station to allocate CG radio resources to the UE, and a method for receiving and sending CG resources. In addition, the method proposed in the present disclosure may include a method for sending a HARQ-ACK response to a CG PUSCH reception result, and a method for receiving a retransmitted DCI of the base station through the PDCCH. In addition, the method proposed in the present disclosure may include a process in which the UE sends a signal and a channel to inform its capabilities and / or service requirements and the base station receives the signal and the channel.

[0256] The method proposed in the present disclosure can be applied by selecting some of the following methods. In addition, each method proposed in the present disclosure can be operated independently without separate combination, or can be operated in a linked form by combining one or more methods. As long as the principles of the present disclosure are maintained, some terms, symbols and sequences used to describe the method proposed in the present disclosure can be replaced by other terms, symbols and sequences.

[0257] The present disclosure can support the following CG settings and activation / deactivation, transmission / reception operations, etc. That is, the following CG settings and activation / deactivation, transmission / reception operations, etc. can be incorporated into the method proposed in the present disclosure.

[0258] According to an embodiment of the present disclosure, Fig. 9 Figure 1 illustrates the licensing configuration for multiple configurations.

[0259] -Multiple CGs (e.g., CG1 and CG2 in the case of two CGs) can be configured as one CG group with mutually linked / associated CG configurations, and CG1 can be configured as a primary CG, and CG2 can be configured as a secondary CG. Here, the secondary CG can be a CG that is activated or received according to the transmission of the primary CG. For example, Fig. 9The CG configuration for CG PUSCH 1 is the primary CG configuration, and the CG configuration for CG PUSCH 2 is the secondary CG configuration, and the two CG configurations can be configured as one CG group.

[0260] -The primary CG and the secondary CG can be configured with different CG configuration indexes. Alternatively, the primary CG and the secondary CG can be configured with the same CG configuration index, but can be distinguished by the primary / secondary CG indicator or different sub-indexes through RRC messages or MAC CE or DCI.

[0261] i) If the DCI indicates CG1 and also indicates activation, the UE may activate CG2 simultaneously with CG1 or after a certain period of time.

[0262] ii) Alternatively, if the DCI indicates both CG1 and CG2 and also indicates activation, the UE may activate CG2 simultaneously with CG1 or after a certain period of time. Fig. 9 The diagram shows a case where activation of both the CG configuration for CG PUSCH 1 and the CG configuration for CG PUSCH 2 is indicated by one DCI.

[0263] Here, the DCI may include different CG configuration indexes for both CG1 and CG2.

[0264] Alternatively, the DCI may include a CG configuration index for CG1 and indicate a secondary CG indicator.

[0265] Alternatively, the DCI may include a CG configuration index for CG2 and indicate a primary CG indicator.

[0266] Alternatively, the DCI may include a CG configuration index for CG1 or CG2 and a sub-index for CG2 or CG1.

[0267] Alternatively, the DCI may indicate a common CG configuration index for CG1 and CG2. For example, among the HARQ process identifier (ID) values ​​indicating the CG configuration index, values ​​between 1 and 8 may be configured as conventional CG configuration indexes (i.e., used to indicate a single CG configuration), and HARQ process ID values ​​exceeding 8 may be configured as CG configuration indexes that simultaneously indicate multiple connected CGs.

[0268] Alternatively, the DCI may include all different CG configuration sub-indexes for CG1 and CG2.

[0269] -The base station is able to configure different video frame types (e.g., I frames and P frames) to different logical channels. Accordingly, the UE is able to indicate that data is for different video frames through the value of the logical channel identifier (LCID) field included in the subheader of the uplink MAC protocol data unit (PDU) (i.e., transport block (TB)). Here, the base station is able to configure different logical channels for different video frame types to map to different CGs. Here, CG1 and CG2 can be mapped to the same or different logical channels.

[0270] For example, refer to Fig. 9 , different logical channels can be configured / allocated for I frames and P frames. In addition, the logical channels for I frames can be mapped to the CG for CG PUSCH 1, and the logical channels for P frames can be mapped to the CG for CGPUSCH 2.

[0271] -The activation or transmission / reception of CG2 can be determined depending on whether CG1 is activated or transmitted / received. Here, the activation of CG2 can be configured to occur simultaneously with or after the activation of CG1.

[0272] -UE can expect CG2 PUSCH transmission to occur only after CG1 PUSCH transmission. Accordingly, it can determine the CG2 PUSCH transmission of the next period based on whether CG1 PUSCH is sent.

[0273] -When CG1 PUSCH and CG2 PUSCH are transmitted / allocated in TDM or FDM with the same period or partially overlapping periods, when transmitting CG1 PUSCH, the UE may decide that CG2 PUSCH resources are invalid or skip CG2 PUSCH transmission. Alternatively, the UE may deactivate CG2 or deactivate an activated CG2. For example, Fig. 9 As shown in , the CG configuration for CG PUSCH 1 may be configured with a period of N times 16 ms or 17 ms (N is a natural number), and the CG configuration for CG PUSCH 2 may be configured with a period of 16 ms or 17 ms. Also, the CG configuration for N CG PUSCH 2 may overlap within one period of the CG configuration for CGPUSCH 1. That is, as Fig. 9 As shown in FIG, in the first cycle of CG PUSCH 2, CG PUSCH 2 and CG PUSCH 1 can be allocated as TDM or FDM. In this case, CG PUSCH 2 ( Fig. 9 Resources carrying PUSCH 2 of TB2 for I frame can be determined to be invalid or transmission of CG PUSCH 2 can be determined to be skipped.

[0274] -When CG1 PUSCH and CG2 PUSCH are transmitted / allocated in the same time slot as TDM or FDM, or when CG1 PUSCH and CG2 PUSCH resources overlap, the UE prioritizes the reception of CG1 PUSCH regardless of the CG configuration indexes of CG1 and CG2. That is, in this case, the UE is able to skip the CG2 PUSCH resource transmission and transmit the CG1 PUSCH resource. For example, Fig. 9 As shown in , CG PUSCH 2 can be skipped ( Fig. 9 PUSCH2 of TB2 carrying I frame) and only CG PUSCH 1 resources are sent.

[0275] -When the base station configures and activates periodic radio resources (e.g., CG) to the UE, the base station may allocate multiple radio resources to the UE within one period. The multiple radio resources may be allocated with the same time / frequency resource allocation at fixed intervals (e.g., M (M is a natural number) time slots) in one time slot (e.g., for each time slot, 3 symbols of radio resources are repeatedly allocated to the same position), or radio resources with the same length may be continuously allocated in symbols continuous with the first radio resource (e.g., 3 symbols of radio resources are continuously allocated). The number N (N is a natural number) of radio resources may be determined by L1 signaling and / or higher layer signaling. For example, in Fig. 9 In one cycle, only one radio resource is allocated to both CG PUSCH 1 and CG PUSCH 2, however, multiple radio resources may be allocated in one cycle.

[0276] -Base station / UE can use one or more of the multi-CG radio resources to perform transmission in a period according to the traffic pattern. Here, considering the time when the user data of the base station / UE appears, the fastest radio resource capable of sending a transport block (TB) including the user data can be selected.

[0277] According to an embodiment of the present disclosure, Fig.10 Figure 1 shows the licensing configuration for a single configuration.

[0278] In the following, reference will be made to Fig.10 To describe embodiments according to the present disclosure.

[0279] Embodiment 1: When a CG configuration is configured for a UE, the CGPUSCH for the corresponding CG configuration can be sent and received as follows.

[0280] Here, a logical channel mapped to one CG configuration can only be mapped to a specific CG cycle. In addition, the number of CG PUSCH opportunities (ie, TO) allocated per CG cycle can be allocated differently depending on the logical channel to which it is mapped.

[0281] According to this embodiment, the UE can send a CG PUSCH in N (N is a natural number) CG PUSCH opportunities (ie, TO) per CG cycle. For example, for a CG PUSCH belonging to (one or more) CG cycles or CG windows that transmit data of a specific logical channel (hereinafter, the first logical channel) such as an I frame, the UE can allocate and send N (N is a natural number) CG PUSCH opportunities (ie, TO) per CG cycle.

[0282] Here, the base station can allocate N CGPUSCH opportunities per CG cycle only within these (one or more) CG cycles or CG windows. Alternatively, the base station can always allocate N CGPUSCH opportunities per CG cycle regardless of the CG cycle or CG window.

[0283] At the same time, for a CG PUSCH that (i) does not belong to a (one or more) CG cycle or CG window in which the first logical channel data is transmitted, or (ii) belongs to a CG cycle or CG window in which other logical channel (i.e., second logical channel) data is transmitted, the UE may send only k (k is a natural number) CG PUSCH opportunities per CG cycle. Here, the base station is able to configure k to a value less than N. In the above case (i), if (one or more) CG cycles or CG windows are configured for the first logical channel, the configuration of (one or more) CG cycles or CG windows for the second logical channel may not be necessary. On the other hand, in the above case (ii), even if (one or more) CG cycles or CG windows are configured for the first logical channel, the configuration of (one or more) CG cycles or CG windows for the second logical channel may be required separately.

[0284] Here, the base station may allocate k CG PUSCH opportunities (i.e., TO) associated with the second logical channel per CG cycle only within (one or more) CG cycles or CG windows (i.e., in case of (i), the cycle outside the (one or more) CG cycles or CG windows configured for the first logical channel, and in case of (ii), the cycle or CG window or CG cycle configured for the second logical channel). Alternatively, the base station may allocate N CG PUSCH opportunities (i.e., TO) per CG cycle regardless of the (one or more) CG cycles or CG windows associated with the second logical channel, but the UE may send CG PUSCH only in specific k CG PUSCH opportunities among the N CG PUSCH opportunities, and skip CG PUSCH transmission in the remaining Nk CG PUSCH opportunities. Here, the specific k CG PUSCH opportunities (i.e., TO) may correspond to the first CG PUSCH opportunity to the kth CG PUSCH opportunity of the corresponding CG cycle, or may correspond to the (N-k+1)th CG PUSCH opportunity to the last (N)th CG PUSCH opportunity of the corresponding CG cycle.

[0285] Method 1-1: Both the first logical channel (e.g., a logical channel for an I frame) and the second logical channel (e.g., a logical channel for a P frame) can be mapped to a specific CG configuration. In addition, the base station can configure the first logical channel (e.g., a logical channel for an I frame) to be mapped only to CG periods that are multiples of N (i.e., the 0th CG period, the Nth CG period, the 2Nth CG period, etc.), and the second logical channel (e.g., a logical channel for a P frame) to be mapped only to the remaining CG periods (i.e., the 2nd to N-1th CG periods, the N+1th to the 2N-1th CG periods, etc.). For example, if N is 10, the 0th, 10th, 20th, 30th, ... CG periods can be configured to map the first logical channel (e.g., a logical channel for an I frame), and the remaining CG periods can be configured to map the second logical channel (e.g., a logical channel for a P frame). Here, for example, the base station can configure the CG period of a specific CG configuration to be 16 ms or 17 ms.

[0286] According to method 1-1, the base station may configure only the N value of the CG period to which the first logical channel is mapped, and accordingly, the first logical channel may be mapped to a CG period that is a multiple of N. And, even without a separate setting, the second logical channel can be mapped to the remaining CG periods.

[0287] refer to Fig.10, in the first CG cycle and the Nth CG cycle, the logical channels for the I frame may be mapped, and TB 1 and TB 2 for the I frame may be transmitted. In addition, in the remaining CG cycles, the logical channels for the P frame may be mapped, and TBs for the P frame may be transmitted.

[0288] Method 1-2: Both a first logical channel (e.g., a logical channel for I frames) and a second logical channel (e.g., a logical channel for P frames) can be mapped to a specific CG configuration. Here, if there is data for the first logical channel (e.g., a logical channel for I frames), it is possible to preferably construct a TB using only the first logical channel, and data of another second logical channel (e.g., a logical channel for P frames) may not be included in the TB. For example, if I frame data appears, the UE can send a CG PUSCH by constructing a TB with only I frame data even if there is P frame data. Here, if the UE sends a TB for a first logical channel (e.g., a logical channel for I frames) in a specific CG period, it is possible to expect to send a TB for a second logical channel (e.g., a logical channel for P frames) from the next CG period of the same CG configuration.

[0289] According to method 1-2, priorities for the first logical channel and the second logical channel can be configured by the base station. And, depending on whether data for a higher priority logical channel is generated by the UE, transmission of data for a lower priority logical channel can be skipped or postponed.

[0290] refer to Fig.10 , it is possible to explain that data for logical channels mapped to I frames are generated in the first CG cycle and the Nth CG cycle. Accordingly, TB 1 and TB 2 for I frames can be transmitted. Additionally, it is possible to explain that data for logical channels mapped to I frames are not generated in the remaining CG cycles. Accordingly, TBs for P frames can be transmitted.

[0291] Method 1-3: The CG window can be configured for a specific CG configuration. For CGPUSCH transmission within the configured CG window, the CG PUSCH can be sent only on a specific first logical channel (e.g., a logical channel for an I frame). In addition, the base station and the UE can expect this type of operation.

[0292] Here, the CG window may be configured individually for each logical channel, and different logical channels may simply be mapped to different CG windows.

[0293] refer to Fig.10, the first CG cycle and the Nth CG cycle can be interpreted as the case where the CG window for the I frame is configured, and the remaining CG cycles can be interpreted as the case where the CG window for the P frame is configured. Therefore, TB 1 and TB 2 of the logical channel used only for the I frame in the first CG cycle and the Nth CG cycle can be transmitted, and TBs of the logical channels used only for the P frame in the remaining CG cycles can be transmitted.

[0294] Embodiment 2: When a CG configuration is configured for the UE, the CGPUSCH for the corresponding CG configuration can be sent and received as follows.

[0295] For a specific CG (e.g., CG1), a PUSCH opportunity of TDM (i.e., TO) or a PUSCH opportunity of FDM (i.e., TO) is configured in one CG period, and repeated transmission of PUSCH of the same TB or multiple transmissions of PUSCH of different TBs can be supported. Here, another CG (e.g., CG2) can be configured with only one PUSCH opportunity (i.e., TO) or with multiple PUSCH opportunities (i.e., TO) mapped to a single TRP, and CG1 and CG2 can be connected / associated with each other.

[0296] -For TDM PUSCH transmission, if multiple PUSCH resources are allocated according to the conventional PUSCH repetition method, multiple TBs can be sent using different PUSCH resources instead of repetition of the same TB. Here, slot-based PUSCH can be arranged / allocated and sent in different slots, or subslot-based PUSCH can be arranged / allocated and sent in one or more slots.

[0297] - For FDM PUSCH transmission, multiple PUSCH resources can be allocated in the same slot of the same period using FDM. For example, different TBs for short packet data budget (PDB) or different TBs for I frames can be configured to be sent in the same slot using FDM.

[0298] -For TDM CG PUSCH resources or FDM CG PUSCH resources repeated N times in one cycle, M (M is a natural number) TBs can be sent. Here, the PUSCH resources in one cycle are grouped into N / M TDM PUSCH sets or FDM PUSCH sets, and one TB can be repeatedly sent in one TDM or FDM PUSCH set. For example, if four PUSCH resources are allocated in one CG cycle, the first two TDM or FDM CG PUSCH resources and the last two TDM or FDM CG PUSCH resources are configured to different CG PUSCH sets, and different TBs can be sent through different PUSCH sets. Here, TDM or FDM can also be performed between different PUSCH sets.

[0299] Here, FDM CG PUSCH resources or FDM CG PUSCH sets may be allocated to the same or different ULBWPs or to the same or different UL cells.

[0300] In addition, PUSCHs belonging to the same CG PUSCH set are configured with the same time / frequency resource size, but PUSCHs belonging to different PUSCH sets can also be configured with different time / frequency resource sizes.

[0301] For example, in Fig.10 In the first CG cycle, two PUSCHs for CG are sent in the same CG cycle, and different TBs can be sent (i.e., PUSCH carrying TB1 and PUSCH carrying TB2 in the first CG cycle).

[0302] In addition, different PUSCH sets within the same CG period can be mapped to different HARQ process IDs, and different PUSCHs belonging to the same PUSCH set can be mapped to the same HARQ process ID.

[0303] For example, the HARQ process ID1 for the first CG PUSCH set is determined according to Equation 7 below, and the HARQ process ID2 for the second CG PUSCH set in the same CG cycle can be determined as HARQ process ID1 of the first CG PUSCH set + the number of HARQ processes (nrofHARQ-Processes) (see Equation 8) or HARQ process ID1 of the first CG PUSCH set + offset (see Equation 9).

[0304] [Equation 7]

[0305]

[0306] In Equation 7, CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + number of slots in a frame] numberOfSlotsPerFrame represents the number of consecutive slots per frame.

[0307] The HARQ process ID2 of the second CG PUSCH set can be determined according to Equation 8 or Equation 9 below.

[0308] [Equation 8]

[0309] HARQ process ID2 = HARQ process ID1 + nrofHARQ-Processes

[0310] [Equation 9]

[0311] HARQ process ID2 = HARQ process ID1 + harq-ProcID-Set2-Offset

[0312] In Equation 9, the offset (harq-ProcID-Set2-Offset) can be configured by the base station through an RRC message or activation DCI.

[0313] In addition, depending on the configuration of the base station, different CG PUSCH sets for the UE can be configured to be mapped to different TRPs and TCI states. In addition, the same TB can be repeatedly sent with multiple TRPs through different CG PUSCH sets. In this case, the DMRS of different PUSCH sets are QCL-sent to different TCI states. In other words, the uplink transmission spatial filter of the CG PUSCH for different PUSCH sets can be determined separately based on different TCI states.

[0314] For example, in Fig.10 In the example, although two PUSCHs for CG are sent in the same CG period, they can be configured to send the same TB. Here, different PUSCHs can be mapped to the same or different TCI states, so the same TB can be sent repeatedly. Here, different PUSCH sets of the same period can have the same HARQ process ID value.

[0315] Embodiment 3: Even if there are CG resources (ie, even if CG resources are allocated according to CG configuration), a TB exceeding / exceeding the packet delay budget (PDB) or the delay requirement value may not be sent.

[0316] Hereinafter, in the description according to the present embodiment, a PDB value or a delay requirement value may mean an upper limit value of the time that a packet (data) between a UE and a network (e.g., a base station) may be delayed, and the present disclosure is not limited to the terms PDB value or delay requirement value and may be replaced by other terms.

[0317] For example, a PDB value may be configured for a logical channel. In this case, if a specific CG is mapped only to a specific logical channel, the UE may stop sending a CG PUSCH or its retransmission PUSCH based on the maximum or minimum PDB value of the specific logical channel (i.e., the maximum or minimum value among the PDB values ​​of the logical channels mapped to the specific CG).

[0318] As another example, the base station can configure a specific (e.g., worst) PDB value for a specific CG through a CG configuration index (e.g., CG-ConfigIndex). The UE can stop PUSCH transmission for the CG or retransmit PUSCH transmission for the CG based on the delay requirement value.

[0319] Hereinafter, in the description of the present embodiment, for the convenience of explanation, the transmission of CGPUSCH after the initial transmission of CG PUSCH may refer to the CG PUSCH transmission triggered without waiting for feedback on the previous transmission, and the retransmission PUSCH transmission may refer to the CG PUSCH transmission as a retransmission of the previous CG PUSCH triggered by DCI. However, the present disclosure is not limited to this, and all refer to the CG PUSCH for repeatedly sending the same TB, and may be collectively referred to as HARQ retransmission.

[0320] -In the case where multiple CG PUSCH transmissions are assigned the same HARQ process ID in a specific CG cycle, the UE can determine that a specific TB (i.e., the same TB) is repeatedly transmitted from the first CG PUSCH resource or the designated CG PUSCH resource in the specific CG cycle. In addition, if the time difference from the first or last symbol of the first CG PUSCH resource or the designated CG PUSCH resource to the first or last symbol of the Nth (N is a natural number) CG PUSCH transmission is greater than or equal to the PDB value, the UE can refresh the buffer of the HARQ process used for the TB transmission. Thereafter, the UE may not send any N+kth CG PUSCH transmission for the same TB. (k is a natural number, k=1, 2, 3, ...)

[0321] In other words, if the number of repetitions for a special CG configuration (e.g., determined by higher layer signaling or based on lower layer predefined rules, etc.) is greater than 1, the first transmission within a bundle (i.e., collectively referred to as all repetitions) (i.e., CG PUSCH transmission) can be followed by the number of repetitions within the bundle - 1 HARQ retransmission (i.e., CG PUSCH transmission). The same HARQ process can be used for repeated transmissions within a bundle. Within a bundle, HARQ retransmissions (i.e., CG PUSCH transmissions after the first CG PUSCH) can be triggered based on the number of repetitions for the CG configuration without waiting for feedback on the previous transmission. That is, the same TB can be repeatedly sent a certain number of times via CG PUSCH transmissions without retransmission feedback by the base station.

[0322] Alternatively, in the case where multiple CG PUSCH transmissions are assigned to the same HARQ process ID in a specific CG cycle, the UE can determine that a specific TB (i.e., the same TB) is repeatedly transmitted from the first CG PUSCH resource or the designated CG PUSCH resource in the specific CG cycle, and can start or restart the CG timer (e.g., configuredGrantTimer) for the corresponding HARQ process (in addition, when a new CG PUSCH for the same TB is transmitted again, the CG timer can be started or restarted.). If the CG timer expires, the UE refreshes the buffer of the corresponding HARQ process and may not send any subsequent N+kth CG PUSCH transmissions (k=1, 2, 3, ...) restricted to the same TB transmission. That is, these PUSCH transmissions are skipped. If the N+kth CG PUSCH transmission is not limited to the same TB transmission, the UE can construct a new TB and send it through the N+kth CG PUSCH, or if there is no TB to be sent, the transmission can be skipped.

[0323] Here, the CG timer value can be configured individually for each CG configuration (see Table 6 above).

[0324] Alternatively, in the case where multiple CG PUSCH transmissions are assigned the same HARQ process ID in a specific CG cycle, the UE can determine that a specific TB (i.e., the same TB) is repeatedly transmitted from the first CG PUSCH resource or the designated CG PUSCH resource in the specific CG cycle. In addition, if the time difference between the first or last symbol of the initial CG PUSCH resource or the designated CG PUSCH resource and the first or last symbol of the Nth CG PUSCH transmission is greater than or equal to the PDB value, the UE can stop the CG timer for the corresponding HARQ process.

[0325] That is, the CG timer can be stopped or not based on the PDB value (or delay requirement) configured for the corresponding CG or the corresponding logical channel. In other words, regardless of the value configured for the CG timer, the CG timer can expire depending on the PDB value.

[0326] Here, even if the TB is successfully transmitted (for example, if the UE receives an ACK for the corresponding TB from the base station), the CG timer for the corresponding HARQ process can be stopped.

[0327] In addition, if the CG timer is stopped, the UE may not send a CG PUSCH or retransmission PUSCH for the corresponding HARQ process until it is determined that the new data indicator (NDI) is switched (ie, until a new TB transmission is determined). Alternatively, if the UE stops the CG timer, the UE may determine that the NDI is switched and send a new TB from the next CG PUSCH for the corresponding HARQ process.

[0328] If it is determined that the NDI is switched for the CG PUSCH for the corresponding HARQ process (ie, it is determined that a new TB transmission is occurring), the UE may start or restart the CG timer for the corresponding HARQ process.

[0329] - In addition, in the case where the CG PUSCH transmission of a specific TB is assigned with the same HARQ process ID and the TB retransmission of its DCI-based PUSCH, the UE can determine that the specific TB (i.e., the same TB) is repeatedly transmitted from the first CG PUSCH resource or the designated CG PUSCH resource within the CG period. If the time difference from the first or last symbol of the first CG PUSCH resource or the designated CG PUSCH resource to the first or last symbol of the DCI-based PUSCH transmission is greater than or equal to the PDB value, the UE can refresh the buffer of the HARQ process used for the TB transmission. Thereafter, the UE may not send any DCI-based retransmission PUSCH transmission for the same TB (k=1, 2, 3, ...).

[0330] Alternatively, the UE may start or restart the CG timer for the corresponding HARQ process from the initial CG PUSCH resource or the designated CG PUSCH resource (in addition, when a new CG PUSCH or a DCI-based retransmission PUSCH is retransmitted for the same TB, the UE may start or restart the CG timer). If the CG timer expires, the UE may flush the buffer of the corresponding HARQ process and may not send any subsequent DCI-based retransmission PUSCH transmissions for the same TB (k=1, 2, 3, ...).

[0331] -At the same time, when the CG timer for a specific HARQ process ID expires or is stopped, the base station and the UE may consider that the CG PUSCH resources mapped to the same HARQ process ID are subsequently allocated for new TB transmission.

[0332] However, while the CG timer for a specific HARQ process ID is running, consideration may be given to using the CG PUSCH resources mapped to the same HARQ process ID for re-allocation of the TB.

[0333] Alternatively, while the CG timer for a specific HARQ process ID initially started in the Nth CG cycle is running, the CG PUSCH resources mapped to the same HARQ process ID in the N+kth CG cycle can be considered as not sending TBs (k=1, 2, 3, ...).

[0334] According to an embodiment of the present disclosure, Fig.11 A signaling procedure between a network and a UE is illustrated for a method of transmitting and receiving a configured grant PUSCH.

[0335] Fig.11 The method proposed in the present disclosure (e.g., Embodiment 1 to Embodiment 3, a combination of one or more of the methods proposed in Embodiment 1 to Embodiment 3) is illustrated in the figure, in the case of multiple TRPs (i.e., M-TRP, or multi-cell, all TRPs hereinafter can be replaced by cells), the signaling between the network (e.g., TRP 1, TRP 2) and the UE. Here, UE / network is only an example and can be replaced by various devices. Fig.11 It is only used for convenience of explanation and does not limit the scope of the present disclosure. In addition, it may be omitted depending on the situation and / or setting. Fig.11 Some of the steps are shown in the figure.

[0336] Fig.11 The signaling method described in can be extended and applied to signaling between multiple TRPs and multiple UEs. In the following description, the network can be a base station including multiple TRPs, and can also be a cell including multiple TRPs. For example, an ideal / non-ideal backhaul can be configured between TRP 1 and TRP 2 that constitute the network. In addition, the following description is based on multiple TRs, but can be equally extended and applied to transmission through multiple panels. In addition, in the present disclosure, the operation of UE receiving a signal from TRP1 / TRP2 can also be interpreted / described as the operation of UE receiving a signal from the network (via / using TRP1 / 2), and the operation of UE sending a signal to TRP1 / TRP2 can also be interpreted / described as the operation of UE sending a signal to the network (via / using TRP1 / TRP2), and vice versa.

[0337] A base station may be a general term for an object that transmits and receives data to and from a terminal. For example, a base station may be a concept including one or more transmission points (TPs), one or more transmission and reception points (TRPs), and the like. In addition, a TP and / or a TRP may include a panel, a transmission and reception unit, and the like of a base station. In addition, "TRP" may be replaced and applied with expressions such as a panel, an antenna array, a cell (e.g., a micro cell / small cell / pico cell, etc.), a TP (transmission point), a base station (base station, gNB, etc.). As described above, a TRP may be classified according to information (e.g., an index, an ID) on a CORESET group (or a CORESET pool). For example, when one UE is configured to transmit and receive multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one UE. The configuration of such a CORESET group (or CORESET pool) may be performed by higher layer signaling (e.g., RRC signaling, etc.).

[0338] The UE can receive configuration information from the network via / using TRP 1 (and / or TRP 2) (S1101).

[0339] The configuration information may include information related to the configuration of the network (eg, TRP configuration) / information related to transmission and reception based on M-TRP (eg, resource allocation, etc.). Here, the configuration information may be transmitted through higher layer signaling (eg, RRC signaling, MAC-CE, etc.).

[0340] The configuration information may include configuration information related to the CG configuration described in the method proposed in the above description (for example, embodiments 1 to 3, a combination of one or more of the methods proposed in embodiments 1 to 3). For example, one or more CG configurations may be configured to the UE, and the configuration information may include separate configuration information for each of the one or more CG configurations (for example, configuredGrantConfig IE). Here, the separate configuration information for each of the one or more CG configurations may include the information / parameters illustrated in Table 6 above.

[0341] In addition, for example, the configuration information may include information for configuring a joint TCI and / or separate DL / UL TCI. For example, the configuration information may include a list of TCI states, which provides a reference signal for QCL of a DMRS / downlink signal (e.g., CSI-RS) for a downlink channel (e.g., PDSCH, PDCCH), and / or provides a reference for determining an uplink transmission spatial filter of a DMRS / uplink signal (e.g., SRS) for an uplink channel (e.g., PUSCH, PUCCH).

[0342] In addition, for example, according to the embodiments described above, the individual configuration information for each CG configuration may include information about the logical channels associated with the corresponding CG configuration.

[0343] In addition, according to the embodiment described above, the separate configuration information for each CG configuration may include information about the TCI state for the corresponding CG configuration. Here, the TCI state for the corresponding CG configuration may be configured / indicated in the TCI state list.

[0344] At the same time, although Fig.11 , but the UE may receive a MAC CE (i.e., an activation command) from the network to activate and / or deactivate uplink (or joint) TCI states via / using TRP 1 (and / or TRP 2). This MAC CE may indicate activation and / or deactivation of one or more TCI states (i.e., one or more TCI states in a list of TCI states) for an uplink channel / signal, and may also be used to map one TCI state (i.e., a TCI state in a list of TCI states) for an uplink channel / signal to a code point of a TCI field in a DCI.

[0345] The UE can receive downlink control information from the network via / using TRP 1 (and / or TRP 2) (S1102).

[0346] As described above, when configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) is received without detecting an UL grant in the DCI, CG type 1 PUSCH transmission can be configured as semi-static operation. In this case, step S1102 can be omitted. In addition, in this case, the TCI state for one or more CG configurations configured in the UE can be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), or by the MAC CE configuration / indication described above.

[0347] In addition, after receiving configuration information for CG configuration (e.g., configuredGrantConfig excluding rrc-ConfiguredUplinkGrant), CG type 2 PUSCH transmission can be semi-statically scheduled by validly activating the UL grant in the DCI. In this case, the DCI of step S1102 can correspond to the valid activation DCI. In addition, in this case, the TCI state for one or more CG configurations configured in the UE can be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), or configured / indicated by the MAC CE described above, or indicated by a valid activation DCI.

[0348] The UE sends a configured grant (CG) PUSCH to the network via / using TRP 1 (and / or TRP 2) (S1103).

[0349] Here, the UE is able to send a CG PUSCH to the network based on the operations described in the proposed methods described above (eg, embodiments 1 to 3, a combination of one or more methods proposed in embodiments 1 to 3).

[0350] For example, according to Embodiment 1, in a CG configuration, only specific logical channels can be mapped to specific (one or more) periods, and the TB sent in the CGPUSCH can be determined according to the mapped logical channels according to the (one or more) CG periods. Alternatively, when multiple logical channels are mapped in a CG configuration, the TB sent in the CG PUSCH can be determined according to the priority of the logical channels. Alternatively, in a CG configuration, only specific logical channels can be mapped into a specific CG window, and only the CG PUSCH for the corresponding logical channel can be sent.

[0351] In addition, for example, according to Embodiment 2, multiple CGPUSCH resources within one CG PUSCH transmission period for one CG configuration can be divided into multiple CG PUSCH resource sets (i.e., a first CG PUSCH resource set and a second CG PUSCH resource set). In addition, the same or different TBs can be sent via the CG PUSCH within each CG PUSCH resource set. Here, different TCI states can be configured / indicated for each CG PUSCH resource set, and the uplink transmission spatial filter for CG PUSCH transmission in each CG PUSCH resource set can be determined separately based on the TCI state for the corresponding CG PUSCH resource set.

[0352] In addition, for example, according to Embodiment 3, if a packet delay budget (PDB) or a delay requirement value is exceeded, a CG PUSCH for a corresponding TB may not be transmitted even if CG resources are allocated.

[0353] Specifically, based on the CG configuration, an initial CG PUSCH for the first TB is sent, and a configured grant (CG) timer (e.g., configuredGrantTimer) for a HARQ process (e.g., the HARQ process ID may be determined according to Equation 5 or Equation 6 according to the position of the time slot in which the CGPUSCH is sent) may be started at the time of transmission of the initial CG PUSCH. In addition, after the transmission of the initial CG PUSCH, a CG PUSCH for retransmission of the first TB may be repeatedly sent until the CG timer stops. Here, based on a PDB value (or a delay requirement value) associated with the first TB, the retransmission of the first TB may be stopped as the CG timer is stopped. In addition, the CG timer may be stopped when the time difference from the first or last symbol of the initial CG PUSCH to the first or last symbol of the Nth (N is a natural number) CG PUSCH is greater than or equal to the PDB value. For example, the PDB value may be determined based on the PDB value for the logical channel associated with the CG configuration.

[0354] Alternatively, when the UE receives ACK for the first TB, retransmission of the first TB may be stopped.

[0355] In addition, as the CG timer is stopped, the CG PUSCH may not be sent to the HARQ process until the NDI for the HARQ process is considered to be switched. Alternatively, after the CG timer is stopped, the CG PUSCH for the second TB may be sent using the HARQ process. Here, as the CG timer is stopped, the NDI for the HARQ process is considered to be switched, and the CG PUSCH for the second TB may be sent using the HARQ process.

[0356] In addition, as the NDI considered for the HARQ process is switched, the CG timer for the HARQ process may be started.

[0357] According to an embodiment of the present disclosure, Fig.12 is a diagram illustrating the operation of a UE for a method of transmitting and receiving a configured grant PUSCH.

[0358] refer to Fig.12 , Fig.12 The operation of the UE based on the proposed method (eg, Embodiments 1 to 3, a combination of one or more methods proposed in Embodiments 1 to 3) is illustrated. Fig.12The examples are for convenience of explanation and do not limit the scope of the present disclosure. Fig.12 Some of the steps illustrated in the figure may be omitted depending on the situation and / or setting. Fig.12 The UE in is only an example and can be implemented as follows Fig.14 For example, Fig.14 The processor (102 / 202) can control the transceiver (106 / 206) to send and receive channels / signals / data / information, etc., and can also control the channels / signals / data / information to be sent or received to be stored in the memory (104 / 204).

[0359] in addition, Fig.12 The operation can be done by Fig.14 One or more processors (102, 202) of the processor, and Fig.12 The operations may be stored in a memory (eg, Fig.14 One or more memories (104, 204)) for driving Fig.14 At least one processor (eg, 102, 202).

[0360] The UE receives configuration information related to a configured grant (CG) configuration from a base station (via / using TRP 1 (and / or TRP 2)) (S1201).

[0361] The configuration information related to the CG configuration may include the configuration information related to the CG configuration described in the proposed method described above (for example, Embodiment 1 to Embodiment 3, a combination of one or more of the methods proposed in Embodiment 1 to Embodiment 3). For example, one or more CG configurations may be configured to the UE, and separate configuration information for each of the one or more CG configurations (for example, configuredGrantConfig IE) may include the information / parameters illustrated in Table 6 above.

[0362] Additionally, although Fig.12 , but the UE may receive configuration information for configuring joint TCI and / or separate DL / UL TCI from the base station (via / using TRP 1 (and / or TRP 2)). For example, the configuration information may include a list of TCI states, which provides a reference signal for the QCL of DMRS / downlink signals (e.g., CSI-RS) for downlink channels (e.g., PDSCH, PDCCH), and / or provides a reference for determining an uplink transmission spatial filter for DMRS / uplink signals (e.g., SRS) for uplink channels (e.g., PUSCH, PUCCH).

[0363] In addition, for example, according to the embodiments described above, the individual configuration information for each CG configuration may include information about the logical channels associated with the corresponding CG configuration.

[0364] In addition, according to the embodiment described above, the separate configuration information for each CG configuration may include information about the TCI state for the corresponding CG configuration. Here, the TCI state for the corresponding CG configuration may be configured / indicated within the list of TCI states.

[0365] At the same time, although Fig.12 , but the UE may receive a MAC CE (i.e., an activation command) from the base station to activate and / or deactivate uplink (or joint) TCI states (via / using TRP 1 (and / or TRP 2)). This MAC CE may indicate activation and / or deactivation of one or more TCI states (i.e., one or more TCI states in a list of TCI states) for an uplink channel / signal, and may also be used to map one TCI state (i.e., a TCI state in a list of TCI states) for an uplink channel / signal to a code point in a TCI field in a DCI.

[0366] The UE can receive downlink control information from the base station (via / using TRP 1 (and / or TRP 2)) (S1202).

[0367] As described above, when configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) is received without detecting an UL grant in the DCI, CG type 1 PUSCH transmission can be configured as semi-static operation. In this case, step S1202 can be omitted. In addition, in this case, the TCI states for one or more CG configurations configured in the UE can be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), or configured / indicated by the MAC CE described above.

[0368] In addition, after receiving configuration information for CG configuration (e.g., configuredGrantConfig excluding rrc-ConfiguredUplinkGrant), CG type 2 PUSCH transmission can be semi-statically scheduled by effectively activating the UL grant in the DCI. In this case, the DCI of step S1202 can correspond to the effectively activated DCI. In addition, in this case, the TCI states for one or more CG configurations configured in the UE can be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), or configured / indicated by the MAC CE described above, or indicated by effectively activating the DCI.

[0369] The UE transmits the configured grant (CG) PUSCH (via / using TRP 1 (and / or TRP 2)) to the base station (S1203).

[0370] Here, for example, according to Embodiment 3, if a packet delay budget (PDB) or a delay requirement value is exceeded, a CG PUSCH for a corresponding TB may not be transmitted even if CG resources are allocated.

[0371] Specifically, based on the CG configuration, an initial CG PUSCH for the first TB is sent, and a configured grant (CG) timer (e.g., configuredGrantTimer) for a HARQ process (e.g., the HARQ process ID may be determined according to Equation 5 or Equation 6 according to the position of the time slot in which the CGPUSCH is sent) may be started at the time of transmission of the initial CG PUSCH. In addition, after the transmission of the initial CG PUSCH, a CG PUSCH for retransmission of the first TB may be repeatedly sent until the CG timer stops. Here, based on a PDB value (or a delay requirement value) associated with the first TB, the retransmission of the first TB may be stopped as the CG timer is stopped. In addition, the CG timer may be stopped when the time difference from the first or last symbol of the initial CG PUSCH to the first or last symbol of the Nth (N is a natural number) CG PUSCH is greater than or equal to the PDB value. For example, the PDB value may be determined based on the PDB value for the logical channel associated with the CG configuration.

[0372] Alternatively, when the UE receives ACK for the first TB, retransmission of the first TB may be stopped.

[0373] In addition, as the CG timer is stopped, the CG PUSCH may not be sent to the HARQ process until the NDI for the HARQ process is considered to be switched. Alternatively, after the CG timer is stopped, the CG PUSCH for the second TB may be sent using the HARQ process. Here, as the CG timer is stopped, the NDI for the HARQ process is considered to be switched, and the CG PUSCH for the second TB may be sent using the HARQ process.

[0374] In addition, as the NDI considered for the HARQ process is switched, the CG timer for the HARQ process may be started.

[0375] According to an embodiment of the present disclosure, Fig.13 is a diagram illustrating the operation of a base station for a method of transmitting and receiving a configured grant PUSCH.

[0376] refer to Fig.13 , Fig.13 The operation of the base station based on the proposed method (eg, embodiments 1 to 3, or a combination of one or more methods proposed in embodiments 1 to 3) is illustrated. Fig.13 The examples are for convenience of explanation and do not limit the scope of the present disclosure. Fig.13 Some of the steps illustrated in the figure may be omitted depending on the situation and / or setting. Fig.13 The base station in is only an example and can be implemented as follows Fig.14 For example, Fig.14 The processor (102 / 202) can control the transceiver (106 / 206) to send and receive channels / signals / data / information, etc., and can also control the channels / signals / data / information to be sent or received to be stored in the memory (104 / 204).

[0377] in addition, Fig.13 The operation can be done by Fig.14 One or more processors (102, 202) of the processor, and Fig.13 The operations may be stored in a memory (eg, Fig.14 One or more memories (104, 204)) for driving Fig.14 At least one processor (eg, 102, 202).

[0378] The base station transmits configuration information related to a configured grant (CG) configuration to the UE (via / using TRP 1 (and / or TRP 2)) (S1301).

[0379] The configuration information may include configuration information related to the CG configuration described in the proposed method described above (e.g., embodiments 1 to 3, a combination of one or more of the methods proposed in embodiments 1 to 3). For example, one or more CG configurations may be configured to the UE, and separate configuration information for each of the one or more CG configurations (e.g., configuredGrantConfig IE) may include the information / parameters illustrated in Table 6 above.

[0380] Additionally, although Fig.13 Not shown in the figure, but the base station can send configuration information for configuring joint TCI and / or separate DL / UL TCI to the UE (via / using TRP 1 (and / or TRP 2)). For example, the configuration information may include a list of TCI states, which provides a reference signal for the QCL of DMRS / downlink signals (e.g., CSI-RS) for downlink channels (e.g., PDSCH, PDCCH), and / or provides a reference for determining the uplink transmission spatial filter of DMRS / uplink signals (e.g., SRS) for uplink channels (e.g., PUSCH, PUCCH).

[0381] In addition, for example, according to the embodiments described above, the individual configuration information for each CG configuration may include information about the logical channels associated with the corresponding CG configuration.

[0382] In addition, according to the embodiment described above, the separate configuration information for each CG configuration may include information about the TCI state for the corresponding CG configuration. Here, the TCI state for the corresponding CG configuration may be configured / indicated in the TCI state list.

[0383] At the same time, although Fig.13 Not shown in the figure, but the base station can send a MAC CE (i.e., an activation command) to the UE (via / using TRP 1 (and / or TRP 2)) to activate and / or deactivate the uplink (or joint) TCI state. This MAC CE can indicate the activation and / or deactivation of one or more TCI states (i.e., one or more TCI states in the list of TCI states) for the uplink channel / signal, and can also be used to map one TCI state (i.e., a TCI state in the TCI state list) for the uplink channel / signal to a code point in the TCI field in the DCI.

[0384] The base station can transmit downlink control information to the UE (via / using TRP 1 (and / or TRP 2)) (S1302).

[0385] As described above, when configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) is received without detecting an UL grant in the DCI, CG type 1 PUSCH transmission can be configured as semi-static operation. In this case, step S1302 can be omitted. In addition, in this case, the TCI states for one or more CG configurations configured in the UE can be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), or configured / indicated by the MAC CE described above.

[0386] In addition, after receiving configuration information for CG configuration (e.g., configuredGrantConfig excluding rrc-ConfiguredUplinkGrant), CG type 2 PUSCH transmission can be semi-statically scheduled by effectively activating the UL grant in the DCI. In this case, the DCI of step S1302 can correspond to the effectively activated DCI. In addition, in this case, the TCI states for one or more CG configurations configured in the UE can be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), or configured / indicated by the MAC CE described above, or indicated by effectively activating the DCI.

[0387] The base station receives a configured grant (CG) PUSCH from the UE (via / using TRP 1 (and / or TRP 2)) (S1303).

[0388] Here, for example, according to Embodiment 3, if a packet delay budget (PDB) or a delay requirement value is exceeded, a CG PUSCH for a corresponding TB may not be transmitted even if CG resources are allocated.

[0389] Specifically, based on the CG configuration, an initial CG PUSCH for the first TB is sent, and a configured grant (CG) timer (e.g., configuredGrantTimer) for a HARQ process (e.g., the HARQ process ID may be determined according to Equation 5 or Equation 6 according to the position of the time slot in which the CGPUSCH is sent) may be started at the time of transmission of the initial CG PUSCH. In addition, after the transmission of the initial CG PUSCH, a CG PUSCH for retransmission of the first TB may be repeatedly sent until the CG timer stops. Here, based on a PDB value (or a delay requirement value) associated with the first TB, the retransmission of the first TB may be stopped as the CG timer is stopped. In addition, the CG timer may be stopped when the time difference from the first or last symbol of the initial CG PUSCH to the first or last symbol of the Nth (N is a natural number) CG PUSCH is greater than or equal to the PDB value. For example, the PDB value may be determined based on the PDB value for the logical channel associated with the CG configuration.

[0390] Alternatively, when the UE receives ACK for the first TB, retransmission of the first TB may be stopped.

[0391] In addition, as the CG timer is stopped, the CG PUSCH may not be sent to the HARQ process until the NDI for the HARQ process is considered to have switched. Alternatively, after the CG timer is stopped, the CG PUSCH for the second TB may be sent using the HARQ process. Here, as the CG timer is stopped, the NDI of the HARQ process is considered to be switched, and the CG PUSCH for the second TB may be sent using the HARQ process.

[0392] In addition, as the NDI of the HARQ process is considered to be switched, the CG timer for the HARQ process may be started.

[0393] General equipment to which the present disclosure can be applied

[0394] Fig.14 is a diagram illustrating a block diagram of a wireless communication device according to an embodiment of the present disclosure.

[0395] refer to Fig.14 , the first wireless device 100 and the second wireless device 200 can send and receive wireless signals through a variety of radio access technologies (e.g., LTE, NR).

[0396] The first wireless device 100 may include 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 control the memory 104 and / or the transceiver 106 and may be configured to implement the description, function, process, proposal, method and / or operation flowchart disclosed in the present disclosure. For example, the processor 102 may send a wireless signal including the first information / signal through the transceiver 106 after generating the first information / signal by processing the information in the memory 104. In addition, the processor 102 may receive a wireless signal including the second information / signal through the transceiver 106, and then store the information obtained by signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including commands for executing all or part of the process controlled by the processor 102 or for executing the description, function, process, proposal, method and / or operation flowchart disclosed in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may send and / or receive wireless signals through one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0397] The second wireless device 200 may include one or more processors 202 and 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 control the memory 204 and / or the transceiver 206 and may be configured to implement the description, function, process, proposal, method and / or operation flowchart disclosed in the present disclosure. For example, the processor 202 may generate third information / signal by processing the information in the memory 204, and then transmit the wireless signal including the third information / signal through the transceiver 206. In addition, the processor 202 may receive a wireless signal including fourth information / signal through the transceiver 206, and then store the information obtained by signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including commands for executing all or part of the process controlled by the processor 202 or for executing the description, function, process, proposal, method and / or operation flowchart disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may send and / or receive wireless signals through one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0398] In the following, the hardware elements of the wireless device 100, 200 will be described in more detail. It is not limited thereto, and one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the descriptions, functions, processes, proposals, methods, and / or operational flow charts included in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in the present disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in the present disclosure to provide them to one or more transceivers 106, 206. The one or more processors 102, 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in the present disclosure.

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

[0400] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard drive, registers, cash memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located inside and / or outside one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 via a variety of technologies such as wired or wireless connections.

[0401] One or more transceivers 106, 206 may send user data, control information, wireless signals / channels, etc. mentioned in the methods and / or operation flow charts, etc. of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc. mentioned in the description, function, process, proposal, method and / or operation flow chart, etc. disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may send and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to send user data, control information or wireless signals to one or more other devices. In addition, 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. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to send and receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed in the present disclosure through one or more antennas 108, 208. In the present invention, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc. from RF band signals to baseband signals by using one or more processors 102, 202 to process received user data, control information, wireless signals / channels, etc. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals to RF band signals. Therefore, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0402] The above-mentioned embodiments are elements and features of the present disclosure combined in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be considered optional. Each element or feature can be implemented in a form that is not combined with other elements or features. In addition, the embodiments of the present disclosure may include combined partial elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. It is clear that an embodiment may include a combined claim without an explicit dependency in the claim, or may be included as a new claim by modification after application.

[0403] It is clear to those skilled in the art that the present disclosure can be implemented in other specific forms within the scope of the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect, but should be considered as illustrative. The scope of the present invention should be determined by the reasonable interpretation of the attached claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present invention.

[0404] The scope of the present disclosure includes software or machine executable commands (e.g., operating systems, applications, firmware, programs, etc.) that perform operations in a device or computer according to the methods of various embodiments, and non-transitory computer-readable media that store such software or commands, etc. and can be executed in a device or computer. Commands that can be used to program a processing system that performs the features described in the present disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in the present disclosure can be implemented by using a computer program product that includes such a storage medium. The storage medium may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, but is not limited thereto, and it may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices located away from the processor. The memory or alternatively, the non-volatile memory device in the memory includes a non-transitory computer-readable storage medium. The features described in this disclosure may be stored in any machine-readable medium to control the hardware of a processing system, and may be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results from 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.

[0405] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include narrowband Internet of Things for low-power communication, as well as LTE, NR and 6G. Here, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, which may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. In addition or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may perform communication based on LTE-M technology. Here, in the example, LTE-M technology may be an example of LPWAN technology and may be referred to as various names such as eMTC (enhanced machine type communication). For example, LTE-M technology may be implemented in at least any one of the various standards including 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, etc., and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100, 200 of the present disclosure may include at least any one of ZigBee, Bluetooth, and a low power wide area network (LPWAN) considering low power communication, and it is not limited to the above names. In an example, the ZigBee technology may generate a PAN (Personal Area Network) related to small / low power digital communication based on various standards such as IEEE 802.15.4, etc., and may be referred to by various names.

[0406] [Industrial Availability]

[0407] The method proposed in the present invention is mainly described by taking the application in 3GPP LTE / LTE-A and 5G systems as an example, but can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving configuration information associated with a configured grant (CG) configuration from a base station; Based on the configuration information, an initial CG PUSCH (Physical Uplink Shared Channel) for a first transport block (TB) is sent to the base station, wherein a CG timer for a hybrid automatic repeat request (HARQ) process is started at the transmission of the initial CG PUSCH; and After the transmission of the initial CG PUSCH, repeatedly sending a CGPUSCH for retransmission of the first TB to the base station until the CG timer stops, Wherein, based on a packet delay budget (PDB) value associated with the first TB, as the CG timer stops, retransmission of the first TB is stopped.

2. The method according to claim 1, wherein: The PDB value is determined based on the PDB value of the logical channel used to link to the CG configuration.

3. The method according to claim 1, wherein: After the CG timer stops, the CGPUSCH for the second TB is sent using the HARQ process.

4. The method according to claim 1, wherein: Based on the time difference from the first or last symbol of the initial CG PUSCH to the first or last symbol of the Nth (N is a natural number) CG PUSCH being greater than or equal to the PDB value, the CG timer is stopped.

5. The method according to claim 1, wherein: Based on receiving an ACK (acknowledgement) for the first TB, retransmission of the first TB is stopped.

6. The method according to claim 1, wherein: With the CG timer stopped, the HARQ process is not used to send a CG PUSCH until a new data indicator (NDI) for the HARQ process is considered to be switched.

7. The method according to claim 1, wherein: As the CG timer is stopped, the new data indicator (NDI) for the HARQ process is considered to be switched, and the CG PUSCH for the second TB is sent using the HARQ process.

8. The method according to claim 1, wherein: As a new data indicator (NDI) for the HARQ process is deemed to be switched, the CG timer for the HARQ process is started.

9. A user equipment (UE) operating in a wireless communication system, the UE comprising: at least one transceiver, the at least one transceiver configured to send and receive wireless signals; as well as at least one processor configured to control the at least one transceiver, Wherein, the at least one processor is configured to: receiving configuration information associated with a configured grant (CG) configuration from a base station; Based on the configuration information, an initial CG PUSCH (Physical Uplink Shared Channel) for a first transport block (TB) is sent to the base station, wherein a CG timer for a hybrid automatic repeat request (HARQ) process is started at the transmission of the initial CG PUSCH; and After transmission of the initial CG PUSCH, repeatedly sending a CGPUSCH for retransmission of the first TB to the base station until the CG timer is stopped, Wherein, based on a packet delay budget (PDB) value associated with the first TB, as the CG timer stops, retransmission of the first TB is stopped.

10. At least one non-transitory computer-readable medium storing at least one instruction, wherein the at least one instruction executable by the at least one processor controls a user equipment (UE): receiving configuration information associated with a configured grant (CG) configuration from a base station; Based on the configuration information, an initial CG PUSCH (Physical Uplink Shared Channel) for a first transport block (TB) is sent to the base station, wherein: A CG timer for a hybrid automatic repeat request (HARQ) process is started upon transmission of the initial CG PUSCH; and After transmission of the initial CG PUSCH, repeatedly sending a CGPUSCH for retransmission of the first TB to the base station until the CG timer is stopped, Wherein, based on a packet delay budget (PDB) value associated with the first TB, as the CG timer stops, retransmission of the first TB is stopped.

11. A processing device configured to control a user equipment (UE) in a wireless communication system, the processing device comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and storing instructions that, upon execution by the at least one processor, perform operations comprising: receiving configuration information associated with a configured grant (CG) configuration from a base station; Based on the configuration information, an initial CG PUSCH (Physical Uplink Shared Channel) for a first transport block (TB) is sent to the base station, wherein a CG timer for a hybrid automatic repeat request (HARQ) process is started at the transmission of the initial CG PUSCH; and After transmission of the initial CG PUSCH, repeatedly sending a CGPUSCH for retransmission of the first TB to the base station until the CG timer is stopped, Wherein, based on a packet delay budget (PDB) value associated with the first TB, as the CG timer stops, retransmission of the first TB is stopped.

12. A method performed by a base station in a wireless communication system, the method comprising: sending configuration information related to a configured grant (CG) configuration to a user equipment (UE); receiving, based on the configuration information, an initial CG PUSCH (Physical Uplink Shared Channel) for a first transport block (TB) from the UE, wherein a CG timer for a hybrid automatic repeat request (HARQ) process is started upon transmission of the initial CG PUSCH; and after reception of the initial CG PUSCH, repeatedly receiving a CGPUSCH for retransmission of the first TB from the UE until the CG timer is stopped, Wherein, based on a packet delay budget (PDB) value associated with the first TB, as the CG timer stops, retransmission of the first TB is stopped.

13. A base station operating in a wireless communication system, the base station comprising: at least one transceiver, the at least one transceiver configured to send and receive wireless signals; as well as at least one processor configured to control the at least one transceiver, Wherein, the at least one processor is configured to: sending configuration information related to a configured grant (CG) configuration to a user equipment (UE); receiving, based on the configuration information, an initial CG PUSCH (Physical Uplink Shared Channel) for a first transport block (TB) from the UE, wherein a CG timer for a hybrid automatic repeat request (HARQ) process is started upon transmission of the initial CG PUSCH; and after reception of the initial CG PUSCH, repeatedly receiving a CGPUSCH for retransmission of the first TB from the UE until the CG timer is stopped, Wherein, based on a packet delay budget (PDB) value associated with the first TB, as the CG timer stops, retransmission of the first TB is stopped.