User equipment method and device, storage medium, base station method and base station

Abstract

The UE may receive a CG configuration for a cell, and transmit a UTO-UCI based on the CG configuration, where the UTO-UCI may relate to a CG PUSCH occasion that does not include a CG PUSCH occasion that overlaps with a cell DRX inactive period.

Description

Technical Field

[0001] This disclosure relates to a wireless communication system. Background Technology

[0002] Technologies such as machine-to-machine (M2M) communication, machine-type communication (MTC), and various devices requiring high data throughput (e.g., smartphones and tablet PCs) have emerged and become widespread. Consequently, the data throughput required to be processed in cellular networks is rapidly increasing. To meet this rapidly increasing data throughput, carrier aggregation or cognitive radio technologies have been developed for the efficient use of more frequency bands, as well as multiple-input multiple-output (MIMO) or multi-base station (BS) cooperation technologies to improve the data transmission capacity on limited frequency resources.

[0003] As more and more communication devices require greater communication capacity, there is a need for enhanced mobile broadband (eMBB) communication relative to traditional radio access technologies (RAT). Furthermore, massive machine-type communication (mMTC), which enables the provision of various services anytime, anywhere by connecting multiple devices and objects to each other, is a major issue to be considered in next-generation communications.

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

[0005] Technical issues

[0006] There is a need for a method to efficiently transmit data packets in wireless communication systems where jitter may occur.

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

[0008] In applications that restrict uplink reception at the base station (BS) for network energy saving using Discontinuous Cell Reception (DRX) operations, user equipment (UE) needs a method to efficiently notify the BS whether scheduled radio resources are actually in use.

[0009] The purposes that can be achieved by utilizing this disclosure are not limited to those specifically described above, and those skilled in the art will understand more clearly from the following detailed description other purposes not described herein.

[0010] Technical solution

[0011] In one aspect of this disclosure, a method performed by a user equipment (UE) is provided.

[0012] In another aspect of this disclosure, an apparatus is provided. The apparatus includes: at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for a UE.

[0013] In another aspect of this disclosure, a non-transitory computer-readable storage medium is provided. The storage medium stores at least one program code including instructions that, when executed, cause at least one processor to perform operations for a UE.

[0014] The method or operation includes: receiving a cell configuration grant (CG) configuration; and sending Unused Transmission Opportunity-Uplink Control Information (UTO-UCI) based on the CG configuration. The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. The N bits of the N-bit bitmap are mapped one-to-one to N CG Physical Uplink Shared Channel (PUSCH) opportunities, each of the N bits having a first bit value or a second bit value, the first bit value indicating that the UE can transmit the CG PUSCH at the corresponding CGPUSCH opportunity, and the second bit value indicating that the UE does not transmit the CG PUSCH at the corresponding CG PUSCH opportunity.

[0015] In one aspect of this disclosure, a method performed by a base station (BS) is provided.

[0016] In another aspect of this disclosure, a BS is provided. The BS includes: at least one processor; and at least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for the BS.

[0017] The method or operation includes: transmitting a CG configuration for the cell; and receiving a UTO-UCI based on the CG configuration. 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 Physical Uplink Shared Channel (PUSCH) opportunities. Each of the N bits has a first bit value or a second bit value, the first bit value indicating that the UE can transmit the CG PUSCH at the corresponding CG PUSCH opportunity, and the second bit value indicating that the UE does not transmit the CG PUSCH at the corresponding CG PUSCH opportunity.

[0018] In each aspect of this disclosure, the N CG PUSCH timings may exclude CG PUSCH timings that overlap with the inactive period of cell discontinuous reception (DRX).

[0019] In each aspect of this disclosure, the UE may also be provided with a configuration for cell DRX.

[0020] In each aspect of this disclosure, UTO-UCI can be provided via CG PUSCH based on CG configuration.

[0021] The solutions described above are merely some examples of this disclosure, and those skilled in the art can deduce and understand various examples of the technical features incorporated herein from the following detailed description.

[0022] Beneficial effects

[0023] According to some implementations of this disclosure, the waste of radio resources configured for data packets that may jitter can be reduced.

[0024] According to some implementations of this disclosure, radio resources configured based on configuration licenses (CG) can be used for other transmissions.

[0025] According to some implementations of this disclosure, in the case of cell DRX operation where uplink reception at the BS is restricted to network energy saving, it is possible to efficiently report to the BS whether radio resources scheduled for the UE are actually being used.

[0026] The effects of this disclosure are not limited to those specifically described above. Those skilled in the art will understand more clearly from the following detailed description other effects not described herein. Attached Figure Description

[0027] The accompanying drawings are included to provide a further understanding of this disclosure. The drawings illustrate examples of implementations of this disclosure and, together with the detailed description, serve to illustrate the implementations of this disclosure: Figure 1 An example of a communication system 1 to which the implementation of this disclosure is applied is shown; Figure 2 This is a block diagram illustrating an example of a communication device capable of performing the methods according to this disclosure; Figure 3 Another example of a wireless device capable of implementing the embodiments of this disclosure is shown; Figure 4 An example of a frame structure used in a wireless communication system based on the 3rd Generation Partnership Project (3GPP) is shown; Figure 5 The resource grid showing the time slots; Figure 6 Examples of Physical Downlink Shared Channel (PDSCH) Time Domain Resource Assignment (TDRA) caused by Physical Downlink Control Channel (PDCCH) and Physical Uplink Shared Channel (PUSCH) TDRA caused by PDCCH are illustrated. Figure 7 This illustrates the Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) sending / receiving process; Figure 8 Discontinuous reception (DRX) operation is shown for implementations applicable to this disclosure; Figure 9 This shows the configurations for long and short DRX cycles; Figure 10 This is a flowchart illustrating user equipment (UE) operation according to some implementations of this disclosure; Figure 11 This is a flowchart illustrating base station (BS) operation according to some implementations of this disclosure; Figure 12 The signal transmission / reception process between the UE and the BS according to some implementations of this disclosure is illustrated; Figure 13 An example of unused resource information (URI) transmission is illustrated; Figure 14 An example of sending Unused Transmission Opportunity-Uplink Control Information (UTO-UCI) is shown; Figure 15 and Figure 16 Examples of sending UTO-UCI according to some implementations of this disclosure are illustrated; Figure 17 This is a flowchart illustrating UE operation according to some implementations of this disclosure; and Figure 18 This is a flowchart illustrating some implementations of B / S operations according to this disclosure. Detailed Implementation

[0028] In the following, implementations 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 implementations of the present disclosure, and not to show only implementations 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.

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

[0030] The following technologies, devices, and systems can be applied to various wireless multiple access systems. For example, multiple access systems may include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems, etc. 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 Rate GSM Evolution (EDGE) (i.e., GERAN). OFDMA can be specifically implemented using radio technologies such as 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 the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of E-UMTS that uses E-UTRA. 3GPP LTE uses OFDMA on the downlink (DL) and SC-FDMA on the uplink (UL). LTE-Advanced (LTE-A) is an evolution of 3GPP LTE.

[0031] For ease of description, this disclosure will be given under the assumption that it applies to LTE and / or the new RAT (NR). However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is based on a mobile communication system corresponding to a 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.

[0032] For any terms and techniques used in this disclosure that are not described in detail, reference may be made to 3GPP-based standard specifications (e.g., 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300, 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.321, 3GPP TS 38.331, etc.).

[0033] In the examples of this disclosure described later, if the apparatus “assumes” something, this could mean that the channel transmitting entity transmits the channel in accordance with the corresponding “assumption.” This could also mean that the channel receiving entity receives or decodes the channel in a form consistent with that “assumption,” provided that the channel is transmitted in accordance with that “assumption.”

[0034] In this disclosure, a user equipment (UE) can be fixed or mobile. Each of 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 can be referred to as a terminal device, mobile station (MS), mobile terminal (MT), user terminal (UT), subscriber station (SS), radio device, personal digital assistant (PDA), wireless modem, handheld device, etc. In this disclosure, a BS refers to a fixed station that communicates with a UE and / or another BS and exchanges data and control information with the UE and another BS. The term BS can 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 BS for Universal Terrestrial Radio Access (UTRAN) is referred to as an NB, a BS for Evolved UTRAN (E-UTRAN) is referred to as an eNB, and a BS for New Radio Access Technology networks is referred to as a gNB. In the following, for ease of description, regardless of the type or version of the communication technology, NB, eNB, or gNB will be referred to as BS.

[0035] In this disclosure, a node refers to a fixed point capable of sending / receiving radio signals to / from a UE via communication with the UE. Various types of BSs can be used as nodes, regardless of their name. For example, BS, NB, eNB, picocell eNB (PeNB), home eNB (HeNB), repeater, transponder, etc., can be nodes. Alternatively, a node may not be a BS. For example, a Radio Remote Headend (RRH) or Radio Remote Unit (RRU) can be a node. Typically, RRHs and RRUs have a lower power level than the BS. Since RRHs or RRUs (hereinafter, RRH / RRU) are typically connected to the BS via dedicated lines such as fiber optic cables, cooperative communication between the RRH / RRU and the BS can be performed smoothly compared to cooperative communication between the BS connected via a radio link. Each node is equipped with at least one antenna. An antenna can refer to a physical antenna port or a virtual antenna or antenna array. A node can also be referred to as a point.

[0036] In this disclosure, a cell refers to a specific geographical area where one or more nodes provide communication services. Therefore, in this disclosure, communication with a specific cell can mean communication with a BS or node providing communication services to that specific cell. The DL / UL signal of a specific cell refers to the DL / UL signal from / to the BS or node providing communication services to that specific cell. A cell providing UL / DL communication services to a UE is specifically referred to as a serving cell. Furthermore, the channel state / quality of a specific cell refers to the channel state / quality of the channel or communication link generated between the BS or node providing communication services to the specific cell and the UE. In 3GPP-based communication systems, the UE can use the CRS transmitted on the Cell Specific Reference Signal (CRS) resource and / or the CSI-RS transmitted on the Channel State Information Reference Signal (CSI-RS) resource (assigned to the specific node by the antenna port of the specific node) to measure the DL channel state from the specific node.

[0037] 3GPP-based communication systems use the concept of cells to manage radio resources and distinguish between cells associated with radio resources and cells representing geographical areas.

[0038] A "cell" of a geographic area can be understood as the coverage area within which a node can use a carrier to provide service, and a "cell" of radio resources is associated with the bandwidth (BW) of the frequency range configured by the carrier. Since DL coverage (the range within which a node can transmit a valid signal) and UL coverage (the range within which a node can receive a valid signal from a UE) depend on the carrier carrying the signal, a node's coverage area can also be associated with the coverage area of ​​the "cell" of the radio resources used by that node. Therefore, the term "cell" can be used to sometimes indicate the service coverage area of ​​a node, at other times to indicate a radio resource, or at other times to indicate the range within which a signal using a radio resource can reach with available effective strength.

[0039] In 3GPP communication standards, the concept of a cell is used to manage radio resources. A “cell” associated with radio resources is defined by a combination of DL resources and UL resources (i.e., a combination of DL component carriers (CCs) and UL CCs). A cell can be configured solely by DL resources or by a combination of DL and UL resources. If carrier aggregation is supported, the link between the carrier frequencies of the DL resources (or DL ​​CCs) and the UL resources (or UL CCs) can be indicated by system information. For example, a combination of DL and UL resources can be indicated by a System Information Block Type 2 (SIB2) link. In this case, the carrier frequencies can be equal to or different from the center frequencies of the individual cells or CCs. When carrier aggregation (CA) is configured, the UE has only one Radio Resource Control (RRC) connection with the network. During RRC connection establishment / re-establishment / handover, a serving cell provides Non-Access Plane (NAS) mobility information. During RRC connection re-establishment / handover, a serving cell provides security input. This cell is called the primary cell (Pcell). A Pcell refers to the cell operating on the primary frequency on which the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on the UE's capabilities, a secondary cell (Scell) can be configured to form a set of serving cells together with a Pcell. An Scell ​​can be configured after RRC connection establishment and is used to provide additional radio resources beyond those of a 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 (DLSCC), and the carrier corresponding to the Scell ​​on the UL is called the Uplink Secondary CC (UL SCC).

[0040] In dual connectivity (DC) operation, the term Special Cell (SpCell) refers to the Pcell of the Primary Cell Group (MCG) or the primary / secondary cell (Pcell) of the Secondary Cell Group (SCG). The SpCell supports PUCCH transmission and contention-based random access and is always enabled. The MCG is a set of serving cells associated with the primary node (e.g., BS) and includes the SpCell (Pcell) and optionally one or more Scells. For a UE configured with DC, the SCG is a subset of serving cells associated with the secondary node and includes the PSCell and zero or more Scells. The PSCell is the primary Scell ​​of the SCG. For a UE in the RRC_CONNECTED state without a CA or DC configured, only one serving cell exists, consisting only of the Pcell. For a UE in the RRC_CONNECTED state with a CA or DC configured, the term serving cell refers to the set of cells including the SpCell and all Scells. In DC, two Media Access Control (MAC) entities are configured for the UE: one MAC entity for the MCG and one MAC entity for the SCG.

[0041] For a UE configured with a CA but not a DC, a Pcell PUCCH group (also called a primary PUCCH group) including Pcells and 0 or more Scells can be configured, and an Scell ​​PUCCH group (also called a secondary PUCCH group) including only Scells can be configured. For an Scell, an Scell ​​(hereinafter, PUCCH Scell) can be configured to transmit PUCCHs associated with the corresponding cell. The Scell ​​indicating the PUCCH Scell ​​belongs to the Scell ​​PUCCH group (i.e., the secondary PUCCH group) and performs PUCCH transmission of the relevant uplink control information (UCI) on the PUCCH Scell. If no PUCCH Scell ​​is indicated for an Scell, or if the cell indicating the PUCCH transmission for the Scell ​​is a Pcell, then the Scell ​​belongs to the Pcell PUCCH group (i.e., the primary PUCCH group) and performs PUCCH transmission of the relevant UCI on the Pcell. In the following, if the UE is configured with an SCG and some implementations of this disclosure related to PUCCH are applied to the SCG, the primary cell can refer to the PSCell of the SCG. If the UE is configured with a PUCCH Scell ​​and some implementations of this disclosure related to PUCCH are applied to the secondary PUCCH group, then the primary cell may refer to the PUCCH Scell ​​of the secondary PUCCH group.

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

[0043] 3GPP-based communication standards define DL physical channels corresponding to resource elements carrying information originating from higher layers, and 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, and reference signals (RS) and synchronization signals (SS) are defined as DL physical signals. RS (also called pilot) represents a signal with a predefined special waveform known to both the BS and the UE. For example, demodulation reference signal (DMRS) and channel state information RS (CSI-RS) are defined as DL RS. 3GPP-based communication standards also define UL physical channels corresponding to resource elements carrying information originating from higher layers, and UL physical signals corresponding to resource elements used by the physical layer but not carrying information originating from higher layers. For example, the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH) are defined as UL physical channels, and the DMRS for UL control / data signals and the SRS for UL channel measurements are defined, etc.

[0044] In this disclosure, PDCCH refers to the set of time-frequency resources (e.g., resource elements (REs)) carrying downlink control information (DCI), and PDSCH refers to the set of time-frequency resources carrying DL data. PUCCH, PUSCH, and PRACH refer to the set of time-frequency resources carrying UCI, the set of time-frequency resources carrying UL data, and the set of time-frequency resources carrying random access signals, respectively. In the following description, "UE transmits / receives PUCCH / PUSCH / PRACH" is used to mean the same as the UE transmitting / receiving UCI / UL data / random access signals on or through PUCCH / PUSCH / PRACH. Similarly, "BS transmits / receives PBCH / PDCCH / PDSCH" is used to mean the BS transmitting broadcast information / DCI / DL data on or through PBCH / PDCCH / PDSCH.

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

[0046] Because communication devices receive synchronization signal blocks (SSBs), DMRS, CSI, RSPBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on a cell, the communication device may not select and receive radio signals that only include specific physical channels or specific physical signals via a radio frequency (RF) receiver, or it may not select and receive radio signals without specific physical channels or specific physical signals via an RF receiver. In practice, the communication device receives radio signals on the cell via an RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and then uses one or more processors to decode the physical signals and / or physical channels in the baseband signals. Therefore, in some implementations of this disclosure, not receiving physical signals and / or physical channels may mean that the communication device does not attempt to recover physical signals and / or physical channels from the radio signals, for example, it does not attempt to decode physical signals and / or physical channels, rather than that the communication device does not actually receive radio signals that include the corresponding physical signals and / or physical channels.

[0047] With an increasing number of communication devices requiring greater communication capacity, there is a need for eMBB communication relative to traditional radio access technologies (RATs). Furthermore, massive MTC (Medium-Terminal Communication) to provide various services anytime, anywhere by connecting multiple devices and objects to each other is a major issue to be considered in next-generation communications. In addition, communication system designs considering reliability and latency-sensitive services / UEs are also being discussed. The introduction of next-generation RATs is being discussed, taking into account eMBB communication, massive MTC, ultra-reliable low-latency communication (URLLC), etc. Currently, research on next-generation mobile communication systems after EPC is underway within 3GPP. In this disclosure, for convenience, the corresponding technology is referred to as New RAT (NR) or 5th Generation (5G) RAT, and systems using or supporting NR are referred to as NR systems.

[0048] Figure 1 An example of a communication system 1 to which the implementation of this disclosure is applied is shown. (Refer to...) Figure 1The communication system 1 applied to this disclosure includes wireless devices, a network, and a network. Here, a wireless device refers to a device that performs communication using RAT (e.g., 5G NR or LTE (e.g., E-UTRA)) and may be referred to as a communication / radio / 5G device. Wireless devices may include (but are not limited to) robots 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 artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Here, vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches 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, the BS and network may also be implemented as wireless devices, and a particular wireless device may operate as a BS / network node relative to another wireless device.

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

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

[0051] Figure 2 This is a block diagram illustrating an example of a communication device capable of performing the methods according to this disclosure. (Refer to...) Figure 2 The first wireless device 100 and the second wireless device 200 can transmit and / or receive radio signals via various RATs (e.g., LTE and NR). Here, {first wireless device 100 and second wireless device 200} can correspond to Figure 1 {Wireless Device 100x and BS 200} and / or {Wireless Device 100x and Wireless Device 100x}.

[0052] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the functions, processes, and / or methods described / presented below. For example, the processors 102 may process information in the memories 104 to generate first information / signals, and then transmit radio signals including the first information / signals via the transceivers 106. The processors 102 may receive radio signals including second information / signals via the transceivers 106, and then store the information obtained by processing the second information / signals in the memories 104. The memories 104 may be connected to the processors 102 and may store various information related to the operation of the processors 102. For example, the memories 104 may execute some or all of the processes controlled by the processors 102 or store software code including commands for executing the processes and / or methods described / presented below. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to 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. Transceiver 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0053] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the functions, processes, and / or methods described / presented below. For example, the processors 202 may process information in the memories 204 to generate a third message / signal, and then transmit a radio signal including the third message / signal via the transceivers 206. The processors 202 may receive a radio signal including a fourth message / signal via the transceivers 206, and then store the information obtained by processing the fourth message / signal in the memories 204. The memories 204 may be connected to the processors 202 and may store various information related to the operation of the processors 202. For example, the memories 204 may execute some or all of the processes controlled by the processors 202 or store software code including commands for executing the processes and / or methods described / presented below. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to 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. Transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0054] The wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include narrowband Internet of Things (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 implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2. However, NB-IoT technology is not limited to the above names. Alternatively or additionally, the wireless communication technologies implemented in the wireless devices XXX and YYY of this disclosure may perform communication 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 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., but LTE-M technology is not limited to the above names. Additionally or alternatively, considering low-power communication, the wireless communication technology implemented in the wireless devices XXX and YYY of this 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 personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and ZigBee technology may be referred to by various names.

[0055] 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 are 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 the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and 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, processes, proposals, and / or methods disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) and acquire PDUs, SDUs, messages, control information, data, or information from one or more transceivers 106 and 206 according to the functions, processes, proposals, and / or methods disclosed in this disclosure.

[0056] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The 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. Firmware or software configured to perform the functions, processes, proposals, and / or methods disclosed in this disclosure may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The 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 sets of commands.

[0057] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, commands, and / or instructions. One or more memories 104 and 204 may be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations 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.

[0058] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the methods and / or operation flowcharts of this 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 operation flowcharts disclosed in this 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 perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform control to enable one or more transceivers 106 and 206 to 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. One or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure via one or more antennas 108 and 208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc., processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0059] Figure 3 Another example of a wireless device capable of implementing the embodiments of this disclosure is shown. (Refer to...) Figure 3 Wireless devices 100 and 200 can correspond to Figure 2 The wireless devices 100 and 200 are configured with various elements, components, units / parts, 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, transceiver 114 may include Figure 2 The device comprises one or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory 130, and add-on components 140, and controls the overall operation of the wireless device. For example, control unit 120 may control the electrical / mechanical operation of the wireless device based on programs / code / commands / information stored in memory unit 130. Control unit 120 may transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via communication unit 110 in memory unit 130 via a wireless / wired interface.

[0060] The additional component 140 can be configured differently depending on the type of wireless device. For example, the additional component 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 can be configured according to (but is not limited to) a robot ( Figure 1 100a), vehicles ( Figure 1 100b-1 and 100b-2), XR device ( Figure 1 100c), handheld device ( Figure 1 100d), home appliances ( Figure 1 100e), IoT devices ( Figure 1 100f), digital broadcast UE, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environment devices, AI servers / devices ( Figure 1 400), BS ( Figure 1 This can be achieved through 200 network nodes, etc. Wireless devices can be used in mobile or fixed locations depending on usage / service.

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

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

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

[0064] In this disclosure, a processing apparatus or device may include at least one processor and at least one computer memory operatively connected to said at least one processor. The at least one computer memory may store instructions or programs, and when executed, these instructions or programs 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 this disclosure.

[0065] In this 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 implementation of this disclosure or to cause at least one processor to perform operations according to some implementation of this disclosure. The computer program may be provided in the form of a computer program product. A computer program product may include at least one computer-readable (non-transitory) storage medium.

[0066] The communication apparatus of this disclosure includes: at least one processor; and 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 according to examples of this disclosure described later.

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

[0068] Figure 4 The frame structure described is merely exemplary, and the number of subframes, time slots, and symbols within a frame can vary. In an NR system, different sets of OFDM parameters (e.g., subcarrier spacing (SCS)) can be configured for multiple cells aggregated for a UE. Therefore, the (absolute time) duration of time resources comprising the same number of symbols (e.g., subframes, time slots, or transmission time intervals (TTI)) can be configured differently for the aggregated cells. Here, symbols may include OFDM symbols (or cyclic prefix-OFDM (CP-OFDM) symbols) and SC-FDMA symbols (or discrete Fourier transform-extended-OFDM (DFT-s-OFDM) symbols). In this disclosure, symbols, OFDM-based symbols, OFDM symbols, CP-OFDM symbols, and DFT-s-OFDM symbols are used interchangeably.

[0069] Reference Figure 4 In NR systems, UL and DL transmissions are organized into frames. Each frame has a T f =(△f max N f / 100) T c =10 ms duration and is divided into two half-frames, each 5 ms. 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 for 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 cHaving a constant κ=T s / T c =64. Each half-frame consists of 5 subframes, and the duration T of a single subframe is... sf The duration is 1 ms. Subframes are further divided into time slots, and the number of time slots within a subframe depends on the subcarrier spacing. Each time slot comprises either 14 or 12 OFDM symbols based on the cyclic prefix. In normal CP, each time slot comprises 14 OFDM symbols, while in extended CP, each time slot comprises 12 OFDM symbols. The parameter set depends on the exponentially scalable subcarrier spacing Δf = 2. u 15 kHz. The following 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 ).

[0070] [Table 1]

[0071] The following table shows the subcarrier spacing Δf = 2 u 15 kHz, the number of OFDM symbols per time slot, the number of time slots per frame, and the number of time slots per subframe.

[0072] [Table 2]

[0073] For the subcarrier spacing configuration u, the time slots can be indexed in ascending order within the subframe as follows: n u s ∈{0, ..., n subframe ,u slot -1}, and indexed in ascending order within the frame as follows: n u s,f ∈{0, ..., n frame,u slot -1}.

[0074] Figure 5 The resource grid for the time slots is shown. A time slot comprises multiple (e.g., 14 or 12) symbols in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, a Common Resource Block (CRB) is indicated by higher-layer signaling (e.g., RRC signaling). N start,u grid The definition has begun.N size,u grid,x N RB sc Subcarriers and N subframe,u symb A resource grid of OFDM symbols, wherein N size,u grid,x It represents the number of resource blocks (RBs) in the resource grid, and for downlinks, the subscript x is DL, and for uplinks, it is UL. N RB sc This refers to the number of subcarriers per RB. In 3GPP-based wireless communication systems, N RB sc Typically 12. For a given antenna port p Subcarrier spacing configuration u A resource grid exists between the transmission link (DL or UL). The subcarrier spacing configuration u is given to the UE via higher-layer parameters (e.g., RRC parameters). N size,u grid Used for antenna port p and subcarrier spacing configuration. u Each element in the resource grid is called a resource element (RE), and a complex symbol can be mapped to each RE. Each RE in the resource grid is indexed in the frequency domain. k and an index representing the sign position relative to a reference point in the time domain. l Uniquely identified. In NR systems, an RB is defined by 12 consecutive subcarriers in the frequency domain. In NR systems, RBs are classified as CRBs and Physical Resource Blocks (PRBs). For subcarrier spacing configuration... u CRBs are numbered from 0 upwards in the frequency domain. Subcarrier spacing configuration. u The center of subcarrier 0 of CRB 0 is equal to "point A", which serves as the common reference point for the RB grid. Subcarrier spacing configuration u The PRB is defined within the Bandwidth Part (BWP) and ranges from 0 to N size,u BWP,i -1 is the number, where i is the number of BWPs. PRB n in BWPi PRB With CRB n u CRB The relationship between n u PRB =n u CRB + Nsize,u BWP,i Given, among which N size BWP,i The BWP is the CRB that starts relative to CRB 0. A BWP comprises multiple consecutive RBs in the frequency domain. For example, a BWP can be a BWP i on a given carrier with a given set of parameters u. i A subset of adjacent CRBs is defined. A carrier may include up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed via enabled BWPs, and a predetermined number of BWPs (e.g., one BWP) may be active on the component carrier only among the BWPs configured for the UE.

[0075] For each serving cell in the set of DL BWPs or UL BWPs, the network can configure at least an initial DL BWP and one (if the serving cell has an uplink) or two (if supplementary uplinks are used) initial UL BWPs. The network can configure additional UL and DL BWPs. For each DL BWP or UL BWP, the following parameters can be provided to the UE for the serving cell: i) SCS; ii) CP; iii) parameters provided by the network in the UL BWP set. N start BWP= The indicated offset is based on the assumption of 275. RB set and length L RB RRC parameters as Resource Indicator Value (RIV) locationAndBandwidth CRB provided N start BWP = O carrier + RB start and the number of adjacent RBs N size BWP = L RB and by RRC parameters offsetToCarrier For the value provided by SCS O carrier ; an index in the set of DL BWP or UL BWP; a set of BWP common parameters; and a set of BWP specific parameters.

[0076] Virtual Resource Blocks (VRBs) can be defined within a BWP and range from 0 to... N size,u BWP,i-1 index, where i represents the BWP number. VRBs can be mapped to PRBs based on interleaved or non-interleaved mappings. In some implementations, for non-interleaved VRB-to-PRB mappings, VRB n can be mapped to PRB n.

[0077] A UE with CA configured can be configured to use one or more cells. When a UE is configured to have multiple serving cells, it can be configured to have one or more cell groups. A UE can be configured to have multiple cell groups associated with different BSs. Alternatively, a UE can be configured to have 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 can be an Scell ​​within the cell group that is configured as a PUCCH cell. Each serving cell of the UE belongs to one of the UE's cell groups and does not belong to multiple cell groups.

[0078] The NR band is defined as two types of frequency ranges, namely FR1 and FR2. FR2 is also known as millimeter wave (mmW). The following shows the frequency range that NR can operate in.

[0079] [Table 3]

[0080] The physical channels available in 3GPP-based wireless communication systems will be described in detail below.

[0081] The PDCCH carries the DCI. For example, the PDCCH (i.e., the DCI) carries information about the transmission format and resource allocation of the downlink shared channel (DL-SCH), information about the resource allocation of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about the DL-SCH, resource allocation information about control messages (e.g., Random Access Response (RAR) sent on the PDSCH) of layers higher than the physical layer in the UE / BS protocol stack (hereinafter, higher layers), transmission power control commands, and information about enabling / disabling configuration scheduling (CS), etc. The DCI that includes resource allocation information about the DL-SCH is called the PDSCH scheduling DCI, and the DCI that includes resource allocation information about the UL-SCH is called the PUSCH scheduling DCI. The DCI includes Cyclic Redundancy Check (CRC). The CRC is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier (RNTI)) according to the owner and purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRS is masked with the UE identifier (e.g., Cell-RNTI (C-RNTI)). If the PDCCH is used for paging messages, the CRC is masked with the Paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., System Information Block (SIB)), the CRC is masked with the System Information RNTI (SI-RNTI). If the PDCCH is used for random access responses, the CRC is masked with the Random Access-RNTI (RA-RNTI).

[0082] When a PDCCH on one serving cell schedules a 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 one serving cell to schedule resources on another serving cell. When a PDSCH on one serving cell schedules a PDSCH or PUSCH on another serving cell, it is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the 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 a PDCCH on another (scheduling) cell or by the serving cell itself. If the serving cell is scheduled by another (scheduling) cell, the BS can inform the UE which cell signals the DL assignment and UL authorization of the serving cell. In this disclosure, the cell carrying the PDCCH is called 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 called the scheduled cell.

[0083] PDSCH is the physical layer UL channel for UL data transmission. PDSCH carries DL data (e.g., DL-SCH transport blocks) and is modulated using techniques such as Quadrature Phase Shift Keying (QPSK), 16-Quadrature Amplitude Modulation (QAM), 64 QAM, 256 QAM, etc. Codewords are generated by encoding the transport block (TB). PDSCH can carry up to two codewords. Scrambling and modulation mapping can be performed for each codeword, and modulation symbols generated from each codeword can be mapped to one or more layers. Each layer, along with DMRS, is mapped to radio resources and generated as OFDM symbol signals. The OFDM symbol signals are then transmitted through the corresponding antenna ports.

[0084] PUCCH is a physical layer UL channel used for uplink control information (UCI) transmission. PUCCH carries UCI. The types of UCI transmitted on PUCCH include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information, Scheduling Request (SR) information, and Channel State Information (CSI). 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 this disclosure, the HARQ-ACK information bits correspond to the HARQ-ACK codebook. Specifically, the bit sequence of the HARQ-ACK information bits arranged according to a predetermined rule is called the HARQ-ACK codebook.

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

[0086] - Hybrid Automatic Repeat Request (HARQ) - Acknowledgment (ACK): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the communication device has 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 affirmative ACK (simply ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. Here, the term HARQ-ACK can be used interchangeably with HARQ ACK / NACK, ACK / NACK, or A / N.

[0087] - 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). Based on the UCI types included in the CSI, CSI can 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.

[0088] - Link Recovery Request (LRR)

[0089] In this disclosure, for convenience, the PUCCH resources for which the BS configures / instructs the UE to transmit HARQ-ACK, SR, and CSI are referred to as HARQ-ACK PUCCH resources, SR PUCCH resources, and CSI PUCCH resources, respectively.

[0090] The PUCCH format can be defined as follows, depending on the UCI payload size and / or transmission length (e.g., the number of symbols included in the PUCCH resource). See Table 4 for further information on the PUCCH format.

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

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

[0093] - The number of OFDM symbols that make up a single PUCCH: 1 to X symbols (e.g., X=2)

[0094] - Transmission Structure: PUCCH format 0 includes only UCI signals and no DMRS. The UE transmits the UCI status by selecting and transmitting one of several sequences. For example, the UE transmits a specific UCI to the BS by transmitting one of several sequences via PUCCH (PUCCH format 0). The UE transmits PUCCH (PUCCH format 0) only in the PUCCH resources configured for the corresponding SR when transmitting an affirmative SR.

[0095] - The configuration of PUCCH format 0 includes the following parameters for the corresponding 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.

[0096] (1) PUCCH Format 1 (PF1 or F1)

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

[0098] - The number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4 and Z=14).

[0099] - Transmission Structure: DMRS and UCI are configured / mapped to different OFDM symbols according to TDM. In other words, DMRS is transmitted in symbols where no modulation symbols are transmitted, and UCI is represented as a product between a specific sequence (e.g., orthogonal overlay code (OCC)) and a modulation (e.g., QPSK) symbol. Code division multiplexing (CDM) is supported among multiple PUCCH resources (compliant with PUCCH format 1) (within the same RB) by applying cyclic shift (CS) / OCC to both UCI and DMRS. PUCCH format 1 carries up to 2 bits of UCI and extends the modulation symbols in the time domain via OCC (configured differently depending on whether frequency hopping is performed).

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

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

[0102] - Supported UCI payload size: exceeding K bits (e.g., K=2)

[0103] - The number of OFDM symbols that make up a single PUCCH: 1 to X symbols (e.g., X=2)

[0104] - Transmission Structure: Frequency Division Multiplexing (FDM) is used within the same symbol to configure / map DMRS and UCI. The UE transmits UCI by applying IFFT to the encoded UCI bits without DFT. PUCCH Format 2 carries UCI bits larger than K bits, and the modulated symbols undergo FDM with DMRS for transmission. For example, the 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 2-symbol PUCCH Format 2.

[0105] - The configuration of PUCCH Format 2 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols used for PUCCH transmission, and / or the first symbol used for PUCCH transmission.

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

[0107] - Supported UCI payload size: exceeding K bits (e.g., K=2)

[0108] - The number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4 and Z=14).

[0109] - Transmission Structure: DMRS and UCI are configured / mapped to different OFDM symbols according to TDM. The UE transmits UCI by applying DFT to the encoded UCI bits. PUCCH Format 3 does not support UE multiplexing for the same time-frequency resource (e.g., the same PRB).

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

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

[0112] - Supported UCI payload size: exceeding K bits (e.g., K=2)

[0113] - The number of OFDM symbols that make up a single PUCCH: Y to Z symbols (e.g., Y=4 and Z=14).

[0114] - Transmission Structure: DMRS and UCI are configured / mapped to different OFDM symbols using TDM. By applying OCC to the front end of the DFT and CS (or interleaved FDM (IFDM) mapping) to the DMRS, PUCCH Format 4 can multiplex up to 4 UEs in the same PRB. In other words, the modulation symbols of UCI undergo TDM with the DMRS for transmission.

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

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

[0117] [Table 4]

[0118] The 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.

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

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

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

[0123] 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 of PUCCH format 0 to 1, and other PUCCH resource sets can include resources of PUCCH format 2 to 4 (see Table 4).

[0124] The configuration of each PUCCH resource includes the PUCCH resource index, the starting PRB index, and the configuration of one of PUCCH format 0 to PUCCH format 4. The BS configures the code rate for multiplexing HARQ-ACK, SR, and CSI reports in the PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4 for the UE through the high-layer parameter maxCodeRate. The high-layer parameter maxCodeRate is used to determine how to feedback UCI on the PUCCH resources of PUCCH format 2, 3, or 4.

[0125] If the UCI type is SR and CSI, the PUCCH resources to be used for UCI transmission in the PUCCH resource set can be configured for the UE through high-layer signaling (e.g., RRC signaling). If the UCI type is HARQ-ACK for semi-persistent scheduling (SPS) PDSCH, the PUCCH resources to be used for UCI transmission in the PUCCH resource set can be configured for the UE through high-layer signaling (e.g., RRC signaling). On the other hand, if the UCI type is HARQ-ACK for DCI-scheduled PDSCH, the PUCCH resources to be used for UCI transmission in the PUCCH resource set can be scheduled by DCI.

[0126] In the case of DCI-based PUCCH resource scheduling, the BS can send a DCI to the UE on the PDCCH and indicate the PUCCH resources to be used for UCI transmission in a specific PUCCH resource set via an ACK / NACK Resource Indicator (ARI) in the DCI. The ARI can be used to indicate 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 BS can configure a PUCCH resource set for the UE via (UE-specific) higher-layer (e.g., RRC) signaling that includes a larger number of PUCCH resources than the ARI can represent. The ARI can indicate a subset of PUCCH resources in the PUCCH resource set, and which PUCCH resource in the indicated subset to use can be determined based on implicit rules according to transmission resource information about the PDCCH (e.g., the starting CCE index of the PDCCH).

[0127] For UL-SCH data transmission, the UE needs UL resources available to it; for DL-SCH data reception, the UE needs DL resources available to it. The BS assigns UL 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 licensing, and DL resource allocation is also referred to as DL assignment. UL licensing can be dynamically received by the UE on the PDCCH or in the RAR, or UL licensing can be semi-persistently configured to the UE from the BS via RRC signaling. DL assignment can be dynamically received by the UE on the PDCCH, or semi-persistently configured to the UE from the BS via RRC signaling.

[0128] On the UL, the BS can dynamically allocate UL resources to the UE via the PDCCH addressed to the temporary identifier (Cell Radio Network Temporary Identifier, C-RNTI). The UE monitors the PDCCH to detect possible UL licenses for UL transmission. The BS can allocate UL resources to the UE using configuration licenses. Two types of configuration licenses can be used: Type 1 and Type 2. In the case of Type 1, the BS directly provides the configured UL licenses (including periodicity) via RRC signaling. In the case of Type 2, the BS configures the periodicity of RRC-configured UL licenses via RRC signaling and can signal and enable or disable the configured UL licenses via the PDCCH addressed to the configuration scheduling RNTI (CS-RNTI). For example, in the case of Type 2, the PDCCH addressed to the CS-RNTI indicates until deactivation, and the corresponding UL license can be implicitly reused according to the periodicity configured via RRC signaling.

[0129] On the DL (Deep Node) architecture, the BS (Base Station) can dynamically allocate DL resources to the UE via the PDCCH (Programmable Node Distributor) addressed to the C-RNTI (Central Receiver Instruction). The UE monitors the PDCCH to detect potential DL assignments. The BS can allocate DL resources to the UE using semi-persistent scheduling (SPS). The BS can configure the periodicity of the configured DL assignments via RRC (Regulatory Relationship Control) signaling and signal to enable or disable the configured DL assignments via the PDCCH addressed to the CS-RNTI. For example, indicating until deactivation via the PDCCH addressed to the CS-RNTI implicitly reuses the corresponding DL assignment based on the periodicity configured via RRC signaling.

[0130] Resource allocation via PDCCH and resource allocation via RRC will be described in more detail below.

[0131] Resource allocation via PDCCH: Dynamic licensing / assignment

[0132] The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH. The DCI on the PDCCH used for scheduling DL transmissions may include DL resource assignments, which at least include an index I of the modulation and coding format (e.g., modulation and coding scheme (MCS)) associated with the DL-SCH. MCS The DCI on the PDCCH used for scheduling UL transmissions may include UL scheduling authorization, which includes at least the modulation and coding format associated with the UL-SCH, resource allocation, and HARQ information. HARQ information regarding the DL-SCH or UL-SCH may include a New Message Indicator (NDI), Transport Block Size (TBS), Redundancy Version (RV), and HARQ Process ID (i.e., HARQ Process Number). The size and purpose of the 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 can be used to schedule PUSCH, while DCI format 1_0, DCI format 1_1, or DCI format 1_2 can be used to schedule 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 implementations of this disclosure can be applied to UL data transmission based on DCL format 0_2. Some implementations of this disclosure can be applied to DL data reception based on DCI format 1_2.

[0133] Figure 6 Examples of PDSCH TDRA caused by PDCCH and PUSCH TDRA caused by PDCCH are shown.

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

[0135] In the PDSCH time-domain resource configuration, each index row defines the DL assignment and PDSCH slot offset. K 0 , start and length indicator values SLIV (or the start position of the PDSCH in the direct time slot (e.g., the start symbol index)) S ) and allocation length (e.g., number of symbols) L The PUSCH mapping type is also defined. In the PUSCH time-domain resource configuration, each index row defines the UL permission and the PUSCH slot offset. K 2 The starting position of the PUSCH in the time slot (e.g., the start symbol index) S ) and allocation length (e.g., number of symbols) L ) and PUSCH mapping type. PDSCH K 0 and PUSCH K 2 Indicates the difference between a time slot with a PDCCH and a time slot with a corresponding PDSCH or PUSCH. SLIV A start symbol indicating the beginning of a time slot relative to the time slot containing a PDSCH or PUSCH. S And from the symbol S The number of consecutive symbols in the count LThe joint indicator. 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 start 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, according to RRC signaling, the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) in the time slot. 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, the DMRS is located at the first symbol allocated to the 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 this 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.

[0136] The scheduling DCI includes an FDRA field that provides assignment information about the RBs used 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.

[0137] Resource allocation via RRC

[0138] As described above, there are two types of transmissions without dynamic licensing: Configuration License Type 1 and Configuration License Type 2. In Configuration License Type 1, the UL license is provided by the RRC and stored as a configuration UL license. In Configuration License Type 2, the UL license is provided by the PDCCH and stored or cleared as a configuration UL license based on L1 signaling indicating whether the configuration UL license is enabled or disabled. Types 1 and 2 can be configured by the RRC per serving cell and per BWP. Multiple configurations can be active simultaneously on different serving cells.

[0139] When configuring license type 1, the following parameters can be provided to the UE via RRC signaling: - cs-RNTI This corresponds to CS-RNTI used for retransmission; - periodicityThis corresponds to the periodicity of configuration license type 1; - timeReferenceSFN This indicates the system frame number (SFN) used to determine the offset of resources in the time domain. - timeDomainOffset , corresponding to and by timeReferenceSFN The offset associated with the reference SFN; - timeDomainAllocation value m Provides row indexes pointing to the allocation table. m+1 Indicates the start symbol S ,length L Combinations with PUSCH mapping types; - frequencyDomainAllocation Provides frequency domain resource allocation; and - mcsAndTBS It provides indications of modulation order, target code rate, and transport block size. I MCS .

[0140] When configuring configuration license type 1 for the serving cell via RRC, the UE stores the UL license provided by RRC as the configuration UL license for the indicated serving cell, and initializes or reinitializes the configuration UL license according to... timeDomainOffset and S (from SLIV The derivation begins with the symbol and ends with periodicity Duplicate. After configuring UL licensing for license type 1, the UE may consider the UL licensing to be duplicated with each symbol that satisfies the following formula: [(SFN numberOfSlotsPerFrame numberOfSymbolsPerSlot +(number of time slots in the frame) numberOfSymbolsPerSlot [() + number of symbols in the time slot] = () timeReferenceSFN numberOfSlotsPerFrame numberOfSymbolsPerSlot + timeDomainOffset numberOfSymbolsPerSlot + S + N periodicity modulo (1024) numberOfSlotsPerFrame numberOfSymbolsPerSlot For N>=0, where numberOfSlotsPerFrame and numberOfSymbolsPerSlotThese indicate the number of consecutive time slots per frame and the number of consecutive OFDM symbols per time slot, respectively (refer to Tables 1 and 2). Here, "SFN" refers to the SFN of a frame that may have UL license, "number of time slots" refers to the number of time slots within a frame that may have UL license, and "number of symbols" refers to the number of symbols within a time slot that may have UL license.

[0141] For configuration license type 2, the BS can provide the following parameters to the UE via RRC signaling: - cs-RNTI Corresponding to CS-RNTI used for enabling, disabling, and retransmitting; and - periodicity Provides periodicity for configuration license type 2.

[0142] The actual UL license is provided to the UE via PDCCH (addressed to CS-RNTI). After configuring the UL license for license type 2, the UE can assume that the UL license is associated with duplicates of the symbols satisfying the following formula: [(SFN numberOfSlotsPerFrame numberOfSymbolsPerSlot )+(number of time slots in the frame) numberOfSymbolsPerSlot ) + Number of symbols in the time slot] = [(SFN) 开始时间 numberOfSlotsPerFrame numberOfSymbolsPerSlot +slot 开始时间 numberOfSymbolsPerSlot+ symbol 开始时间 )+ N periodicity modulo (1024) numberOfSlotsPerFrame numberOfSymbolsPerSlot For all N>=0, where SFN 开始时间 slot 开始时间 and symbol 开始时间 These represent the SFN, slot, and symbol of the first transmission opportunity of PUSCH after the configuration license is (re)initialized. numberOfSlotsPerFrame and numberOfSymbolsPerSlot These indicate the number of consecutive time slots per frame and the number of consecutive OFDM symbols per time slot, respectively (refer to Tables 1 and 2). Here, "SFN" refers to the SFN of a frame that may have UL license, "number of time slots" refers to the number of time slots within a frame that may have UL license, and "number of symbols" refers to the number of symbols within a time slot that may have UL license.

[0143] In some scenarios, the BS can further provide the UE with parameters for deriving the HARQ process ID for configuring UL permission. harq-ProcID-Offset and / or parameters harq-ProcID-Offset2 . harq-ProcID-Offset It is the offset of the HARQ process for configuring permissions for shared spectrum channel access operations. harq-ProcID-Offset2 This is the offset of the HARQ process configured with permissions. In this disclosure, cg-RetransmissionTimer This is the duration following a transmission (retransmission) that is configured to allow, where the UE should not autonomously perform retransmissions based on the HARQ process of the transmission (retransmission). When configuring retransmissions with UL-permitted settings, the BS can... cg-RetransmissionTimer Provided to the UE. For those that are not configured... harq-ProcID- Offset Not configured cg-RetransmissionTimer The configuration license can be derived from the following formula: HARQ process ID associated with the first symbol of UL transmission: HARQ process ID = [floor(CURRENT_symbol / periodicity modulo nrofHARQ-Processes For those with harq-ProcID-Offset2 The UL license configuration can be derived from the following formula: HARQ process ID associated with the first symbol of UL transmission: HARQ process ID = [floor(CURRENT_symbol / periodicity modulo nrofHARQ-Processes + harq-ProcID-Offset2 , where CURRENT_symbol=(SFN numberOfSlotsPerFrame numberOfSymbolsPerSlot +time slot number in the frame numberOfSymbolsPerSlot + the symbol in the time slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot These represent the number of consecutive time slots per frame and the number of consecutive OFDM symbols per time slot, respectively. For frames with... cg-RetransmissionTimer To configure UL permission, the UE can select a HARQ process ID from the HARQ process IDs available for configuring permission.

[0144] On the DL, semi-persistent scheduling (SPS) can be provided to the UE from the BS per serving cell and per BWP via RRC signaling. For DL ​​SPS, DL assignments are provided to the UE via PDCCH and are stored or cleared based on L1 signaling indicating whether SPS is enabled or disabled. If SPS is configured, the UE can receive the following parameters from the BS via RRC signaling used to configure semi-persistent transmission (e.g., SPS configuration): - cs-RNTIThis corresponds to the CS-RNTI used for enabling, disabling, and retransmitting; - nrofHARQ-Processes Provides the number of HARQ processes used for SPS; - periodicity Provides periodicity for configuration DL assignments for SPS; - n1PUCCH-AN Provides HARQ resources for PUCCH used in SPS (the network configures the HARQ resources to format 0 or format 1, and the actual PUCCH resources are provided by...) PUCCH-Config Configure and n1PUCCH-AN (Referring to its ID).

[0145] Multiple DL SPS configurations can be configured within the BWP of the serving cell. After configuring DL assignment for the SPS, the UE can sequentially assume that the Nth DL assignment occurs in a time slot satisfying the following formula: ( numberOfSlotsPerFrame SFN + number of time slots in the frame) = [( numberOfSlotsPerFrame SFN 开始时间 +slot 开始时间 )+ N periodicity numberOfSlotsPerFrame / 10] modulo (1024 numberOfSlotsPerFrame ), of which SFN 开始时间 and slot 开始时间 These represent the SFN and time slot of the first transmission of PDSCH after the configuration DL assignment is (re)initialized. numberOfSlotsPerFrame and numberOfSymbolsPerSlot These indicate the number of consecutive time slots per frame and the number of consecutive OFDM symbols per time slot, respectively (refer to Tables 1 and 2). Here, "SFN" refers to the SFN of a frame that may have DL assignment, and "number of time slots" refers to the number of time slots within a frame that may have DL assignment.

[0146] In some scenarios, the BS can further provide the UE with parameters for deriving the HARQ process ID assigned by the configuration DL. harq-ProcID-Offset . harq-ProcID-Offset This is the offset of the SPS HARQ process. For those without... harq- ProcID-Offset The DL assignment configuration can be determined by the following formula: HARQ process ID associated with the slot where the DL transfer begins: HARQ process ID = [floor(CURRENT_slot)] 10 / ( numberOfSlotsPerFrame periodicity))] modulo nrofHARQ-Processes , where CURRENT_slot=[(SFN numberOfSlotsPerFrame [) + slot number in the frame], and numberOfSlotsPerFrame This indicates the number of consecutive time slots per frame. For frames with... harq-ProcID-Offset The DL assignment configuration can be determined by the following formula, which specifies the HARQ process ID associated with the slot where the DL transfer begins: HARQ process ID = [floor(CURRENT_slot / periodicity)] modulo nrofHARQ-Processes + harq-ProcID-Offset, where CURRENT_slot = [(SFN [numberOfSlotsPerFrame) + slot number in the frame, and numberOfSlotsPerFrame This indicates the number of consecutive time slots per frame.

[0147] If the corresponding DCI format CRC uses RRC parameters cs-RNTI If the provided CS-RNTI scrambling and the new data indicator field for enabling transport blocks is set to 0, the UE enables or releases the verification of DL SPS assignment PDCCH or configures UL license type 2 PDCCH for scheduling. If all fields of the DCI format are set according to Tables 5 and 6, DCI format verification is implemented. Table 5 shows examples of special fields for enabling PDCCH verification for DL ​​SPS and UL license type 2 scheduling, and Table 6 shows examples of special fields for releasing PDCCH verification for DL ​​SPS and UL license type 2 scheduling.

[0148] [Table 5]

[0149] [Table 6]

[0150] The actual DL assignment and UL license for DL ​​SPS or UL license type 2, and the corresponding MCS, are provided by the resource assignment field (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 license type 2 scheduling enabled PDCCH. If verification is implemented, the UE will treat the information in the DCI format as a valid enable or release of DL SPS or configured UL license type 2.

[0151] In this disclosure, a PDSCH based on DL SPS may be referred to as an SPS PDSCH, and a PUSCH based on UL Configuration License (CG) may be referred to as a CG PUSCH. A PDSCH dynamically scheduled by DCI carried on a PDCCH may be referred to as a Dynamically Licensed (DG) PDSCH, and a PUSCH dynamically scheduled by DCI carried on a PDCCH may be referred to as a DG PUSCH.

[0152] Figure 7 This illustrates the HARQ-ACK sending / receiving process.

[0153] Reference Figure 7 The UE can detect the PDCCH in time slot n. Next, the UE can receive the PDSCH in time slot n+K0 based on the scheduling information received via the PDCCH in time slot n, and then send a UCI via the PUCCH in time slot n+K1. In this case, the UCI includes a HARQ-ACK response to the PDSCH.

[0154] The DCI (e.g., DCI format 1_0 or DCI format 1_1) carried by the PDCCH used to schedule the PDSCH may include the following information.

[0155] - FDRA: FDRA indicates the set of RBs assigned to PDSCH.

[0156] - TDRA: TDRA indicates the DL assignment with respect to the 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. PDSCH mapping type A or PDSCH mapping type B can be indicated by TDRA. For PDSCH mapping type A, the DMRS is located in the third symbol (symbol #2) or fourth symbol (symbol #3) in the slot. For PDSCH mapping type B, the DMRS is allocated in the first symbol assigned to the PDSCH.

[0157] - PDSCH-to-HARQ_feedback timer indicator: This indicator points to K1.

[0158] If the PDSCH is configured to send a maximum of one TB, the HARQ-ACK response can consist of one bit. If the PDSCH is configured to send a maximum of two TBs, the HARQ-ACK response can consist of two bits when spatial binding is not configured, and one bit when spatial binding is configured. When the timing of HARQ-ACK transmission for multiple PDSCHs is specified as time slot n+K1, the UCI transmitted in time slot n+K1 includes HARQ-ACK responses for multiple PDSCHs.

[0159] In this disclosure, the HARQ-ACK payload consisting of one or more HARQ-ACK bits of the PDSCH can be referred to as the HARQ-ACK codebook. Depending on the HARQ-ACK payload determination scheme, the HARQ-ACK codebook can be classified as i) a semi-static HARQ-ACK codebook, ii) a dynamic HARQ-ACK codebook, and iii) a HARQ process-based HARQ-ACK codebook.

[0160] In the case of a semi-static HARQ-ACK codebook, parameters related to the size of the HARQ-ACK payload to be reported by the UE are semi-statically determined by (UE-specific) higher-layer (e.g., RRC) signals. The size of the HARQ-ACK payload in the semi-static HARQ-ACK codebook (e.g., the (maximum) HARQ-ACK payload (size) transmitted via a PUCCH in one slot) can be determined based on the number of HARQ-ACK bits corresponding to a combination (hereinafter, the bundled window) of all DL carriers (i.e., DL serving cells) configured for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) that can indicate the timing of HARQ-ACK transmission. That is, in a semi-static HARQ-ACK codebook scheme, the size of the HARQ-ACK codebook is fixed (to the maximum value), regardless of the actual amount of DL data scheduled. For example, the DL-granted DCI (PDCCH) includes PDSCH and HARQ-ACK timing information, and the PDSCH and HARQ-ACK timing information can have one of several values ​​(e.g., k). For example, when a PDSCH is received in time slot #m and the PDSCH and HARQ-ACK timing information in the DL-licensed DCI (PDCCH) used to schedule the PDSCH indicates k, the HARQ-ACK information for the PDSCH can be sent in time slot #(m+k). As an example, k∈{1, 2, 3, 4, 5, 6, 7, 8}. When HARQ-ACK information is sent in time 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 time slot #n may include the HARQ-ACK corresponding to time 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 slots #(n-8) to #(n-1), regardless of the actual DL data reception (i.e., the maximum number of HARQ-ACKs). Here, the HARQ-ACK information can be replaced by the HARQ-ACK codebook or the HARQ-ACK payload. Slots can be understood / replaced as candidate times for DL ​​data reception. As described in the example, the bundling window can be determined based on the HARQ-ACK slots using PDSCH and HARQ-ACK timing, and the PDSCH and HARQ-ACK timing set can have predefined values ​​(e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or can be configured by higher-layer (RRC) signaling. A 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.

[0161] In the case of a dynamic HARQ-ACK codebook, the size of the HARQ-ACK payload that the UE needs to report can be dynamically changed through DCI, etc. The dynamic HARQ-ACK codebook is referred to as a Type 2 HARQ-ACK codebook. A Type 2 HARQ-ACK codebook can be considered an optimized HARQ-ACK feedback because the UE only sends feedback for the scheduled serving cell. 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 the downlink assignment index and is used by the BS to inform the UE that a HARQ-ACK transmission sent or scheduled should include its HARQ-ACK PDSCH. Specifically, c-DAI is an index indicating the order among PDCCHs (hereinafter, DL-scheduled PDCCHs) carrying DL-scheduled DCIs, and t-DAI is an index indicating the total number of DL-scheduled PDCCHs up to the point where there is a current slot with a PDCCH having t-DAI.

[0162] In the case of a HARQ-ACK codebook based on HARQ processes, 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 that the UE will report using a HARQ-ACK codebook based on HARQ processes can 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. A HARQ-ACK codebook based on HARQ processes is also known as a Type 3 HARQ-ACK codebook. A Type 3 HARQ-ACK codebook can be used for one-time feedback.

[0163] Discontinuous reception (DRX) of UE

[0164] To reduce power consumption, the UE uses DRX. A UE operating on DRX repeatedly turns its receive operation on and off. The characteristics of DRX for reducing unnecessary power consumption in the UE are as follows. For DRX, there are separately defined structures: one for UEs in the RRC_IDLE state where an RRC connection has not yet been established between the UE and the BS (hereinafter referred to as I-DRX), and one for UEs in the RRC_CONNECTED state where an RRC connection has been established between the UE and the BS (hereinafter referred to as C-DRX). Both DRX structures are designed to define periodic intervals (e.g., active time or on-duration period) at which the UE can expect to receive DL signals, thus reducing unnecessary power consumption in other periods. In particular, in the case of C-DRX, the start position of the on-duration period is periodically defined according to the NR Rel-16 specification. In this case, the size of the configured period (i.e., the DRX cycle) can be determined / configured by higher-level signaling such as RRC signaling provided by the BS to the UE.

[0165] Figure 8 This illustrates discontinuous reception (DRX) operation. Specifically, Figure 10 The DRX loop for a UE in the RRC_CONNECTED state is shown.

[0166] Reference Figure 8The DRX cycle includes an on-duration period and a DRX timing. The DRX cycle defines the time interval between periodic repetitions of the on-duration period, followed by a possible inactivity period. The on-duration period is the time period during which the UE monitors the PDCCH. When the UE is configured with DRX, it performs PDCCH monitoring during the on-duration period. When the UE successfully detects a PDCCH during the PDCCH monitoring period, it starts an inactivity timer and remains awake. Conversely, when the UE fails to detect any PDCCH during the PDCCH monitoring period, it transitions to a sleep state after the on-duration period. Therefore, when DRX is configured, the UE can perform PDCCH monitoring / reception discontinuously in the time domain within the procedures and / or methods according to the implementation of this disclosure. For example, when DRX is configured, the PDCCH reception timing (e.g., a time slot with a PDCCH search space) can be configured discontinuously according to the DRX configuration in this disclosure. Conversely, when DRX is not configured, the UE can perform PDCCH monitoring / reception continuously in the time domain. For example, when DRX is not configured, the timing of PDCCH reception can be configured continuously in this disclosure (e.g., time slots with PDCCH search space). Regardless of whether DRX is configured, PDCCH monitoring can be restricted during the time period configured as a measurement interval. DRX configuration information is received via higher-layer (e.g., RRC) signaling, and DRX on / off is controlled via DRX commands from the MAC layer. Once DRX is configured, the UE can perform PDCCH monitoring discontinuously, such as... Figure 10 As shown.

[0167] The table below describes the UE's DRX operation. Referring to the table, DRX configuration information is received via higher-layer signaling (e.g., RRC signaling), and DRX is enabled / disabled via DRX commands from the MAC layer. Once DRX is configured, the UE can perform PDCCH monitoring discontinuously, such as... Figure 8 As shown.

[0168] [Table 7]

[0169] MAC-CellGroupConfig includes the configuration information required to configure MAC parameters for a cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, when defining a DRX, MAC-CellGroupConfig may include the following information.

[0170] The value of -drx-OnDurationTimer: Configures the duration at which the DRX cycle begins.

[0171] The value of -drx-SlotOffset: Configures the delay before starting drx-onDurationTimer.

[0172] The value of -drx-InactivityTimer: PDCCH indicates the duration following the PDCCH timing of a new UL or DL ​​transmission by a MAC entity.

[0173] The value of -drxRetransmissionTimerDL (per DL HARQ processing, excluding broadcast processing): configures the maximum duration until a DL retransmission is received.

[0174] The value of -drxRetransmissionTimerUL (per UL HARQ process): Configures the maximum duration until a permission to retransmit to the UL is received.

[0175] The value of -drx-HARQ-RTT-TimerDL (per DL HARQ processing, excluding broadcast processing): configures the maximum duration from receiving the initial DL transmission to receiving the DL assignment for HARQ retransmission.

[0176] The value of -drx-HARQ-RTT-TimerUL (per UL HARQ process): Configures the maximum duration from receiving permission for the initial UL transmission to receiving permission for a UL retransmission.

[0177] -drx-LongCycleStartOffset: Configures the long DRX cycle and drx-StartOffset, which defines the subframes at the start of the long and short DRX cycles.

[0178] -drx-ShortCycle (optional): Configures a short DRX cycle.

[0179] -drx-ShortCycleTimer (optional): Configures the duration for which the UE should follow a short DRX cycle. For example, the value of a multiple of the short DRX cycle can be configured via drx-CycleTimer. For example, a value of n can correspond to n drx-ShortCycle.

[0180] If a DRX group is active, the UE can perform PDCCH monitoring on the serving cells within the DRX group. In this case, a DRX group refers to a group of serving cells configured by RRC and having the same DRX active time. Here, active time refers to the total duration for which the UE monitors the PDCCH. Active time may include the duration of the DRX cycle being active, the time during which the UE performs continuous reception while the inactivity timer has not expired, and the time during which the UE performs continuous reception while waiting for a retransmission opportunity. For example, when configuring DRX, the active time of a serving cell in a DRX group includes i) the time during which the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or ii) the time during which the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell in the DRX group; or the ra-ContentionResoultionTimer or msgB-RsponseWindow is running; or the time during which a new transmission of C-RNTI indicating to the MAC entity to be sent to the UE is not received after a successful reception of a random access response to a random access preamble not selected by the MAC entity in a contention-based random access preamble.

[0181] One or more DRX groups can be configured for the UE via RRC signaling from the BS. For example, if two DRX groups are configured, each serving cell is uniquely assigned to one of the two DRX groups. DRX parameters drx-onDurationTimer and drx-InactivityTimer are configured separately for each DRX group. DRX parameters drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL are common to all DRX groups. Since each serving cell belongs to only one DRX group, and the DRX parameters drx-onDurationTimer and drx-InactivityTimer are configured for each DRX group, while other DRX parameters are common to the DRX group, it can be considered that the serving cell is associated with only one set of DRX parameters.

[0182] Figure 9 This shows the configurations for long and short DRX cycles. Specifically, Figure 9This shows the case where drx-ShortCycleTimer is set to 2.

[0183] The BS can configure a long DRX cycle and an additional short DRX cycle shorter than the long DRX cycle. If no short DRX cycle is configured, the UE will follow the long DRX cycle. When a short DRX cycle is configured, the BS can set the duration of the long DRX cycle to a positive integer multiple of the short DRX cycle. The same settings can be configured for both long and short DRX cycles. onDurationTimer The value. If there is no data activity during the on-duration of the long DRX cycle (e.g., no PDCCH is received), the UE follows the long DRX cycle as if no short DRX cycle were configured. If there is data activity during the on-duration of the long DRX cycle, for example, while drx-onDurationTimer is running, the UE switches to a short DRX cycle and follows the short DRX cycle for a specific time period (e.g., while drx-ShortCycleTimer is running). In this case, the start of the on-duration in the short DRX cycle is determined by... drx-StartOffset and drx-SlotOffset Confirmed, just like in a long DRX loop. (See reference...) Figure 9 If there is no data activity during the time period when the UE follows the short DRX cycle, for example, if there is no data activity during the time period specified by drx-ShortCycleTimer If there is no data activity during the period defined by drx-ShortCycle, the UE switches from a short DRX cycle, which has a duration of drx-ShortCycleTimer, to a long DRX cycle.

[0184] Network energy saving and community DRX / DTX

[0185] Due to its potential contribution to building environmentally friendly networks by reducing carbon emissions and cutting communication operators' operating expenses (OPEX), network energy efficiency is being significantly considered in wireless communication systems, including those of 3GPP. In particular, with the increasing demand for high transmission rates following the advent of 5G communications, network base stations (BSs) need to be equipped with a greater number of antennas and provide services across wider bandwidths and frequency bands. According to recent research, the energy cost of BSs has reached up to 20% of total OPEX. Due to this increased focus on BS energy efficiency, 3GPP NR Release 18 approved a new research project called the "Network Energy Efficiency Study." For example, to enhance energy efficiency in BS transmission and reception, this study investigates how to use potential support / feedback from UEs and potential UE support information to achieve more efficient transmission and / or reception operations dynamically and / or semi-statically in the time, frequency, spatial, and power domains with finer adaptive granularity based on one or more network energy efficiency techniques.

[0186] When a BS operates in Network Energy Saving (NES) mode for energy saving (ES), it means that the BS has been pre-configured to disable the transmission of specific DL signals (e.g., the BS's Discontinuous Transmission (DTX) cycle) for multiple shutdown periods, and dynamically instructs one of these shutdown periods to indicate that no DL signals are transmitted during a predefined time period, thus reducing the power consumption of the BS and UE. NES mode can refer to an operating mode that reduces the power consumption of the BS and UE by performing operations in the frequency domain (e.g., BWP handover and dynamic resource block (RB) adaptation), the spatial domain (e.g., semi-statically or dynamically disabling a specific BS receive antenna port to stop transmission and / or reception through it), and the time domain.

[0187] As described above, when a UE is in connected mode after its initial connection to the BS, it should continuously perform PDCCH monitoring to identify whether scheduled transmissions for it exist in the search space of its various configurations. However, when such scheduling does not occur continuously, the UE's battery may be rapidly depleted due to unnecessary PDCCH monitoring each time. Therefore, the BS can configure the UE to have on periods (on duration) for PDCCH monitoring and off periods when monitoring is not required. That is, the BS can configure C-DRX for the UE to save UE power. The UE's C-DRX can also help the BS save power. For example, since the BS does not need to send PDCCH to a particular UE during the C-DRX off period of a particular UE, the BS can use resources (e.g., radio resources during the UE's C-DRX off period) for other purposes or to achieve ES gain from DTX / DRX. However, since the UE can perform transmissions without restriction in pre-configured resources (e.g., SR, PUCCH, CG PUSCH, etc.) when needed, the BS should remain ready to receive these unexpected UL transmissions from the UE even during the off period. Furthermore, because C-DRX is configured in a UE-specific manner, DRX cycles or on / off periods are not aligned among UEs within a cell (or BS). Therefore, when a UE's on period is configured in time-division multiplexing (TDM), the BS will not sleep, as it must remain awake during each on period of the UE within the cell (or BS) to transmit PDCCH, making it difficult for the BS to anticipate ES gain.

[0188] Therefore, in some implementations of this disclosure, similar to UE C-DRX, the BS can save energy by utilizing cell (specific) DTX / DRX configurations during recurring active and inactive periods to disable the transmission / reception of specific signals / channels during inactive periods. The following describes some implementations of this disclosure for the BS's cell (specific) DTX / DRX operation to save BS energy through restricted DTX / DRX, which either completely disables transmission / reception on the cell or allows transmission / reception of specific signals / channels during specific time periods. Furthermore, some implementations of this disclosure for UE operation during each time period of the combination of cell DTX / DRX with the UE's DRX operation in the cell are described. Although, for convenience, methods and corresponding operation methods for combining cell DTX / DRX with the UE's C-DRX operation are primarily described, some implementations of this disclosure can be similarly applied to and extended not only to C-DRX but also to and extended to other UE DRX operations (e.g., idle mode DRX).

[0189] During the periodic on duration, the UE performs PDCCH monitoring to identify any UL or DL ​​transmission / reception to be performed. Upon receiving the PDCCH, the UE performs DL reception or UL transmission according to the PDCCH's indication. For UL, if data to be transmitted exists in the UL buffer, the UE can wake up and send a scheduling request (SR) regardless of C-DRX, even if it is in sleep mode. UEs in idle mode periodically perform paging monitoring. When the UE is not a paging target, it can re-enter sleep mode and operate in idle mode (idle mode DRX (i.e., I-DRX)). When it is said that the UE operates in sleep mode, this can mean that the UE performs SR transmissions "regardless of the active time determined by C-DRX" or "even during periods outside the active time determined by C-DRX". In C-DRX operation, a DRX cycle is a recurring time period that includes an on duration and an off duration. The length of the DRX cycle can be defined from the beginning of the on duration until the next on duration. DRX cycles can be classified as long DRX cycles and short DRX cycles. As the DRX cycle length increases, latency can increase because when the BS has a PDSCH to send to the UE immediately after the end of a specific on-time duration, the BS must wait until the UE's next on-time duration. From the BS's perspective, since the UE does not send periodic CSI (P-CSI) or sounding reference signals (SRS) during the off-time period, the BS can allocate these resources (i.e., resources used for P-CSI or SRS transmission) to other UEs, thereby increasing resource utilization. The BS can also switch to power-saving mode during the UE's off-time period to conserve energy.

[0190] Regarding C-DRX, the BS can instruct the UE to immediately enter DRX sleep mode and not operate in active mode until the on-time duration ends via the DRX command MAC control element (CE). For example, the BS can instruct the UE to end its current active time and immediately enter a DRX cycle. When the UE is only configured with a long DRX cycle, it can operate in a long DRX cycle (based on the DRX command MAC CE). When both long and short DRX cycles are configured for the UE, the UE immediately enters a short DRX cycle after receiving the DRX command MAC CE. Furthermore, when the BS provides a long DRX command MAC CE, the UE can operate in a long DRX cycle even if a short DRX cycle is configured. The BS can also configure the long DRX cycle via RRC parameters. drx-LongCycleStartOffset and the subframes that define the start of long and short DRX cycles. drx-SlotOffset Adjust / change the starting point of a long DRX cycle. RRC parameters drx- LongCycleStartOffset The value is defined in milliseconds to allow long DRX cycles to begin at slot boundaries. Additionally, another RRC parameter... drx-SlotOffset This can be used to configure the start point of the on-time duration with slot-level granularity. In this case, by ( drx-SlotOffset The time slot offset indicated is applied to drx-LongCycleStartOffset The indicated reference point is used to define the relative position of the on duration. Although the BS can use the alignment between the on duration and off duration of multiple UEs within the cell, for ES based on the BS's dynamic transmit / receive off time mode by adjusting the start of the DRX cycle and the start of the on duration, a more dynamic offset value indication may be required.

[0191] Compared to continuous monitoring of the PDCCH (e.g., in every time slot), the UE can save energy by waking up only during the active duration to monitor the PDCCH sent to it according to the C-DRX configuration. Furthermore, when the BS has no data to send to the UE during the upcoming active duration, the BS can save even more battery power by sending a Wake-Up Signal (WUS) before the start of the UE's active duration, thus indicating that waking up is not required during the active duration (i.e., no need to initiate the onDurationTimer). In this case, when the BS has no data to send to / receive from a UE with C-DRX configuration during the upcoming active duration, the BS can instruct the UE not to wake up during that active duration by sending a WUS that can be transmitted in DCI format 2_6 (used to notify one or more UEs of power-saving information outside of DRX active time) at a WUS timing configured before the active duration. Upon receiving the WUS (e.g., a wake-up indication via DCI format 2_6), the UE can remain in sleep mode without transitioning to active mode, thus saving even more energy.

[0192] In the following description, UE DRX or C-DRX and I-DRX refer to discontinuous reception from the UE's perspective. Cell DRX refers to discontinuous reception from the BS's perspective, while cell DTX refers to discontinuous transmission from the BS's perspective. From the UE's perspective, cell DRX can mean disabling UL transmission, and cell DTX can mean disabling DL reception.

[0193] Based on cell DTX / DRX operation, similar to the structure of UE C-DRX, active and inactive periods (periods outside the active period) can be configured. During an active period, all signals and channels can be transmitted / received without restriction. During an inactive period, transmission / reception of all signals and channels is disabled, or only specific signals and channels can be transmitted / received with restrictions (e.g., only channels / signals such as PDCCH transmission or RACH / SR PUCCH reception are allowed to be transmitted / received). Cell DTX / DRX configuration can be configured and activated solely by RRC (i.e., solely via RRC signaling), or some parameters for cell DTX / DRX can be configured by RRC, while the remaining parameters are configured / indicated and activated by L1 and / or L2 signaling (e.g., (group common) DCI and / or MAC CE). Information regarding the location and duration (in the time domain) of the cell DTX / DRX active and inactive periods can be pre-configured via specific RRC parameters. For example, the start of an active period can be configured by offset from a specific subframe boundary or a specific system frame number (SFN) value, and the duration can be configured by duration-related parameters or timers. In some implementations, the BS can pre-configure multiple parameter or timer candidates and indicate one of the candidates when activated via L1 and / or L2 signaling. During a cell DTX / DRX active period, the transmission / reception of all signals and channels may not be subject to special restrictions, as is the case during normal BS operation. Time periods outside of active periods are generally considered inactive periods, during which transmission / reception is restricted except for pre-configured signals and channels, and the BS can achieve ES gain by performing only such minimal transmission / reception operations. Therefore, operations performed when NES state / mode is enabled can be considered for use in time periods outside of active periods.

[0194] For example, to reduce the activity time of DL transmission / UL reception by the BS, the UE can be configured with periodic cell DTX / DRX patterns (i.e., active and inactive periods). The cell DTX / DRX pattern can be shared by all UEs within the cell. Periodic cell DTX patterns can be configured for individual serving cells via RRC. The BS can configure cell-only DTX, cell-only DRX, or both for a cell. Cell DTX and cell DRX patterns can be configured and enabled individually. Up to N cell DTX / DRX patterns can be configured per MAC entity for different serving cells, where N is a predefined value. Cell DTX / DRX can be enabled / disabled via RRC signaling or L1 group common signaling (e.g., signaling via group common PDCCH). The BS can control cell DTX and cell DRX operations by providing cell DTX / DRX configuration via RRC signaling. For example, through cell DTX / DRX configuration, the BS can provide timers (e.g., cell DTX / DRX enable duration timers) related to the active period at the start of a cell DTX / DRX cycle, the subframe at the start of the cycle, the delay before the start of the active period, and the RRC parameters for the cell DTX / DRX cycle period (i.e., cell DTX / DRX periodicity). The active period in cell DTX / DRX can be the period during which the UE waits to receive a PDCCH or SPS and transmits an SR or CG. Cell DTX / DRX cycling specifies that the active period repeats periodically following the inactive period. The active period and cycle parameters can be common to both cell DTX and cell DRX. The BS can configure C-DRX and cell DTX / DRX to at least partially overlap between the UE's C-DRX enable period and the cell DTX / DRX active period. For example, the BS can configure the UE's C-DRX periodicity to be an integer multiple of the cell DTX / DRX periodicity, and vice versa.

[0195] In some implementations, cell DTX operation may affect the UE's monitoring activity of PDCCH and configured DL assignments under RRC_CONNECTED. For a serving cell with cell DTX configured and enabled, the UE (e.g., the UE's MAC entity) monitors the PDCCH on the serving cell when the serving cell is in a cell DTX activity period. The serving cell's cell DTX activity period may include the time period for running a cell DTX / DRX enable duration timer for the serving cell. For example, for a serving cell with cell DTX configured and enabled, when the serving cell is not in a cell DTX activity period, the UE (e.g., the UE's MAC entity) will not monitor the PDCCH on the serving cell and will not receive transport blocks on the serving cell according to the SPS configured DL assignment (i.e., SPS PDSCH reception is not performed), regardless of whether the UE is in a UE C-DRX activity period.

[0196] In some implementations, cell DRX operation can control the SR (Send Transfer) and configure UL (Ultimate Required Transfer) activities of a UE in RRC_CONNECTED state. In some cases, when cell DRX is configured and enabled for a serving cell, the UE (e.g., the UE's MAC entity) can, in principle, only perform CG PUSCH and PUCCH transmissions on the serving cell during cell DRX active periods (if the serving cell is a PUCCH cell). For example, when the serving cell with cell DRX configured and enabled is in a cell DRX inactive period, the UE (e.g., the UE's MAC entity) does not send SRs in the PUCCH resources used for SRs (even if the serving cell is a PUCCH cell), does not report periodic CSIs on the PUCCH (even if the serving cell is a PUCCH cell), and does not report semi-persistent CSIs configured on the serving cell's PUSCH. In other words, when cell DRX is configured and enabled for a serving cell, the UE will not perform transmissions in the serving cell's CG resources or send SRs on the serving cell during DRX inactive periods.

[0197] Multiple SPS PDSCH / CG PUSCH timings within a single cycle of an SPS / CG configuration

[0198] As one use case for URLLC, Time-Sensitive Networking (TSN) can be included. TSN refers to a communication network system in which all devices within a specific area are time-synchronized with the same clock for real-time communication, and motion control of devices or collaborative robots in a factory is established based on this time synchronization. Additionally, XR services can be included as an alternative application of NR systems.

[0199] XR refers to immersive technologies and services that utilize technologies such as Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), and holograms to provide users with an environment in which they can communicate and live in a virtual space similar to reality without the constraints of time and space. XR is one of the main services introduced in NR wireless communication systems. Typically, XR has specific services in which one or more DL video streams are closely synchronized with frequent UL attitude / control updates.

[0200] 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 pre-configured resources such as SPS / CG is considered to support XR. For example, the BS can provide SPS / CG configuration to the UE considering the average inter-arrival time of packets. However, due to jitter (which refers to unintentional time deviations occurring in periodic signals), the actual inter-arrival time of packets is inconsistent (random). In XR, jitter occurs because the time required to process a frame before transmission varies due to the different amount of information in each frame.

[0201] 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 repeat periodically in the time domain as determined by each SPS / CG configuration. That is, the initial configuration / indicated resource allocation can repeat periodically as 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 procedure. Various types of XR data exist. Among these types, sensor information, location information, and video data, typically reported periodically by the UE, can be transmitted and received on SPS / CG resources. The arrival time of this data is inconsistent due to variations in video encoding time, sensor measurement time, higher-layer operation, or network routing, which can cause jitter. Additionally, the size of the radio resources required for transmission can vary depending on the encoding method and frame type used by the UE / BS to transmit video.

[0202] To support this video data transmission, allocating radio resources based on the maximum radio resource size required by the BS could lead to a waste of radio resources in most cases of video information transmission. Allocating radio resources based on a smaller radio resource size could result in additional radio resource allocation during periods of heavy traffic, leading to additional latency.

[0203] Furthermore, since some data is generated based on events, it is difficult to accurately determine the time of data generation. To reduce latency caused by scheduling, SPS / CG resources could be used for this data. In this case, a skipping method could be considered. According to this skipping method, a sufficient number of resources are allocated at short intervals to prepare for data occurrence, and the UE or BS selectively uses some resources while ignoring others. However, to skip transmission and reception, response signals need to be properly considered to check the reception and transmission status between the UE and the BS. If the UE sends a response signal even for transmissions that have not been received, the BS needs to prepare resources for the UE to always send a 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 result in a significant UL burden. In addition, considering that such resources can be multiplexed among UEs, the UL resource burden needs to be carefully considered.

[0204] The above considerations should be taken into account when using XR services or similar third-party services. For example, to efficiently transmit information such as video with dynamically changing payload sizes for various services or traffic, the UE can selectively use the CG PUSCH configured in the SPS / CG and report the unselected radio resources to the BS in advance. This operation allows the BS to alleviate the burden on UL radio resources by allocating resources to other UL transmissions.

[0205] Some implementations of this disclosure will be described below. In such implementations, 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 only on 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 UE).

[0206] In the following description, implementations of this disclosure will be based on semi-persistently configured DL SPS and UL CG radio resources. However, implementations of this disclosure are not limited to this and can also be applied to radio resources allocated by dynamic scheduling received by the UE. For example, implementations of this disclosure can be applied whereby the UE determines a HARQ-ACK timing for multiple DL radio resources allocated to the UE, regardless of whether it is an SPS PDSCH or a PDSCH indicated by dynamic scheduling. Additionally, implementations of this disclosure can be applied when multiple radio resources are not semi-persistently configured but configured by dynamic indication, for example, when multiple radio resources are configured at once via DCI. Therefore, even without separate explanation, implementations of this disclosure can be applied to all types of transmit / receive methods desired by the BS and UE. In the following description, for ease of explanation, the general term "SPS" will be used to refer to semi-persistently configured radio resources (e.g., DL / UL SPS, CG, etc.) to describe implementations of this disclosure.

[0207] In some implementations of this disclosure, the term "transmission opportunity (TO)" may refer to radio resources configured for SPS / CG purposes (e.g., SPS PDSCH or CG PUSCH). An entity performing a transmission (e.g., a BS for DL ​​or a UE for UL) may attempt to transmit on a TO, while a receiver (e.g., a UE for DL ​​or a BS for UL) may expect to transmit and attempt to receive on each TO. In this disclosure, the term "TO" may be used interchangeably with transmission opportunity. TO or transmission opportunity is simply referred to as opportunity.

[0208] In the following description, implementations of this disclosure will be based on NR systems; however, implementations of this disclosure are not limited to transmission / reception in NR. Furthermore, although implementations of this disclosure will be described using the characteristics and structure of XR services as examples, implementations of this disclosure are not limited to supporting XR services. In other words, even without separate explanation, implementations of this disclosure are applicable to all wireless communication transmission / reception structures and services.

[0209] The following describes some implementations of the methods and procedures disclosed herein regarding a UE notifying a BS of unused radio resources. Implementations of this disclosure may include methods by which the BS allocates PDSCH / PUSCH radio resources to the UE, and methods by which the UE performs DL reception or UL reception on the allocated radio resources. Some implementations of this disclosure may include methods by which the UE transmits a HARQ-ACK PUCCH response in response to PDSCH reception, and methods by which the UE receives retransmitted DCI from the BS via PDCCH after PUSCH transmission. In some implementations of this disclosure, the UE may transmit signals and channels to advertise its capabilities and / or service requirements, and the BS may receive said signals and channels.

[0210] Figure 10 The operation flow of a UE according to some implementations of this disclosure is illustrated, and Figure 11 The operation flow of a BS according to some implementations of this disclosure is illustrated.

[0211] Reference Figure 10 The UE can receive RRC configurations related to unused resource indications / information (URIs), that is, RRC parameters related to the URI and RRC configurations related to CG PUSCH (e.g., CG configuration) (S1001). CG configurations can be automatically activated or initially deactivated. When the UE has UL services / data to transmit, that is, when the UL services / data become available for transmission, the UE can determine or predict the CG PUSCH resources required for the transmission of the UL services / data (i.e., CG PUSCH timing) (S1003). The UE can report the URI to the BS based on the required CG PUSCH resources (or their quantity) (S1005). The UE can use the CG PUSCH resources to transmit PUSCHs carrying services / data (S1007).

[0212] Reference Figure 11The BS can provide the UE with RRC configuration for the URI and RRC configuration related to the CG PUSCH (e.g., CG configuration) (S1101). The BS can receive the URI from the UE (S1103). The BS can receive PUSCH on the CG PUSCH resource based on the CG configuration (S1105). The BS can perform UL scheduling based on the URI.

[0213] Figure 12 The signal transmission / reception flow of a UE and BS according to some implementations of this disclosure is illustrated.

[0214] Reference Figure 12 The UE can receive RRC configuration for the URI and RRC configuration for sending CG PUSCH from the BS (e.g., IE). ConfiguredGrantConfig (S1201 and S1202). The semi-persistent configuration (i.e., CG PUSCH configuration) provided to the UE can be automatically activated or initially deactivated. When the UE has UL service (S1203) and intends to perform UL transmission on CG PUSCH, the UE with RRC configuration set for the URI can determine or predict the timing of CG PUSCH usage, taking into account the UE's buffer state and the characteristics of CG PUSCH (S1004). Considering the number of CG PUSCHs determined or predicted to be used, the UE can report information to the BS about unused CG PUSCH resources (i.e., CG PUSCH timing) (S1205). Upon receiving this information, the BS can release unused CG PUSCH resources only at the corresponding time and schedule UL transmissions for other purposes to the UE or other UEs. The UE may perform UL transmission on other CG PUSCH resources that are reported as unused, in addition to the CG PUSCH resources mentioned above, and the BS may attempt UL reception on radio resources among other CG PUSCH resources that are reported as unused, in addition to the CG PUSCH resources mentioned above (S1206).

[0215] Figure 13 An example of a CG PUSCH configured according to some implementations of this disclosure is shown.

[0216] Regarding URIs, the following implementations can be considered for efficient use of radio resources in the system.

[0217] As an example, in some implementations, the BS can indicate and configure one or more CG PUSCHs to the UE during a predetermined time interval T. As another example, the BS may include information about multiple TDRAs in a CG configuration or activate the relevant CG via a DCI containing TDRA information, thereby configuring multiple radio resources (i.e., multiple CGPUSCH opportunities) within a period. For instance, the BS may provide the UE with a UL-licensed CG configuration including multiple consecutive configurations within a single period. (See reference...) Figure 13 Depending on the CG configuration, multiple CG PUSCH opportunities can occur within a single period of the CG configuration.

[0218] As another example, the BS may instruct the UE to configure one or more SPS / CG radio resources and allocate multiple SPS / CG radio resources to repeatedly transmit a TB within a periodic period or a predetermined time range. For example, one or more SPS / CG configurations may be provided, and the PDSCH / PUSCH timing based on one or more SPS / CG configurations may occur within a periodic period or a predetermined time range.

[0219] As another example, the BS may instruct the UE to configure one or more SPS / CG radio resources and allocate multiple SPS / CG radio resources to transmit multiple TBs within a periodic period or a predetermined time range. For example, one or more SPS / CG configurations may be provided, and the PDSCH / PUSCH timing based on one or more SPS / CG configurations may occur within a periodic period or a predetermined time range.

[0220] In the following text, for convenience, the UCI in the CG PUSCH carrying the URI will be referred to as Unused Transmission Time (UTO)-UCI. That is, the terms UTO-UCI and URI are used interchangeably in the following text.

[0221] Figure 14 An example of UTO-UCI transmission is shown. In Figure 14 In this context, "TO" indicates the transmission timing. Figure 14 In the example, in the bit values ​​of the URI (i.e., UTO-UCI), "0" can indicate that the UE can send CGPUSCH to the corresponding TO in the case of CG, and "1" can indicate that the UE will send CG PUSCH to the corresponding TO in the case of not being in CG.

[0222] For example, in the case where the URI sent at CG PUSCH timing #i indicates whether to use the four CG PUSCH timings following CG PUSCH timing #i (CG PUSCH timings #(i+1) to (i+4)), refer to Figure 14 Bit 0011 of the URI sent at CG PUSCH time #1 is mapped one-to-one to CG PUSCH time #2 to CG PUSCH time #5 in ascending order of start time; bit 0111 of the URI sent at CG PUSCH time #2 is mapped one-to-one to CG PUSCH time #3 to CG PUSCH time #6 in ascending order of start time; and bit 0011 of the URI sent at CG PUSCH time #3 is mapped one-to-one to CG PUSCH time #4 to CG PUSCH time #7 in ascending order of start time.

[0223] When a CG PUSCH is configured for a cell and a cell DTX / DRX configuration is also applied to that cell, it is unclear how to configure the UTO-UCI. In this regard, some implementations of the UCI transmission method of this disclosure considering cell DTX / DRX configuration are described below. For example, some implementations of this disclosure are described regarding how to handle CG PUSCH resources that overlap with or are included in the off-duration period (i.e., the cell DRX inactivity period) when generating the UTO-UCI when performing cell DRX operations where the BS periodically repeats the on / off duration mode for UL reception to save energy.

[0224] When a UCI on a PUSCH / (CG-)PUCCH is multiplexed into a single PUCCH / PUSCH and the single PUCCH / PUSCH including the multiplexed UCI overlaps with a cell DRX inactive period, it may be inappropriate to unconditionally not transmit the single PUCCH / PUSCH including the multiplexed UCI, because a large number of UCIs may not be provided to the BS. Below, some implementations of this disclosure are described regarding how to transmit UCIs when a PUCCH / PUSCH transmission carrying multiplexed UCIs overlaps with a cell DRX inactive period.

[0225] Some of the implementations / methods described below may be selectively applied. Alternatively, each implementation / method described below may be executed independently without combination with other implementations / methods, or one or more implementations / methods may be executed in combination. Some terms, symbols, and orders used in this disclosure may be replaced with other terms, symbols, and orders.

[0226] It can be specified that the implementation methods / methods described in this disclosure are applied only when the UE receives relevant configuration information from the BS (or core network). The configuration information can be provided by higher-layer signaling (e.g., SIB or RRC signaling). Alternatively, the information configured by higher-layer signaling (e.g., SIB or RRC signaling) can be activated / deactivated by separate signaling (e.g., DCI or MAC control element (CE)). Furthermore, it can be specified that the UE reports information indicating whether it can support the implementation methods / methods of this disclosure (e.g., capabilities), and the BS (or core network) receives this information.

[0227] <Method #1> A method for handling CG PUSCH resources that overlap with the UE's inactive DRX cycle within a cell configured with cell DTX / DRX, and a method for configuring UTO-UCI.

[0228] (1) A method of indicating UTO-UCI by also treating CG PUSCH resources that overlap with the cell DRX inactive period as invalid (e.g., a method of configuring a UTO-UCI bitmap that does not include invalid CG resources).

[0229] (2) A method of mapping the remaining bits, except those allocated to valid CGs before the cell DRX inactive period, as “unused” (e.g., treating CG PUSCH TOs belonging to the cell DRX inactive period as valid but indicating them as unused).

[0230] (3) A method for treating CG resources in inactive periods as invalid when sending CG PUSCH during an active period, and treating CG resources in inactive periods as valid when sending CG PUSCH during an inactive period, based on the cell DTX / DRX configuration.

[0231] (4) Methods for not equipping UTO-UCI on the CG PUSCH or not expecting related configuration when cell DTX / DRX is configured.

[0232] (5) A method to not mount UTO-UCI on the CG PUSCH only when the cell DTX / DRX is configured and activated, and to mount UTO-UCI on the CG PUSCH when the cell DTX / DRX is deactivated.

[0233] (6) A method for deactivating / releasing only the CG configured for UTO-UCI (i.e., the CG configuration used for UTO-UCI reporting) when cell DTX / DRX is configured and activated.

[0234] When cell DTX / DRX is configured and executed in the serving cell configured for the UE, the transmission / reception of specific DL / UL signals / channels can be disabled during inactive periods according to predefined active / inactive period patterns. For example, when the reception of CG PUSCH is configured and / or defined to be disabled during the cell DRX inactive period (in the standard), the UE will not transmit CG PUSCH in CG resources (i.e., CG PUSCH timings) included in the inactive period or overlapping with the inactive period, and the BS may not expect to receive CG PUSCH at the corresponding timing.

[0235] However, since the UE can notify the BS whether the available CG PUSCH resources in the future CG PUSCH resources (which are the available CG PUSCH resources in the pre-configured CG resources) are used or unused by the UTO-UCI sent with the CG PUSCH, a method may be needed to handle CG-PUSCH resources that overlap with the cell DRX inactive period and configure the UTO-UCI.

[0236] Figure 15 and Figure 16 This is an example of UTO-UCI transmission based on some implementations of this disclosure.

[0237] In this disclosure, when a CG resource is considered valid, it means that information about whether the TO corresponding to the corresponding CG PUSCH is used / unused is included in the UTO-UCI. Conversely, when a CG resource is considered invalid, it means that information about whether the TO corresponding to the corresponding CG PUSCH is used / unused is excluded from the UTO-UCI. Furthermore, a bit value of "1" in the bitmap included in the UTO-UCI can indicate that the UE does not send a CG PUSCH at the corresponding TO (i.e., the corresponding bit is mapped to "unused"), and a bit value of "0" can indicate that the UE can send a CG PUSCH at the corresponding TO.

[0238] In one approach to cell DRX inactivity periods, the UE may treat all CG resources (i.e., CG PUSCH timings) included in or overlapping with cell DRX inactivity periods as invalid CG resources and exclude them from the UTO-UCI. That is, the UE may treat only the remaining CG resources belonging to the cell DRX active period as valid CG resources, excluding invalid CG resources overlapping with the cell DRX inactivity period, and may configure the UTO-UCI bitmap with bits corresponding to the valid CG resources respectively and provide it to the BS. Assuming the UE configures the UTO-UCI in this manner, the BS can receive and interpret the UTO-UCI. The cell DRX inactivity period may be an inactivity period determined according to the UE-specific cell DRX mode under a semi-static configuration, regardless of the (de)activated DCI indicating the cell DRX configuration, or it may be an inactivity period dynamically determined by the (de)activated DCI indicating the cell DRX configuration. For example, in the case where a UTO-UCI transmission includes a 4-bit bitmap corresponding to 4 subsequent PUSCH timings, refer to... Figure 15 In some implementations of this disclosure, TO#4 is considered an invalid TO for UTO-UCI (because it overlaps with the cell DRX inactivity period), and in TOs after the CG PUSCH timing (i.e., TO) when UTO-UCI is to be sent, UTO-UCI can be configured by not treating TO#4 as the target of UTO-UCI. Figure 15In the example, bit 0011 of the URI sent at CG PUSCH time #1 (i.e., TO #1) is mapped one-to-one with CG PUSCH time #2, CG PUSCH time #3, CG PUSCH time #5, and CG GPUSCH time #6 in ascending order of start time; bit 0111 of the URI sent at CG PUSCH time #2 is mapped one-to-one with CG PUSCH time #3, CG PUSCH time #5, CG PUSCH time #6, and CG PUSCH time #7 in ascending order of start time; and bit 1110 of the URI sent at CG PUSCH time #3 can be mapped one-to-one with CG PUSCH time #5 through CG PUSCH time #8 in ascending order of start time. The UTO-UCI for CG PUSCH times overlapping with cell DRX inactivity periods may not need to be provided to the BS. This is because the BS knows the cell DRX inactivity period and therefore can say that it knows the CG PUSCH times within the cell DRX inactivity period will not be used by the UE. According to some implementations of this disclosure, when a CG PUSCH timing based on a CG PUSCH configuration with UTO-UCI overlaps with an inactive period of an active cell DRX configuration, the UE treats the overlapping CG PUSCH timing as an invalid PUSCH timing, and the invalid CG PUSCH timing is excluded from the N CG PUSCHs corresponding to the N bits of UTO-UCI. Accordingly, since the BS has prior knowledge, the UE does not send unnecessary information. Instead, when it has already determined whether to use the CG PUSCH timing after the cell DRX inactive period before the start of the cell DRX inactive period, there are the following advantages: the UTO-UCI sent before the cell DRX inactive period can notify the BS in advance whether to use the CG PUSCH timing after the inactive period.

[0239] As another approach (especially when DRX activity periods are long), the following method can be considered: The remaining bits, excluding those allocated to valid CG resources before the cell DRX inactivity period, are mapped to "unused" (or mapped to a predefined / configured value between "0" and "1"). That is, although CG resources belonging to the cell DRX inactivity period are also considered valid CG resources, they can be indicated as unused in the UTO-UCI (or mapped to a predefined / configured value between "0" and "1"). The cell DRX inactivity period can be an inactivity period determined according to the semi-statically configured UE-specific cell DRX mode, regardless of the (de)activated DCI indicating the cell DRX configuration, or it can be an inactivity period dynamically determined by the (de)activated DCI indicating the cell DRX configuration. See reference. Figure 16 In some implementations of this disclosure, TO#4 overlaps with the cell DRX inactive cycle, but is considered a valid TO for UTO-UCI, and the UE can set the corresponding bit to indicate that the UE will not send CG PUSCH on TO#4 and will include it in UTO-UCI. Figure 16 In the example, bit 0011 of the URI sent at CG PUSCH time #1 (i.e., TO #1) is mapped one-to-one with CG PUSCH time #2, CG PUSCH time #3, CG PUSCH time #5 and CG PUSCH time #6 in ascending order of start time; bit 0111 of the URI sent at CG PUSCH time #2 is mapped one-to-one with CG PUSCH time #3, CG PUSCH time #5, CG PUSCH time #6 and CG PUSCH time #7 in ascending order of start time; and bit 1110 of the URI sent at CG PUSCH time #3 can be mapped one-to-one with CG PUSCH time #5 to CG PUSCH time #8 in ascending order of start time.

[0240] In another method, when a UE transmits a CG PUSCH during a semi-static active period determined by the cell DRX configuration, it can configure UTO-UCI by treating the CG resources during the cell DRX inactive period as invalid, and conversely, when a UE transmits a CG PUSCH during a semi-static cell DRX inactive period, it can configure UTO-UCI by treating the CG resources during the inactive period as valid.

[0241] When a cell DRX is configured for its serving cell, the UE may not load the UTO-UCI on the CG PUSCH, or may not expect the relevant configuration (e.g., the RRC parameter for configuring the UTO-UCI bit width). nrof_UTO_UCI Configure the RRC parameter for the encoding rate of UTO-UCI. betaOffsetUTO-UCI Alternatively, the UE can choose not to apply the relevant configuration even if it is received. Furthermore, the UE can choose not to load UTO-UCI only when the cell DRX is configured and the DRX configuration is actually activated via RRC or DCI, and can load UTO-UCI on the deactivated CG PUSCH even if the cell DRX is configured. Alternatively, when the cell DRX is configured or activated for its serving cell, the UE can simply deactivate and / or release the CG configuration that has UTO-UCI configured.

[0242] In the above method, the BS can actually deactivate / release the CG resources configured to configure UTO-UCI, and when the cell DRX is configured or activated, the UE can consider that the CG resources configured to configure UTO-UCI have been deactivated / released. In other words, the BS can actually deactivate or release the CG PUSCH timings that overlap with the cell DRX inactivity period in the CG PUSCH timings of the CG configuration including UTO-UCI, and when the cell DRX is configured (and activated), the UE can generate UTO-UCI by treating the CG PUSCH timings that overlap with the cell DRX inactivity period in the CG PUSCH timings of the CG configuration including UTO-UCI as having been deactivated / released.

[0243] <Method #2> UCI transmission method when multiple UCIs are multiplexed into one PUCCH / PUSCH and the PUCCH / (CG-)PUSCH overlaps with the cell DRX inactive period, including UCIs.

[0244] For PUCCH / (CG)-PUSCH that are reused across multiple UCIs: - Method (1): Determining whether to discard PUCCH / (CG)-PUSCH based on the degree of overlap with the cell's DRX inactive cycle.

[0245] - Method (2): A method for determining whether to discard PUCCH / (CG)-PUSCH based on the number or type of reused UCIs.

[0246] - Method (3): A method for determining whether to discard PUCCH / (CG)-PUSCH for each included HARQ-ACK codebook type

[0247] - Method (4): When multiple UCIs are reused, the multiplexed PUCCH / (CG-)PUCCH should be discarded, only HARQ-ACK should be sent individually.

[0248] - Method (5): A method for determining whether to discard PUCCH / (CG)-PUSCH by combining the above methods.

[0249] In some scenarios, when the UE receives the cell DRX configuration from the BS and the cell DRX is activated, no transmit / receive operations are performed during the cell DRX inactive period, except for the SPS PDSCH or DL / UL (including HARQ-ACK) scheduled during the active period (via dynamic DL assignment or UL permission). That is, the UE does not transmit the semi-static PUCCH / (CG-)PUSCH included in the cell DRX inactive period, and the BS does not expect to receive it. When multiple PUCCHs and / or (CG-)PUSCHs are scheduled in the same time slot, the UE can first multiplex them according to the UCI multiplexing rules in the standard document, and if it overlaps with the cell inactive period, discard the PUCCH / (CG-)PUSCH carrying the multiplexed UCI, and only transmit it if it does not overlap. However, this approach may result in a large loss of UCIs because the container with multiple UCIs multiplexed (i.e., PUCCH / (CG-)PUSCH) is completely discarded due to the cell DRX inactive period. Therefore, in some implementations of this disclosure, a method may be considered for determining whether to send PUCCH / PUSCH that overlaps with the cell DRX inactive period based on specific conditions pre-configured by the BS (or defined in a standard document).

[0250] According to method (1), when some symbols of the PUCCH / (CG-)PUSCH, which serves as a container for multiplexed UCI after UCI multiplexing, overlap with the cell DRX inactive period, it is determined whether to discard the PUCCH / (CG-PUSCH) based on the number of overlapping symbols. For example, when the BS sets the threshold to 2 symbols for the UE, it can be configured / indicated that when 2 or fewer of the (scheduled) symbols of the PUCCH / (CG-)PUSCH carrying multiple multiplexed UCIs overlap with the cell DRX inactive period, transmission is performed even if the PUCCH / (CG-PUSCH) overlaps with the inactive period; otherwise (i.e., when more than 2 symbols overlap), transmission is discarded. Alternatively, it can be configured / indicated that the PUCCH / (CG-)PUSCH used as a container after UCI multiplexing is transmitted when the symbols of the container partially overlap with the cell DRX inactive period, and is discarded when they completely overlap (i.e., all symbols of the PUCCH / (CG-)PUSCH are included in the inactive period).

[0251] According to method (2), whether to discard a PUCCH / (CG-)PUSCH is determined based on the number or type of UCIs multiplexed in the PUCCH / (CG-)PUSCH, which is a container multiplexed as a UCI. For example, it can be configured / indicated that a PUCCH / (CG-)PUSCH is sent only when HARQ-ACK or HARQ-ACK and non-periodic CSI (AP-CSI) are included in the multiplexed UCIs, instead of being discarded, and discarded in other cases. Alternatively, it can be configured / indicated that a PUCCH / (CG-)PUSCH is sent when the number of multiplexed UCIs is 3 or greater, and discarded when the number is less than 3.

[0252] According to method (3), it is determined whether to discard each PUCCH / (CG-PUSCH) of each HARQ-ACK codebook type included in the PUCCH / (CG-)PUSCH that serves as a UCI multiplexed container. For example, PUCCH / (CG-PUSCH) can be discarded when the included codebook is of type 1 (i.e., semi-static codebook), and PUCCH / (CG-PUSCH) can be sent when it is of type 2 (i.e., dynamic codebook).

[0253] According to method (4), when the PUCCH / (CG-)PUSCH, which is a UCI multiplexed container, includes HARQ-ACK, overlaps with the cell DRX inactive period (on all or some symbols), and should therefore be discarded, the UE sends HARQ-ACK through the PUCCH that the UE originally intended to send in the same time slot (i.e., the PUCCH resources initially indicated for HARQ-ACK transmission are preserved as is).

[0254] Methods #1 and #2 described above can be used individually or together.

[0255] Figure 17 This is a flowchart illustrating some implementations of UE operation according to this disclosure.

[0256] The UE can perform operations according to some implementations of this disclosure. The UE 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 implementations of this disclosure. A processing apparatus for the UE 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 implementations of this 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 implementations of this disclosure.

[0257] Reference Figure 17 The operation of the UE or the UE, processing device, (non-transitory) computer-readable storage medium and / or computer program product may include: receiving CG configuration for the cell (S1701); and transmitting UTO-UCI based on the CG configuration (S1703).

[0258] In some implementations, the UTO-UCI may include information indicating whether a predetermined number of CGPUSCH times, excluding CG PUSCH times that overlap with the inactive period of the cell DRX within the CGPUSCH times configured in the CG, are used or not. For example, 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 the N CG PUSCH times, and each of the N bits may have a first bit value or a second bit value. The first bit value may indicate that the UE can transmit CG PUSCH at the corresponding CG PUSCH time, and the second bit value may indicate that the UE does not transmit CG PUSCH at the corresponding CG PUSCH time.

[0259] In some implementations, the method or operation may further include: receiving a configuration for cell DRX.

[0260] In some implementations, UTO-UCI can be sent via CG PUSCH based on CG configuration.

[0261] Figure 18 This is a flowchart illustrating some implementations of B / S operations according to this disclosure.

[0262] The BS can perform operations according to some implementations of this 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 implementations of this disclosure. A processing apparatus 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 implementations of this 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 implementations of this disclosure.

[0263] Reference Figure 18 The operation of the BS method or the BS, processing apparatus, (non-transitory) computer-readable storage medium and / or computer program product may include: transmitting CG configuration for the cell (S1801); and receiving UTO-UCI based on the CG configuration (S1803).

[0264] In some implementations, the UTO-UCI may include information indicating whether a predetermined number of CGPUSCH times, excluding CG PUSCH times that overlap with the inactive period of the cell DRX within the CGPUSCH times configured in the CG, are used or not. For example, 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 the N CG PUSCH times, and each of the N bits may have a first bit value or a second bit value. The first bit value may indicate that the UE can transmit CG PUSCH at the corresponding CG PUSCH time, and the second bit value may indicate that the UE does not transmit CG PUSCH at the corresponding CG PUSCH time.

[0265] In some implementations, the method or operation may further include: sending a configuration for the cell DRX.

[0266] In some implementations, UTO-UCI can be received via CG PUSCH based on CG configuration.

[0267] Examples of this disclosure as described above have been presented to enable those skilled in the art to implement and practice this disclosure. Although the disclosure is described with reference to examples, various modifications and variations can be made to the examples of this disclosure by those skilled in the art. Therefore, this disclosure is not intended to be limited to the examples set forth herein, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

[0268] Implementations of this disclosure can be used in BS, UE, or other devices in wireless communication systems.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Receive configuration license (CG) configuration for the cell; as well as Based on the CG configuration, unused link transmission timing - uplink control information UTO-UCI is sent. The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. In this N-bit bitmap, N bits are mapped one-to-one to N CG Physical Uplink Shared Channel (PUSCH) timings. Each of the N bits has a first bit value or a second bit value. The first bit value indicates that the UE can transmit CG PUSCH at the corresponding CG PUSCH timing, and the second bit value indicates that the UE does not transmit CG PUSCH at the corresponding CGPUSCH timing. The N CG PUSCH timings do not include CGPUSCH timings that overlap with the inactive period of discontinuous DRX reception in the cell.

2. The method according to claim 1, further comprising the following steps: Receive the configuration for the DRX of the cell.

3. The method according to claim 1, wherein, The UTO-UCI is sent via CG PUSCH based on the CG configuration.

4. An apparatus, the apparatus comprising: At least one processor; as well as At least one memory, operatively connectable to the at least one processor and storing instructions, which, when executed, cause the at least one processor to perform operations for a user equipment (UE), the operations including: Receive configuration license (CG) settings for the cell; and Based on the CG configuration, Unused Transmission Hour-Uplink Control Information (UTO-UCI) is sent. The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. In this N-bit bitmap, N bits are mapped one-to-one to N CG Physical Uplink Shared Channel (PUSCH) timings. Each of the N bits has a first bit value or a second bit value. The first bit value indicates that the UE can transmit CG PUSCH at the corresponding CG PUSCH timing, and the second bit value indicates that the UE does not transmit CG PUSCH at the corresponding CGPUSCH timing. The N CG PUSCH timings do not include CGPUSCH timings that overlap with the inactive period of discontinuous DRX reception in the cell.

5. The device according to claim 4, wherein, The operation also includes: Receive the configuration for the DRX of the cell.

6. The device according to claim 4, wherein, The UTO-UCI is sent via CG PUSCH based on the CG configuration.

7. A non-transitory computer-readable storage medium storing at least one program code including instructions that, when executed, cause at least one processor to perform operations for a user equipment (UE), the operations including: Receive configuration license (CG) settings for the cell; as well as Based on the CG configuration, Unused Transmission Hour-Uplink Control Information (UTO-UCI) is sent. The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. In this N-bit bitmap, N bits are mapped one-to-one to N CG Physical Uplink Shared Channel (PUSCH) timings. Each of the N bits has a first bit value or a second bit value. The first bit value indicates that the UE can transmit CG PUSCH at the corresponding CG PUSCH timing, and the second bit value indicates that the UE does not transmit CG PUSCH at the corresponding CGPUSCH timing. The N CG PUSCH timings do not include CGPUSCH timings that overlap with the inactive period of discontinuous DRX reception in the cell.

8. The non-transitory computer-readable storage medium according to claim 7, wherein, The operation also includes: Receive the configuration for the DRX of the cell.

9. The non-transitory computer-readable storage medium according to claim 7, wherein, The UTO-UCI is sent via CG PUSCH based on the CG configuration.

10. A method performed by a base station (BS), the method comprising the following steps: Send the configuration license (CG) configuration for the cell; and Based on the CG configuration, Unused Transmission Hour-Uplink Control Information (UTO-UCI) is received from the User Equipment (UE). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. In this N-bit bitmap, N bits are mapped one-to-one to N CG Physical Uplink Shared Channel (PUSCH) timings. Each of the N bits has a first bit value or a second bit value. The first bit value indicates that the UE can transmit CG PUSCH at the corresponding CG PUSCH timing, and the second bit value indicates that the UE does not transmit CG PUSCH at the corresponding CGPUSCH timing. The N CG PUSCH timings do not include CGPUSCH timings that overlap with the inactive period of discontinuous DRX reception in the cell.

11. The method according to claim 10, further comprising the step of: Send the configuration for the DRX of the cell.

12. The method according to claim 10, wherein, The UTO-UCI is received via CG PUSCH based on the CG configuration.

13. A base station (BS), the BS comprising: At least one processor; as well as At least one memory, operatively connectable to the at least one processor and storing instructions, which, when executed, cause the at least one processor to perform an operation for the BS, the operation including: Send the configuration license (CG) configuration for the cell; and Based on the CG configuration, Unused Transmission Hour-Uplink Control Information (UTO-UCI) is received from the User Equipment (UE). The UTO-UCI includes an N-bit bitmap, where N is a predetermined positive integer. In this N-bit bitmap, N bits are mapped one-to-one to N CG Physical Uplink Shared Channel (PUSCH) timings. Each of the N bits has a first bit value or a second bit value. The first bit value indicates that the UE can transmit CG PUSCH at the corresponding CG PUSCH timing, and the second bit value indicates that the UE does not transmit CG PUSCH at the corresponding CGPUSCH timing. The N CG PUSCH timings do not include CGPUSCH timings that overlap with the inactive period of discontinuous DRX reception in the cell.

14. The BS according to claim 13, wherein, The operation also includes: Send the configuration for the DRX of the cell.

15. The BS according to claim 13, wherein, The UTO-UCI is received via CG PUSCH based on the CG configuration.

Images