Method for transmitting uplink signals, user equipment, processing device and storage medium, and method for receiving uplink signals and base station

Abstract

The UE receives a configured grant (CG) configuration; and, based on the CG configuration, can transmit a first CG PUSCH including uplink transmission occasion uplink control information (UTO-UCI) at a first CG PUSCH occasion. The UTO-UCI includes an N-bit bitmap, where N bits of the N-bit bitmap are one-to-one mapped to N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion, and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

Description

[Technical Field]

[0001] The present invention relates to wireless communication systems. [Background technology]

[0002] Various devices and technologies, such as smartphones and tablet PCs (Personal Computers), which require high data transmission rates, including machine-to-machine (MtoM, MM, M2M) communication and machine-type communication (MTC), have emerged and become widespread. Accordingly, the amount of data required to be processed by cellular networks has also increased dramatically. To meet this rapidly increasing data processing demand, technologies such as carrier aggregation and cognitive radio, which allow for the efficient use of more frequency bands, and multiple antenna and multiple BS coordination technologies, which increase the data capacity transmitted within limited frequencies, are being developed.

[0003] As a large number of communication devices require larger communication capacity, there is a growing need for enhanced mobile broadband (eMBB) communication, which is superior to legacy radio access technology (RAT).In addition, massive machine type communications (mMTC), which connects multiple devices and objects to provide a variety of services anytime, anywhere, is being considered as the next generation of communication.

[0004] Furthermore, communication systems designed for services / user equipment (UE) that are sensitive to reliability and latency are also being considered. The introduction of next-generation wireless access technologies is being discussed, including eMBB communication, mMTC, and ultra-reliable and low latency communication (URLLC). Summary of the Invention [Problem to be solved by the invention]

[0005] There is a need for a method for efficiently transmitting data packets in a wireless communication system where jitter may occur.

[0006] A method is required that minimizes radio resource waste based on semi-persistent scheduling or configured grants.

[0007] A method is required to efficiently report to the BS whether the UE is actually using the scheduled radio resources.

[0008] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the examples of the present invention described below. [Means for solving the problem]

[0009] According to one aspect of the present invention, there is provided a method for transmitting an uplink signal by a user equipment (UE) in a wireless communication system. The method includes: receiving a configured grant (CG) configuration; and transmitting a first CG physical uplink shared channel (PUSCH) occasion based on the CG configuration, the first CG PUSCH including unused transmission occasion uplink control information (UTO-UCI). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are one-to-one mapped to the N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion, and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0010] Another aspect of the present invention provides a user equipment (UE) for transmitting uplink signals in a wireless communication system. The UE includes: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: receiving a configured grant (CG) configuration; and transmitting, based on the CG configuration, a first CG physical uplink shared channel (PUSCH) occasion containing unused transmission occasion uplink control information (UTO-UCI). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are one-to-one mapped to the N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion, and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0011] In yet another aspect of the present invention, a processing device is provided. The processing device includes: at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: receiving a configured grant (CG) setting; and transmitting, based on the CG setting, a first CG physical uplink shared channel (PUSCH) occasion including unused transmission occasion uplink control information (UTO-UCI). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are one-to-one mapped to the N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion, and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0012] According to another aspect of the present invention, there is provided a computer-readable storage medium having stored thereon at least one program code including instructions that, when executed, cause at least one processor to perform operations including: receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) occasion based on the CG setting, the first CG PUSCH occasion including unused transmission occasion uplink control information (UTO-UCI). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are one-to-one mapped to the N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion, and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0013] According to another aspect of the present invention, there is provided a method for a base station (BS) receiving an uplink signal from a user equipment (UE) in a wireless communication system. The method includes: transmitting a configured grant (CG) configuration; and receiving a first CG physical uplink shared channel (PUSCH) occasion based on the CG configuration, the first CG PUSCH occasion including unused transmission occasion uplink control information (UTO-UCI). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are one-to-one mapped to the N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion, and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0014] In yet another aspect of the present invention, there is provided a base station (BS) for receiving uplink signals from a user equipment (UE) in a wireless communication system. The BS includes: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: transmitting a configured grant (CG) configuration; and receiving, based on the CG configuration, a first CG physical uplink shared channel (PUSCH) occasion containing unused transmission occasion uplink control information (UTO-UCI) in a first CG PUSCH occasion. The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are one-to-one mapped to the N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion, and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0015] In each embodiment of the present invention, N is a value provided by higher layer signaling from the BS.

[0016] In each aspect of the invention, N is the value provided for the CG setting.

[0017] In each aspect of the present invention, the subsequent N CG PUSCH occasions to which the N bits of the N-bit bitmap are one-to-one mapped exclude invalid PUSCH occasions.

[0018] In each aspect of the present invention, the invalid CG PUSCH timing is a CG PUSCH timing that overlaps with a symbol indicated as uplink by the TDD uplink-downlink configuration (e.g., the RRC parameter tdd-UL-DL-ConfigurationCommon and / or the RRC parameter tdd-UL-DL-ConfigurationDedicated).

[0019] In each aspect of the present invention, the invalid CG PUSCH time is a CG PUSCH time that overlaps with a symbol of a synchronization signal / physical broadcast channel block (e.g., a symbol of an SS / PBCH block with an index provided by the RRC parameter ssb-PositionsInBurst).

[0020] In each aspect of the present invention, the method of the UE or the operation of the UE, the processing device, or the storage medium further includes: based on the presence of HARQ-ACK information to be transmitted in the first CG PUSCH occasion, jointly encoding the HARQ-ACK information and the UTO-UCI to obtain jointly coded bits, and mapping the jointly coded bits to the first CG PUSCH by rate matching.

[0021] In each aspect of the present invention, the method of the BS or the operations of the BS include: obtaining jointly coded bits for the HARQ-ACK information and the UTO-UCI on the first PUSCH based on the presence of HARQ-ACK information to be received at the first CG PUSCH occasion, and assuming that the jointly coded bits are mapped to the first CG PUSCH by rate matching.

[0022] In each aspect of the present invention, the method of the UE or the operation of the UE, the processing device or the storage medium includes: not transmitting a CG PUSCH in a CG PUSCH occasion mapped to a bit having a second value among the N bits.

[0023] In each aspect of the present invention, the method of the BS or the operation of the BS includes: not expecting to receive a CG PUSCH at a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

[0024] The above-described solutions to problems are merely some of the embodiments of the present invention, and various embodiments reflecting the technical features of the present invention will be understood by those skilled in the art from the detailed description of the present invention set forth below. [Effects of the Invention]

[0025] Some implementations of the present invention can reduce waste of radio resources reserved for data packets that may experience jitter.

[0026] According to some implementations of the present invention, radio resources based on the configured grant configuration can be used for other transmissions.

[0027] According to some embodiments of the present invention, the actual use or non-use of radio resources scheduled to a UE can be efficiently reported to a BS.

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

[0029] The following attached drawings are included as part of the detailed description to aid in understanding the present invention, and illustrate embodiments of the present invention and, together with the detailed description, explain the technical features of the present invention: [Figure 1] 1 shows an example of a communication system 1 to which the present invention is applied. [Figure 2] 1 is a block diagram showing an example of a communication device for carrying out a method according to the present invention; [Figure 3] 1 illustrates another example of a wireless device that may implement an embodiment of the present invention. [Figure 4] 1 shows an example of a frame structure that can be used in a wireless communication system based on the 3rd generation partnership project (3GPP: registered trademark; the same applies hereinafter). [Figure 5] 1 shows an example of a resource grid for slots. [Figure 6] 1 shows an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH. [Figure 7] 1 illustrates an example of a hybrid automatic repeat request-acknowledgement (HARQ-ACK) transmission / reception process. [Figure 8] 1 illustrates an example flow of UE operation according to some implementations of the present invention. [Figure 9] 1 illustrates an example flow of BS operation according to some implementations of the present invention. [Figure 10] 1 illustrates an example of a signal transmission / reception flow between a UE and a BS according to some embodiments of the present invention. [Figure 11] 1 illustrates an example of URI transmission according to some implementations of the present invention. [Figure 12] 1 illustrates an example of URI transmission according to some implementations of the present invention. [Figure 13] 1 illustrates an example of a flow of UE uplink signal transmission according to some embodiments of the present invention. [Figure 14] 1 illustrates an example of a flow chart of a BS receiving an uplink signal according to some embodiments of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0030] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention can be practiced. The detailed description below includes specific details to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention can be practiced without such specific details.

[0031] In some cases, in order to avoid obscuring the concept of the present invention, well-known structures and devices are omitted or shown in block diagram form focusing on the core functions of each structure and device. Furthermore, the same components are described throughout this specification with the same reference numerals.

[0032] The techniques, devices, and systems described below can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE) (i.e., GERAN). OFDMA can be implemented by wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved-UTRA), etc. UTRA is a part of UMTS (Universal Mobile Telecommunication System), and 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS that uses E-UTRA.3GPP LTE uses OFDMA for the downlink (DL) and SC-FDMA for the uplink (UL). LTE-advanced (LTE-A) is an evolved version of 3GPP LTE.

[0033] For convenience of explanation, the following description will be made assuming that the present invention is applied to a 3GPP-based communication system, such as LTE or NR. However, the technical features of the present invention are not limited thereto. For example, even if the following detailed description is based on a mobile communication system corresponding to the 3GPP LTE / NR system, matters specific to the 3GPP LTE / NR system may be applied to any other mobile communication system.

[0034] For terms and techniques used in this invention that are not specifically explained, please refer to 3GPP-based standard documents, such as 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300, 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.321, 3GPP TS 38.331, etc.

[0035] In the embodiments of the present invention described below, the expression that a device "assumes" means that an entity transmitting a channel transmits the channel in accordance with the corresponding "assumption." An entity receiving a channel receives or decodes the channel in a form in accordance with the corresponding "assumption," under the assumption that the channel was transmitted in accordance with the corresponding "assumption."

[0036] In the present invention, a UE may be stationary or mobile, and includes various devices that communicate with a base station (BS) to transmit and / or receive user data and / or various control information. A UE is also referred to as a terminal equipment (Terminal Equipment), a mobile station (MS), a mobile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, a personal digital assistant (PDA), a wireless modem, a handheld device, etc. In addition, in the present invention, a BS generally refers to a fixed station that communicates with a UE and / or other BSs, and communicates with the UE and other BSs to exchange various data and control information. A BS is also referred to as an advanced base station (ABS), a node-B (NB), an evolved-node-B (eNB), a base transceiver system (BTS), an access point, a processing server (PS), etc. In particular, a UTRAN base station is called a Node-B, an E-UTRAN base station is called an eNB, and a new radio access technology network base station is called a gNB. For ease of explanation, base stations will be collectively referred to as BSs hereinafter, regardless of the type or version of communication technology.

[0037] In the present invention, a node refers to a fixed point that can communicate with a UE and transmit / receive wireless signals. Various types of BSs can be used as nodes, regardless of their names. For example, a BS, NB, eNB, picocell eNB (PeNB), home eNB (HeNB), relay, repeater, etc. can be used as a node. A node does not have to be a BS. For example, a radio remote head (RRH) or a radio remote unit (RRU) can also be used. RRHs and RRUs generally have a lower power level than the BS. Since an RRH or RRU (hereinafter referred to as an RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between the RRH / RRU and the BS can be performed more smoothly than cooperative communication using a BS connected via a wireless line. At least one antenna is installed in each node. This antenna can refer to a physical antenna, an antenna port, a virtual antenna, or an antenna group. A node is also called a point.

[0038] In the present invention, a cell refers to a geographical area where one or more nodes provide communication services. Therefore, in the present invention, communicating with a specific cell refers to communicating with a BS or node providing communication services to the specific cell. Furthermore, a downlink / uplink signal of a specific cell refers to a downlink / uplink signal from / to a BS or node providing communication services to the specific cell. A cell providing uplink / downlink communication services to a UE is particularly referred to as a serving cell. Furthermore, a channel state / quality of a specific cell refers to the channel state / quality of a channel or communication link established between a BS or node providing communication services to the specific cell and the UE. In a 3GPP-based communication system, a UE can measure a downlink channel state from a specific node using a Cell-specific Reference Signal (CRS) transmitted on a CRS resource allocated to the specific node by an antenna port of the specific node and / or a Channel State Information Reference Signal (CSI-RS) transmitted on a CSI-RS resource.

[0039] Meanwhile, the 3GPP-based communication system uses the concept of a cell to manage radio resources, but a cell associated with a radio resource is distinct from a cell in a geographical area.

[0040] A "cell" of a geographical area can be understood as the coverage where a node can provide a service using a carrier, and a "cell" of radio resources relates to a bandwidth (BW), which is a frequency range configured by the carrier. Since downlink coverage, which is the range where a node can transmit a valid signal, and uplink coverage, which is the range where a valid signal can be received from a UE, depend on the carrier that carries the signal, the coverage of a node can also be related to the coverage of a "cell" of radio resources used by the node. Thus, the term "cell" can sometimes refer to the coverage of a service provided by a node, sometimes to a radio resource, and sometimes to the range where a signal using the radio resource can reach with effective strength.

[0041] Meanwhile, 3GPP communication standards use the concept of a cell to manage radio resources. A "cell" in relation to radio resources is defined as a combination of downlink (DL) resources and uplink (UL) resources, i.e., a combination of a DL component carrier (CC) and a UL CC. A cell can be configured with only DL resources or a combination of DL and UL resources. When carrier aggregation (CA) is supported, the linkage between the carrier frequency of DL resources (or DL ​​CC) and the carrier frequency of UL resources (or UL CC) can be indicated by system information. For example, the combination of DL and UL resources is indicated by System Information Block Type 2 (SIB2) linkage. Here, the carrier frequency may be the same as or different from the center frequency of each cell or CC. When carrier aggregation (CA) is configured, the UE has only one radio resource control (RRC) connection with the network. One serving cell provides non-access stratum (NAS) mobility information during RRC connection establishment / re-establishment / handover, and one serving cell provides security input during RRC connection re-establishment / handover. Such a cell is called a primary cell (Pcell). A Pcell is a cell operating on a primary frequency where a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. Depending on the UE capabilities, a secondary cell (Scell) can be configured to form a serving cell set together with the Pcell.An Scell ​​can be set up after RRC (Radio Resource Control) connection establishment and is a cell that provides additional radio resources in addition to the resources of a special cell (SPcell). In the downlink, a carrier corresponding to a Pcell is called a Downlink Primary CC (DL PCC), and in the uplink, a carrier corresponding to a Pcell is called a UL Primary CC (DL PCC). In the downlink, a carrier corresponding to an Scell ​​is called a DL Secondary CC (DL SCC), and in the uplink, a carrier corresponding to an Scell ​​is called a UL Secondary CC (UL SCC).

[0042] In dual connectivity (DC) operation, the term special cell (SpCell) refers to a Pcell in a master cell group (MCG) or a primary secondary cell (PSCell) in a secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based voluntary access and is always activated. An MCG is a group of serving cells associated with a master node (e.g., BS) and consists of an SpCell (Pcell) and optionally one or more Scells. For a UE configured for DC, an SCG is a subset of serving cells associated with a secondary node and consists of a primary secondary cell (PSCell) and zero or more Scells. A PSCell is the primary Scell ​​of an SCG. For a UE in RRC_CONNECTED state that is not configured for CA or DC, there is only one serving cell consisting of only a Pcell. For a UE in RRC_CONNECTED state configured in CA or DC, the term serving cell refers to the set of cells consisting of the SpCell and all Scells. In DC, two medium access control (MAC) entities are configured in the UE: one for the MCG and one for the SCG.

[0043] For a UE configured with CA but not configured with DC, a Pcell PUCCH group (also referred to as a primary PUCCH group) consisting of a Pcell and zero or more Scells, and an Scell ​​PUCCH group (also referred to as a secondary PUCCH group) consisting of only Scells are configured. In the case of an Scell, an Scell ​​(hereinafter referred to as a PUCCH cell) is configured to transmit a PUCCH associated with the cell. An Scell ​​for which a PUCCH Scell ​​is indicated belongs to the Scell ​​PUCCH group (i.e., the secondary PUCCH group), and PUCCH transmission of associated UCI is performed on the PUCCH Scell. An Scell ​​for which a PUCCH Scell ​​is not indicated or a cell indicated as a PUCCH transmission cell is a Pcell belongs to the Pcell PUCCH group (i.e., the primary PUCCH group), and PUCCH transmission of associated UCI is performed on the Pcell. Hereinafter, when a UE is configured with an SCG and some embodiments of the present invention related to PUCCH are applied to the SCG, a primary cell will refer to a PSCell of the SCG. When a UE is configured with a PUCCH Scell ​​and some embodiments of the present invention related to PUCCH are applied to a secondary PUCCH group, a primary cell refers to the PUCCH Scell ​​of the secondary PUCCH group.

[0044] In a wireless communication system, a UE receives information from a BS via a downlink (DL) and transmits information to a BS via an uplink (UL). The information transmitted and / or received by the BS and the UE includes data and various control information, and various physical channels exist depending on the type / purpose of the information transmitted and / or received.

[0045] The 3GPP infrastructure communication standard defines downlink physical channels corresponding to resource elements carrying information from higher layers and downlink physical signals corresponding to resource elements used by the physical layer but not carrying information from higher layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, and reference signals and synchronization signals (SS) are defined as downlink physical signals. A reference signal (RS), also called a pilot, refers to a signal with a predefined special waveform that is mutually known between the BS and UE. For example, a demodulation reference signal (DMRS) and a channel state information RS (CSI-RS) are defined as downlink reference signals. The 3GPP infrastructure communication standard defines uplink physical channels corresponding to resource elements carrying information from higher layers and uplink physical signals corresponding to resource elements used by the physical layer but not carrying information from higher layers. For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as uplink physical channels, and a demodulation reference signal (DMRS) for uplink control / data signals and a sounding reference signal (SRS) used for uplink channel measurement are also defined.

[0046] In this invention, a physical downlink control channel (PDCCH) refers to a set of time-frequency resources (e.g., resource elements (RE)) carrying downlink control information (DCI), and a physical downlink shared channel (PDSCH) refers to a set of time-frequency resources carrying downlink data. Furthermore, a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), and a physical random access channel (PRACH) refer to sets of time-frequency resources carrying uplink control information (UCI), uplink data, and optional access signals, respectively. Hereinafter, the expressions "user equipment transmits / receives PUCCH / PUSCH / PRACH" are used interchangeably to mean "transmitting / receiving uplink control information / uplink data / optional access signals on or via PUCCH / PUSCH / PRACH," respectively. Furthermore, the expression that a BS transmits / receives a PBCH / PDCCH / PDSCH is used interchangeably with the expression that a BS transmits broadcast information / downlink control information / downlink data on or through the PBCH / PDCCH / PDSCH, respectively.

[0047] In this invention, the radio resources (eg, time-frequency resources) scheduled or configured by the BS to the UE for transmitting or receiving the PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.

[0048] Because a communication device receives a synchronization signal block (SSB), DMRS, CSI-RS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of a radio signal in a cell, it cannot selectively receive a radio signal including only a specific physical channel or specific physical signal using an RF receiver, or selectively receive a radio signal excluding only a specific physical channel or physical signal using an RF receiver. In actual operation, the communication device first receives a radio signal in a cell using an RF receiver, converts the RF band signal into a baseband signal, and decodes the physical signal and / or physical channel in the baseband signal using one or more processors. Therefore, in some embodiments of the present invention, receiving a physical signal and / or physical channel does not actually mean that the communication device never receives a radio signal including the corresponding physical signal and / or physical channel, but rather means that the communication device does not attempt to recover the physical signal and / or physical channel from the radio signal, e.g., does not attempt to decode the physical signal and / or physical channel.

[0049] As more communication devices require greater communication capacity, there is a growing need for improved mobile broadband communications compared to existing radio access technologies (RATs). Furthermore, massive machine-type communications (mMTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is becoming a major issue in next-generation communications. Furthermore, communication system designs that take into account reliability- and latency-sensitive services / UEs are also being considered. The introduction of next-generation RATs that take into account advanced mobile broadband communications, mMTC, and Ultra-Reliable and Low Latency Communication (URLLC), is currently under discussion. 3GPP is currently conducting research on next-generation mobile communication systems beyond EPC. For convenience, this specification refers to the relevant technologies as new RATs (NR) or 5G RATs, and systems that use or support NR as NR systems.

[0050] FIG. 1 illustrates an example of a communication system 1 to which the present invention is embodied. Referring to FIG. 1, the communication system 1 to which the present invention is embodied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that communicates using a wireless connection technology (e.g., 5G NR, LTE (e.g., E-UTRA)), and is also referred to as a communication / wireless / 5G device. The wireless device includes, but is not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an XR (eXtended Reality) device 100c, a handheld device 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI device / server 400. For example, the vehicle includes a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of vehicle-to-vehicle communication, and the like. Here, the vehicle includes an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices include Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR) devices, and are embodied in the form of Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) mounted on vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital billboards, vehicles, robots, etc. Mobile devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, etc.), etc. Home appliances include TVs, refrigerators, washing machines, etc. IoT devices include sensors, smart meters, etc. For example, BSs and networks can also be embodied in wireless devices, and certain wireless devices can act as BS / network nodes for other wireless devices.

[0051] The wireless devices 100a to 100f are connected to a network 300 via a BS 200. Artificial Intelligence (AI) technology is applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f are connected to an AI server 400 via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the BS 200 / network 300, but can also communicate directly without going through the BS / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). IoT devices (e.g., sensors) can also communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0052] Wireless communication / connections 150a, 150b are performed between the wireless devices 100a-100f / BSs 200 and the wireless devices 100a-100f. Here, the wireless communication / connections are performed using various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication). The wireless communication / connections 150a, 150b enable the wireless devices and the BSs / wireless devices to transmit / receive wireless signals to / from each other. For example, according to various proposals of the present invention, any of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes are performed.

[0053] 2 is a block diagram showing an example of a communication device that performs a method according to the present invention. Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 transmit and / or receive wireless signals using various wireless access technologies (e.g., LTE, NR). Here, {first wireless device 100, second wireless device 200} corresponds to {wireless device 100x, BS 200} and / or {wireless device 100x, wireless device 100x} in FIG. 1.

[0054] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 is configured to control the memory 104 and / or the transceiver 106 to implement the functions, procedures, and / or methods described / suggested below. For example, the processor 102 processes information in the memory 104 to generate first information / signals, and then transmits a wireless signal including the first information / signals via the transceiver 106. The processor 102 also receives a wireless signal including second information / signals via the transceiver 106, and then stores information obtained from signal processing of the second information / signals in the memory 104. The memory 104 is coupled to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing some or all of the processes controlled by the processor 102 or for performing the procedures and / or methods described / suggested below. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (radio frequency) unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0055] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 is configured to control the memory 204 and / or the transceiver 206 to implement the functions, procedures, and / or methods described / suggested below. For example, the processor 202 processes information in the memory 204 to generate third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including fourth information / signal via the transceiver 206, and then stores information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for performing the procedures and / or methods described / suggested below. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0056] The wireless communication technology implemented in the wireless devices 100 and 200 of the present invention includes not only LTE, NR, and 6G, but also NB-IoT (Narrowband Internet of Things) for low-power communication. Here, for example, the NB-IoT technology is an example of LPWAN (Low Power Wide Area Network) technology and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices XXX and YYY of the present invention performs communication based on LTE-M technology. Here, for example, the LTE-M technology is an example of LPWAN technology and is referred to by various names such as eMTC (enhanced Machine Type Communication). For example, the LTE-M technology may be implemented in any of various standards such as 1) LTE CAT0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices XXX and YYY of the present invention may include any of ZigBee, Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which consider low-power communication, but are not limited to the above names. For example, ZigBee technology creates personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and is called by various names.

[0057] The hardware elements of the wireless devices 100, 200 will be described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, the one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). The one or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the functions, procedures, suggestions, and / or methods disclosed herein. The one or more processors 102, 202 generate messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed in the present invention. The one or more processors 102, 202 generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed in the present invention, and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed in the present invention.

[0058] The one or more processors 102, 202 may also be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. For example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The functions, procedures, suggestions, and / or methods disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, suggestions, and / or methods disclosed herein may be included in the one or more processors 102, 202 or may be stored in one or more memories 104, 204 and executed by the one or more processors 102, 202. The functions, procedures, suggestions and / or methods disclosed in this invention may be embodied using firmware or software in the form of code, instructions and / or sets of instructions.

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

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

[0061] FIG. 3 shows another example of a wireless device for implementing an embodiment of the present invention. Referring to FIG. 3, wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 2 and are composed of various elements, components, units / sections, and / or modules. For example, the wireless devices 100 and 200 include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102 and 202 and / or one or more memories 104 and 204 of FIG. 2. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional component 140 and controls the overall operation of the wireless device. For example, the control unit 120 controls the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 through a wireless / wired interface, or stores information received from an external device (e.g., another communication device) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0062] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Wireless devices may be embodied in the form of, but are not limited to, a robot (FIG. 1, 100a), a vehicle (FIG. 1, 100b-1, 100b-2), an XR device (FIG. 1, 100c), a mobile device (FIG. 1, 100d), a home appliance (FIG. 1, 100e), an IoT device (FIG. 1, 100f), a digital broadcasting terminal, a hologram 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 (FIG. 1, 400), a BS (FIG. 1, 200), a network node, etc. Wireless devices may be mobile or fixed depending on the use case / service.

[0063] 3, various elements, components, units / sections, and / or modules in the wireless devices 100 and 200 are all connected to each other via a wired interface, or at least some are connected wirelessly via the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected via a wire, and the control unit 120 and a first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. Each element, component, unit / section, and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is configured with a set of one or more processors. For example, the control unit 120 is configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 may be composed of 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.

[0064] In the present invention, at least one memory (e.g., 104 or 204) stores instructions or programs that, when executed, cause at least one processor operably coupled to the at least one memory to perform operations according to some embodiments or implementations of the present invention.

[0065] In the present invention, a computer-readable (non-transitory) storage medium stores at least one instruction or computer program, which, when executed by at least one processor, causes the at least one processor to perform operations according to some embodiments or implementations of the present invention.

[0066] In the present invention, a processing device or apparatus includes at least one processor and at least one computer memory connectable to the at least one processor, the at least one computer memory storing instructions or programs that, when executed, cause the at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present invention.

[0067] In the present invention, a computer program is stored in at least one computer-readable (non-transitory) storage medium and includes program code that, when executed, performs operations according to some embodiments of the present invention or causes at least one processor to perform operations according to some embodiments of the present invention. The computer program is provided in the form of a computer program product. The computer program product includes at least one computer-readable (non-transitory) storage medium.

[0068] The communications device of the present invention includes at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations in accordance with examples of the present invention as described below.

[0069] FIG. 4 is a diagram showing an example of a frame structure that can be used in a 3GPP-based wireless communication system.

[0070] The frame structure of Figure 4 is merely an example, and the number of subframes, slots, and symbols in a frame can be varied. In an NR system, the OFDM numerology (e.g., subcarrier spacing (SCS)) is configured to be different among multiple cells aggregated to one UE. As a result, the (absolute time) duration of time resources (e.g., subframes, slots, or transmission time intervals (TTIs)) consisting of the same number of symbols is configured to be different among the aggregated cells. Here, the symbols include OFDM symbols (or cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) symbols) and SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols). In the present invention, symbols, OFDM-based symbols, OFDM symbols, CP-OFDM symbols and DFT-s-OFDM symbols are interchangeable.

[0071] Referring to Figure 4, in an NR system, uplink and downlink transmissions are organized into frames. Each frame is a T f =(△f max *N f / 100)*T c = 10 ms duration, divided into two half-frames of 5 ms duration each, where the basic time unit for NR is T c =1 / (△f max *N f ) and △f max =480*10 3 Hz and N f = 4096. For reference, the basic time unit for LTE is T s =1 / (△f ref *N f,ref) and △f ref =15*10 3 Hz and N f,ref =2048. T c and T f is the constant κ=T c / T f =64. Each half frame consists of five subframes, and the duration of a single subframe is T sf is 1 ms. A subframe is divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols depending on the cyclic prefix. In the normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, and in the extended CP case, each slot consists of 12 OFDM symbols. The pneumatology uses an exponentially scalable subcarrier spacing Δf=2 u *Depends on 15kHz. The table below shows the subcarrier spacing △f=2 for general CP. u *Number of OFDM symbols per slot at 15 kHz (N slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0072] [Table 1]

[0073] The following table shows the subcarrier spacing for extended CP: u *Indicates the number of OFDM symbols per slot, number of slots per frame, and number of slots per subframe at 15 kHz.

[0074] [Table 2]

[0075] For subcarrier spacing setting u, the slots are n in increasing order within a subframe. u s ∈{0,…,n subframe,u slot -1}, and in increasing order within a frame, n u s,f ∈{0,…,n frame,u slot -1}.

[0076] Figure 5 shows an example of a resource grid for a slot. A slot includes multiple (e.g., 14 or 12) symbols in the time domain. For each neurology (e.g., subcarrier spacing) and carrier, common resource blocks (CRBs) N are allocated as indicated by higher layer signaling (e.g., radio resource control (RRC) signaling). start,u grid Starts with N size,u grid,x *N RB sc subcarriers and N subframe,u symb A resource grid of N OFDM symbols is defined, where N size,u grid,x is the number of resource blocks (RB) in the source grid, and the subscript x is DL for downlink and UL for uplink. RB sc is the number of subcarriers per RB, and in a 3GPP-based wireless communication system, N RB sc is typically 12. For a given antenna port p, subcarrier spacing configuration u and transmission direction (DL or UL), there is one resource grid. size,u gridis provided to the UE by higher layer parameters (e.g., RRC parameters) from the network. Each element in the resource grid for antenna port p and subcarrier spacing setting u is called a resource element (RE), and one complex symbol is mapped to each resource element. Each resource element in the resource grid is uniquely identified by index k in the frequency domain and index l, which indicates the symbol position relative to a reference point in the time domain. In an NR system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs are classified into common resource blocks (CRBs) and physical resource blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing setting u. The center of subcarrier 0 of CRB0 for subcarrier spacing setting u coincides with 'point A', which is the common reference point for the resource block grid. A PRB for subcarrier spacing setting u is defined within a bandwidth part (BWP), ranging from 0 to N size,u BWP,i Common resource block n is numbered from -1, where i is the number of the bandwidth part. u CRB and physical resource block n within bandwidth part i PRB The relationship between is as follows: u PRB =n u CRB +N start,u BWP,i , where N start,u BWP,i is the common resource block whose bandwidth part starts relative to CRB0. A BWP contains multiple consecutive RBs in the frequency domain. For example, a BWP is a given neurology U within BWPi on a given carrier. iA carrier contains up to N (e.g., 5) BWPs. A UE is configured to have one or more BWPs on a given component carrier. Data communication is performed using activated BWPs, and only a predetermined number (e.g., one) of the BWPs configured in the UE are activated on the corresponding carrier.

[0077] For each serving cell in the set of DL BWPs or UL BWPs, the network configures at least an initial DL BWP and one (if the serving cell is configured with an uplink) or two (if a supplementary uplink is used) initial UL BWPs. The network may also configure additional UL and DL BWPs for the serving cell. For each DL BWP or UL BWP, the UE is provided with the following parameters for the serving cell: i) subcarrier spacing, ii) cyclic prefix, iii) N start BWP = 275, offset RB set and length L RB The CRB N is applied by the RRC parameter locationAndBandwidth, which indicates start BWP =O carrier +RB start and the number of consecutive RBs, N size BWP =L RB , and the subcarrier spacing is given by the RRC parameter offsetToCarrier carrier ; Index within the set of DL BWP or UL BWP; set of BWP-common parameters and set of BWP-specific parameters.

[0078] Virtual resource blocks (VRBs) are defined within the bandwidth part and range from 0 to N size,u BWP,iNumbered from -1, where i is the bandwidth part number. VRBs are mapped to physical resource blocks (PRBs) by non-interleaved mapping. In some implementations, in the case of non-interleaved VRB-to-PRB mapping, VRB n is mapped to PRB n.

[0079] A UE configured with carrier aggregation is configured to use one or more cells. When a UE is configured with multiple serving cells, the UE is configured with one or more cell groups. The UE is configured with multiple cell groups associated with different BSs. Alternatively, the UE is configured with multiple cell groups associated with a single BS. Each cell group of the UE consists of one or more serving cells, and each cell group includes a single PUCCH cell with PUCCH resources configured. A PUCCH cell is a Pcell or an Scell ​​of a corresponding cell group that is configured as a PUCCH cell. Each serving cell of a UE belongs to one of the UE's cell groups and does not belong to multiple cell groups.

[0080] The NR frequency band is defined by two types of frequency ranges, FR1 and FR2, also known as millimeter wave (mmW). The table below illustrates the frequency ranges in which NR can operate:

[0081] [Table 3]

[0082] The physical channels used in 3GPP-based wireless communication systems will now be described in more detail.

[0083] The PDCCH carries DCI. For example, the PDCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the paging channel (PCH), system information on the DL-SCH, resource allocation information for control messages of layers above the physical layer in the UE / BS protocol stack (hereinafter referred to as upper layers) such as a random access response (RAR) transmitted on the PDSCH, transmit power control commands, and activation / deactivation of configured scheduling (CS). DCI containing resource allocation information for the DL-SCH is called PDSCH scheduling DCI, and DCI containing resource allocation information for the UL-SCH is called PUSCH scheduling DCI. The DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled to various identifiers (e.g., radio network temporary identifier (RNTI)) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked to a UE identifier (e.g., cell RNTI (C-RNTI)). If the PDCCH is related to paging, the CRC is masked to a paging RNTI (P-RNTI). If the PDCCH is related to system information (e.g., system information block (SIB)), the CRC is masked to a system information RNTI (SI-RNTI). If the PDCCH is related to an unsolicited access response, the CRC is masked to a random access RNTI (RA-RATI).

[0084] Cross-carrier scheduling refers to the PDCCH on one serving cell scheduling the PDSCH or PUSCH of another serving cell. Cross-carrier scheduling using a carrier indicator field (CIF) allows the PDCCH of a serving cell to schedule resources on another serving cell. On the other hand, self-carrier scheduling refers to the PDSCH on a serving cell scheduling the PDSCH or PUSCH on the serving cell. When cross-carrier scheduling is used in a cell, the BS provides the UE with information about the cell scheduling the cell. For example, the BS provides the UE with information about whether the serving cell is scheduled by the PDCCH on another (scheduling) cell or by the serving cell, and, if the serving cell is scheduled by the other (scheduling) cell, which cell signals the downlink assignment and uplink grant for the serving cell. In this invention, a cell that carries a PDCCH is called a scheduling cell, and a cell in which transmission of a PUSCH or PDSCH is scheduled by DCI included in the PDCCH, i.e., a cell that carries a PUSCH or PDSCH scheduled by the PDCCH, is called a scheduled cell.

[0085] The PDSCH is a physical layer UL channel for UL data transport. The PDSCH carries downlink data (e.g., DL-SCH transport blocks) and employs modulation methods such as Quadrature Phase Shift Keying (QPSK), Quadrature Amplitude Modulation (16QAM), 64QAM, and 256QAM. A transport block (TB) is encoded to generate a codeword. 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 are mapped to one or more layers. Each layer is mapped to radio resources along with the DMRS, generated into an OFDM symbol signal, and transmitted via the corresponding antenna port.

[0086] PUCCH refers to a physical layer UL channel for UCI transmission. PUCCH carries UCI (Uplink Control Information). UCI types transmitted on PUCCH include hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information, scheduling request (SR), and channel state information (CSI). UCI bits include HARQ-ACK information bits, if available, SR information bits, LRR information bits, if available, and CSI bits, if available. In this invention, HARQ-ACK information bits correspond to a HARQ-ACK codebook. In particular, a bit sequence in which HARQ-ACK information bits are arranged according to a predetermined rule is called a HARQ-ACK codebook.

[0087] - Scheduling request (SR): Information used to request UL-SCH resources.

[0088] - Hybrid Automatic Repeat Request (HARQ)-acknowledgement (ACK): A response to a downlink data packet (e.g., codeword) on the PDSCH. It indicates whether the downlink data packet was successfully received by the communication device. A 1-bit HARQ-ACK is transmitted in response to a single codeword, and a 2-bit HARQ-ACK is transmitted in response to two codewords. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (NACK), DTX, or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ ACK / NACK, ACK / NACK, or A / N.

[0089] - Channel State Information (CSI): Feedback information for the downlink channel. CSI includes channel quality information (CQI), rank indicator (RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH resource block indicator, layer indicator (LI), etc. CSI is divided into CSI Part 1 and CSI Part 2 depending on the UCI type included in the CSI. For example, CRI, RI, and / or CQI for the first codeword are included in CSI Part 1, and LI, PMI, and CQI for the second codeword are included in CSI Part 2.

[0090] - Link recovery request (LRR)

[0091] In this invention, for convenience, the PUCCH resources configured and / or instructed by the BS to the UE for HARQ-ACK, SR, and CSI transmission are referred to as the HARQ-ACK PUCCH resource, the SR PUCCH resource, and the CSI PUCCH resource, respectively.

[0092] The PUCCH formats are classified as follows according to the UCI payload size and / or transmission length (for example, the number of symbols constituting the PUCCH resource): Please refer to Table 5 for details regarding the PUCCH formats.

[0093] (0) PUCCH format 0 (PF0, F0)

[0094] - Supported UCI payload size: up to K bits (e.g., K=2)

[0095] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0096] - Transmission structure: PUCCH format 0 consists of only a UCI signal without DMRS, and the UE transmits the UCI status by selecting and transmitting one of multiple sequences. For example, the UE transmits one of multiple sequences over a PUCCH with PUCCH format 0 to transmit specific UCI to the BS. The UE transmits a PUCCH with PUCCH format 0 within the PUCCH resource for the corresponding SR setting only when transmitting a positive SR.

[0097] - The configuration for PUCCH format 0 includes the following parameters for the corresponding PUCCH resource: index for initial cyclic transition, number of symbols for PUCCH transmission, first symbol for PUCCH transmission.

[0098] (1) PUCCH Format 1 (PF1, F1)

[0099] - Supported UCI payload size: up to K bits (e.g., K=2)

[0100] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0101] - Transmission structure: DMRS and UCI are configured / mapped to different OFDM symbols in a TDM format. That is, DMRS is transmitted in symbols where no modulation symbols are transmitted. UCI is expressed by multiplying a specific sequence (e.g., orthogonal cover code (OCC)) by a modulation (e.g., QPSK) symbol. A cyclic shift (CS) / OCC is applied to both UCI and DMRS, and code division multiplexing (CDM) is supported between multiple PUCCH resources (according to PUCCH format 1) (within the same RB). PUCCH format 1 carries UCI with a maximum size of 2 bits, and modulation symbols are spread in the time domain by an orthogonal cover code (OCC) (which is configured differently depending on whether frequency hopping is present or not).

[0102] - The configuration for PUCCH format 1 includes the following parameters for the corresponding PUCCH resource: an index for initial cyclic transition, the number of symbols for PUCCH transmission, the first symbol for PUCCH transmission, and an index for an orthogonal cover code.

[0103] (2) PUCCH format 2 (PF2, F2)

[0104] Supported UCI payload size: More than K bits (e.g., K=2)

[0105] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0106] - Transmission structure: DMRS and UCI are configured / mapped in the same symbol in a frequency division multiplexed (FDM) format. The UE applies only IFFT to the coded UCI bits without DFT and transmits them. PUCCH format 2 carries UCI with a bit size greater than K bits, and the modulation symbols are FDM-multiplexed with DMRS and transmitted. For example, DMRS is located at symbol indexes #1, #4, #7, and #10 in a given resource block with 1 / 3 density. A pseudo noise (PN) sequence is used for the DMRS sequence. Frequency hopping is enabled for 2-symbol PUCCH format 2.

[0107] - The configuration for PUCCH format 2 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, and the first symbol for PUCCH transmission.

[0108] (3) PUCCH format 3 (PF3, F3)

[0109] Supported UCI payload size: More than K bits (e.g., K=2)

[0110] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0111] - Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format. UE applies DFT to coded UCI bits and transmits them. PUCCH format 3 does not support UE multiplexing for the same time-frequency resource (e.g., the same PRB).

[0112] - The configuration for PUCCH format 3 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, and the first symbol for PUCCH transmission.

[0113] (4) PUCCH Format 4 (PF4, F4)

[0114] Supported UCI payload size: More than K bits (e.g., K=2)

[0115] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0116] - Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format. PUCCH format 4 applies OCC before DFT and applies CS (or interleaved FDM (IFDM) mapping) to DMRS, allowing up to four UEs to be multiplexed within the same PRB. In other words, the UCI modulation symbols are transmitted using TDM (Time Division Multiplexing) with DMRS.

[0117] - The configuration for PUCCH format 4 includes the following parameters for the corresponding PUCCH resource: the number of symbols for PUCCH transmission, the length for the orthogonal cover code, the index for the orthogonal cover code, and the first symbol for PUCCH transmission.

[0118] The following table shows examples of PUCCH formats, which are divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3 and 4) according to the PUCCH transmission length.

[0119] [Table 4]

[0120] The PUCCH resources are determined for each UCI type (e.g., A / N, SR, CSI). The PUCCH resources used for UCI transmission are determined based on the UCI (payload) size. As an example, the BS sets multiple PUCCH resource sets for the UE, and the UE selects a specific PUCCH resource set corresponding to a specific range according to the range of the UCI (payload) size (e.g., the number of UCI bits). For example, the UE can select any of the following PUCCH resource sets according to the number of UCI bits (N UCI )

[0121] - PUCCH resource set #0, UCI bit number ≤ 2

[0122] - PUCCH resource set #1, 2 < UCI bit number ≤ N1

[0123] ...[[ID=XX]] [[ID=XX]]

[0124] [[ID=XX]] - PUCCH resource set #(K - 1), N K-2 < UCI bit number ≤ N K-1

[0125] Here, K is the number of PUCCH resource sets (K > 1), and N i is the maximum number of UCI bits supported by the PUCCH resource set #i. For example, the PUCCH resource set #1 is composed of resources of PUCCH format 0 - 1, and the other PUCCH resource sets are composed of resources of PUCCH format 2 - 4 (see Table 4).

[0126] Note: In the translation, the tags UCI , K-2 , K-1 , i , ,

[0121] , , ,

[0122] , , ,

[0123] , , ,

[0124] , , ,

[0125] , , <00The configuration for each PUCCH resource includes a PUCCH resource index, a starting PRB index, and a configuration for one of PUCCH formats 0 to 4. The code rate for multiplexing HARQ-ACK, SR, and CSI report in a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4 is configured in the UE by the BS via the upper layer parameter maxCodeRate. The upper layer parameter maxCodeRate is used to determine how to feed back UCI on the PUCCH resource for PUCCH format 2, 3, or 4.

[0127] When the UCI type is SR or CSI, the PUCCH resources used for UCI transmission within the PUCCH resource set are configured in the UE by the network through higher layer signaling (e.g., RRC signaling). When the UCI type is HARQ-ACK for SPS (Semi-Persistent Scheduling) PDSCH, the PUCCH resources used for UCI transmission within the PUCCH resource set are configured in the UE by the network through higher layer signaling (e.g., RRC signaling). On the other hand, when the UCI type is HARQ-ACK for PDSCH scheduled by DCI, the PUCCH resources used for UCI transmission within the PUCCH resource set are scheduled based on the DCI.

[0128] In DCI-based PUCCH resource scheduling, the BS transmits DCI to the UE via the PDCCH and can indicate the PUCCH resource to be used for UCI transmission within a specific PUCCH resource set using an ACK / NACK resource indicator (ARI) in the DCI. The ARI is used to indicate the PUCCH resource for ACK / NACK transmission and is also referred to as a PUCCH resource indicator (PRI). Here, the DCI is the DCI used for PDSCH scheduling, and the UCI includes a HARQ-ACK for the PDSCH. In addition, the BS can configure a PUCCH resource set consisting of more PUCCH resources than the number of states that the ARI can represent to the UE using (UE-specific) higher layer (e.g., RRC) signaling. At this time, the ARI indicates a PUCCH resource subset within the PUCCH resource set, and which PUCCH resource to use within the indicated PUCCH resource subset is determined according to an implicit rule based on transmission resource information for the PDCCH (e.g., the starting control channel element (CCE) index of the PDCCH, etc.).

[0129] A UE must have available uplink resources for UL-SCH data transmission and available downlink resources for DL-SCH data reception. Uplink and downlink resources are assigned to a UE through resource allocation by the BS. Resource allocation includes time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). In this specification, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment. Uplink grants are dynamically received by the UE on the PDCCH or in the RAR, or are semi-persistently configured to the UE by RRC signaling from the BS. Downlink assignments are dynamically received by the UE on the PDCCH or are semi-persistently configured to the UE by RRC signaling from the BS.

[0130] In the UL, the BS can dynamically allocate uplink resources to the UE via a PDCCH addressed to a cell radio network temporary identifier (C-RNTI). The UE monitors the PDCCH to search for possible uplink grants for UL transmission. The BS can also allocate uplink resources to the UE using configured grants. Two types of configured grants are used: Type 1 and Type 2. In Type 1, the BS directly provides the configured uplink grant (including the periodicity) via RRC signaling. In Type 2, the BS configures the periodicity of the RRC-configured uplink grant via RRC signaling and signals and activates or deactivates the configured uplink grant via a PDCCH addressed to a configured scheduling RNTI (CS-RNTI). For example, in the case of Type 2, it indicates that the PDCCH addressed to the CS-RNTI can be implicitly reused according to a period set by RRC signaling until the corresponding uplink grant is deactivated.

[0131] In DL, the BS can dynamically allocate downlink resources to the UE via a PDCCH addressed to the C-RNTI. The UE monitors the PDCCH to search for possible downlink allocations. The BS can also allocate downlink resources to the UE using semi-static scheduling (SPS). The BS configures the period of the configured downlink allocation via RRC signaling and signals and activates or deactivates the configured downlink allocation via the PDCCH addressed to the CS-RNTI. For example, the PDCCH addressed to the CS-RNTI indicates that the corresponding downlink allocation can be implicitly reused with the period configured by RRC signaling until it is deactivated.

[0132] Resource allocation by PDCCH and resource allocation by RRC will be explained in more detail below.

[0133] *Resource allocation via PDCCH: Dynamic grant / allocation

[0134] The PDCCH is used to schedule DL transmissions on the PDSCH or UL transmissions on the PUSCH. The DCI on the PDCCH that schedules DL transmissions indicates the modulation and coding format (e.g., modulation and coding scheme (MCS) index I) associated with the DL-SCH. MCSThe DCI on the PDCCH for scheduling UL transmission includes an uplink scheduling grant including at least a modulation and coding format, resource allocation, and HARQ information related to the UL-SCH. The HARQ information related to the DL-SCH or the UL-SCH includes a new data indicator (NDI), a transport block size (TBS), a redundancy version (RV), and an HARQ process ID (i.e., an HARQ process number). The size and usage of DCI carried by one PDCCH differ depending on the DCI format. For example, DCI format 0_0, DCI format 0_1, or DCI format 0_2 is used for scheduling the PUSCH, and DCI format 1_0, DCI format 1_1, or DCI format 1_2 is used for scheduling the PDSCH. In particular, DCI format 0_2 and DCI format 1_2 are used to schedule transmissions with higher transmission reliability and lower latency requirements than those guaranteed by DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. Some embodiments of the present invention are applicable to transmission of UL data based on DCI format 0_2. Some embodiments of the present invention are applicable to reception of DL data based on DCI format 1_2.

[0135] FIG. 6 shows an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.

[0136] The DCI carried by the PDCCH for scheduling the PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, which provides a value m for a row index m+1 into an allocation table for the PDSCH or PUSCH. A predetermined default PDSCH time domain allocation is applied as the allocation table for the PDSCH, or a PDSCH time domain resource allocation table set by the BS via RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for the PDSCH. A predetermined default PUSCH time domain allocation is applied as the allocation table for the PUSCH, or a PUSCH time domain resource allocation table set by the BS via RRC signaling pusch-TimeDomainAllocationList is applied as the allocation table for the PUSCH. The applied PDSCH time domain resource allocation table and / or the applied PUSCH time domain resource allocation table are determined by fixed / predetermined rules (e.g., see 3GPP TS38.214).

[0137] In PDSCH time-domain resource configuration, each indexed row defines the DL allocation-to-PDSCH slot offset K0, the start and length indicator value SLIV (or directly the starting position of the PDSCH within the slot (e.g., starting symbol index S) and the allocation length (e.g., number of symbols L)), and the PDSCH mapping type. In PUSCH time-domain resource configuration, each indexed row defines the UL grant-to-PUSCH slot offset K2, the starting position of the PUSCH within the slot (e.g., starting symbol index S) and the allocation length (e.g., number of symbols L), and the PUSCH mapping type. K0 for PDSCH or K2 for PUSCH indicates the difference between the slot in which the PDCCH is located and the slot in which the PDSCH or PUSCH corresponding to the PDCCH is located. SLIV is a joint indication of the starting symbol S relative to the start of the slot with the PDSCH or PUSCH and the number of consecutive symbols L counting from symbol S. For PDSCH / PUSCH mapping types, there are two mapping types: one is mapping type A and the other is mapping type B. In PDSCH / PUSCH mapping type A, a demodulation reference signal (DMRS) is mapped to a PDSCH / PUSCH resource based on the start of the slot, but one or two symbols of the PDSCH / PUSCH resource can be used as a DMRS symbol according to other DMRS parameters. For example, in PDSCH / PUSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot according to RRC signaling. In PDSCH / PUSCH mapping type B, the DMRS is mapped based on the first OFDM symbol of the PDSCH / PUSCH resource, but one or two symbols from the first symbol of the PDSCH / PUSCH resource can be used as a DMRS symbol according to other DMRS parameters.For example, for PDSCH / PUSCH mapping type B, the DMRS is located in the first symbol allocated for the PDSCH / PUSCH. In this specification, the PDSCH / PUSCH mapping type is also referred to as a mapping type or a DMRS mapping type. For example, in this specification, PUSCH mapping type A is also referred to as a mapping type A or a DMRS mapping type A, and PUSCH mapping type B is also referred to as a mapping type B or a DMRS mapping type B.

[0138] The scheduling DCI includes a frequency domain resource assignment (FDRA) field that provides allocation information regarding resource blocks used for the PDSCH or PUSCH. For example, the FDRA field provides the UE with information regarding the cell for PDSCH or PUSCH transmission, information regarding the BWP for PDSCH or PUSCH transmission, and information regarding resource blocks for PDSCH or PUSCH transmission.

[0139] *Resource allocation by RRC

[0140] As mentioned above, for the uplink, there are two types of transmissions without dynamic grants: configured grant type 1 and configured grant type 2. For configured grant type 1, an UL grant is provided by RRC signaling and stored as a configured grant. For configured grant type 2, an UL grant is provided by PDCCH and stored or removed as a configured uplink grant based on L1 signaling indicating configured uplink grant activation or deactivation. Type 1 and Type 2 are configured by RRC signaling per serving cell and per BWP. Multiple configurations can be activated simultaneously on multiple different serving cells.

[0141] When grant type 1 is configured, the UE is provided with the following parameters by the BS via RRC signaling:

[0142] - cs-RNTI, which is the CS-RNTI for retransmissions;

[0143] - periodicity, the periodicity of the configured grant type 1;

[0144] - timeReferenceSFN indicating the system frame number (SFN) used for determining the resource offset in the time domain;

[0145] - timeDomainOffset, which is the offset relative to the reference SFN indicated by timeReferenceSFN;

[0146] - a timeDomainAllocation value m providing a row index m+1 pointing to an allocation table indicating the combination of starting symbol S, length L and PUSCH mapping type;

[0147] - frequencyDomainAllocation, which provides frequency domain resource allocation; and

[0148] - I indicating the modulation order, target code rate and transport block size MCS Provided by mcsAndTBS.

[0149] When RRC configures a configuration grant type 1 for a serving cell, the UE stores the UL grant provided by RRC as the configured uplink grant for the indicated serving cell and initializes or re-initializes the configured uplink grant to start at a symbol according to timeDomainOffset and S (derived from SLIV) and to recur with a periodicity. After an uplink grant is configured for configured grant type 1, the UE may consider the uplink grant to recur in association with each symbol that satisfies the following: [(SFN * numberOfSlotsPerFrame (numberOfSymbolsPerSlot) + (SlotNumber in the frame * numberOfSymbolsPerSlot) + symbolNumber in the slot] = (timeDomainOffset * numberOfSymbolsPerSlot + S + N * periodicity) modulo (1024 * numberOfSlotsPerFrame * numberOfSymbolsPerSlot), for all N≧0, where numberOfSlotsPerFrame and numberOfSymbolsPerSlot indicate the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Tables 1 and 2). "SFN" is the system frame number of the frame in which the uplink grant may occur, and "slot number" is the number of consecutive OFDM symbols per slot. "Slot number" is the slot number of a slot in which the uplink grant can occur within the frame, and "symbol number" is the symbol number of a symbol in which the uplink grant can occur within the slot.

[0150] When grant type 2 is configured, the UE is provided with the following parameters by the BS via RRC signaling:

[0151] - cs-RNTI, the CS-RNTI for activation, deactivation and retransmission; and

[0152] - A periodicity that provides a set grant type 2 periodicity.

[0153] The actual uplink grant is provided to the UE via the PDCCH (addressed to the CS-RNTI). After an uplink grant is configured for grant type 2, the UE considers the uplink grant to recur in association with each symbol that satisfies the following: [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot) + (SlotNumber in the frame * numberOfSymbolsPerSlot) + symbolNumber in the slot] = [(SFN start time *numberOfSlotsPerFrame *numberOfSymbolsPerSlot+slot start time *numberOfSymbolsPerSlot+symbol start time )+N*periodicity] modulo (1024 *numberOfSlotsPerFrame *numberOfSymbolsPerSlot), for all N≧0, where SFN start time , slot start time and symbol start timeindicates the SFN, slot, and symbol of the first PUSCH transmission opportunity after the configured grant is (re-)initialized, respectively, and numberOfSlotsPerFrame and numberOfSymbolsPerSlot indicate the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Tables 1 and 2). "SFN" is the system frame number of a frame in which the uplink grant can occur, "slot number" is the slot number of a slot in the frame in which the uplink grant can occur, and "symbol number" is the symbol number of a symbol in the slot in which the uplink grant can occur.

[0154] In some scenarios, the BS further provides the UE with parameters harq-ProcID-Offset and / or harq-ProcID-Offset2 used to derive the HARQ process ID for the configured uplink grant. harq-ProcID-Offset is the offset of the HARQ process for the configured grant for operation with shared spectrum channel access, and harq-ProcID-Offset2 is the offset of the HARQ process for the configured grant. In this specification, cg-RetransmissionTimer is the duration during which the UE must not autonomously perform a retransmission using the HARQ process of the (re)transmission after a (re)transmission based on the configured grant, and is a parameter provided to the UE by the BS when retransmission on the configured uplink grant is configured. For a configured grant where neither harq-ProcID-Offset nor cg-RetransmissionTimer is configured, the HARQ process ID associated with the first symbol of the UL transmission is derived from the following formula: HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes.For a configured uplink grant with harq-ProcID-Offset2, the HARQ process ID associated with the first symbol of an UL transmission is derived from the following formula: HARQ Process ID=[floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes+harq-ProcID-Offset2, where CURRENT_symbol=(SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot+slot number in the frame*numberOfSymbolsPerSlot+symbol number in the slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot denote the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively. For a configured UL grant with cg-RetransmissionTimer, the UE may arbitrarily select a HARQ process ID from among the HARQ process IDs available for configuration of the configured grant.

[0155] For downlink, the UE is configured with semi-persistent scheduling (SPS) per serving cell and per BWP via RRC signaling from the BS. For DL ​​SPS, the DL allocation is provided to the UE via PDCCH and is stored or removed based on L1 signaling indicating SPS activation or deactivation. When SPS is configured, the UE is provided with the following parameters from the BS via RRC signaling:

[0156] - cs-RNTI, the CS-RNTI for activation, deactivation and retransmission;

[0157] - nrofHARQ-Processes, providing the number of configured HARQ processes for SPS;

[0158] - periodicity, which provides the periodicity of the configured downlink allocation for SPS.

[0159] - n1PUCCH-AN providing HARQ resources for PUCCH for SPS (the network configures HARQ resources as format 0 or format 1, and the actual PUCCH-resources are configured in PUCCH-Config and referred to in n1PUCCH-AN by their ID).

[0160] Multiple downlink SPS configurations can be configured within the BWP of the serving cell. After a downlink allocation for SPS is configured, the UE can consecutively consider the Nth downlink allocation to occur in a slot that satisfies: (numberOfSlotsPerFrame*SFN+slotNumber in the frame)=[(numberOfSlotsPerFrame*SFN start time +slot start time )+N*periodicity*numberOfSlotsPerFrame / 10] modulo (1024 *numberOfSlotsPerFrame), where SFN start time and slot start time where "SFN", "slot", and "symbol" respectively indicate the SFN, slot, and symbol of the first transmission of PDSCH after the configured downlink allocation is (re-)initialized, and "numberOfSlotsPerFrame" and "numberOfSymbolsPerSlot" respectively indicate the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot (see Tables 1 and 2). "SFN" is the system frame number of a frame in which the downlink allocation can occur, and "slot number" is the slot number of a slot in the frame in which the downlink allocation can occur.

[0161] In some scenarios, the BS also provides the UE with a parameter harq-ProcID-Offset, which is used to derive the HARQ process ID for the configured downlink assignment. harq-ProcID-Offset is the offset of the HARQ process for SPS. For configured downlink assignments without harq-ProcID-Offset, the HARQ process ID associated with the slot where DL transmission starts is determined from the following formula: HARQ Process ID=[floor(CURRENT_slot*10 / (numberOfSlotsPerFrame*periodicity))] modulo nrofHARQ-Processes, where CURRENT_slot=[(SFN*numberOfSlotsPerFrame)+slot number in the frame], and numberOfSlotsPerFrame is the number of consecutive slots per frame. For a configured downlink allocation with harq-ProcID-Offset, the HARQ process ID associated with the slot where DL transmission starts is determined by the following formula: HARQ Process ID=[floor(CURRENT_slot / periodicity)] modulo nrofHARQ-Processes+harq-ProcID-Offset, where CURRENT_slot=[(SFN*numberOfSlotsPerFrame)+slot number in the frame], and numberOfSlotsPerFrame means the number of consecutive slots per frame.

[0162] If the cyclic redundancy check (CRC) of the corresponding DCI format is scrambled with the CS-RNTI provided by the RRC parameter cs-RNTI and the new data indicator field for an enabled transport block is set to 0, the UE validates the DL SPS-allocated PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or descheduling. Validation of a DCI format is achieved when all fields for the DCI format are set according to Table 6 or Table 7. Table 5 illustrates specific fields for DL ​​SPS and UL grant type 2 scheduling activation PDCCH validity confirmation, and Table 6 illustrates specific fields for DL ​​SPS and UL grant type 2 descheduling PDCCH validity confirmation.

[0163] [Table 5]

[0164] [Table 6]

[0165] The actual DL allocation or UL grant for the DL SPS or UL grant type 2, and the corresponding modulation and coding scheme, are provided by resource allocation fields (e.g., a TDRA field providing the TDRA value m, an FDRA field providing the frequency resource block allocation, and a modulation and coding scheme field) in the DCI format carried by the scheduling activation PDCCH for the corresponding DL SPS or UL grant type 2. If a valid confirmation is achieved, the UE considers the information in the DCI format as a valid activation or deactivation of the DL SPS or configured UL grant type 2.

[0166] In this invention, a PDSCH based on DL SPS is also referred to as an SPS PDSCH, a PUSCH based on UL CG is also referred to as a CG PUSCH, a PDSCH dynamically scheduled by DCI carried by a PDCCH is also referred to as a DG PDSCH, and a PUSCH dynamically scheduled by DCI carried by a PDCCH is also referred to as a DG PUSCH.

[0167] FIG. 7 shows an example of a HARQ-ACK transmission / reception process.

[0168] 7, a UE may detect a PDCCH in slot n. Then, the UE receives a PDSCH in slot n+K0 according to the scheduling information received via the PDCCH in slot n, and then transmits UCI via a PUCCH in slot n+K1. Here, the UCI includes a HARQ-ACK response to the PDSCH.

[0169] The DCI (e.g., DCI format 1_0, DCI format 1_1) carried by the PDCCH that schedules the PDSCH includes the following information:

[0170] - Frequency domain resource assignment (FDRA): Indicates the RB set allocated to the PDSCH.

[0171] - Time domain resource assignment (TDRA): Indicates the DL assignment-to-PDSCH slot offset K0, the starting position (e.g., symbol index S) and length (e.g., number of symbols L) of the PDSCH within the slot, and the PDSCH mapping type. PDSCH mapping type A or PDSCH mapping type B is indicated by TDRA. For PDSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot. For PDSCH mapping type B, the DMRS is located at the first symbol allocated for the PDSCH.

[0172] - PDSCH-to-HARQ_feedback timing indicator: indicates K1.

[0173] If the PDSCH is configured to transmit up to one TB, the HARQ-ACK response consists of 1 bit. If the PDSCH is configured to transmit up to two transport blocks (TBs), the HARQ-ACK response consists of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the HARQ-ACK transmission time for multiple PDSCHs is specified as slot n+K1, the UCI transmitted in slot n+K1 includes the HARQ-ACK responses for multiple PDSCHs.

[0174] In this specification, a HARQ-ACK payload consisting of HARQ-ACK bits for one or more PDSCHs is also referred to as a HARQ-ACK codebook. HARQ-ACK codebooks are classified into i) semi-static HARQ-ACK codebooks, ii) dynamic HARQ-ACK codebooks, and iii) HARQ process-based HARQ-ACK codebooks depending on how the HARQ-ACK payload is determined.

[0175] In the case of a semi-static HARQ-ACK codebook, parameters related to the HARQ-ACK payload size reported by the UE are semi-statically configured by (UE-specific) higher layer (e.g., RRC) signaling. For example, the size of the HARQ-ACK payload in the semi-static HARQ-ACK codebook is determined based on the number of HARQ-ACK bits corresponding to the combination (hereinafter referred to as the bundling window) of all DL carriers (i.e., DL serving cells) configured for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) for which HARQ-ACK transmission timing is indicated, i.e., the maximum HARQ-ACK payload size transmitted via one PUCCH in one slot. In other words, the semi-static HARQ-ACK codebook scheme is a scheme in which the size of the HARQ-ACK codebook is fixed (to the maximum value) regardless of the number of DL data actually scheduled. For example, the DL grant DCI (PDCCH) includes PDSCH to HARQ-ACK timing information, which has one of multiple values ​​(e.g., k). For example, if a PDSCH is received in slot #m and the PDSCH to HARQ-ACK timing information in the DL grant DCI (PDCCH) scheduling the PDSCH indicates k, the HARQ-ACK information for the PDSCH is transmitted in slot #(m+k). For example, k∈{1, 2, 3, 4, 5, 6, 7, 8}. On the other hand, if the HARQ-ACK information is transmitted in slot #n, it includes as many HARQ-ACKs as possible based on the bundling window. That is, the HARQ-ACK information in slot #n includes the HARQ-ACK corresponding to slot #(nk). For example, if k∈{1, 2, 3, 4, 5, 6, 7, 8}, the HARQ-ACK information for slot #n includes HARQ-ACKs corresponding to slot #(n-8) to slot #(n-1) (i.e., the maximum number of HARQ-ACKs), regardless of the actual DL data reception. Here, the HARQ-ACK information can be replaced with a HARQ-ACK codebook or a HARQ-ACK payload.Furthermore, the slots can be understood / replaced as candidate occasions for DL ​​data reception. As illustrated, the bundling window is determined based on the PDSCH-to-HARQ-ACK timing with respect to the HARQ-ACK slot, and the PDSCH-to-HARQ-ACK timing set has a predetermined value (e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or is configured by higher layer (RRC) signaling. A semi-static HARQ-ACK codebook is also referred to as a Type-1 HARQ-ACK codebook. In the case of a Type-1 HARQ-ACK codebook, the number of bits transmitted in a HARQ-ACK report is fixed and may be large. A Type-1 HARQ-ACK codebook is inefficient when many cells are configured but only a few cells are scheduled.

[0176] In addition, in the case of a dynamic HARQ-ACK codebook, the HARQ-ACK payload size reported by the UE can be dynamically changed depending on DCI, etc. A dynamic HARQ-ACK codebook is also called a type-2 HARQ-ACK codebook. The type-2 HARQ-ACK codebook can be considered a more optimized HARQ-ACK feedback because the UE only sends feedback for the scheduled serving cells. In addition, in poor channel conditions, the UE may incorrectly determine the number of scheduled serving cells. To address this issue, a DAI is included as part of the DCI. For example, in the dynamic HARQ-ACK codebook scheme, the DL scheduling DCI includes a counter-DAI (i.e., c-DAI) and / or a total-DAI (i.e., t-DAI). Here, DAI refers to a downlink assignment index, which is used by the BS to inform the UE of the transmitted or scheduled PDSCH included in one HARQ-ACK transmission. In particular, c-DAI is an index indicating the order between PDCCHs carrying DL scheduling DCI (hereinafter referred to as DL scheduling PDCCHs), and t-DAI is an index indicating the total number of DL scheduling PDCCHs up to the current slot in which a PDCCH having t-DAI is present.

[0177] On the other hand, in the case of an HARQ process-based HARQ-ACK codebook, the HARQ-ACK payload is determined based on all HARQ processes of all configured (or activated) serving cells in a PUCCH group. For example, the HARQ-ACK payload size reported by a UE using an HARQ process-based HARQ-ACK codebook is determined by the number of all configured or activated serving cells in a PUCCH group configured for the UE and the number of HARQ processes for the serving cells. The HARQ process-based HARQ-ACK codebook is also called a Type-3 HARQ-ACK codebook. The Type-3 HARQ-ACK codebook can be applied to one-shot feedback.

[0178] One use case of URLLC is a time-sensitive network (TSN). TSN refers to a communication network system in which all devices in a specific area have the same clock time when performing real-time communication, assuming a time-synchronized situation, and based on this, building motion control of devices and collaborative robots in factories. Another use case of the NR system may include XR services.

[0179] Extended reality (XR) is a super-sensory technology and service that utilizes virtual reality (VR), augmented reality (AR), mixed reality (MR), and holograms to provide users with a reality-like virtual space where they can communicate and live without time and space constraints. XR is one of the major services being implemented in NR wireless communication systems. XR is characterized by specific traffic, typically consisting of one or more downlink video streams tightly synchronized with frequent uplink pose / control updates.

[0180] The successful implementation of XR requires support from the wireless system. 3GPP-based wireless communication systems, such as NR wireless communication systems, consider the use of pre-configured resources such as SPS / CG to support XR. For example, a BS can provide SPS / CG settings to a UE based on the average arrival interval of packets. However, the actual arrival interval of packets is not constant (random) due to jitter. Jitter refers to undesirable time deviation in periodic signals. In XR, the amount of information per frame differs, resulting in jitter due to the difference in the time required to process each frame before transmitting it.

[0181] In NR, one or more SPS PDSCHs or CG PUSCHs can be configured in a UE for periodic transmission and reception, low latency, and reduced PDCCH overhead. The configured / instructed resources can be repeated in the time domain at the period specified by each SPS / CG configuration. For example, the initially configured / instructed resource allocation is repeated at the period specified by the SPS / CG configuration, allowing the UE to perform downlink reception / uplink transmission on the resource without a separate PDCCH reception process. Meanwhile, there are various types of data that can be generated in XR. Among these data, UE sensor and location information, which are generally reported at specific periods, and video data transmission are considered to be transmitted and received using SPS / CG resources. The traffic arrival time of this data may not be constant due to factors such as video encoding time, sensor measurement time, upper layer operation, or network routing changes, resulting in jitter. Furthermore, the size of the radio resources required for each transmission may vary depending on the type and coding method of the video frame transmitted by the UE / BS.

[0182] To support such video data transmission, if the BS allocates radio resources based on the maximum size of the required radio resources, radio resources may be wasted when transmitting most of the video information. If the BS allocates radio resources based on a smaller size, additional radio resources will need to be allocated when large traffic occurs, which will result in additional delays.

[0183] Furthermore, because some data is generated based on events, it is difficult to accurately determine the actual time of data generation. However, to reduce delays caused by scheduling, it is possible to consider using SPS / CG resources for such data. In this case, a skipping scheme can be considered, in which a sufficient amount of resources is allocated in a short period in preparation for data generation, and the UE or BS selectively uses some of the resources while not actually using the other resources. However, to use the skipping scheme for transmission and reception, it is necessary to properly consider the response signal used to determine whether transmission or reception is occurring between the UE and the BS. If the UE transmits a response signal even for transmissions that were not received, the BS must always prepare resources for the UE to send the response signal. Considering that the skipping scheme requires sufficient radio resources to be configured in advance, configuring the corresponding response signal resources for all radio resources can place a significant burden on the uplink. Furthermore, considering that these resources may be multiplexed between UEs, the burden on uplink resources should be given even greater consideration.

[0184] The above points should be taken into consideration when using an XR service or a similar third service. For example, to effectively transmit various services or information such as video, where the payload size of traffic dynamically changes, it is possible for the UE to selectively use the SPS / CG-configured radio resources, especially the CG PUSCH, and report the unselected radio resources to the base station in advance. This allows the BS to use those radio resources for other uplink transmissions, thereby reducing the burden on uplink radio resources.

[0185] Hereinafter, several embodiments of the present invention will be described in which, when a UE is configured with multiple radio resources to receive video information required for various services or XR, the UE attempts transmission or reception using only some of the configured radio resources and does not use the remaining radio resources, the UE reports the unused radio resources to a BS, and the BS can allocate the reported radio resources to the UE or another UE.

[0186] Hereinafter, an embodiment of the present invention will be described based on semi-statically configured downlink SPS and uplink CG radio resources. However, the present invention is not limited thereto and can be extended to radio resources allocated by dynamic scheduling received by a UE. For example, an embodiment of the present invention in which a UE determines one HARQ-ACK timing for multiple downlink radio resources allocated to the UE can be applied regardless of the SPS PDSCH or the PDSCH indicated by dynamic scheduling. Furthermore, the present invention can be applied even when multiple radio resources are not configured semi-statically but are configured by dynamic instruction, for example, when multiple radio resources are configured at once by DCI. Therefore, the present invention can be applied to all types of transmission / reception schemes expected by a BS and a UE without any special description. For convenience of explanation, the present invention will be described below using SPS as a general term to refer to semi-statically configured radio resources (e.g., DL / UL SPS, CG).

[0187] In some implementations of the present invention, a transmission occasion (TO) may refer to a radio resource (e.g., an SPS PDSCH or a CG PUSCH) configured for SPS / CG use. An entity transmitting at a transmission occasion (e.g., a BS for downlink, or a UE for uplink) may attempt transmission at the transmission occasion, and a receiving side (e.g., a UE for downlink, or a BS for uplink) may expect transmission at each transmission occasion and attempt reception. In the present invention, the term "transmission occasion" may be used interchangeably with the term "transmission opportunity." Also, in the present invention, a transmission occasion or a transmission opportunity may be simply referred to as "occasion."

[0188] Hereinafter, an embodiment of the present invention will be described based on an NR system, but the embodiment of the present invention is not limited to NR transmission / reception. Also, in the present invention, an embodiment of the present invention will be described using the characteristics and structure of an XR service as an example, but the embodiment of the present invention is not limited to supporting the XR service. Unless otherwise specified, the embodiment of the present invention can be applied to all wireless communication transmission / reception structures and services.

[0189] The following describes some embodiments of the present invention related to methods and procedures for a UE to notify a BS of unused radio resources. The embodiments of the present invention include a method in which a BS allocates PDSCH / PUSCH radio resources to a UE, and a method in which the UE performs downlink or uplink reception on the allocated radio resources. Some embodiments of the present invention include a method in which a UE transmits a HARQ-ACK PUCCH response to a PDSCH reception result, and a method in which a BS receives a retransmitted DCI via a PDCCH after a PUSCH transmission. In some embodiments of the present invention, a UE can transmit signals and channels for notifying its capabilities and / or service requirements, and the BS can receive the signals and channels.

[0190] FIG. 8 illustrates a flow of UE operation according to some implementations of the present invention, and FIG. 9 illustrates a flow of BS operation according to some implementations of the present invention.

[0191] Referring to FIG. 8, a UE may receive an RRC configuration for unused resource indication / information (URI), i.e., an RRC configuration (e.g., a CG configuration) related to a URI and a CG PUSCH (e.g., a CG configuration) (S801). The CG configuration may be automatically activated or initially deactivated. When UL traffic / data to be transmitted occurs in the UE, in other words, when the UL traffic / data becomes transmittable, the UE may determine or predict CG PUSCH resources (i.e., CG PUSCH timing) required for transmitting the UL traffic / data (S803). The UE may report a URI to a BS based on the required CG PUSCH resources (or the number thereof) (S805). The UE may transmit a PUSCH carrying the traffic / data using the CG PUSCH resources (S807).

[0192] 9, a BS may provide a UE with an RRC configuration for a URI and an RRC configuration related to a CG PUSCH (e.g., a CG configuration) (S901). The BS may receive the URI from the UE (S903). The BS may receive a PUSCH in a CG PUSCH resource based on the CG configuration (S905). The BS may perform UL scheduling based on the URI.

[0193] FIG. 10 illustrates an example of a signal transmission / reception flow for a UE and a BS according to some embodiments of the present invention.

[0194] Referring to FIG. 10, a UE may receive an RRC configuration for a URI and an RRC configuration for transmitting a CG PUSCH (e.g., IE ConfiguredGrantConfig) from a BS (S1001, S1002). The semi-static configuration (i.e., CG PUSCH configuration) provided to the UE may be automatically activated or initially deactivated. When UL traffic occurs (S1003) and uplink transmission via a CG PUSCH is to be performed, the UE that has received the RRC configuration for the URI can determine or predict a CG PUSCH timing to be used, taking into account the UE's buffer status and characteristics of the CG PUSCH (S1004). The UE can report information about unused CG PUSCH resources (i.e., CG PUSCH timing) to the BS, taking into account the determined or predicted number of CG PUSCHs to be used (S1005). The BS that receives this information can release the unused CG PUSCH resources for the current time only and schedule uplink transmission for another purpose to the UE or another UE. The UE can perform uplink transmission on other CG PUSCH resources except for the CG PUSCH resources reported as unused, and the BS can attempt uplink reception on other CG PUSCH resources except for the CG PUSCH resources reported as unused (S1006).

[0195] Some of the embodiments / methods described below may be selectively applied. Also, each embodiment / method described below may operate independently without being combined with other embodiments / methods, or one or more embodiments / methods may be combined and operated in conjunction with each other. Some terms, symbols, sequences, etc. used in the present invention may be replaced with other terms, symbols, sequences, etc.

[0196] The implementations / methods described in the present invention may be specified to be applied only when the UE receives related configuration information from the BS (or core network). The configuration information may be provided via higher layer signaling (e.g., SIB or RRC signaling). Alternatively, information configured via higher layer signaling (e.g., SIB or RRC signaling) may be activated / deactivated via other signaling (e.g., DCI or MAC control element (CE)). Furthermore, the UE may be specified to report information (e.g., capabilities) regarding whether the implementations / methods of the present invention are supported, and the BS (or core network) may receive this information.

[0197] In some implementations of the present invention, the URI is also referred to as an unused transmission occasion (UTO)-UCI, since the URI serves as a UCI to inform the BS of an unused transmission occasion.

[0198] With respect to URIs, the following realizations are applicable:

[0199] <Realization 1: Instructions for unused CG resources>

[0200] 11 and 12 show examples of URI transmission according to some embodiments of the present invention. In FIGS. 11 and 12, "TO" indicates a transmission time. In the examples of FIGS. 11 and 12, a "0" in the bit value of the URI indicates that the UE may transmit a CG PUSCH in the TO in the case of CG, and indicates that the UE expects to receive an SPS PDSCH in the TO in the case of DL SPS. On the other hand, in the examples of FIGS. 11 and 12, a "1" in the bit value of the URI indicates that the UE does not transmit a CG PUSCH in the TO in the case of CG, and indicates that the UE does not expect to receive an SPS PDSCH in the TO in the case of DL SPS. In the examples of FIGS. 11 and 12, the URI is expressed as indicating whether or not a TO is available within a period, but the TOs that the URI can indicate whether or not a URI is available may not be limited to one period. For example, in some embodiments described below, the URI indicates whether or not a TO is available within a period different from the period to which the PUCCH / PUSCH carrying the URI belongs. As another example, in some implementations described below, the length of the URI indicates whether or not a TO can be used within multiple periods.

[0201] The BS can indicate and configure one or more CG PUSCHs for a given time interval T to the UE.

[0202] For example, by including information about multiple TDRAs in one CG configuration, multiple radio resources (i.e., multiple CG PUSCH occasions) can be configured within a periodicity by activating the CG using DCI including the TDRA information. For example, a BS can provide a CG configuration including multiple consecutive uplink grants within a single period to a UE. According to this CG configuration, multiple CG PUSCH occasions can occur within a single period of the CG configuration.

[0203] As another example, a BS may instruct and configure one or more SPS / CG radio resources for a UE, and multiple SPS / CG radio resources may be allocated for repeatedly transmitting one transport block (TB) within a period or a certain time range. For example, one or more SPS / CG configurations may be provided, and PDSCH / PUSCH opportunities based on the one or more SPS / CG configurations may occur within a period or a certain time range.

[0204] As another example, a BS may instruct and configure one or more SPS / CG radio resources for a UE, and multiple SPS / CG radio resources for transmitting multiple TBs within a period or a certain time range may be allocated to the UE. For example, multiple SPS / CG configurations may be provided, and PDSCH / PUSCH opportunities based on the multiple SPS / CG configurations may occur within a period or a certain time range.

[0205] Even when uplink traffic occurs in the UE and configured CG PUSCH transmission is necessary, the UE may not use all of the configured CG PUSCHs within the time period T. For example, the UE may decide to use some of the configured CG PUSCHs within the time period T, decide not to use some of them, and reserve the decision for future uplink transmissions for some of them. In some embodiments of the present invention, the UE may transmit information (hereinafter, URI) regarding the CG PUSCHs that it has decided not to use to the BS. For example, the UE may transmit information regarding the radio resources it has decided to use and the CG PUSCHs that it determines are necessary for future uplink transmissions. The UE may not transmit user data in CG PUSCH times that it has not notified it will use or has not notified it will not use. For example, the BS may assume that the UE does not generate a MAC PDU to transmit for the PUSCH in a CG PUSCH time that it has not notified it will not use, or that the PUSCH does not exist and is skipped. Alternatively, a configured grant indicated as unused on the MAC layer can be considered as having been de-prioritized during logical channel (LCH) prioritization.

[0206] In using embodiment 1, such an operation may be performed based on an explicit request from the UE. For example, when the UE uses a CG PUSCH, it may notify the BS via embodiment 1 of whether or not to use the configured radio resources only if the responsiveness of the configured CG PUSCH is reduced. The UE may transmit a separate message for notifying the BS of the use of embodiment 1 via L1 signaling (e.g., PUCCH, PUSCH) or higher layer signaling so that the BS can receive information on whether or not to use each radio resource. The BS that receives the message may receive information on whether or not to use the CG PUSCH timing by the UE, assuming that the CG PUSCH transmission by the UE or the separately configured PUCCH includes information on whether or not to use the CG PUSCH timing by the UE.

[0207] Alternatively, it may be considered that such an operation is performed based on an explicit request from the BS when using Implementation 1. For example, the BS may transmit a separate message notifying the UE of the use of Implementation 1 via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling, MAC signaling). The UE that receives the message may transmit information indicating whether the UE can use the CG PUSCH timing, i.e., a URI, together with the CG PUSCH transmission of the UE or a separately configured PUCCH, and the BS may receive the URI based on the information.

[0208] In some cases, a UE needs to have a specific capability to use an operation related to Implementation 1. In such cases, the UE can notify the BS whether it can use Implementation 1 through a capability report. By receiving the capability report, the BS can perform the BS operation only for UEs that can use Implementation 1.

[0209] The operation related to Embodiment 1 can be performed for each CG setting set in the UE. For example, whether or not to use the operation related to Embodiment 1 can be set individually for each CG setting, and the UE can execute Embodiment 1 only for the CG setting set to use Embodiment 1.

[0210] When performing the operations according to embodiment 1, the CG configuration of the CG PUSCH transmitting the URI may differ from the CG configuration to which the URI is applied, as will be described in more detail in embodiments 1-5.

[0211] When using embodiment 1, a BS that has not received a separate message from a UE and a UE that has not sent a separate message to a BS can assume that all configured CG PUSCH times are not unused.

[0212] <Implementation 1-1: Where to transmit Unused CG resource indication>

[0213] As a transmission method for a UE to transmit information (hereinafter, referred to as URI) regarding a CG PUSCH that the UE has decided not to use to a BS, at least one of the following methods can be considered.

[0214] The UE may transmit the URI via a piggybacked UCI that is also transmitted on the CG PUSCH transmission.

[0215] The UE may transmit the URI via the MAC CE that is transmitted together on the CG PUSCH transmission.

[0216] The UE may transmit the URI via a separate PUCCH for the URI.

[0217] The UE can transmit the URI via a DMRS symbol on the CG PUSCH transmission. For example, N orthogonal DMRS sequences can be used to transmit one of N different information values.

[0218] <Realization 1-2: Reference time region for unused CG resource indication>

[0219] When a UE transmits a URI to a BS, the URI may include information about a CG PUSCH included in a time interval T. In this case, at least one of the following may be considered to determine the time interval T:

[0220] > To determine the start of a time interval T,

[0221] >> The start point of the time interval T may be the beginning or end of the start symbol of the PUSCH or PUCCH in which the URI is transmitted. That is, the URI carried by a certain PUSCH / PUCCH may include information regarding whether or not a CG PUSCH is transmitted for a predetermined time from the start / end symbol of the corresponding PUSCH / PUCCH.

[0222] >>> In some implementations, when a URI is transmitted on a CG PUSCH, the start point of the time interval T may be the beginning or end of the start symbol of the next CG PUSCH that is closest to the CG PUSCH on which the URI is transmitted. For example, referring to FIG. 11 or 12, the URI transmitted at CG PUSCH occasion #i may include information on whether a subsequent CG PUSCH occasion, i.e., a CG PUSCH occasion within a predetermined time from the start symbol of CG PUSCH occasion #i+1, is used.

[0223] >>> In some implementations, when a URI is transmitted on a CG PUSCH, the start of the time interval T may be the beginning or end of the start symbol of the next CG PUSCH closest within the period of the CG PUSCH in which the URI is transmitted.

[0224] >> The start point of the time interval T is a predetermined time interval T from the beginning or end of the start symbol of the PUSCH or PUCCH in which the URI is transmitted. proc,URI The time may be separated by a few seconds.

[0225] >>> When a URI is transmitted on a CG PUSCH, the start point of the time interval T is a predetermined time interval T from the beginning or end of the start symbol of the next CG PUSCH closest (within the period) of the CG PUSCH on which the URI is transmitted. proc,URI The time may be separated by a few seconds.

[0226] >> The start point of the time interval T may be the beginning or end of the last symbol of the PUSCH or PUCCH in which the URI is transmitted. That is, the URI transmitted by a certain PUSCH / PUCCH may include information regarding whether a CG PUSCH is transmitted within a predetermined time period from the last symbol of the PUSCH / PUCCH.

[0227] >>> When a URI is transmitted on a CG PUSCH, the start point of the time interval T may be the beginning or end of the last symbol of the next CG PUSCH closest (within the period) to the CG PUSCH on which the URI is transmitted.

[0228] >> The start point of the time interval T is a predetermined time interval T from the beginning or end of the last symbol of the PUSCH or PUCCH in which the URI is transmitted. proc,URI The time may be separated by a few seconds.

[0229] >>> When a URI is transmitted on a CG PUSCH, the start point of the time interval T is a predetermined time interval T from the beginning or end of the last symbol of the next CG PUSCH (within the period) of the CG PUSCH on which the URI is transmitted. proc,URI The time may be separated by a few seconds.

[0230] >> If a URI is transmitted on a CG PUSCH, the start of the time interval T may be the start of a period including the CG PUSCH, or the start of the time interval T may be the start of a period including a CG PUSCH that is closest to the CG PUSCH carrying the URI.

[0231] >> When the URI is transmitted on a CG PUSCH, the start point of the time interval T is a predetermined time interval T from the start of the period in which the CG PUSCH is included. proc,URI Alternatively, the start point of the time interval T may be a time point separated by a predetermined time interval T from the start of the period in which the CG PUSCH that carries the URI is included, the CG PUSCH being the closest to the CG PUSCH in question. proc,URI The time may be separated by a few seconds.

[0232] >> If the URI is transmitted on a CG PUSCH, the start point of the time interval T may be the end of the period in which the CG PUSCH is included (i.e., the start of the next period).

[0233] >> When a URI is transmitted on a CG PUSCH, the start point of the time interval T is a predetermined time interval T from the end of the period in which the CG PUSCH is included (i.e., the start of the next period). proc,URI The time may be separated by a few seconds.

[0234] >> the predetermined time interval T proc,URI The predetermined time interval T may be the time required for the BS to reschedule the uplink radio resources indicated as unused resources by the URI after the URI transmission. proc,URI may be a value provided by the BS via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling), a predefined value, or a value determined by the BS based on the relevant UE capabilities. As an example, as described in 3GPP TS 38.214, the values ​​N1 or N2 are used to determine the time required for the PUCCH or PUSCH preparation process, taking into account the UE capabilities and the SCS of the UL BWP, or the time T calculated from these values. proc,1 or T proc,2 T proc,URI More specifically, these values ​​can be used to determine T proc,URI or a fraction of this value may be used as T proc,URI It may also be used as

[0235] >> When a URI is transmitted on a CG PUSCH, the start point of the time interval T may be the start of every N periods including the CG PUSCH, i.e., the start of the first CG PUSCH among the N periods including the CG PUSCH. Alternatively, the start point of the time interval T may be the start of every N periods including a CG PUSCH that is closest to the CG PUSCH carrying the URI. In some implementations, the boundaries (starts and ends) of every N periods can be determined by treating the first N periods of the CG PUSCH from SFN#0 as a first group and the subsequent N periods as a second group.

[0236] >>> Here, N may be a value given via higher layer signaling from the BS, or may be a value determined via the value.

[0237] >> When a URI is transmitted on a CG PUSCH, the start point of the time interval T is a predetermined time interval T from the start of every N periods including the CG PUSCH. proc,URI Alternatively, the start point of the time interval T may be a time point separated by a predetermined time interval T from the start of every N periods in which the nearest subsequent CG PUSCH of the CG PUSCH carrying the URI is included. proc,URI In some implementations, the boundaries (start and end) of every N periods can be determined by treating the first N periods of the CG PUSCH from SFN#0 as a first group and the subsequent N periods as a second group.

[0238] >>> Here, N is a value given through upper layer signaling from the base station or a value determined based on a corresponding value.

[0239] >> When a URI is transmitted on a CG PUSCH, the start point of the time interval T may be the end of every N periods including the CG PUSCH (i.e., the start of the next N periods). In some implementations, to determine the boundaries (starts and ends) of every N periods, the first N periods of the CG PUSCH from SFN#0 are grouped as a first group, and the next N periods are grouped as a second group, thereby determining the boundaries of every N periods.

[0240] >>> Here, N is a value given via upper layer signaling from the BS, or a value determined based on the corresponding value.

[0241] >> When a URI is transmitted on a CG PUSCH, the start point of the time interval T is a predetermined time interval T from the end of every N periods including the CG PUSCH (i.e., the start of the next N periods). proc,URI In some implementations, the boundaries (start and end) of every N periods can be determined by treating the first N periods of the CG PUSCH from SFN#0 as a first group and the next N periods as a second group.

[0242] >>> Here, N is a value given via upper layer signaling from the BS, or a value determined based on the corresponding value.

[0243] > To determine the length of the time interval T,

[0244] >> The time interval T may be a value given via higher layer signaling from the BS.

[0245] >> The time interval T may be a value determined by the UE and indicated in the URI. In this case, the URI may be composed of two parts: a part indicating the length of the time interval T, and a part indicating whether the CG PUSCH is unused during the time interval T indicated in the part.

[0246] >> The time interval T may be a multiple of the period of a configured grant (CG) PUSCH configured by a CG configuration.

[0247] >>> In this case, the CG setting may be the CG setting to which the URI applies.

[0248] >>> In this case, the CG configuration may be a CG configuration that transmits a URI. In particular, this can take into account the case where the URI is transmitted on the CG PUSCH.

[0249] >> The time interval T may be a specific time (for example, X ms).

[0250] >> The time interval T may be a specific slot length (eg, Y slots).

[0251] >>> In this case, the slot length may be converted into an absolute time length based on a separately set reference SCS setting or the BWP to which the URI can be applied or transmitted (e.g., 1 slot = 1 ms (in the case of 15 kHz SCS)).

[0252] >> The time interval T may be a time to which N CG PUSCH occasions are allocated. For example, the time interval T may extend to the last symbol of the last CG PUSCH occasion among the N CG PUSCH occasions that start after the start of the time interval T, or to the slot in which the last symbol is located.

[0253] >>> The number N of CG PUSCH occasions may be a value provided via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling) of the BS, and multiple values ​​may be provided for each CG configuration, or one value may be provided for the entire CG configuration. For example, referring to FIG. 11, if N=4 is provided for the CG configuration via higher layer signaling, the URI transmitted at CG PUSCH occasion #i may indicate whether or not the four CG PUSCH occasions (CG PUSCH occasions #(i+1) to (i+4)) following the CG PUSCH occasion i are available. 11, bits 0011 of the URI transmitted at CG PUSCH time #1 are mapped one-to-one to CG PUSCH times #2 to #5 in ascending order, bits 0111 of the URI transmitted at CG PUSCH time #2 are mapped one-to-one to CG PUSCH times #3 to #6 in ascending order, and bits 0011 of the URI transmitted at CG PUSCH time #3 are mapped one-to-one to CG PUSCH times #4 to #7 in ascending order. A BS that receives a URI at CG PUSCH time #1 can determine that the UE may transmit a CG PUSCH at CG PUSCH times #2 and #3, and can attempt to receive the CG PUSCH at CG PUSCH times #2 and #3, respectively. A BS that receives a URI at CG PUSCH times #1 to #3 can determine that CG PUSCH times #4 to #7 are not being used by the UE, and can therefore not expect or attempt to receive a CG PUSCH from the UE at CG PUSCH times #4 to #7. Because it is unclear whether CG PUSCH time #8 will be used, the BS can attempt to receive a CG PUSCH from the UE at CG PUSCH time #8.According to some embodiments of the present invention, a UE notifies N TOs subsequent to a TO transmitting a URI of whether the URI is in use or not via the URI. Therefore, even if the UE changes its decision regarding the CG PUSCH occasion indicated to be used by the URI after transmitting a URI at CG PUSCH occasion #i, the use status of the subsequent CG PUSCH occasion can be updated to an unused state via the URI transmitted in another CG PUSCH occasion indicated to be used by the URI. Furthermore, by transmitting the URI at a predetermined size indicated / set by the BS, excessive increase in URI signaling overhead can be prevented.

[0254] >> The time interval T may be a time period in which CG PUSCHs configured to transmit N TBs are allocated. That is, the time interval T may extend to the last symbol or slot in which the last symbol of the last CG PUSCH is located among CG PUSCHs configured to transmit N TBs that start after the start of the time interval T.

[0255] >>> The number N of CG PUSCHs (i.e., the number N of CG PUSCH occasions) may be a value given via L1 signaling or higher layer signaling from the BS, and multiple values ​​may be given for each CG setting, or one value may be given for the entire CG setting.

[0256] >>> When repeated transmission is configured for the CG PUSCH, the time interval T may be up to the last symbol or the slot in which the last symbol of the last CG PUSCH is located among the CG PUSCH group configured to transmit N TBs whose initial transmission starts after the start of the time interval T.

[0257] >> The time interval T may be from the start point to the end point of a predetermined period, or to the end of the last CG PUSCH in the predetermined period. For example, if the period including the start point is period X, the time interval T may refer to the time interval from the start point to the end point of period X+k, or to the end of the last symbol of the last CG PUSCH included in the period. The k is an integer greater than or equal to 0, and may be provided or determined via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling) of the BS.

[0258] >>> As another example, consider a case where the start of the next closest CG PUSCH in the period of the CG PUSCH in which the URI is transmitted is set as the start point of time interval T, and time interval T ends at the end point of the period. In this case, the UE can transmit the URI only in the CG PUSCHs remaining after the CG PUSCH in which the URI is transmitted in the period, thereby reducing the information required for transmission.

[0259] >> As another example, the time interval T may be from the start point to the end point of N periods, or the last CG PUSCH included in the N periods. More specifically, if N periods including the start point are defined as a period group X, the regular time interval T may be from the start point to the end point of the period group X, or the last CG PUSCH included in the period group X.

[0260] >>> To determine the boundaries (start and end) of each N period, the first N periods from SFN#0 to CG PUSCH are grouped as the first group, and the next N periods are grouped as the second group.

[0261] >>> N is an integer greater than or equal to 1, and may be provided or determined via L1 signaling or higher layer signaling of the BS.

[0262] >>> As another example, consider a case where the start of the next closest CG PUSCH within N periods including a CG PUSCH in which a URI is transmitted is set as the start point of time interval T, and time interval T ends at the end point of the N periods. In this case, the UE can transmit the URI only in the CG PUSCHs remaining after the CG PUSCH in which the URI is transmitted in each of the N periods, thereby reducing the amount of information required for transmission.

[0263] > When considering the period of CG setting, one period can be defined as follows:

[0264] >> The start of a period can be the end of the previous period, i.e., periods are connected together to form a continuous time.

[0265] >> When one radio resource is allocated and the radio resource is repeated for a certain time period P, the start point of each period is the start point of the radio resource, and the length of the period is P.

[0266] >> When one radio resource is assigned to a UE, and the radio resource is repeated at slot intervals to use multiple radio resources, and the multiple radio resources are repeated over a certain time period P, the starting point of each period is the starting point of the first radio resource, and the length of the period is P.

[0267] >> When one radio resource is allocated and the radio resource is repeated at slot intervals or continuously within a slot, if multiple radio resources are used and the multiple radio resources are repeated over a time period P, the start of each period is the start of the first radio resource and the length of the period is P.

[0268] >> When multiple radio resources are provided through one time domain resource allocation information and the multiple radio resources are repeated in a predetermined time interval P, the start point of each period is the start time of the earliest starting radio resource among the multiple radio resources, and the length of the period is P.

[0269] In some implementations, if there is not enough time between the start of the time interval T (i.e., the start of the radio resource for which the URI can provide information on whether or not to transmit the CG PUSCH) and the end of the UE's URI transmission, the BS may have difficulty rescheduling uplink resources using the information provided by the URI. To prevent this problem, in some implementations, there may be enough time between the start of the time interval T and the end of the UE's URI transmission. proc,URI Alternatively, the UE may be allowed to transmit the URI only if a sufficient time interval T is ensured between the start of the time interval T and the end of the URI transmission of the UE. proc,URI If the UE does not secure the information included in the URI, the information included in the URI is proc,URI The UE and / or BS may ignore all or part of the URI information including or related to the radio resources during the period. Even for CG PUSCHs indicated as unused in the ignored URI information, the UE can still perform CG PUSCH transmission, and the BS can still attempt reception on the CG PUSCH even when it receives such information. When the UE or BS applies URI to a CG PUSCH period or a predetermined time / resource unit, the URI information may be ignored for all CG PUSCHs included in that time / resource unit.

[0270] In some implementations, the time interval T may represent a minimum scope of application of the URI. For example, after receiving the message, the BS may not instruct the UE to send additional messages or may always instruct the UE to send the same message (i.e., without changing the content once instructed) during the minimum scope of application, and may allow the UE to send another message after the minimum scope of application. If the UE does not send a message or continues to instruct the UE to send the same message, a method may be considered in which the application continues as if the message were received again after the time interval T.

[0271] In the first embodiment, the UE may report whether or not a CG PUSCH time is unused in two separate messages. For example, the first message indicates the range of the CG PUSCH time, i.e., time interval T, for which the CG PUSCH time is to be reported as unused, and the second message indicates whether or not the CG PUSCH on time interval T is unused. In this case, to facilitate blind decoding by the BS, the information in the first message may have a fixed length, and the length of the second message may be variable according to the range of time interval T in the first message. For example, the first message may express K CG PUSCH time periods or K CG PUSCH periods (K<2) using fixed N-bit information. N ), the second message may transmit a K-bit bitmap indicating the radio resources that the UE will use or will not use during the K CG PUSCH occasions or K CG PUSCH periods.

[0272] <Realization 1-3: Construction of unused CG resource indication>

[0273] The UE can transmit information regarding whether or not to transmit a CG PUSCH for time interval T as a URI as follows:

[0274] First, to configure the URI, the time interval T can be divided into certain time units. At this time, the URI information can be determined based on whether or not the CG PUSCH included in each time unit is unused.

[0275] >> As an example, the time unit may be a specific time (e.g., xms) determined via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling) of the BS.

[0276] >> As an example, the time unit may be a specific slot length (e.g., y slots) determined via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling) of the BS.

[0277] >> As an example, the time unit may be a period of the CG PUSCH set in the CG configuration or a multiple of that period.

[0278] >>> In this case, the CG setting may be the CG setting to which the URI applies.

[0279] >>> In this case, the CG setting may be the CG setting of the PUSCH carrying the URI. In particular, this can be considered when the URI is transmitted on a CG PUSCH.

[0280] >> As an example, the time unit may be the period of the CG PUSCH set in the CG configuration, or may be a size obtained by dividing the period by an integer N greater than 1.

[0281] >>> In this case, the CG setting may be the CG setting to which the URI applies.

[0282] >>> In this case, the CG setting may be the CG setting of the PUSCH carrying the URI, especially when the URI is transmitted on the CG PUSCH.

[0283] >> As an example, the time unit may refer to one or n CG PUSCH occasions.

[0284] >>> More specifically, one time unit can mean from the first symbol of a certain CG PUSCH occasion to (the start of) the first symbol of the nearest next certain CG PUSCH occasion.

[0285] In this case, the time period T may be a time period in which N CG PUSCH opportunities are allocated.

[0286] >>> In some implementations, the number n of CG PUSCHs may be provided via L1 signaling (e.g., DCI) or higher layer signaling (RRC signaling) from the BS.

[0287] >> As an example, the time unit may be a time allocated to a CG PUSCH configured to transmit one or n TBs.

[0288] >>> More specifically, one time unit can mean from the first symbol of a CG PUSCH configured to transmit one TB to the (start of) the first symbol of the nearest CG PUSCH configured to transmit another TB.

[0289] >>> In this case, the time period T may be a time period allocated to a CG PUSCH configured to transmit N TBs.

[0290] >> If the time interval T is not divisible by the time unit, the following is considered:

[0291] >>> If a given time unit exceeds the end of the time interval T, the UE may assume that the corresponding time unit ends at the end of the time interval T.

[0292] >>> The BS may configure multiple time units to the UE via higher layer signaling. The UE may divide a time interval T, which is an entire interval expressed by a URI, by arranging the multiple time units in order and determine whether to use the CG PUSCH in each time unit. In this case, the sum of the multiple time units may be the time interval T or a larger value. If the sum of the multiple time units is larger than the time interval T, the UE may assume that a given time unit ends at the end of the time interval T if the given time unit extends beyond the end of the time interval T.

[0293] 11, the UE can configure a URI by indicating the positions of time units including unused CG PUSCH resources over N consecutive time units as "1" and the positions of other time resources as "0" using a bitmap having a size of N. Alternatively, the UE can configure a URI by indicating the positions of time units including CG PUSCHs that have not been determined to be unused over N consecutive time units as "1" and the positions of other time resources as "0" using a bitmap having a size of N.

[0294] >> Here, N may be the number of CG PUSCHs included in the time interval T (i.e., the number of CG PUSCH occasions).

[0295] >>> For example, N may be the number of configured CG PUSCHs included in the time interval T. That is, N may be the number of radio resources included in the time interval T when time domain radio resources determined through L1 signaling or higher layer signaling are repeated at a predetermined period based on CG configuration.

[0296] >>> For example, N may be the number of valid CG PUSCHs included in the time interval T. That is, among the CG PUSCHs included in time interval T, N may be the number of CG PUSCHs that do not overlap with the DL symbols indicated by the RRC parameter tdd-UL-DL-ConfigurationCommon or, if provided, the RRC parameter tdd-UL-DL-ConfigurationDedicated, or the symbols and times of the SS / PBCH blocks (i.e., SSBs) of the indices provided by the RRC parameter ssb-PositionsInBurst. In this case, the CG PUSCHs that can be indicated may be limited to the valid CG PUSCH (time) or a time unit including a valid CG PUSCH (time). For example, referring to FIG. 12, if N=4 is provided for the CG configuration by higher layer signaling, the URI transmitted at CG PUSCH time #i may indicate whether or not four CG PUSCH times subsequent to CG PUSCH time i are usable, excluding invalid CG PUSCH times. 12, bits 0011 of the URI transmitted at CG PUSCH time #1 are mapped one-to-one to CG PUSCH times #2 to #5 in ascending order, bits 0111 of the URI transmitted at CG PUSCH time #2 are mapped one-to-one to CG PUSCH times #3, 4, 5, and 7 in ascending order, and bits 0011 of the URI transmitted at CG PUSCH time #3 are mapped one-to-one to CG PUSCH times #4, 5, 7, and 8 in ascending order. A BS that receives UCI at CG PUSCH times #1 to #3 can determine that CG PUSCH times #4, 5, 7, and 8 are unused by the UE, and can therefore not expect to receive a CG PUSCH from the UE at CG PUSCH times #4 to #7 and can not attempt to receive a CG PUSCH from the UE. The BS knows that CG PUSCH opportunity #6 is an invalid opportunity in which the UE cannot transmit a PUSCH, and therefore does not expect to receive a CG PUSCH and may not attempt to receive a CG PUSCH.This allows the BS to know whether the CG PUSCH can be used for a longer period by providing URIs for TOs other than those for which the BS already knows that the CG PUSCH will not be used.

[0297] >> As an example, the position of a time unit that includes unused resources among the N time units can be indicated by "1" (or "0"), and the position of other time resources can be indicated by "0" (or "1"), in order to indicate that a radio resource that includes at least one unused CG PUSCH is unused.

[0298] >> As an example, the positions of time units that do not include unused resources among the N time units can be indicated by "0" (or "1"), and the positions of other time resources can be indicated by "1" (or "0"), in order to indicate that radio resources including at least one usable CG PUSCH are unused.

[0299] >> As another example, among invalid CG PUSCHs, i.e., CG PUSCHs included in time interval T, DL symbols indicated by the RRC parameter tdd-UL-DL-ConfigurationCommon or, if provided, the RRC parameter tdd-UL-DL-ConfigurationDedicated, or CG PUSCHs that do not overlap with the symbols and time of SS / PBCH blocks of indexes provided by the RRC parameter ssb-PositionsInBurst, can always be indicated as unused resources.

[0300] >> As another example, the UE may consider only K valid CG PUSCHs in a bitmap of size N and indicate whether the K CG PUSCHs are unused in K consecutive bits from the MSB or LSB. That is, values ​​for valid CG PUSCHs may be arranged consecutively. In this case, the remaining (NK) bits may be represented as a bit value indicating unused bits or as '0'. In this case, the size N may be the (maximum) number of CG PUSCHs configured within the interval, as described above, or the (maximum) number of valid PUSCHs that can be included in the CG configuration. The size N may be a size provided or determined via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling) of the BS.

[0301] >> As described in Embodiments 1-2, when a CG PUSCH carries URI information, the time interval T associated with the URI information may not include the CG PUSCH. This is because there is no case in which the CG PUSCH carrying the URI information is unused. When the UE configures a bitmap for a certain time interval T as a URI, it can exclude bits associated with the CG PUSCH transmitting the URI in consideration of this.

[0302] The UE may indicate a first position of a time unit including radio resources usable for the UE to notify usable CG PUSCH included in K consecutive time units among N time units and the number of time units including usable radio resources. For example, the position S of the first time unit to be used among N time units and the number K of consecutive time units including usable radio resources may be expressed as N*(N+1) / 2 state values. In this case, the jointly coded information value I may be derived using the following equation: I=N×(K−1)+S.

[0303] The UE may indicate the first position of the time unit including the unused CG PUSCH and the number of consecutive time units including the unused CG PUSCH so that the UE can report the unused CG PUSCH included in K consecutive time units among N time units. For example, the position S of the first time unit including unused resources among N time units and the position K of the time unit including the last unused CG PUSCH among N time units may be expressed as N*(N+1) / 2 state values. In this case, the jointly coded information value I may be derived using the following equation: I=N×(K-1)+S.

[0304] The UE may indicate the number of consecutive time units including available radio resources from the start of the time interval T, so that the UE can notify available CG PUSCHs included in the first K consecutive time units out of the N time units.

[0305] The UE may indicate the number of consecutive time units including unused CG PUSCHs from the start of the time interval T so that the UE can report unused CG PUSCHs included in the first K consecutive time units out of the N time units.

[0306] The BS may preconfigure a list of one or more patterns of unused resources (or available resources) for the UE. Alternatively, these patterns may be predefined. For example, multiple bitmaps may be configured for the UE, and each bitmap may indicate, over N consecutive time units, the positions of time units that include unused CG PUSCH resources or the positions of time units that include CG PUSCHs that have not been determined as unused, with "1", and the positions of other time resources with "0".

[0307] The plurality of patterns may include a pattern in which all bits are "0" or a pattern in which all bits are "1." In other words, this may include cases in which there are no unused resources or all unused resources.

[0308] The UE compares the determined unused resources with the configured patterns and reports the index of the appropriate pattern to the BS as a URI. To determine the appropriate pattern, at least one of the following is considered:

[0309] >>> Condition 1: A pattern in which all unused CG PUSCHs determined by the UE are shown as unused, and / or a pattern that satisfies this and has the fewest unused resources

[0310] >>> Condition 2: A pattern in which all remaining CG PUSCH resources excluding unused CG PUSCH determined by the UE are indicated as usable, and / or a pattern that satisfies this and has the fewest usable resources

[0311] The UE compares the determined unused resources with the configured patterns and reports the index of the appropriate pattern to the BS as a URI. Some states of the URI may be predefined. For example, when the UE transmits an N-bit URI, a state in which all N bits are set to '1' may indicate a pattern in which no unused CG PUSCH exists within time interval T. As another example, a specific state may indicate a pattern in which all resources within time interval T are unused CG PUSCHs. Each of the other states may be associated with one of the pattern lists. This behavior may be limited to the case where the pattern index associated with that state is not configured. For example, in a 4-bit URI,

[0000] ,

[0001] ,

[0010] , ...,

[1110] , and

[1111] may be associated with patterns 1 through 16 in a pattern list containing up to 16 patterns. If the 16th pattern is not configured,

[1111] may indicate a pattern in which no unused CG PUSCH exists within time interval T.

[0312] The UE may indicate the number of unused CG PUSCHs in each time unit. For example, the UE may indicate a value X indicating the number of unused CG PUSCHs included in each time unit from the start of the time interval T, and the UE and BS may assume that the last X transmission opportunities in each time unit are unused CG PUSCH resources.

[0313] When using implementations 1-3, if the size of the URI is 0, for example, if there is no valid CG PUSCH within time interval T or if there is no CG PUSCH, the UE can transmit only the CG PUSCH without the URI.

[0314] <1-3-1>

[0315] Using implementations 1-3, the UE can indicate CG PUSCH transmission opportunities from the start point to the end point of the time interval T. The time interval T can be a unit of the transmission opportunity itself, or can represent an absolute time range. In particular, when the transmission opportunity itself is used as a unit, the time interval from the first URI transmission to the next transmission is not fixed, but can vary according to the transmission opportunity interval given by the CG setting. In this case, even if an upcoming transmission opportunity is indicated, the BS cannot reflect this, and such information may be wasted. Therefore, to reduce this overhead, the following method can be used to determine transmission opportunities and time ranges excluded from actual URI information, and a time range or transmission opportunities within this range reflected in the actual URI information excluding this can be determined. The excluded transmission opportunities and the time range including them are referred to as T. excl Then, T is calculated by the following method. excl can be determined.

[0316] First, T excl The start point of the URI may be the end point of the last symbol of the radio resource (e.g., CG-PUSCH) on which the URI is transmitted, or the start point of the time interval T if it is earlier than the start point of the time interval T. In other words, the earlier of these may be T excl This could be the start of

[0317] Next, T excl The end point can be determined in the following ways:

[0318] > T excl The end point of the URI is a certain time interval T from the end point of the last symbol of the radio resource (e.g., CG-PUSCH) on which the URI is transmitted. proc,URI The time may be separated by a certain amount of time.

[0319] > If the URI is transmitted on CG PUSCH, T excl The end point of may be the start of the next closest CG PUSCH start symbol in the radio resource (eg, CG-PUSCH) on which the URI is transmitted.

[0320] > If the URI is transmitted on CG PUSCH, T excl The end point of the URI is a certain time interval T from the start or end of the next closest CG PUSCH start symbol in the radio resource (e.g., CG-PUSCH) where the URI is transmitted. proc,URI It may just be the time before.

[0321] > Said T excl The end point of the URI is a certain time interval T proc,URI Alternatively, the CG PUSCH may be located at a time separated by a certain time interval T proc,URI The time may be separated by a certain amount of time.

[0322] > the given time interval T proc,URI The predetermined time interval T may be a time required for the BS to reschedule the uplink radio resource designated as an unused resource by the URI after the URI transmission. proc,URImay be a value provided by the BS via L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling), may be a predefined value, or may be a value determined by the BS based on the associated UE capabilities. As an example, as described in 3GPP TS 38.214, the value N1 or N2 may be used to determine the time required for the PUCCH or PUSCH preparation process, taking into account the UE capabilities and the SCS of the UL BWP, or the time T calculated from this value. proc,1 or T proc,2 T proc,URI More specifically, this value can be used to determine T proc,URI may be used as a constant fraction of the value T proc,URI It may also be used as

[0323] T determined above excl overlaps with a portion of a PUSCH transmission opportunity, the following can be considered:

[0324] > time range T excl Other CG transmission occasions (to which the URI applies, i.e., the CG setting to which the URI applies) that overlap by at least one symbol with the time range T excl Other CG transmission opportunities that overlap with at least one symbol (to which the URI applies) may be excluded from being subject to availability indicated by the URI.

[0325] > time range T excl Other CG transmission opportunities (i.e., CG PUSCH occasions) that do not overlap (at least one symbol) with the time interval or radio resource indicated as unused (to which the URI applies) may be included in the URI indication, i.e., the transmission opportunity may be excluded from the URI indication only if all symbols of the other CG transmission opportunity overlap with the time interval or radio resource indicated as unused.

[0326] > time range T exclOther CG transmission opportunities that overlap (to which the URI applies) with a predetermined number X or more of symbols can be excluded from the URI indication. The number of symbols X may be a value defined by L1 signaling and / or higher layer signaling of the BS, or may be a predefined value, or may be derived from the length of the CG transmission opportunity to which the URI applies (i.e., the number of OFDM symbols belonging to the CG transmission opportunity). As an example, if the length of the CG transmission opportunity to which the URI applies is L, more than ceil(L / N) (e.g., N=2 or 1.5) symbols fall within the time range T excl If there is an overlap with the CG transmission opportunity, the CG transmission opportunity may be excluded from the URI indication.

[0327] <Realization 1-4: When to transmit Unused CG resource indication>

[0328] If a URI containing information on whether one or more CG PUSCHs are unused is transmitted on the CG PUSCH, the UE does not need to transmit the URI for each CG PUSCH. In this case, the UE can minimize the overhead caused by the URI by transmitting the URI at a position determined as follows, and enable the BS to simultaneously determine whether multiple CG PUSCHs are unused.

[0329] > The UE may transmit a URI at the first CG PUSCH occasion of each period. If the UE has no UL-SCH to transmit at the first CG PUSCH occasion of each period, the UE may transmit a CG PUSCH containing only a URI without a UL-SCH. This may be limited to the case where the CG configuration field startingFromRV0-r16, which is used to determine the initial transmission occasion of the TB for a given redundancy version (RV) sequence, is set to "on".

[0330] The UE may transmit the URI in the last transmission of each period.

[0331] > The UE may send the URI in the first transmission of each period, which may be only if the field startingFromRV0-r16 in the CG configuration is set to "on".

[0332] <Realization 1-5: Where to apply unused CG resource indication>

[0333] In the operation described in embodiment 1, the CG configuration of the CG PUSCH in which the URI is transmitted may differ from the CG configuration to which the URI is applied. For example, a specific CG PUSCH configuration (e.g., a CG configuration with index A) can configure 1) whether the UE transmits a URI through the CG PUSCH, and 2) which CG PUSCH configuration (e.g., a CG configuration with index B) the URI indicates unused resource information for. As a result, the UE can operate to indicate / transmit unused resource information for CG PUSCH configuration index B through the URI on the CG PUSCH with CG PUSCH configuration index A. To achieve this, the following can be considered.

[0334] > Each CG setting may include whether or not a URI is transmitted on the CG PUSCH of that CG setting and / or one or more CG setting indexes for receiving that URI (i.e., the CG setting index of the CG PUSCH used to carry the URI).

[0335] >> If the CG setting does not include another CG setting index that receives the URI (i.e., the CG setting index for the CG PUSCH used to carry the URI), the URI may be applied only to the CG setting.

[0336] >> Alternatively, it may be assumed that the CG setting is always included in one or more CG setting indexes that receive the URI. If a URI is transmitted in a CG PUSCH of a certain CG setting X, it is always assumed that the URI applies to the CG PUSCH of CG setting X, even if CG setting X is not explicitly included in the CG setting list that the URI is targeted for.

[0337] > Each CG setting may include whether or not a URI is transmitted on the CG PUSCH for that CG setting and / or one or more CG setting indices (i.e., CG setting indices of the CG PUSCH used to carry the URI for that CG setting) to which the CG setting refers (or does not refer) to a URI.

[0338] >> If the CG setting does not contain another CG setting index that references a URI, then the URI may apply only to the CG setting.

[0339] >> Alternatively, it can be assumed that the CG configuration is always included in one or more CG configuration indices that refer to a URI. It can be assumed that the CG configuration of a CG PUSCH that carries a URI for a CG configuration always includes its own CG configuration index, or this is the case even if there is no explicit configuration.

[0340] Alternatively, it may be assumed that a URI always relates to all CG configurations. For example, if a URI transmitted in a CG PUSCH of a certain CG configuration indicates whether a CG PUSCH is unused on a certain time interval T, it may also indicate whether the CG PUSCHs of all CG configurations configured on the time interval T are unused. That is, according to the combination of implementations 1-1 / 2 / 3 / 4 described above, if an unused CG PUSCH is reported in at least one CG configuration (i.e., on a CG PUSCH based on at least one CG configuration), it may mean that all other CG PUSCHs overlapping with the unused CG PUSCH are also assumed to be unused. For example, when a UE transmits a URI on a CG PUSCH based on a certain CG configuration, the time interval T and time unit of the URI are based on a CG PUSCH timing. If at least one CG PUSCH within a time unit is indicated as unused, the UE may use a URI indicating the time unit (including unused CG PUSCHs) as a time unit including unused CG PUSCHs.

[0341] Such an operation can be used, for example, to send information about whether or not CG settings for intermittently transmitted video traffic are in use to a URI sent on a CG setting for continuously transmitted pose data.

[0342] In the use of embodiments 1 to 5, other settings for redefining such behavior are considered. As an example, to protect CG setting B, which is used to transmit traffic with high transmission priority, from a URI-based behavior, a URI transmitted by another CG setting A as described above is assumed to apply to all CGs except for the CG setting B, or even if the CG setting B is indicated as the target of the URI to be transmitted, the URI is transmitted while ignoring it. The BS can indicate or configure such a configuration through L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling). That is, L1 signaling and / or higher layer signaling that indicates / configures indifference by the URI can be performed by a conventional DCI field / RRC parameter (e.g., priority indicator) or a new DCI field or a new RRC parameter.

[0343] In the use of embodiments 1-2, 1-3, and / or 1-5, the URI may indicate only a portion of the CG PUSCH opportunity for the time interval T determined by embodiment 1-2, or another time unit determined to indicate unused CG PUSCH resources in that time interval T. For example, if the time unit is not aligned with the CG PUSCH opportunity and the time unit determined for the URI overlaps only a portion of the CG PUSCH opportunity, the URI may indicate only the overlapping portion. For example, if the URI indicates used / unused resources for a set of symbols #0 to #6 and a set of symbols #7 to #13 in a slot, and a CG PUSCH occupies symbols #4 to #10 in the slot, the URI may indicate use / unused for some of the overlapping symbols. Alternatively, if URI applicability is possible between CG configurations as described in embodiments 1-5, the time interval and time unit of the CG transmission may indicate only a portion of the PUSCH transmission opportunity of another CG configuration. In such cases, the unused resources may be determined taking the following into consideration.

[0344] > A time interval indicated by the URI as unused or another CG transmission opportunity (to which the URI is applied) that overlaps with at least one symbol of a radio resource indicated (directly) as unused can be treated as being designated as unused. That is, a PUSCH opportunity based on another CG configuration that overlaps with a time interval indicated by the URI as unused or with at least one symbol of a radio resource indicated (directly) as unused and whose use / unused status is indicated by the URI can be treated as being designated as unused.

[0345] > Any other CG transmission opportunity (to which the URI applies) that does not overlap with at least one symbol a time interval or radio resource that the URI indicates as unused, or (directly) an unused radio resource, may be treated as not being designated as unused, i.e., it may be determined to be unused only if all symbols of the other CG transmission opportunity overlap with a time interval or radio resource that the URI indicates as unused.

[0346] Other CG transmission opportunities (to which the URI is applied) that overlap with a time interval indicated by the URI as unused or with a radio resource (directly) indicated as unused by a predetermined number X or more of symbols may be treated as being designated as unused. The number X of symbols may be defined through L1 signaling and / or higher layer signaling of the BS, may be a predefined value, or may be derived from the length of the CG transmission opportunity to which the URI is applied (i.e., the number of OFDM symbols belonging to the CG PUSCH opportunity). As an example, if the length of the CG transmission opportunity to which the URI is applied is L, and more than ceil(L / N) (e.g., N=2 or 1.5) symbols overlap with the time interval / radio resource indicated as unused by the URI, the CG transmission opportunity may be determined as unused.

[0347] The UE may determine that the time interval indicated by the URI as unused or the radio resource indicated (directly) as unused is unused, and may not transmit PUSCH in that symbol. In other CG transmission opportunities (to which the URI applies) that overlap with at least one symbol, the UE may either stop transmission from the first symbol indicated as unused (i.e., the first symbol of the other CG transmission opportunity that overlaps with the time interval / radio resource indicated as unused by the URI) or allow transmission up to the first symbol indicated as unused (i.e., up to just before the first symbol that overlaps with the time interval / radio resource indicated as unused by the URI).

[0348] <Implementation 2: UL multiplexing of unused CG resource indication>

[0349] In the first embodiment, it may be considered that the UE transmits a K-bit URI including information on whether a future CG PUSCH is unused to the BS. Such a URI may be multiplexed and transmitted on the CG PUSCH as described above. In particular, when the URI is transmitted in the form of piggybacked UCI, it is necessary to consider a method for multiplexing the URI with other UCI that needs to be transmitted on the PUSCH. In this case, the following methods may be considered.

[0350] *Method 1: The URI can be assumed to be a type of CG-UCI. For example, it can be treated and multiplexed as the CG-UCI described in 3GPP TS 38.212. The CG configuration for a shared spectrum includes a higher layer parameter, cgRetransmissionTimer. If the UE fails to receive a CG-downlink feedback information (CG-DFI) providing HARQ-ACK information for the initial transmission of a TB on a PUSCH configured by the CG configuration before the expiration of the cgRetransmissionTimer, the UE considers the TB not to have been correctly decoded and performs an automatic retransmission at the next CG PUSCH opportunity based on the CG configuration. A UCI called CG-UCI can be included in each CGPUSCH transmission, where the CG-UCI includes shared information regarding an HARQ process ID, an RV, a new data indicator (NDI), and a channel occupancy time (COT). If another CG-UCI is already included in the PUSCH, the URI is treated as an additional bit field included in the CG-UCI, and the UE concatenates the URI with a bit sequence generated based on the other CG-UCI and multiplexes it into one CG-UCI. This may be limited to cases where the UE uses an unlicensed band, i.e., when a CG-UCI is always included in the CG PUSCH to transmit a CG PUSCH. That is, the URI may be multiplexed and transmitted together with the HARQ-ACK. For example, as with the CG-UCI described in 3GPP TS 38.212, if there is no other HARQ-ACK in the PUSCH, the URI is multiplexed onto the PUSCH in the same manner as the HARQ-ACK, except for the URI. If another HARQ-ACK is included in the PUSCH, the URI is jointly coded with the HARQ-ACK and multiplexed onto the PUSCH as one coded bit sequence.

[0351] *Method 2: The URI can be treated as CSI Part 1 and multiplexed onto the PUSCH. For example, among the CSIs described in 3GPP TS 38.212, the URI can be treated as CSI Part 1 and multiplexed. If other CSI is already included in the PUSCH, the UE can concatenate the URI with the bit sequence of CSI Part 1 of the CSI and multiplex it onto the PUSCH as one CSI Part 1. In some implementations, this may be limited to cases where the UE is not using an unlicensed band, i.e., no CG-UCI other than the URI is included in the CG PUSCH to transmit the CG PUSCH. In some implementations, this may also be limited to cases where the size of the URI is always fixed.

[0352] *Method 3: The URI can be treated as CSI Part 2 and multiplexed onto the PUSCH. For example, among the CSIs described in 3GPP TS 38.212, the URI can be treated as CSI Part 2 and multiplexed onto the PUSCH. If another CSI Part 2 already needs to be included in the PUSCH, the UE can drop the CSI Part 2 and replace it with the URI as CSI Part 2 to include on the PUSCH, or can concatenate the bit sequence of the CSI Part 2 with the URI and multiplex it onto the PUSCH as one CSI Part 2. To achieve this, an indicator indicating the length of the URI can be included in CSI Part 1. This may be limited to cases where the UE is not using an unlicensed band, i.e., where the CG PUSCH does not include any CG-UCI other than the URI.

[0353] As described above, the UE can use either Method 1 or Method 2 / 3 depending on whether it uses an unlicensed band, or the UE can report capability information related to Methods 1 / 2 / 3 to the BS, and the BS can set any of Methods 1 / 2 / 3 based on the capability report.

[0354] Each UE may have different capabilities for including the CG-UCI and URI in the PUSCH. For example, in a conventional NR wireless communication system, UEs may be capable of jointly encoding the HARQ-ACK and CG-UCI, multiplexing them on the PUSCH or PUCCH, and transmitting them. Each UE may notify the network / BS of its capabilities through a capability report. A UE capable of this operation processes the multiplexed UCI and transmits them, while a UE incapable of this operation or a UE configured by the BS not to perform this operation transmits the PUCCH of the HARQ-ACK and drops the CG-UCI and the associated CG PUSCH. This is because transmission of the CG-UCI is essential for transmitting the CG PUSCH in an unlicensed band. Meanwhile, a URI according to some embodiments of the present invention may have a similar format and transmission method to the CG-UCI, but may not be essential for transmitting the CG PUSCH. In particular, when a UE uses NR wireless communication through a licensed band, the BS can successfully receive the PUSCH without receiving the URI transmitted from the UE. In such cases, even if it is not possible to jointly code the CG-UCI alone or jointly code the CG-UCI and other UCI, there is less need to drop PUSCH transmissions.

[0355] Therefore, in unlicensed bands (i.e., shared spectrum) and licensed bands, more precisely, when CG-UCI that is essential for CG PUSCH transmission is multiplexed with a URI and transmitted (e.g., when the upper layer parameter cg-RetransmissionTimer is set), and when CG-UCI that is not essential for CG PUSCH transmission (i.e., a CG-UCI that is not essential for CG PUSCH transmission) or a URI multiplexed with it or a URI transmitted alone (e.g., when the upper layer parameter cg-RetransmissionTimer is not set), if additional multiplexing or joint coding with other UCI (e.g., HARQ-ACK) is required, the UE can perform different operations as follows.

[0356] > When CG-UCI, which is required for CG PUSCH transmission, is multiplexed with URI and transmitted as one UCI, for example, when the higher layer parameter cg-RetransmissionTimer is configured.

[0357] >> A UE that can jointly encode CG-UCI and other UCI (e.g., HARQ-ACK) that needs to be multiplexed (or a UE configured to perform joint encoding) can perform at least one of the following operations.

[0358] >>> The CG-UCI, URI, and HARQ-ACK are jointly coded as one UCI, and then multiplexed into the CG PUSCH as one UCI for transmission. This may be limited to cases where the UE is capable of such joint coding, especially when no other UCI (e.g., SR, CSI, etc.) is present. If the UE is capable of jointly coding the CG-UCI, URI, and HARQ-ACK as one UCI, as described above, it can send a capability report to the BS indicating this.

[0359] >>> CG-UCI and HARQ-ACK are jointly encoded as one UCI, multiplexed onto CG PUSCH as one UCI, and transmitted. URI is dropped and not transmitted. This maintains the previous operation, but allows URI to be transmitted when HARQ-ACK is not transmitted.

[0360] >>> Do not transmit CG PUSCH, drop CG-UCI and URI, and transmit HARQ-ACK on PUCCH. This is applicable when CG-UCI is pre-encoded with URI and it is difficult to multiplex HARQ-ACK, or when it is difficult to multiplex CG-UCI and HARQ-ACK.

[0361] >> A UE that cannot jointly code CG-UCI and other UCI (e.g., HARQ-ACK) (or is configured not to perform joint coding) can perform at least one of the following operations:

[0362] >>> Do not transmit CG PUSCH, drop CG-UCI and URI, and transmit HARQ-ACK on PUCCH.

[0363] > When a CG-UCI that is not required for transmission, or a UCI in which such a CG-UCI and a URI are multiplexed, or a URI is transmitted, for example, when the higher layer parameter cg-RetransmissionTimer is not configured.

[0364] >> A UE that can jointly encode CG-UCI and other UCI (e.g., HARQ-ACK) that needs to be multiplexed (or a UE configured to perform joint encoding) can perform at least one of the following operations:

[0365] >>> The CG-UCI, URI, and HARQ-ACK are jointly coded as one UCI, and then multiplexed into the CG PUSCH as one UCI for transmission. This may be limited to cases where the UE is capable of such joint coding, especially when no other UCI (e.g., SR, CSI, etc.) is present. If the UE is capable of jointly coding the CG-UCI, URI, and HARQ-ACK as one UCI, as described above, it can send a capability report to the BS indicating this.

[0366] >>> The CG-UCI or URI is jointly encoded with the HARQ-ACK as one UCI, and then multiplexed and transmitted as one UCI on the CG PUSCH. Any other URIs or CG-UCI that are not multiplexed are dropped and not transmitted. This maintains the conventional operation while allowing the URI to be transmitted when the HARQ-ACK is not transmitted. Which UCI of the CG-UCI and URI is multiplexed with the HARQ-ACK and transmitted on the CG-PUSCH may be predefined or may be notified to the UE via L1 signaling or higher layer signaling from the BS.

[0367] >>> Do not transmit CG PUSCH, drop CG-UCI and URI, and transmit HARQ-ACK on PUCCH. This is applicable when CG-UCI is pre-encoded with URI and it is difficult to multiplex HARQ-ACK, or when it is difficult to multiplex CG-UCI and HARQ-ACK.

[0368] >> A UE that cannot jointly encode CG-UCI and other UCI (e.g., HARQ-ACK) (or a UE that is configured not to perform joint encoding) can perform at least one of the following operations:

[0369] >>> Transmit CG-PUSCH multiplexed with HARQ-ACK. Drop CG-UCI and URI. Unlike conventional methods, if the UE cannot perform joint coding, it can transmit HARQ-ACK on CG PUSCH.

[0370] >>> Do not transmit CG PUSCH, drop CG-UCI and URI, and transmit HARQ-ACK on PUCCH.

[0371] > When CG-UCI and URI, which are necessary for CG PUSCH transmission, are coded separately and transmitted as their respective UCIs

[0372] >> A UE that can jointly encode CG-UCI and other UCI (e.g., HARQ-ACK) (or a UE configured to perform joint encoding) can perform at least one of the following operations.

[0373] >>> The CG-UCI, URI, and HARQ-ACK are jointly coded as one UCI, and then multiplexed into the CG PUSCH as one UCI for transmission. This may be limited to cases where the UE is capable of performing such joint coding, especially when no other UCI (e.g., SR, CSI, etc.) is present. If the UE can jointly code the CG-UCI, URI, and HARQ-ACK as one UCI as described above, it can send a capability report to the BS indicating this.

[0374] >>> CG-UCI and HARQ-ACK are jointly encoded as one UCI, multiplexed into CG PUSCH as one UCI, and transmitted. URI is dropped and not transmitted. This maintains the conventional operation, but allows URI to be transmitted when HARQ-ACK is not transmitted.

[0375] >>> Do not transmit CG PUSCH, drop CG-UCI and URI, and transmit HARQ-ACK on PUCCH. This is applicable when CG-UCI is pre-encoded with URI and it is difficult to multiplex HARQ-ACK, or when it is difficult to multiplex CG-UCI and HARQ-ACK.

[0376] >> A UE that cannot jointly encode CG-UCI and other UCI (e.g., HARQ-ACK) (or a UE that is configured not to perform joint encoding) can perform at least one of the following operations:

[0377] >>> If no additional UCI multiplexing is required (e.g., only a single type of UCI (e.g., HARQ-ACK) is involved), drop the URI and transmit only CG-UCI on the PUSCH.

[0378] >>> If there is a HARQ-ACK that needs to be multiplexed, do not transmit CG PUSCH, drop CG-UCI and URI, and transmit HARQ-ACK on PUCCH.

[0379] In cases where the CG-UCI is used for another purpose, such as to indicate the NDI of each transmission, the value included in the CG-UCI may be fixed to a specific value when the CG-UCI is dropped. For example, when the CG-UCI is dropped, the NDI value is always assumed to be 0.

[0380] As another example, when using embodiment 1, it is possible for the UE to transmit to the BS on another PUCCH the URI of K-bit information including information on whether or not a future CG PUSCH opportunity will be used. In this case, it is necessary to consider a method of multiplexing with other UCI that needs to be transmitted on the PUCCH. In this case, the following methods are considered.

[0381] > URIs can be treated as SRs and multiplexed in the PUCCH, i.e., URIs can be multiplexed in the PUCCH in a similar manner to how SRs are transmitted on the PUCCH as described in 3GPP TS 38.212.

[0382] In such a case, in some implementations, if the URI is multiplexed with other UCIs, it may be transmitted with multiple bit sizes.

[0383] In such a case, in some implementations, if there is no other UCI and only the URI is transmitted on the PUCCH, if the URI is 2 bits or more, it is treated as a HARQ-ACK, and the URI can be multiplexed into the PUCCH in a manner similar to the method for transmitting a HARQ-ACK on the PUCCH described in 3GPP TS 38.212.

[0384] In such a case, in some implementations, when no other UCI is present and only the URI is transmitted on the PUCCH, the URI may be 1-bit information to indicate whether the entire CG PUSCH time associated with the URI is used or not. For example, when the URI indicates use / non-use for a time interval T, in this situation, the URI may be 1-bit to indicate whether the entire time interval T is used or not.

[0385] In some implementations, in a situation where a UE does not have the capability of joint coding of URI and HARQ-ACK, or where joint coding is not configured for a UE that has such capability, if a specific CG PUSCH includes a URI (without the conventional CG-UCI) and overlaps in time with a HARQ-ACK PUCCH, the UE may operate to multiplex and transmit the HARQ-ACK on the CG PUSCH while omitting (or dropping) the URI transmission.

[0386] Considering implementation 1, in some implementations, the size of the URI information may be 2 bits or less, or when the URI and HARQ-ACK are jointly encoded, the total size of the URI and HARQ-ACK information (i.e., the result of the joint encoding) may be 2 bits or less. In such cases, at least one of the following may be considered:

[0387] > When transmitting a URI of 2 bits or less, or when jointly encoding the URI and HARQ-ACK, if the total size of the URI and HARQ-ACK information is 2 bits or less, the UE can transmit UCI by puncturing the PUSCH at a fixed position, just as when transmitting a conventional HARQ-ACK of 2 bits or less. The BS can receive / acquire UCI based on this assumption.

[0388] > When transmitting a URI of 2 bits or less, or when jointly encoding the URI and HARQ-ACK, if the total size of the URI and HARQ-ACK information (i.e., the result of joint encoding) is 2 bits or less, the UE can transmit UCI by rate-matching the PUSCH in the same manner as transmitting a conventional HARQ-ACK of 3 bits or more. To achieve this, in some implementations, the URI or the URI and HARQ-ACK information can be padded with "0" bits to make it 3 bits or more. The BS can receive / acquire UCI assuming this.

[0389] > When transmitting a URI of 2 bits or less, the UE can exclude the URI from transmission and transmit only PUSCH and other UCI. The BS can assume this and receive / acquire UCI.

[0390] If the size of the jointly coded UCI obtained by jointly coding the URI and HARQ-ACK is 2 bits or less, the UE can exclude the URI from transmission and transmit the HARQ-ACK and other UCI on the PUSCH. The BS can receive / acquire UCI assuming this.

[0391] <Implementation 3: Two priority handling of unused CG resource indication>

[0392] When a UE transmits a URI on a PUSCH or PUCCH, especially on a PUSCH or PUCCH at a fixed position (for example, on the first CG PUSCH transmission in a period), it is possible that the transmission may be dropped by other uplink transmissions, especially by PUCCHs or PUSCHs with higher priority. In such a case, the BS may not be able to receive the URI at a given time. In this case, the following UE and BS operations are considered.

[0393] If a UE fails to transmit a certain URI, it can assume that none of the CG PUSCHs within the time interval indicated by the URI are unused are reported as unused. In this case, if a BS fails to receive a certain URI, it can assume that none of the CG PUSCHs within the time interval indicated by the URI are unused are reported as unused. The BS does not need to reschedule for that time interval.

[0394] If a UE fails to transmit a certain URI, it can assume that all CG PUSCHs within the time interval indicated by the URI as being unused are reported as unused. Therefore, the UE may not use any CG PUSCHs within that time interval. In this case, if a BS fails to receive a certain URI, it can assume that all CG PUSCHs within the time interval indicated by the URI as being unused are unused. The BS can reschedule for that time interval.

[0395] <Implementation 4: URI for two codewords on CG PUSCH>

[0396] When a UE transmits a URI on a PUSCH, the CG PUSCH indicated by the URI may contain two or more codewords, i.e., two or more TBs. If the UE can transmit two or more TBs on a radio resource, the UE can choose not to use the radio resource, transmit only one TB, or transmit two TBs based on the user data arriving at the UE. By indicating these cases via the URI, the UE can inform the BS not only whether transmission will be performed on the radio resource, but also how many TBs will be transmitted. More specifically, the following can be considered:

[0397] If the CG PUSCH includes two or more codewords, i.e., two or more TBs, in a URI configured as a bitmap, the bit size corresponding to each CG PUSCH may be 2-bit. In this case, the use or non-use of the CG PUSCH may be indicated using the following bit representation:

[0398] >>> If the UE does not use the radio resource, the bit position is set to "11".

[0399] >>> If the UE transmits only one TB, the corresponding bit position is set to "01" or "10".

[0400] >>> If the number of TBs that the UE will transmit is not determined or if the UE will transmit two TBs, the corresponding bit position is set to "00".

[0401] > As another example, if a CG PUSCH in a URI configured with a bitmap includes two or more codewords, i.e., two or more TBs, each bit of each bitmap can correspond to each TB that can be transmitted on the CG PUSCH within a period.

[0402] > As another example, when transmitting a URI taking TB into consideration, MIMO-related information that the BS can assume upon reception, such as information related to a transmission layer or DMRS port, can be additionally transmitted.

[0403] <Implementation 5: URI for CG PUSCH repetition or TBoMS>

[0404] When a UE transmits a URI on a PUSCH, it is possible to repeatedly transmit one TB over multiple radio resources by repeating transmission on the PUSCH, or to transmit one TB over multiple radio resources across multiple slots (for example, TB over multiple slots (TBoMS)). TBoMS is a method introduced to solve the problem of insufficient TB size applied to the PUSCH and difficulty in properly processing the TB when the TB size is determined by the number of REs scheduled in one slot in which the PUSCH is transmitted, and one PUSCH is transmitted or processed over multiple slots. The number of slots belonging to TBoMS is set by RRC signaling numberOfSlots-TBoMS and is used to calculate the TB size used for TBoMS. With TBoMS, the TB size can be calculated based on the number of REs in the PUSCH scheduled in multiple slots.

[0405] When a UE transmits a URI on a PUSCH, if one TB is repeatedly transmitted using multiple radio resources through repeated transmission on the PUSCH, or one TB is transmitted using multiple radio resources across multiple slots, the UE can transmit the URI by regarding the multiple radio resources as one radio resource, or can transmit one URI shared by the multiple radio resources. More specifically, the following can be considered.

[0406] *Method 1-1: When repeated transmission or TBoMS is used in a URI configured with a bitmap, multiple radio resources used to transmit one TB may correspond to one bit. That is, each bit of the bitmap used as the URI can correspond to each TB that can be transmitted on the CG PUSCH within a period. That is, a set of radio resources transmitting one TB corresponds to one bit. For example, when a single TB is configured / instructed to be repeatedly transmitted across N radio resources (e.g., N PUSCHs), the entire set of N radio resources corresponds / maps to one bit on the URI. In this case, a K-bit URI on the CG PUSCH transmitting a specific TB can indicate unused information for each of the K CG PUSCH sets transmitting the other K TBs thereafter.

[0407] *Method 1-2: As in Implementation 1, one radio resource may correspond to one bit. That is, each bit of the bitmap may correspond to each CG PUSCH radio resource in the interval. For example, if a single TB is configured / instructed to be repeatedly transmitted over N radio resources (e.g., N PUSCHs), each single radio resource may correspond / map to one bit on the URI.

[0408] In some implementations, the UE may transmit URIs only for valid (i.e., transmittable) radio resources. For example, considering the following content of Section 11.1 of 3GPP TS 38.213, URI information may be transmitted only for transmittable radio resources. In this case, when using Method 1-1, if at least one PUSCH is transmittable among multiple radio resources used to transmit one TB, URI information for the TB may be generated. That is, when using Method 1-1, the bitmap may be information indicating whether or not to transmit a TB that is transmittable on at least one valid radio resource.

[0409] [Table 7]

[0410] When the UE transmits a URI to the BS via UCI piggybacked on the CG PUSCH as in embodiment 1-1, the CG PUSCH may be repeatedly transmitted. If repeated transmission is configured for the CG PUSCH on which the URI is transmitted, the following can be considered for transmitting the URI.

[0411] *Method 2-1: It is possible that the URI is included in all repeated transmissions and transmitted. For example, if it is configured / instructed to repeatedly transmit a single TB across N radio resources (e.g., N PUSCHs), the URI can be transmitted on each of these N radio resources.

[0412] *Method 2-2: It is possible that the URI is included only in a specific repeat transmission (e.g., the first repeat transmission) of a repeat transmission bundle that transmits a single TB. For example, when it is configured / instructed to repeatedly transmit a single TB across N radio resources (e.g., N PUSCHs), the URI is transmitted only on a specific radio resource (e.g., the first) among the N radio resources, and transmission of the URI is omitted on the remaining radio resources.

[0413] When transmitting a URI for the same TB or the same PUSCH time in a repeated transmission, the UE may assume that the same URI will always be transmitted during the repeated transmission. For example, in a repeated transmission bundle in which one TB is transmitted, the UE may generate and transmit a URI value by estimating whether or not a TB transmission or PUSCH time is used before the first URI transmission, and may always transmit the same URI value in subsequent URI transmissions without any additional estimation. By combining Method 1 and Method 2, the UE may transmit a URI on a CG PUSCH configured for repeated transmission. For example, when a URI is transmitted in all repeated transmissions as in Method 2-1, the UE may indicate whether or not each radio resource in the repeated transmission bundle is used using Method 1-2, or may indicate whether or not the entire repeated transmission bundle is used using one bit per repeated transmission bundle using Method 1-1. Furthermore, when indicating whether or not each radio resource in the repeated transmission bundle is used using Method 1-2, as described above, the URI value transmitted on each radio resource in the repeated transmission bundle may always be the same.

[0414] In some implementations, the UE can refer to another RRC parameter value to select between Method 1-1 and Method 1-2. For example, it can refer to the parameter startingFromRV0 in the IE ConfiguredGrantConfig. If this value is "off," the UE always starts transmission only in the first transmission of a repeated transmission bundle to transmit a TB. Therefore, when transmitting the TB, the UE always uses the first radio resource. In this case, even if the URI is included only in the first repeated transmission using Method 1-1, one URI per TB is always transmitted. On the other hand, if the value of startingFromRV0 is "on," the UE may start transmission from the middle of a repeated transmission bundle. In this case, the BS cannot predict the UE's transmission start position and must transmit a URI every time, as in Method 1-2. Taking this into consideration, it is possible to use Method 1-1 when the value of the parameter startingFromRV0 is "off" and use Method 1-2 when the value is "on."

[0415] As another example, either Method 2-1 or Method 2-2 is used depending on the total size X of the URI bitmap and the number of repeated transmissions of the CG PUSCH (or the number of CG PUSCHs in a period) Y. For example, if X>Y, Method 2-1 is used, and if Y≧X, Method 2-2 is used.

[0416] According to some embodiments of the present invention, a UE can selectively use a CG PUSCH as in the conventional method and report unselected radio resources to a BS in advance. According to some embodiments of the present invention, actual use or non-use of radio resources scheduled for a UE can be efficiently reported to a BS. According to some embodiments of the present invention, the BS can use the radio resources for other uplink transmissions, thereby reducing the burden on uplink radio resources and effectively transmitting various services or information such as video whose traffic payload size changes dynamically.

[0417] FIG. 13 illustrates an example of a flow of UE uplink signal transmission according to some embodiments of the present invention.

[0418] A UE may perform operations according to some embodiments of the present invention in connection with uplink signal transmission. The UE includes at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some embodiments of the present invention. A processing device for a UE includes at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some embodiments of the present invention. A computer-readable (non-transitory) storage medium stores at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some embodiments of the present invention. A computer program or computer program product is recorded on at least one computer-readable (non-transitory) storage medium and includes instructions that, when executed, cause (at least one processor) to perform operations according to some embodiments of the present invention.

[0419] 13, the UE method, or the operations of the UE, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, include: receiving a CG configuration (S1301); and transmitting a first CG PUSCH including a UTO-UCI (e.g., a URI described in embodiments 1 to 5) at a first CG PUSCH opportunity based on the CG configuration (S1303). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. Each of the N bits of the N-bit bitmap is one-to-one mapped to the N CG PUSCH occasions subsequent to the first PUSCH occasion, where each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion (i.e., indicates that the UE may transmit a CG PUSCH at the CG PUSCH occasion), and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0420] In some implementations, N is a value provided by higher layer signaling from the BS.

[0421] In some implementations, N is a value provided for the CG setting.

[0422] In some implementations, the subsequent N CG PUSCH occasions to which the N bits of the N-bit bitmap are one-to-one mapped exclude non-valid PUSCH occasions.

[0423] In some implementations, the invalid CG PUSCH timing is a CG PUSCH timing that overlaps with a symbol indicated as uplink by the TDD uplink-downlink configuration (e.g., the RRC parameter tdd-UL-DL-ConfigurationCommon and / or the RRC parameter tdd-UL-DL-ConfigurationDedicated).

[0424] In some implementations, the invalid CG PUSCH occasions are CG PUSCH occasions that overlap with symbols of a synchronization signal / physical broadcast channel block (e.g., symbols of an SS / PBCH block at an index provided by the RRC parameter ssb-PositionsInBurst).

[0425] In some implementations, the method or operation further includes: based on the presence of HARQ-ACK information to be transmitted in the first CG PUSCH occasion, jointly encoding the HARQ-ACK information and the UTO-UCI to obtain jointly encoded bits, and mapping the jointly encoded bits to the first CG PUSCH by rate matching.

[0426] In some implementations, the method or operation includes: not transmitting a CG PUSCH in a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

[0427] FIG. 14 illustrates an example of a flow chart of uplink signal reception by a BS according to some embodiments of the present invention.

[0428] The BS may perform operations according to some embodiments of the present invention in connection with receiving uplink signals. The BS includes at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some embodiments of the present invention. The processing device for the BS includes at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some embodiments of the present invention. A computer-readable (non-transitory) storage medium stores at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some embodiments of the present invention. A computer program or computer program product is stored on at least one computer-readable (non-transitory) storage medium and includes instructions that, when executed, cause (at least one processor) to perform operations according to some embodiments of the present invention.

[0429] 14, in the BS method, or in the BS, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations include: transmitting a CG configuration (S1401); and receiving a first CG PUSCH including a UTO-UCI (e.g., a URI described in embodiments 1 to 5) from a UE at a first CG PUSCH occasion based on the CG configuration (S1403). The UTO-UCI includes the N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are mapped one-to-one to the N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value, where the first bit value indicates that the UE can transmit a CG PUSCH at the CG PUSCH occasion (i.e., indicates that the UE may transmit a CG PUSCH at the CG PUSCH occasion), and the second bit value indicates that the UE will not transmit a CG PUSCH at the CG PUSCH occasion.

[0430] In some implementations, N is a value provided by higher layer signaling from the BS.

[0431] In some implementations, N is a value provided for the CG setting.

[0432] In some implementations, the subsequent N CG PUSCH occasions to which the N bits of the N-bit bitmap are one-to-one mapped exclude non-valid PUSCH occasions.

[0433] In some implementations, the invalid CG PUSCH timing is a CG PUSCH timing that overlaps with a symbol indicated as uplink by the TDD uplink-downlink configuration (e.g., the RRC parameter tdd-UL-DL-ConfigurationCommon and / or the RRC parameter tdd-UL-DL-ConfigurationDedicated).

[0434] In some implementations, the invalid CG PUSCH occasions are CG PUSCH occasions that overlap with symbols of a synchronization signal / physical broadcast channel block (e.g., symbols of an SS / PBCH block at an index provided by the RRC parameter ssb-PositionsInBurst).

[0435] In some implementations, the method or operations include obtaining, on the first PUSCH based on the presence of HARQ-ACK information to be received at the first CG PUSCH occasion, jointly coded bits for the HARQ-ACK information and the UTO-UCI, and the method or operations include: assuming that the jointly coded bits are mapped to the first CG PUSCH by rate matching.

[0436] In some implementations, the method or operation includes: not expecting CG PUSCH reception in a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

[0437] The above-disclosed examples of the present invention are provided to enable those skilled in the art to embody and practice the present invention. Although the present invention has been described above with reference to preferred embodiments, those skilled in the art can make various modifications and variations to the present invention. Therefore, the present invention is not intended to be limited to the embodiments disclosed herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0438] Implementations of the present invention may be used in a BS or user equipment, or other equipment, in a wireless communication system.

[0439] [Claims at the time of international application] [Claim 1] A method for transmitting an uplink signal by a user equipment (UE) in a wireless communication system, comprising: receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) occasion including unused transmission occasion uplink control information (UTO-UCI) based on the CG configuration; the UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; the first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH opportunity. [Claim 2] 2. The uplink signal transmission method according to claim 1, wherein N is a value provided by higher layer signaling. [Claim 3] The uplink signal transmission method according to claim 2 , wherein N is provided for the CG configuration. [Claim 4] 2. The uplink signal transmission method according to claim 1, wherein the subsequent N CG PUSCH occasions to which the N bits of the N-bit bitmap are one-to-one mapped exclude invalid PUSCH occasions. [Claim 5] 5. The uplink signal transmission method of claim 4, wherein the invalid CG PUSCH occasion is a CG PUSCH occasion that overlaps with a symbol designated as an uplink by a time division duplex (TDD) uplink-downlink configuration. [Claim 6] The uplink signal transmission method according to claim 4, wherein the invalid CG PUSCH occasions are CG PUSCH occasions that overlap with symbols of a synchronization signal / physical broadcast channel block. [Claim 7] Based on the presence of HARQ-ACK information to be transmitted in the first CG PUSCH occasion, jointly encoding the HARQ-ACK information and the UTO-UCI to obtain jointly coded bits; and The uplink signal transmission method according to claim 1 , further comprising: mapping the jointly coded bits to the first CG PUSCH by rate matching. [Claim 8] The uplink signal transmission method according to claim 1 , further comprising: not transmitting a CG PUSCH in a CG PUSCH opportunity mapped to a bit having a second value among the N bits. [Claim 9] 1. In a wireless communication system, a user equipment (UE) configured to transmit an uplink signal, comprising: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and having instructions stored therein; the instructions, when executed, cause the at least one processor to perform an action; The operation is receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) occasion including unused transmission occasion uplink control information (UTO-UCI) based on the CG configuration; the UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; the first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH occasion. [Claim 10] A processing device in a wireless communication system, comprising: at least one processor; and at least one computer memory operatively connected to the at least one processor and having instructions stored therein; the instructions, when executed, cause the at least one processor to perform an action; The operation is receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) occasion including unused transmission occasion uplink control information (UTO-UCI) based on the CG configuration; the UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that a user equipment (UE) can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE will not transmit a CG PUSCH in the CG PUSCH occasion. [Claim 11] A computer-readable storage medium, comprising: the storage medium is configured to store at least one program code including instructions that, when executed, cause at least one processor to perform operations; The operation is receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) occasion including unused transmission occasion uplink control information (UTO-UCI) based on the CG configuration; the UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that a user equipment (UE) can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE will not transmit a CG PUSCH in the CG PUSCH occasion. [Claim 12] A method for a base station (BS) receiving an uplink signal from a user equipment (UE) in a wireless communication system, comprising: Sending configured grant (CG) settings; and receiving a first CG physical uplink shared channel (PUSCH) occasion including unused transmission occasion uplink control information (UTO-UCI) based on the CG configuration; the UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; the first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH opportunity. [Claim 13] 1. A base station (BS) in a wireless communication system configured to receive an uplink signal from a user equipment (UE), comprising: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and having instructions stored therein; the instructions, when executed, cause the at least one processor to perform an action; The operation is Sending configured grant (CG) settings; and receiving a first CG physical uplink shared channel (PUSCH) occasion including unused transmission occasion uplink control information (UTO-UCI) based on the CG configuration; the UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; the first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The base station, wherein the second bit value indicates that the UE will not transmit a CG PUSCH in the CG PUSCH opportunity. [Claim 14] The base station of claim 13, wherein N is a value provided by higher layer signaling of the BS. [Claim 15] 15. The base station of claim 14, wherein N is a value provided by higher layer signaling. [Claim 16] The base station of claim 13, wherein the subsequent N CG PUSCH occasions to which the N bits of the N-bit bitmap are one-to-one mapped exclude non-valid PUSCH occasions. [Claim 17] 17. The base station of claim 16, wherein the invalid CG PUSCH occasions are CG PUSCH occasions that overlap with symbols designated as uplink by a time division duplex (TDD) uplink-downlink configuration. [Claim 18] 17. The base station of claim 16, wherein the non-valid CG PUSCH occasions are CG PUSCH occasions that overlap with symbols of a synchronization signal / physical broadcast channel block. [Claim 19] The operations include: obtaining jointly coded bits for the HARQ-ACK information and the UTO-UCI on the first PUSCH based on the presence of HARQ-ACK information to be received at the first CG PUSCH occasion; The base station according to claim 13, wherein the jointly coded bits are mapped to the first CG PUSCH by rate matching. [Claim 20] The base station of claim 13 , wherein the operation includes: not expecting to receive a CG PUSCH in a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

Claims

1. 1. A method for transmitting an uplink signal by a user equipment (UE) in a wireless communication system, comprising: receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission occasion uplink control information (UTO-UCI) in a first CG PUSCH occasion based on the CG configuration; The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH opportunity.

2. 2. The uplink signal transmission method according to claim 1, wherein N is a value provided by higher layer signaling.

3. The uplink signal transmission method according to claim 2 , wherein N is provided for the CG configuration.

4. The uplink signal transmission method of claim 1, wherein the subsequent N CG PUSCH occasions to which the N bits of the N-bit bitmap are one-to-one mapped exclude invalid PUSCH occasions.

5. 5. The uplink signal transmission method according to claim 4, wherein the invalid CG PUSCH timing is a CG PUSCH timing that overlaps with a symbol designated as an uplink by a time division duplex (TDD) uplink-downlink configuration.

6. The uplink signal transmission method according to claim 4 , wherein the invalid CG PUSCH occasion is a CG PUSCH occasion that overlaps with a symbol of a synchronization signal / physical broadcast channel block.

7. Based on the presence of HARQ-ACK information to be transmitted in the first CG PUSCH occasion, Jointly encoding the HARQ-ACK information and the UTO-UCI to obtain jointly coded bits; and The uplink signal transmission method of claim 1 , further comprising: mapping the jointly coded bits to the first CG PUSCH by rate matching.

8. The uplink signal transmission method according to claim 1 , further comprising: not transmitting a CG PUSCH in a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

9. 1. A user equipment (UE) configured to transmit an uplink signal in a wireless communication system, the user equipment (UE) comprising: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions; the instructions, when executed, cause the at least one processor to perform an action; The operation is receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission occasion uplink control information (UTO-UCI) in a first CG physical uplink shared channel (PUSCH) occasion based on the CG configuration; The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH occasion.

10. A processing device in a wireless communication system, comprising: at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions; the instructions, when executed, cause the at least one processor to perform an action; The operation is receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission occasion uplink control information (UTO-UCI) in a first CG PUSCH occasion based on the CG configuration; The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that a user equipment (UE) can transmit a CG PUSCH in the CG PUSCH opportunity; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH occasion.

11. A computer-readable storage medium, comprising: the storage medium is configured to store at least one program code including instructions that, when executed, cause at least one processor to perform operations; The operation is receiving a configured grant (CG) setting; and transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission occasion uplink control information (UTO-UCI) in a first CG PUSCH occasion based on the CG configuration; The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that a user equipment (UE) can transmit a CG PUSCH in the CG PUSCH opportunity; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH occasion.

12. A method for a base station (BS) receiving an uplink signal from a user equipment (UE) in a wireless communication system, comprising: Sending configured grant (CG) settings; and receiving a first CG physical uplink shared channel (PUSCH) including unused transmission occasion uplink control information (UTO-UCI) at a first CG PUSCH occasion based on the CG configuration; The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH occasion.

13. 1. A base station (BS) in a wireless communication system configured to receive an uplink signal from a user equipment (UE), the base station (BS) comprising: at least one transceiver; at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions; the instructions, when executed, cause the at least one processor to perform an action; The operation is Sending a configured grant (CG) setting; and receiving a first CG physical uplink shared channel (PUSCH) including unused transmission occasion uplink control information (UTO-UCI) at a first CG PUSCH occasion based on the CG configuration; The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer; N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH occasions subsequent to the first PUSCH occasion, and each of the N bits has a first bit value or a second bit value; The first bit value indicates that the UE can transmit a CG PUSCH in the CG PUSCH occasion; The second bit value indicates that the UE does not transmit a CG PUSCH in the CG PUSCH opportunity.

14. The base station of claim 13, wherein N is a value provided by higher layer signaling of the BS.

15. The base station of claim 14, wherein N is a value provided by higher layer signaling.

16. The base station of claim 13, wherein the subsequent N CG PUSCH occasions to which the N bits of the N-bit bitmap are one-to-one mapped exclude invalid PUSCH occasions.

17. The base station of claim 16, wherein the invalid CG PUSCH timing is a CG PUSCH timing that overlaps with a symbol designated as an uplink by a time division duplex (TDD) uplink-downlink configuration.

18. The base station of claim 16 , wherein the non-valid CG PUSCH occasions are CG PUSCH occasions that overlap with symbols of a synchronization signal / physical broadcast channel block.

19. The operations include: obtaining jointly coded bits for the HARQ-ACK information and the UTO-UCI on the first PUSCH based on the presence of HARQ-ACK information to be received in the first CG PUSCH occasion; The base station of claim 13 , wherein the jointly coded bits are mapped to the first CG PUSCH by rate matching.

20. The base station of claim 13 , wherein the action includes: not expecting CG PUSCH reception in a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

Images