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

Abstract

The UE can receive a configuration grant (CG) configuration, and transmit a first CG PUSCH including uplink transmission opportunity uplink control information (UTO-UCI) in a first CG PUSCH period based on the CG configuration. The UTO-UCI includes an N-bit bitmap, and N bits of the N-bit bitmap are mapped to N CG PUSCH periods following a first PUSCH period in a one-to-one manner, where each of the N bits has a first bit value or a second bit value, the first bit value indicates that the UE is capable of transmitting the CG PUSCH within the respective CG PUSCH period, and the second bit value indicates that the UE is not to transmit the CG PUSCH within the respective CG PUSCH period.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system. Background Art

[0002] Technologies such as machine-to-machine (M2M) communication, machine-type communication (MTC), and various devices requiring high data throughput, such as smartphones and tablet personal computers (PCs), have emerged and become widespread. Consequently, the data throughput required to be handled by cellular networks has rapidly increased. To meet this rapid increase in data throughput, carrier aggregation and cognitive radio technologies have been developed to efficiently utilize more frequency bands, as well as multiple-input multiple-output (MIMO) and multi-base station (BS) collaboration technologies to increase the data capacity transmitted using limited frequency resources.

[0003] As more and more communication devices require greater communication capacity, enhanced mobile broadband (eMBB) communications, compared to traditional radio access technologies (RATs), are becoming increasingly popular. Furthermore, massive machine-type communications (mMTC), which connects multiple devices and objects to provide a variety of services anytime, anywhere, is a major consideration for next-generation communications.

[0004] Discussions are also underway to design communication systems that take into account services / user equipment (UE) that are sensitive to reliability and latency. The introduction of next-generation RATs is under discussion, taking into account eMBB communications, mMTC, and ultra-reliable low-latency communications (URLLC). Summary of the Invention

[0005] Technical issues

[0006] What is needed is a method for efficiently transmitting data packets in a wireless communication system where jitter may occur.

[0007] A method is needed to minimize the waste of radio resources based on semi-persistent scheduling or configuring grants.

[0008] What is needed is a method for efficiently informing a base station of the actual usage of radio resources scheduled to a user equipment.

[0009] The objects to be achieved by using the present disclosure are not limited to those specifically described above, and other objects not described herein will be more clearly understood by those skilled in the art from the following detailed description.

[0010] Technical Solution

[0011] In another aspect of the present disclosure, a method for transmitting an uplink signal by a user equipment (UE) in a wireless communication system is provided. The method may include: receiving a configuration grant (CG) configuration; and transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission opportunity uplink control information (UTO-UCI) on a first CG PUSCH opportunity based on the CG configuration. The UTO-UCI may include an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap may be mapped one-to-one to N CG PUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE is capable of transmitting a CG PUSCH on the related CG PUSCH opportunity, and the second bit value may indicate that the UE is not capable of transmitting a CG PUSCH on the related CG PUSCH opportunity.

[0012] In another aspect of the present disclosure, a UE configured to send an uplink signal in a wireless communication system is provided. The UE may include: at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations. The operations may include: receiving a CG configuration; and sending a first CG PUSCH including a UTO-UCI on a first CG PUSCH opportunity based on the CG configuration. The UTO-UCI may include an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap may be mapped one-to-one to N CG PUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE is capable of sending a CG PUSCH on the relevant CG PUSCH opportunity, and the second bit value may indicate that the UE does not send a CG PUSCH on the relevant CG PUSCH opportunity.

[0013] In another aspect of the present disclosure, a processing device is provided herein. The processing device may include: at least one processor; and at least one computer memory, which is operably connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations. The operations may include: receiving a CG configuration; and sending a first CG PUSCH including a UTO-UCI on a first CG PUSCH opportunity based on the CG configuration. The UTO-UCI may include an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap may be mapped one-to-one to N CG PUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE is capable of sending a CG PUSCH on the relevant CG PUSCH opportunity, and the second bit value may indicate that the UE does not send a CG PUSCH on the relevant CG PUSCH opportunity.

[0014] In another aspect of the present disclosure, a computer-readable storage medium is provided herein, which is configured to store at least one program code including instructions, which, when executed, cause at least one processor to perform operations. The operations may include: receiving a CG configuration; and based on the CG configuration, sending a first CG PUSCH including a UTO-UCI on a first CG PUSCH opportunity. The UTO-UCI may include an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap may be mapped one-to-one to N CG PUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE is capable of sending a CG PUSCH on the relevant CG PUSCH opportunity, and the second bit value may indicate that the UE does not send a CG PUSCH on the relevant CG PUSCH opportunity.

[0015] In another aspect of the present disclosure, a method for receiving an uplink signal from a UE by a base station (BS) in a wireless communication system is provided. The method may include: sending a CG configuration; and receiving a first CG PUSCH including a UTO-UCI on a first CGPUSCH opportunity based on the CG configuration. The UTO-UCI may include an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap may be mapped one-to-one to N CGPUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE is capable of sending a CG PUSCH on the relevant CG PUSCH opportunity, and the second bit value may indicate that the UE does not send a CG PUSCH on the relevant CGPUSCH opportunity.

[0016] In another aspect of the present disclosure, a base station (BS) configured to receive uplink signals from a UE in a wireless communication system is provided. The BS may include: at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations. The operations may include: transmitting a CG configuration; and, based on the CG configuration, receiving a first CG PUSCH including a UTO-UCI on a first CG PUSCH opportunity. The UTO-UCI may include an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap may be mapped one-to-one to N CG PUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE is capable of transmitting a CG PUSCH on the relevant CG PUSCH opportunity, and the second bit value may indicate that the UE is not capable of transmitting a CG PUSCH on the relevant CG PUSCH opportunity.

[0017] In each aspect of the present disclosure, N may be provided by higher layer signaling from the BS.

[0018] In each aspect of the present disclosure, N may be provided for the CG configuration.

[0019] In each aspect of the present disclosure, subsequent N CG PUSCH opportunities mapped one-to-one to N bits of an N-bit bitmap may be obtained by excluding invalid PUSCH opportunities.

[0020] In each aspect of the present disclosure, an invalid CG PUSCH opportunity may be a CG PUSCH opportunity that overlaps with a symbol indicated as UL by a TDD UL-DL configuration (eg, a radio resource control (RRC) parameter tdd-UL-DL-ConfigurationCommon and / or an RRC parameter tdd-UL-DL-ConfigurationDedicated).

[0021] In each aspect of the present disclosure, an invalid CG PUSCH opportunity is a CG PUSCH opportunity that overlaps with a symbol in an SS / PBCH block (eg, a symbol in the SS / PBCH block with an index given by the RRC parameter ssb-PositionsInBurst).

[0022] In each aspect of the present disclosure, the method performed by the UE, or the operation of the UE, processing device or storage medium may further include: based on the presence of HARQ-ACK information to be sent on the first CG PUSCH opportunity, obtaining jointly coded bits by jointly coding the HARQ-ACK information and the UTO-UCI; and mapping the jointly coded bits to the first CG PUSCH through rate matching.

[0023] In each aspect of the present disclosure, a method performed by a base station or an operation of the base station may include obtaining bits for joint coding of HARQ-ACK information and UTO-UCI on a first PUSCH based on the presence of HARQ-ACK information to be received on a first CG PUSCH opportunity. The method or operation may include assuming that the jointly coded bits are mapped to the first CG PUSCH by rate matching.

[0024] In each aspect of the present disclosure, the method performed by the UE, or the operation of the UE, processing device, or storage medium may include not transmitting the CG PUSCH on the CG PUSCH opportunity mapped to the bit having the second value among the N bits.

[0025] In each aspect of the present disclosure, the method performed by the BS or the operation of the BS may include anticipating not receiving the CG PUSCH on a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

[0026] The above solutions are only some examples of the present disclosure, and those skilled in the art can deduce and understand various examples into which the technical features of the present disclosure are incorporated from the following detailed description.

[0027] Beneficial effects

[0028] According to some embodiments of the present disclosure, it is possible to reduce the waste of radio resources configured for data packets that may experience jitter.

[0029] According to some embodiments of the present disclosure, radio resources configured based on a Configuration Grant (CG) may be used for other transmissions.

[0030] According to some embodiments of the present disclosure, actual usage of radio resources scheduled to a user equipment (UE) may be efficiently reported to a base station (BS).

[0031] Effects according to the present disclosure are not limited to those specifically described above, and other effects not described herein will be more clearly understood by those skilled in the art to which the present disclosure relates from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate examples of embodiments of the disclosure and together with the detailed description serve to explain embodiments of the disclosure:

[0033] Figure 1 An example of a communication system 1 to which an embodiment of the present disclosure is applied is illustrated;

[0034] Figure 2 is a block diagram illustrating an example of a communication device capable of performing the method according to the present disclosure;

[0035] Figure 3 illustrates another example of a wireless device capable of performing embodiments of the present disclosure;

[0036] Figure 4 An example of a frame structure used in a wireless communication system based on the 3rd Generation Partnership Project (3GPP) is illustrated;

[0037] Figure 5 A resource grid illustrating time slots is shown;

[0038] Figure 6 Illustrated are examples of physical downlink shared channel (PDSCH) time domain resource assignment (TDRA) caused by a physical downlink control channel (PDCCH) and examples of physical uplink shared channel (PUSCH) TDRA caused by the PDCCH;

[0039] Figure 7 Figure 1 shows the hybrid automatic repeat request-acknowledgement (HARQ-ACK) transmission / reception process;

[0040] Figure 8 FIGURE 1 illustrates an operation flow of a user equipment (UE) according to some embodiments of the present disclosure;

[0041] Figure 9 FIGURE 1 illustrates an operation flow of a base station (BS) according to some embodiments of the present disclosure;

[0042] Figure 10 FIGURE 1 illustrates a signal transmission / reception process between a UE and a BS according to some embodiments of the present disclosure;

[0043] Figure 11 and Figure 12 Illustrated is an example of unused resource indication / information (URI) transmission according to some embodiments of the present disclosure.

[0044] Figure 13 illustrates a flow of uplink signal transmission at a UE according to some embodiments of the present disclosure; and

[0045] Figure 14A flow of uplink signal reception at a BS according to some embodiments of the present disclosure is illustrated. DETAILED DESCRIPTION

[0046] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description given below with reference to the accompanying drawings is intended to illustrate exemplary embodiments of the present disclosure, rather than to illustrate the only embodiments that can be implemented according to the present disclosure. The following detailed description includes specific details in order to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure can be practiced without these specific details.

[0047] In some cases, known structures and devices may be omitted or shown in block diagram form to focus on important features of the structures and devices so as not to obscure the concepts of the present disclosure. The same reference numerals will be used throughout this disclosure to refer to the same or similar parts.

[0048] The following techniques, devices, and systems can be applied to various wireless multiple-access systems. For example, multiple-access systems may include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA). CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio 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 specifically implemented using radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS), and 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of E-UMTS, which uses E-UTRA. 3GPP LTE uses OFDMA on the downlink (DL) and SC-FDMA on the uplink (UL). LTE-Advanced (LTE-A) is an evolved version of 3GPP LTE.

[0049] For ease of description, the present disclosure will be described assuming that it is applied to LTE and / or New RAT (NR). However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to the 3GPP LTE / NR system, the mobile communication system is applicable to any other mobile communication system except for matters specific to the 3GPP LTE / NR system.

[0050] For terms and techniques used in this disclosure that are not described in detail, reference may be made to standard specifications based on 3GPP (for example, 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.331, etc.).

[0051] In an example of the present disclosure described later, if a device "assumes" something, this may mean that a channel transmission entity transmits the channel in accordance with the corresponding "assumption." This may also mean that a channel reception entity receives or decodes the channel in a form that conforms to the "assumption" provided that the channel is transmitted in accordance with the "assumption."

[0052] In this disclosure, a user equipment (UE) can be fixed or mobile. Each of the various devices that transmit and / or receive user data and / or control information by communicating with a base station (BS) can be a UE. The term UE may be referred to as terminal equipment, mobile station (MS), mobile terminal (MT), user terminal (UT), subscriber station (SS), wireless device, personal digital assistant (PDA), wireless modem, handheld device, etc. In this disclosure, a base station (BS) refers to a fixed station that communicates with a UE and / or another base station and exchanges data and control information with the UE and another base station. The term base station may be referred to as an advanced base station (ABS), node B (NB), evolved node B (eNB), base transceiver system (BTS), access point (AP), processing server (PS), etc. Specifically, a base station for universal terrestrial radio access (UTRAN) is referred to as an NB, a base station for evolved UTRAN (E-UTRAN) is referred to as an eNB, and a base station for a new radio access technology network is referred to as a gNB. For convenience, NB, eNB, or gNB will be referred to as a base station below, regardless of the type or version of the communication technology.

[0053] In this disclosure, a node refers to a fixed point capable of transmitting and receiving radio signals to and from a UE by communicating with the UE. Regardless of the name, various types of base stations (BSs) can serve as nodes. For example, a base station (BS), a base station (NB), an eNB, a picocell eNB (PeNB), a home eNB (HeNB), a relay, a transponder, etc. can be a node. Furthermore, a node may not be a base station (BS). For example, a radio remote head (RRH) or a radio remote unit (RRU) can be a node. Typically, RRHs and RRUs have lower power levels than base stations. Since RRHs or RRUs (hereinafter referred to as RRH / RRUs) are typically connected to a base station (BS) via dedicated lines such as optical cables, cooperative communication between the RRH / RRU and the BS can be performed more smoothly than cooperative communication between the BS connected via wireless links. Each node is equipped with at least one antenna. An antenna can refer to a physical antenna port or a virtual antenna or antenna group. A node can also be referred to as a point.

[0054] In the present disclosure, a cell refers to a specific geographical area where one or more nodes provide communication services. Therefore, in the present disclosure, communication with a specific cell may mean communication with a BS or node that provides communication services to the specific cell. The DL / UL signal of a specific cell refers to the DL / UL signal from / to the BS or node that provides communication services to the specific cell. A cell that provides UL / DL communication services to a UE is specifically referred to as a serving cell. In addition, the channel state / quality of a specific cell refers to the channel state / quality of a channel or communication link generated between the BS or node that provides communication services to the specific cell and the UE. In a 3GPP-based communication system, the UE can use a cell-specific reference signal (CRS) resource transmitted on a CRS and / or a channel state information reference signal (CSI-RS) resource (allocated to a specific node by its antenna port) to measure the DL channel state from a specific node.

[0055] The 3GPP-based communication system uses the concept of cells in order to manage radio resources, and distinguishes cells related to radio resources from cells of geographical areas.

[0056] A "cell" of a geographic area can be understood as the coverage area where a node can use a carrier to provide services, and a "cell" of radio resources is associated with a bandwidth (BW), which is a frequency range configured by the carrier. Because downlink coverage (the range within which a node can transmit valid signals) and uplink coverage (the range within which a node can receive valid signals from UEs) depend on the carrier carrying the signal, the coverage area of ​​a node can also be associated with the coverage area of ​​the "cell" of the radio resources used by the node. Therefore, the term "cell" can sometimes refer to the service coverage area of ​​a node, at other times to the radio resource, or at other times to the range within which a signal using the radio resource can reach with effective strength.

[0057] The 3GPP communications standard uses the concept of cells to manage radio resources. A "cell," associated with radio resources, is defined by a combination of downlink (DL) and uplink (UL) resources (i.e., a combination of a DL component carrier (CC) and an UL component carrier (CC). A cell can be configured with only DL resources or a combination of both. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. For example, the combination of DL and UL resources can be indicated by a System Information Block Type 2 (SIB2) linkage. In this case, the carrier frequency can be equal to 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. During RRC connection establishment / reestablishment / handover, one serving cell provides non-access stratum (NAS) mobility information. During RRC connection reestablishment / handover, one serving cell provides security input. This cell is referred to as the primary cell (Pcell). The Pcell is the cell operating on the primary frequency used by the UE to perform initial connection establishment or initiate connection reestablishment. Depending on UE capabilities, a secondary cell (Scell) can be configured to form a set of serving cells along with the PCell. The Scell ​​can be configured after RRC connection establishment is complete and is used to provide additional radio resources in addition to those of the specific cell (SpCell). The carrier corresponding to the PCell on the DL is called the downlink primary CC (DL PCC), and the carrier corresponding to the PCell on the UL is called the uplink primary CC (UL PCC). The carrier corresponding to the Scell ​​on the DL is called the downlink secondary CC (DL SCC), and the carrier corresponding to the Scell ​​on the UL is called the uplink secondary CC (UL SCC).

[0058] In dual connectivity (DC) operation, the term special cell (SpCell) refers to the Pcell of a primary cell group (MCG) or the primary and secondary cells (Pcells) of a secondary cell group (SCG). SpCells support PUCCH transmission and contention-based random access and are always enabled. An MCG is a set of serving cells associated with a master node (e.g., a base station) and includes an SpCell (Pcell) and, optionally, one or more Scells. For UEs configured with DC, an SCG is a subset of serving cells associated with a secondary node and includes a PSCell and zero or more Scells. The PSCell is the primary Scell ​​of the SCG. For UEs in the RRC_CONNECTED state without CA or DC configured, there is only one serving cell, consisting of only the Pcell. For UEs in the RRC_CONNECTED state with CA or DC configured, the term serving cell refers to the set of cells, including the SpCell and all Scells. In DC, two medium access control (MAC) entities are configured for the UE: one for the MCG and one for the SCG.

[0059] For a UE configured with CA but not DC, a Pcell PUCCH group (also referred to as a primary PUCCH group) including a Pcell and 0 or more Scells and a Scell ​​PUCCH group (also referred to as a secondary PUCCH group) including only Scells can be configured. For an Scell, an Scell ​​(hereinafter, a PUCCH cell) that transmits a PUCCH associated with the corresponding cell can be configured. The Scell ​​indicating the PUCCH Scell ​​belongs to the Scell ​​PUCCH group (i.e., a secondary PUCCH group) and performs PUCCH transmission of related uplink control information (UCI) on the PUCCH Scell. If a PUCCH Scell ​​is not indicated for the Scell ​​or the cell indicating PUCCH transmission for the Scell ​​is the Pcell, the Scell ​​belongs to the Pcell PUCCH group (i.e., a primary PUCCH group) and performs PUCCH transmission of related UCI on the Pcell. Hereinafter, if the UE is configured with an SCG and some embodiments of the present disclosure related to PUCCH are applied to the SCG, the primary cell may refer to the PSCell of the SCG. If the UE is configured with a PUCCH Scell ​​and some embodiments of the present disclosure related to PUCCH are applied to a secondary PUCCH group, the primary cell may refer to a PUCCH Scell ​​of the secondary PUCCH group.

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

[0061] 3GPP-based communication standards define downlink (DL) physical channels corresponding to resource elements that carry information originating from higher layers, as well as downlink (DL) physical signals corresponding to resource elements used by the physical layer but not carrying information originating from higher layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), physical multicast channel (PMCH), physical control format indicator channel (PCFICH), and physical downlink control channel (PDCCH) are defined as DL physical channels, while reference signals (RS) and synchronization signals are defined as DL physical signals. RS (also known as pilot) signals have predefined, special waveforms known to both the base station and the user equipment terminal. For example, the demodulation reference signal (DMRS) and channel state information RS (CSI-RS) are defined as DL RS. 3GPP-based communication standards define uplink (UL) physical channels corresponding to resource elements that carry information originating from higher layers, as well as uplink physical signals corresponding to resource elements used by the physical layer but not carrying information originating 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 UL physical channels, and a DMRS for UL control / data signals, a sounding reference signal (SRS) for UL channel measurement, etc. are defined.

[0062] In this disclosure, PDCCH refers to a set of time-frequency resources (e.g., resource elements (REs)) that carry downlink control information (DCI), and PDSCH refers to a set of time-frequency resources that carry downlink data. PUCCH, PUSCH, and PRACH refer to a set of time-frequency resources that carry UCI, UL data, and random access signals, respectively. In the following description, "a UE transmits / receives PUCCH / PUSCH / PRACH" is used to mean the UE transmits / receives UCI / UL data / random access signals on or via PUCCH / PUSCH / PRACH, respectively. Furthermore, "a base station transmits / receives PBCH / PDCCH / PDSCH" is used to mean the base station transmits broadcast information / DCI / DL data on or via PBCH / PDCCH / PDSCH, respectively.

[0063] In this specification, radio resources (eg, time-frequency resources) scheduled or configured by a BS for a UE to transmit or receive a PUCCH / PUSCH / PDSCH may be referred to as PUCCH / PUSCH / PDSCH resources.

[0064] Because a communication device receives synchronization signal blocks (SSBs), DMRSs, CSI-RSs, PBCHs, PDCCHs, PDSCHs, PUSCHs, and / or PUCCHs in the form of radio signals on a cell, the communication device may not select and receive a radio signal that includes only a specific physical channel or specific physical signal via a radio frequency (RF) receiver, or may not select and receive a radio signal without a specific physical channel or specific physical signal via an RF receiver. In actual operation, the communication device receives the radio signal on the cell via an RF receiver, converts the radio signal, which is an RF band signal, into a baseband signal, and then uses one or more processors to decode the physical signal and / or physical channel in the baseband signal. Therefore, in some embodiments of the present disclosure, not receiving the physical signal and / or physical channel may mean that the communication device does not attempt to recover the physical signal and / or physical channel from the radio signal, for example, does not attempt to decode the physical signal and / or physical channel, rather than the communication device actually receiving the radio signal including the corresponding physical signal and / or physical channel.

[0065] As more and more communication devices require greater communication capacity, eMBB communication, which is different from traditional radio access technology (RAT), is needed. In addition, large-scale MTC, which provides various services anytime and anywhere by connecting multiple devices and objects to each other, is a major issue to be considered in next-generation communications. In addition, the design of communication systems that take into account services / UEs that are sensitive to reliability and latency is also under discussion. Considering eMBB communication, large-scale MTC, ultra-reliable low-latency communication (URLLC), etc., the introduction of next-generation RAT is under discussion. Currently, in 3GPP, research on the next-generation mobile communication system after EPC is underway. In this disclosure, for convenience, the corresponding technology is referred to as new RAT (NR) or fifth-generation (5G) RAT, and the system using NR or supporting NR is referred to as an NR system.

[0066] Figure 1 An example of a communication system 1 to which an embodiment of the present disclosure is applied is shown. Figure 1The communication system 1 applied to the present disclosure includes wireless devices, a base station, and a network. Here, wireless devices refer to devices that perform communications using a RAT (e.g., 5G NR or LTE (e.g., E-UTRA)) and may be referred to as communication / radio / 5G devices. Wireless devices may include (but are not limited to) a robot 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and an artificial intelligence (AI) device / server 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of vehicle-to-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR), virtual reality (VR), and mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs), vehicle-mounted heads-up displays (HUDs), televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, and the like. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, base stations and networks may also be implemented as wireless devices, and a particular wireless device may operate as a base station / network node relative to another wireless device.

[0067] Wireless devices 100a to 100f can connect to a network 300 via a base station (BS) 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to an AI server 400 via the network 300. Network 300 can be configured using a 3G network, a 4G network (e.g., LTE), or a 5G network (e.g., NR). While wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also communicate directly with each other (e.g., sidelink communication) without going through the BS / network. For example, vehicles 100b-1 and 100b-2 can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0068] Wireless communications / connections 150a and 150b may be established between wireless devices 100a to 100f and BS 200, and between wireless devices 100a to 100f. Wireless communications / connections, such as UL / DL communications 150a and sidelink communications 150b (or device-to-device (D2D) communications), may be established via various RATs (e.g., 5G NR). The wireless devices and BS / wireless devices may transmit and receive radio signals to and from each other via wireless communications / connections 150a and 150b. To this end, various configuration information configuration procedures, various signal processing procedures (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and at least a portion of resource allocation procedures for transmitting and receiving radio signals may be performed based on various proposals of the present disclosure.

[0069] Figure 2 is a block diagram illustrating an example of a communication device capable of executing the method according to the present disclosure. Figure 2 , the first wireless device 100 and the second wireless device 200 may transmit and / or receive radio signals via various RATs (eg, LTE and NR). Here, {the first wireless device 100 and the second wireless device 200} may correspond to Figure 1 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0070] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the functions, processes, and / or methods described / proposed below. For example, the processor 102 may process information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals via the transceiver 106. The processor 102 may receive a radio signal including second information / signals via the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may execute some or all of the processes controlled by the processor 102 or store software code including commands for executing the processes and / or methods described / proposed below. Here, the processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The term "transceiver" 106 may be used interchangeably with a radio frequency (RF) unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0071] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may also include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the functions, processes, and / or methods described / proposed below. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals via the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals via the transceiver 206, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may execute some or all of the processes controlled by the processor 202 or store software code including commands for executing the processes and / or methods described / proposed below. Here, the processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The term "transceiver 206" may be used interchangeably with "RF unit." In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0072] The wireless communication technologies implemented in the wireless devices 100 and 200 of the present disclosure may include narrowband IoT (NB-IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide area network (LPWAN) technology and is implemented in standards such as LTE Cat. NB1 and / or LTE Cat. NB-IoT technology, however, is not limited to these designations. Alternatively or additionally, the wireless communication technology implemented in the wireless devices XXX and YYY of the present disclosure may be based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and is referred to by various names including enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented in accordance with at least one of the following standards: 1) LTE Cat. 0, 2) LTE Cat. M1, 3) LTE Cat. M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, etc., although LTE-M technology is not limited to these designations. Additionally or alternatively, considering low-power communication, the wireless communication technology implemented in the wireless devices XXX and YYY of the present disclosure may include at least one of ZigBee, Bluetooth, and LPWAN, but the wireless communication technology is not limited to the above names. For example, ZigBee technology can be used to create a personal area network (PAN) related to low / low-power digital communication based on various standards such as IEEE 802.15.4, and ZigBee technology can be referred to by various names.

[0073] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (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). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure. The one or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure, and provide the generated signal to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure and obtain the PDU, SDU, message, control information, data, or information.

[0074] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented using hardware, firmware, software, or a combination thereof. For example, 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) may be included in the one or more processors 102 and 202. The functions, processes, proposals, and / or methods disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. The firmware or software configured to perform the functions, processes, proposals, and / or methods disclosed in this disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 to be driven by the one or more processors 102 and 202. The functions, processes, proposals, and / or methods disclosed in this disclosure may be implemented using firmware or software in the form of code, commands, and / or command sets.

[0075] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, commands, and / or instructions. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, a hard drive, registers, cache memory, a computer-readable storage medium, and / or a combination thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies, such as wired or wireless connections.

[0076] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the methods and / or operational flow charts of the present disclosure to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the functions, processes, proposals, methods, and / or operational flow charts disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208. The one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels as described in the functional, process, proposal, method, and / or operational flow charts disclosed herein via the one or more antennas 108 and 208. In the present disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc., can be processed by the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc., processed by the one or more processors 102 and 202, from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0077] Figure 3 Another example of a wireless device capable of executing the embodiments of the present disclosure is shown. Figure 3 , the wireless devices 100 and 200 may correspond to Figure 2 The wireless devices 100 and 200 may be configured by various elements, components, units / portions and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 2One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Figure 2 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or may store information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0078] The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the following manner: Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR devices ( Figure 1 100c), handheld device ( Figure 1 100d), household appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcast UE, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 1 400), BS ( Figure 1 200), network nodes, etc. The wireless device can be used in a mobile or fixed location depending on the usage / service.

[0079] exist Figure 3In the wireless devices 100 and 200, the various elements, components, units / portions, and / or modules may all be connected to each other via wired interfaces, or at least a portion thereof may be wirelessly connected via the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected via the communication unit 110. The various elements, components, units / portions, and / or modules within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the control unit 120 may be configured by a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory 130 may be configured by random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-transitory memory, and / or a combination thereof.

[0080] In the present disclosure, at least one memory (e.g., 104 or 204) may store instructions or programs, and these instructions or programs, when executed, may cause at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of the present disclosure.

[0081] In the present disclosure, a computer-readable (non-transitory) storage medium may store at least one instruction or program, and when the at least one instruction or program is executed by at least one processor, the at least one processor may cause the at least one processor to perform operations according to some embodiments or implementations of the present disclosure.

[0082] In the present disclosure, a processing device or apparatus may include at least one processor and at least one computer memory operatively connected to the at least one processor. The at least one computer memory may store instructions or programs, and when these instructions or programs are executed, they may cause the at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of the present disclosure.

[0083] In the present disclosure, a computer program may include program code stored on at least one computer-readable (non-transitory) storage medium, and when executed, is configured to perform operations according to some embodiments of the present disclosure or cause at least one processor to perform operations according to some embodiments of the present disclosure. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-transitory) storage medium.

[0084] The communication device of the present disclosure includes: at least one processor; and at least one computer memory, which is operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations according to examples of the present disclosure described later.

[0085] Figure 4 An example of a frame structure used in a 3GPP-based wireless communication system is shown.

[0086] Figure 4 The frame structure is merely exemplary, and the number of subframes, slots, and symbols in a frame may vary. In an NR system, different OFDM parameter sets (e.g., subcarrier spacing (SCS)) may be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of time resources comprising the same number of symbols (e.g., subframes, slots, or transmission time intervals (TTIs)) may be configured differently for the aggregated cells. Symbols may include OFDM symbols (or cyclic prefix-OFDM (CP-OFDM) symbols) and SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols). In this disclosure, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbol may be used interchangeably.

[0087] Reference Figure 4 In the NR system, UL transmission and DL transmission are organized into frames. Each frame has T f =(△f max *N f / 100)*T c = 10 ms duration and is divided into two half frames of 5 ms each. The basic time unit of NR is T c =1 / (△f max *N f ), where △f max =480*10 3 Hz and N f =4096. For reference, the basic time unit of LTE is T s =1 / (△f ref *N f,ref ), where △f ref =15*10 3 Hz and N f,ref =2048. T s and T c With constant κ=T s / T c =64. Each half frame includes 5 subframes, and the duration of a single subframe is Tsf The subframe is further divided into slots, and the number of slots in a subframe depends on the SCS. Each slot includes 14 or 12 OFDM symbols based on the cyclic prefix. In normal CP, each slot includes 14 OFDM symbols, and in extended CP, each slot includes 12 OFDM symbols. The parameter set depends on the exponential scalable subcarrier spacing ∆f=2 u *15 kHz. The following table shows the number of OFDM symbols per time slot (N slot symb ), the number of time slots per frame (N frame,u slot ) and the number of time slots per subframe (N subframe,u slot ).

[0088] [Table 1]

[0089]

[0090] The following table shows that according to SCS △f=2 u *15 kHz, number of OFDM symbols per slot, number of slots per frame, and number of slots per subframe.

[0091] [Table 2]

[0092]

[0093] For SCS configuration u, the time slots may be indexed in ascending order within a subframe as follows: n u s ∈{0, ..., n subframe,u slot -1}, and are indexed in ascending order within the frame as follows: n u s,f ∈{0, ..., n frame,u slot -1}.

[0094] Figure 5 The resource grid of a time slot is shown. A time slot includes multiple (e.g., 14 or 12) symbols in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, the common resource blocks (CRBs) N indicated by higher layer signaling (e.g., RRC signaling) are allocated. start,u grid Begins to define N size,u grid,x *N RB sc subcarriers and N subframe,u symb OFDM symbol resource grid, where N size,u grid,xis the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for the downlink and UL for the uplink. N RB sc is the number of subcarriers per RB. In 3GPP-based wireless communication systems, N RB sc Typically 12. For a given antenna port p, SCS configuration u, and transmission link (DL or UL), there is one resource grid. The carrier bandwidth N of SCS configuration u is given to the UE through higher-layer parameters (e.g., RRC parameters). size,u grid . Each element in the resource grid for antenna port p and SCS configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l representing the symbol position relative to a reference point in the time domain. In the NR system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In the NR system, RBs are classified into CRBs and physical resource blocks (PRBs). For SCS configuration u, CRBs are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of CRB 0 of SCS configuration u is equal to "point A" used as a common reference point for the RB grid. PRBs of subcarrier spacing configuration u are defined within a bandwidth part (BWP) and are numbered from 0 to N size,u BWP,i −1 numbering, where i is the number of BWPs. PRB n in BWP i PRB With CRB n u CRB The relationship between n u PRB =n u CRB +N size,u BWP,i Given, where N size BWP,i is the CRB where the BWP starts relative to CRB 0. A BWP consists of multiple consecutive RBs in the frequency domain. For example, a BWP may be a CRB with a given parameter set u in BWP i on a given carrier. i A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Data communication is performed via enabled BWPs, and only a predetermined number of BWPs (e.g., one BWP) among those configured for the UE can be active on the component carrier.

[0095] For each serving cell in the set of DL BWPs or UL BWPs, the network may configure at least an initial DL BWP and one (if the serving cell is configured with uplink) or two (if supplementary uplink) initial UL BWPs. The network may configure additional UL and DL BWPs. For each DL BWP or UL BWP, the following parameters may be provided to the UE for the serving cell: i) SCS; ii) CP; iii) start BWP= 275 indicates the offset RB set and length L RB CRB N provided as the RRC parameter locationAndBandwidth of the Resource Indicator Value (RIV) start BWP =O carrier +RB start and the number of adjacent RBs N size BWP =L RB , and the value 0 provided by the RRC parameter offsetToCarrier for SCS carrier ; an index into a set of DL BWP or UL BWP; a set of BWP common parameters; and a set of BWP dedicated parameters.

[0096] Virtual Resource Blocks (VRBs) can be defined within a BWP and are numbered from 0 to N. size,u BWP,i -1 index, where i represents the BWP number. VRBs can be mapped to PRBs according to interleaved mapping or non-interleaved mapping. In some embodiments, for non-interleaved VRB to PRB mapping, VRB n can be mapped to PRB n.

[0097] A UE configured with carrier aggregation may be configured to use one or more cells. If the UE is configured with multiple serving cells, the UE may be configured with one or more cell groups. The UE may also be configured with multiple cell groups associated with different BSs. Alternatively, the UE may be configured with multiple cell groups associated with a single BS. Each cell group of the UE includes one or more serving cells and includes a single PUCCH cell configured with PUCCH resources. The PUCCH cell may be a Pcell or an Scell ​​configured as a PUCCH cell among the Scells of the corresponding cell group. Each serving cell of the UE belongs to one of the cell groups of the UE and does not belong to multiple cells.

[0098] NR frequency bands are defined as two types of frequency ranges: FR1 and FR2. FR2 is also known as millimeter wave (mmW). The following table shows the frequency ranges in which NR can operate.

[0099] [Table 3]

[0100]

[0101] Hereinafter, physical channels available in a 3GPP-based wireless communication system will be described in detail.

[0102] The PDCCH carries DCI. For example, the PDCCH (i.e., DCI) carries information on 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 about the DL-SCH, resource allocation information for control messages in layers higher than the physical layer (hereinafter referred to as higher layers) within the UE / BS protocol stack (e.g., the random access response (RAR) sent on the PDSCH), transmit power control commands, and information on enabling / disabling configuration scheduling (CS). DCI that includes resource allocation information for the DL-SCH is called PDSCH scheduling DCI, while DCI that includes resource allocation information for the UL-SCH is called PUSCH scheduling DCI. The DCI includes a cyclic redundancy check (CRC). The CRC is masked / scrambled with various identifiers (e.g., the radio network temporary identifier (RNTI)) depending on the owner and usage of the PDCCH. For example, if the PDCCH is for a specific UE, the CRS is masked with the UE identifier (e.g., cell-RNTI (C-RNTI)). If the PDCCH is for a paging message, the CRC is masked with the paging RNTI (P-RNTI). If the PDCCH is for system information (e.g., system information block (SIB)), the CRC is masked with the system information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the random access RNTI (RA-RNTI).

[0103] When the PDCCH on one serving cell schedules the PDSCH or PUSCH on another serving cell, it is called cross-carrier scheduling. Cross-carrier scheduling with a carrier indicator field (CIF) allows the PDCCH on the serving cell to schedule resources on another serving cell. When the PDSCH on the serving cell schedules the PDSCH or PUSCH on the serving cell, it is called self-carrier scheduling. When cross-carrier scheduling is used within a cell, the base station (BS) can provide the UE with information about the scheduling cell. For example, the BS can inform the UE whether the serving cell is scheduled by the PDCCH on another (scheduling) cell or by the serving cell. If the serving cell is scheduled by another (scheduling) cell, the BS can inform the UE which cell signals the DL assignments and UL grants for the serving cell. In this disclosure, the cell carrying the PDCCH is referred to as the scheduling cell, and the cell whose PUSCH or PDSCH transmission is scheduled by the DCI included in the PDCCH (i.e., the cell carrying the PUSCH or PDSCH scheduled by the PDCCH) is referred to as the scheduled cell.

[0104] The PDSCH is a physical layer (UL) channel used for UL data transmission. The PDSCH carries DL data (e.g., DL-SCH transport blocks) and uses modulation schemes such as Quadrature Phase Shift Keying (QPSK), 16-bit Quadrature Amplitude Modulation (QAM), 64-QAM, and 256-QAM. Codewords are generated by encoding transport blocks (TBs). The PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer, along with the DMRS, is mapped to radio resources and generated as an OFDM symbol signal. The OFDM symbol signal is then transmitted via the corresponding antenna port.

[0105] The PUCCH is a physical layer UL channel used for transmitting uplink control information (UCI). The PUCCH carries UCI. The types of UCI transmitted on the PUCCH include hybrid automatic repeat request acknowledgement (HARQ-ACK) information, scheduling request (SR), and channel state information (CSI). The UCI bits include HARQ-ACK information bits (if present), SR information bits (if present), link recovery request (LRR) information bits (if present), and CSI bits (if present). In the present disclosure, the HARQ-ACK information bits correspond to the HARQ-ACK codebook. In particular, the bit sequence in which the HARQ-ACK information bits are arranged according to a predetermined rule is called the HARQ-ACK codebook.

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

[0107] - Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK): A response to a DL data packet (e.g., a codeword) on the PDSCH. The HARQ-ACK indicates whether the communication device successfully received the DL data packet. A 1-bit HARQ-ACK can be sent in response to a single codeword. A 2-bit HARQ-ACK can be sent in response to two codewords. HARQ-ACK responses include positive ACK (abbreviated as ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. Herein, the term HARQ-ACK is used interchangeably with HARQ ACK / NACK, ACK / NACK, or A / N.

[0108] - Channel State Information (CSI): Feedback information about the DL channel. CSI may include channel quality information (CQI), rank indicator (RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH resource block indicator (SSBRI), and layer indicator (L1). Depending on the type of UCI included in the CSI, CSI may be classified into CSI Part 1 and CSI Part 2. For example, the CRI, RI, and / or CQI of the first codeword may be included in CSI Part 1, and the LI, PMI, and / or CQI of the second codeword may be included in CSI Part 2.

[0109] - Link Recovery Request (LRR)

[0110] In this disclosure, for convenience, the PUCCH resources configured / indicated by the BS for / to the UE for HARQ-ACK, SR, and CSI transmission are referred to as HARQ-ACK PUCCH resources, SR PUCCH resources, and CSI PUCCH resources, respectively.

[0111] According to the UCI payload size and / or transmission length (eg, the number of symbols included in the PUCCH resource), the PUCCH format may be defined as follows: For the PUCCH format, reference may also be made to Table 4.

[0112] (0) PUCCH format 0 (PF0 or F0)

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

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

[0115] - Transmission structure: PUCCH format 0 includes only the UCI signal without the DMRS. The UE selects and transmits one of multiple sequences to indicate the UCI status. For example, the UE transmits one of multiple sequences via the PUCCH (PUCCH format 0) to the base station to send specific UCI. The UE transmits the PUCCH (PUCCH format 0) in the PUCCH resources used for the corresponding SR configuration only when transmitting a positive SR.

[0116] - The configuration of PUCCH format 0 includes the following parameters corresponding to the PUCCH resource: the index of the initial cyclic shift, the number of symbols used for PUCCH transmission and / or the first symbol used for PUCCH transmission.

[0117] (1) PUCCH format 1 (PF1 or F1)

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

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

[0120] -Transmission structure: DMRS and UCI are mapped to / on different OFDM symbols using a time-division multiplexing (TDM) configuration. In other words, DMRS is transmitted in symbols where modulation symbols are not transmitted, and UCI is represented as the product of a specific sequence (e.g., an orthogonal cover code (OCC)) and a modulation (e.g., QPSK) symbol. By applying cyclic shift (CS) / OCC to both UCI and DMRS, code division multiplexing (CDM) is supported across multiple PUCCH resources (compliant with PUCCH format 1) within the same RB. PUCCH format 1 carries up to 2 bits of UCI, and modulation symbols are spread in the time domain by the OCC (configured differently depending on whether frequency hopping is performed).

[0121] - The configuration of PUCCH format 1 includes the following parameters corresponding to the PUCCH resource: the index of the initial cyclic shift, the number of symbols used for PUCCH transmission, the first symbol used for PUCCH transmission and / or the index of the OCC.

[0122] (2) PUCCH format 2 (PF2 or F2)

[0123] - Supported UCI payload size: more than K bits (e.g., K=2)

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

[0125] -Transmission Structure: DMRS and UCI are configured / mapped using frequency division multiplexing (FDM) within the same symbol. The UE transmits UCI by applying IFFT to the coded UCI bits without DFT. PUCCH format 2 carries UCI with a bit size larger than K bits, and the modulated symbols undergo FDM with DMRS for transmission. For example, DMRS is located in symbol indices #1, #4, #7, and #10 within a given RB, with a density of 1 / 3. A pseudo-noise (PN) sequence is used for the DMRS sequence. Frequency hopping can be enabled for the two-symbol PUCCH format 2.

[0126] - The configuration of PUCCH format 2 includes the following parameters corresponding to PUCCH resources: the number of PRBs, the number of symbols used for PUCCH transmission and / or the first symbol used for PUCCH transmission.

[0127] (3) PUCCH format 3 (PF3 or F3)

[0128] - Supported UCI payload size: more than K bits (e.g., K=2)

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

[0130] -Transmission structure: DMRS and UCI are configured / mapped to different OFDM symbols using time-division multiplexing (TDM). The UE transmits UCI by applying DFT to the coded UCI bits. PUCCH format 3 does not support UE multiplexing for the same time-frequency resources (e.g., the same PRB).

[0131] - The configuration of PUCCH format 3 includes the following parameters corresponding to PUCCH resources: the number of PRBs, the number of symbols used for PUCCH transmission and / or the first symbol used for PUCCH transmission.

[0132] (4) PUCCH format 4 (PF4 or F4)

[0133] - Supported UCI payload size: more than K bits (e.g., K=2)

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

[0135] -Transmission Structure: DMRS and UCI are allocated / mapped to different OFDM symbols using time-division multiplexing (TDM). By applying OCC (Optical Cross-Conversion) to the DFT front end and applying CS (or interleaved frequency division multiplexing (IFDM) mapping) to DMRS, PUCCH format 4 can multiplex up to four UEs in the same PRB. In other words, the modulation symbols of UCI are TDM-ed with DMRS for transmission.

[0136] - The configuration of PUCCH format 4 includes the following parameters for the corresponding PUCCH resources: the number of symbols for PUCCH transmission, the length of OCC, the index of OCC, and the first symbol for PUCCH transmission.

[0137] The following table shows PUCCH formats. According to the PUCCH transmission length, PUCCH formats can be divided into short PUCCH formats (format 0 and 2) and long PUCCH formats (format 1, 3 and 4).

[0138] [Table 4]

[0139]

[0140] PUCCH resources can be determined according to the UCI type (e.g., A / N, SR or CSI). The PUCCH resources for UCI transmission can be determined based on the UCI (payload) size. For example, the BS can configure multiple PUCCH resource sets for the UE, and the UE can select 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 one of the following PUCCH resource sets according to the number of UCI bits NUCI.

[0141] - PUCCH resource set #0, if the number of UCI bits <= 2

[0142] - PUCCH resource set #1, if 2 < the number of UCI bits <= N1 ...

[0144] - PUCCH resource set #(K - 1), if N K-2 < the number of UCI bits <= N K-1

[0145] Here, K represents the number of PUCCH resource sets (K > 1), and N i represents the maximum number of UCI bits supported by PUCCH resource set #i. For example, PUCCH resource set #1 can include resources for PUCCH formats 0 to 1, and other PUCCH resource sets can include resources for PUCCH formats 2 to 4 (see Table 4).

[0146] The configuration of each PUCCH resource includes the PUCCH resource index, the starting PRB index, and the configuration of one of PUCCH formats 0 to PUCCH format 4. The BS configures the UE, through the higher-layer parameter maxCodeRate, the code rate used to multiplex HARQ-ACK, SR, and CSI reports within PUCCH transmissions using PUCCH format 2, PUCCH format 3, or PUCCH format 4. The higher-layer parameter maxCodeRate is used to determine how to feed back UCI on PUCCH resources in PUCCH format 2, 3, or 4.

[0147] If the UCI type is SR and CSI, the PUCCH resources in the PUCCH resource set to be used for UCI transmission may be configured for the UE via higher-layer signaling (e.g., RRC signaling). If the UCI type is HARQ-ACK for a semi-persistently scheduled (SPS) PDSCH, the PUCCH resources in the PUCCH resource set to be used for UCI transmission may be configured for the UE via higher-layer signaling (e.g., RRC signaling). On the other hand, if the UCI type is HARQ-ACK for a PDSCH scheduled by DCI, the PUCCH resources in the PUCCH resource set to be used for UCI transmission may be scheduled by DCI.

[0148] In the case of DCI-based PUCCH resource scheduling, the base station can send DCI to the UE on the PDCCH and indicate the PUCCH resources to be used for UCI transmission within a specific PUCCH resource set using an ACK / NACK resource indicator (ARI) in the DCI. The ARI can be used to indicate the PUCCH resources used for ACK / NACK transmission and is also called a PUCCH resource indicator (PRI). Here, the DCI can be used for PDSCH scheduling, and the UCI may include HARQ-ACK for the PDSCH. The base station can configure a PUCCH resource set for the UE using (UE-specific) higher-layer (e.g., RRC) signaling that includes a larger number of PUCCH resources than can be represented by the ARI. The ARI can indicate a PUCCH resource subset of the PUCCH resource set, and the PUCCH resource to be used within the indicated PUCCH resource subset can be determined according to an implicit rule based on transmission resource information about the PDCCH (e.g., the starting CCE index of the PDCCH).

[0149] For UL-SCH data transmission, the UE should include the UL resources available to the UE, and for DL-SCH data reception, the UE should include the DL resources available to the UE. The base station assigns UL resources and DL resources to the UE through resource allocation. Resource allocation may include time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). In this disclosure, UL resource allocation is also referred to as UL grant, and DL resource allocation is referred to as DL assignment. UL grants are dynamically received by the UE on the PDCCH or in the RAR, or semi-persistently configured by the base station for the UE through RRC signaling. DL assignments are dynamically received by the UE on the PDCCH, or semi-persistently configured by the base station for the UE through RRC signaling.

[0150] On the UL, the BS can dynamically allocate UL resources to the UE via a PDCCH addressed to the Cell Radio Network Temporary Identifier (C-RNTI). The UE monitors the PDCCH to discover possible UL grants for UL transmission. The BS can use a configuration grant to allocate UL resources to the UE. Two types of configuration grants are available: Type 1 and Type 2. In Type 1, the BS directly provides the configured UL grant (including periodicity) via RRC signaling. In Type 2, the BS can configure the periodicity of the RRC-configured UL grant via RRC signaling and signal, activate, or deactivate the configured UL grant via a PDCCH addressed to the Configuration Scheduling RNTI (CS-RNTI). For example, in Type 2, the PDCCH addressed to the CS-RNTI indicates that the corresponding UL grant can be implicitly reused according to the periodicity configured via RRC signaling until deactivation.

[0151] On the DL, the BS can dynamically allocate DL resources to the UE via a PDCCH addressed to the C-RNTI. The UE monitors the PDCCH for possible DL grants. The BS can use SPS to allocate DL resources to the UE. The BS can configure the periodicity of the configured DL assignments via RRC signaling and signal, activate, or deactivate the configured DL assignments via a PDCCH addressed to the CS-RNTI. For example, a PDCCH addressed to the CS-RNTI may indicate that the corresponding DL assignments may be implicitly reused according to the periodicity configured via RRC signaling until deactivated.

[0152] Hereinafter, resource allocation through PDCCH and resource allocation through RRC will be described in more detail.

[0153] * Resource allocation via PDCCH: dynamic grant / assignment

[0154] The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The DCI on the PDCCH used to schedule DL transmissions may include a DL resource assignment, which includes at least the modulation and coding format associated with the DL-SCH (e.g., the modulation and coding scheme (MCS) index (IMCS), resource allocation, and HARQ information. The DCI on the PDCCH used to schedule UL transmissions may include an UL scheduling grant, which includes at least the modulation and coding format associated with the UL-SCH, resource allocation, and HARQ information. HARQ information for the DL-SCH or UL-SCH may include a new information indicator (NDI), transport block size (TBS), redundancy version (RV), and HARQ process ID (i.e., HARQ process number). The size and purpose of DCI carried by a PDCCH vary depending on the DCI format. For example, DCI format 0_0, DCI format 0_1, or DCI format 0_2 may be used to schedule the PUSCH, while DCI format 1_0, DCI format 1_1, or DCI format 1_2 may be used to schedule the PDSCH. Specifically, DCI format 0_2 and DCI format 1_2 can be 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, or DCI format 1_1. Some embodiments of the present disclosure may be applied to UL data transmission based on DCI format 0_2. Some embodiments of the present disclosure may be applied to DL data reception based on DCI format 1_2.

[0155] Figure 6 An example of PDSCH TDRA caused by a PDCCH and an example of PUSCH TDRA caused by a PDCCH are shown.

[0156] The DCI carried by the PDCCH for scheduling the PDSCH or PUSCH includes a TDRA field. The TDRA field provides the value m of the row index m+1 for the allocation table of the PDSCH or PUSCH. The predefined default PDSCH time domain allocation is applied as the allocation table for the PDSCH, or the PDSCH TDRA table configured by the BS through the RRC signal pdsch-TimeDomainAllocationList is applied as the allocation table for the PDSCH. The predefined default PUSCH time domain allocation is applied as the allocation table for the PUSCH, or the PUSCH TDRA table configured by the BS through the RRC signal pusch-TimeDomainAllocationList is applied as the allocation table for the PUSCH. The PDSCH TDRA table to be applied and / or the PUSCH TDRA table to be applied may be determined according to fixed / predefined rules (e.g., refer to 3GPP TS 38.214).

[0157] In a PDSCH time-domain resource configuration, each index row defines a DL assignment with a PDSCH slot offset K0, a start and length indicator value SLIV (or the starting position (e.g., starting symbol index S) and allocation length (e.g., number of symbols L) of the PDSCH in the direct slot), and the PDSCH mapping type. In a PUSCH time-domain resource configuration, each index row defines a UL grant with a PUSCH slot offset K2, the starting position (e.g., starting symbol index S) and allocation length (e.g., number of symbols L) of the PUSCH in the slot, and the PUSCH mapping type. K0 for the PDSCH and K2 for the PUSCH indicate the difference between the slot with the PDCCH and the slot with the PDSCH or PUSCH corresponding to the PDCCH. SLIV represents a joint indicator of the starting symbol S relative to the start of the slot with the PDSCH or PUSCH and the number of consecutive symbols, L, counted from symbol S. There are two PDSCH / PUSCH mapping types: mapping type A and mapping type B. In the case of PDSCH / PUSCH mapping type A, DMRS is mapped to the PDSCH / PUSCH resource relative to the beginning of the time slot. Depending on other DMRS parameters, one or two symbols of the PDSCH / PUSCH resource can be used as DMRS symbols. For example, in the case of PDSCH / PUSCH mapping type A, the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) in the time slot, depending on RRC signaling. In the case of PDSCH / PUSCH mapping type B, DMRS is mapped relative to the first OFDM symbol of the PDSCH / PUSCH resource. Depending on other DMRS parameters, one or two symbols starting from the first symbol of the PDSCH / PUSCH resource can be used as DMRS symbols. For example, in the case of PDSCH / PUSCH mapping type B, DMRS is located at the first symbol allocated for PDSCH / PUSCH. In this disclosure, the PDSCH / PUSCH mapping type may be referred to as a mapping type or a DMRS mapping type. For example, in the present disclosure, PUSCH mapping type A may be referred to as mapping type A or DMRS mapping type A, and PUSCH mapping type B may be referred to as mapping type B or DMRS mapping type B.

[0158] The scheduling DCI includes an FDRA field that provides information about the assignment of RBs for PDSCH or PUSCH. For example, the FDRA field provides information about the cell used for PDSCH or PUSCH transmission to the UE, information about the BWP used for PDSCH or PUSCH transmission, and / or information about the RBs used for PDSCH or PUSCH transmission.

[0159] *Resource allocation via RRC

[0160] As described above, there are two types of transmission without dynamic grants: Configuration Grant Type 1 and Configuration Grant Type 2. In Configuration Grant Type 1, the UL grant is provided by the RRC and stored as a Configuration UL Grant. In Configuration Grant Type 2, the UL grant is provided by the PDCCH and stored or cleared as a Configuration UL Grant based on L1 signaling indicating activation or deactivation of the Configuration UL Grant. Type 1 and Type 2 can be configured by the RRC per serving cell and per BWP. Multiple configurations can be active simultaneously on different serving cells.

[0161] When configuration grant type 1 is configured, the following parameters may be provided to the UE via RRC signaling:

[0162] -cs-RNTI, corresponding to the CS-RNTI used for retransmission;

[0163] -periodicity, which corresponds to the periodicity of configuration permission type 1;

[0164] -timeReferenceSFN, indicating the system frame number (SFN) used for determination of resource offset in the time domain;

[0165] -timeDomainOffset, corresponding to the offset associated with the SFN indicated by timeReferenceSFNt;

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

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

[0168] -mcsAndTBS, which provides I2C data indicating the modulation order, target code rate, and transport block size. MCS .

[0169] When the UL grant type 1 is configured for the serving cell via RRC, the UE stores the UL grant provided by the RRC as the configured UL grant for the indicated serving cell, and initializes or reinitializes the configured UL grant to start at the symbol according to timeDomainOffset and S (derived from SLIV) and recur at periodicity. After the UL grant is configured for the configured grant type 1, the UE may consider the UL grant to be consistent with the condition [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + (number of slots in frame * numberOfSymbolsPerSlot) + number of symbols in slot] = (timeReferenceSFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + timeDomainOffset * numberOfSymbolsPerSlot + S + N * periodicity) modulo (1024 * numberOfSlotsPerFrame * The OFDM UEFI standard specifies the number of consecutive OFDM symbols per frame (numberOfSymbolsPerSlot) for each OFDM symbol, for 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). Here, "SFN" refers to the SFN of a frame in which a UL grant may appear, "Slot Number" refers to the slot number of a slot in which a UL grant may appear within a frame, and "Symbol Number" refers to the symbol number of a symbol in which a UL grant may appear within the slot.

[0170] For configuration grant type 2, the BS may provide the following parameters to the UE via RRC signaling:

[0171] -cs-RNTI, corresponding to the CS-RNTI used for activation, deactivation, and retransmission; and

[0172] -periodicity, provides the periodicity for configuring permission type 2.

[0173] The actual UL grant is provided to the UE via PDCCH (addressed to the CS-RNTI). After configuring the UL grant for configuration grant type 2, the UE may consider the UL grant to be consistent with the condition [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot) + (number of slots in a frame * numberOfSymbolsPerSlot) + symbol number in a slot] = [(SFNstart time * numberOfSlotsPerFrame * numberOfSymbolsPerSlot +slot start time * numberOfSymbolsPerSlot + symbol start time ) + N * periodicity] modulo (1024 * numberOfSlotsPerFrame * numberOfSymbolsPerSlot) each symbol is associated and reproduced, for all N>=0, where SFN start time 、slot start time and symbol start time "SFN", "time slot", and "symbol" respectively represent the SFN, time slot, and symbol of the first transmission opportunity of the PUSCH after the configuration grant is (re)initialized. "numberOfSlotsPerFrame" and "numberOfSymbolsPerSlot" respectively indicate the number of consecutive time slots per frame and the number of consecutive OFDM symbols per time slot (see Table 1 and Table 2). "SFN" is the system frame number of the frame in which the uplink grant may appear, "time slot number" is the time slot number of the time slot in which the uplink grant may appear within the frame, and "symbol number" is the symbol number of the symbol in which the uplink grant may appear within the time slot.

[0174] In some scenarios, the base station may further provide the UE with the parameter harq-ProcID-Offset and / or parameter harq-ProcID-Offset2 for deriving the HARQ process ID for the configured UL grant. harq-ProcID-Offset is the offset of the HARQ process for the configured grant for shared spectrum channel access operations, and harq-ProcID-Offset2 is the offset of the HARQ process for the configured grant. In the present disclosure, cg-RetransmissionTimer is the duration after a transmission (retransmission) based on a configured grant, during which the UE should not autonomously perform retransmissions based on the HARQ process for the transmission (retransmission). The base station may provide the UE with the cg-RetransmissionTimer when configuring retransmissions related to a configured UL grant. For a configuration grant where neither harq-ProcID-Offset nor cg-RetransmissionTimer is configured, the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following formula: HARQ process ID = [floor (CURRENT_symbol / periodicity)] modulo fHARQ-Processes. For a configured UL grant with harq-ProcID-Offset2, the HARQ process ID associated with the first symbol of the UL transmission may be derived from the following formula: HARQ Process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + harq-ProcID-Offset2, where CURRENT_symbol = (SFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot + number of slots in a frame*numberOfSymbolsPerSlot + number of symbols in a slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent 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 select a HARQ process ID from among the HARQ process IDs available for the configured grant configuration.

[0175] On the DL, semi-persistent scheduling (SPS) can be provided to the UE from the BS via RRC signaling per serving cell and per BWP. For DL ​​SPS, the DL assignment is provided to the UE via PDCCH and is stored or cleared based on L1 signaling indicating SPS activation or deactivation. If SPS is configured, the UE can receive the following parameters from the BS via RRC signaling (e.g., SPS configuration) to configure semi-persistent transmission:

[0176] -cs-RNTI, corresponding to the CS-RNTI used for activation, deactivation, and retransmission;

[0177] -nrofHARQ-Processes, provides the number of HARQ processes used for SPS;

[0178] -periodicity, provides the periodicity of the configured DL assignments for SPS;

[0179] -n1PUCCH-AN, which provides HARQ resources for PUCCH used for SPS (the network configures the HARQ resources as format 0 or format 1, and the actual PUCCH resources are configured by PUCCH-Config and referenced by their ID in n1PUCCH-AN).

[0180] Multiple DL SPS configurations can be configured within the BWP of the serving cell. After configuring DL assignments for SPS, the UE may sequentially consider that the Nth DL assignment occurs when (numberOfSlotsPerFrame*SFN+time slot number 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 "numberOfSlotsPerFrame" and "numberOfSymbolsPerSlot" respectively indicate the SFN and time slot of the first transmission of the PDSCH after the configuration DL assignment is (re)initialized, and "numberOfSlotsPerFrame" and "numberOfSymbolsPerSlot" respectively indicate the number of consecutive time slots per frame and the number of consecutive OFDM symbols per time slot (see Tables 1 and 2). "SFN" is the system frame number of the frame in which the DL assignment may appear, and "Time Slot Number" is the time slot number of the time slot in which the DL assignment may appear within the frame.

[0181] In some scenarios, the BS may further provide the UE with a parameter harq-ProcID-Offset for deriving the HARQ process ID of the configured DL assignment. harq-ProcID-Offset is the offset of the HARQ process of the SPS. For a configured DL assignment without harq-ProcID-Offset, the HARQ process ID associated with the time slot in which the DL transmission starts can be determined from the following formula: HARQ Process ID = [floor (CURRENT_slot*10 / (numberOfSlotsPerFrame*periodicity))] modulo nrofHARQ-Processes, where CURRENT_slot = [(SFN*numberOfSlotsPerFrame) + the time slot number in the frame], and numberOfSlotsPerFrame represents the number of consecutive time slots per frame. For a configured DL assignment with harq-ProcID-Offset, the HARQ process ID associated with the timestamp in which the DL transmission starts can be determined from the following formula: HARQ Process ID = [floor(CURRENT_slot / periodicity)] modulo nrofHARQ-Processes + harq-ProcID-Offset, where CURRENT_slot = [(SFN*numberOfSlotsPerFrame) + timestamp number in the frame], and numberOfSlotsPerFrame represents the number of consecutive timeslots per frame.

[0182] If the CRC of the corresponding DCI format is scrambled using the CS-RNTI provided by the RRC parameter cs-RNTI and the New Data Indicator field of the Enabled Transport Block is set to 0, the UE verifies the DL SPS assignment PDCCH or the configuration of the UL grant type 2 PDCCH for scheduling enable or scheduling release. If all fields of the DCI format are set according to Tables 5 and 6, the DCI format is verified. Table 5 shows an example of special fields for DL ​​SPS and UL grant type 2 scheduling enable PDCCH verification, and Table 6 shows an example of special fields for DL ​​SPS and UL grant type 2 scheduling release PDCCH verification.

[0183] [Table 5]

[0184]

[0185] [Table 6]

[0186]

[0187] The actual DL assignment and UL grant and corresponding MCS for DL ​​SPS or UL grant type 2 are provided by the resource assignment fields (e.g., the TDRA field providing the TDRA value m, the FDRA field providing the frequency resource block assignment, and / or the MCS field) in the DCI format carried by the corresponding DL SPS or UL grant type 2 scheduling activation PDCCH. If verification is achieved, the UE regards the information in the DCI format as a valid activation or release of DL SPS or UL grant type 2.

[0188] In this disclosure, a PDSCH based on DL SPS may be referred to as an SPS PDSCH, and a PUSCH based on an UL configuration grant (CG) may be referred to as a CG PUSCH. A PDSCH dynamically scheduled by a DCI carried on a PDCCH may be referred to as a dynamic grant (DG) PDSCH, and a PUSCH dynamically scheduled by a DCI carried on a PDCCH may be referred to as a DG PUSCH.

[0189] Figure 7 The HARQ-ACK transmission / reception process is shown.

[0190] Reference Figure 7 , the UE may detect the PDCCH in slot n. Next, the UE may receive the PDSCH in slot n+K0 based on the scheduling information received via the PDCCH in slot n, and then transmit UCI via the PUCCH in slot n+K1. In this case, the UCI includes a HARQ-ACK response for the PDSCH.

[0191] The DCI (eg, DCI format 1_0 or DCI format 1_1) carried by the PDCCH for scheduling the PDSCH may include the following information.

[0192] - FDRA: FDRA indicates the RB set allocated to PDSCH.

[0193] - TDRA: TDRA indicates the DL assignment and PDSCH slot offset K0, the starting position (e.g., symbol index S) and length (e.g., number of symbols L) of the PDSCH in the slot, and the PDSCH mapping type. TDRA can indicate PDSCH mapping type A or PDSCH mapping type B. For PDSCH mapping type A, the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot. For PDSCH mapping type B, the DMRS is allocated in the first symbol allocated for the PDSCH.

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

[0195] If the PDSCH is configured to transmit up to one TB, the HARQ-ACK response may consist of one bit. If the PDSCH is configured to transmit up to two TB, the HARQ-ACK response may consist of two bits when spatial bundling is not configured, and one bit when spatial bundling is configured. When the HARQ-ACK transmission timing for multiple PDSCHs is specified as slot n+K1, the UCI transmitted in slot n+K1 includes the HARQ-ACK responses for the multiple PDSCHs.

[0196] In the present disclosure, the HARQ-ACK payload consisting of HARQ-ACK bits of one or more PDSCHs may be referred to as a HARQ-ACK codebook. Depending on the HARQ-ACK payload determination scheme, the HARQ-ACK codebook may be categorized as i) a semi-static HARQ-ACK codebook, ii) a dynamic HARQ-ACK codebook, and iii) a HARQ process-based HARQ-ACK codebook.

[0197] In the case of a semi-static HARQ-ACK codebook, parameters related to the HARQ-ACK payload size to be reported by the UE are semi-statically determined by (UE-specific) higher-layer (e.g., RRC) signaling. The HARQ-ACK payload size of the semi-static HARQ-ACK codebook (e.g., the (maximum) HARQ-ACK payload (size) transmitted via one PUCCH in one slot) can be determined based on the number of HARQ-ACK bits corresponding to the combination 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) that can indicate HARQ-ACK transmission timing (hereinafter referred to as the bundling window). In other words, in a semi-static HARQ-ACK codebook scheme, the HARQ-ACK codebook size is fixed (to a maximum value) regardless of the amount of DL data actually scheduled. For example, a DL grant DCI (PDCCH) includes PDSCH and HARQ-ACK timing information, and this PDSCH and HARQ-ACK timing information can have one of multiple values ​​(e.g., k). For example, when a PDSCH is received in slot #m and the PDSCH and HARQ-ACK timing information in the DL grant DCI (PDCCH) used to schedule the PDSCH indicates k, HARQ-ACK information for the PDSCH may be sent in slot #(m+k). As an example, k∈{1,2,3,4,5,6,7,8}. When HARQ-ACK information is sent in slot #n, the HARQ-ACK information may include the maximum possible HARQ-ACK based on the bundling window. That is, the HARQ-ACK information for slot #n may include the HARQ-ACK corresponding to slot #(nk). For example, when k∈{1,2,3,4,5,6,7,8}, the HARQ-ACK information for slot #n may include HARQ-ACKs corresponding to slot #(n-8) through slot #(n-1), regardless of the actual DL data received (i.e., the maximum number of HARQ-ACKs). Here, the HARQ-ACK information may be replaced by a HARQ-ACK codebook or a HARQ-ACK payload. The time slot may be understood / replaced as a candidate time for DL ​​data reception. As described in the example, the bundling window may be determined based on the PDSCH and HARQ-ACK timing based on the HARQ-ACK time slot, and the PDSCH and HARQ-ACK timing set may have a predefined value (e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or may be configured by higher layer (RRC) signaling. The semi-static HARQ-ACK codebook is referred to as a Type 1 HARQ-ACK codebook. For a Type 1 HARQ-ACK codebook, the number of bits to be sent in the HARQ-ACK report is fixed and may be large. If many cells are configured but only a few are scheduled, the Type 1 HARQ-ACK codebook may be inefficient.

[0198] In the case of a dynamic HARQ-ACK codebook, the HARQ-ACK payload size to be reported by the UE can be dynamically changed through DCI or the like. The dynamic HARQ-ACK codebook is referred to as a Type 2 HARQ-ACK codebook. The Type 2 HARQ-ACK codebook can be considered as optimized HARQ-ACK feedback because the UE only sends feedback for the scheduled serving cells. However, under poor channel conditions, the UE may incorrectly determine the number of scheduled serving cells. To address this issue, a downlink assignment index (DAI) can be included as part of the DCI. For example, in a dynamic HARQ-ACK codebook scheme, the DL scheduling DCI may include counter-DAI (i.e., c-DAI) and / or total-DAI (i.e., t-DAI). Here, the DAI indicates a downlink assignment index and is used by the BS to inform the UE of the PDSCH whose HARQ-ACK is to be included in one HARQ-ACK transmission sent or scheduled. Specifically, c-DAI is an index indicating the order between PDCCHs carrying DL scheduling DCI (hereinafter, DL scheduling PDCCHs), and t-DAI is an index indicating the total number of DL scheduling PDCCHs up to the current slot in which there is a PDCCH with t-DAI.

[0199] In the case of a HARQ process-based HARQ-ACK codebook, the HARQ-ACK payload is determined based on all HARQ processes of all configured (or enabled) serving cells in the PUCCH group. For example, the size of the HARQ-ACK payload to be reported by the UE using the HARQ process-based HARQ-ACK codebook may be determined based on the number of all configured or enabled serving cells in the PUCCH group configured for the UE and the number of HARQ processes of the serving cells. The HARQ process-based HARQ-ACK codebook is also referred to as a Type 3 HARQ-ACK codebook. The Type 3 HARQ-ACK codebook may be applied to one-time feedback.

[0200] One use case for URLLC can include time-sensitive networking (TSN). TSN refers to a communication network system that assumes all devices within a specific area have the same clock time for real-time communication and is time-synchronized. This assumption is used to establish motion control for equipment or collaborative robots in factories. XR services can also be provided as another use case for NR systems.

[0201] XR is a hyper-immersive technology and service that leverages virtual reality (VR), augmented reality (AR), mixed reality (MR), and holographic technologies to provide users with an environment where they can communicate and interact in a virtual space similar to the real world, without time or spatial constraints. XR is one of the main services introduced in NR wireless communication systems. XR is typically characterized by specific services with one or more downlink video streams tightly synchronized with frequent uplink gesture / control updates.

[0202] The successful implementation of XR requires support from the wireless system. In 3GPP-based wireless communication systems, such as NR wireless communication systems, the use of preconfigured resources such as SPS / CG is being considered to support XR. For example, the base station (BS) can provide the SPS / CG configuration to the UE, taking into account the average inter-arrival time of packets. However, the actual inter-arrival time of packets is inconsistent (random) due to jitter, which refers to the unintended time deviation in periodic signals. In XR, jitter occurs because the time required to process a frame before transmitting it varies due to the different amount of information in each frame.

[0203] In NR, a UE can be configured with one or more SPS PDSCHs or CG PUSCHs for periodic transmission and reception, low latency, and low PDCCH overhead. The configured / indicated resources can be repeated in the time domain with a periodicity determined by each SPS / CG configuration. That is, the initially configured / indicated resource allocation can be repeated with a periodicity configured by the SPS / CG configuration, and the UE can perform DL reception and / or UL transmission on the corresponding resources without any separate PDCCH reception process. There are various XR data types. Among the various data types, the UE's sensor information, location information, and video data, typically reported with specific periodicity, can be sent and received on SPS / CG resources. The arrival time of traffic for such data is inconsistent due to the following reasons: video encoding time, sensor measurement time, higher layer operations, or changes in network routing, which can all cause jitter. In addition, the size of the radio point resources required for transmission may vary depending on the type of frame and encoding method used by the UE / BS to send video.

[0204] To support such video data transmission, if radio resources are allocated based on the maximum radio resource size required by the BS, video information transmission may result in wasted radio resources in most cases. If radio resources are allocated based on a smaller radio resource size, additional radio resources may be allocated when large traffic occurs, resulting in additional latency.

[0205] In addition, some data is generated based on events, and it is therefore difficult to accurately determine the time when the data is generated. In order to reduce the delay caused by scheduling, it is also possible to consider using SPS / CG resources for such data. In this case, a skipping method can be considered. According to the skipping method, a sufficient number of resources are allocated at shorter intervals to prepare for data occurrence, and the UE or BS selectively uses some resources and does not use other resources. However, in order to skip transmission and reception, it is necessary to properly consider the response signal to check the reception and transmission status between the UE and the BS. If the UE sends a response signal even for a transmission that is not received, the BS needs to prepare resources for the UE to always send the response signal. Considering that the skipping method is based on configuring a sufficient number of radio resources, configuring response signal resources for all radio resources may impose a significant UL burden. In addition, considering that such resources can be multiplexed among user equipment (UE), the burden on UL resources needs to be carefully considered.

[0206] When using XR services or similar third-party services, the above factors need to be considered. For example, in order to efficiently transmit information such as video where the payload size of various services or traffic changes dynamically, it is possible to consider the UE selectively using the CG PUSCH configured in the SPS / CG and reporting unselected radio resources to the BS in advance. This operation allows the BS to reduce the burden on UL radio resources by using the resources for other UL transmissions.

[0207] Hereinafter, some embodiments of the present disclosure will be described. In an embodiment, when a UE is configured with multiple radio resources to receive video information required for various services or XR, if the UE attempts to transmit or receive on only some of the configured radio resources and does not use the remaining radio resources, the UE may report the unused radio resources to the BS so that the BS may allocate the reported radio resources to the UE or another UE (or other UEs).

[0208] Hereinafter, while the embodiments of the present disclosure are described based on semi-statically configured DL SPS and UL CG radio resources, the embodiments of the present disclosure are not limited thereto and can be widely applied to radio resources allocated by dynamic scheduling and received by the UE. As an example, an embodiment of the present disclosure in which the UE determines the timing of one HARQ-ACK of multiple DL radio resources allocated thereto can be applied without considering the SPS PDSCH and the PDSCH indicated by dynamic scheduling. Additionally, when multiple radio resources are not semi-statically configured and are configured by dynamic indication, for example, even when multiple radio resources are configured simultaneously by DCI, the embodiments of the present disclosure can be applied. Therefore, even if there is no separate explanation, the embodiments of the present disclosure can be applied to all types of transmission / reception methods desired by the BS and the UE. Hereinafter, for convenience of description, SPS is used as a general term collectively referred to as semi-statically configured radio resources (e.g., DL / UL SPS and CG) to describe the embodiments of the present disclosure.

[0209] In some embodiments of the present disclosure, a transmission opportunity (TO) may refer to a radio resource configured for SPS / CG (e.g., SPS PDSCH or CG PUSCH). An entity transmitting in a TO (e.g., a base station on the DL or a UE on the UL) may attempt to transmit in the TO, and a receiver (e.g., a UE on the DL or a base station on the UL) may attempt to receive, expecting a transmission in each TO. In this disclosure, the term transmission opportunity is used interchangeably with the term transmission opportunity. A TO or transmission opportunity is simply referred to as an opportunity.

[0210] Hereinafter, while the embodiments of the present disclosure are described based on the NR system, the embodiments of the present disclosure are not limited to NR transmission / reception. Additionally, while the features and structures of XR services are used as examples to describe the embodiments of the present disclosure, the embodiments of the present disclosure are not limited to support for XR services. Even if not described separately, the embodiments of the present disclosure can also be applied to all wireless communication transmission / reception structures and services.

[0211] Hereinafter, some embodiments of the present disclosure regarding methods and processes for a UE to notify a BS of radio resources to be used will be described. Embodiments of the present disclosure may include a method for a BS to allocate PDSCH / PUSCH radio resources to a UE, and a method for the UE to perform DL reception or UL reception on the allocated radio resources. Some embodiments of the present disclosure may include a method for a UE to send a HARQ-ACK PUCCH response in response to a PDSCH reception, and a method for a UE to receive DCI retransmitted by the BS via a PDCCH after a PUSCH transmission. In some embodiments of the present disclosure, a UE may send signals and channels to announce its capabilities and / or service requirements, and a BS may receive these signals and channels.

[0212] Figure 8 The operation flow of the UE according to some embodiments of the present disclosure is illustrated, and Figure 9 The diagram illustrates an operation flow of a BS according to some embodiments of the present disclosure.

[0213] refer to Figure 8 , the UE may receive an RRC configuration associated with an unused resource indication / information (URI), i.e., RRC parameters associated with the URI, and an RRC configuration associated with a CG PUSCH (e.g., a CG configuration) (S801). The CG configuration may be automatically activated or initially deactivated. When the UE has UL traffic / data to send, i.e., when the UL traffic / data becomes available for transmission, the UE may determine or predict the CG PUSCH resources required to transmit the UL traffic / data (i.e., CG PUSCH timing) (S803). The UE may report the URI to the BS based on the required CG PUSCH resources (or the number thereof) (S805). The UE may use the CG PUSCH resources to send a PUSCH carrying traffic / data (S807).

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

[0215] Figure 10 The diagram illustrates a signal transmission / reception process of a UE and a BS according to some embodiments of the present disclosure.

[0216] refer to Figure 10, the 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 and S1002). The semi-persistent configuration provided to the UE (i.e., CGPUSCH configuration) may be automatically activated or initially deactivated. When the UE has UL traffic (S1003) and intends to perform UL transmission on the CG PUSCH, the UE provided with the RRC configuration for the URI may determine or predict the CG PUSCH timing to be used taking into account the UE's buffer status and the characteristics of the CGPUSCH (S1004). The UE may report information about unused CG PUSCH resources (i.e., CG PUSCH timing) to the BS taking into account the determined or predicted number of CGPUSCHs to be used (S1005). Upon receiving this information, the BS may release the unused CG PUSCH resources only at the corresponding time and schedule UL transmission to the UE or other UEs for other purposes. The UE may perform UL transmission on other CG PUSCH resources except the CG PUSCH resources reported as unused, and the BS may attempt UL reception on radio resources among other CG PUSCH resources except the CG PUSCH resources reported as unused ( S1006 ).

[0217] The embodiments / methods described later may be selectively applied. Alternatively, each embodiment / method mentioned below may operate independently without being combined with other embodiments / methods, or one or more embodiments / methods may operate in a coordinated manner. Some terms, symbols, sequences, etc. used in this disclosure may be replaced with different terms, symbols, sequences, etc.

[0218] The embodiments / methods described in this disclosure may be defined to be applied only when the UE receives relevant configuration information from the BS (or core network). The configuration information may be provided via a higher-layer signal (e.g., SIB or RRC signaling). Alternatively, the information configured via a higher-layer signal (e.g., SIB or RRC signaling) may be activated / deactivated via separate signaling (e.g., DCI or MAC control element (CE)). In addition, the UE may be configured to report information (e.g., capabilities) regarding whether the UE can support the embodiments / methods of this disclosure, and the BS (or core network) may be configured to receive this information.

[0219] In some embodiments of the present disclosure, the URI may be referred to as an unused transmission opportunity UCI (UTO-UCI) because the URI plays a role of notifying the BS of unused transmission opportunities.

[0220] The following embodiments may be applied in relation to URIs.

[0221] <Implementation 1: Indication of Unused CG Resources>

[0222] Figure 11 and Figure 12 FIGURE 1 illustrates an example of URI transmission according to some embodiments of the present disclosure. Figure 11 and 12 In the , "TO" indicates the transmission timing. Figure 11 and Figure 12 In the example of , "0" among the bit values ​​of the URI indicates that, in case of CG, the UE can transmit CG PUSCH on the corresponding TO and in case of DL SPS, the UE is expected to receive SPS PDSCH on the corresponding TO. Figure 11 and Figure 12 In the example of , "1" among the bit values ​​of the URI indicates that, in case of CG, the UE may not transmit CG PUSCH on the corresponding TO, and in case of DL SPS, the UE does not need to receive SPSPDSCH on the corresponding TO. Figure 11 and Figure 12 In the example, the URI indicates the availability of the TO within a periodicity. However, the TO whose availability is indicated by the URI is not limited to one periodicity. In one example, according to some embodiments described later in the present disclosure, the URI may indicate the availability of the TO in a periodicity other than the periodicity to which the PUCCH / PUSCH carrying the URI belongs. As another example, according to some embodiments described later in the present disclosure, the availability of the TO across multiple periodicities may be indicated depending on the length of the URI.

[0223] The BS may indicate and configure one or more CG PUSCHs to the UE during a predetermined time interval T.

[0224] As an example, the BS includes information about multiple TDRAs in a CG configuration, or activates the relevant CGs through DCI containing TDRA information, thereby configuring multiple radio resources (i.e., multiple CG PUSCH opportunities) within a periodicity. For example, the BS may provide the UE with a CG configuration that includes multiple consecutively configured UL grants within a single periodicity. Depending on the CG configuration, multiple CG PUSCH opportunities may occur within a single periodicity of the CG configuration.

[0225] As another example, it can be considered that the BS indicates and configures one or more SPS / CG radio resources to the UE and allocates multiple SPS / CG radio resources to repeatedly transmit a TB within a periodicity or a predetermined time range. For example, one or more SPS / CG configurations can be provided, and PDSCH / PUSCH opportunities according to the one or more SPS / CG configurations can occur within a periodicity or a predetermined time range.

[0226] As another example, it can be considered that the BS indicates and configures one or more SPS / CG radio resources to the UE and allocates the multiple SPS / CG radio resources to transmit multiple TBs within a periodic or predetermined time range. For example, one or more SPS / CG configurations can be provided, and PDSCH / PUSCH opportunities according to the one or more SPS / CG configurations can occur within a periodic or predetermined time range.

[0227] When the UE has UL traffic and therefore needs to perform configured CG PUSCH transmission, the UE may not use all configured CG PUSCHs within the time interval T. For example, the UE may determine to use some of the configured CG PUSCHs within the time interval T and determine not to use some of the CG PUSCHs. In addition, the UE may suppress the determination of using some CG PUSCHs for future UL transmission. In some embodiments of the present disclosure, the UE may send information about the CG PUSCH that the UE determines not to use (hereinafter referred to as URI) to the BS. For example, the UE may send information about the radio resources that the UE determines to use and about the CG PUSCH information determined to be necessary for future UL link transmission to the BS. The UE may not send user data on the CG PUSCH opportunity that the UE does not notify of use or the CG PUSCH opportunity that the UE notifies of not use. For example, for the CG PUSCH opportunity that the UE notifies of not use, the base station may assume that the UE has not generated a MAC PDU to be sent on the corresponding PUSCH, does not have a MAC PDU to be sent on the corresponding PUSCH, or skips the CG PUSCH opportunity. Alternatively, a CG indicated as unused at the MAC layer may be considered to be deprioritized in the logical channel (LCH) prioritization procedure.

[0228] When using embodiment 1, such operations can be considered to be performed under an explicit request from the UE. For example, when using CG PUSCH, the UE can notify the BS whether to use the configured radio resources through embodiment 1 only when the availability of the configured CG PUSCH is weakened. In order to ensure that the BS receives information about each radio resource usage notified by the UE, a separate message indicating the use of embodiment 1 can be sent through L1 signaling (e.g., PUCCH, PUSCH, etc.) or higher layer signaling. Upon receiving the corresponding message, the BS can assume that the information about whether the UE uses the CG PUSCH timing is included in the CG PUSCH or the separately configured PUCCH transmitted by the UE and then perform reception.

[0229] Alternatively, when using Embodiment 1, the operation may be considered to be performed under an explicit request from the BS. For example, the BS may send a separate message to the UE via Layer 1 signaling (e.g., DCI) or higher-layer signaling (e.g., RRC signaling, MAC signaling, etc.), indicating the use of Embodiment 1. Upon receiving this message, the UE may transmit information regarding whether to use a CG PUSCH opportunity (i.e., a URI) via the CG PUSCH or a separately configured PUCCH. The BS may receive the URI by assuming UE operation.

[0230] In order to use the operations described in Embodiment 1, the UE may need to have specific capabilities. In this case, the UE may notify the BS of the availability of Embodiment 1 through a capability report. Upon receiving the capability report, the BS may perform BS operations only for UEs capable of using Embodiment 1.

[0231] The operations described in embodiment 1 may be performed for each CG configuration configured for the UE. For example, whether to use the operations described in embodiment 1 may be configured separately for each CG configuration, and the UE may perform embodiment 1 only for the CG configuration configured to use embodiment 1.

[0232] When performing the operation described in Embodiment 1, the CG configuration of the CG PUSCH carrying the URI may be different from the CG configuration to which the URI is applied. The details will be explained in Embodiments 1-5.

[0233] When using embodiment 1, if the BS does not receive a separate message from the UE or the UE does not send a separate message to the BS, it can be assumed that all configured CG PUSCH opportunities are not used.

[0234] <Implementation 1-1: Location for Sending Indication of Unused CG Resources>

[0235] As a method of transmitting information (hereinafter referred to as URI) on a CG PUSCH that the UE determines not to use to the BS, at least one of the following may be considered.

[0236] >The UE may send the URI via piggybacked UCI sent together with the CG PUSCH transmission.

[0237] >The UE may send the URI via a MAC CE sent together with the CG PUSCH transmission.

[0238] >UE can send URI through a separate PUCCH for URI.

[0239] >The UE may send a URI in the DMRS symbol of the CG PUSCH transmission. For example, one of N information values ​​may be sent using N orthogonal DMRS sequences.

[0240] <Implementation 1-2: Reference Time Zone for Indicating Unused CG Resources>

[0241] When the UE transmits the URI to the BS, the URI may be information about the CG PUSCH included in the time interval T. In this case, the time interval T may be determined in consideration of at least one of the following.

[0242] To determine the starting point of the time interval T,

[0243] >>The starting point of the time interval T may be the start or end of the PUSCH or PUCCH start symbol carrying the URI. That is, the URI carried by a specific PUSCH / PUCCH may include information on whether to transmit a CG PUSCH within a specific time period starting from the start / end symbol of the corresponding PUSCH / PUCCH.

[0244] >>>In some embodiments, if the URI is sent on the CG PUSCH, the starting point of the time interval T may be the start or end of the starting symbol of the subsequent CG PUSCH closest to the CG PUSCH carrying the URI. Figure 11 or Figure 12 , the URI transmitted on the CG PUSCH opportunity #i may include information on whether the CG PUSCH opportunity is used within a specific time period starting from the start symbol of the GG PUSCH opportunity #i+1 which is the subsequent CG PUSCH opportunity.

[0245] >>>In some embodiments, when a URI is sent on a CG PUSCH, the starting point of the time interval T may be the start or end of the start symbol of the subsequent CG PUSCH that is closest to the CG PUSCH carrying the URI within its periodicity.

[0246] >>The starting point of the time interval T can be a specific time interval T away from the start or end of the starting symbol of the PUSCH or PUCCH carrying the URI proc,URI time point.

[0247] >>>If the URI is sent on CG PUSCH, the start of the time interval T may be a specific time interval T away from the start or end of the next CG PUSCH start symbol that is closest to the CGPUSCH carrying the URI (within its periodicity) proc,URI time point.

[0248] >>The starting point of the time interval T can be the start or end of the last symbol of the PUSCH or PUCCH carrying the URI. That is, the URI transmitted by a specific PUSCH / PUCCH may include information on whether the CG PUSCH is transmitted within a specific time period starting from the last symbol of the corresponding PUSCH / PUCCH.

[0249] >>>If the URI is sent on the CG PUSCH, the starting point of the time interval T can be the start or end of the last symbol of the subsequent CG PUSCH that is closest (within its periodicity) to the CGPUSCH carrying the URI.

[0250] >>The starting point of the time interval T can be a specific time interval T away from the start or end of the last symbol of the PUSCH or PUCCH carrying the URI proc,URI time point.

[0251] >>>If the URI is sent on the CG PUSCH, the start of the time interval T can be a specific time interval T away from the start or end of the last symbol of the subsequent CG PUSCH closest (within its period) to the CGPUSCH carrying the URI proc,URI time point.

[0252] >>When a URI is sent on a CG PUSCH, the start point of the time interval T may be the start point of the periodicity including the corresponding CG PUSCH. Alternatively, the start point of the time interval T may be the start point of the periodicity including the subsequent CG PUSCH closest to the corresponding CG PUSCH carrying the URI.

[0253] >>When the URI is sent on the CG PUSCH, the starting point of the time interval T may be a specific time interval T from the start of the periodicity that includes the corresponding CG PUSCH proc,URIAlternatively, the starting point of the time interval T may be a specific time interval from the start of the periodicity of the subsequent CG PUSCH that includes the nearest CG PUSCH carrying the URI. Tproc,URI time point.

[0254] >>When the URI is sent on the CG PUSCH, the starting point of the time interval T may be the end of the periodicity including the corresponding CG PUSCH (ie, the start of the next periodicity).

[0255] >>When a URI is sent on a CG PUSCH, the start of the time interval T may be a specific time interval T away from the end of the periodicity that includes the corresponding CG PUSCH (i.e., the start of the next periodicity). proc,URI time point.

[0256] >>Specific time interval T proc,URI It can be the time required by the BS to reschedule the UL radio resources indicated as unused resources by the URI from the start of URI transmission. proc,URI It can be a value given by the BS through 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 relevant UE capabilities. For example, as described in 3GPP TS 38.214, the N1 or N2 value obtained by considering the UE capabilities used to determine the time required for the SCS for the PUCCH or PUSCH preparation procedure and the ULBWP, or the time T calculated based on the N1 or N2 value proc,1 or T proc,2 Can be used to determine T proc,URI More specifically, the above values ​​can be used directly as T proc,URI , or a specific fraction of this value can be used as T proc,URI .

[0257] >>When a URI is transmitted on a CG PUSCH, the starting point of the time interval T may be the start of every N periodicities that include the corresponding CG PUSCH. That is, the starting point of the time interval T may be the start of the first CG PUSCH in every N periodicities that include the corresponding CG PUSCH. Alternatively, the starting point of the time interval T may be the start of every N periodicities that include the subsequent CG PUSCH closest to the CG PUSCH carrying the URI. In some embodiments, the (start and end) boundaries of every N periodicities may be determined by grouping the first N periodicities for the CG PUSCH starting from SFN#0 into a first bundle and the next N periodicities into a second bundle.

[0258] >>>Here, N may be a value given through higher layer signaling from the BS, or a value determined based on a corresponding value.

[0259] >>When the URI is sent on the CG PUSCH, the starting point of the time interval T may be a specific time interval T away from the start of each N periodicity that includes the corresponding CG PUSCH proc,URI Alternatively, the starting point of the time interval T may be a specific time interval T away from the start of each N periodicity of the subsequent CG PUSCH including the CG PUSCH closest to the URI. proc,URI In some embodiments, the boundaries (start and end) of each N periodicities may be determined by grouping the first N periodicities for CG PUSCH starting from SFN#0 into a first bundle and the next N periodicities into a second bundle.

[0260] >>>Here, N may be a value given through higher layer signaling from the BS, or a value determined based on a corresponding value.

[0261] >>When the URI is sent on the CG PUSCH, the starting point of the time interval T may be the end of every N periodicities that include the corresponding CG PUSCH (i.e., the start of the next N periodicities). In some embodiments, the boundaries (start and end) of every N periodicities may be determined by grouping the first N periodicities for the CG PUSCH starting from SFN#0 into a first bundle and the next N periodicities into a second bundle.

[0262] >>>Here, N may be a value given through higher layer signaling from the BS, or a value determined based on a corresponding value.

[0263] >>When the URI is sent on the CG PUSCH, the starting point of the time interval T may be a specific time interval T away from the end of every N periodicities that include the corresponding CG PUSCH (i.e., the start of the next N periodicities). proc,URI In some embodiments, the boundaries (start and end) of each N periodicities may be determined by grouping the first N periodicities for CG PUSCH starting from SFN#0 into a first bundle and the next N periodicities into a second bundle.

[0264] >>>Here, N may be a value given through higher layer signaling from the BS, or a value determined based on a corresponding value.

[0265] To determine the length of the time interval T,

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

[0267] >>The time interval T may be determined by the UE and indicated in the URI. In this case, the URI may consist of two parts: a part indicating the length of the time interval T and a part indicating whether the CG PUSCH is not used during the time interval T, which is indicated in the corresponding part.

[0268] >>The time interval T can be a multiple of the periodicity of the CG PUSCH configured by the CG configuration.

[0269] >>> In this case, the CG configuration can be the CG configuration of the application URI.

[0270] >>>In this case, the CG configuration may be a CG configuration for sending a URI. Specifically, it may be considered that the URI is sent on the CG PUSCH.

[0271] >>The time interval T can be a specific time (e.g., X milliseconds).

[0272] >>The time interval T can be a specific time slot length (e.g., Y time slots).

[0273] >>> In this case, the slot length can be considered as an absolute time length that can be adjusted based on a separately configured reference SCS configuration or BWP to which a URI can be applied or sent (e.g. for 15kHz SCS one slot = 1ms).

[0274] >>Time interval T may be the time allocated for the N CG PUSCH opportunities. For example, time interval T may extend from the start of time interval T to the last symbol of the last CG PUSCH opportunity among the N CG PUSCH opportunities, or to the time slot where the last symbol is located.

[0275] >>>The number N of CG PUSCH opportunities can be a value given by L1 signaling (e.g., DCI) or higher layer signaling from the BS (e.g., RRC signaling). For the number N of CG PUSCH opportunities, multiple values ​​can be specified for each CG configuration, or one value can be specified for all CG configurations. For example, refer to Figure 11 , when N=4 is provided for the relevant CG configuration by higher layer signaling, the URI sent on CG PUSCH opportunity #i can indicate whether to use the four GGPUSCH opportunities (CG PUSCH opportunities #(i+1) to #(i+4)) after CG PUSCH opportunity i. Figure 11URI bits 0011 transmitted on CG PUSCH opportunity #1 are mapped one-to-one to CG PUSCH opportunities #2 to #5 in ascending order; URI bits 0111 transmitted on CG PUSCH opportunity #2 are mapped one-to-one to CG PUSCH opportunities #3 to #6 in ascending order; and URI bits 0011 transmitted on CG PUSCH opportunity #3 are mapped one-to-one to CG PUSCH opportunities #4 to #7 in ascending order. Upon receiving the URI on CG PUSCH opportunity #1, the BS can recognize that the UE can perform CG PUSCH transmission on CG PUSCH opportunities #2 and #3 and attempt CG PUSCH reception on CG PUSCH opportunities #2 and #3. Upon receiving the URI on CG PUSCH opportunities #1 to #3, the BS can recognize that the corresponding UE does not use CG PUSCH opportunities #4 to #7. Therefore, the BS may not expect to receive CG PUSCH from the UE on CG PUSCH opportunities #4 to #7 and may not attempt to receive CG PUSCH from the UE thereon. Because the BS cannot know whether CG PUSCH opportunity #8 has been used, the BS may attempt to receive CG PUSCH from the UE on CG PUSCH opportunity #8. According to some embodiments of the present disclosure, because the UE notifies through the URI whether to use N TOs after the TO in which the URI is sent, even if the UE changes its decision on the CG PUSCH opportunity indicated for use by the URI after sending the URI on CGPUSCH opportunity #i. The usage status for subsequent CGPUSCH opportunities can be updated to unused by the URI sent in another CG PUSCH opportunity indicated for use by the URI. In addition, by sending the URI in a specific size indicated / set by the BS, it is possible to prevent the URI signaling overhead from increasing excessively. In addition, the URI is sent in a predetermined size indicated / configured by the BS, thereby preventing the URI signaling overhead from increasing excessively.

[0276] >>Time interval T may be the time allocated for a CG PUSCH configured to transmit N TBs. That is, time interval T may extend from the start of time interval T to the last symbol of the last CG PUSCH among the CG PUSCHs configured to transmit N TBs, or to the time slot in which the last symbol is located.

[0277] >>>The number N of CG PUSCHs (i.e., the number of CG PUSCH opportunities) may be a value given through L1 signaling or higher layer signaling from the BS. For the number N of CG PUSCH opportunities, multiple values ​​may be given for each CG configuration, or one value may be given for all CG configurations.

[0278] >>>When CG PUSCH is configured for repeated transmission, the time interval T may extend from the start of time interval T to the last symbol of the last CG PUSCH in a group of CG PUSCHs configured to transmit N TBs (where the initial transmission starts), or to the time slot in which the last symbol is located.

[0279] >>The time interval T may extend from its start point to the end point of a specific periodicity or to the end point of the last CG PUSCH in the specific periodicity. For example, assuming that the periodicity including the start point is periodicity X, the time interval T may mean the time interval between the start point and the end point of periodicity X+k or the end point of the last CG PUSCH included in the periodicity, where k is an integer greater than or equal to 0 and may have a value given or determined through L1 signaling (e.g., DCI) or higher layer signaling (e.g., RRC signaling) from the BS.

[0280] >>> As another example, when the starting point of a time interval T is the start of the subsequent CG PUSCH closest to the CG PUSCH carrying the URI within its periodicity, the time interval T can be considered to end at the end of the periodicity. In this case, the UE can send the URI only on the remaining CG PUSCHs after the CG PUSCH carrying the URI within the corresponding periodicity, thereby saving the information required for transmission.

[0281] >>As another example, the time interval T may extend from the start point of the N periodicities to the end point thereof, or to the last CG PUSCH within the N periodicities. More specifically, assuming that the N periodicities including the start point are a periodicity group X (a group of periods), the time interval T may extend from the start point of the periodicity group X to the end point thereof, or to the last CG PUSCH included in the periodicity.

[0282] >>>The boundaries (start and end) of each N periodicities may be determined by grouping the first N periodicities for CG PUSCH starting from SFN#0 into a first bundle and the next N periodicities into a second bundle.

[0283] >>>Here, N is an integer greater than or equal to 1, and may have a value given or determined by L1 signaling or higher layer signaling from the BS.

[0284] >>> As another example, when the starting point of the time interval T is the start of the nearest subsequent CG PUSCH that carries the URI within N periodicities including the CG PUSCH that carries the URI, the time interval T can be considered to end at the end of the N periodicities. In this case, the UE can only send the URI of the remaining CG PUSCHs after the CG PUSCH that carries the URI within N periodicities, thereby saving the information required for transmission.

[0285] >When considering the periodicity of CG configuration, a periodicity can be defined as follows.

[0286] >>The starting point of a particular periodicity can be the end point of the previous periodicity. In other words, each periodicity forms a continuous time period.

[0287] >>When a radio resource is allocated and the radio resource is repeated at a specific time interval P, the starting point of each periodicity is the starting point of the radio resource, where the length of the periodicity is P.

[0288] >>When a radio resource is allocated to a UE, the radio resource is repeated at time slot intervals so that multiple radio resources are used, and the multiple radio resources are repeated at a specific time interval P. The starting point of each periodicity is the starting point of the first radio resource, where the length of the periodicity is P.

[0289] >>When a radio resource is allocated, the radio resource is repeated at time slot intervals or is continuously repeated within a time slot so that multiple radio resources are used, and the multiple radio resources are repeated at a specific time interval P, and the starting point of each periodicity is the starting point of the first radio resource, where the length of the periodicity is P.

[0290] >>When multiple radio resources are given by a single time domain resource allocation information and the multiple radio resources are repeated at a specific time interval P, the starting point of each periodicity is the starting point of the earliest starting radio resource among the multiple radio resources, where the length of the periodicity is P.

[0291] In some embodiments, when there is not enough time interval between the start of the time interval T (i.e., the start of the radio resources where the URI can provide information about the CG PUSCH transmission) and the end of the URI sent by the UE, it may be difficult for the BS to reschedule the UL resources based on the information provided by the URI. To avoid such problems, in some embodiments, the BS can reschedule the UL resources only when there is enough time interval (denoted as T) between the start of the time interval T and the end of the URI transmission by the UE. proc,URIAlternatively, if there is not enough time interval T between the start of the time interval T and the end of the UE's URI transmission, the UE is allowed to send the URI. proc,URI , the UE and / or the base station may ignore the specific time interval T from the end point of the UE's URI transmission among the information included in the URI. proc,URI Alternatively, the UE and / or BS may ignore all or part of the URI information including the above information. The UE may perform CG PUSCH transmission on the CGPUSCH opportunity indicated as unused in the ignored URI information, and the BS may attempt to receive the CGPUSCH even if the BS receives the corresponding information. If the UE or BS applies a URI based on the periodicity of the CG PUSCH or its specific time / resource unit, the URI information may be ignored for all CG PUSCHs included in the time / resource unit.

[0292] In some embodiments, the time interval T may represent the minimum duration for URI application. For example, the following method may be considered. Upon receiving the relevant message, the BS may assume that the UE cannot send additional messages or continue to send messages with the same content (i.e., without changing the content) during the minimum application duration. If the UE does not send a message or continues to send messages with the same content, the BS may maintain the application as if the message is received again after the time interval T.

[0293] When using embodiment 1, it may be considered that the UE notifies whether the CG PUSCH opportunity is not used in two separate messages. For example, the first message may indicate the range of unused CG PUSCH opportunities, that is, the time interval T. Then, the second message may indicate the unused CG PUSCH opportunities within the time interval T. In this case, in order to facilitate blind decoding of the BS, the information in the first message may have a fixed size, and the size of the second message may be considered to be variable depending on the range of the time interval T indicated in the first message. For example, the first message may use a fixed N-bit information (where K<2 N ) indicates K CG PUSCH opportunities or CG PUSCH periodicities, and the second message may provide a K-bit bitmap representing radio resources that the UE may use or not use during the K CG PUSCH opportunities or the K CG PUSCH periodicities.

[0294] Implementation 1-3: Construction of indication of unused CG resources

[0295] The UE may transmit information on whether to transmit the CG PUSCH within the time interval T as a URI as follows.

[0296] > First, in order to configure the URI, the time interval T can be divided into specific time units. In this case, the URI information can be determined based on whether the CG PUSCH included in each time unit is unused.

[0297] For example, the time unit may be a specific time (eg, x milliseconds) determined through L1 signaling (eg, DCI) or higher layer signaling (eg, RRC signaling) from the BS.

[0298] For example, the time unit may be a specific time slot length (eg, y time slots) determined through L1 signaling (eg, DCI) or higher layer signaling (eg, RRC signaling) from the BS.

[0299] For example, the time unit may be the periodicity of the CG PUSCH configured in the CG configuration or a multiple of the periodicity.

[0300] In this case, the CG configuration may be the CG configuration of the application URI.

[0301] In this case, the CG configuration can be the CG configuration of the PUSCH carrying the URI. Specifically, this can be taken into account when the URI is sent on the CGPUSCH.

[0302] >>For example, the time unit can be the periodicity of the CG PUSCH configured in the CG configuration or a value obtained by dividing the periodicity by an integer N greater than 1.

[0303] >>> In this case, the CG configuration can be the CG configuration of the application URI.

[0304] >>> In this case, the CG configuration can be the CG configuration of the PUSCH carrying the URI. Specifically, this can be taken into account when the URI is sent on the CGPUSCH.

[0305] >>For example, a time unit may mean one or n CG PUSCH opportunities.

[0306] >>>More specifically, one time unit may mean a duration from the first symbol of a specific CG PUSCH opportunity to the start of the first symbol of a subsequent CG PUSCH opportunity nearest to the specific CG PUSCH opportunity.

[0307] >>>In this case, the time interval T may be the time for allocating N CG PUSCH opportunities.

[0308] >>>In some embodiments, the number n of CG PUSCHs may be given through L1 signaling (eg, DCI) or higher layer signaling (RRC signaling) from the BS.

[0309] >>For example, the time unit may be a time for allocating a CG PUSCH configured to transmit one or n TBs.

[0310] >>>More specifically, one time unit may refer to a duration 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.

[0311] >>>In this case, the time interval T may be the time for allocating a CG PUSCH configured to transmit N TBs.

[0312] >>>If the time interval T is not evenly divided into time units, the following can be considered.

[0313] >>>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.

[0314] >>>The base station can configure multiple time units to the UE through higher layer signaling. By arranging the multiple time units in sequence, the UE can divide the time interval T, which is the total time interval indicated by the URI, and determine whether to use the CG PUSCH in each time unit. In this case, the sum of the multiple time units can be the time interval T or larger. When the sum of the multiple time units is greater than the time interval T, if a given time unit exceeds the end of the time interval T, the UE can assume that the corresponding time unit ends at the end of the time interval T.

[0315] >Reference Figure 11 , the UE may use a bitmap of size N. The UE may configure the URI by marking the position of the time unit including the unused CG PUSCH resource among the N consecutive time units as "1". In addition, the UE may configure the URI by marking the position of the time unit not including the unused CG PUSCH resource as "0". Conversely, using a bitmap with size N, the UE may configure the URI by marking the position of the time unit that is not determined to be an unused CG PUSCH resource among the N consecutive time units as "1". In addition, the UE may configure the URI by marking the position of the other time units as "0".

[0316] >>In this case, N may be the number of CG PUSCHs included in the time interval T (ie, the number of CG PUSCH opportunities).

[0317] >For example, N may be the number of configured CG PUSCHs included in the time interval T. That is, when the time domain radio resources determined by L1 signaling or higher layer signaling are repeated with a given periodicity based on the CG configuration, the number of radio resources included in the time interval T may be determined.

[0318] >>>For example, N may be the number of valid CG PUSCHs included in the time interval T. That is, N may be the number of CG PUSCHs that do not overlap in time with the DL symbols indicated by the RRC parameter tdd-UL-DL-ConfigurationCommon or the RRC parameter tdd-UL-DL-ConfigurationDedicated (if provided), or the symbols of the SS / PBCH blocks (i.e., SSBs) indexed by the RRC parameter ssb-PositionsInBurst among the CG PUSCHs included in the time interval T. In this case, the CG PUSCHs that can be indicated may be limited to the valid CG PUSCH (opportunity) or the time unit including the valid CG PUSCH (opportunity). For example, referring to Figure 12 , if higher layer signaling provides N=4 for the relevant CG configuration, the URI sent on CG PUSCH opportunity #i may indicate whether to use the four GG PUSCH opportunities excluding the invalid CG PUSCH opportunities among the CG PUSCH opportunities after CG PUSCH opportunity i. Figure 12 URI bits 0011 transmitted on CG PUSCH opportunity #1 are mapped one-to-one to CG PUSCH opportunities #2 to #5 in ascending order, URI bits 0111 transmitted on CG PUSCH opportunity #2 are mapped one-to-one to CG PUSCH opportunities #3, #4, #5, and #7 in ascending order, and URI bits 0011 transmitted on CG PUSCH opportunity #3 are mapped one-to-one to CG PUSCH opportunities #4, #5, #7, and #8 in ascending order. Upon receiving the URI on CG PUSCH opportunities #1 to #3, the BS may recognize that the UE will not use CG PUSCH opportunities #4, #5, #7, and #8. Therefore, the BS may not expect to receive CG PUSCH from the UE on CG PUSCH opportunities #4 to #7 and will not attempt to receive CG PUSCH from the UE thereon. Because the BS knows that CG PUSCH opportunity #6 is an invalid opportunity when the UE cannot perform PUSCH transmission, the BS does not expect to perform CG PUSCH reception and may not attempt CG PUSCH reception. The UE may provide URIs for TOs other than the TOs that the BS knows the UE will not use, thereby enabling the BS to determine the use / availability of CG PUSCH for a longer duration.

[0319] >>For example, the position of a time unit including unused resources among the N time units may be indicated as "1" (or "0"), and the position of a time unit not including unused resources may be indicated as "0" (or "1"). This indicates that the radio resources including at least one unused CG PUSCH are not used.

[0320] >>For example, the position of a time unit that does not include unused resources among the N time units may be indicated as "0" (or "1"), and the position of a time unit that does not include unused resources may be indicated as "1" (or "0"). This indicates that the radio resources including at least one available CG PUSCH are not used.

[0321] >>As another example, CG PUSCHs included in time interval T that do not temporally overlap with DL symbols indicated by the RRC parameter tdd-UL-DL-ConfigurationCommon or the RRC parameter tdd-UL-DL-ConfigurationDedicated (if provided) or symbols of the SS / PBCH block with the index given by the RRC parameter ssb-PositionsInBurst may always be indicated as unused resources.

[0322] >>As another example, the UE may consider only the K valid CG PUSCHs in a bitmap with a size of N, and indicate whether the K CG PUSCHs are used in K consecutive bits starting from the most significant bit (MSB) or the least significant bit (LSB). That is, the values ​​for the valid CG PUSCHs may be arranged consecutively. In this case, the remaining (NK) bits may be represented as unused bit values ​​or "0". The size of N may be the (maximum) number of CG PUSCHs configured in the interval, the (maximum) number of valid PUSCHs in the CG configuration, or a size determined or provided by L1 signaling (e.g., DCI) or higher layer signaling from the BS (e.g., RRC signaling).

[0323] >>As described in Embodiments 1-2, when a CG PUSCH carries URI information, time interval T associated with the URI information may not include the corresponding CG PUSCH. This is because there may be cases where the CG PUSCH carrying URI information is unused. Therefore, when the UE configures the bitmap for time interval T as a URI, the UE may exclude bits associated with the CG PUSCH carrying the URI.

[0324] The UE may indicate the position of the first time unit including radio resources that the UE can use to notify the available CG PUSCH included in K consecutive time units among N time units, and the number of time units including radio resources to be used. 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 available radio resources may be represented by N*(N+1) / 2 state values. In this case, the joint coding information value I may be derived according to the following formula: I = N x (K-1) + S.

[0325] >To notify the unused CG PUSCH included in K consecutive time units among N time units, the UE can indicate the position of the first time unit including the unused CG PUSCH and the number of consecutive time units including the unused CG PUSCH. For example, among the N time units, the position S of the first time unit including unused resources and the position K of the time unit including the last unused CG PUSCH can be represented by N*(N+1) / 2 state values. In this case, the information value I of the joint coding can be derived according to the following formula: I = N x (K-1) + S.

[0326] >In order to notify the available CG PUSCH included in the first K consecutive time units among the N time units, the UE may indicate the number of consecutive time units including radio resources available from the start of the time interval T.

[0327] >In order to notify the unused CG PUSCH included in the first K consecutive time units among the N time units, the UE may indicate the number of consecutive time units including the unused CG PUSCH starting from the time interval T.

[0328] >The BS may preconfigure a list of patterns for one or more unused resources (or available resources) to the UE. Alternatively, such patterns may be predefined. For example, multiple bitmaps may be configured to the UE. In each bitmap, the position of a time unit including an unused CG PUSCH resource or a time unit including a CG PUSCH that is not determined to be unused among N consecutive time units may be represented as "1". Otherwise, the position of other time resources may be represented as "0".

[0329] >>The plurality of patterns may include a pattern of all “0” or a pattern of all “1”. In other words, it may include a case where there is no unused resource or a case where all resources are unused.

[0330] >>UE may compare the determined unused resources with the configured pattern and then report the index of the appropriate pattern as a URI to the BS.The appropriate pattern may be determined in consideration of at least one of the following.

[0331] >>>Condition 1: A pattern in which all unused CG PUSCH resources determined by the UE are marked as unused, and / or a pattern with the least unused resources among the patterns that meet this condition.

[0332] >>>Condition 2: All remaining CG PUSCH resources except the unused CG PUSCH determined by the UE are marked as available patterns, and / or the pattern with the least available resources among the patterns that meet this condition.

[0333] >>When the UE compares the determined unused resources with the configured patterns and reports the index of the appropriate pattern as a URI to the BS, some states of the URI may be predefined. For example, if the UE sends an N-bit URI, a state in which all N bits are marked as "1" may mean that there is no pattern of unused CG PUSCH within the time interval T. As another example, a specific state may represent a pattern in which all resources are unused CG PUSCH within the time interval T. A different state may be associated with each pattern in the list. This operation may be limited to the case where there is no configured pattern index associated with the corresponding state. For example, in a 4-bit URI,

[0000] ,

[0001] ,

[0010] , ...,

[1110] ,

[1111] may be associated with up to 16 patterns or with the 1st to 16th patterns in a list of patterns including 16 patterns. If the sixteenth pattern is not configured,

[1111] may mean that there is no pattern of unused CG PUSCH within the time interval T.

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

[0335] In implementations 1-3, when the size of the URI is 0, for example, there is no valid CGPUSCH within the time interval T, or when there is no CG PUSCH, the UE may transmit only the CG PUSCH in addition to the URI.

[0336] <1-3-1>

[0337] According to embodiments 1-3, the UE may indicate the CG PUSCH transmission opportunities between the start and end points of the time interval T. For the time interval T, the transmission opportunity may be used as a unit, or the time interval T may represent an absolute time range. Specifically, when the transmission opportunity is used as a unit, the time interval between the first URI transmission and the next transmission may vary depending on the transmission opportunity interval given by the CG configuration, rather than being fixed. In this case, even if close transmission opportunities are indicated, the BS may not be able to reflect these transmission opportunities, resulting in information waste. Therefore, in order to reduce such overhead, the time range and transmission opportunities to be excluded from the actual URI information are determined according to the following method, and then in addition to the excluded time range and transmission opportunities, the time range or transmission opportunities reflected in the actual URI information may also be determined. Assume that the transmission opportunities to be excluded and the time range including these opportunities are T excl , and T excl can be determined as follows.

[0338] First, T excl The starting point of may be the end of the last symbol of the radio resource (eg CG-PUSCH) on which the URI is sent. Alternatively, if T excl The starting point of is earlier than the starting point of time interval T, then T excl The starting point of can be the starting point of time interval T. In other words, the earlier of the two can be T excl The starting point.

[0339] Next, T can be determined according to the following method excl The end point.

[0340] T excl The end point may be a point that is temporally distant from the end of the last symbol of the radio resource (eg, CG-PUSCH) on which the URI is sent.

[0341] >When URI is sent on CG PUSCH, T excl The end point may be the start of a starting symbol of a subsequent CG PUSCH that is closest to the radio resource (eg, CG-PUSCH) on which the URI is transmitted.

[0342] >When URI is sent on CG PUSCH, T excl The end time of the URI may be advanced by a predetermined time interval T from the start or end of the start symbol of the subsequent CG PUSCH closest to the radio resource (eg, CG-PUSCH) on which the URI is transmitted. proc,URI time point.

[0343] >When URI is sent on CG PUSCH, T exclThe end point may be a predetermined time interval T from the start of the periodicity including the corresponding CG PUSCH. proc,URI Alternatively, it may be a time point that is separated from the start of the periodicity including the subsequent CG PUSCH closest to the corresponding CG PUSCH by a predetermined time interval T. proc,URI time point.

[0344] >>Specific time interval T proc,URI The specific time interval T may be the time required for the BS to reschedule the UL radio resources indicated by the URI as unused resources starting from the URI transmission. proc,URI It can be a value given by the BS through 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. For example, as described in 3GPP TS 38.214, the N1 or N2 value obtained by considering the UE capabilities used to determine the time required for the PUCCH or PUSCH preparation process and the SCS of the UL BWP, or the time T calculated based on the N1 or N2 value proc,1 or T proc,2 Can be used to determine T proc,URI More specifically, the above values ​​can be used directly as T proc,URI , or a specific fraction of this value can be used as T proc,URI .

[0345] If the T determined above excl Overlapping with some PUSCH transmission opportunities, the following can be considered.

[0346] > It is possible to exclude from the URI indication at least one symbol and the time range T excl Other CG transmission opportunities (to which the corresponding URI is applied) that overlap (i.e., CG transmission opportunities to which the corresponding URI is applied in the CG configuration). That is, the targets whose availability is indicated by the URI may be excluded from which at least one symbol is incompatible with the time range T excl Overlapping other CG transmission opportunities (to which the corresponding URI applies).

[0347] > where at least one symbol is within the time range T excl Other overlapping CG transmission opportunities (i.e., CG PUSCH opportunities) (for which the corresponding URI applies) may be included in the URI indication. Thus, only a CG transmission opportunity may be excluded from the URI indication if all symbols of the opportunity overlap with an unused time interval or a radio resource indicated as unused.

[0348] > Symbols with a predetermined number X or more and a time range T may be excluded from the URI indication exclOverlapping other CG transmission opportunities (to which the corresponding URI is applied). The number of symbols X can be a value defined by the BS through L1 signaling and / or higher layer signaling, a predefined value, or derived according to the length of the CG transmission opportunity to which the URI is applied (i.e., the number of OFDM symbols belonging to the CG transmission opportunity). For example, assuming that the length of the CG transmission opportunity to which the URI is applied is L, if more symbols than ceil(L / N) (e.g., N=2 or 1.5) are included in the time range T excl If there is any overlap, the corresponding CG transmission opportunity can be excluded from the URI instruction.

[0349] <Implementation 1-4: Timing of Sending an Indication of Unused CG Resources>

[0350] When a URI including information on whether one or more CG PUSCHs are unused is transmitted on a CG PUSCH, the UE may not need to transmit a URI for each CG PUSCH. In this case, the UE may transmit the URI to a predetermined location as follows, thereby allowing the BS to identify whether multiple CG PUSCHs are unused at the same time while minimizing the overhead generated by the URI.

[0351] >The UE may send a URI on the first CG PUSCH opportunity of each periodicity. If the UE does not have an UL-SCH to send on the first CG PUSCH opportunity of each periodicity, the UE may send a CG PUSCH including only the URI without any UL-SCH. This operation may be limited to the case where the CG configuration field startingFromRV0-r16 is set to "on", which is used to determine the initial transmission timing of TBs for a given redundancy version (RV) sequence.

[0352] >UE can send URI at the end of each periodic transmission.

[0353] >UE may send the URI in the first transmission of each period. This operation may be restricted to the case where the CG configuration field startingFromRV0-r16 is set to "on".

[0354] <Implementation 1-5: Position of indication of unused CG resources>

[0355] In the operation described in Embodiment 1, the CG configuration of the CG PUSCH used to carry the URI may be different from the CG configuration applied to the URI. For example, the following can be configured by a specific CG PUSCH configuration (e.g., a CG configuration with an index of A): 1) whether the UE sends the URI through the corresponding CG PUSCH; and 2) to which CG PUSCH configuration (e.g., a CG configuration with an index of B) the unused resource information in the URI is related. As a result, the UE can be configured to indicate / send unused resource information for the CG configuration with an index of B via a URI on the CG PUSCH with an index of A. To this end, the following can be considered.

[0356] >Each CG configuration may include information about whether a URI is sent on the CG PUSCH of the corresponding CG configuration and / or one or more CG configuration indexes for receiving the URI (ie, the CG configuration index of the CG PUSCH used to transmit the URI).

[0357] >>If the corresponding CG configuration does not include a separate CG configuration index for receiving a URI (ie, a CG configuration index of a CG PUSCH used to transmit a URI), the URI may be restrictively applied to the corresponding CG configuration.

[0358] >> Alternatively, it may be assumed that the corresponding CG configuration is always included in the list of one or more CG configuration indices used for receiving URIs. When a URI is sent on the CG PUSCH for CG configuration X, it may be assumed that the URI applies to the CG PUSCH for configuration X, even if configuration X is not explicitly included in the list of CG configurations targeted by the URI.

[0359] >Each CG configuration may include information about whether the URI is sent on the CG PUSCH of the corresponding CG configuration and / or one or more CG configuration indexes in which the corresponding CG configuration references (or does not reference) the URI (i.e., the CG configuration index used to carry the CG PUSCH for the URI of the corresponding CG configuration).

[0360] >>If the corresponding CG configuration does not include a separate CG configuration index for referencing the URI, the URI may be restrictively applied to the corresponding CG configuration.

[0361] >>Alternatively, it may be assumed that the corresponding CG configuration is always included in one or more CG configuration indices of the reference URI. The above assumption may always hold true when its CG configuration index is always included in the CG configuration carrying the CG PUSCH for a specific CG configuration URI or when there is no explicit signaling.

[0362] >Alternatively, it may be assumed that a URI is always associated with all CG configurations. For example, if a URI sent on the CGPUSCH of a specific CG configuration indicates whether the CG PUSCH is unused within a predetermined time interval T, it may indicate whether the CG PUSCHs of all CG configurations configured within the corresponding time interval T are unused. In other words, according to any combination of the above-mentioned embodiments 1-1 / 2 / 3 / 4, if an unused CG PUSCH is reported for at least one CG configuration (i.e., 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 sends a URI on a CG PUSCH based on a specific CG configuration, if the time unit of the URI and the time interval T are based on the CG PUSCH opportunity, and if at least one CG PUSCH is indicated as unused within the time unit, the UE may use the URI indicating the corresponding time unit (including the unused CG PUSCH) as the time unit including the unused CG PUSCH.

[0363] Such an operation can be used for a method of transmitting information on whether a CG configuration for a video service (which is intermittently transmitted) is used via a URI transmitted based on a CG configuration for gesture data (which is continuously transmitted).

[0364] When using embodiments 1-5, a separate configuration for redefining the operation may be considered. For example, in order to protect CG configuration B, which is used to send high-priority services, from URI-based operations, it may be assumed that the URI sent by CG configuration A, which is a different configuration, is applied to all CGs except CG configuration B, as in the example above. Alternatively, even if CG configuration B is indicated as the target for the sent URI, the URI may be sent by ignoring this indication. The BS may indicate or configure such a configuration through L1 signaling (e.g., DCI) or higher-layer signaling (e.g., RRC signaling). In other words, L1 signaling and / or higher-layer signaling indicating / configuring immunity from URIs may be provided through conventional DCI fields / RRC parameters (e.g., priority indicators) or new DCI fields or new RRC parameters.

[0365] When using embodiments 1-2, 1-3 and / or 1-5, if the time interval T determined according to embodiment 1-2 or the separate time unit determined to indicate unused CG PUSCH resources in the time interval T is not aligned therewith, the URI may indicate only part of the CG PUSCH opportunities. For example, if the time unit is not aligned with the CG PUSCH opportunity and the time unit determined for the URI overlaps with only part of the CG PUSCH opportunity, the URI may indicate only the overlapping part. For example, when the URI indicates used / unused resources for the set of symbols #0 to #6 and the set of symbols #7 to #13 in the time slot, if the CG PUSCH occupies symbols #4 to #10 in the time slot, the URI may indicate use / non-use of some of the overlapping symbols. Alternatively, if the URI applies between CG configurations, as described in embodiment 1-5, the time interval and time unit of the corresponding CG transmission may indicate only part of the PUSCH transmission opportunities of the different CG configurations. In this case, the unused resources can be determined by considering the following:

[0366] > Time intervals indicated by a URI as unused or other CG transmission opportunities (where the corresponding URI applies) in which at least one symbol overlaps with a radio resource (directly) indicated as unused may be considered to be indicated as unused. In other words, time intervals indicated by a URI as unused or in which at least one symbol overlaps with a radio resource (directly) indicated as unused may be considered to be unused based on their use / non-use of different CG configurations indicated by the URI.

[0367] > Other CG transmission opportunities (applying the corresponding URI) that are time intervals indicated as unused by a URI or in which at least one symbol does not (directly) overlap with a radio resource indicated as unused may be considered as not indicated as unused. That is, all symbols of other CG transmission opportunities may be determined as unused only if their symbols overlap with the time interval or radio resource indicated as unused by the URI.

[0368] >Time intervals indicated by a URI as unused or other CG transmission opportunities (to which the corresponding URI is applied) in which radio resources overlap with a predetermined number or more symbols may be considered to be unused. The number of symbols X may be defined by L1 signaling and / or higher layer signaling from the BS, be a predefined value, or 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 transmission opportunity). For example, assuming that the length of the CG transmission opportunity to which the URI is applied is L, if more symbols than ceil(L / N) (e.g., N=2 or 1.5) overlap with the time interval / radio resource indicated by the URI as unused, the corresponding CG transmission opportunity may be determined to be unused.

[0369] >The UE may determine that a time interval indicated as unused by a URI or a radio resource (directly) indicated as unused is not used, and may not perform PUSCH transmission in the corresponding symbol. For other CG transmission opportunities (for which the corresponding URI is applied) that overlap with at least one symbol, the UE may stop transmission from the first symbol indicated as unused (i.e., the first symbol among the symbols of the other CG transmission opportunities that overlaps with the time interval / radio resource indicated as unused by the URI). However, transmission may be allowed until the symbol immediately preceding the first symbol indicated as unused (i.e., the symbol immediately preceding the first symbol that overlaps with the time interval / radio resource indicated as unused by the URI).

[0370] <Implementation 2: UL multiplexing for indicating unused CG resources>

[0371] When using embodiment 1, it is possible to consider that the UE sends a K-bit URI to the BS, which contains information about whether the CG PUSCH opportunity will be unused in the future. The URI can be multiplexed and sent on the CG PUSCH as described above. Specifically, when the URI is sent in the form of piggybacked UCI, a method of multiplexing the URI with other UCI that needs to be sent on the PUSCH can be considered. Specifically, the following can be considered:

[0372] *Method 1: The URI can be assumed to be a type of CG-UCI. For example, the URI can be considered to be a CG-UCI as described in 3GPP TS38.212 and multiplexed. The CG configuration for shared spectrum includes a higher layer parameter cgRetransmissionTimer. If the UE does not receive a CG-DL feedback indicator (i.e., configuration grant downlink feedback information (CG-DFI)) providing HARQ-ACK information for the initial transmission of the TB on the PUSCH configured by the CG configuration before the expiration of the cgRetransmissionTimer, the UE can assume that the TB is not correctly decoded, and then perform autonomous retransmission at the next CG PUSCH opportunity based on the CG configuration. UCI, referred to as CG-UCI, can be included in each CG PUSCH transmission. Here, the CG-UCI includes information about the HARQ process ID, RV, new data indicator (NDI), and channel occupancy time (COT) sharing information. If other CG-UCIs are already included in the PUSCH, the URI is considered to be an additional bit field included in the corresponding CG-UCI. The UE can multiplex the URI into a single CG UCI by concatenating the URI with a bit sequence generated based on other CG-UCIs. This operation can be limited to the case where the UE uses an unlicensed band, that is, the case where the UE always includes the CG-UCI in the CG PUSCH to send the CGPUSCH. In other words, the URI can be multiplexed and sent together with the HARQ-ACK. For example, when there is no other HARQ-ACK on the PUSCH (such as in the CG-UCI described in 3GPP TS 38.212), the URI can be multiplexed with the PUSCH alone in the same way as the HARQ-ACK. If HARQ-ACK is included in the PUSCH, the URI can be jointly compiled with the corresponding HARQ-ACK and multiplexed as one compiled bit sequence on the PUSCH.

[0373] *Method 2: The URI can be considered as CSI Part 1 and then multiplexed on the PUSCH. For example, the URI can be considered as CSI Part 1 described in 3GPP TS 38.212 and multiplexed. If other CSI is already included in the PUSCH, the UE can concatenate the URI with the bit sequence of the corresponding CSI Part 1 and multiplex the URI as CSI Part 1 onto the PUSCH. In some embodiments, this operation can be limited to the case where the UE does not use the unlicensed band, that is, the CG PUSCH does not contain CG-UCI other than the URI to transmit the CG PUSCH. In some embodiments, this operation can be limited to the case where the size of the URI is always fixed.

[0374] *Method 3: The URI may be considered as CSI Part 2 and then multiplexed on the PUSCH. For example, the URI may be considered as Part 2 of the CSI described in 3GPP TS 38.212 and then multiplexed. If other CSI Part 2 is needed in the PUSCH, the UE may discard the corresponding CSI Part 2 and include the URI on the PUSCH by replacing the CSI Part 2 with the URI. Alternatively, the UE may concatenate the bit sequence of the CSI Part 2 with the URI and multiplex the URI as the CSI Part 2 on the PUSCH. To this end, an indicator indicating the length of the URI may be included in the CSI Part 1. This operation may be limited to the case where the UE does not use an unlicensed band, that is, the case where the CG-UCI other than the URI is not included in the CG PUSCH to transmit the CGPUSCH.

[0375] As described above, depending on whether the UE uses the unlicensed band, the UE can use Method 1 or Method 2 / 3. Alternatively, the UE can send a UE capability report for Method 1 / 2 / 3 to the BS, and the BS can configure one of Methods 1 / 2 / 3 based on the UE capability report.

[0376] The ability of each UE to include CG-UCI and URI in PUSCH may be different. For example, in a conventional NR wireless communication system, there are UEs that are capable of jointly compiling HARQ-ACK and CG-UCI and multiplexing HARQ-ACK and CG-UCI on PUSCH or PUCCH, and UEs that are unable to perform such transmissions. Each UE can provide the network / BS with information about whether each UE is capable of performing the operation through a capability report. If the UE is able to do this, the UE can process and multiplex two types of UCI and send the UCI. However, if the UE is unable to perform the operation or the BS configures the UE not to perform the operation, the UE can send HARQ-ACK PUCCH and then discard the CG-UCI and CG PUSCH for this purpose. This is because CG-UCI transmission is essential for CG PUSCH transmission in the unlicensed band. On the other hand, the URI according to some embodiments of the present disclosure is similar to the CG-UCI in form and transmission method, but the URI may not be essential for CG PUSCH transmission. Specifically, when the UE performs NR wireless communication in the licensed band, the BS can successfully receive the PUSCH without receiving the URI sent from the UE. In this case, the necessity of dropping PUSCH transmission due to the joint encoding of CG-UCI or the inability to jointly encode CG-UCI with other UCI is reduced.

[0377] Therefore, in the unlicensed band (i.e., shared spectrum) and the licensed band, when the CG-UCI that is critical to CG PUSCH transmission is multiplexed with the URI and sent (for example, when the higher layer parameter cg-RetransmissionTimer is configured), and when other CG-UCI (i.e., CG-UCI that is not critical to CG PUSCH transmission), URI, or URI multiplexed therewith is sent (for example, when the higher layer parameter cg-RetransmissionTimer is not configured), if additional multiplexing or joint encoding with other UCI (e.g., HARQ-ACK) is required, the UE can perform different operations as follows.

[0378] >When the CG-UCI that is essential for CG PUSCH transmission is multiplexed with the URI and sent as one UCI, for example, when the higher layer parameter cg-RetransmissionTimer is configured,

[0379] >>If the UE is capable of jointly encoding CG-UCI and other UCI that needs to be multiplexed (e.g., HARQ-ACK) (or if the UE is configured to perform joint encoding), the UE may perform at least one of the following operations.

[0380] >>>CG-UCI, URI, and HARQ-ACK are jointly compiled into one UCI and then multiplexed and transmitted on the CG PUSCH. This operation may be limited to cases where the UE is capable of joint coding, especially when no other UCI (e.g., SR, CSI, etc.) is present. If the UE is capable of jointly encoding the CG-UCI, URI, and HARQ-ACK into one UCI as described above, the UE may send a capability report to inform the BS of the UE's capabilities.

[0381] >>>CG-UCI and HARQ-ACK are jointly compiled into one UCI and then multiplexed and sent on the CG PUSCH. In this case, the URI will be discarded, that is, no URI is sent. This operation allows the transmission of the URI when there is no HARQ-ACK transmission while maintaining normal operation.

[0382] >>>Discard CG-UCI and URI when not sending CG PUSCH, and send HARQ-ACK on PUCCH. This operation can be applied to the case where CG-UCI is first encoded together with URI, and as a result, it is difficult to additionally multiplex HARQ-ACK. Alternatively, this operation can be applied to the case where it is difficult to multiplex CG-UCI and HARQ-ACK.

[0383] >>If the UE is unable to jointly encode CG-UCI and other UCI (e.g., HARQ-ACK) (or if the UE is configured not to perform joint encoding), the UE may perform at least one of the following operations.

[0384] >>>Discard CG-UCI and URI without sending CG PUSCH, and send HARQ-ACK on PUCCH.

[0385] >When a CG-UCI that is not critical to transmission, a UCI where the CG-UCI is multiplexed with a URI, or a URI is sent, for example, when the higher layer parameter cg-RetransmissionTimer is not configured

[0386] >>If the UE is capable of jointly encoding CG-UCI and other UCI that needs to be multiplexed (e.g., HARQ-ACK) (or if the UE is configured to perform joint encoding), the UE may perform at least one of the following operations.

[0387] >>>Jointly compile the CG-UCI, URI, and HARQ-ACK into one UCI and then multiplex and transmit it on the CG PUSCH. This operation may be limited to cases where the UE is capable of joint compilation, especially when there is no other UCI (e.g., SR, CSI, etc.). If the UE is capable of jointly compiling the CG-UCI, URI, and HARQ-ACK into one UCI as described above, the UE may send a capability report to inform the BS of the UE's capability.

[0388] >>>CG-UCI or URI is jointly compiled with HARQ-ACK into one UCI. Then, the CG-UCI or URI is multiplexed with HARQ-ACK on the CG PUSCH and sent. If there is an unmultiplexed URI or CG-UCI, the unmultiplexed URI or CG-UCI is discarded, that is, not sent. This operation allows the transmission of URI while maintaining normal operation when there is no HARQ-ACK transmission. The UCI to be multiplexed with HARQ-ACK and sent through CG-PUSCH among the CG-UCI or URI can be predefined or can be provided to the UE through L1 signaling or higher layer signaling from the BS.

[0389] >>> In the case where CG PUSCH is not transmitted, CG-UCI and URI are discarded, and HARQ-ACK is transmitted on PUCCH. This operation can be applied to the case where CG-UCI is first encoded with URI, and as a result, it is difficult to additionally multiplex HARQ-ACK. Alternatively, this operation can be applied to the case where it is difficult to multiplex CG-UCI and HARQ-ACK.

[0390] >>If the UE is unable to jointly encode CG-UCI and other UCI (e.g., HARQ-ACK) (or if the UE is configured not to perform joint encoding), the UE may perform at least one of the following operations.

[0391] >>>The UE sends a CG-PUSCH multiplexed with HARQ-ACK by discarding the CG-UCI and URI. If the UE is unable to perform joint coding, the UE may send HARQ-ACK through a CG-PUSCH that is different from the prior art.

[0392] >>>Discard CG-UCI and URI without sending CG PUSCH, and send HARQ-ACK on PUCCH.

[0393] >When the CG-UCI and URI, which are essential for CG PUSCH transmission, are separately encoded and sent as each UCI

[0394] >>If the UE is capable of jointly encoding CG-UCI and other UCI that needs to be multiplexed (such as HARQ-ACK) (or if the UE is configured to perform joint encoding), the UE may perform at least one of the following operations.

[0395] >>>Jointly compile the CG-UCI, URI, and HARQ-ACK into one UCI and then multiplex and transmit it on the CG PUSCH. This operation may be limited to cases where the UE is capable of joint compilation, especially when no other UCI (e.g., SR, CSI, etc.) is present. If the UE is capable of jointly compiling the CG-UCI, URI, and HARQ-ACK into one UCI as described above, the UE may send a capability report to inform the BS of the UE's capability.

[0396] >>>CG-UCI and HARQ-ACK are jointly compiled into one UCI and then multiplexed and sent on the CG PUSCH. In this case, the URI is discarded, that is, the URI is not sent. This operation allows the transmission of the URI while maintaining normal operation when there is no HARQ-ACK transmission.

[0397] >>> In the case where CG PUSCH is not transmitted, CG-UCI and URI are discarded, and HARQ-ACK is transmitted on PUCCH. This operation can be applied to the case where CG-UCI is first encoded together with URI, and as a result, it is difficult to additionally multiplex HARQ-ACK. Alternatively, this operation can be applied to the case where it is difficult to multiplex CG-UCI and HARQ-ACK.

[0398] >>If the UE is unable to jointly encode the CG-UCI and other UCI (e.g., HARQ-ACK) (or if the UE is configured not to perform joint encoding), the UE may perform at least one of the following operations.

[0399] >>>If additional UCI multiplexing is not required (e.g., if a single type of UCI is included (e.g., HARQ-ACK)), the URI is discarded and only CG-UCI is sent on PUSCH.

[0400] >>>If there is HARQ-ACK that needs to be multiplexed, do not send CG PUSCH, discard CG-UCI and URI, and send HARQ-ACK on PUCCH.

[0401] When the CG-UCI is discarded for other purposes, such as indicating the NDI for each transmission, the value included in the CG-UCI can always be fixed to a specific value. For example, if the CG-UCI is discarded, the NDI value can always be assumed to be 0.

[0402] As another example, when using embodiment 1, the UE can transmit a K-bit URI to the base station on a separate PUCCH. This URI contains information about whether a CG PUSCH opportunity will be used in the future. In this case, it is necessary to consider a method for multiplexing the URI with other UCI assumed to be transmitted on the PUCCH. To this end, the following method can be considered.

[0403] >URI is considered as SR and can be multiplexed on PUCCH. That is, URI can be multiplexed on PUCCH in the same way as the method of sending SR on PUCCH, which is described in 3GPP TS 38.212.

[0404] >In the above case, according to some embodiments, if the URI is multiplexed with other UCI, the URI can be sent in multiple bit sizes.

[0405] >In the above case, according to some embodiments, when only a URI is transmitted on a PUCCH without other UCI, if the URI has 2 bits or more, the URI is considered to be a HARQ-ACK and can be multiplexed on the PUCCH in the same manner as the method of transmitting HARQ-ACK on the PUCCH described in 3GPP TS 38.212.

[0406] In the above case, according to some embodiments, if only a URI is transmitted on the PUCCH without other UCI, it is possible to immediately indicate whether all CG PUSCH opportunities associated with the URI are used using 1 bit of information. For example, when the URI indicates use / non-use of time interval T, the 1-bit URI can indicate use or non-use of the entire time interval T.

[0407] In some embodiments, in a situation where the UE does not have the capability of joint coding between URI and HARQ-ACK, or the joint coding is not configured for a UE with such capability, when a particular CG PUSCH includes a URI without the traditional CG-UCI, if the CG PUSCH overlaps with the HARQ-ACK PUCCH in time, the UE may multiplex and send the HARQ-ACK on the corresponding CG PUSCH while skipping (or discarding) the URI transmission.

[0408] Considering embodiment 1, in some embodiments, when the size of the URI information is 2 bits or less or the URI is jointly encoded with the HARQ-ACK, the sum of the sizes of the URI and HARQ-ACK information (i.e., the result of the joint encoding) may be 2 bits or less. In this case, at least one of the following may be considered:

[0409] When a UE transmits a URI of 2 bits or less or jointly encodes a URI and HARQ-ACK, if the sum of the URI and HARQ-ACK information sizes is 2 bits or less, the UE can puncture the PUSCH and transmit UCI at a fixed position in the same manner as transmitting an HARQ-ACK of 2 bits or less in the prior art. The base station can receive / acquire UCI by assuming the above UE operation.

[0410] When a UE transmits a URI of 2 bits or less or jointly encodes a URI and HARQ-ACK, if the sum of the URI and HARQ-ACK information sizes (i.e., the result of the joint encoding) is 2 bits or less, the UE can perform rate matching on the PUSCH and transmit UCI in the same manner as transmitting HARQ-ACK of 3 bits or more in the prior art. To this end, in some embodiments, the URI or both the URI and HARQ-ACK information can be padded with "0" bits, resulting in a total of 3 bits or more. The base station can receive / acquire UCI by assuming the above UE operation.

[0411] > When the UE sends a URI of 2 bits or less, the UE may exclude the URI from transmission and send only PUSCH and other UCI. The base station may receive / acquire UCI by assuming the above UE operation.

[0412] > When the size of UCI obtained by jointly compiling URI and HARQ-ACK is 2 bits or less, the UE may exclude the URI from transmission and send HARQ-ACK and other UCI on the PUSCH. The BS may receive / acquire UCI by assuming the above UE operation.

[0413] <Implementation 3: Two-priority handling of indications of unused CG resources>

[0414] When a UE transmits a URI on a PUSCH or PUCCH, and more specifically, transmits a URI on a PUSCH or PUCCH at a fixed location (e.g., on the first CG PUSCH transmitted periodically), it can be considered that the corresponding transmission is discarded by other UL transmissions, particularly high-priority PUCCH or PUSCH. In this case, the BS may not be able to receive the URI at the assigned time. In this case, the following UE and BS operations can be considered.

[0415] >If the UE fails to transmit a specific URI, the UE may assume that not all CG PUSCHs are reported as unused within the time interval in which the use / non-use of CG PUSCH is indicated by the corresponding URI. In this case, if the BS does not receive the specific URI, the BS may assume that not all CG PUSCHs are unused within the time interval in which the corresponding URI indicates whether CG PUSCH is unused. The BS may not perform rescheduling within the corresponding time interval.

[0416] >If the UE fails to send a specific URI, the UE may assume that not all CG PUSCHs are reported as unused within the time interval in which the use / non-use of CG PUSCHs is indicated by the corresponding URI. Therefore, the UE may not use all CG PUSCHs within the time interval. In this case, if the BS does not receive the specific URI, the BS may assume that not all CG PUSCHs are used within the time interval in which the corresponding URI indicates whether the CG PUSCHs are unused. The BS may perform rescheduling within the corresponding time interval.

[0417] <Implementation 4: Two Codeword URIs for CG PUSCH>

[0418] When a UE transmits a URI on a PUSCH, the CG PUSCH indicated by the URI can be considered to include two or more codewords, that is, two or more TBs. If the UE is capable of transmitting two or more TBs on a radio resource, the UE may not use the radio resource and transmit only one TB, or may transmit two TBs based on the user data received by the UE. By indicating the above situation via a URI, the UE can not only inform the BS whether to perform transmission on the corresponding radio resource, but also how many TBs to transmit. More specifically, the following can be considered.

[0419] >When the URI is configured using a bitmap, if the CG PUSCH can include two or more codewords, that is, two or more TBs, the bit size corresponding to each CG PUSCH can be 2 bits. In this case, the following bit representation can be used to indicate whether the CG PUSCH is used.

[0420] >>>If the UE does not use the corresponding radio resources, "11" is set at the corresponding bit position.

[0421] >>>If the UE sends only one TB, set "01" or "10" at the corresponding bit position.

[0422] >>>If the number of TBs transmitted by the UE is not determined or two TBs are transmitted, "00" is set at the corresponding bit position.

[0423] >As another example, when the URI is configured using a bitmap, if the CG PUSCH can include two or more codewords, ie, 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.

[0424] >As another example, when a URI is transmitted in consideration of a TB, MIMO-related information that a BS can assume upon reception, for example, information on a transport layer and a DMRS port, may be additionally transmitted.

[0425] <Implementation 5: URI for CG PUSCH Repetition or TB over Multiple Slots (TBoMS)>

[0426] When a UE transmits a URI on the PUSCH, it can be considered that one TB is repeatedly transmitted on multiple radio resources based on repeated transmissions on the corresponding PUSCH, or that one TB is transmitted on multiple radio resources across multiple time slots (e.g., via TB over multiple slots (TBs)). TBoMS is a technology introduced to address the difficulty in correctly processing TBs due to insufficient TB size applied to PUSCHs, when the TB size determines the number of resource elements (REs) scheduled in the time slot in which the PUSCH is transmitted. According to TBoMS, one PUSCH is transmitted or processed across multiple time slots. The number of time slots included in TBoMS is configured by the RRC signaling numberOfSlots-TBoMS, which is used when calculating the size of the TB used in TBoMS. According to TBoMS, the size of the TB can be derived based on the number of REs in the PUSCH scheduled across multiple time slots.

[0427] When a UE transmits a URI on a PUSCH, if a TB is repeatedly transmitted on multiple radio resources based on repeated transmissions on the corresponding PUSCH or if a TB is transmitted on multiple radio resources across multiple time slots, the UE may treat the multiple radio resources as one radio resource and transmit the URI, or transmit a single URI shared by the multiple radio resources. More specifically, the following may be considered.

[0428] *Method 1-1: When a URI is configured using a bitmap, if TBoMS or repeated transmission is used, multiple radio resources used to transmit one TB can correspond to one bit. In other words, 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. In other words, the bundle of radio resources used to transmit one TB corresponds to one bit. For example, when a single TB is configured / instructed to be repeatedly transmitted on N radio resources (e.g., N PUSCHs), the entire set of N radio resources can correspond / map to one bit in the URI. In this case, a K-bit URI on the CG PUSCH that transmits a specific TB can indicate whether each of the K CG PUSCH sets that transmit the other K TBs is unused. In this case, a K-bit URI on the CG PUSCH that carries a specific TB can indicate whether each of the subsequent K CG PUSCH sets transmits the other K TBs.

[0429] *Method 1-2: As described in Embodiment 1, one radio resource may correspond to one bit. In other words, each bit in the bitmap may correspond to each CG PUSCH radio resource within a period. For example, when a single TB is configured / instructed to be repeatedly transmitted on N radio resources (e.g., N PUSCHs), each radio resource may correspond to / map to one bit in the URI.

[0430] In some implementations, the UE may only transmit a URI on valid (i.e., transmittable) radio resources. For example, considering the contents of Section 11.1 of 3GPP TS 38.213, URI information may only be transmitted on transmittable radio resources. In this case, to use Method 1-1, if at least one PUSCH is transmittable among multiple radio resources used to transmit a TB, URI information for the corresponding TB may be generated. That is, when using Method 1-1, the bitmap may include information regarding whether a TB that can be transmitted on at least one valid radio resource will be transmitted in the future.

[0431] Table 7

[0432]

[0433] As in embodiment 1-1, if the UE sends a URI on the CG PUSCH, for example, by sending the URI to the BS via UCI piggybacked on the CG PUSCH, the CG PUSCH can be considered repeated. If repeated transmission is configured for the CG PUSCH carrying the URI, the following can be considered to send the URI.

[0434] *Method 2-1: The URI may be considered to be sent and included in all repeated transmissions. For example, when a single TB is configured / instructed to be repeatedly transmitted on N radio resources (e.g., N PUSCHs), the URI may be sent on each of these N radio resources.

[0435] *Method 2-2: The URI may be considered to be included only in a specific repetitive transmission (e.g., the first repetitive transmission) in a bundle for transmitting repetitive transmissions of a single TB. For example, if a single TB is configured / instructed to be repeatedly transmitted on N radio resources (e.g., N PUSCHs), the URI may be transmitted only on a specific radio resource (e.g., the first radio resource) among the N radio resources, and URI transmission may be discarded on the remaining radio resources.

[0436] When a URI is sent for the same TB or the same PUSCH opportunity during repeated transmission, the UE may assume that the same URI is always sent during the repeated transmission. In subsequent URI transmissions, the UE may always send the same URI value without evaluation. For example, during a bundle of repeated transmissions for sending a single TB, the UE may generate and send a URI value by evaluating the usage status of the TB transmission or PUSCH opportunity before the first URI transmission. The UE may send a URI on the CG PUSCH where repeated transmissions are configured by combining method 1 and method 2. For example, if the URI is sent on all repeated transmissions as in method 2-1, the UE may use method 1-2 to indicate whether each radio resource within the repeated transmission bundle is used. Alternatively, the UE may use method 1-1 to indicate whether all repeated transmission bundles are used by a single bit for each repeated transmission bundle. In addition, when method 1-2 is used to indicate whether each radio resource within the repeated transmission bundle is used, the URI value sent on each radio resource within the repeated transmission bundle may always be the same as described above.

[0437] In some embodiments, the UE may reference a separate RRC parameter value to select one of Method 1-1 and Method 1-2. For example, the UE may reference the parameter startingFromRV0 within the IE ConfiguredGrantConfig. If the corresponding value is set to "off", the UE always starts transmission from the first transmission of the repeated transmission bundle to send the TB. Therefore, when sending a TB, the UE always uses radio resources for the first transmission. In this case, even if Method 1-1 is used to include only the URI in the first repeated transmission, one URI is always sent for each TB. On the other hand, if the value of the parameter startingFromRV0 is "on", the UE may start transmission in the middle of the repeated transmission bundle. In this case, the BS may not be able to predict the UE's transmission starting position. Therefore, the UE needs to send the URI each time as in Method 1-2. Therefore, when the parameter startingFromRV0 is set to "off", Method 1-1 can be used; and when the parameter startingFromRV0 is set to "on", Method 1-2 can be used.

[0438] As another example, depending on the total size X of the URI bitmap and the number of times the CG PUSCH is repeatedly transmitted Y (or the number of CG PUSCHs within a periodicity), method 2-1 or 2-2 can be used. For example, if X>Y, method 2-1 can be used; however, if Y>=X, method 2-2 can be used.

[0439] According to some embodiments of the present disclosure, the UE can selectively use the CG PUSCH as in the prior art and report unselected radio resources to the BS in advance. According to some embodiments of the present disclosure, the UE can effectively report the actual usage status of the radio resources scheduled for the UE to the BS. According to some embodiments of the present disclosure, the BS can use the radio resources for other UL transmissions, thereby reducing the burden on UL radio resources. In addition, the BS can efficiently transmit information such as video in which the payload size of various services or services changes dynamically.

[0440] Figure 13 The diagram illustrates a UL signal transmission process of a UE according to some embodiments of the present disclosure.

[0441] A UE may perform operations associated with uplink signal transmission according to some embodiments of the present disclosure. The UE may include 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 disclosure. A processing device for the UE may include 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 disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program including instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some embodiments of the present disclosure. A computer program or computer program product may include instructions recorded on at least one computer-readable (non-transitory) storage medium. When executed, the instructions cause (the at least one processor) to perform operations according to some embodiments of the present disclosure. The computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may include instructions that, when executed, cause (the at least one processor) to perform operations according to some embodiments of the present disclosure.

[0442] refer to Figure 13The method performed by a UE or the operations of the UE, a processing device, a computer-readable (non-transitory) storage medium, and / or a computer program product may include: receiving a CG configuration (S1301); and transmitting a first CG PUSCH including a UTO-UCI (e.g., the URI described in Embodiments 1 to 5) on 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. The N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE may transmit a CG PUSCH on the corresponding CG PUSCH opportunity (i.e., there is a possibility that the UE may transmit a CG PUSCH on the relevant CG PUSCH opportunity), and the second bit value may indicate that the UE intends to transmit a CG PUSCH on the corresponding CG PUSCH opportunity.

[0443] In some implementations, N may be provided by higher layer signaling.

[0444] In some embodiments, N may be provided for a CG configuration.

[0445] In some implementations, the subsequent N CG PUSCH opportunities that are mapped one-to-one to the N bits of the N-bit bitmap may be obtained by excluding invalid PUSCH opportunities.

[0446] In some embodiments, an invalid CG PUSCH opportunity may be a CG PUSCH opportunity that overlaps with a symbol indicated as UL by a TDD UL-DL configuration (eg, RRC parameter tdd-UL-DL-ConfigurationCommon and / or RRC parameter tdd-UL-DL-ConfigurationDedicated).

[0447] In some implementations, an invalid CG PUSCH opportunity is a CG PUSCH opportunity that overlaps with a symbol in an SS / PBCH block (eg, a symbol in the SS / PBCH block with an index given by the RRC parameter ssb-PositionsInBurst).

[0448] In some embodiments, the method or operation may include: based on HARQ-ACK information to be sent at the first CG PUSCH opportunity: obtaining jointly coded bits by jointly coding the HARQ-ACK information and the UTO-UCI; and mapping the jointly coded bits to the first CG PUSCH through rate matching.

[0449] In some embodiments, the method or operation may include not transmitting the CG PUSCH on a CG PUSCH opportunity mapped to a bit having the second value among the N bits.

[0450] Figure 14 FIG. 1 illustrates a UL signal reception process of a BS according to some embodiments of the present disclosure.

[0451] A base station (BS) may perform operations associated with receiving uplink (UL) signals according to some embodiments of the present disclosure. The BS may include 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 according to some embodiments of the present disclosure. A processing device for the BS may include 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 according to some embodiments of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program including instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some embodiments of the present disclosure. A computer program or computer program product may include instructions recorded on at least one computer-readable (non-transitory) storage medium that, when executed, cause (the at least one processor) to perform operations according to some embodiments of the present disclosure.

[0452] refer to Figure 14 The method performed by a base station (BS) or the operations of a BS, a processing device, a computer-readable (non-transitory) storage medium, and / or a computer program product may include: transmitting a CG configuration (S1401); and receiving a first CG PUSCH including a UTO-UCI (e.g., the URI described in Embodiments 1 to 5) from a UE on a first CG PUSCH opportunity based on the CG configuration (S1403). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are mapped one-to-one to N CG PUSCH opportunities following the first PUSCH opportunity, where each of the N bits has a first bit value or a second bit value. The first bit value may indicate that the UE may transmit a CG PUSCH on the corresponding CG PUSCH opportunity (i.e., there is a possibility that the UE may transmit a CG PUSCH on the relevant CG PUSCH opportunity), and the second bit value may indicate that the UE is expected to transmit a CG PUSCH on the corresponding CG PUSCH opportunity.

[0453] In some implementations, N may be provided by higher layer signaling from the BS.

[0454] In some embodiments, N may be provided for a CG configuration.

[0455] In some implementations, the subsequent N CG PUSCH opportunities that are mapped one-to-one to the N bits of the N-bit bitmap may be obtained by excluding invalid PUSCH opportunities.

[0456] In some embodiments, an invalid CG PUSCH opportunity may be a CG PUSCH opportunity that overlaps with a symbol indicated as UL by a TDD UL-DL configuration (eg, RRC parameter tdd-UL-DL-ConfigurationCommon and / or RRC parameter tdd-UL-DL-ConfigurationDedicated).

[0457] In some implementations, an invalid CG PUSCH opportunity is a CG PUSCH opportunity that overlaps with a symbol in an SS / PBCH block (eg, a symbol in the SS / PBCH block with an index given by the RRC parameter ssb-PositionsInBurst).

[0458] In some embodiments, the method or operation may include: obtaining bits for joint coding of the HARQ-ACK information and the UTO-UCI on the first PUSCH based on HARQ-ACK information to be received on the first CG PUSCH opportunity. The method or operation may include assuming that the jointly coded bits are mapped to the first CG PUSCH by rate matching.

[0459] In some embodiments, the method or operation may include anticipating not receiving a CG PUSCH on a CG PUSCH opportunity mapped to a bit having a second value among the N bits.

[0460] The examples of the present disclosure described above are intended to enable those skilled in the art to implement and practice the present disclosure. Although the present disclosure has been described with reference to examples, those skilled in the art may make various modifications and variations to the examples of the present disclosure. Therefore, the present disclosure is not limited to the examples set forth herein, but should be accorded the widest scope consistent with the principles and features disclosed herein.

[0461] The embodiments of the present disclosure may be applied to a BS, a UE, or other devices in a wireless communication system.

Claims

1. A method for transmitting an uplink signal by a user equipment (UE) in a wireless communication system, the method comprising: Receive configuration clearance (CG) configuration; as well as Based on the CG configuration, transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission opportunity uplink control information (UTO-UCI) on a first CG PUSCH opportunity, The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. wherein the N bits of the N-bit bitmap are mapped one-to-one to N CGPUSCH opportunities following the first PUSCH opportunity, wherein each of the N bits has a first bit value or a second bit value, The first bit value indicates that the UE can send CG PUSCH in the corresponding CG PUSCH opportunity, and The second bit value indicates that the UE does not send CG PUSCH in the corresponding CG PUSCH opportunity.

2. The method according to claim 1, wherein N is provided by higher layer signaling.

3. The method according to claim 2, wherein: Provide N for the CG configuration.

4. The method according to claim 1, wherein Subsequent N CG PUSCH opportunities that are one-to-one mapped to the N bits of the N-bit bitmap are obtained by excluding invalid PUSCH opportunities.

5. The method according to claim 4, wherein The invalid CG PUSCH opportunity is a CG PUSCH opportunity that overlaps with a symbol indicated as uplink by a time division duplex (TDD) uplink-downlink configuration.

6. The method according to claim 4, wherein: The invalid CG PUSCH opportunity is a CG PUSCH opportunity that overlaps with a symbol in a synchronization signal / physical broadcast channel block.

7. The method according to claim 1, further comprising: Based on the presence of Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information to be sent on the first CG PUSCH opportunity: Obtaining jointly-coded bits by jointly coding the HARQ-ACK information and the UTO-UCI; and The jointly coded bits are mapped to the first CG PUSCH through rate matching.

8. The method according to claim 1, comprising: CGPUSCH is not transmitted on a CG PUSCH opportunity mapped to a bit having the second value among the N bits.

9. A user equipment (UE) configured to transmit an uplink signal in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations comprising: Receive Configuration Grant (CG) configuration; and Based on the CG configuration, transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission opportunity uplink control information (UTO-UCI) on a first CG PUSCH opportunity, The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. wherein the N bits of the N-bit bitmap are mapped one-to-one to N CGPUSCH opportunities following the first PUSCH opportunity, wherein each of the N bits has a first bit value or a second bit value, The first bit value indicates that the UE can send CG PUSCH in the corresponding CG PUSCH opportunity, and The second bit value indicates that the UE does not send CG PUSCH in the corresponding CG PUSCH opportunity.

10. A processing device in a wireless communication system, the processing device comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations comprising: Receive Configuration Grant (CG) configuration; and Based on the CG configuration, transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission opportunity uplink control information (UTO-UCI) on a first CG PUSCH opportunity, The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. wherein the N bits of the N-bit bitmap are mapped one-to-one to N CGPUSCH opportunities following the first PUSCH opportunity, wherein each of the N bits has a first bit value or a second bit value, The first bit value indicates that the user equipment (UE) can send CGPUSCH in the corresponding CG PUSCH opportunity, and The second bit value indicates that the UE does not send CG PUSCH in the corresponding CG PUSCH opportunity.

11. A computer-readable storage medium configured to store at least one program code comprising instructions that, when executed, cause at least one processor to perform operations comprising: Receive configuration clearance (CG) configuration; as well as Based on the CG configuration, transmitting a first CG physical uplink shared channel (PUSCH) including unused transmission opportunity uplink control information (UTO-UCI) on a first CG PUSCH opportunity, The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. wherein the N bits of the N-bit bitmap are mapped one-to-one to N CGPUSCH opportunities following the first PUSCH opportunity, wherein each of the N bits has a first bit value or a second bit value, The first bit value indicates that the user equipment (UE) can send CGPUSCH in the corresponding CG PUSCH opportunity, and The second bit value indicates that the UE does not send CG PUSCH in the corresponding CG PUSCH opportunity.

12. A method for receiving, by a base station (BS), an uplink signal from a user equipment (UE) in a wireless communication system, the method comprising: Send configuration permission (CG) configuration; as well as receiving, based on the CG configuration, a first CG physical uplink shared channel (PUSCH) including unused transmission opportunity uplink control information (UTO-UCI) on a first CG PUSCH opportunity, The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. wherein the N bits of the N-bit bitmap are mapped one-to-one to N CGPUSCH opportunities following the first PUSCH opportunity, wherein each of the N bits has a first bit value or a second bit value, The first bit value indicates that the UE can send CG PUSCH in the corresponding CG PUSCH opportunity, and The second bit value indicates that the UE does not send CG PUSCH in the corresponding CG PUSCH opportunity.

13. A base station (BS) configured to receive an uplink signal from a user equipment (UE) in a wireless communication system, the BS comprising: at least one transceiver; at least one processor; as well as at least one computer memory operatively connected to the at least one processor and configured to store instructions that, when executed, cause the at least one processor to perform operations comprising: Sending Configuration Grant (CG) configuration; and receiving, based on the CG configuration, a first CG physical uplink shared channel (PUSCH) including unused transmission opportunity uplink control information (UTO-UCI) on a first CG PUSCH opportunity, The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. wherein the N bits of the N-bit bitmap are mapped one-to-one to N CGPUSCH opportunities following the first PUSCH opportunity, wherein each of the N bits has a first bit value or a second bit value, The first bit value indicates that the UE can send CG PUSCH in the corresponding CG PUSCH opportunity, and The second bit value indicates that the UE does not send CG PUSCH in the corresponding CG PUSCH opportunity.

14. The BS according to claim 13, wherein: N is provided by higher layer signaling from the BS.

15. The BS according to claim 14, wherein: N is provided by the higher layer signaling.

16. The BS according to claim 13, wherein: Subsequent N CG PUSCH opportunities that are one-to-one mapped to the N bits of the N-bit bitmap are obtained by excluding invalid PUSCH opportunities.

17. The BS according to claim 16, wherein: The invalid CG PUSCH opportunity is a CG PUSCH opportunity that overlaps with a symbol indicated as uplink by a time division duplex (TDD) uplink-downlink configuration.

18. The BS according to claim 16, wherein: The invalid CG PUSCH opportunity is a CG PUSCH opportunity that overlaps with a symbol in a synchronization signal / physical broadcast channel block.

19. The BS according to claim 13, wherein: The operations include: obtaining bits for jointly coding hybrid automatic repeat request acknowledgement (HARQ-ACK) information and the UTO-UCI on the first PUSCH based on the presence of HARQ-ACK information to be received on the first CG PUSCH opportunity, and The jointly coded bits are mapped to the first CG PUSCH through rate matching.

20. The BS according to claim 13, wherein The operations include anticipating not receiving a CG PUSCH on a CG PUSCH opportunity mapped to a bit having the second value among the N bits.

Images