Method and apparatus for transmitting or receiving configuration grant PUSCH in wireless communication system

Abstract

A method and an apparatus for transmitting or receiving a configuration grant PUSCH in a wireless communication system are disclosed. A method according to one embodiment of the present disclosure may comprise the steps of: receiving individual configuration information related to one or more CG configurations from a base station; receiving, from the base station, control information including information on a specific interval and not performing transmission of a CG PUSCH in a CG PUSCH resource configured for one or more CGs included in the specific interval; and transmitting the CG PUSCH in a CG PUSCH resource configured for the one or more CGs not included in the specific interval.

Description

Technical Field

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

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

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

[0004] Technical issues

[0005] The technical objective of the present disclosure is to provide a method and device for sending and receiving CG PUSCH configured for CG.

[0006] In addition, an additional technical object of the present disclosure is to provide a method and apparatus for transmitting and receiving a CG PUSCH while considering a discontinuous reception (DRX) operation of a base station or a UE.

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

[0008] Technical Solution

[0009] According to one aspect of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system may include the following steps: receiving corresponding configuration information related to one or more configuration grant (CG) configurations from a base station; receiving control information from the base station, wherein the control information includes information about a specific duration and does not perform transmission of a CG PUSCH on CG PUSCH (physical uplink shared channel) resources for one or more CG configurations included in the specific duration; and sending the CG PUSCH on CG PUSCH resources for the one or more CG configurations not included in the specific duration.

[0010] According to additional aspects of the present disclosure, a method performed by a base station in a wireless communication system may include the following steps: sending corresponding configuration information related to one or more configuration grant (CG) configurations to a user equipment (UE); sending control information to the UE, wherein the control information includes information about a specific duration and does not receive transmission of a CG PUSCH on CG PUSCH (physical uplink shared channel) resources for one or more CG configurations included in the specific duration; and receiving the CG PUSCH on CG PUSCH resources for the one or more CG configurations not included in the specific duration.

[0011] Technical Effects

[0012] According to an embodiment of the present disclosure, unnecessary power waste can be reduced by determining whether to send CGPUSCH according to the DRX operation of the UE or the base station.

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

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

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

[0016] Figure 1 The structure of a wireless communication system to which the present disclosure can be applied is illustrated.

[0017] Figure 2 The frame structure in a wireless communication system to which the present disclosure can be applied is illustrated.

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

[0019] Figure 4 The physical resource blocks in a wireless communication system to which the present disclosure can be applied are illustrated.

[0020] Figure 5 The time slot structure in a wireless communication system to which the present disclosure can be applied is illustrated.

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

[0022] Figure 7 is a diagram illustrating a DRX cycle in a wireless communication system to which the present disclosure can be applied.

[0023] Figure 8 The structure / mode of a group of pictures is illustrated.

[0024] Fig. 9 A plurality of configuration permission configurations according to one embodiment of the present disclosure are illustrated.

[0025] Fig.10 A single configuration licensing configuration according to one embodiment of the present disclosure is illustrated.

[0026] Fig.11 A signaling procedure for a method for transmitting and receiving a configuration grant PUSCH between a network and a UE according to one embodiment of the present disclosure is illustrated.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0040] For 3GPP LTE, reference may be made to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (Overall Description), and TS 36.331 (Radio Resource Control).

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

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

[0043] -BM: Beam Management

[0044] -CQI: Channel Quality Indicator

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

[0046] -CSI: Channel State Information

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

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

[0049] -DMRS: Demodulation Reference Signal

[0050] -FDM: Frequency Division Multiplexing

[0051] -FFT: Fast Fourier Transform

[0052] -IFDMA: Interleaved Frequency Division Multiple Access

[0053] -IFFT: Inverse Fast Fourier Transform

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

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

[0056] -MAC: Media Access Control

[0057] -NZP: Non-Zero Power

[0058] -OFDM: Orthogonal Frequency Division Multiplexing

[0059] -PDCCH: Physical Downlink Control Channel

[0060] -PDSCH: Physical Downlink Shared Channel

[0061] -PMI: Precoding matrix indicator

[0062] -RE: Resource Element

[0063] -RI: Rank indicator

[0064] -RRC: Radio Resource Control

[0065] -RSSI: Received Signal Strength Indicator

[0066] -Rx: Receive

[0067] -QCL: Quasi-Co-located

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

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

[0070] -TDM: Time Division Multiplexing

[0071] -TRP: Transmit and Receive Point

[0072] -TRS: Tracking Reference Signal

[0073] -Tx: Send

[0074] -UE: User Equipment

[0075] -ZP: Zero Power

[0076] Overall system

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

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

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

[0080] Figure 1 The structure of a wireless communication system to which the present disclosure can be applied is illustrated.

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

[0082] Figure 2 The frame structure in a wireless communication system to which the present disclosure can be applied is illustrated.

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

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

[0085] [Table 1]

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

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

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

[0089] [Table 2]

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

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

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

[0093] [Table 3]

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

[0095] [Table 4]

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

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

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

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

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

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

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

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

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

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

[0106] [Formula 1]

[0107]

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

[0109] [Formula 2]

[0110]

[0111] is the common resource block where the BWP starts relative to common resource block 0.

[0112] Figure 4 The physical resource blocks in the wireless communication system to which the present disclosure can be applied are illustrated. Figure 5 The time slot structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0113] Reference Figure 4 and Figure 5 , a time slot includes multiple symbols in the time domain. For example, for a normal CP, 1 time slot includes 7 symbols, but for an extended CP, 1 time slot includes 6 symbols

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

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

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

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

[0118] 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. The information sent and received by the base station and the terminal includes data and various control information, and there are various physical channels according to the type / purpose of the information they send and receive.

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

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

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

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

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

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

[0125] [Table 5]

[0126]

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

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

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

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

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

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

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

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

[0135] Configuration permission for uplink

[0136] The configuration grant (CG) for PUSCH is divided into CG type 1 and CG type 2.

[0137] CG Type 1 is fully configured or released for resource allocation using RRC signaling. When CG Type 1 is configured, a resource set is allocated to the UE on which PUSCH can be periodically sent. PDCCH is requested only when retransmission is required. CG Type 1 PUSCH transmission is semi-statically configured to operate upon receiving the higher-layer parameter configuredGrantConfig including rrc-ConfiguredUplinkGrant without detecting UL grant in DCI. The UE can perform PUSCH transmission according to the configured CG Type 1 until additional RRC signaling is re-established for the UE.

[0138] CG Type 2 is partially configured with resource allocation using RRC signaling and activated / deactivated using PDCCH transmissions. Since PDCCH also provides time and frequency resource allocations, the resource allocations can change each time it is activated. After receiving the higher layer parameter configuredGrantConfig that does not include rrc-ConfiguredUplinkGrant, CG Type 2 PUSCH transmissions are semi-persistently scheduled by effectively activating the UL grant in the DCI.

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

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

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

[0142] [Table 6]

[0143]

[0144]

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

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

[0147] repK indicates the number of repetitions, that is, indicates the repetition level for each PUSCH transmission. repK can have one of the values ​​of {1, 2, 4, 8}. For CG type 1, if pusch-RepTypeIndicator in rrc-ConfiguredUplinkGrant indicates "pusch-RepTypeB", PUSCH repetition type B is applied, otherwise PUSCH repetition type A is applied. For CG type 2, the PUSCH repetition type is determined by the UL grant of the DCI. Depending on the configured PUSCH repetition type A or B, the UE repeatedly sends uplink TBs for the configured number of repetitions.

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

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

[0150] mcs-Table indicates the MCS table that the UE uses for PUSCH without transform precoding, and mcs-TableTransformPrecoder indicates the MCS table that the UE uses for PUSCH with transform precoding. transformPrecoder indicates whether transform precoding is enabled for PUSCH.

[0151] rrc-ConfiguredUplinkGrant is the configuration for CG type 1 transmission. If this field is not present, the UE uses the UL grant configured by DCI through CS-RNTI (i.e., CG type 2). timeDomainAllocation indicates the starting symbol and length of the PUSCH and the PUSCH mapping type. timeDomainOffset indicates the 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 indicated number before receiving the configuration grant configuration, and if this field is not present, the reference SFN is 0.

[0152] After configuring the uplink grant for CG type 1, the MAC entity considers that the Nth (N≥0) uplink grant appears in the symbol in turn according to the following formula 3. That is, when CG type 1 is used, the CG PUSCH can be sent at the transmission timing / opportunity that satisfies the following formula 3.

[0153] [Formula 3]

[0154] [(SFN×numberOfSlotsPerFrame×nnumberOfSymbolsPerSlot)

[0155] + (number of slots in a frame × numberOfSymbolsPerSlot) + number of symbols in a slot] =

[0156] (timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot

[0157] +timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)

[0158] modulo(1024×nnumberOfSlotsPerFrame×nnumberOfSymbolsPerSlot)

[0159] In addition, after configuring the uplink grant for CG type 2, the MAC entity considers that the Nth (N≥0) uplink grant appears in the symbol in turn according to the following formula 4. That is, when CG type 2 is used, the CG PUSCH can be sent at the transmission timing / opportunity that satisfies the following formula 4.

[0160] [Formula 4]

[0161] [(SFN×nnumberOfSlotsPerFrame×numberOfSymbolsPerSlot)

[0162] + (number of slots in a frame × numberOfSymbolsPerSlot) + number of symbols in a slot] =

[0163] [(SFN start time ×numberOfSlotsPerFrame×numberOfSymbolsPerSlot

[0164] +slot start time ×numberOfSymbolsPerSlot+symbol start time )+N×periodicity]

[0165] modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)

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

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

[0168] In addition, SFN starttime 、slot starttime and symbol starttime Represents the SFN, time slot and symbol, respectively, of the first transmission timing / opportunity of the PUSCH where the CG is (re)initialized (i.e., in the PUSCH transmission that occurs according to the resource allocation in the active PDCCH).

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

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

[0171] [Formula 5]

[0172] HARQ process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes

[0173] [Formula 6]

[0174] HARQ process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-ProcID-offset2

[0175] In Equation 5 and Equation 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 a HARQ process ID for a specific PUSCH transmission.

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

[0177] In addition, in Table 6, configuredGrantTimer indicates the initial value of the CG timer as a multiple of the period. That is, configuredGrantTimer defines the duration (period) that the UE waits for a retransmission request after sending an uplink packet. The CG timer works independently for each HARQ process.

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

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

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

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

[0182] Discontinuous Reception (DRX) Operation

[0183] A UE configured with DRX may not continuously receive DL signals to reduce power consumption. DRX may be performed in RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state.

[0184] Hereinafter, a DRX operation in the RRC_CONNECTED state is described.

[0185] In the RRC_CONNECTED state, DRX is used for discontinuous reception of PDCCH. For ease of description, DRX performed in the RRC_CONNECTED state is referred to as RRC_CONNECTED DRX.

[0186] Figure 7 is a diagram illustrating a DRX cycle in a wireless communication system to which the present disclosure can be applied.

[0187] Reference Figure 7, the DRX cycle includes the timing and on-duration for DRX. The DRX cycle defines the time interval of the periodically repeated on-duration. The on-duration indicates the time period during which the UE monitors and receives the PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the on-duration. If there is a successfully detected PDCCH during the PDCCH monitoring, the UE starts the inactivity timer and remains in the awake state. On the other hand, if there is no successfully detected PDCCH during the PDCCH monitoring, the UE enters the sleep state after the on-duration ends. Therefore, when DRX is configured, when the processes and / or methods described / proposed above are executed, PDCCH monitoring / reception can be performed discontinuously in the time domain.

[0188] Table 7 shows the DRX (RRC_CONNECTED state) related procedures of the UE.

[0189] [Table 7]

[0190]

[0191] Referring to Table 7, DRX-related configuration information is received via a high-level (e.g., RRC) signaling (e.g., DRX-Config), and whether DRX is turned on / off is controlled by a DRX command MAC CE of the MAC layer. When DRX is configured, Figure 7 As shown, the UE may perform PDCCH monitoring discontinuously.

[0192] Here, the configuration information for the MAC cell group (MAC-CellGroupConfig) includes the configuration information required to configure the MAC parameters for the cell group. MAC-CellGroupConfig may also include configuration information about DRX (e.g., DRX-Config). For example, the configuration information about DRX (e.g., DRX-Config) may include the following information defining DRX:

[0193] -drx-onDurationTimer: defines the duration in the DRX cycle time.

[0194] -drx-SlotOffset: defines the delay before the drx-onDurationTimer starts.

[0195] -drx-InactivityTimer: defines the duration after a PDCCH opportunity indicating a new UL, DL or SL for the MAC entity.

[0196] -drx-RetransmissionTimerDL: defines the maximum duration until a DL retransmission is received.

[0197] -drx-RetransmissionTimerUL: defines the maximum duration until a grant for UL retransmission is received.

[0198] -drx-LongCycleStartOffset: Indicates the long DRX cycle and also defines the subframes where the long DRX cycle and the short DRX cycle start.

[0199] -drx-ShortCycle (optional): defines a short DRX cycle.

[0200] -drx-ShortCycleTimer (optional): defines the period during which the UE should follow the short DRX cycle.

[0201] -drx-HARQ-RTT-TimerDL: defines the minimum period before a DL assignment for a HARQ retransmission expected by the MAC entity.

[0202] -drx-HARQ-RTT-TimerUL: defines the minimum period before a UL HARQ retransmission grant is expected by the MAC entity.

[0203] More specifically, regarding short DRX and long DRX operations, first, after receiving a PDCCH indicating initial UL or DL ​​data, a DRX inactivity timer (drx-InactivityTimer) is started / restarted, and the UE remains in an awake state until the DRX inactivity timer (drx-InactivityTimer) expires.

[0204] When the DRX inactivity timer (drx-InactivityTimer) expires, a short DRX cycle can be optionally performed. That is, the base station can configure the UE to use a short DRX cycle by including a short DRX parameter set (i.e., drx-ShortCycle, drx-ShortCycleTimer) in the DRX-Config. In other words, if the short DRX parameter set in the DRX-Config is not configured, the UE can use the long DRX cycle described below. During the period of the short DRX cycle, if [(SFN×10)+subframe number] modulo(drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle) is satisfied at the beginning of a specific subframe, the DRX active period starts after the DRX offset (drx-SlotOffset).

[0205] The UE maintains the DRX active state for a period defined by the DRX on duration timer (drx-onDurationTimer). If data transmission is initiated during the DRX active period, the DRX inactivity timer (drx-InactivityTimer) is restarted, and the above operations are performed thereafter.

[0206] The long DRX cycle starts when the short DRX cycle period (drx-ShortCycle×drx-ShortCycleTimer) ends. Alternatively, if the short DRX parameter set in DRX-Config is not configured, the long DRX cycle can be started when the DRX inactivity timer (drx-InactivityTimer) expires. During the long DRX cycle period, if [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset is satisfied at the beginning of a specific subframe, the DRX active period starts after the DRX offset (drx-SlotOffset).

[0207] In addition, if the UE becomes DRX inactive after sending uplink data on PUSCH, the UE needs to temporarily return to the DRX active state to check for a retransmission request from the base station. The DRX UL HARQ RTT (Round Trip Time) timer (drx-HARQ-RTT-TimerUL) specifies the timing of returning to the DRX active state relative to the end of the first repetition of PUSCH transmission (or the end of PUSCH transmission if PUSCH repetition is not configured). That is, when the DRX UL HARQ RTT (Round Trip Time) timer (drx-HARQ-RTT-TimerUL) expires, the UE transitions from the DRX inactive state to the DRX active state. The UE maintains the DRX active state for the period defined by the DRX UL retransmission timer (drx-RetransmissionTimerUL).

[0208] Similarly, if the UE is in the DRX inactive state after receiving downlink data on the PDSCH, and the UE sends a NACK (negative acknowledgement) for the data on the PUCCH, the UE needs to return to the DRX active state to receive a retransmission from the base station. In this case, after the UE sends the NACK on the PUCCH, the DRX DL HARQ RTT timer (drx-HARQ-RTT-TimerDL) is started. That is, when the DRX DL HARQ RTT timer (drx-HARQ-RTT-TimerDL) expires, the UE transitions from the DRX inactive state to the DRX active state. The UE maintains the DRX active state for a period defined by the DRX DL retransmission timer (drx-RetransmissionTimerDL).

[0209] In addition, the DRX Command MAC CE and the Long DRX Command MAC CE are used to immediately put the UE into the DRX Inactive state without waiting for the DRX Inactivity Timer (drx-InactivityTimer) to expire. The DRX Command MAC CE instructs the UE to enter the DRX Inactive state, and if short DRX is configured, the UE starts a short DRX cycle, and if short DRX is not configured, the UE starts a long DRX cycle. The Long DRX Command MAC CE instructs the UE to enter the DRX Inactive state and start a long DRX cycle.

[0210] Method for transmitting and receiving PUSCH using Configuration Grant (CG)

[0211] In the present disclosure, when using pre-configured resources (such as configuration grant (CG) of NR wireless communication system) to send video information of extended reality (XR) service, a method is proposed to reduce power consumption and improve the efficiency of wireless resources while ensuring the availability and reliability of transmission resources.

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

[0213] In addition, the types of data that can be generated in XR are diverse. Among these data, video data transmission, which is usually reported in a specific period, and sensor and location information of the UE are considered to be sent and received from CG resources. These data may not always have a fixed data generation time (service arrival time) and may have jitter due to reasons such as video encoding time, sensor measurement time, high-level operation, or routing changes of the transmitted network.

[0214] If resources are allocated far enough away from the expected service occurrence time while taking jitter into consideration, resource availability can be guaranteed, but delays may occur. On the other hand, if CG resources with a fixed period are allocated to the expected data occurrence time, a large delay may occur due to the delay until the next available resource when jitter occurs.

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

[0216] Since ensuring low latency is essential for XR service quality, a method needs to be considered to minimize the impact of latency while reducing the impact of jitter. In the present disclosure, in order to solve this problem, a method is discussed that selectively uses some of the multiple CG resources configured between the UE and the base station, and simplifies and sends the response to the used CG resources to a predetermined location.

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

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

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

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

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

[0222] Figure 8 The structure / mode of a group of pictures is illustrated.

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

[0224] The GOP structure is usually represented by two numbers, for example, M=3, N=12. The first number (M) indicates the distance between two anchor frames (I or P). The second number (N) is the GOP size, which indicates the distance between two complete images (I frames). For example, for M=3, N=12, the GOP structure is IBBPBBPBBPBBI. Instead of the M parameter, the maximum number of B frames between two consecutive anchor frames can also be used.

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

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

[0227] In the following disclosure, the proposed method is described based on the semi-statically configured uplink CG radio resource, but this is for ease of explanation, and the method proposed in the present disclosure is not limited to this. Therefore, it can 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 the UE. For example, a method for determining a HARQ-ACK timing for multiple downlink radio resources allocated to the UE can be applied independently of the PDSCH and SPS PDSCH indicated by the dynamic scheduling. In addition, when multiple wireless resources are not semi-statically configured but configured by dynamic instructions, for example, when multiple wireless resources are configured at once by DCI, the method proposed in the present disclosure can be applied. Therefore, even without a separate explanation, as long as the principle of the proposed method is not violated, the method proposed in the present disclosure can also be applied to all types of transmission and reception methods expected by the base station and the UE. ...

[0228] In addition, in the present disclosure, a transmission opportunity (TO) means a radio resource (e.g., CG PUSCH) configured for CG use. At the transmission opportunity, the object performing the transmission (i.e., the base station in the case of downlink and the UE in the case of uplink) can attempt to transmit in the TO, and the receiver (i.e., the UE in the case of downlink and the base station in the case of uplink) can expect to transmit in each TO and attempt to receive it.

[0229] In the following, in order to explain the principles of the proposed method, the present disclosure provides an example based on the NR system, but the proposed method does not specifically limit the transmission and reception forms of NR unless otherwise specified. In addition, in order to explain the principles of the proposed method, the present disclosure provides examples based on the characteristics and structure of the XR service, but unless otherwise specified, the proposed method does not specifically limit the support of the XR service. Therefore, even if not separately stated, the method proposed in the present disclosure can be applied to all wireless communication transmission and reception structures and services as long as it does not violate the principles of the proposed method.

[0230] Hereinafter, the present disclosure proposes a method in which it is possible to control CG transmission only during a specific time interval according to a GOP mode. Thus, the power consumption of the base station can be reduced by allowing CG PUSCH transmission only during a specified time interval, and CG resources can be efficiently operated according to the business mode.

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

[0232] The method that the present disclosure proposes can be applied by selecting some methods in the following methods. In addition, each method that the present disclosure proposes can operate independently without the need for separate combination, or can operate in a linked form by combining one or more methods. As long as the principle of the present invention is maintained, some terms, symbols and sequences that are used to describe the method that the present disclosure proposes can be replaced with other terms, symbols and sequences.

[0233] The following CG settings and activation / deactivation, sending / receiving operations, etc. can be supported in the present disclosure. That is, the following CG settings and activation / deactivation, sending / receiving operations, etc. can be incorporated into the method proposed in the present disclosure.

[0234] Fig. 9 A plurality of configuration permission configurations according to one embodiment of the present disclosure are illustrated.

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

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

[0237] i) If the DCI indicates CG1 and also indicates activation, the UE can activate CG2 simultaneously with CG1 or after a specific time period.

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

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

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

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

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

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

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

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

[0246] For example, refer to Fig. 9 Different logical channels may be configured / allocated for I frames and P frames. In addition, the logical channels for I frames may be mapped to the CG for CG PUSCH1, and the logical channels for P frames may be mapped to the CG for CG PUSCH 2.

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

[0248] -The UE may expect CG2 PUSCH transmission to occur only after CG1 PUSCH transmission. Therefore, the CG2 PUSCH transmission in the next time period may be determined based on whether CG1 PUSCH is sent.

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

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

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

[0252] -Base station / UE can perform transmission according to the traffic mode using one or some of the multiple CG radio resources within the period. Here, considering the occurrence time of user data of the base station / UE, the fastest radio resource capable of sending a transport block (TB) including user data can be selected.

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

[0254] Embodiment 1: For periodic CG PUSCH resources (i.e., TO) for activated CG, only some CG PUSCH resources may be used to send CG PUSCH transmission, or CG PUSCH transmission may be skipped on some CG PUSCH resources based on a window (i.e., available resources / duration) or a mask (i.e., unavailable resources / duration).

[0255] The window (or mask) may be configured / operated in a duration (or TO) when the UE is expected to have no UL traffic at all or in a duration (or TO) when the base station will reduce power consumption.

[0256] Method 1-1: The base station may configure a periodic or non-periodic CG window for one or more specific CGs (ie, specific CG configuration indexes (eg, ConfigIndex)). Thus, power consumption of the UE or the base station may be prevented.

[0257] In this case, when the corresponding CG is activated, the UE can determine that only the CG PUSCH resources within the configured CG window (included in the configured CG window) are valid and send the CG PUSCH, and can determine that the CG PUSCH resources outside the CG window (not included in the CG window) are invalid and may not send the CG PUSCH. The base station may also not receive CG PUSCH transmissions outside the CG window to reduce power consumption.

[0258] In addition, the UE can also ignore PUSCH resource allocation based on dynamic grant (DG) outside the CG window (for example, UL grant via DCI) based on the base station configuration. That is, even if the UE receives PUSCH resource allocation based on DG grant in a time period / resource other than the CG window, the UE may not send PUSCH.

[0259] Here, the CG window may be valid only within a specific time period. For example, the CG window may be valid only within a specific CG period. As another example, the CG window may be valid only within a specific time period starting immediately after the CG window configured / indicated by RRC / MAC CE / DCI or immediately after sending an ACK for the indication. Alternatively, the CG window may be configured to be continuously valid during the period when the CG is activated.

[0260] The configuration information for the CG window may be included and configured in the RRC message configuring the CG (eg, CG-config), or may be indicated to the UE via a MAC CE or DCI.

[0261] In addition, the CG window can be configured per CG configuration index (e.g., CG-ConfigIndex), per priority (i.e., priority for the CG), per cell, per UL BWP, or configured or indicated per UE. For example, the CG window can also be configured with a priority, and in this case, a CG window with a higher priority (HP) can be applied only to a CG with HP, and a CG window with a lower priority (LP) can be applied only to a CG with LP.

[0262] The configuration information for the CG window may consist of a CG window starting point (e.g., time slot number / index or TO number / index) and a length (i.e., duration) (e.g., number of time slots, number of TOs), and may be specified in units of time slots (or in units of TOs). In addition, in the case of a periodic CG window, the period of the CG window may also be additionally configured. In addition, even in the case of a periodic CG window, if it has the same periodicity as the CG period, the CG period may be applied without additionally setting the period of the CG window.

[0263] For example, the MAC CE may include the above-mentioned CG configuration index (e.g., CG-ConfigIndex) field and the CG window configuration information. Alternatively, the DCI for activating the CG with a CRC (cyclic redundancy check) scrambled by the CS (configuration scheduling)-RNTI or the DCI for CG retransmission may indicate the CG window start time and length (i.e., duration) (i.e., in this case, the identification of the CG configuration index may follow the conventional method).

[0264] If the UE receives new CG window configuration information after receiving and applying the CG window configuration information, the UE can release the existing CG window configuration information and apply the new CG window configuration information. In this case, since a separate signaling for releasing the CG window configuration is not used, the signaling overhead can be reduced.

[0265] The UE can be configured to start the CG window timer at the start time of the CG window and stop the CG window timer at the end time of the CG window. Therefore, when the CG window timer is running, the UE can determine that the CG PUSCH is valid. Here, the CG window timer and the CG timer (e.g., configuredGrantTimer, see Table 6) can be the same or different.

[0266] Method 1-2: The base station may configure a periodic or non-periodic CG mask for one or more specific CGs (ie, specific CG configuration indexes (eg, CG-ConfigIndex)). This may prevent power consumption of the UE or base station.

[0267] In this case, when the corresponding CG is activated, the UE can determine that only the CG PUSCH resources outside the configured CG mask (not included in the configured CG mask) are valid and send the CG PUSCH, and can determine that the CG PUSCH resources within the CG mask (included in the CG mask) are invalid and may not send the CG PUSCH. The base station may also not receive CG PUSCH transmission within the CG mask to reduce power consumption.

[0268] Here, the CG mask may be valid only within a specific time period. For example, the CG mask may be valid only within a specific CG period. As another example, the CG mask may be valid only within a specific time period starting immediately after the CG mask configured / indicated by the RRC / MAC CE / DCI or immediately after sending an ACK for the indication. Alternatively, the CG mask may be configured to be valid continuously within the period during which the CG is activated.

[0269] The configuration information for the CG mask may be included and configured in an RRC message (eg, CG-config) that configures the CG, or may be indicated to the UE via a MAC CE or DCI.

[0270] In addition, the CG mask can be configured per CG configuration index (e.g., CG-ConfigIndex), per priority (i.e., priority for the CG), per cell, per UL BWP, or configured or indicated per UE. For example, the CG mask can also be configured with a priority, in which case a CG mask as an HP can be applied only to a CG as an HP, and a CG mask as an LP can be applied only to a CG as an LP.

[0271] The configuration information for the CG mask may consist of a CG mask starting point (e.g., a time slot number / index or a TO number / index) and a length (i.e., duration) (e.g., number of time slots, number of TOs), and may be specified in units of time slots (or in units of TOs). In addition, in the case of a periodic CG window, the period of the CG window may also be additionally configured. In addition, even in the case of a periodic CG window, if it has the same periodicity as the CG period, the CG period may be applied without additionally setting the period of the CG window.

[0272] For example, the MAC CE may include the above-mentioned CG configuration index (e.g., CG-ConfigIndex) field and the CG mask configuration information. Alternatively, the DCI for activating the CG with a CRC (cyclic redundancy check) scrambled by the CS-RNTI or the DCI for CG retransmission may indicate the CG mask start time and length (i.e., duration) (i.e., in this case, the identification of the CG configuration index may follow the conventional method).

[0273] If the UE receives new CG mask configuration information after receiving and applying the CG mask configuration information, the UE can release the existing CG mask configuration information and apply the new CG mask configuration information. In this case, since a separate signaling for releasing the CG mask configuration is not used, the signaling overhead can be reduced.

[0274] The UE may be configured to start the CG mask timer at the start time of the CG mask and to stop the CG mask timer at the end time of the CG mask. Thus, when the CG mask timer is running, the UE may determine that the CG PUSCH is invalid. Here, the CG mask timer and the CG timer (e.g., configuredGrantTimer, see Table 6) may be the same or different.

[0275] Method 1-3: CG PUSCH transmission on specific CG PUSCH resources of one or more activated specific CGs (specific CG configuration index (eg, CG-ConfigIndex)) may be skipped via DCI or DL ​​MAC CE indication.

[0276] If the DCI indicates skipping of CG PUSCH transmission, the CRC of the DCI may be scrambled with the CS-RNTI or a separate RNTI. Here, if the DCI indicates a PUCCH resource, the UE receiving the DCI may use the indicated PUCCH resource to send a HARQ ACK for receiving the DCI (i.e., the PUCCH resource is determined based on the information indicated by the DCI).

[0277] The HARQ process ID indicated by the DCI can be mapped to the CG configuration index of the CG (e.g., CG-ConfigIndex).

[0278] In addition, DCI can indicate the activation of CG or the allocation of retransmission resources. In this case, when indicating the activation of CG or the allocation of retransmission resources, skipping for the corresponding CG can be indicated.

[0279] In addition, the DCI may indicate a skip duration (e.g., a duration or number of TOs). Here, for example, the skip duration may indicate skipping the transmission of one or more CG PUSCHs allocated immediately after receiving the DCI or immediately after sending an ACK for the DCI. As another example, the skip duration may indicate the number of CG periods that start immediately after receiving the DCI or immediately after sending an ACK for the DCI. In this way, if the DCI indicates a skip duration (i.e., if there is a field for indicating the skip duration), it can be considered that skipping is indicated, and if the DCI does not indicate a skip duration (i.e., if there is no field for indicating the skip duration), it can be considered that skipping is not indicated.

[0280] In addition, when the MAC CE indicates a CG transmission skip, the MAC CE may indicate a CG configuration index (e.g., CG-ConfigIndex) of the corresponding CG and a skip duration (e.g., a time interval or the number of TOs) of the corresponding CG.

[0281] Here, the skip duration may indicate skipping the transmission of one or more CG PUSCHs allocated immediately after receiving the MAC CE or immediately after sending the ACK for the MAC CE. Alternatively, the skip duration may indicate the number of CG cycles starting immediately after receiving the MAC CE or immediately after sending the ACK for the MAC CE. In this way, if the MAC CE indicates the skip duration (i.e., if there is a field for indicating the skip duration), it can be considered that skipping is indicated, and if the skip duration is not indicated (i.e., if there is no field for indicating the skip duration), it can be considered that skipping is not indicated.

[0282] Method 1-4: Based on a specific uplink transmission sent by the UE (e.g., PUSCH, PUCCH, uplink service, uplink control information (UCI), etc.), a CG PUSCH transmission for a specific CG (e.g., associated / linked with a specific uplink transmission (for XR service)) can be resumed or skipped. For example, based on a PUCCH transmission or UCI transmission indicating or including pose information of a user of the UE, or a CG PUSCH transmission for pose, the base station and the UE can resume or skip CG PUSCH transmission of one or more specific CGs associated with the pose information (e.g., CG for XR service).

[0283] For example, a UE supporting virtual reality (VR) can report posture information to a base station based on the movement of a user wearing the VR UE. For example, the VR UE can send posture information to the base station at a period of 4 ms.

[0284] To this end, for example, the base station may configure / allocate a separate logical channel for sending posture information and map / link it to a specific configuration license. In addition, a specific configuration license may be configured / defined to send only uplink data for a logical channel for posture. Here, the CG PUSCH resource for posture may send the UCI carried together (i.e., TB and UCI are sent together), for example, such UCI may indicate whether the posture information has changed. For example, if the posture change of the user is greater than a threshold (i.e., detected by the UE) compared to 4ms ago, the UCI may be indicated as 1, otherwise it may be indicated as 0. Alternatively, if there is a posture change compared to 4ms ago (i.e., detected by the UE), the UCI may indicate 1, and if there is no posture change, it may indicate 0. Alternatively, if multiple step thresholds are defined / configured, the maximum posture change may be indicated as 11, a smaller posture change may be indicated as 10, an even smaller posture change may be indicated as 01, and if there is no posture change, it is 00. The bit value indicated in the above UCI is only an example, and the present disclosure is not limited to this.

[0285] In addition, the TB of the PUSCH for attitude may include attitude information of higher layers.

[0286] In addition, if there is no posture change or if there is a posture change but it is less than or equal to a threshold, the UE can skip the transmission of both the CG PUSCH for the posture and the UCI carried thereon. Here, data units for posture information without a posture change (e.g., TBs including posture information) can also be discarded. For example, if there is no posture change, or if there is a posture change but it is less than or equal to a threshold, the PDCP (Packet Data Convergence Protocol) entity that provides a radio bearer for posture information can discard data units for posture information. As another example, if there is no posture change or if there is a posture change but it is less than or equal to a threshold, the UE can be configured to discard data units by expiring a PDCP discard timer for data units of posture information in the corresponding PDCP entity.

[0287] Alternatively, if there is no posture change or if there is a posture change but the amount is less than a threshold, the UE may discard the TB containing only such posture information.

[0288] Alternatively, if there is no attitude change or if there is an attitude change but the number is less than a threshold, the higher layers of the UE may discard such attitude information or send it to a separate radio bearer and logical channel. Here, the PDCP entity for the separate radio bearer may be configured with a PDCP discard timer that is shorter than the PDCP discard timer of the PDCP entity.

[0289] As another example, the base station may configure / allocate a separate logical channel for sending posture information and map / link it to a specific PUCCH resource and a specific scheduling request (SR) setting. Then, when posture information for a logical channel appears, the posture information may be configured to trigger a buffer status 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 posture information to be sent through the value of the logical channel group field or another specific field. Alternatively, when posture information for a logical channel appears, it may be configured to directly trigger an SR without the need for a BSR. When an SR for a posture is triggered, the UE may send UCI using the PUCCH resources for it.

[0290] Here, if there is no posture change or if there is a posture change but it is less than a threshold, it can be configured not to trigger BSR or SR. Alternatively, if there is no posture change or if there is a posture change but it is less than a threshold, it can be configured not to trigger BSR or SR by allowing the posture information to be discarded.

[0291] To this end, for example, the base station may link / associate the posture information with a specific CG configuration index (e.g., CG-ConfigIndex) (e.g., the first CG configuration), or link / associate the posture information with a specific SR configuration. The UE and the base station may link / associate a specific CG for a posture (e.g., the first CG configuration) or a specific SR configuration (for XR services) with a specific CG (e.g., the second CG configuration). After sending a UCI or CG PUSCH for a posture for a specific CG (e.g., the first CG configuration) or sending a specific SR PUCCH for a posture, the UE and the base station may start a CG window or CG mask immediately after (a specific time), or start a CG window timer or a CG mask timer.

[0292] Here, whether the CG window (or CG window timer) or the CG mask (or CG mask timer) starts can be determined based on information or values ​​(e.g., posture information) within the UCI.

[0293] For example, if UCI indicates a value other than 1 or 00, or if SR is transmitted, the CG window may start immediately from the time of posture information transmission or the time of UCI transmission or the time of SR transmission (at a specific time), or the CG window timer may start immediately from the time of posture information transmission or the time of UCI transmission or the time of SR transmission (at a specific time). Here, the UE may send a CG PUSCH (for XR services) during the CG window or while the CG window timer is running.

[0294] As another example, if 0 or 1 is indicated by UCI or if SR is sent, the CG mask may start immediately after the posture information transmission time or the UCI transmission time or the SR transmission time (at a specific time) or the CG mask timer may start immediately after the posture information transmission time or the UCI transmission time or the SR transmission time (at a specific time). Here, the UE may skip CG PUSCH transmission (for XR services) during CG masking or while the CG mask timer is running.

[0295] The specific time may be configured / indicated to the UE by the base station through an RRC message or MAC CE or DCI. Alternatively, the UE may specify the specific time by including it in the posture information and sending it to the base station. For example, the specific time may be configured as a round trip time (RTT) timer.

[0296] In addition, in the above-mentioned methods 1-1 to 1-4, the CG window or CG mask or CG skip duration may be configured / indicated as the number of CG periods or the number of CG PUSCH resources (i.e., the number of TOs) or the number of time slots with CG PUSCH resources. In addition, the CG window or CG mask or CG skip duration may be configured for one or more CG configuration indexes (e.g., CG-ConfigIndex). In addition, the CG window or CG mask or CG skip duration may be configured as a CG configuration index (e.g., CG-ConfigIndex) that is not applied to the CG for posture (i.e., the CG used to send posture information).

[0297] In addition, in the above methods 1-1 to 1-4, in the case of CG mask or CG skip duration, in addition to CGPUSCH transmission, the UE can also skip monitoring the retransmission DCI for the corresponding CG (i.e., the DCI for the retransmission indication of the CG PUSCH). To this end, the search space for the retransmission DCI can be separately specified / configured. For example, the retransmission DCI is monitored in the corresponding search space, but even in the corresponding search space, the retransmission DCI may not be monitored in the CG mask or skip duration.

[0298] Fig.10 A single configuration licensing configuration according to one embodiment of the present disclosure is illustrated.

[0299] In the following, reference will be made to Fig.10 An embodiment according to the present disclosure is described.

[0300] Implementation method 2: When a CG configuration is configured for a UE, a CG PUSCH for the corresponding CG configuration may be sent and received as follows.

[0301] Here, the logical channels mapped to one CG configuration can be mapped only to a specific CG period. In addition, the number of CG PUSCH opportunities (ie, TO) allocated per CG period can be allocated differently according to the logical channels to which they are mapped.

[0302] According to this embodiment, the UE may send a CG PUSCH at N (N is a natural number) CG PUSCH opportunities (i.e., TO) per CG period. For example, for a CG PUSCH belonging to (one or more) CG periods or CG windows that transmit data of a specific logical channel (hereinafter, the first logical channel) such as an I frame, the UE may allocate and send N (N is a natural number) CG PUSCH opportunities (i.e., TO) per CG period.

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

[0304] In addition, for (i) CG PUSCH that does not belong to (one or more) CG time periods or CG windows for sending first logical channel data, or (ii) CG PUSCH that belongs to a CG time period or CG window for sending other logical channel (i.e., second logical channel) data, the UE may send only k (k is a natural number) CG PUSCH opportunities per CG time period. Here, the base station may configure k to a value less than N. In the above case (i), if (one or more) CG time periods or CG windows are configured for the first logical channel, the configuration of (one or more) CG time periods or CG windows for the second logical channel may be unnecessary. On the other hand, in the above case (ii), even if (one or more) CG time periods or CG windows are configured for the first logical channel, the configuration of (one or more) CG time periods or CG windows for the second logical channel may be required, respectively.

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

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

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

[0308] Reference Fig.10 In the first CG period and the Nth CG period, the logical channels for the I frame can be mapped, and TB 1 and TB 2 for the I frame can be transmitted. In addition, in the remaining CG periods, the logical channels for the P frame can be mapped, and the TB for the P frame can be transmitted.

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

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

[0311] Reference Fig.10 , it can be explained that data for the logical channel mapped to the I frame is generated in the first CG period and the Nth CG period. Therefore, TB 1 and TB 2 for the I frame can be transmitted. In addition, it can be explained that data for the logical channel mapped to the I frame is not generated in the remaining CG periods. Therefore, TB for the P frame can be transmitted.

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

[0313] Here, the CG window may be configured separately for each logical channel, and different logical channels may be mapped only to different CG windows.

[0314] Reference Fig.10 , the first CG period and the Nth CG period can be interpreted as a case of configuring a CG window for an I frame, and the remaining CG periods can be interpreted as a case of configuring a CG window for a P frame. Therefore, only TB1 and TB2 of a logical channel for an I frame can be sent in the first CG period and the Nth CG period, and only TBs of a logical channel for a P frame can be sent in the remaining CG periods.

[0315] Implementation 3: DRX-based CG PUSCH transmission method

[0316] In the present disclosure, DRX activity time (or DRX activity (state)) may refer to the DRX activity time (or DRX activity (state)) of a base station or a UE. For example, the DRX activity time may be the cell DRX activity time of the base station or the UE-specific DRX activity time.

[0317] In other words, the CG window in implementation mode 1 may be included in the cell DRX active time of the base station, or may correspond to an example. In addition, the CG mask may be included in the cell DRX inactive time of the base station, or may correspond to an example.

[0318] The UE may send only the CG or DGPUSCH including the UL time slot corresponding to the DRX active time or the UE active time. Alternatively, the UE may determine only the CG or DGPUSCH including the UL time slot corresponding to the DRX active time or the UE active time as a valid PUSCH resource, and invalidate or skip other PUSCH resources. In other words, if either of the CG or DG PUSCH resources is a UL time slot corresponding to the DRX active time or the UE active time, the UE may send the CG or DG PUSCH (or determine that it is valid). On the other hand, if neither the CG or DG PUSCH resource is a UL time slot corresponding to the DRX active time or the UE active time, the UE may not send the CG or DG PUSCH (i.e., skip it) (or determine that it is invalid).

[0319] Alternatively, the UE transmits only on CG or DG PUSCH resources during DRX active time or UE active time. Alternatively, the UE may only regard the CG or DG PUSCH during DRX active time or UE active time as valid PUSCH resources, and invalidate or skip the CG or DG PUSCH outside the DRX active time or UE active time. In other words, if the CG or DG PUSCH resources are included in the DRX active time or UE active time, the UE may transmit the CG or DG PUSCH (or consider the CG or DG PUSCH valid). On the other hand, if the CG or DGPUSCH resources do not belong to the DRX active time or UE active time, the UE may not transmit (i.e., skip) the CG or DG PUSCH (or consider the CG or DG PUSCH invalid).

[0320] Here, a separate on-duration timer for the UL active time for CG PUSCH transmission may be periodically configured. Alternatively, the CG PUSCH may be transmitted only in the existing DRX active time period (see DRX operation and Figure 7 ). The above-mentioned DRX active time or separate on-duration time can be mapped only to one or more specific CG-ConfigIndex, or only to one or more specific service cells configured with CG, or to all CG configurations (i.e., all CG configurations configured in the UE).

[0321] For example, if the DRX active time or a separate on-duration is included in a specific CG PUSCH opportunity, or vice versa, if a specific CG PUSCH opportunity is included in the DRX active time or a separate on-duration, the UE may send the corresponding CG PUSCH. Otherwise, the UE may skip sending the corresponding CG PUSCH.

[0322] Here, if the UE sends a specific CG PUSCH, the UE may start or restart an inactivity timer for the DRX active time or the UL active time. The UE may then send an additional CG PUSCH while the inactivity timer is running. Thereafter, when the inactivity timer expires, a short DRX cycle or a long DRX cycle may start.

[0323] The first CG PUSCH opportunity of each CG period can be defined / configured to be included in the DRX active time or the UL active time. Therefore, if the UE has data (e.g., TB) to be sent from the logical channel mapped to the corresponding CG, the UE can always send the CG PUSCH at the first CG PUSCH opportunity of each CG period. Afterwards (if there is additional data to be sent from the logical channel mapped to the corresponding CG), the UE can start or restart the inactivity timer to send the additional data (e.g., TB) through the next CG PUSCH opportunity of the same CG period.

[0324] Here, if the PUSCH cannot be transmitted because it is not included in the active time, the UE can transmit an additional TB through the PUSCH included in the next active time. If uplink transmission (e.g., TB, etc.) cannot be performed as a CG or DG PUSCH opportunity because it is not included in the DRX active time or the UE active time, the UE can perform uplink transmission by shifting / changing the CG or DG PUSCH opportunity to the next DRX active time or the UE active time according to the base station configuration.

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

[0326] Fig.11 The signaling process between a user equipment (UE) and a network (e.g., TRP1, TRP2) based on the above-proposed method (e.g., Embodiment 1 to Embodiment 3, a combination of one or more of the proposed methods in Embodiment 1 to Embodiment 3) is illustrated. Here, UE / network is only an example and can be replaced by various devices. Fig.11 It is only for the convenience of explanation and does not limit the scope of the present disclosure. In addition, depending on the situation and / or setting, it can be omitted Fig.11 Some of the steps shown.

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

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

[0329] The UE may receive configuration information from the network (S1101).

[0330] The configuration information may include information related to the configuration of the network (e.g., TRP configuration) / information related to transmission and reception based on M-TRP (e.g., resource allocation, etc.). Here, the configuration information may be sent via high-layer signaling (e.g., RRC signaling, MAC-CE, etc.).

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

[0332] In addition, for example, according to the above-mentioned embodiment, the individual configuration information for each CG configuration may include information about the logical channel associated with the corresponding CG configuration.

[0333] The UE may receive downlink control information from the network (S1102).

[0334] As described above, CG type 1 PUSCH transmission can be configured to operate semi-statically without detecting the UL grant in the DCI upon receiving configuration information for the CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant). In this case, step S1102 can be omitted. In addition, in this case, the TCI stated for one or more CG configurations configured in the UE can be configured by configuration information related to the CG configuration (e.g., configuredGrantConfig IE) or configured / indicated by the above-mentioned MAC CE.

[0335] In addition, after receiving configuration information for CG configuration (e.g., configuredGrantConfig excluding rrc-ConfiguredUplinkGrant), CG type 2 PUSCH transmission can be semi-statically scheduled by effectively activating the UL grant in the DCI. In this case, the DCI of step S1102 may correspond to the valid activation DCI. In addition, 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 configured / indicated by the above-mentioned MAC CE or indicated by the valid activation DCI.

[0336] Here, according to Embodiment 1, the MAC CE or DCI (eg, valid activation DCI) may include information on a specific duration (eg, inactivity duration).

[0337] For example, the information about the specific duration may include the start time and length of the specific duration. Here, the start time and length may be indicated in units of CG PUSCH resources (or TO) or time slots.

[0338] In addition, the specific duration may be periodically configured or aperiodically configured. Here, if the specific duration is periodically configured, the information about the specific duration may also include periodic information.

[0339] The information about the specific duration may be valid / applicable only within a predetermined period. For example, it may be valid / applicable only within a predetermined time immediately after receiving the control information or immediately after sending an ACK (acknowledgement) for the control information.

[0340] In addition, the specific duration may be configured / indicated not to be included in the DRX active time according to embodiment 3 (eg, the cell DRX active time of the base station or the UE-specific DRX active time).

[0341] The UE sends a configured grant (CG) PUSCH to the network (S1103).

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

[0343] Here, for example, according to embodiment 1, if MAC CE or DCI (e.g., valid activation DCI) includes information about a specific duration (e.g., inactive duration), transmission of CG PUSCH may not be performed in CG PUSCH resources (or TO) configured for one or more CGs included in the specific duration. In addition, CG PUSCH may be transmitted in CG PUSCH resources (or TO) configured for one or more CGs not included in the specific duration.

[0344] Here, as described above, information for a specific duration may be valid / applicable only within a predetermined period. For example, it may be valid / applicable only within a predetermined time period immediately after receiving the control information or immediately after sending an ACK (acknowledgement) for the control information. That is, only during the period in which the information for a specific duration is valid / applicable, the transmission of the CG PUSCH may not be performed in the CG PUSCH resources (or TO) configured for one or more CGs within the specific duration. Moreover, in the period in which the information for a specific duration is invalid / inapplicable, the transmission of the CG PUSCH in the CG PUSCH resources (or TO) configured for one or more CGs may be performed regardless of the control information.

[0345] In addition, for example, according to embodiment 2, a specific logical channel may be mapped only to a specific (one or more) time period in a CG configuration, and a TB transmitted in a CG PUSCH may be determined based on the logical channel mapped based on the (one or more) CG time period. Alternatively, when multiple logical channels are mapped in a CG configuration, a TB transmitted in a CG PUSCH may be determined based on the priority of the logical channel. Alternatively, in a CG configuration, only a specific logical channel may be mapped within a specific CG window, and only a CG PUSCH for the corresponding logical channel may be transmitted.

[0346] Here, for example, according to embodiment 3, CG PUSCH may be transmitted only in CG PUSCH resources configured for one or more CGs and included in DRX active time (e.g., cell DRX active time of a base station or UE-specific DRX active time). On the other hand, transmission of CG PUSCH may not be performed in CGPUSCH resources configured for one or more CGs and not included in DRX active time.

[0347] Here, as described above, the specific duration may not be included in the DRX active time (e.g., the cell DRX active time of the base station or the UE-specific DRX active time). That is, in this case, the specific duration may be configured / indicated by the control information so that the transmission of the CG PUSCH can be guaranteed during the DRX active time.

[0348] According to the above-mentioned embodiment 1 or embodiment 3, the CG PUSCH resources (or TO) in which the CG PUSCH is not transmitted may have their positions changed (shifted) in the time domain, and the CG PUSCH may be transmitted in the changed CG PUSCH resources (or TO).

[0349] Fig.122 is a diagram illustrating an operation of a method of transmitting and receiving a configuration grant PUSCH of a UE according to an embodiment of the present disclosure.

[0350] Reference Fig.12 , Fig.12 The operation of the UE based on the above-proposed method (eg, Embodiments 1 to 3, or a combination of one or more of the methods proposed in Embodiments 1 to 3) is illustrated. Fig.12 The examples are only for convenience of explanation and do not limit the scope of the present disclosure. Fig.12 Some of the steps shown. In addition, Fig.12 The UE in is only an example and can be implemented as follows Fig.14 For example, Fig.14 The processor (102 / 202) can control the transceiver (106 / 206) to send and receive channels / signals / data / information, etc., and can also control Fig.14 The processor (102 / 202) stores the transmitted or received channel / signal / data / information etc. in the memory (104 / 204).

[0351] in addition, Fig.12 The operation can be done by Fig.14 One or more processors (102, 202) of the invention are used to process the Fig.12 The operation can be used to drive Fig.14 The instructions / programs (eg, instructions, executable codes) of at least one processor (eg, 102, 202) are stored in a memory (eg, Fig.14 in one or more memories (104, 204)).

[0352] The UE receives individual configuration information related to one or more configuration grant (CG) configurations from a base station (S1201).

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

[0354] In addition, for example, according to the above-mentioned embodiment, the individual configuration information for each CG configuration may include information about the logical channel associated with the corresponding CG configuration.

[0355] The UE receives control information from the base station (S1202).

[0356] As described above, CG type 1 PUSCH transmission can be configured to operate semi-statically when configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) is received without detecting UL grant in DCI. In this case, the control information of step S1202 can correspond to a MAC CE (e.g., a MAC CE that activates CG settings).

[0357] In addition, after receiving configuration information for CG configuration (e.g., configuredGrantConfig excluding rrc-ConfiguredUplinkGrant), CG type 2 PUSCH transmission can be semi-statically scheduled by effectively activating the UL grant in the DCI. In this case, the DCI of step S1202 can correspond to the effective activation DCI.

[0358] Here, according to Embodiment 1, the MAC CE or DCI (eg, valid activation DCI) may include information on a specific duration (eg, inactivity duration).

[0359] For example, the information about the specific duration may include the start time and length of the specific duration. Here, the start time and length may be indicated in units of CG PUSCH resources (or TO) or time slots.

[0360] In addition, the specific duration may be periodically configured or aperiodically configured. Here, if the specific duration is periodically configured, the information about the specific duration may also include periodic information.

[0361] The information about the specific duration may be valid / applicable only within a predetermined period. For example, it may be valid / applicable only within a predetermined time immediately after receiving the control information or immediately after sending an ACK (acknowledgement) for the control information.

[0362] In addition, the specific duration may be configured / indicated not to be included in the DRX active time according to embodiment 3 (eg, the cell DRX active time of the base station or the UE-specific DRX active time).

[0363] The UE sends a configured grant (CG) PUSCH to the base station (S1203).

[0364] Here, the UE may send a CG PUSCH to the base station based on the operations described in the above-mentioned proposed methods (eg, embodiments 1 to 3, or a combination of one or more of the proposed methods in embodiments 1 to 3).

[0365] Here, for example, according to embodiment 1, if MAC CE or DCI (e.g., valid activation DCI) includes information about a specific duration (e.g., inactive duration), transmission of CG PUSCH may not be performed in CG PUSCH resources (or TO) configured for one or more CGs included in the specific duration. In addition, CG PUSCH may be transmitted in CG PUSCH resources (or TO) configured for one or more CGs not included in the specific duration.

[0366] Here, as described above, information for a specific duration may be valid / applicable only within a predetermined period. For example, it may be valid / applicable only within a predetermined time period immediately after receiving the control information or immediately after sending an ACK (acknowledgement) for the control information. That is, only during the period in which the information for a specific duration is valid / applicable, the transmission of CG PUSCH may not be performed in the CG PUSCH resources (or TO) configured for one or more CGs within the specific duration. Moreover, in the period in which the information for a specific duration is invalid / inapplicable, the transmission of CG PUSCH may be performed in the CG PUSCH resources (or TO) configured for one or more CGs regardless of the control information.

[0367] In addition, for example, according to embodiment 3, CG PUSCH may be transmitted only in CG PUSCH resources configured for one or more CGs and included in DRX active time (e.g., cell DRX active time of a base station or UE-specific DRX active time). On the other hand, transmission of CG PUSCH may not be performed in CGPUSCH resources configured for one or more CGs and not included in DRX active time.

[0368] Here, as described above, the specific duration may not be included in the DRX active time (e.g., the cell DRX active time of the base station or the UE-specific DRX active time). That is, in this case, the specific duration may be configured / indicated by the control information so that the transmission of the CG PUSCH can be guaranteed during the DRX active time.

[0369] According to the above-mentioned embodiment 1 or embodiment 3, the CG PUSCH resources (or TO) in which the CG PUSCH is not transmitted may have their positions changed (shifted) in the time domain, and the CG PUSCH may be transmitted in the changed CG PUSCH resources (or TO).

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

[0371] Reference Fig.13 , Fig.13 The operation of the base station based on the above-proposed method (eg, Embodiments 1 to 3, or a combination of one or more of the methods proposed in Embodiments 1 to 3) is illustrated. Fig.13 The examples are only for convenience of explanation and do not limit the scope of the present disclosure. Depending on the situation and / or setting, the Fig.13 Some of the steps shown. In addition, Fig.13 The base station in is only an example and can be implemented as follows Fig.14 For example, Fig.14 The processor (102 / 202) can control the transceiver (106 / 206) to send and receive channels / signals / data / information, etc., and can also control Fig.14 The processor (102 / 202) stores the transmitted or received channel / signal / data / information etc. in the memory (104 / 204).

[0372] in addition, Fig.13 The operation can be done by Fig.14 One or more processors (102, 202) of the invention are used to process the Fig.13 The operation can be used to drive Fig.14 The instructions / programs (eg, instructions, executable codes) of at least one processor (eg, 102, 202) are stored in a memory (eg, Fig.14 in one or more memories (104, 204)).

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

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

[0375] In addition, for example, according to the above-mentioned embodiment, the individual configuration information for each CG configuration may include information about the logical channel associated with the corresponding CG configuration.

[0376] The base station sends control information to the UE (S1302).

[0377] As described above, CG type 1 PUSCH transmission can be configured to operate semi-statically when configuration information for CG configuration (e.g., configuredGrantConfig including rrc-ConfiguredUplinkGrant) is received without detecting UL grant in DCI. In this case, the control information of step S1302 can correspond to a MAC CE (e.g., a MAC CE that activates CG settings).

[0378] In addition, after receiving configuration information for CG configuration (e.g., configuredGrantConfig excluding rrc-ConfiguredUplinkGrant), CG type 2 PUSCH transmission can be semi-statically scheduled by effectively activating the UL grant in the DCI. In this case, the DCI of step S1302 can correspond to the effective activation DCI.

[0379] Here, according to Embodiment 1, the MAC CE or DCI (eg, valid activation DCI) may include information on a specific duration (eg, inactivity duration).

[0380] For example, the information about the specific duration may include the start time and length of the specific duration. Here, the start time and length may be indicated in units of CG PUSCH resources (or TO) or time slots.

[0381] In addition, the specific duration may be periodically configured or aperiodically configured. Here, if the specific duration is periodically configured, the information about the specific duration may also include periodic information.

[0382] The information about the specific duration may be valid / applicable only within a predetermined period. For example, it may be valid / applicable only within a predetermined time immediately after receiving the control information or immediately after sending an ACK (acknowledgement) for the control information.

[0383] In addition, the specific duration may be configured / indicated not to be included in the DRX active time according to embodiment 3 (eg, the cell DRX active time of the base station or the UE-specific DRX active time).

[0384] The base station receives a configuration grant (CG) PUSCH from the UE (S1303).

[0385] Here, the base station may receive the CG PUSCH from the UE based on the operations described in the above-mentioned proposed methods (eg, embodiments 1 to 3, or a combination of one or more of the proposed methods in embodiments 1 to 3).

[0386] Here, for example, according to embodiment 1, if MAC CE or DCI (e.g., valid activation DCI) includes information about a specific duration (e.g., inactive duration), transmission of CG PUSCH may not be performed in CG PUSCH resources (or TO) configured for one or more CGs included in the specific duration. In addition, CG PUSCH may be transmitted in CG PUSCH resources (or TO) configured for one or more CGs not included in the specific duration.

[0387] Here, as described above, information for a specific duration may be valid / applicable only within a predetermined period. For example, it may be valid / applicable only within a predetermined time period immediately after receiving the control information or immediately after sending an ACK (acknowledgement) for the control information. That is, only during the period in which the information for a specific duration is valid / applicable, the transmission of CG PUSCH may not be performed in the CG PUSCH resources (or TO) configured for one or more CGs within the specific duration. Moreover, in the period in which the information for a specific duration is invalid / inapplicable, the transmission of CG PUSCH may be performed in the CG PUSCH resources (or TO) configured for one or more CGs regardless of the control information.

[0388] In addition, for example, according to embodiment 3, CG PUSCH may be transmitted only in CG PUSCH resources configured for one or more CGs and included in DRX active time (e.g., cell DRX active time of a base station or UE-specific DRX active time). On the other hand, transmission of CG PUSCH may not be performed in CGPUSCH resources configured for one or more CGs and not included in DRX active time.

[0389] Here, as described above, the specific duration may not be included in the DRX active time (e.g., the cell DRX active time of the base station or the UE-specific DRX active time). That is, in this case, the specific duration may be configured / indicated by the control information so that the transmission of the CG PUSCH can be guaranteed during the DRX active time.

[0390] According to the above-mentioned embodiment 1 or embodiment 3, the CG PUSCH resources (or TO) in which the CG PUSCH is not transmitted may have their positions changed (shifted) in the time domain, and the CG PUSCH may be transmitted in the changed CG PUSCH resources (or TO).

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

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

[0393] Reference Fig.14 , the first wireless device 100 and the second wireless device 200 can send and receive wireless signals through various radio access technologies (e.g., LTE, NR).

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

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

[0396] In the following, the hardware elements of the wireless device 100, 200 will be described in more detail. Without limitation thereto, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors 102, 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed in the present disclosure to provide it to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow charts disclosed in the present disclosure, and obtain the PDU, SDU, message, control information, data, or information.

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

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

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

[0400] The above-mentioned embodiments are to combine the elements and features of the present disclosure in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be regarded as optional. Each element or feature can be implemented in a form that is not combined with other elements or features. In addition, the embodiments of the present disclosure may include a combination of some elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, the embodiments may include claims that do not have a clear reference relationship in the combined claims, or may be included as new claims by modification after application.

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

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

[0403] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include narrowband Internet of Things for low-power communication, as well as LTE, NR and 6G. Here, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, which may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2 and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may perform communication based on LTE-M technology. Here, for example, LTE-M technology may be an example of LPWAN technology and may be referred to as various names such as eMTC (enhanced machine type communication). For example, LTE-M technology may be implemented in at least any one of various standards, including 1) LTE CAT 0; 2) LTE Cat M1; 3) LTE Cat M2; 4) LTE non-BL (non-bandwidth limited); 5) LTE-MTC; 6) LTE machine type communication; and / or 7) LTE M, etc., and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100, 200 of the present disclosure may include at least any one of ZigBee, Bluetooth, and a low power wide area network (LPWAN) considering low power communication, and is not limited to the above names. For example, ZigBee technology can generate a PAN (Personal Area Network) related to small / low power digital communication based on various standards (e.g., IEEE 802.15.4, etc.), and can be called various names.

[0404] Industrial Applicability

[0405] The method proposed in the present disclosure is mainly described based on examples applied to 3GPP LTE / LTE-A and 5G systems, but can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising the following steps: receiving corresponding configuration information related to one or more configuration-permitted CG configurations from a base station; receiving control information from the base station, wherein the control information includes information about a specific duration, and not performing transmission of a CG PUSCH on a CG physical uplink shared channel (PUSCH) resource configured for one or more CGs included in the specific duration; and The CG PUSCH is sent on CG PUSCH resources configured for the one or more CGs that are not included in the specific duration.

2. The method according to claim 1, wherein: The information about the specific duration includes a start time and a length of the specific duration, and The start time and the length are indicated in units of CG PUSCH resources or time slots.

3. The method according to claim 1, wherein: The specific duration is configured periodically or aperiodically.

4. The method according to claim 1, wherein: The information about the specific duration is valid only within a predetermined time immediately after receiving the control information or immediately after sending an acknowledgment ACK for the control information.

5. The method according to claim 1, wherein: The control information is a medium access control MAC control element CE or downlink control information DCI.

6. The method according to claim 1, wherein: The specific duration is not included in the discontinuous reception DRX active time.

7. The method according to claim 6, wherein: The CG PUSCH is sent only in the CG PUSCH resources configured for the one or more CGs included in the DRX active time.

8. The method according to claim 6, wherein: The CG PUSCH is not sent in CG PUSCH resources configured for the one or more CGs that are not included in the DRX active time.

9. The method according to claim 1, wherein: The CG PUSCH resources in which the CG PUSCH is not transmitted are shifted in the time domain, and the CG PUSCH is transmitted in the shifted CG PUSCH resources.

10. The method according to claim 1, wherein: The specific duration is an inactivity duration.

11. A user equipment UE operating in a wireless communication system, the UE comprising: at least one transceiver, the at least one transceiver configured to send and receive wireless signals; as well as at least one processor configured to control the at least one transceiver, Wherein, the at least one processor is configured to: receiving corresponding configuration information related to one or more configuration-permitted CG configurations from a base station; receiving control information from the base station, wherein the control information includes information about a specific duration, and not performing transmission of a CG PUSCH on a CG physical uplink shared channel (PUSCH) resource configured for one or more CGs included in the specific duration; and The CG PUSCH is sent on CG PUSCH resources configured for the one or more CGs that are not included in the specific duration.

12. At least one non-transitory computer-readable medium storing at least one instruction, wherein: The at least one instruction executable by at least one processor controls a user equipment UE: receiving corresponding configuration information related to one or more configuration-permitted CG configurations from a base station; receiving control information from the base station, wherein the control information includes information about a specific duration, and not performing transmission of a CG PUSCH on a CG physical uplink shared channel (PUSCH) resource configured for one or more CGs included in the specific duration; and The CG PUSCH is sent on CG PUSCH resources configured for the one or more CGs that are not included in the specific duration.

13. A processing device, the processing device being configured to control a user equipment UE in a wireless communication system, the processing device comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and storing instructions that, upon execution by the at least one processor, perform operations comprising: receiving corresponding configuration information related to one or more configuration-permitted CG configurations from a base station; receiving control information from the base station, wherein the control information includes information about a specific duration, and not performing transmission of a CG PUSCH on a CG physical uplink shared channel (PUSCH) resource configured for one or more CGs included in the specific duration; and The CG PUSCH is sent on CG PUSCH resources configured for the one or more CGs that are not included in the specific duration.

14. A method performed by a base station in a wireless communication system, the method comprising the following steps: Sending corresponding configuration information related to one or more configuration permission CG configurations to the user equipment UE; sending control information to the UE, wherein the control information includes information about a specific duration, and not receiving transmission of a CG PUSCH on a CG physical uplink shared channel (PUSCH) resource configured for one or more CGs included in the specific duration; and The CG PUSCH is received on CG PUSCH resources configured for the one or more CGs that are not included in the specific duration.

15. A base station operating in a wireless communication system, the base station comprising: at least one transceiver, the at least one transceiver configured to send and receive wireless signals; as well as at least one processor configured to control the at least one transceiver, Wherein, the at least one processor is configured to: Sending corresponding configuration information related to one or more configuration permission CG configurations to the user equipment UE; sending control information to the UE, wherein the control information includes information about a specific duration, and not receiving transmission of a CG PUSCH on a CG physical uplink shared channel (PUSCH) resource configured for one or more CGs included in the specific duration; and The CG PUSCH is received on CG PUSCH resources configured for the one or more CGs that are not included in the specific duration.

Images