Method and apparatus for transmitting or receiving wireless signal in wireless communication system

Abstract

A method for transmitting a signal by a terminal in a wireless communication system according to at least one embodiment disclosed in the present specification may comprise the steps of: receiving a configuration grant (CG) configuration for uplink transmission; and transmitting a first physical uplink shared channel (PUSCH) including first uplink control information (UCI) at a first CG-PUSCH occasion among CG-PUSCH occasion related to the CG configuration, in which the first UCI includes information indicating whether the terminal does not transmit a second PUSCH at a second CG-PUSCH occasion located after the first CG-PUSCH occasion.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting / receiving a wireless signal. Background Art

[0002] Generally, wireless communication systems are evolving to cover wide areas differently to provide communication services such as audio communication services, data communication services, etc. Wireless communication is a multi-access system capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, the multi-access system may be any one of a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency division multiple access (SC-FDMA) system. Summary of the Invention

[0003] Technical Problem

[0004] An object of the present disclosure is to provide a method and apparatus for efficiently performing a wireless signal transmission / reception process.

[0005] Those skilled in the art will understand that the objects achievable by the present disclosure are not limited to those specifically described above, and the above and other objects achievable by the present disclosure will be more clearly understood from the following detailed description.

[0006] Technical Solution

[0007] In one aspect of the present disclosure, there is provided a method for a user equipment (UE) to transmit a signal in a wireless communication system. The method includes the steps of: receiving a configured grant (CG) configuration for uplink transmission; and transmitting a first physical uplink shared channel (PUSCH) including a first uplink control information (UCI) at a first CG-PUSCH occasion among CG-PUSCH occasions related to the CG configuration. The first UCI may include information indicating whether the UE will not transmit a second PUSCH at a second CG-PUSCH occasion after the first CG-PUSCH occasion.

[0008] The information indicating whether the UE will not transmit the second PUSCH may be a bitmap, and bits of the bitmap may be respectively associated with a predetermined number of CG-PUSCH occasions after the first CG-PUSCH occasion.

[0009] Each bit of the bitmap may be set to a first value indicating that PUSCH transmission is to be performed at the associated CG-PUSCH occasion or a second value indicating that PUSCH transmission is not to be performed at the associated CG-PUSCH occasion. The first value may be 0, and the second value may be 1.

[0010] Based on the first UCI indicating that the UE is to transmit a second PUSCH at a second CG-PUSCH occasion, the UE may transmit the second PUSCH at the second CG-PUSCH occasion.

[0011] The second PUSCH may include a second UCI, and the second UCI may include information indicating whether the UE is to transmit a third PUSCH at a third CG-PUSCH occasion located after the second CG-PUSCH occasion.

[0012] Based on the first UCI indicating that the UE is not to transmit a third PUSCH at a third CG-PUSCH occasion, the second UCI may further indicate that the UE is not to transmit a third PUSCH at the third CG-PUSCH occasion.

[0013] The UE may report, based on the CG configuration, whether to use subsequent CG-PUSCH occasions for respective CG-PUSCH transmissions.

[0014] The CG configuration may include configuration information indicating whether the UE is to report whether to use subsequent CG-PUSCH occasions for respective CG-PUSCH transmissions.

[0015] In another aspect of the present disclosure, there is provided a computer-readable recording medium having recorded thereon a program for the above-described signal transmission method.

[0016] In another aspect of the present disclosure, there is provided a UE configured to perform the above-described signal transmission method.

[0017] In another aspect of the present disclosure, there is provided an apparatus configured to control a UE to perform the above-described signal transmission method.

[0018] In another aspect of the present disclosure, there is provided a method for a base station (BS) to receive signals in a wireless communication system. The method includes the steps of: transmitting a CG configuration for uplink reception; and receiving a first PUSCH including a first UCI at a first CG-PUSCH occasion among CG-PUSCH occasions related to the CG configuration. The first UCI may include information indicating whether not to receive a second PUSCH at a second CG-PUSCH occasion located after the first CG-PUSCH occasion.

[0019] In another aspect of the present disclosure, there is provided a BS configured to perform the above-described signal reception method.

[0020] Advantageous Effects

[0021] According to an embodiment of the present disclosure, signals can be transmitted and received more accurately and more efficiently in a wireless communication system.

[0022] Those skilled in the art will understand that the effects achievable using the present disclosure are not limited to those specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 Illustrates physical channels used in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system and a general signaling method using the same.

[0024] Figure 2 Illustrates a radio frame structure.

[0025] Figure 3 Illustrates a resource grid of a time slot.

[0026] Figure 4 Illustrates an exemplary mapping of physical channels in a time slot.

[0027] Figure 5 Illustrates an example of a physical downlink shared channel (PDSCH) transmission / reception process.

[0028] Figure 6 Illustrates an example of a physical uplink shared channel (PUSCH) transmission / reception process.

[0029] Figure 7 Illustrates an example of a GOP structure / pattern.

[0030] Figure 8 and Figure 9 Illustrates an example of a method for indicating used / unused configured grant (CG) PUSCH opportunities according to an embodiment.

[0031] Figure 10 Illustrates a flow of a signal transmission method of a user equipment (UE) according to an embodiment.

[0032] Figure 11 Illustrates a flow of a signal reception method of a base station (BS) according to an embodiment.

[0033] Figures 12 to 15 Illustrates a communication system 1 and a wireless device applicable to the present disclosure.

[0034] Figure 16 Illustrates discontinuous reception (DRX) operations applicable to the present disclosure. DETAILED DESCRIPTION

[0035] Embodiments of the present disclosure are applicable to various radio access technologies such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA). CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented as radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) is an evolved version of 3GPP LTE. 3GPP New Radio (NR) (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0036] As more and more communication devices require greater communication capacity, enhanced mobile broadband communication is needed relative to traditional radio access technologies (RATs). Additionally, massive machine type communication (MTC), which is capable of providing various services anytime and anywhere by connecting multiple devices and objects, is another important issue to be considered in next-generation communications. The design of communication systems that consider services / user equipment (UEs) sensitive to reliability and latency is also being discussed. Therefore, the introduction of new radio access technologies that consider enhanced mobile broadband communication (eMBB), massive MTC, and ultra-reliable low-latency communication (URLLC) is being discussed. In the present disclosure, for simplicity, this technology will be referred to as NR (New Radio or New RAT).

[0037] For the sake of simplicity, 3GPP NR is mainly described, but the technical concept of the present disclosure is not limited thereto.

[0038] Details of the background, terms, abbreviations, etc. used herein can be found in the following documents.

[0039] 3GPP NR

[0040] - 3GPP TS 38.211: Physical Channels and Modulation

[0041] - 3GPP TS 38.212: Multiplexing and Channel Coding

[0042] - 3GPP TS 38.213: Physical Layer Procedures for Control

[0043] - 3GPP TS 38.214: Physical Layer Procedures for Data

[0044] - 3GPP TS 38.215: Physical Layer Measurements

[0045] - 3GPP TS 38.300: NR and NG-RAN Overall Description

[0046] - 3GPP TS 38.304: User Equipment (UE) Procedures in Idle Mode and RRC Inactive State

[0047] - 3GPP TS 38.321: Medium Access Control (MAC) Protocol

[0048] - 3GPP TS 38.322: Radio Link Control (RLC) Protocol

[0049] - 3GPP TS 38.323: Packet Data Convergence Protocol (PDCP)

[0050] - 3GPP TS 38.331: Radio Resource Control (RRC) Protocol

[0051] - 3GPP TS 37.324: Service Data Adaptation Protocol (SDAP)

[0052] - 3GPP TS 37.340: Multi-Connection; Overall Description

[0053] - 3GPP TS23.287: Application Layer Support for V2X Services; Functional Architecture and Information Flows

[0054] - 3GPP TS23.501: System Architecture for 5G Systems

[0055] - 3GPP TS23.502: Procedures for 5G Systems

[0056] - 3GPP TS23.503: Policy and Charging Control Framework for 5G Systems; Phase 2

[0057] - 3GPP TS24.501: Non-Access Stratum (NAS) Protocol for 5G Systems (5GS); Phase 3

[0058] - 3GPP TS24.502: Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access Networks

[0059] - 3GPP TS24.526: User Equipment (UE) Policy for 5G Systems (5GS); Phase 3

[0060] Abbreviations and Terms

[0061] -SS: Search Space

[0062] -CSS: Common Search Space

[0063] -USS: UE-Specific Search Space

[0064] -PDCCH: Physical Downlink Control Channel

[0065] -PDSCH: Physical Downlink Shared Channel;

[0066] -PUCCH: Physical Uplink Control Channel;

[0067] -PUSCH: Physical Uplink Shared Channel;

[0068] -DCI: Downlink Control Information

[0069] -UCI: Uplink Control Information

[0070] -PO: Paging Opportunity

[0071] -MO: Monitoring Opportunity

[0072] -SI: System Information

[0073] -SIB: System Information Block

[0074] -MIB: Master Information Block

[0075] -IE: Information Element

[0076] -RE: Resource Element

[0077] -RS: Reference Signal

[0078] -TRS: Tracking Reference Signal

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

[0080] -DRX: Discontinuous Reception

[0081] -C-DRX: Connected-Mode DRX

[0082] -RRC: Radio Resource Control

[0083] -AR: Augmented Reality

[0084] -VR: Virtual Reality

[0085] -SPS: Semi-Persistent Scheduling

[0086] -CG: Configuration Grant

[0087] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) through a downlink (DL) and transmits information to the BS through an uplink (UL). The information transmitted and received by the BS and the UE includes data and various control information, and includes various physical channels according to the type / usage of the information transmitted and received by the UE and the BS.

[0088] Figure 1 Shows the physical channels used in the 3GPP NR system and the general signaling method using them.

[0089] When the UE powers on again from a powered-off state or enters a new cell, in step S101, the UE performs an initial cell search process (e.g., establish synchronization with the BS). To this end, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE establishes synchronization with the BS based on the PSS / SSS and obtains information such as a cell identifier (ID). The UE can obtain broadcast information in the cell based on the PBCH. The UE can receive a DL reference signal (RS) during the initial cell search process to monitor the DL channel state.

[0090] The cell search process of the UE can be summarized as follows.

[0091] - Step 1 (related to PSS): Obtain the symbol timing of the SS / PBCH block (SSB) and detect the cell ID within the cell ID group (3 hypotheses)

[0092] - Step 2 (related to SSS): Detect the cell ID group (336 hypotheses)

[0093] - Step 3 (related to PBCH DMRS): SSB index and half-frame (HF) index (slot and frame boundary detection)

[0094] - Step 4 (related to PBCH): Obtain time information (80 ms, system frame number (SFN), SSB index, HF), remaining minimum system information (RMSI), control resource set (CORESET) / search space configuration

[0095] - Step 5 (related to PDCCH and PDSCH): Receive cell access information and RACH configuration

[0096] There can be 336 cell ID groups, and each cell ID group can have three cell IDs. There can be a total of 1008 cell IDs. Information about the cell ID group to which the cell ID of a cell belongs can be provided / obtained from the SSS of the cell, and information about the cell among the 336 cells can be provided / obtained from the PSS.

[0097] There can be 336 cell ID groups, and each cell ID group can have three cell IDs. There can be a total of 1008 cell IDs. Information about the cell ID group to which the cell ID of a cell belongs can be provided / obtained from the SSS of the cell, and information about the cell among the 336 cells can be provided / obtained from the PSS.

[0098] The SSB is transmitted periodically with the SSB period. The default SSB period assumed by the UE in the initial cell search is defined as 20 ms. After cell access, the network (e.g., BS) can set the SSB period to one of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms}. The SSB burst set can be configured at the start of the SSB period. The SSB burst set can be set to a time window of 5 ms (i.e., a half-frame), and the SSB can be repeatedly transmitted within the SS burst set up to L times. The maximum number L of SSB transmissions can be given as follows according to the carrier frequency band. One time slot includes at most two SSBs.

[0099] - For a frequency range of up to 3 GHz, L = 4

[0100] - For a frequency range from 3 GHz to 6 GHz, L = 8

[0101] - For a frequency range from 6 GHz to 52.6 GHz, L = 64

[0102] The time-domain position of the candidate SSBs in the SS burst set can be defined according to the subcarrier spacing. The time-domain position of the candidate SSBs is indexed in chronological order from (SSB index) 0 to L - 1 within the SSB burst set (i.e., a half-frame).

[0103] Multiple SSBs can be transmitted within the frequency span of a carrier. Each SSB may not need to have a unique physical layer cell identifier, but different SSBs can have different physical layer cell identifiers.

[0104] The UE can obtain DL synchronization by detecting the SSB. The UE can identify the structure of the SSB burst set based on the detected SSB (time) index, so the UE can detect symbol / slot / half-frame boundaries. The frame / half-frame number to which the detected SSB belongs can be identified based on the system frame number (SFN) information and the half-frame indication information.

[0105] Specifically, the UE can obtain the 10-bit SFN of the frame to which the PBCH belongs from the PBCH. Then, the UE can obtain 1-bit half-frame indication information. For example, when the UE detects a PBCH with the half-frame indication bit set to 0, the UE can determine that the SSB to which the PBCH belongs is included in the first half-frame of the frame. When the UE detects a PBCH with the half-frame indication bit set to 1, the UE can determine that the SSB to which the PBCH belongs is included in the second half-frame of the frame. Finally, the UE can obtain the SSB index of the SSB to which the PBCH belongs based on the DMRS sequence and the PBCH payload carried by the PBCH.

[0106] After initial cell search, in step S102, the UE can obtain more specific system information by receiving the physical downlink control channel (PDCCH) and receiving the physical downlink shared channel (PDSCH) based on the information of the PDCCH.

[0107] In steps S103 to S106, the UE can perform a random access procedure to access the BS. For random access, the UE can send a preamble on the physical random access channel (PRACH) to the BS (S103) and receive a response message to the preamble on the PDCCH and the PDSCH corresponding to the PDCCH (S104). In the case of contention-based random access, the UE can perform a contention resolution procedure by further sending the PRACH (S105) and receiving the PDCCH and the PDSCH corresponding to the PDCCH (S106).

[0108] After the foregoing procedures, the UE can receive the PDCCH / PDSCH (S107) and send the physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108), as a general downlink / uplink signal transmission process. The control information sent from the UE to the BS is called uplink control information (UCI). UCI includes hybrid automatic repeat request and acknowledgement / negative acknowledgement (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. Although UCI is usually sent on the PUCCH, when it is necessary to send control information and traffic data simultaneously, UCI can be sent on the PUSCH. In addition, UCI can be sent non-periodically on the PUSCH according to the request / command of the network.

[0109] Figure 2Shows the radio frame structure. In NR, uplink transmission and downlink transmission are configured with a frame. Each radio frame has a length of 10 ms and is divided into two 5-ms half-frames (HFs). Each half-frame is divided into five 1-ms sub-frames (SFs). A sub-frame is divided into one or more time slots, and the number of time slots in a sub-frame depends on the subcarrier spacing (SCS). According to the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When using normal CP, each time slot includes 14 OFDM symbols. When using extended CP, each time slot includes 12 OFDM symbols.

[0110] Table 1 exemplarily shows that when using normal CP, the number of symbols per time slot, the number of time slots per frame, and the number of time slots per sub-frame vary according to the SCS.

[0111] [Table 1]

[0112] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb > <![CDATA[N frame,u slot > <![CDATA[N subframe,u slot > 15KHz (u = 0) 14 10 1 30KHz (u = 1) 14 20 2 60KHz (u = 2) 14 40 4 120KHz (u = 3) 14 80 8 240KHz (u = 4) 14 160 16

[0113] *N slot symb : Number of symbols in a time slot

[0114] *N frame,u slot : Number of time slots in a frame

[0115] *N subframe,u slot : Number of time slots in a sub-frame

[0116] Table 2 shows that when using extended CP, the number of symbols per time slot, the number of time slots per frame, and the number of time slots per sub-frame vary according to the SCS.

[0117] [Table 2]

[0118] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb > <![CDATA[N frame,u slot > <![CDATA[N subframe,u slot > 60KHz (u = 2) 12 40 4

[0119] The structure of the frame is only an example. The number of sub-frames, time slots, and symbols in a frame can vary.

[0120] In the NR system, OFDM parameter sets (e.g., SCS) can be configured differently for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) composed of the same number of symbols (referred to as a time unit (TU) for simplicity) can be configured differently among the aggregated cells. Here, the symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete Fourier transform - spread - OFDM (DFT - s - OFDM) symbols).

[0121] Figure 3Shows a resource grid of a time slot. A time slot includes multiple symbols in the time domain. For example, when using normal CP, a time slot includes 14 symbols. However, when using extended CP, a time slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple consecutive subcarriers in the frequency domain (e.g., 12 consecutive subcarriers). A bandwidth part (BWP) can be defined as multiple consecutive physical resource blocks (PRBs) in the frequency domain and corresponds to a single parameter set (e.g., SCS, CP length, etc.). A carrier can include at most N (e.g., five) BWPs. Data communication can be performed through an enabled BWP, and only one BWP can be enabled for one UE. In the resource grid, each element is called a resource element (RE), and one complex symbol can be mapped to each RE.

[0122] Figure 4 Shows an exemplary mapping of physical channels in a time slot. In an NR system, a frame is characterized by a self - contained structure in which a DL control channel, DL or UL data, and a UL control channel can all be included in one time slot. For example, the first N symbols of a time slot (hereinafter referred to as the DL control region) can be used to transmit a DL control channel (e.g., PDCCH), and the last M symbols of the time slot (hereinafter referred to as the UL control region) can be used to transmit a UL control channel (e.g., PUCCH). Each of N and M is an integer equal to or greater than 0. The resource region between the DL control region and the UL control region (hereinafter referred to as the data region) can be used to transmit DL data (e.g., PDSCH) or UL data (e.g., PUSCH). A guard period (GP) provides a time gap for the transmission mode to reception mode switching or reception mode to transmission mode switching at the BS and the UE. Some symbols at the DL - to - UL handover in a subframe can be configured as the GP.

[0123] The PDCCH transmits DCI. For example, the PDCCH (i.e., DCI) can carry information about the transmission format and resource allocation of the DL shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about the DL-SCH, information about the resource allocation of high-layer control messages (e.g., RAR sent on the PDSCH), transmit power control commands, information about the enabling / release of the configured scheduling, etc. The DCI includes a cyclic redundancy check (CRC). The CRC is masked using various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)) according to the owner or use of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked by the UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is for a paging message, the CRC is masked by the paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., system information block (SIB)), the CRC is masked by the system information RNTI (SI-RNTI). When the PDCCH is for the RAR, the CRC is masked by the random access-RNTI (RA-RNTI).

[0124] The BS can send a control resource set (CORESET) configuration to the UE. The CORESET is defined as a set of resource element groups (REGs) with a given parameter set (e.g., SCS, CP length, etc.). A REG is defined by one (P)RB for one OFDM symbol. Multiple CORESETs for one UE can overlap with each other in the time domain / frequency domain. The CORESET can be configured by system information (e.g., master information block (MIB)) or high-layer signaling (e.g., radio resource control (RRC) signaling). For example, the configuration information about a specific common CORESET (e.g., CORESET#0) can be sent in the MIB. For example, the PDSCH carrying the system information block 1 (SIB1) can be scheduled by a specific PDCCH, and CORESET#0 can be used to carry the specific PDCCH. The configuration information about CORESET#N (e.g., N>0) can be sent by RRC signaling (e.g., cell-common RRC signaling or UE-specific RRC signaling). For example, the UE-specific RRC signaling carrying the CORESET configuration information can include various types of signaling, such as RRC setup messages, RRC reconfiguration messages, and / or BWP configuration information. Specifically, the CORESET configuration can include the following information / fields.

[0125] -controlResourceSetId: Indicates the ID of the CORESET.

[0126] - frequencyDomainResources: Indicates the frequency resources of the CORESET. The frequency resources of the CORESET are indicated by a bitmap where each bit corresponds to an RBG (e.g., 6 (consecutive) RBs). For example, the most significant bit (MSB) of the bitmap corresponds to the first RBG. The RBGs corresponding to the bits set to 1 are allocated as the frequency resources of the CORESET.

[0127] - duration: Indicates the time resources of the CORESET. duration indicates the number of consecutive OFDM symbols included in the CORESET. duration has values from 1 to 3.

[0128] - cce-REG-MappingType: Indicates the control channel element (CCE) to REG mapping type. Interleaved and non-interleaved types are supported.

[0129] - interleaverSize: Indicates the interleaver size.

[0130] - pdcch-DMRS-ScramblingID: Indicates the value used for PDCCH DMRS initialization. When pdcch-DMRS-ScramblingID is not included, the physical cell ID of the serving cell is used.

[0131] - precoderGranularity: Indicates the precoder granularity in the frequency domain.

[0132] - reg-BundleSize: Indicates the REG bundle size.

[0133] - tci-PresentInDCI: Indicates whether the transmission configuration indicator (TCI) field is included in DL-related DCI.

[0134] - tci-StatesPDCCH-ToAddList: Indicates a subset of the TCI states configured in pdcch-Config that provides the quasi-colocation (QCL) relationship between the DL RS in the RS set (TCI state) and the PDCCH DMRS ports.

[0135] In addition, the BS may send the PDCCH search space (SS) configuration to the UE. The PDCCH SS configuration can be sent via higher layer signaling (e.g., RRC signaling). For example, the RRC signaling may include (but is not limited to) various types of signaling such as RRC setup messages, RRC reconfiguration messages, and / or BWP configuration information. For example, the CORESET configuration and the PDCCH SS configuration may be sent in one message (e.g., via one RRC signaling) or sent separately in different messages.

[0136] The PDCCH SS configuration may include information about the configuration of the PDCCH SS set. The PDCCH SS set may be defined as a set of PDCCH candidates to be monitored (e.g., blindly detected) by the UE. One or more SS sets may be configured for the UE. Each SS set may be a USS set or a CSS set. For convenience, the PDCCH SS set may be referred to as "SS" or "PDCCH SS".

[0137] The PDCCH SS set includes PDCCH candidates. A PDCCH candidate is a CCE that the UE monitors to receive / detect the PDCCH. Monitoring includes blind decoding (BD) of the PDCCH candidates. One PDCCH (candidate) includes 1, 2, 4, 8, or 16 CCEs according to the aggregation level (AL). One CCE includes 6 REGs. Each CORESET configuration is associated with one or more SSs, and each SS is associated with a CORESET configuration. One SS is defined based on one SS configuration, and the SS configuration may include the following information / fields.

[0138] - searchSpaceId: Indicates the ID of the SS.

[0139] - controlResourceSetId: Indicates the CORESET associated with the SS.

[0140] - monitoringSlotPeriodicityAndOffset: Indicates the periodicity (in time slots) and offset (in time slots) of PDCCH monitoring.

[0141] - monitoringSymbolsWithinSlot: Indicates the first OFDM symbol for PDCCH monitoring in the time slot configured with PDCCH monitoring. The first OFDM symbol for PDCCH monitoring is indicated by a bitmap in which each bit corresponds to an OFDM symbol in the time slot. The MSB of the bitmap corresponds to the first OFDM symbol of the time slot. The OFDM symbol corresponding to the bit set to 1 corresponds to the first symbol of the CORESET in the time slot.

[0142] - nrofCandidates: Indicates the number of PDCCH candidates for each AL (one of the values 0, 1, 2, 3, 4, 5, 6, and 8), where AL = {1, 2, 4, 8, 16}.

[0143] - searchSpaceType: Indicates the common search space (CSS) or UE-specific search space (USS) and the DCI format used in the corresponding SS type.

[0144] Subsequently, the BS may generate a PDCCH and send the PDCCH to the UE, and the UE may monitor PDCCH candidates in one or more SSs to receive / detect the PDCCH. The timing (e.g., time / frequency resources) for the UE to monitor PDCCH candidates is defined as the PDCCH (monitoring) occasion. One or more PDCCH (monitoring) occasions may be configured in a time slot.

[0145] Table 3 shows the characteristics of each SS.

[0146] [Table 3]

[0147]

[0148] Table 4 shows the DCI formats transmitted on the PDCCH.

[0149] [Table 4]

[0150]

[0151] DCI format 0_0 can be used to schedule a TB (or TB-level) based PUSCH, and DCI format 0_1 can be used to schedule a TB (or TB-level) based PUSCH or a codeblock group (CBG) (or CBG-level) based PUSCH. DCI format 1_0 can be used to schedule a TB (or TB-level) based PDSCH, and DCI format 1_1 can be used to schedule a TB (or TB-level) based PDSCH or a CBG (or CBG-level) based PDSCH (or DL grant DCI). DCI formats 0_0 / 0_1 can be referred to as UL grant DCI or UL scheduling information, and DCI formats 1_0 / 1_1 can be referred to as DL grant DCI or DL scheduling information. DCI format 2_0 is used to convey dynamic time slot format information (e.g., dynamic time slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to convey DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 may be sent to a corresponding group of UEs on the group common PDCCH (PDCCH pointing to a group of UEs).

[0152] DCI formats 0_0 and 1_0 can be referred to as fallback DCI formats, while DCI formats 0_1 and 1_1 can be referred to as non-fallback DCI formats. In the case of fallback DCI formats, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, in the case of non-fallback DCI formats, the DCI size / field configuration varies according to the UE configuration.

[0153] The PDSCH carries downlink data (e.g., DL-SCH transport block, DL-SCH TB). A modulation scheme such as quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (QAM), 64QAM, or 256QAM is applied to the PDSCH. Codewords are generated by encoding the TB. The PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer, together with the demodulation reference signal (DMRS), is mapped to resources, generated as an OFDM symbol signal, and transmitted through the corresponding antenna port.

[0154] The PUCCH carries uplink control information (UCI). The UCI can include one or more of the following information.

[0155] - SR (scheduling request): Information for requesting UL-SCH resources.

[0156] - HARQ (hybrid automatic repeat request)-ACK (acknowledgment): It is a response to a downlink data packet (e.g., codeword) on the PDSCH, indicating whether the downlink data packet has been successfully received. A 1-bit HARQ-ACK can be sent in response to a single codeword, and a 2-bit HARQ-ACK can be sent in response to two codewords. The HARQ-ACK response includes a positive ACK (simply referred to as ACK), a negative ACK (NACK), DTX, or NACK / DTX. Here, the HARQ-ACK can be referred to as HARQ ACK / NACK and ACK / NACK.

[0157] - CSI (channel state information): Feedback information on the downlink channel. The multiple-input multiple-output (MIMO)-related feedback information includes a rank indicator (RI) and a precoding matrix indicator (PMI).

[0158] Table 5 shows the PUCCH formats. According to the PUCCH length, the PUCCH formats can be classified into short PUCCH (format 0, 2) and long PUCCH (format 1, 3, 4).

[0159] [Table 5]

[0160]

[0161] The PUSCH carries uplink data (e.g., UL-SCH transport block, UL-SCH TB) and / or uplink control information (UCI). The PUCCH is transmitted based on the CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) waveform or the Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the UE performs transform precoding for the PUSCH. For example, if transform precoding is not performed (e.g., transform precoding is disabled), the UE transmits the PUSCH based on the CP-OFDM waveform. If transform precoding is performed (e.g., transform precoding is enabled), the UE transmits the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. The PUSCH transmission is dynamically scheduled by UL grant in DCI (e.g., layer 1 (PDCCH) signaling), and / or semi-statically scheduled based on higher layer (e.g., RRC) signaling (configured grant). The PUSCH transmission can be performed based on a codebook or non-codebook.

[0162] Figure 5 Shows an example of the PDSCH transmission / reception process. Refer to Figure 5 , the UE can detect the PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH indicates the DL assignment to the PDSCH offset (K0) and the PDSCH-HARQ-ACK reporting offset (K1). For example, DCI format 1_0 and 1_1 can include the following information.

[0163] - Frequency Domain Resource Assignment (FDRA): The FDRA indicates the set of RBs allocated to the PDSCH

[0164] - Time Domain Resource Assignment (TDRA): The TDRA indicates K0 (e.g., slot offset), the starting position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index), and the length of the PDSCH (e.g., the number of OFDM symbols)

[0165] - PDSCH-to-HARQ_feedback timing indicator, which indicates K1 (e.g., slot offset)

[0166] - HARQ process number (4 bits), which indicates the HARQ process ID (identification) of the data (e.g., PDSCH or TB)

[0167] - PUCCH Resource Indicator (PRI): The PRI indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources in the PUCCH resource set

[0168] The UE receives the PDSCH in time slot #(n + K0) based on the scheduling information received in time slot #n. After the reception of the PDSCH in time slot #n1 (where n + K0 ≤ n1) is completed, the UE may send UCI from time slot #(n1 + K1) via the PUCCH. Here, the UCI may include a HARQ-ACK response for the PDSCH. In Figure 5 For convenience, it is assumed that the SCS of the PDSCH and the SCS of the PUCCH are the same, and it is assumed that time slot #n1 = time slot #n + K0, but the present disclosure is not limited thereto. If the SCSs are different, K1 may be indicated / interpreted based on the SCS of the PUCCH.

[0169] If the PDSCH is configured to carry at most 1 TB, the HARQ-ACK response may have 1 bit. When the PDSCH is configured to carry at most 2 TBs, when spatial bundling is not configured, the HARQ-ACK response may be configured with 2 bits, and when spatial bundling is configured, the HARQ-ACK response may be configured with 1 bit. When the HARQ-ACK transmission time for multiple PDSCHs is configured as time slot #(n + K1), the UCI sent in time slot #(n + K1) includes HARQ-ACK responses for the multiple PDSCHs.

[0170] It may be configured for each cell group whether the UE should perform spatial bundling for the HARQ-ACK response (e.g., RRC / higher layer signaling). As an example, spatial bundling may be configured separately in each HARQ-ACK response sent via the PUCCH and / or the HARQ-ACK response sent via the PUSCH.

[0171] When the maximum number of TBs (or codewords) that can be received (or scheduled by 1 DCI) in a corresponding serving cell at one time is two (or two or more) (e.g., the higher layer parameter maxNrofCodeWordsScheduledByDCI is equal to 2 - TB), spatial bundling may be supported. In addition, more than four layers may be used for 2 - TB transmission, and at most four layers may be used for 1 - TB transmission. As a result, when spatial bundling is configured in a corresponding cell group, spatial bundling may be performed for serving cells in the corresponding cell group that can be scheduled for more than four layers. On a corresponding serving cell, a UE desiring to send a HARQ-ACK response via spatial bundling may generate the HARQ-ACK response by performing a (bitwise) logical AND operation on the ACK / NACK (A / N) bits of multiple TBs.

[0172] For example, assume that the UE receives DCI for scheduling two transport blocks (TBs) and receives the two TBs via PDSCH based on the DCI. If spatial bundling is performed, a single A / N bit may be generated by performing a logical AND operation on the first A / N bit of the first TB and the second A / N bit of the second TB. As a result, if both the first TB and the second TB are ACKs, the UE reports the ACK bit value to the BS, and when either TB is a NACK, the UE reports the NACK bit value to the BS.

[0173] For example, when actually only one TB is scheduled on the serving cell that allows reception of two TBs, the UE may generate a single A / N bit by performing a logical AND operation on the A / N bit of the corresponding one TB and the bit value 1. As a result, the UE may report the A / N bit of the corresponding one TB to the BS as it is.

[0174] Multiple parallel downlink (DL) hybrid automatic repeat request (HARQ) processes may be configured for DL transmission in a base station / terminal. The multiple parallel HARQ processes allow DL transmissions to be continuously performed while waiting for the HARQ feedback on whether the reception of a previous DL transmission was successful or not. Each HARQ process is associated with a HARQ buffer in the media access control (MAC) layer. Each DL HARQ process manages information related to the number of MAC protocol data unit (PDU) transmissions in the buffer, the HARQ feedback of the MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0175] Figure 6 An example of the PUSCH transmission / reception process is shown. Referring to Figure 6 , the UE may detect a physical downlink control channel (PDCCH) in time slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI format 0_0, 0_1). DCI formats 0_0 and 0_1 may include the following information.

[0176] - Frequency-domain resource allocation (FDRA), which indicates the set of resource blocks (RBs) allocated to the PUSCH

[0177] - Time-domain resource allocation (TDRA), which indicates the time slot offset K2, the start position (e.g., symbol index) of the PUSCH in the time slot, and the length (e.g., the number of OFDM symbols). The start symbol and the length may be indicated by a start and length indicator value (SLIV), or may be indicated separately.

[0178] The UE may transmit a PUSCH in time slot #(n + K2) according to the scheduling information received in time slot #n. The PUSCH may include a UL-SCH TB.

[0179] Configuration Grant (CG)

[0180] A semi-static configured grant (CG) can be configured for a UE by a higher layer (RRC). For the BWP of a serving cell, the UE can be configured with up to 12 active CGs.

[0181] Each CG can be of type 1 or type 2. For a type 1 CG, all parameters of UL transmission (e.g., PUSCH) are signaled by the higher layer. For a type 2 CG, some parameters of UL transmission are signaled by the higher layer, while the remaining parameters are signaled by the PDCCH (e.g., DCI format 0_1 in Table 4). The enabling / disabling of type 1 CGs can be performed independently between serving cells. The enabling / disabling of type 2 CGs can be performed by DCI carried on a PDCCH scrambled with a configured scheduling RNTI (CS-RNTI). When multiple type 2 CGs are configured, the enabling of each type 2 CG can be performed individually by DCI. One DCI can disable one type 2 CG or multiple type 2 CGs.

[0182] For CG-based transmission in NR-U (i.e., shared spectrum channel access), configured grant uplink control information (CG-UCI) is sent on a CG PUSCH (i.e., a PUSCH scheduled by a CG). In NR-U, multiplexing between a PUCCH carrying CG-UCI and a PUCCH carrying HARQ-ACK can be configured / allowed by the BS. In the case where multiplexing between a PUCCH carrying CG-UCI and a PUCCH carrying HARQ-ACK is not configured, if the PUCCH carrying HARQ-ACK overlaps with a CG PUSCH within a PUCCH group, the CG PUSCH transmission is discarded.

[0183] Repetition can be configured for the transmission of a CG PUSCH. Specifically, PUSCH repetition type A or PUSCH repetition type B can be configured. For PUSCH repetition type A, the CG PUSCH is repeated K times in K consecutive time slots (i.e., one PUSCH is mapped to each time slot). For PUSCH repetition type A, if the nominal repetition count and the time resource of the first nominal repetition are indicated to the UE, the UE performs the actual repetition based on this. The actual repetition count can be greater than the nominal repetition count. For example, the time resource of subsequent nominal repetitions is determined from the time resource of the nominal repetition indicated to the UE. If there is a DL resource between nominal repetitions or if a nominal repetition crosses a time slot boundary, the nominal repetition can be divided into multiple actual repetitions in the time domain.

[0184] Dynamic Indication of Unused CG PUSCH Opportunities or Resources

[0185] In the present disclosure, a method will be described for transmitting video information for an extended reality (XR) service on preconfigured resources (e.g., CG) in an NR wireless communication system while reducing power consumption and increasing the efficiency of radio resources while ensuring the availability and reliability of transmission resources.

[0186] In NR, for periodic transmission and reception, low latency, and low PDCCH overhead, a UE may be configured with one or more CG PUSCHs. Each CG configuration may have a cycle, so the configured / indicated resources may be repeated. In other words, the initially configured / indicated resource allocation may be repeated according to the configured cycle, and the UE may perform UL transmission on the resources without separate PDCCH reception processing. There are various types of XR data. Among the various types of data, sensor information, location information, and video data of the UE that are typically reported in a specific cycle may be transmitted and received on CG resources. Due to reasons such as video encoding time, sensor measurement time, higher layer operations, and network routing changes, this data may have varying traffic arrival times, which may cause jitter.

[0187] Considering jitter, if resources are allocated at a time sufficiently far from the expected traffic arrival time, the availability of the resources can be ensured, but delays may occur. On the other hand, if CG resources with a fixed cycle are allocated at the expected data arrival time, due to jitter, greater delays may occur due to the waiting time until the next available resource.

[0188] Some data appears based on events, so it is not possible to accurately determine the exact time when the actual data appears. However, using CG resources for such data is being considered in order to reduce the delay caused by scheduling. For this purpose, methods for skipping have been discussed. According to these methods, when preparing for the appearance of data, sufficient resources are allocated in a shorter cycle, and the UE or BS selectively uses these resources without using other resources. It is necessary to carefully consider the response signal to determine whether to confirm the reception and transmission between the UE and the BS. If the UE transmits a response signal for a transmission that the UE has not received, the BS needs to always prepare resources for the UE to transmit such a response signal. Considering that the skipping method is based on allocating sufficient resources among radio resources, these resources may become a significant UL burden. In addition, considering that these resources can be multiplexed among UEs, the burden on UL resources should be considered more strictly.

[0189] For the quality of the XR service, ensuring low latency is crucial. Therefore, it is necessary to consider a method that minimizes the impact on latency while reducing the impact of jitter. To solve this problem, the present disclosure relates to a method of selectively using some of the multiple CG resources configured between the UE and the BS and simplifying and transmitting a response to the used CG resources at a predefined location.

[0190] GOP (Group of Pictures)

[0191] Figure 7 An example of a GOP structure / pattern is shown.

[0192] A GOP for video coding may include I, P, B, and D picture types.

[0193] An I picture or I frame (also referred to as an intra-coded picture, 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).

[0194] A predictive-coded (P) picture or P frame includes motion-compensated difference information relative to a previously decoded picture. In older designs such as MPEG-1, H.262 / MPEG-2, and H.263, each P picture may only refer to one picture, and that picture should be before the P picture in both display and decoding order, and should be an I or P picture. This constraint is not imposed on the latest standards H.264 / MPEG-4 AVC and HEVC.

[0195] A bi-predictive-coded (B) picture or B frame includes motion-compensated difference information relative to a previously decoded picture. In older designs such as MPEG-1 and H.262 / MPEG-2, each B picture may only refer to two pictures: one before the B picture and one after it. All reference pictures should be I or I.P pictures. This constraint is not imposed on the latest standards H.264 / MPEG-4 AVC and HEVC.

[0196] A direct-coded (DC) (D) picture or D frame is used as a fast-access representation of a picture for loss robustness or fast forward. D pictures are only used in MPEG-1 video.

[0197] As Figure 7 shown, the I frame indicates the start of the GOP. This is followed by multiple P frames and B frames. In previous schemes, the allowed order and reference structure were relatively limited.

[0198] A GOP structure can be represented by two numbers, e.g., M = 3 and N = 12. The first number represents the distance between two anchor frames (I or P). The second number represents the distance between two complete images (I frames). This is the GOP size. In the example of M = 3 and N = 12, the GOP structure is IBBPBBPBBPBBI. Instead of the M parameter, the maximum number of B frames between two consecutive anchor frames can be used.

[0199] For example, in the pattern sequence IBBBBPBBBBPBBBBBI, 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).

[0200] An I-frame includes a complete image and does not require any additional information to reconstruct it. Generally, the encoder uses a GOP structure that makes each I-frame a "clean random access point". Therefore, decoding can start at an I-frame, and any errors within the GOP structure can be corrected after processing the correct I-frame.

[0201] The present disclosure proposes a method for UL CG radio resources based on semi-static configuration. However, those skilled in the art can understand that the proposed method is not limited thereto and can be extended to radio resources allocated by dynamic scheduling received by the UE. For example, regardless of whether it is SPS PDSCH or dynamically scheduled PDSCH, a method for determining a single HARQ-ACK timing for multiple DL radio resources allocated to the UE can be applied. Additionally, when multiple radio resources are not semi-statically configured but are configured by dynamic indication, for example, when multiple radio resources are configured at once via DCI, the proposed method can also be applied. Therefore, it is obvious that the proposed method can be applied to all types of transmission and reception methods expected by the BS and the UE. For ease of explanation, the present disclosure uses the term SPS as a general concept referring to radio resources configured semi-statically (e.g., DL / UL SPS, CG).

[0202] In the present disclosure, a transmission occasion (TO) refers to radio resources configured for CG purposes (e.g., CG PDSCH). The entity that performs transmission during the transmission occasion (i.e., the BS in the case of DL and the UE in the case of UL) can attempt to transmit during the transmission occasion, and the receiver (i.e., the UE in the case of DL and the BS in the case of UL) can expect transmission and attempt to receive during each transmission occasion.

[0203] The following examples are described based on the NR system, but the proposed method is not limited to the specific transmission and reception forms of NR. Additionally, although the following examples are described based on the characteristics and structures of XR services, the proposed method is not limited to supporting XR services. Therefore, the proposed method can be applied to the structures and services of all wireless communication transmissions and receptions.

[0204] Hereinafter, a method for the UE to report unused CG PUSCH resources that are not available for UL MAC PDU transmission to the BS is proposed.

[0205] The UE may send an unused CG indicator (i.e., an indicator of used and / or unused CG PUSCH resources / timings) in UL before the unused CG PUSCH resources (CG PUSCH resources / timings). Alternatively, the UE may use the unused CG PUSCH resources for UL transmission. If UL transmission is performed before the CG PUSCH resources, the UL transmission needs to be sent before a symbol or a specific symbol or specific timing of a slot of the unused CG PUSCH resources (e.g., before at most 14 symbols from the symbol or slot of the unused CG PUSCH resources).

[0206] If the indicator is sent before a symbol or a specific symbol or specific timing of a slot of the unused CG PUSCH resources, the UE MAC does not configure a MAC PDU for the indicated unused CG PUSCH resources in the logical channel prioritization function. In other words, in the logical channel prioritization function, the indicated CG PUSCH resources are not considered as valid UL resources for configuring MAC PDUs. Alternatively, even if the UE MAC configures the MAC PDU to be sent on the indicated unused CG PUSCH resources, when receiving the MAC PDU, the UE physical layer may send the MAC PDU in UL, may not send the MAC PDU by discarding / skipping the MAC PDU, may send the MAC PDU with low priority, or may delay and send (retransmit) the MAC PDU.

[0207] If the indicator is not sent before a symbol or a specific symbol or specific timing of a slot of the unused CG PUSCH resources, the UE MAC may configure a MAC PDU for the indicated unused CG PUSCH resources according to the logical channel prioritization function. In other words, in the logical channel prioritization function, the indicated CG PUSCH resources may be considered as valid UL resources for configuring MAC PDUs. If a MAC PDU is configured for the indicated unused CG PUSCH resources, the UE physical layer may send the MAC PDU (alternatively, the UE physical layer may not send the MAC PDU by discarding / skipping the MAC PDU, may send the MAC PDU with low priority, or may delay and send (retransmit) the MAC PDU).

[0208] The unused CG indicator may be sent as UCI on a UE-specific PUCCH resource, UCI on a cell-specific PUCCH resource, UCI on a UE-common PUCCH resource, UCI sent using PUSCH, CG-UCI sent using CG PUSCH, a specific MAC CE included in the MAC PDU of PUSCH, or a specific RRC message included in the MAC PDU of PUSCH.

[0209] A UCI, MAC CE, or RRC message containing an unused CG indicator may include the HARQ process ID, MCS, FDRA, and / or TDRA of the CGPUSCH used to send the unused CG indicator. Alternatively, the UCI, MAC CE, or RRC message may include the HARQ process ID, MCS, FDRA, and / or TDRA of a used or unused CG PUSCH indicated by the unused CG indicator.

[0210] The unused CG indicator may indicate the used or unused status of the CG PUSCH that sends the unused CG indicator, or the unused CG indicator may indicate the used or unused status of a previous CG PUSCH or a subsequent CG PUSCH that is not the CG PUSCH that sends the unused CG indicator.

[0211] The UE may uplink transmit the unused CG indicator before the unused CG PUSCH resource (i.e., an indication of used and / or unused CGPUSCH resources / timings) or use the unused CG PUSCH resource for UL transmission.

[0212] - The UE may uplink transmit the unused CG indicator within the same CG cycle as the unused CG PUSCH resource. Alternatively, the UE may uplink transmit the unused CG indicator on the CG PUSCH resource or within the CG cycle of the HARQ process ID that is the same as the HARQ process ID mapped to the unused CG PUSCH resource.

[0213] - Alternatively, the UE may uplink transmit the unused CG indicator within the previous CG cycle of the unused CG PUSCH resource. The UE may uplink transmit the unused CG indicator on the CG PUSCH resource or within the CG cycle of the HARQ process ID that is before the HARQ process ID mapped to the unused CG PUSCH resource.

[0214] The UE may send the unused CG indicator according to the following options. In this case, the unused CG indicator may indicate one or more time slots of one or more used and / or unused CG PUSCH resources. The indicated multiple used and / or unused CG PUSCH resources may be within the same CG cycle or in different CG cycles. Additionally, the indicated multiple used and / or unused CG PUSCH resources may be limited to CG resources with the same HARQ process ID or may be CG resources with different HARQ process IDs.

[0215] (1) Option 1A: The UE sends an indicator indicating only the used CG PUSCH via UCI or MAC CE.

[0216] The UCI or MAC CE associated with the used CG PUSCH occasion X of the CG period Y (or HARQ ID Y) of the CG configuration Z may indicate at least one of the following (hereinafter, k, m, and n may be set / signaled as positive integers, negative integers, or 0):

[0217] 1) The use of the associated CG PUSCH occasion X may be indicated by at least one of the following:

[0218] (i) A 1-bit in the UCI / MAC CE.

[0219] (ii) The use of the associated CG PUSCH occasion X may be indicated by multiple bits in the UCI / MAC CE. Additionally, the MCS and / or FDRA of the used CG PUSCH resource / occasion may be indicated.

[0220] (iii) Indicating that the CG PUSCH occasion X + k (k > 0) of the CG period Y is not used.

[0221] 2) The use of the CG PUSCH occasion X + k in the same CG period, CG period Y (or HARQ ID Y), may be indicated by at least one of the following:

[0222] (i) Indicating a single value of k.

[0223] For example, in this case, each CGPUSCH from the CG PUSCH occasion X to the CG PUSCH occasion X + k may be used.

[0224] Alternatively, each CG PUSCH occasion from X + 1 to X + k may not be used.

[0225] (ii) Indicating multiple k values (e.g., the values are indicated in the form of a bitmap or the number of k values).

[0226] For example, a bitmap indicating discontinuous used / unused CG PUSCH may be used.

[0227] For example, the number of k values representing continuous used CG PUSCH may be used.

[0228] 3) The indication that the CG PUSCH occasion X + k is not used for the same CG period, CG period Y (or HARQ process ID Y), may be provided by at least one of the following:

[0229] (i) Indicating a single value of k.

[0230] For example, in this case, each CG PUSCH occasion from CG PUSCH occasion X to CG PUSCH occasion X+k can be used.

[0231] (ii) Multiple values of k can be indicated (e.g., in the form of a bitmap or the number of k values).

[0232] For example, a bitmap indicating discontinuous used / unused CG PUSCH can be used.

[0233] For example, the number of k values representing consecutive used CG PUSCH can be used.

[0234] 4) Whether the CG PUSCH occasion X+k is used for the same CG cycle, CG cycle Y (or HARQ process ID Y) can be indicated by at least one of the following:

[0235] (i) Indicating one or more "k" values and the "used" or "unused" indication for each CG PUSCH occasion (e.g., via a bitmap or the number of k values).

[0236] 5) Whether the CG PUSCH occasion X+k is used for CG cycle Y+m (or HARQ process ID Y+m).

[0237] (i) Indicating that the CG PUSCH occasion X+k is not used by the HARQ process ID of UCI or MAC CE.

[0238] The "k" value can indicate the used / unused CG PUSCH occasions of different HARQ process IDs.

[0239] (ii) Indicating CG cycle Y+m (or HARQ process ID Y+m) via UCI.

[0240] All CG PUSCH occasions of CG cycle Y+m (or HARQ process ID Y+m) can be used or not used according to the corresponding indication.

[0241] 6) Whether the CG PUSCH occasion X+k is used for the CG cycle Y+m (or HARQ process ID Y+m) of CG configuration Z+n can be indicated by at least one of the following:

[0242] (i) Indicating that the CG PUSCH occasion X+k is not used by indicating CG configuration Z+n via UCI or MAC CE

[0243] The indication of the used CG PUSCH occasion X of CG cycle Y+m (or HARQ process ID Y+m) of CG configuration Z can represent the following:

[0244] - This indication represents the "used" or "unused" status of each CG PUSCH opportunity of CG configuration Z+n associated with the used CG PUSCH opportunity X of CG cycle Y+m (or HARQ process ID Y+m) of CG configuration Z.

[0245] For example, when Z = 1 and n = 1 and 2, CG configurations 2 and 3 can be associated with CG configuration 1. In this case, if CG configurations 1, 2, and 3 are all enabled, and the UCI or MAC CE indicates the use of a specific CG PUSCH opportunity in CG configuration 1, the UE determines whether to use or not use the CG PUSCH opportunities of the associated CG configurations 2 and 3. If CG configuration 4, which is not connected to CG configuration 1, is enabled, it may not be possible to determine whether to use any CG PUSCH opportunities in CG configuration 4 based on whether a specific CG PUSCH opportunity in CG configuration 1 is used. In other words, this operation can only be applied to connected CG configurations.

[0246] Alternatively, this operation can be applied among all enabled CG configurations regardless of their connection status.

[0247] (ii) Indicate CG configuration Z+n via UCI or MAC CE.

[0248] According to the indication, all CG PUSCH opportunities of CG configuration Z+n can be used or not used.

[0249] - For example, when Z = 1 and n = 1 and 2, CG configurations 2 and 3 are associated with CG configuration 1. In this case, if CG configurations 1, 2, and 3 are all enabled, and the UCI or MAC CE indicates the use of CG configuration 1 or a specific CG PUSCH opportunity of CG configuration 1, the UE determines whether to use or not use all CG PUSCH opportunities of the associated CG configurations 2 and 3. If CG configuration 4, which is not connected to CG configuration 1, is enabled, it may not be possible to determine whether to use all CG PUSCH opportunities in CG configuration 4 based on whether CG configuration 1 or a specific CG PUSCH opportunity of CG configuration 1 is used. In other words, this operation can only be applied to connected CG configurations.

[0250] - Alternatively, this operation can be applied among all enabled CG configurations regardless of their connection status.

[0251] (2) Option 1B: The UE sends an indicator indicating only the unused CG PUSCH via UCI or MAC CE.

[0252] In this case, the UCI can be CG-UCI sent using CG PUSCH.

[0253] The UCI associated with the unused CG PUSCH occasion X of the CG period Y (or HARQ ID Y) of the CG configuration Z may indicate the following:

[0254] 1) The UCI may indicate not to use the associated CG PUSCH occasion X.

[0255] (i) It may be indicated by 1 bit in the UCI or MAC CE.

[0256] - The UCI may indicate not to use the associated CG PUSCH occasion X + k.

[0257] (i) A single value of k may be indicated.

[0258] For example, in this case, each CG PUSCH occasion from the CG PUSCH occasion X to the CG PUSCH occasion X + k may not be used.

[0259] Alternatively, each CG PUSCH occasion from the CG PUSCH occasion X + 1 to the CG PUSCH occasion X + k may be used.

[0260] (ii) Indicate multiple "k" values (e.g., indicate a bitmap or the number of k values).

[0261] For example, a bitmap indicating discontinuous unused / used CG PUSCH may be used.

[0262] For example, the number of k values indicating continuous unused CG PUSCH may be used.

[0263] 2) The indication to use the associated CG PUSCH occasion X + k may be provided according to at least one of the following:

[0264] (i) A single value of k is indicated.

[0265] In this case, each CG PUSCH occasion up to the CG PUSCH occasion X + k may not be used.

[0266] (ii) Indicate multiple "k" values (e.g., indicate a bitmap or the number of k values).

[0267] For example, a bitmap indicating discontinuous used / unused CG PUSCH may be used.

[0268] For example, the number of k values representing continuous used CG PUSCH may be used.

[0269] 3) Indicate whether to use the CG PUSCH occasion X + k in the same CG period, CG period Y (or HARQ process ID Y).

[0270] (i) Indicate one or more "k" values and an indication of "used" or "unused" for each CG PUSCH occasion (e.g., indicate a bitmap or the number of k values).

[0271] 4) Indicate whether to use CG PUSCH occasion X + k in CG cycle Y + m (or HARQ process ID Y + m).

[0272] (i) Indicate not to use CG PUSCH occasion X + k through the HARQ process ID in UCI or MAC CE.

[0273] The "k" value can indicate the used / unused CG PUSCH occasions of different HARQ process IDs.

[0274] (ii) Indicate CG cycle Y + m (or HARQ process ID Y + m) through UCI.

[0275] According to the indication, all CG PUSCH occasions of CG cycle Y + m (or HARQ process ID Y + m) can be used or not used.

[0276] 5) Whether to use CG PUSCH occasion X + k of CG cycle Y + m (or HARQ process ID Y + m) of CG configuration Z + n can be indicated by at least one of the following:

[0277] (i) Indicate not to use CG PUSCH occasion X + k by indicating CG configuration Z + n via UCI or MAC CE.

[0278] The indication of the used CG PUSCH occasion X of CG cycle Y + m (or HARQ process ID Y + m) of CG configuration Z can represent the following:

[0279] - The "used" or "unused" status of each CG PUSCH occasion of CG configuration Z + n associated with the used CG PUSCH occasion X of CG cycle Y + m (or HARQ process ID Y + m) of CG configuration Z.

[0280] For example, when Z = 1 and n = 1 and 2, CG configurations 2 and 3 are associated with CG configuration 1. In this case, if CG configurations 1, 2, and 3 are all enabled, and UCI or MAC CE indicates to use a specific CG PUSCH occasion of CG configuration 1, the UE determines whether to use the CG PUSCH occasions of associated CG configurations 2 and 3. If CG configuration 4 that is not connected to CG configuration 1 is enabled, it may not be possible to determine whether to use any CG PUSCH occasions of CG configuration 4 based on whether to use a specific CG PUSCH occasion in CG configuration 1. In other words, this operation can only be applied to connected CG configurations.

[0281] Alternatively, this operation can be applied between all enabled CG configurations regardless of their connection status.

[0282] (ii) Indicate CG configuration Z + n via UCI or MAC CE.

[0283] All CG PUSCH opportunities of CG configuration Z + n can be used or not used according to the indication.

[0284] - For example, when Z = 1 and n = 1 and 2, CG configurations 2 and 3 are associated with CG configuration 1. In this case, if CG configurations 1, 2, and 3 are all enabled, and UCI or MAC CE indicates to use CG configuration 1 or a specific CG PUSCH opportunity of CG configuration 1, then the UE determines whether to use all CG PUSCH opportunities of the associated CG configurations 2 and 3. If CG configuration 4, which is not connected to CG configuration 1, is enabled, it may not be possible to determine whether to use all CG PUSCH opportunities of CG configuration 4 based on whether to use CG configuration 1 or a specific CG PUSCH opportunity of CG configuration 1. In other words, this operation can only be applied to connected CG configurations.

[0285] - Alternatively, this operation can be applied between all enabled CG configurations regardless of their connection status.

[0286] (3) Option 1C: The UE always sends UCI for each CG PUSCH resource / opportunity.

[0287] MAC PDUs can be sent together or not sent together on CG PUSCH resources / opportunities.

[0288] Alternatively, the UE always sends MAC CE for each CG PUSCH resource / opportunity. In this case, RLC PDUs can be sent together or not sent together on CG PUSCH resources / opportunities.

[0289] The UCI or MAC CE sent on CG PUSCH opportunity X indicates the transmission status of one or more associated CG PUSCH opportunities Y. In this case, X = Y, X > Y, or X < Y.

[0290] - A single UCI or a single MAC CE indicates the used / unused status of one CG PUSCH (see Option 1A and Option 1B).

[0291] - A single UCI or a single MAC CE indicates the used / unused status of multiple CG PUSCHs (see Option 1A and Option 1B).

[0292] (i) Indicate the used / unused status only for multiple CG PUSCHs of the same CG cycle of the same CG configuration.

[0293] (ii) For multiple CG cycles of the same CG configuration (or the same or different HARQ process IDs), multiple CG PUSCHs indicate the used / unused status.

[0294] (iii) For multiple CG cycles of different CG configurations (or the same or different HARQ process IDs), multiple CG PUSCHs indicate the used / unused status.

[0295] (4) Options 2 and 3: Dedicated UCI resources are allocated to send the unused CG indicator.

[0296] 1) When sending an unused CG indicator on dedicated UCI resources (e.g., dedicated PUCCH resources for unused CG indicators), the UE can allocate dedicated UCI resources according to one of the following options based on the configuration of the BS:

[0297] (i) Option 2A: For each CG configuration, allocate UCI resources for one or more CG PUSCH occasions.

[0298] (ii) Option 2B: For each CG configuration, allocate one or more UCI resources for each CG cycle.

[0299] - In this case, the UCI can indicate the unused CG indicator and the HARQ process ID together.

[0300] (iii) Option 2C: Allocate one or more UCI resources for multiple CG configurations.

[0301] - In this case, the UCI can indicate the unused CG indicator and the CG configuration index and / or HARQ ID.

[0302] 2) The UE can allocate UCI resources according to the above Option 2A, 2B, or 2C and the following Option 3A, 3B, or 3C.

[0303] (i) Option 3A: Allocate UCI resources to the same symbol as the CG PUSCH based on frequency division multiplexing (FDM).

[0304] (ii) Option 3B: Allocate UCI resources to a symbol different from the CG PUSCH based on time division multiplexing (TDM).

[0305] - In this case, the UCI resources can be allocated to a specific symbol in the same time slot as the CG PUSCH (e.g., the first / last symbol of the time slot determined by RRC).

[0306] - Alternatively, UCI resources can be allocated to the previous time slot of the CG PUSCH. For example, the last symbol of the Nth time slot before the CG PUSCH time slot determined by RRC can be allocated for UCI transmission (where N is a positive integer).

[0307] (iii) Option 3C: Allocate UCI resources to symbols different from the CG PUSCH based on FDM.

[0308] The unused CG indicator sent on the dedicated UCI resource can be provided according to the above Option 1A, 1B or 1C.

[0309] For example, the UE can send the unused CG indicator by combining the dedicated UCI (e.g., dedicated PUCCH) and Option 1A.

[0310] - In this case, only the first PUSCH within the CG period is configured to be associated with the dedicated PUCCH, and the UE can send the unused CG indicator according to Option 1A. The first PUSCH may or may not be actually transmitted. Even if the first PUSCH is not transmitted, the UE can send or not send the dedicated UCI.

[0311] - Alternatively, all PUSCH opportunities in a specific CG period can be configured to be associated with the dedicated UCI resource, and the UE can send the unused CG indicator according to Option 1A.

[0312] (5) Option 4: The unused CG PUSCH is used for other logical channel data transmissions without sending an unused CG indicator.

[0313] In the above method, a specific CG configuration can be mapped to one or more logical channels. In this case, the UE MAC needs to configure the MAC PDU only using the data from the logical channels mapped to the CG PUSCH resources in the specific CG configuration.

[0314] 1) Option 4A: In the above method, for the CG PUSCH opportunity of a specific CG configuration, if there is (temporarily) no data from the logical channels mapped to the specific CG configuration, the UE determines that the corresponding CG PUSCH opportunity is unused, and (according to one or more options) the UE can send an unused CG indicator indicating the unused state, or the UE may not send an unused CG indicator indicating the used state. Alternatively, for the CG PUSCH opportunity of a specific CG configuration, if there is data from the logical channels mapped to the specific CG configuration, the UE determines that the corresponding CG PUSCH opportunity is used, and (according to one or more options) the UE may not send an unused CG indicator indicating the unused state, or the UE can send an unused CG indicator indicating the used state.

[0315] 2) Option 4B: In the above method, for the CG PUSCH occasion of a specific CG configuration, if there is (temporarily) no data from the logical channel mapped to the specific CG configuration, the UE determines that the corresponding CG PUSCH occasion is unused. In this case, if there is data from a logical channel not mapped to the specific CG configuration, or if there is a specific UL MAC CE to be sent, the UE may configure a MAC PDU including the data from the logical channel not mapped to the specific CG configuration and / or the specific UL MAC CE, and then uplink transmit the MAC PDU at the corresponding CG PUSCH occasion.

[0316] The priority of a specific logical channel not mapped to a specific CG configuration may be higher than that of the logical channel mapped to the specific CG configuration. Alternatively, the priority of a specific logical channel not mapped to a specific CG configuration may be equal to, higher than, or lower than a specified priority.

[0317] The priority of a specific UL MAC CE may be higher than that of the logical channel mapped to the specific CG configuration. Alternatively, regardless of the priority, if there is no data from the logical channel mapped to the specific CG configuration, the specific UL MAC CE may be included in the MAC PDU. Alternatively, regardless of the priority and regardless of whether there is data from the logical channel mapped to the specific CG configuration, the specific UL MAC CE may be included in the MAC PDU.

[0318] In this case, regardless of the used or unused status (according to one or more options), the UE may not send an unused CG indicator to the BS. Alternatively, the UE may send an unused CG indicator indicating the unused status, or may not send an unused CG indicator indicating the used status (according to one or more options). Alternatively, the UE may not send an unused CG indicator indicating the unused status, or may send an unused CG indicator indicating the used status (according to one or more options).

[0319] Hereinafter, reference will be made together to Figure 8 and Figure 9 Describe an implementation example of a method for indicating used / unused CG-PUSCH occasions according to Option 1 (Option 1A and Option 1B).

[0320] Refer to Figure 8, the UE can receive a CG configuration (A05) from the BS. According to the CG configuration, the first CG-PUSCH occasion (#n), the second CG-PUSCH occasion (#n+1), the third CG-PUSCH occasion (#n+2), the fourth CG-PUSCH occasion (#n+3), the fifth CG-PUSCH occasion (#n+4), etc. can be configured. The CG configuration may include configuration information indicating whether the UE reports the use of subsequent CG-PUSCH occasions for each CG-PUSCH transmission.

[0321] The UE can send a first CG-PUSCH (A10) including a first UCI at the first CG-PUSCH occasion. The first UCI may include a first bitmap. The first bitmap may include bits indicating whether to perform CG-PUSCH transmission at subsequent CG-PUSCH occasions of the first CG-PUSCH occasion. For example, the first bitmap may include 0101..., which means that CG-PUSCH transmission can be performed at the second CG-PUSCH occasion (#n+1) and the fourth CG-PUSCH occasion (#n+3), but not at the third CG-PUSCH occasion (#n+2) and the fifth CG-PUSCH occasion (#n+4).

[0322] The UE can send a second CG-PUSCH (A15) including a second UCI at the second CG-PUSCH occasion. The second UCI may include a second bitmap. The second bitmap may include bits indicating whether to perform CG-PUSCH transmission at subsequent CG-PUSCH occasions of the second CG-PUSCH occasion. For example, the second bitmap may include 101..., which means that CG-PUSCH transmission can be performed at the fourth CG-PUSCH occasion (#n+3), but not at the third CG-PUSCH occasion (#n+2) and the fifth CG-PUSCH occasion (#n+4).

[0323] The UE may not perform CG-PUSCH transmission at the third CG-PUSCH occasion, and it is reported through the first UCI and the second UCI that CG-PUSCH transmission will not be performed. On the other hand, the UE can perform CG-PUSCH transmission at the fourth CG-PUSCH occasion.

[0324] Figure 10 It is a diagram for explaining the signal transmission of the UE according to an embodiment.

[0325] Refer to Figure 10 , the UE can receive a CG configuration (B05) sent for UL.

[0326] The UE may transmit a first PUSCH (B10) including a first UCI at a first CG-PUSCH occasion among the CG-PUSCH occasions related to the CG configuration.

[0327] The first UCI may include information indicating whether the UE does not transmit a second PUSCH at a second CG-PUSCH occasion after the first CG-PUSCH occasion.

[0328] The information indicating whether the UE does not transmit the second PUSCH is a bitmap, and the bits of the bitmap may be associated with a specific number of CG-PUSCH occasions after the first CG-PUSCH occasion.

[0329] Each bit of the bitmap may be set to a first value indicating that PUSCH transmission is to be performed at the associated CG-PUSCH occasion or a second value indicating that PUSCH transmission is not to be performed. The first value may be 0 and the second value may be 1.

[0330] Based on the first UCI indicating that the UE is to transmit a second PUSCH at the second CG-PUSCH occasion, the UE may transmit the second PUSCH at the second CG-PUSCH occasion.

[0331] The second PUSCH includes a second UCI, and the second UCI may include information indicating whether the UE is to transmit a third PUSCH at a third CG-PUSCH occasion after the second CG-PUSCH occasion.

[0332] Based on the first UCI indicating that the UE does not transmit the third PUSCH at the third CG-PUSCH occasion, the second UCI may also indicate that the UE does not transmit the third PUSCH at the third CG-PUSCH occasion.

[0333] The UE may report whether to use subsequent CG-PUSCH occasions for each CG-PUSCH transmission based on the CG configuration.

[0334] The CG configuration may include configuration information indicating whether the UE reports whether to use subsequent CG-PUSCH occasions for each CG-PUSCH transmission.

[0335] Figure 11 It is a diagram for explaining signal reception of the BS according to an embodiment.

[0336] Refer to Figure 11 , the BS may transmit a CG configuration (C05) for UL reception.

[0337] The BS may receive a first PUSCH (C10) including a first UCI at a first CG-PUSCH occasion among the CG-PUSCH occasions related to the CG configuration.

[0338] The first UCI may include information indicating whether to receive a second PUSCH at a second CG-PUSCH occasion after the first CG-PUSCH occasion.

[0339] The information indicating whether to receive the second PUSCH is a bitmap, and the bits of the bitmap may be associated with a specific number of CG-PUSCH occasions after the first CG-PUSCH occasion.

[0340] Each bit of the bitmap may be set to a first value indicating that PUSCH reception is to be performed at the associated CG-PUSCH occasion or a second value indicating that PUSCH reception is not to be performed. The first value may be 0 and the second value may be 1.

[0341] Based on the first UCI indicating that the second PUSCH is to be received at the second CG-PUSCH occasion, the BS may receive the second PUSCH at the second CG-PUSCH occasion.

[0342] The second PUSCH includes a second UCI, and the second UCI may include information indicating whether to receive a third PUSCH at a third CG-PUSCH occasion after the second CG-PUSCH occasion.

[0343] For each CG-PUSCH reception based on the CG configuration, it may be received whether to use a subsequent CG-PUSCH occasion.

[0344] The CG configuration may include configuration information indicating whether the UE reports whether to use a subsequent CG-PUSCH occasion for each CG-PUSCH transmission.

[0345] The various details, functions, procedures, proposals, methods, and / or operation flowcharts described in this document may be applied to various fields (e.g., 5G) that require wireless communication / functions between devices.

[0346] Hereinafter, a detailed description will be given with reference to the drawings. In the following drawings / description, unless otherwise specified, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or functional blocks.

[0347] Figure 12 A communication system 1 to which the present disclosure is applied is shown.

[0348] Refer to Figure 12, the communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Herein, the wireless device represents a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or Long-Term Evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a TV, a smart phone, a computer, a wearable device, a home appliance device, a digital sign, a vehicle, a robot, etc. The handheld device may include a smart phone, a smart board, a wearable device (e.g., a smart watch or smart glasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include sensors and smart meters. For example, the BS and the network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0349] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. The AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other through the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0350] Wireless communication / connections 150a, 150b, or 150c can be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Herein, wireless communication / connections can be established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device can send / receive radio signals to / from each other via wireless communication / connections 150a and 150b. For example, wireless communication / connections 150a and 150b can send / receive signals via various physical channels. To this end, at least a part of the various configuration information configuring processes for sending / receiving radio signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes can be executed based on various proposals of the present disclosure.

[0351] Figure 13 Shows a wireless device applicable to the present disclosure.

[0352] Referring to Figure 13 , the first wireless device 100 and the second wireless device 200 can send radio signals via various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} can correspond to Figure 12 {wireless device 100x and BS200} and / or {wireless device 100x and wireless device 100x}.

[0353] 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 descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit radio signals including the first information / signals through the transceiver 106. The processor 102 may receive radio signals including second information / signals through the transceiver 106, and then store the information obtained by processing the second information / signals 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 part or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with the radio frequency (RF) unit. In this disclosure, the wireless device may represent a communication modem / circuit / chip.

[0354] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit radio signals including the third information / signals through the transceiver 206. The processor 202 may receive radio signals including fourth information / signals through the transceiver 206, and then store the information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for executing part or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with the RF unit. In this disclosure, the wireless device may represent a communication modem / circuit / chip.

[0355] In the following, the hardware components of wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (such as functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate signals (such as baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (such as baseband signals) from one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document.

[0356] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processor devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. The firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and / or command sets.

[0357] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, register, cache memory, computer-readable storage medium, and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various techniques such as wired or wireless connections.

[0358] One or more transceivers 106 and 206 may send user data, control information, and / or radio signals / channels mentioned in the methods and / or operational flowcharts of this document to one or more other devices. One or more transceivers 106 and 206 may receive descriptions, functions, processes, proposals, methods, and / or user data, control information, and / or radio signals / channels mentioned in the operational flowcharts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may execute controls such that one or more transceivers 106 and 206 may send user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may execute controls such that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert the received radio signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0359] Figure 14 Another example of a wireless device applied to the present disclosure is shown. The wireless device may be implemented in various forms according to usage / service (refer to Figure 12 ).

[0360] Refer to Figure 14 , the wireless devices 100 and 200 may correspond to Figure 13Wireless devices 100 and 200, and can be configured by various components, assemblies, units / parts, and / or modules. For example, each of wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 13 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Figure 13 One or more transceivers 106 and 206 and / or one or more antennas 108 and 208. The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operations of the wireless device based on programs / codes / commands / information stored in the memory unit 130. The control unit 120 may send the information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store the information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0361] The additional components 140 may be configured differently according to the type of the wireless device. For example, the additional components 140 may include at least one of a power unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be implemented as (but not limited to) a robot ( Figure 12 of 100a), a vehicle ( Figure 12 of 100b-1 and 100b-2), an XR device ( Figure 12 of 100c), a handheld device ( Figure 12 of 100d), a household appliance ( Figure 12 of 100e), an IoT device ( Figure 12 of 100f), a digital broadcast terminal, a holographic device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device ( Figure 12 of 400), a BS ( Figure 12 of 200), a network node, etc. The wireless device may be used in a mobile or fixed location according to usage examples / services.

[0362] In Figure 14In this case, various elements, components, units / parts, and / or modules in the wireless devices 100 and 200 can all be connected to each other through a wired interface, or at least a part of them can be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 can be wired-connected, and the control unit 120 and the first units (e.g., 130 and 140) can be wirelessly connected through the communication unit 110. Each element, component, unit / part, and / or module within the wireless devices 100 and 200 can also include one or more elements. For example, the control unit 120 can be configured by a set of one or more processors. As an example, the control unit 120 can be configured by a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory 130 can be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0363] Figure 15 Illustrates a vehicle or an autonomous driving vehicle to which the present disclosure is applied. The vehicle or the autonomous driving vehicle can be implemented by a mobile robot, an automobile, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0364] Referring to Figure 15 , the vehicle or the autonomous driving vehicle 100 can include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 can be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d respectively correspond to Figure 14 blocks 110 / 130 / 140 of

[0365] The communication unit 110 may transmit signals (e.g., data and control signals) to and receive signals from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous driving vehicle 100. The control unit 120 may include an electronic control unit (ECU). The driving unit 140a may cause the vehicle or autonomous driving vehicle 100 to travel on a road. The driving unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100 and includes a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may acquire vehicle state, surrounding environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a depth sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement technologies for maintaining the lane in which the vehicle is traveling, for automatically adjusting the speed (e.g., adaptive cruise control), for autonomously traveling along a determined path, for traveling by automatically setting a path if a destination is set, etc.

[0366] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 may control the driving unit 140a so that the vehicle or autonomous driving vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 may acquire the latest traffic information data from the external server non-periodically / periodically and acquire surrounding traffic information data from neighboring vehicles. During autonomous driving, the sensor unit 140c may obtain the vehicle state and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and the driving plan based on the newly obtained data / information. The communication unit 110 may transmit information about the vehicle position, the autonomous driving path, and / or the driving plan to the external server. The external server may use AI technology, etc. to predict traffic information data based on the information collected from the vehicle or autonomous driving vehicle and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0367] Figure 16 is a diagram illustrating a discontinuous reception (DRX) operation of a UE according to an embodiment of the present disclosure.

[0368] The UE can perform DRX operations in the processes and / or methods described / proposed above. The UE configured with DRX can reduce power consumption by receiving DL signals discontinuously. DRX can be performed in the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. The UE performs DRX in the RRC_IDLE state and RRC_INACTIVE state to receive paging signals discontinuously. The DRX in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.

[0369] Referring to Figure 16 , the DRX cycle includes an on-duration and a DRX opportunity. The DRX cycle defines the time interval between the periodic repetitions of the on-duration. The on-duration is the time period during which the UE monitors the PDCCH. When the UE is configured with DRX, the UE performs PDCCH monitoring during the on-duration. When the UE successfully detects the PDCCH during PDCCH monitoring, the UE starts an inactivity timer and remains awake. On the contrary, when the UE fails to detect any PDCCH during PDCCH monitoring, the UE transitions to the sleep state after the on-duration. Therefore, when DRX is configured, PDCCH monitoring / reception can be performed discontinuously in the time domain in the processes and / or methods described / proposed above. For example, when DRX is configured, the PDCCH reception timing (e.g., the time slot with PDCCH SS) can be configured discontinuously according to the DRX configuration in the present disclosure. On the contrary, when DRX is not configured, PDCCH monitoring / reception can be performed continuously in the time domain. For example, when DRX is not configured, the PDCCH reception timing (e.g., the time slot with PDCCH SS) can be configured continuously in the present disclosure. Regardless of whether DRX is configured, PDCCH monitoring can be restricted during the time period configured as a measurement gap.

[0370] Table 6 describes the DRX operations of the UE (in the RRC_CONNECTED state). Referring to Table 6, the DRX configuration information is received through higher layer signaling (e.g., RRC signaling), and the DRX on / off is controlled by a DRX command from the MAC layer. Once DRX is configured, the UE can perform PDCCH monitoring discontinuously when executing the processes and / or methods described / proposed above.

[0371] [Table 6]

[0372]

[0373] MAC-CellGroupConfig includes the configuration information required to configure MAC parameters for a cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, when defining DRX, MAC-CellGroupConfig may include the following information. - The value of drx-OnDurationTimer: Defines the duration of the starting period of a DRX cycle.

[0374] - The value of drx-InactivityTimer: Defines the duration of the time period during which the UE wakes up after detecting a PDCCH occasion of a PDCCH indicating initial UL or DL data.

[0375] - The value of drx-HARQ-RTT-TimerDL: Defines the duration of the maximum time period from receiving a DL initial transmission until receiving a DL retransmission.

[0376] - The value of drx-HARQ-RTT-TimerUL: Defines the duration of the maximum time period from receiving a UL initial transmission grant until receiving a UL retransmission grant.

[0377] - drx-LongCycleStartOffset: Defines the duration and start time of a DRX cycle.

[0378] - drx-ShortCycle (optional): Defines the duration of a short DRX cycle.

[0379] When any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL is running, the UE performs PDCCH monitoring at each PDCCH occasion and remains in the wake-up state.

[0380] The above embodiments correspond to combinations of elements and features of the present disclosure in a prescribed form. And, unless explicitly mentioned, each element or feature can be regarded as selective. Each element or feature can be implemented in a form that does not combine with other elements or features. In addition, embodiments of the present disclosure can be implemented by partially combining elements and / or features. The operation sequence described for each embodiment of the present disclosure can be modified. Some configurations or features of one embodiment can be included in another embodiment, or can replace the corresponding configurations or features of another embodiment. And, it is obvious and understandable that embodiments are configured by combining claims that do not have an explicit citation relationship in the appended claims, or can be included as new claims by modification after filing an application.

[0381] Those skilled in the art will understand that the present disclosure may be implemented in other specific forms than those set forth herein without departing from the spirit and basic characteristics of the present disclosure. Accordingly, the above-described embodiments should be construed in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the above description, and all changes falling within the meaning and scope of the appended claims are intended to be covered therein.

[0382] Industrial Applicability

[0383] The present disclosure is applicable to UEs, BSs or other devices in a wireless mobile communication system.

Claims

1. A method for a user equipment (UE) to transmit a signal in a wireless communication system, the method comprises the following steps: receiving a configuration grant (CG) configuration for uplink transmission; and transmitting a first physical uplink shared channel (PUSCH) including a first uplink control information (UCI) at a first CG-PUSCH occasion among CG-PUSCH occasions related to the CG configuration, wherein the first UCI includes information indicating whether the UE does not transmit a second PUSCH at a second CG-PUSCH occasion after the first CG-PUSCH occasion, wherein the information indicating whether the UE does not transmit the second PUSCH is a bitmap, and wherein bits of the bitmap are respectively associated with a predetermined number of CG-PUSCH occasions after the first CG-PUSCH occasion.

2. The method according to claim 1, wherein each bit of the bitmap is set to a first value indicating that PUSCH transmission is to be performed at an associated CG-PUSCH occasion or a second value indicating that the PUSCH transmission is not to be performed at the associated CG-PUSCH occasion.

3. The method according to claim 2, wherein the first value is 0, and wherein the second value is 1.

4. The method according to claim 1, the method further comprises the following steps: based on the first UCI indicating that the UE transmits the second PUSCH at the second CG-PUSCH occasion, transmitting the second PUSCH at the second CG-PUSCH occasion, wherein the second PUSCH includes a second UCI, and wherein the second UCI includes information indicating whether the UE is to transmit a third PUSCH at a third CG-PUSCH occasion after the second CG-PUSCH occasion.

5. The method according to claim 4, wherein based on the first UCI indicating that the UE does not transmit the third PUSCH at the third CG-PUSCH occasion, the second UCI also indicates that the UE does not transmit the third PUSCH at the third CG-PUSCH occasion.

6. The method according to claim 1, wherein the UE reports whether subsequent CG-PUSCH occasions are used for each CG-PUSCH transmission based on the CG configuration.

7. The method according to claim 1, wherein the CG configuration includes configuration information indicating whether the UE reports whether subsequent CG-PUSCH occasions are used for each CG-PUSCH transmission.

8. A computer-readable recording medium having recorded thereon a program for executing the method according to claim 1.

9. An apparatus for wireless communication, the apparatus comprises: a memory configured to store instructions; and a processor configured to perform operations by executing the instructions, wherein the operations of the processor include: receiving a configuration grant (CG) configuration for uplink transmission; and Transmit a first physical uplink shared channel (PUSCH) including a first uplink control information (UCI) at a first CG-PUSCH occasion among CG-PUSCH occasions related to the CG configuration. Wherein, the first UCI includes information indicating whether to refrain from transmitting a second PUSCH at a second CG-PUSCH occasion after the first CG-PUSCH occasion. Wherein, the information indicating whether to refrain from transmitting the second PUSCH is a bitmap, and wherein, bits of the bitmap are respectively associated with a predetermined number of CG-PUSCH occasions after the first CG-PUSCH occasion.

10. The apparatus according to claim 9, further comprising a transceiver, wherein, the apparatus is a user equipment (UE) operating in a wireless communication system.

11. The apparatus according to claim 9, wherein, the apparatus is a processing device configured to control a user equipment (UE) operating in a wireless communication system.

12. A method for a base station (BS) to receive signals in a wireless communication system, the method comprising the steps of: transmitting a configuration grant (CG) configuration for uplink reception; and receiving a first PUSCH including a first uplink control information (UCI) at a first CG-PUSCH occasion among CG-PUSCH occasions related to the CG configuration, wherein, the first UCI includes information indicating whether to refrain from receiving a second PUSCH at a second CG-PUSCH occasion after the first CG-PUSCH occasion, wherein, the information indicating whether to refrain from receiving the second PUSCH is a bitmap, and wherein, bits of the bitmap are respectively associated with a predetermined number of CG-PUSCH occasions after the first CG-PUSCH occasion.

13. A computer-readable recording medium having recorded thereon a program for executing the method according to claim 12.

14. A base station (BS) for wireless communication, the BS comprising: a memory configured to store instructions; and a processor configured to perform operations by executing the instructions, wherein, the operations of the processor include: transmitting a configuration grant (CG) configuration for uplink reception; and receiving a first PUSCH including a first uplink control information (UCI) at a first CG-PUSCH occasion among CG-PUSCH occasions related to the CG configuration, wherein, the first UCI includes information indicating whether to refrain from receiving a second PUSCH at a second CG-PUSCH occasion after the first CG-PUSCH occasion, wherein, the information indicating whether to refrain from receiving the second PUSCH is a bitmap, and wherein, bits of the bitmap are respectively associated with a predetermined number of CG-PUSCH occasions after the first CG-PUSCH occasion.

Images