Method and apparatus for transmitting and receiving grant PUSCH signals set in a wireless communication system

Abstract

A grant PUSCH transmission and reception method and apparatus configured in a wireless communication system are disclosed. The method according to an embodiment of the present disclosure includes receiving, from a base station, individual configuration information related to one or more CG configurations, and transmitting UCI to the base station, where the UCI includes information related to a resource at which a CG PUSCH for the one or more CG configurations is resumed, and the CG PUSCH is not transmitted before a resource determined by the information related to the resource at which the CG PUSCH is resumed, and transmitting, to the base station, the CG PUSCH for the one or more CG configurations from the resource determined by the information related to the resource at which the CG PUSCH is resumed.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems, and more particularly to methods and apparatus for transmitting and receiving configured grant (CG) physical uplink shared channel (PUSCH) in wireless communication systems. [Background technology]

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

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

[0004] A technical problem of the present disclosure is to provide a method and apparatus for adjusting the transmission timing of a CG PUSCH relative to a CG setting or activating a deactivated CG.

[0005] Another technical problem of the present disclosure is to provide a method and apparatus for transmitting and receiving CG PUSCH for multiple connected / linked CG configurations.

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

[0007] According to one embodiment of the present disclosure, a method performed by a user equipment (UE) may include: receiving individual configuration information related to one or more configured grant (CG) configurations from a base station; transmitting uplink control information (UCI) to the base station, the UCI including information related to a resource on which a next CG PUSCH (physical uplink shared channel) transmission for the one or more CG configurations will occur, and the CG PUSCH transmission for the one or more CG configurations is not performed before a resource determined by the information related to the resource on which the next CG PUSCH transmission will occur; and transmitting the CG PUSCH for the one or more CG configurations to the base station on a resource determined by the information related to the resource on which the next CG PUSCH transmission will occur.

[0008] According to another aspect of the present disclosure, a method performed by a base station in a wireless communication system may include: transmitting individual configuration information related to one or more configured grant (CG) configurations to a user equipment (UE); receiving uplink control information (UCI) from the UE, the UCI including information related to a resource on which a next CG PUSCH (physical uplink shared channel) transmission will occur for the one or more CG configurations, and no CG PUSCH transmission for the one or more CG configurations is received before a resource determined by the information related to the resource on which the next CG PUSCH transmission will occur; and receiving the CG PUSCH for the one or more CG configurations from the UE on a resource determined by the information related to the resource on which the next CG PUSCH transmission will occur. [Effects of the Invention]

[0009] According to an embodiment of the present disclosure, CG PUSCHs for multiple connected / linked CG configurations can be transmitted and received.

[0010] Furthermore, according to the embodiment of the present disclosure, resources for a CG setting can be quickly adjusted, thereby enabling optimized resource allocation for the CG setting.

[0011] Furthermore, according to the embodiments of the present disclosure, CG resources can be efficiently managed to support XR (extended reality) operations.

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

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

[0014] [Figure 1] 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied. [Figure 2] 1 illustrates an example of a frame structure in a wireless communication system to which the present disclosure can be applied. [Figure 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied. [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied. [Figure 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied. [Figure 6] 1 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels. [Figure 7] Illustrates the structure / pattern of a group of pictures. [Figure 8] 1 illustrates an example of multiple configured grant configurations according to one embodiment of the present disclosure. [Figure 9] 10 illustrates a signaling procedure between a network and a UE for a configured grant PUSCH transmission / reception method according to one embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating the operation of a UE with respect to a configured grant PUSCH transmission / reception method according to one embodiment of the present disclosure. [Figure 11] FIG. 10 is a diagram illustrating the operation of a base station for a configured grant PUSCH transmission / reception method according to one embodiment of the present disclosure. [Figure 12] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

[0028] - BM: Beam management

[0029] - CQI: Channel Quality Indicator

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

[0031] - CSI: Channel State Information

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

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

[0034] - DMRS: Demodulation Reference Signal

[0035] - FDM: Frequency Division Multiplexing

[0036] - FFT: Fast Fourier transform

[0037] - IFDMA: Interleaved frequency division multiple access

[0038] - IFFT: Inverse fast Fourier transform

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

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

[0041] - MAC: Medium Access Control

[0042] - NZP: Non-zero power

[0043] - OFDM: Orthogonal frequency division multiplexing

[0044] - PDCCH: Physical downlink control channel

[0045] - PDSCH: Physical downlink shared channel

[0046] - PMI: Precoding matrix indicator

[0047] - RE: resource element

[0048] - RI: Rank indicator

[0049] - RRC: Radio resource control

[0050] - RSSI: received signal strength indicator

[0051] - Rx: Reception

[0052] - QCL: quasi co-location

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

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

[0055] - TDM: time division multiplexing

[0056] - TRP: transmission and reception point

[0057] - TRS: Tracking reference signal

[0058] - Tx: transmission

[0059] - UE: User equipment

[0060] - ZP: Zero power

[0061] System in general

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

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

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

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

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

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

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

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

[0070] [Table 1]

[0071] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands, a 30 kHz / 60 kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidths, and a 60 kHz or higher SCS supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0072] The NR frequency band is defined as two types of frequency ranges (FR1 and FR2). FR1 and FR2 may be configured as shown in Table 2 below. FR2 may also refer to millimeter wave (mmW).

[0073] [Table 2]

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

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

[0076] [Table 3]

[0077] [Table 4]

[0078] Figure 2 shows an example where μ = 2 (SCS is 60 kHz), and one subframe can include four slots as shown in Table 3. One subframe = {1, 2, 4} slots shown in Figure 2 is an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols.

[0079] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered. The physical resources that can be considered in an NR system will be specifically described below.

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

[0081] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0082] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB It consists of subcarriers, and one subframe is 14.2 μ In the NR system, a transmitted signal is composed of N OFDM symbols. RBμ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RB μ ≦N RB max,μ The above N RB max,μ represents the maximum transmission bandwidth, which may vary not only depending on the numerology but also between the uplink and downlink. In this case, one resource grid may be configured for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and is represented by an index pair. JPEG0007785974000005.jpg7169, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG0007785974000006.jpg7169 represents the position of a symbol within a subframe. When referring to resource elements within a slot, the index pair (k, l) is used, where l = 0,...,N symb μ μ and the resource element for antenna port p. JPEG0007785974000007.jpg7169 is a complex value JPEG0007785974000008.jpg8169. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indices p and μ may be dropped, so that the complex value is JPEG0007785974000009.jpg9169 or JPEG0007785974000010.jpg7169. Also, a resource block (RB) is a set of N sc RB = 12 consecutive subcarriers.

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

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

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

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

[0087]

number

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

[0089]

number

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0104] [Table 5]

[0105] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), hybrid-automatic repeat and request (HARQ) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0106] DCI format 0_0 is used for PUSCH scheduling in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled using a Cell Radio Network Temporary Identifier (C-RNTI), a Configured Scheduling RNTI (CS-RNTI), or a Modulation Coding Scheme Cell RNTI (MCS-C-RNTI) before being transmitted.

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

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

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

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

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

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

[0113] Quasi-Co Location (QCL)

[0114] Antenna ports are defined such that the channel on which symbols on an antenna port are carried can be inferred from the channel on which other symbols on the same antenna port are carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-located) relationship if the properties of the channel on which symbols on one antenna port are carried can be inferred from the channel on which symbols on the other antenna port are carried.

[0115] Here, the channel characteristics include one or more of delay spread, Doppler spread, frequency / Doppler shift, average received power, received timing / average delay, and spatial Rx parameter, where the spatial Rx parameter refers to a spatial (reception) channel characteristic parameter such as angle of arrival.

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

[0117] Each TCI-State contains parameters for setting quasi-co-location relationships between one or two DL reference signals and DM-RS ports of the PDSCH.

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

[0119] 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:

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

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

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

[0123] - "QCL-TypeD":{Spatial Rx parameter}

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

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

[0126] Uplink configured grant

[0127] PUSCH configured grants (CGs) are classified into CG Type 1 and CG Type 2.

[0128] CG Type 1 is configured or released completely through resource allocation using RRC signaling. When CG Type 1 is configured, the terminal is assigned a resource set that can transmit PUSCH periodically, and PDCCH is requested only when retransmission is necessary. CG Type 1 PUSCH transmission is semi-statically configured to operate when receiving the higher layer parameter configuredGrantConfig including rrc-ConfiguredUplinkGrant without detecting a UL grant in DCI. The terminal can perform PUSCH transmission according to the configured CG Type 1 until additional RRC signaling is reconfigured for the terminal.

[0129] In CG Type 2, resource allocation is partially configured using RRC signaling, and activation / deactivation is indicated using PDCCH transmission. Since the PDCCH also provides time and frequency resource allocation, the resource allocation may change every time it is activated. CG Type 2 PUSCH transmission is semi-persistently scheduled by the UL grant in a valid activation DCI after receiving the higher layer parameter configuredGrantConfig, which does not include rrc-ConfiguredUplinkGrant.

[0130] One or more CG configurations of CG Type 1 and / or CG Type 2 may be activated simultaneously on an activated BWP of a serving cell.

[0131] In a PUSCH transmission corresponding to CG Type 1 or CG Type 2, parameters for the PUSCH transmission may be provided by configuredGrantConfig.

[0132] Table 6 shows an example of the configuredGrantConfig IE. The configuredGrantConfig IE is used to configure uplink transmission without dynamic grant via DCI. In practice, uplink grants may be configured by RRC (CG Type 1) or provided by PDCCH (via CS-RNTI) (CG Type 2). Multiple CG configurations may be configured within one BWP of a serving cell.

[0133] [Table 6-1] [Table 6-2]

[0134] In Table 6, "periodicity" represents the period for uplink CG transmission, which means the time interval 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.

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

[0136] repK represents the number of repetitions, i.e., indicates the repetition level for each PUSCH transmission. repK may have one value of {1, 2, 4, 8}. In the case of CG Type 1, if the pusch-RepTypeIndicator in the rrc-ConfiguredUplinkGrant indicates 'pusch-RepTypeB', PUSCH repetition type B is applied; otherwise, PUSCH repetition type A is applied. In the case of CG Type 2, the PUSCH repetition type is determined by the UL grant of the DCI. The UE repeats and transmits the uplink TB for the configured number of repetitions according to the configured PUSCH repetition type A or B.

[0137] repK-RV represents the redundancy version sequence. repK-RV is set when repetition is used (i.e., when repK is set to one of the values ​​{2, 4, 8}).

[0138] resourceAllocation represents the setting of bitmap-based resource allocation type 0 or resource indication value (RIV)-based resource allocation type 1.

[0139] The mcs-Table indicates an MCS table to be used by the terminal for a PUSCH in which transform precoding is not used, and the mcs-TableTransformPrecoder indicates an MCS table to be used by the terminal for a PUSCH in which transform precoding is used. The transformPrecoder indicates whether transform precoding is enabled for the PUSCH.

[0140] rrc-ConfiguredUplinkGrant is a setting for CG Type 1 transmission. If this field is not present, the UE uses the UL grant configured by the DCI according to the CS-RNTI (i.e., CG Type 2). timeDomainAllocation indicates the start symbol and length of the PUSCH and the PUSCH mapping type. timeDomainOffset represents an offset relative to the reference SFN (system frame number) indicated by timeReferenceSFN. timeReferenceSFN indicates the SFN used to determine the resource offset in the time domain. The UE uses the SFN closest to the number indicated before receiving the configured grant setting, and if this field is not present, the reference SFN is 0.

[0141] After an uplink grant is configured for CG Type 1, the MAC entity sequentially considers that the Nth (N≧0) uplink grant occurs within a symbol according to the following Equation 3. That is, when CG Type 1 is used, a CG PUSCH may be transmitted at a transmission occasion / opportunity that satisfies the following Equation 3.

[0142]

number

[0143] Also, after the uplink grant is configured for CG Type 2, the MAC entity sequentially considers that the Nth (N≧0) uplink grant occurs within a symbol according to the following Equation 4. That is, when CG Type 2 is used, the CG PUSCH may be transmitted at a transmission occasion / opportunity that satisfies the following Equation 4.

[0144]

number

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

[0146] Furthermore, timeReferenceSFN is used to determine the offset of resources in the time domain, and the UE can use the SFN closest to the number indicated before receiving the configured CG. timeDomainOffset represents the offset relative to the reference SFN indicated by timeReferenceSFN. periodicity represents the periodicity of UL transmission for CG Type 1. timeReferenceSFN, timeDomainOffset, and periodicity may be configured by configuredGrantConfig (see Table 6). Furthermore, S corresponds to the start symbol deduced from timeDomainAllocation (see Table 6), and N is an integer value corresponding to the Nth transmission occasion / opportunity.

[0147] Also, SFN start time , slot start time and symbol start time denote the SFN, slot, and symbol of the first transmission occasion (transmission opportunity) of the PUSCH for which the CG is (re)initialized (i.e., in a PUSCH transmission that occurs due to resource allocation in an active PDCCH), respectively.

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

[0149] When an offset (e.g., harq-ProcID-Offset2) used to derive an HARQ process ID and a retransmission timer (cg-RetransmissionTimer) are not configured, the UE derives an HARQ process ID associated with a slot where uplink transmission starts from the following Equation 5. Alternatively, when an offset (e.g., harq-ProcID-Offset2) used to derive an HARQ process ID is configured, the UE derives an HARQ process ID associated with a slot where uplink transmission starts from the following Equation 6.

[0150]

number

[0151]

number

[0152] In Equations 5 and 6, nrofHARQ-Processes defines the number of uplink HARQ processes and may 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.

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

[0154] 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) that the UE waits for a retransmission request after transmitting an uplink packet. The CG timer is driven independently for each HARQ process.

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

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

[0157] The UE can assume a positive acknowledgment when the CG timer expires. The UE assumes a positive acknowledgment when this timer expires (i.e., if it does not receive a retransmission request until the timer expires), allowing the UE to subsequently transmit new uplink data using the same HARQ process.

[0158] This CG timer needs to be set long enough to ensure that the base station has time to receive the uplink packet and schedule a retransmission request. However, if the CG timer is set too long, the UE may not be able to reuse the HARQ process for a new transmission until it receives a positive acknowledgment for the previous transmission, which may result in delays.

[0159] Configured grant (CG) PUSCH transmission / reception method

[0160] This disclosure proposes a method for reducing power consumption and improving radio resource efficiency while ensuring the availability and reliability of transmission resources when video information of an Extended Reality (XR) service is transmitted using pre-configured resources such as a configured grant (CG) of an NR wireless communication system.

[0161] In NR, one or more CG PUSCHs can be configured in a UE for periodic transmission and reception or low latency and PDCCH overhead. Each CG configuration may be periodically repeated for configured / instructed resources. That is, the initially configured / instructed resource allocation is repeated at the configured period, allowing the UE to perform uplink transmission on the resource without another PDCCH reception process.

[0162] Meanwhile, various types of data can be generated in XR. Among these data, UE sensor and location information and video data, which are generally reported at specific intervals, are considered to be transmitted and received by CG resources. The traffic arrival time of such data is not always constant due to reasons such as video encoding time, sensor measurement time, upper layer operations, or changes in the network routing to be transmitted, and jitter can occur.

[0163] If resources are allocated at a location far enough away in time from the expected traffic occurrence point, taking jitter into consideration, resource availability can be guaranteed, but delays may occur. Conversely, if CG resources with a fixed period are allocated at the expected data occurrence point, larger delays may occur due to the wait time until the next available resource when jitter occurs.

[0164] Furthermore, because some data is generated based on events, it is impossible to accurately determine the actual time of data generation. However, to reduce the delay caused by scheduling, it is considered to use CG resources for such data as well. In this case, a skipping method has been discussed, in which a sufficient number of resources are allocated in a short period in preparation for data generation, and the UE or the base station selectively uses these resources while not actually using other resources. However, to use the method of skipping transmission and reception, it is necessary to consider a response signal between the UE and the base station to determine whether or not a transmission or reception has occurred. If the UE sends a response signal even for a transmission that it has not received, the base station must always prepare resources for the UE to send the response signal. Furthermore, since the skipping method is based on allocating a sufficient number of resources within the radio resources, it can impose a heavy uplink burden. Furthermore, considering that such resources may be multiplexed between UEs, the burden of uplink resources should be given even greater consideration.

[0165] Since ensuring low latency is essential for the quality of XR services, it is necessary to consider a method for minimizing the impact on latency while reducing the impact of jitter.To solve this problem, the present disclosure describes a method for selectively using some of a plurality of CG resources established between a UE and a base station, and for simply transmitting a response to the used CG resource to a predetermined location.

[0166] A group of pictures (GOP) in video coding may include the following picture types:

[0167] An I-picture or I-frame (i.e., intra-coded picture) (also known as a keyframe or i-frame) is a picture that is coded independently of all other pictures. Each GOP begins with a picture of this type (in decoding order).

[0168] 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 could only reference one picture, which must precede the P picture in display order and decoding order and must be an I or P picture. Such restrictions do not apply to the newer standards H.264 / MPEG-4 AVC and HEVC.

[0169] A B picture or B frame (bipredictively coded picture) contains motion-compensated difference information relative to a 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 of which precedes the B picture in display order and the other of which follows the B picture, and all referenced pictures must be I or P pictures. This restriction does not apply to the newer standards H.264 / MPEG-4 AVC and HEVC.

[0170] D-pictures or D-frames (direct coded (DC) pictures) serve as fast-access representations of pictures for loss robustness or fast-forward. D-pictures are only used in MPEG-1 video.

[0171] FIG. 7 illustrates the structure / pattern of a group of pictures.

[0172] 7, an I-frame indicates the start of a GOP, followed by multiple P and B-frames. Previous designs were relatively limited in the ordering and referencing structure allowed.

[0173] The GOP structure is often referred to as two numbers, e.g., M=3, N=12. The first number (M) represents the distance between two anchor frames (I or P). The second number (N) is the GOP size, which tells the distance between two full images (I-frames). For example, if M=3, N=12, the GOP structure is IBBPBBPBBPBBI. Instead of the M parameter, the maximum number of B frames between two consecutive anchor frames can also be used.

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

[0175] An I-frame contains the full image and does not require any additional information to reconstruct it. Generally, encoders use a GOP structure that ensures that each I-frame is a "clean random access point." Therefore, decoding can start cleanly with an I-frame, and any errors in the GOP structure are corrected after processing the correct I-frame.

[0176] Hereinafter, the present disclosure will describe the proposed method based on semi-statically configured uplink CG radio resources. However, this is for convenience of explanation, and the method proposed in the present disclosure is not limited thereto. Therefore, it will be understood by those skilled in the art that the method proposed in the present disclosure can be extended and applied to radio resources allocated by dynamic scheduling received by a UE. For example, the method of determining one HARQ-ACK timing for multiple downlink radio resources allocated by a UE may be applied regardless of the SPS PDSCH or the PDSCH indicated by dynamic scheduling. Furthermore, the method proposed in the present disclosure may be applied when multiple radio resources are configured not semi-statically but by dynamic instruction, for example, when multiple radio resources are configured at once by DCI. Therefore, the method proposed in the present disclosure may be applied to any type of transmission / reception scheme expected by a base station and a terminal, unless otherwise specified, as long as the principles of the proposed method are not violated. Hereinafter, in this disclosure, for convenience of explanation, semi-persistent scheduling (SPS) may be used as a general concept to collectively refer to semi-statically configured radio resources (e.g., DL / UL SPS, CG).

[0177] In addition, in this disclosure, a transmission opportunity (TO) refers to a radio resource (e.g., a CG PUSCH) configured for CG use. An entity transmitting in a transmission opportunity (i.e., a base station in the downlink, a UE in the uplink) can attempt to transmit in the TO, and a receiver (i.e., a UE in the downlink, a base station in the uplink) can attempt to receive in anticipation of transmission in each TO.

[0178] In the following, this disclosure will be described using examples based on an NR system to explain the principles of the proposed method, but the proposed method is not limited to a specific NR transmission / reception format unless otherwise specified. Also, in the following, this disclosure will be described using examples based on the characteristics and structure of an XR service to explain the principles of the proposed method, but the proposed method is not limited to supporting an XR service unless otherwise specified. Therefore, the method proposed in this disclosure may be applied to any wireless communication transmission / reception structure and service, even if not otherwise specified, as long as the principles of the proposed method are not violated.

[0179] In the following, the present disclosure proposes a method for linking / associating multiple CG settings for multiple CG resources established between a UE and a base station in preparation for the occurrence of GOP pattern jitter and / or a method for activating / transmitting a second CG transmission using a linked / associated first CG transmission. The present disclosure also proposes a method for adjusting the transmission timing of a CG PUSCH or activating a deactivated CG in consideration of uplink traffic jitter. This enables quick response to uplink virtual reality (VR) / entended reality (XR) video traffic transmission due to UE movement and optimized CG resource allocation in consideration of uplink video traffic jitter.

[0180] To this end, the method proposed in this disclosure may include a method in which a base station allocates CG radio resources to a UE and a method in which a base station receives and transmits CG resources. The method proposed in this disclosure may also include a method in which a base station transmits a HARQ-ACK response to a CG PUSCH reception result, and then receives a retransmission DCI from the base station on a PDCCH. The method proposed in this disclosure may also include a process in which a UE transmits a signal and a channel for informing its capability and / or service requirements, and the base station receives the signal and a channel.

[0181] The method proposed in this disclosure may be applied by selecting some of the following methods. In addition, each method proposed in this disclosure may operate independently without any other combination, or one or more methods may be combined and operated in a linked form. Some terms, symbols, and sequences used to describe the method proposed in this disclosure may be replaced with other terms, symbols, and sequences as long as the principles of the invention are maintained.

[0182] In the present disclosure, the following CG setting, activation / deactivation, transmission / reception operations, etc. may be supported. That is, the following CG setting, activation / deactivation, transmission / reception operations, etc. may be incorporated into the method proposed in the present disclosure.

[0183] FIG. 8 illustrates a plurality of configured grant settings according to one embodiment of the present disclosure.

[0184] - Multiple CGs (e.g., CG1 and CG2 in the case of two CGs) may be configured as one CG group by linking / associating CG configurations with each other, where CG1 may be configured as the primary CG and CG2 may be configured as the secondary CG. Here, the secondary CG may be a CG that is activated or received by transmission of the primary CG. For example, in FIG. 8, the CG configuration for CG PUSCH 1 may be the primary CG configuration, and the CG configuration for CG PUSCH 2 may be the secondary CG configuration, and the two CG configurations may be configured as one CG group.

[0185] The primary CG and the secondary CG may be configured with different CG configuration indexes, or may be configured with the same CG configuration index but may be distinguished by an RRC message, MAC CE, or DCI as a primary / secondary CG indicator or different sub-indexes.

[0186] i) When the DCI indicates CG1 and also indicates activation, the UE can activate CG2 at the same time as activating CG1 or after a certain period of time.

[0187] ii) Or, when the DCI indicates both CG1 and CG2 and also indicates activation, the UE can activate CG2 simultaneously with activating CG1 or after a certain period of time. For example, Figure 8 illustrates a case in which one DCI indicates activation of both CG configuration for CG PUSCH 1 and CG configuration for CG PUSCH 2. Also, it illustrates a case in which CG configuration for CG PUSCH 1 and CG configuration for CG PUSCH 2 are activated simultaneously.

[0188] Here, the DCI may include all the different CG setting indexes for CG1 and CG2.

[0189] Alternatively, the DCI may include a CG setting index for CG1 to indicate a secondary CG indicator.

[0190] Alternatively, the DCI may include a CG setting index for CG2, indicating the primary CG indicator.

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

[0192] Alternatively, the DCI may indicate a common CG configuration index for CG1 and CG2. For example, among HARQ process ID (identity) values ​​indicating a CG configuration index, values ​​in the range of 1 to 8 may be set as conventional CG configuration indexes (i.e., to indicate a single CG configuration), and HARQ process ID values ​​greater than 8 may be set as CG configuration indexes that simultaneously indicate multiple concatenated CGs.

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

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

[0195] For example, referring to Figure 8, different logical channels may be configured / assigned for I frames and P frames. Also, the logical channel for I frames may be mapped to a CG for CG PUSCH 1, and the logical channel for P frames may be mapped to a CG for CG PUSCH 2.

[0196] The activation or transmission / reception of CG2 may be determined depending on whether or not CG1 is activated or transmitting / receiving. Here, the activation of CG2 may be set to occur simultaneously with or after the activation of CG1.

[0197] The UE can expect that CG2 PUSCH transmission occurs only after CG1 PUSCH transmission. Therefore, the CG2 PUSCH transmission in the next cycle may be determined depending on whether or not CG1 PUSCH transmission occurs.

[0198] When the CG1 PUSCH and the CG2 PUSCH are transmitted / allocated using TDM or FDM in the same period or in partially overlapping periods, the UE may determine that the CG2 PUSCH resource is not available or may skip the CG2 PUSCH transmission when transmitting the CG1 PUSCH. Alternatively, the UE may deactivate the CG2 or deactivate an activated CG2. For example, as shown in FIG. 8, 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. Furthermore, the CG configurations for N CG PUSCHs 2 within one period of the CG configuration for CG PUSCH 1 may overlap. That is, as shown in FIG. 8, in the first period of CG PUSCH 2, CG PUSCH 2 and CG PUSCH 1 may be allocated using TDM or FDM. In this case, it may be determined that the resources for CG PUSCH 2 (PUSCH 2 carrying TB2 for the I frame in FIG. 8) are not valid, or it may be determined to skip the transmission of CG PUSCH 2.

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

[0200] When a base station configures and activates a periodic radio resource (e.g., CG) for a UE, the base station can allocate multiple radio resources to the UE within one period. The multiple radio resources may be allocated by repeating the same time / frequency resource allocation within a slot at regular intervals (e.g., M slots (M is a natural number)) (e.g., radio resources of three symbols are repeatedly allocated to the same position in each slot), or by consecutively repeatedly allocating radio resources of the same length to symbols consecutive to the first radio resource (e.g., radio resources of three symbols are repeatedly allocated consecutively). The number N of radio resources (N is a natural number) may be determined by L1 signaling and / or higher layer signaling. For example, although FIG. 8 illustrates an example in which only one radio resource is allocated to both CG PUSCH 1 and CG PUSCH 2 within one period, multiple radio resources may be allocated within one period.

[0201] The base station / UE may transmit using one or some of the multiple CG radio resources within the period according to a traffic pattern. Here, the earliest radio resource available for transmitting a transmission block (TB) including user data may be selected, taking into account the time point when user data is generated by the base station / UE.

[0202] In the present disclosure, a base station may activate multiple CGs that are linked / associated with each other using one DCI or different DCIs. Here, different CGs may be mapped to the same or different UL cells. Also, different CGs may be mapped to the same or different UL bandwidth parts (BWPs). Also, different CGs may be mapped to the same or different resource block (RB) sets. For example, when two CGs are linked / associated, different periodic CG PUSCH resources for the two CGs may be assigned to one or more UL cells, one or more UL BWPs, or one or more RB sets.

[0203] Example 1: When multiple CG configurations configured in a UE are linked / interlocked with each other, the CG PUSCH for each CG configuration may be transmitted and received as follows.

[0204] Here, multiple CG settings may be mapped to one or more different logical channels, or may be mapped to the same one or more logical channels, or may be mapped to some overlapping logical channels.

[0205] When CG1 (i.e., CG Configuration Index 1) (e.g., CG-ConfigIndex) is mapped to a logical channel for an I frame, and CG2 (i.e., CG Configuration Index 2) is mapped to both a logical channel for an I frame and a logical channel for a P frame, and CG1 and CG2 are configured as concatenated / linked CGs, the UE can transmit different CG PUSCHs as follows:

[0206] In such a CG configuration, multiple TBs for an I frame may be transmitted on CG PUSCHs for multiple CGs. For example, as shown in Figure 8, logical channel data for an I frame may be transmitted in two TBs, with PUSCH 1 for CG1 and PUSCH 2 for CG2.

[0207] Method 1-1: The UE can determine that the CG2 resource is valid only when there is a CG1 transmission. In other words, when two linked CG configurations are configured for the UE, when a CG PUSCH transmission for one CG configuration is made (or an ACK for the same is received), the CG PUSCH resource for the other CG configuration may be valid. Here, an invalid CG PUSCH resource may mean that the CG PUSCH resource is not allocated.

[0208] That is, assuming that CG2 is assigned PUSCH resources by CG1, the UE can determine CG PUSCH transmission for CG2 when it determines that CG1 PUSCH transmission will occur (i.e., will occur) or when it receives HARQ-ACK information (e.g., ACK) for CG PUSCH transmission for CG1.

[0209] Method 1-2: The UE can activate CG2 only when there is a CG1 transmission. In other words, when two linked CG configurations are configured for a UE, the other CG configuration may be activated when a CG PUSCH transmission for one CG configuration is made (or when an ACK for the same is received).

[0210] For example, if the base station instructs activation of CG1 and CG2 in one DCI, the UE can activate CG1 first, and then activate CG2 and transmit the CG2 PUSCH when there is a TB to transmit on the CG1 PUSCH (or when HARQ-ACK information (e.g., ACK) for the CG1 PUSCH is received).

[0211] Here, if there is no TB to transmit on the CG1 PUSCH in the resource allocated for CG1 PUSCH transmission, or if it is determined that there is no data to transmit on the CG1 PUSCH for a certain period of time, or if CG1 PUSCH transmission fails or a NACK is received, the UE can determine that CG2 is deactivated (or can deactivate an activated CG2).

[0212] If necessary, even if the base station has already instructed activation of CG1 and CG2 by the first DCI, the base station can instruct activation / release of CG2 by a separate second DCI. If two DCIs (the first DCI and the second DCI) activate the same CG2, the UE can reactivate CG2 by the last received DCI (i.e., the second DCI) even if CG2 is already activated.

[0213] Method 1-3: The UE can determine whether to transmit a CG2 PUSCH based on the MAC PDU header or MAC CE content transmitted in the CG1 PUSCH. In other words, when two linked CG configurations are configured for a UE, the content of a CG PUSCH transmission for one CG configuration can determine whether to transmit a CG PUSCH for the other CG configuration. Here, determining whether to transmit a CG PUSCH can mean whether a CG PUSCH resource for the corresponding CG configuration is allocated (i.e., whether it is enabled) or whether the corresponding CG configuration is activated.

[0214] For example, the LCID field of the MAC PDU transmitted on the CG1 PUSCH or the MAC CE may indicate the start of a GOP pattern, indicate a logical channel corresponding to an I frame, or indicate the transmission or activation of a concatenated CG2. In this case, the UE may activate a deactivated CG2 and transmit the TB of the next frame (e.g., a P frame) on the activated CG2 PUSCH.

[0215] Example 2: When multiple CG configurations configured in a UE are linked / associated with each other, the CG PUSCH for each CG configuration may be transmitted and received as follows.

[0216] Here, multiple CG settings may be mapped to one or more different logical channels, or may be mapped to the same one or more logical channels, or may be mapped to some overlapping logical channels.

[0217] If CG1 (i.e., CG Configuration Index 1) is mapped to a logical channel for an I frame, CG2 (i.e., CG Configuration Index 2) is mapped to a logical channel for a P frame, and CG1 and CG2 are configured as concatenated / linked CGs, the UE can transmit different CGs as follows:

[0218] In such a CG configuration, multiple TBs for an I frame may be transmitted on multiple CG PUSCHs for CG 1. For example, as shown in FIG. 8, logical channel data for an I frame may be divided into two TBs and transmitted on different (consecutive) PUSCHs for CG 1.

[0219] Method 2-1: CG PUSCH resources may not be allocated to specific (one or more) CG periods of CG2. In other words, when two linked CG configurations are configured for a UE, CG PUSCH resources in one or more specific periods of a specific CG configuration may not be allocated (may be disabled).

[0220] For example, the UE may determine that a CG PUSCH resource allocated to a particular CG period(s) of CG2 that overlaps with a CG1 PUSCH transmission is invalid, and / or the base station may not allocate a CG PUSCH resource to a particular CG period(s) of CG2 that overlaps with a CG1 PUSCH transmission.

[0221] In this manner, a mask (i.e., a period during which CG PUSCH is not transmitted) may be set in units of CG periods to disable or not allocate CG PUSCH resources in specific M-th (or one or more) overlapping CG periods. As a result, the UE and the base station do not need to disable or not allocate CG PUSCH resources in the specific M-th (or one or more) CG periods for which the mask is set.

[0222] Method 2-2: CG2 transmission may be skipped in one or more CG2 periods that overlap with CG1. In other words, when two linked CG configurations are configured for a UE, CG PUSCH transmission may be skipped in one or more specific periods of a specific CG configuration that overlaps with another CG configuration. That is, CG PUSCH resources may be allocated in the one or more periods, but CG PUSCH transmission may be skipped.

[0223] The UE may skip PUSCH transmissions assigned to particular CG period(s) of CG2 that overlap with CG1 PUSCH transmissions.

[0224] In this manner, a mask may be configured for each CG period to skip a specific Mth (or one or more) overlapping CG periods, thereby allowing the UE and the base station to skip CG PUSCH transmission for the specific Mth (or one or more) CG periods for which the mask is configured.

[0225] Here, an ACK may be transmitted as HARQ-ACK information for the skipped CG PUSCH, or the response of the HARQ-ACK information for the skipped CG PUSCH may also be skipped.

[0226] Method 2-3: When a CG1 PUSCH transmission is performed in a specific CG1 period, or when a CG1 PUSCH is transmitted in a specific CG1 period, the CG2 PUSCH resource of the CG2 period that starts after the CG1 PUSCH transmission can be determined to be valid. This allows the UE to transmit the CG2 PUSCH using the valid CG2 PUSCH resource. In other words, when two concatenated / linked CG configurations are configured for a UE, when a CG PUSCH for one CG configuration is transmitted, a CG PUSCH for the other CG configuration may be transmitted within one or more periods that start after the CG PUSCH transmission.

[0227] Example 3: When multiple CG configurations configured in a UE are linked / interlocked with each other, a CG PUSCH transmission for one CG configuration may indicate a CG PUSCH transmission for the other CG configuration.

[0228] Here, multiple CG settings may be mapped to one or more different logical channels, or may be mapped to the same one or more logical channels, or may be mapped to some overlapping logical channels.

[0229] When CG1 (i.e., CG Configuration Index 1) is mapped to a logical channel for an I frame, CG2 (i.e., CG Configuration Index 2) is mapped to a logical channel for a P frame, and CG1 and CG2 are configured as connected / associated CGs, the UE can activate all connected / associated CGs by DCI and instruct transmission of a CG1 PUSCH or a CG2 PUSCH with a period N (N is a natural number) by transmitting a CG1 PUSCH with a period N (N is a natural number).

[0230] In other words, when two concatenated / linked CG configurations are configured for a UE, CG PUSCH transmission within a particular period of a particular CG configuration may later indicate CG PUSCH transmission in one or more periods for that CG configuration and / or the remaining CG configurations.

[0231] For example, the UE may indicate the start of a GOP pattern in the sub-header or MAC CE of the CG1 PUSCH of period N, indicate a logical channel corresponding to an I frame, or indicate concatenated CG2 transmission or activation. The UE may transmit a CG2 PUSCH in the k-th period (k=1, 2, 3, ..., M) after transmitting the CG1 PUSCH. After transmitting the CG2 PUSCH M times according to the GOP pattern, the UE may not transmit a CG2 PUSCH until the next CG1 PUSCH transmission. According to the instruction, the base station may expect a CG2 PUSCH transmission in the k-th period (k=1, 2, 3, ..., M) after transmitting the CG1 PUSCH.

[0232] Here, the UE can transmit multiple CG2 PUSCHs following the k-th period. For example, if the UE expects uplink transmission of three P frames immediately after an I frame according to information instructed by a higher layer of the UE or information notified by the base station, the UE can transmit CG2 PUSCHs in the k-th, k+1-th, and k+2-th periods (k=1, 2, 3, ..., M) immediately after the CG1 PUSCH transmission.

[0233] In addition, the UE may receive information about the GOP pattern from the base station in an RRC message, MAC CE, or DCI for setting up or activating CG1 and CG2.

[0234] Example 4: Information regarding the start time of the CG PUSCH within the next CG period (i.e., the next CG PUSCH transmission period) (i.e., information related to the resource on which the CG PUSCH starts) may be adjusted / indicated by control information (e.g., DCI or MAC CE) from the base station.

[0235] The base station and the UE can periodically allocate CG PUSCH time resources. Here, the base station can adjust / indicate the initial resource of the CG PUSCH (i.e., in a PUSCH transmission generated by resource allocation in an active CG PDCCH) in slot units using control information (e.g., DCI or MAC CE). Alternatively, the base station can activate a deactivated CG or reactivate an activated CG using control information (e.g., DCI or MAC CE).

[0236] For example, the UE and the base station can periodically allocate the CG PUSCH time resource according to the following equation (7): Here, the base station uses control information (e.g., DCI or MAC CE) to determine the slot start time (slot start time ) can be adjusted / instructed on a slot-by-slot basis.

[0237]

number

[0238] In Equation 7, numberOfSlotsPerFrame represents the number of consecutive slots per frame, and numberOfSymbolsPerSlot represents the number of consecutive symbols per slot. Also, in Equation 7, N is an integer value corresponding to the Nth PUSCH transmission (i.e., TO). periodicity is the transmission period of the CG PUSCH, and may be set by configuredGrantConfig (see Table 6). SFN start time , slot start time and denote the SFN and slot of the first transmission (i.e., the first resource (TO)) of the PUSCH for which the CG is (re)initialized (i.e., in a PUSCH transmission that occurs due to resource allocation in an active PDCCH), respectively.

[0239] For example, when adjusting / indicating a time resource of a CG PUSCH (i.e., a resource where a CG PUSCH starts) using a MAC CE, the MAC CE may adjust / indicate a CG configuration index (e.g., CG-ConfigIndex) value of the CG to be adjusted / indicated and a newly applied slot start time (slot start time ) can be specified as an absolute slot value or as an offset value in slot units that will be changed in an existing slot.

[0240] The UE may apply information related to the resource where the CG PUSCH starts (e.g., the adjusted slot value) from the point where the next CG period starts after the UE has completed receiving the MAC CE or transmitted an ACK for the MAC CE. start time When this is specified, the adjusted slot will be used from the next CG period after the above point. start time may be applied.

[0241] As another example, when a DCI is used to adjust / indicate a time resource of a CG PUSCH (i.e., a resource where a CG PUSCH starts), the CRC of the DCI may be scrambled with the CS-RNTI or a new RNTI (i.e., a new RNTI defined for use in adjusting / indicating a CG PUSCH time resource). Here, the HARQ process ID of the DCI indicates a CG configuration index (e.g., CG-ConfigIndex) value of the corresponding CG, and a newly applied slot start time (slot start time ) can be specified as an absolute slot value or a slot-by-slot offset value that is to be changed in an existing slot.

[0242] The UE may apply information related to the resource on which the CG PUSCH starts (e.g., the adjusted slot value) from the point at which the next CG period starts after the UE has completed reception of the DCI, or the point at which it has transmitted HARQ-ACK information (e.g., ACK) for the DCI, or the point at which it has completed transmission of a PUSCH scheduled by the DCI, or the point at which it has transmitted HARQ-ACK information (e.g., ACK) for a PUSCH scheduled by the DCI. Here, the HARQ-ACK information (e.g., ACK) for the DCI or the HARQ-ACK information (e.g., ACK) for a PUSCH scheduled by the DCI may be transmitted on a PUCCH resource indicated by the DCI, or (if there is no indicated PUCCH resource), on a PUCCH resource closest after a certain time among the A / N PUCCH resources configured for the CG.

[0243] - When the resource (e.g., the start slot of the CG PUSCH) of a periodic CG PUSCH is adjusted / indicated by the above-described method, the CG period may not be changed in the next CG period, and only the start slot of the periodic CG PUSCH resource may be changed. Alternatively, the CG period may also be changed in slot units according to the change in the CG PUSCH resource. For example, the slot may be specified as information related to the resource where the CG PUSCH starts by control information (e.g., DCI or MAC CE). start time When a value is specified, the specified slot in the formula 7 is used. start time The value may be applied to determine the resource from which the CG PUSCH transmission begins.

[0244] - In addition, in the above formula 7, the slot start time (slot start time ) along with the symbol start time (symbol start time) may be added using control information (for example, DCI or MAC CE). As an example of information related to the resource where the CG PUSCH starts, a symbol start time (symbol start time) adjusted in symbol units may be added. start time ) or a symbol-unit offset value that is changed from the existing symbol. That is, in the above-mentioned method, control information (e.g., DCI or MAC CE) can be used as an example of information related to the resource where the CG PUSCH starts. start time Instead of symbol start time You can also specify slot start time together with symbol start time The UE receiving this may also indicate the resource from which the CG PUSCH starts (for example, the adjusted slot) from the next CG period, the next CG PUSCH resource, or the CG PUSCH resource of the next CG period. start time and / or symbol start time ) value can be applied.

[0245] For example, using control information (e.g., DCI or MAC CE), slot number is used as information related to the resource where the CG PUSCH starts. start time and / or symbol start time When a value is specified, the specified slot is calculated using the following formula 8. start time and / or symbol start time The value may be applied to determine the resource from which the CG PUSCH transmission begins.

[0246]

number

[0247] In Equation 8, numberOfSlotsPerFrame represents the number of consecutive slots per frame, and numberOfSymbolsPerSlot represents the number of consecutive symbols per slot. Also, in Equation 8, N is an integer value corresponding to the Nth PUSCH transmission (i.e., TO). periodicity is the transmission period of the CG PUSCH, and may be set by configuredGrantConfig (see Table 6). SFN start time , slot start time , symbol start time denote the SFN, slot, and symbol of the first transmission (i.e., the first resource (TO)) of the PUSCH for which the CG is (re)initialized (i.e., in a PUSCH transmission that occurs due to resource allocation in an active PDCCH), respectively.

[0248] In addition, the base station may determine a resource (e.g., slot start time) at which a CG PUSCH for a specific CG (e.g., a CG associated with a specific uplink transmission) starts according to a specific uplink transmission (e.g., PUSCH, PUCCH, uplink traffic, uplink control information (UCI), etc.) transmitted by the UE. start time ) and / or symbol start time (symbol start time ), activate linked inactive CGs, or reactivate linked active CGs.

[0249] For example, a UE supporting virtual reality (VR) can report pose information based on the motion of a user wearing the VR UE to a base station. For example, the VR UE can transmit pose information to the base station at a 4 ms cycle.

[0250] To this end, for example, the base station may configure / allocate a separate logical channel for transmitting pause information and configure it to be mapped / associated with a specific configured grant (CG) for pause. The specific CG may be configured / defined to transmit only data of the logical channel for pause uplink. Here, the PUSCH resource for the specific CG may also transmit piggybacked UCI (i.e., transmit both TB and UCI). For example, the UCI may indicate whether or not there is a change in pause information. For example, if there is a user pause change equal to or greater than a threshold compared to the previous 4 ms (i.e., detected by the UE), the UCI may indicate 1, and if there is not, the UCI may indicate 0. Alternatively, if there is a pause change compared to the previous 4 ms (i.e., detected by the UE), the UCI may indicate 1, and if there is no pause change, the UCI may indicate 0. Alternatively, when multiple threshold levels are defined / set, the largest pause change can be indicated as 11, a smaller pause change as 10, a smaller pause change as 01, and no pause change as 00. The bit values ​​indicated in the UCI described above are merely examples, and the present disclosure is not limited thereto.

[0251] On the other hand, the TB of the PUSCH for pause may include pause information of higher layers.

[0252] Furthermore, if there are no pause changes or if there are only a few pause changes below a threshold, the UE may skip all transmission of the pause CG PUSCH and piggybacked UCI. Here, a data unit for pause information without a pause change (e.g., a TB including the pause information) may also be discarded. For example, if there are no pause changes or if there are only a few pause changes below a threshold, a PDCP (Passet Data Convergence Protocol) entity providing a radio bearer for the pause information may discard a data unit for the pause information. As yet another example, if there are no pause changes or if there are only a few pause changes below a threshold, the UE may be configured to discard the data unit by expiring a PDCP discard timer for the pause information data unit in the PDCP entity.

[0253] Alternatively, if there are no pause changes or if there are only a few pause changes below a threshold, the UE can discard the TB containing only such pause information.

[0254] Alternatively, if there are no pause changes or if the pause changes are less than a threshold, the upper layer of the UE can discard such pause information or transmit it on a separate radio bearer and logical channel, where the PDCP entity for the separate radio bearer may be configured with a shorter PDCP discard timer than the PDCP entity for the previous PDCP entity.

[0255] As another example, the base station may configure / allocate a separate logical channel for transmitting pause information and configure it to be mapped / associated with a specific PUCCH resource and a specific scheduling request (SR) configuration. When pause information occurs for the logical channel, the pause information may trigger a buffer state request (BSR), and the BSR may be configured to trigger an SR. Here, for example, the BSR MAC CE may indicate that the UE has pause information to transmit, based on the value of a logical channel group field or another specific field. Alternatively, when pause information occurs for the logical channel, the BSR MAC CE may be configured to immediately trigger an SR without a BSR. When pause information for the logical channel is triggered, the UE may transmit UCI on the corresponding PUCCH resource.

[0256] Here, if there are no pause changes or if there are only a few pause changes below a threshold, the setting may be such that BSR or SR is not triggered. Alternatively, if there are no pause changes or if there are only a few pause changes below a threshold, the setting may be such that the pause information is discarded and BSR or SR is not triggered.

[0257] By transmitting UCI indicating or including the pause information, or PUCCH transmission, or CG PUSCH transmission, the base station and the UE determine the resource (e.g., slot start time) where the CG PUSCH of a specific CG (e.g., linked / associated CG) starts according to the pause information. start time ) and / or symbol start time (symbol start time For example, if the pause information indicates a jitter change or the UCI or PUCCH for the pause information requests a CG timing change, the base station and the UE may adjust the resource (e.g., slot start time) at which the CG PUSCH of the specific CG PUSCH for XR traffic linked / associated with the pause information starts.start time ) and / or symbol start time (symbol start time Alternatively, the base station may transmit a DCI indicating a CG configuration index (e.g., CG-ConfigIndex) for the CG for XR traffic, and activate a connected deactivated CG or reactivate a connected activated CG.

[0258] To this end, the base station can link the pause information with a specific CG configuration index (e.g., CG-ConfigIndex) or link the pause information with a specific SR configuration. The UE and the base station can link such a specific CG (e.g., a CG for transmitting pause information) or a specific SR configuration with a specific CG (e.g., a CG for transmitting XR traffic). Therefore, a CG-UCI or CG-PUSCH transmission for a specific CG linked with a pause, or a specific SR PUCCH transmission linked with a pause, is determined based on the resource (e.g., slot start time) where the CG PUSCH starts. start time ) and / or symbol start time (symbol start time ), the resource (e.g., slot start time (slot )) where the CG PUSCH starts in the next CG period of the specific CG PUSCH for the concatenated XR traffic. start time ) and / or symbol start time (symbol start time )) may be adjusted.

[0259] Alternatively, the UE may use RRC signaling (e.g., an RRC assistant information message) to determine the resource (e.g., slot start time) at which the CG PUSCH adjusted for the specific CG PUSCH for XR traffic starts. start time ) and / or symbol start time (symbol start time)) values ​​can be reported to the base station.

[0260] FIG. 9 illustrates a signaling procedure between a network and a UE for a configured grant PUSCH transmission / reception method according to one embodiment of the present disclosure.

[0261] FIG. 9 illustrates signaling between a network (e.g., TRP1, TRP2) and a UE for a method proposed in the present invention (e.g., Examples 1 to 4, or a combination of one or more of the proposed methods of Examples 1 to 4). Here, the UE / network is merely an example, and various devices may be substituted. FIG. 9 is provided for convenience of explanation only and does not limit the scope of the present disclosure. Also, some steps illustrated in FIG. 9 may be omitted depending on the situation and / or settings.

[0262] The signaling scheme described in FIG. 9 may be extended to signaling between multiple TRPs and multiple UEs. In the following description, a network may be a base station including multiple TRPs or a cell including multiple TRPs. As an example, an ideal / non-ideal backhaul may be configured between TRP1 and TRP2 constituting the network. Also, although the following description is based on multiple TRPs, it may be extended to transmission using multiple panels as well. In the present disclosure, the operation of a UE receiving a signal from TRP 1 / TRP 2 may also be interpreted / described (or may be an operation) as the operation of the UE receiving a signal from the network (via / using TRP 1 / 2), and the operation of a terminal transmitting a signal to TRP 1 / TRP 2 may also be interpreted / described (or may be an operation) as the operation of the UE transmitting a signal to the network (via / using TRP 1 / TRP 2), and the reverse interpretation / description is also possible.

[0263] A base station may collectively refer to an object that transmits and receives data to and from a UE. For example, the base station may be a concept including one or more Transmission Points (TPs) and one or more Transmission and Reception Points (TRPs). Furthermore, the TP and / or TRP may include a base station panel, a transmission and reception unit, etc. Furthermore, the term "TRP" may be used interchangeably with expressions such as a panel, an antenna array, a cell (e.g., a macro cell, a small cell, a pico cell, etc.), a transmission point (TP), a base station (gNB), etc. As described above, a TRP may be distinguished by information (e.g., an index, an ID) regarding a CORESET group (or a CORESET pool). For example, if one UE is configured to transmit and receive data to and from multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one UE. Such a configuration for a CORESET group (or a CORESET pool) may be performed by higher layer signaling (for example, RRC signaling, etc.).

[0264] The UE can receive configuration information from the network (S901).

[0265] The configuration information may include information related to network configuration (e.g., TRP configuration) / information related to M-TRP-based transmission and reception (e.g., resource allocation, etc.), etc. In this case, the configuration information may be transmitted by higher layer signaling (e.g., RRC signaling, MAC-CE, etc.).

[0266] The configuration information may include configuration information related to the CG configuration described in the above-mentioned proposed method (e.g., Examples 1 to 4, or a combination of one or more of the proposed methods in Examples 1 to 4). For example, one or more CG configurations may be configured in the UE, and the configuration information may include individual configuration information (e.g., configuredGrantConfig IE) for each of the one or more CG configurations. Here, the individual configuration information for each of the one or more CG configurations may include the information / parameters exemplified above in Table 6.

[0267] Also, for example, according to the above-described embodiment, the individual setting information for each CG setting may include information about the logical channel associated with that CG setting.

[0268] The UE may receive downlink control information from the network (S902).

[0269] As described above, CG Type 1 PUSCH transmission may be configured to operate semi-statically when receiving configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) without detecting a UL grant in DCI. In this case, step S902 may be omitted. In this case, the TCI state for one or more CG configurations configured in the UE may be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE) or may be configured / instructed by the MAC CE described above.

[0270] Furthermore, CG Type 2 PUSCH transmission may be semi-statically scheduled by a UL grant in a valid activation DCI after receiving configuration information for a CG configuration (e.g., configuredGrantConfig without an rrc-ConfiguredUplinkGrant). In this case, the DCI in step S902 may correspond to the valid activation DCI. In this case, the TCI state for one or more CG configurations configured in the UE may be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), configured / indicated by the MAC CE described above, or indicated by the valid activation DCI.

[0271] The UE transmits the configured grant (CG) PUSCH to the network (S903).

[0272] Here, the UE can transmit the CG PUSCH to the network based on the operations described in the above-mentioned proposed methods (for example, Examples 1 to 4, or a combination of one or more of the proposed methods in Examples 1 to 4).

[0273] For example, when multiple CG configurations configured in a UE are linked / interlocked with each other according to the first embodiment, the UE can determine that resources for other CG configurations are valid or that other CG configurations are activated only when there is a transmission for a specific CG configuration. Also, the UE can determine whether to transmit CG PUSCHs for other CGs via a CG PUSCH for a specific CG.

[0274] For example, when multiple CG configurations configured in a UE are linked / interlocked with each other according to the second embodiment, a CG PUSCH resource for CG2 may not be allocated in a CG PUSCH transmission cycle for a CG2 configuration that overlaps with a CG1 configuration, and the UE may skip CG PUSCH transmission. Also, only when a CG1 PUSCH transmission occurs, a CG PUSCH for the CG2 configuration may be transmitted in the next CG PUSCH transmission cycle.

[0275] Also, for example, according to the third embodiment, when multiple CG settings configured in a UE are connected / linked to each other, a CG PUSCH transmission for one of the CG settings may indicate a CG PUSCH transmission for the other CG setting.

[0276] Furthermore, for example, according to the fourth embodiment, information related to resources on which the next CG PUSCH transmission for one or more CG configurations will occur (or on which CG PUSCH transmission will resume (or start)) is transmitted and received by downlink control information (e.g., DCI or MAC CE) or uplink control information (UCI), so that the CG PUSCH transmission may not be performed before the resource determined by the information. Then, the CG PUSCH for the one or more CG configurations may be transmitted on (or from) the resource determined by the information related to the resource on which the CG PUSCH will resume.

[0277] In this case, although not shown in FIG. 9, the UE may transmit UCI to the network. Here, the UCI may include information related to a resource on which the next CG PUSCH transmission occurs (or a resource on which the CG PUSCH transmission resumes (or starts)) for one or more CG configurations. In addition, the information related to the resource on which the next CG PUSCH transmission occurs may be indicated in slot or symbol units. For example, the information related to the resource on which the next CG PUSCH transmission occurs may indicate a slot or symbol of the resource on which the next CG PUSCH transmission occurs, or an offset value from the slot or symbol of the resource on which the next CG PUSCH transmission occurs.

[0278] Furthermore, the UCI may be transmitted on a CG PUSCH for a specific CG configuration associated with the transmission of the UCI. Here, the CG PUSCH for the specific CG configuration may include only data for a specific logical channel mapped to the specific CG configuration, and the UCI may be piggybacked on the CG PUSCH for the specific CG configuration. Alternatively, the UCI may be transmitted on a PUCCH based on an SR associated with the UCI.

[0279] In this way, when the UCI includes information related to a resource on which the next CG PUSCH transmission for the one or more CG configurations will occur, the CG PUSCH transmission may not be performed before the resource determined by the information related to the resource on which the next CG PUSCH transmission will occur. The CG PUSCH for the one or more CG configurations may be transmitted on (or from) the resource determined by the information related to the resource on which the next CG PUSCH transmission will occur. Here, one or more CG configurations may be configured to be associated with the UCI, and the resource on which the next CG PUSCH transmission for the associated one or more CG configurations will occur may be determined based on the UCI.

[0280] FIG. 10 is a diagram illustrating an example of a UE operation for a configured grant PUSCH transmission / reception method according to one embodiment of the present disclosure.

[0281] Referring to FIG. 10, FIG. 10 illustrates an example of a UE operation based on the previously proposed method (e.g., Examples 1 to 4, or a combination of one or more of the proposed methods in Examples 1 to 4). The illustration in FIG. 10 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 10 may be omitted depending on the situation and / or setting. Also, the UE in FIG. 10 is merely an example and may be embodied by the device illustrated in FIG. 12. For example, the processor 102 / 202 in FIG. 12 may control the transceiver 106 / 206 to transmit and receive channels / signals / data / information, etc., and may also control the memory 104 / 204 to store the transmitted or received channels / signals / data / information, etc.

[0282] 10 may be processed by one or more processors 102, 202 of FIG. 12, and the operations of FIG. 10 may be stored in a memory (e.g., one or more memories 104, 204 of FIG. 12) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 102, 202) of FIG. 12.

[0283] The UE receives individual configuration information related to one or more configured grant (CG) configurations from the base station (S1001).

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

[0285] Also, for example, according to the above-described embodiment, the individual setting information for each CG setting may include information about the logical channel associated with that CG setting.

[0286] The UE can receive downlink control information from the base station (S1002).

[0287] As described above, CG Type 1 PUSCH transmission may be configured to operate semi-statically when receiving configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) without detecting a UL grant in DCI. In this case, step S1002 may be omitted. In this case, the TCI state for one or more CG configurations configured in the UE may be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE) or may be configured / instructed by the MAC CE described above.

[0288] Furthermore, CG Type 2 PUSCH transmission may be semi-statically scheduled by a UL grant in a valid activation DCI after receiving configuration information for a CG configuration (e.g., configuredGrantConfig without an rrc-ConfiguredUplinkGrant). In this case, the DCI in step S1002 may correspond to the valid activation DCI. In this case, the TCI state for one or more CG configurations configured in the UE may be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE), configured / indicated by the MAC CE described above, or indicated by the valid activation DCI.

[0289] The UE transmits uplink control information (UCI) to the base station (S1003).

[0290] Here, the UCI may include information related to a resource on which the next CG PUSCH transmission occurs (or on which the CG PUSCH transmission is resumed (or started)) for one or more CG configurations. Furthermore, the information related to the resource on which the next CG PUSCH transmission occurs may be indicated in slot or symbol units. For example, the information related to the resource on which the next CG PUSCH transmission occurs may indicate a slot or symbol of the resource on which the next CG PUSCH transmission occurs, or may indicate an offset value from the slot or symbol of the resource on which the next CG PUSCH transmission occurs.

[0291] Furthermore, the UCI may be transmitted on a CG PUSCH for a specific CG configuration associated with the transmission of the UCI. Here, the CG PUSCH for the specific CG configuration may include only data for a specific logical channel mapped to the specific CG configuration, and the UCI may be piggybacked on the CG PUSCH for the specific CG configuration. Alternatively, the UCI may be transmitted on a PUCCH based on an SR associated with the UCI.

[0292] The UE transmits the configured grant (CG) PUSCH to the base station (S1004).

[0293] As described above, when the UCI includes information related to a resource on which the next CG PUSCH transmission for the one or more CG configurations will occur, the UE does not need to transmit the CG PUSCH to the base station before the resource determined by the information related to the resource on which the next CG PUSCH transmission will occur. Then, the UE can transmit the CG PUSCH for the one or more CG configurations to the base station on (or from) the resource determined by the information related to the resource on which the next CG PUSCH transmission will occur. Here, one or more CG configurations may be configured to be associated with the UCI, and the resource on which the next CG PUSCH transmission for the associated one or more CG configurations will occur may be determined based on the UCI.

[0294] FIG. 11 is a diagram illustrating an operation of a base station for a configured grant PUSCH transmission / reception method according to one embodiment of the present disclosure.

[0295] Referring to FIG. 11, FIG. 11 illustrates an example of the operation of a base station based on the previously proposed methods (e.g., Examples 1 to 4, or a combination of one or more of the proposed methods in Examples 1 to 4). The illustration in FIG. 11 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 11 may be omitted depending on the situation and / or setting. Also, the base station in FIG. 11 is merely an example and may be embodied by the device illustrated in FIG. 12. For example, the processor 102 / 202 in FIG. 12 may control the transceiver 106 / 206 to transmit and receive channels / signals / data / information, etc., and may also control the memory 104 / 204 to store the transmitted or received channels / signals / data / information, etc.

[0296] 11 may be processed by one or more processors 102, 202 of FIG. 12, and the operations of FIG. 11 may be stored in a memory (e.g., one or more memories 104, 204 of FIG. 12) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 102, 202) of FIG. 12.

[0297] The base station transmits individual configuration information related to one or more configured grant (CG) configurations to the UE (S1101).

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

[0299] Also, for example, according to the above-described embodiment, the individual setting information for each CG setting may include information about the logical channel associated with that CG setting.

[0300] The base station may transmit downlink control information to the UE (S1102).

[0301] As described above, CG Type 1 PUSCH transmission may be configured to operate semi-statically when receiving configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) without detecting a UL grant in DCI. In this case, step S1102 may be omitted. In this case, the TCI state for one or more CG configurations configured in the UE may be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE) or may be configured / instructed by the MAC CE described above.

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

[0303] The base station receives uplink control information (UCI) from the UE (S1103).

[0304] Here, the UCI may include information related to a resource on which the next CG PUSCH transmission occurs (or on which the CG PUSCH transmission is resumed (or started)) for one or more CG configurations. Furthermore, the information related to the resource on which the next CG PUSCH transmission occurs may be indicated in slot or symbol units. For example, the information related to the resource on which the next CG PUSCH transmission occurs may indicate a slot or symbol of the resource on which the next CG PUSCH transmission occurs, or may indicate an offset value from the slot or symbol of the resource on which the next CG PUSCH transmission occurs.

[0305] Furthermore, the UCI may be transmitted on a CG PUSCH for a specific CG configuration associated with the transmission of the UCI. Here, the CG PUSCH for the specific CG configuration may include only data for a specific logical channel mapped to the specific CG configuration, and the UCI may be piggybacked on the CG PUSCH for the specific CG configuration. Alternatively, the UCI may be transmitted on a PUCCH based on an SR associated with the UCI.

[0306] The base station receives the configured grant (CG) PUSCH from the UE (S1104).

[0307] As described above, when the UCI includes information related to a resource on which the next CG PUSCH transmission for the one or more CG configurations will occur, the base station may not receive the CG PUSCH transmission from the UE before the resource determined according to the information related to the resource on which the next CG PUSCH transmission will occur. The base station may then receive the CG PUSCH for the one or more CG configurations from the UE on (or from) the resource determined according to the information related to the resource on which the next CG PUSCH transmission will occur. Here, one or more CG configurations may be configured to be associated with the UCI, and the resource on which the next CG PUSCH transmission for the associated one or more CG configurations will occur may be determined based on the UCI.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A step in which a user equipment (UE) receives configuration information related to a configured grant (CG) configuration from a base station; and transmitting a CG PUSCH for the CG configuration to the base station in one or more CG PUSCH TOs among the plurality of CG PUSCH TOs based on uplink control information (UCI) in a plurality of CG PUSCH (physical uplink shared channel) transmission occasions (TOs) for the CG configuration; The UCI indicates whether the CG PUSCH is transmitted in each of the plurality of CG PUSCH TOs by using one bit corresponding to each of the plurality of CG PUSCH TOs.

2. The method of claim 1 , wherein the UCI indicates a CG PUSCH TO at which transmission of the CG PUSCH begins, or indicates an offset value from a CG PUSCH TO at which transmission of the CG PUSCH begins.

3. The method of claim 1 , wherein the UCI is multiplexed and transmitted with the CG PUSCH for the CG configuration associated with transmission of the UCI.

4. The method of claim 3 , wherein the CG PUSCH includes only data for a specific logical channel mapped to the CG configuration.

5. A UE (user equipment), at least one transceiver for transmitting and receiving radio signals; at least one processor for controlling the at least one transceiver; The at least one processor Receives configuration information related to a configured grant (CG) setting from a base station; The UE is configured to transmit a CG PUSCH for the CG configuration to the base station in one or more CG PUSCH TOs among the plurality of CG PUSCH TOs, based on uplink control information (UCI) in a plurality of CG PUSCH (physical uplink shared channel) TOs (transmission occasions) for the CG configuration; The UCI indicates whether the CG PUSCH is transmitted in each of the plurality of CG PUSCH TOs by using one bit corresponding to each of the plurality of CG PUSCH TOs.

6. At least one non-transitory computer-readable storage medium storing at least one instruction, The at least one instruction executable by at least one processor: Receives configuration information related to a configured grant (CG) setting from a base station; Control a user equipment (UE) to transmit a CG PUSCH for the CG configuration to the base station in one or more CG PUSCH TOs among the plurality of CG PUSCH TOs based on uplink control information (UCI) in a plurality of CG PUSCH (physical uplink shared channel) TOs (transmission occasions) for the CG configuration; The UCI indicates whether the CG PUSCH is transmitted in each of the plurality of CG PUSCH TOs by using one bit corresponding to each of the plurality of CG PUSCH TOs.

7. 1. A processing device configured to control user equipment (UE) in a wireless communication system, comprising: at least one processor; at least one computer memory operably coupled to the at least one processor and configured to store instructions; The instructions, upon execution by the at least one processor, receiving configuration information related to a configured grant (CG) setting from a base station; transmit a CG PUSCH for the CG configuration to the base station in one or more CG PUSCH TOs among the plurality of CG PUSCH TOs based on uplink control information (UCI) in a plurality of CG PUSCH TOs (transmission occasions) for the CG configuration; The UCI indicates whether the CG PUSCH is transmitted in each of the plurality of CG PUSCH TOs by using one bit corresponding to each of the plurality of CG PUSCH TOs.

8. A base station transmits configuration information related to a configured grant (CG) configuration to a user equipment (UE); receiving, by the base station, a CG PUSCH for the CG configuration in one or more CG PUSCH TOs among the plurality of CG PUSCH TOs based on uplink control information (UCI) in a plurality of CG PUSCH transmission occasions (TOs) for the CG configuration from the UE; The UCI indicates whether the CG PUSCH is transmitted in each of the plurality of CG PUSCH TOs by using one bit corresponding to each of the plurality of CG PUSCH TOs.

9. at least one transceiver for transmitting and receiving radio signals; at least one processor for controlling the at least one transceiver; The at least one processor Sending configuration information related to a configured grant (CG) setting to a user equipment (UE); and receiving a CG PUSCH (physical uplink shared channel) for the CG configuration from the UE in one or more CG PUSCH TOs among the plurality of CG PUSCH TOs based on uplink control information (UCI) in a plurality of CG PUSCH TOs (transmission occasions) for the CG configuration; The UCI indicates whether the CG PUSCH is transmitted in each of the plurality of CG PUSCH TOs by using one bit corresponding to each of the plurality of CG PUSCH TOs.

Images