Method performed by user equipment, user equipment, processing device, and storage medium, and method performed by base station and base station

By optimizing DCI formats for scheduling PDSCH and PUSCH, the method addresses the complexity of UE operations in 5G systems, improving data speeds and connectivity while ensuring reliable uplink control information transmission.

WO2026235333A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005813
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-05-04
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in achieving very high data speeds, large numbers of connected devices, global connectivity, low latency, reduced energy consumption for IoT devices, ultra-reliable connectivity, and machine learning capabilities, particularly in reducing the implementation complexity of user equipment (UE) related to uplink control information transmission.

Method used

The method involves detecting and transmitting downlink control information (DCI) formats capable of simultaneously scheduling physical downlink shared channels (PDSCH) and physical uplink shared channels (PUSCH), with specific fields in the DCI format determining whether the PUSCH includes uplink shared channel (UL-SCH) data, uplink control channel (UCI), or both, thereby optimizing UE operations.

Benefits of technology

This approach reduces the complexity of UE implementation related to uplink control information transmission, enhancing the performance of 5G systems in terms of data speeds, connectivity, and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005813_12112026_PF_FP_ABST
    Figure KR2026005813_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This UE may: detect a DCI format capable of simultaneously scheduling a PDSCH and a PUSCH; and transmit the PUSCH on the basis of the DCI format. On the basis that a first field in the DCI format includes a first value, the PUSCH may include UL-SCH data and UCI. On the basis that the first field in the DCI format includes a second value, the PUSCH may include the UCI without the UL-SCH data.
Need to check novelty before this filing date? Find Prior Art

Description

A method performed by a user device, a user device, a processing device and a storage medium, and a method performed by a base station and a base station

[0001] This specification relates to a wireless communication system.

[0002] 5G mobile communication systems are a successor technology to LTE (long term evolution) and are new clean-slate type mobile communication systems with characteristics such as high performance, low latency, and high availability. In the case of 5G NR, all available spectrum resources can be utilized, ranging from low frequency bands below 1 GHz to intermediate frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0003] However, there is a growing need to develop a new mobile communication system that goes beyond the limitations of 5G mobile communication and possesses (i) very high data speeds per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) machine learning capabilities.

[0004] One technical objective of this specification is to provide methods and devices for reducing the implementation complexity of user equipment (UE) related to uplink control information transmission.

[0005] The technical problems that this specification aims to solve are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0006] In one aspect of the present specification, a method by user equipment (UE) is provided. In another aspect of the present specification, a UE is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a processing device is provided comprising at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that, when executed, cause the at least one processor to perform operations. The above method or the above operations may include: detecting a downlink control information (DCI) format capable of simultaneously scheduling a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and transmitting the PUSCH based on the DCI format. Based on the first field in the DCI format containing a first value, the PUSCH may include uplink shared channel (UL-SCH) data and uplink control channel (UCI).Based on the fact that the first field in the above DCI format includes a second value, the above PUSCH may include the above UCI without the above UL-SCH data.

[0007] In one aspect of the present specification, a method by means of a base station (BS) is provided. In another aspect of the present specification, a BS is provided comprising: at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The method or the operations may include: transmitting a downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and receiving the PUSCH based on the DCI format. Based on a first field in the DCI format containing a first value, the PUSCH may include uplink shared channel (UL-SCH) data and uplink control channel (UCI). Based on the fact that the first field in the above DCI format includes a second value, the above PUSCH may include the above UCI without the above UL-SCH data.

[0008] In each aspect of the specification, the first field may be an identifier field for DCI formats, a time domain resource allocation (TDRA) field, a modulation and coding scheme (MCS) field for the PUSCH, or a UL-SCH indicator field.

[0009] Based on the identifier field, the first value may be '0' indicating that it is in UL DCI format and the second value may be '1'.

[0010] In each aspect of the specification, based on the fact that the first field is the TDRA field, the first value may be a TDRA entry value associated with PUSCH having UL-SCH data and the second value may be a TDRA entry value associated with PUSCH without UL-SCH data.

[0011] In each aspect of the specification, based on the fact that the first field is the MCS field, the first value may be a value other than a specific value, and the second value may be the specific value.

[0012] In each aspect of the specification, based on the fact that the first field is the UL-SCH indicator field, the first value may be '0' and the second value may be '1'.

[0013] In each aspect of the specification, based on the fact that the first field is the UL-SCH indicator field, the first value may be '1' and the second value may be '0'.

[0014] In each aspect of the present specification, the DCI format may include a frequency domain resource allocation (FDRA) field for the PDSCH. Based on the fact that the FDRA field associated with the PDSCH contains invalid information, the PDSCH may be determined not to be scheduled.

[0015] In each aspect of the present specification, based on the fact that the FDRA field associated with the PDSCH contains invalid information, the PUSCH may be transmitted or received based on the field associated with the PDSCH.

[0016] In each aspect of the present specification, the DCI format may include a TDRA field for the PDSCH. Based on the fact that the TDRA field associated with the PDSCH contains invalid information, the PDSCH may be determined not to be scheduled.

[0017] In each aspect of the present specification, based on the fact that the TDRA field associated with the PDSCH contains invalid information, the PUSCH may be transmitted or received based on the field associated with the PDSCH.

[0018] In each aspect of this specification, the PUSCH may be transmitted or received within a slot. The DCI format may include a PDSCH-to-HARQ_feedback_timing_indicator field, and the slot may be determined or indicated based on the PDSCH-to-HARQ_feedback_timing_indicator field.

[0019] In each aspect of the specification, the DCI format may include an enhanced Type-3 hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook indicator field, and based on the Type-3 HARQ-ACK codebook being triggered through the enhanced Type-3 HARQ-ACK codebook indicator field, the PUSCH may be transmitted or received based on a field associated with the PDSCH within the DCI format.

[0020] In each aspect of the present specification, the DCI may include an enhanced Type-3 HARQ-ACK codebook indicator field, and based on the fact that the Type-3 HARQ-ACK codebook is triggered through the enhanced Type-3 HARQ-ACK codebook indicator field and the FDRA field for the PDSCH includes an invalid value, the PUSCH may be transmitted or received based on the field associated with the PDSCH within the DCI format.

[0021] The above-mentioned problem-solving methods are merely some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person with ordinary knowledge in the relevant technical field based on the detailed description below.

[0022] According to some implementations of this specification, the complexity of implementing user equipment (UE) related to uplink control information transmission can be reduced.

[0023] The effects of this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0024] The attached drawings, included as part of the detailed description to aid in understanding the implementations of this specification, provide examples of the implementations of this specification and describe the implementations of this specification together with the detailed description:

[0025] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification are applied;

[0026] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing the method according to the present specification;

[0027] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification;

[0028] FIG. 4 illustrates an example of a frame structure available in a 3rd generation partnership project (3GPP)-based wireless communication system;

[0029] FIG. 5 illustrates a resource grid of slots;

[0030] FIG. 6 illustrates physical channels used in a 3rd generation partnership project (3GPP)-based communication system, which is an example of a wireless communication system, and the signal transmission / reception process using them;

[0031] FIG. 7 illustrates the process of acquiring system information (SI);

[0032] FIG. 8 illustrates an arbitrary connection process that may be applied to the implementation(s) of the present specification;

[0033] FIG. 9 illustrates an example of time-domain resource allocation of a physical downlink shared channel (PDSCH) by a physical downlink control channel (PDCCH) and an example of time-domain resource allocation of a physical uplink shared channel (PUSCH) by a PDCCH;

[0034] FIG. 10 illustrates the HARQ-ACK transmission / reception process;

[0035] FIG. 11 illustrates an example of scheduling PDSCH and PUSCH through a single DCI according to some implementations of the present specification;

[0036] FIG. 12 illustrates a situation in which PUSCH transmissions collide due to multiple DCIs, each scheduling PDSCH and PUSCH according to some implementations of the present specification;

[0037] FIG. 13 is an example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification;

[0038] FIGS. 14 and 15 are illustrated to explain some implementations of the present specification of transmitting HARQ-ACK information for DG PDSCH via a configured grant-based PUSCH;

[0039] FIGS. 16 and 17 are illustrated to explain some implementations of the present specification of transmitting HARQ-ACK information for SPS PDSCH via an established grant-based PUSCH;

[0040] FIG. 18 is another example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification;

[0041] FIG. 19 illustrates the flow of uplink (UL) signal transmission in a UE according to some implementations of the present specification;

[0042] FIG. 20 illustrates the flow of receiving an uplink (UL) signal in a BS according to some implementations of the present specification.

[0043] Implementations according to this specification are described below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only form in which this specification may be practiced. The detailed description below includes specific details to provide a complete understanding of this specification. However, a person skilled in the art will know that this specification may be practiced without such specific details.

[0044] In some cases, to avoid ambiguity regarding the concepts of this specification, known structures and devices may be omitted or depicted in the form of block diagrams focusing on the core functions of each structure and device. Additionally, the same reference numerals are used to describe identical components throughout this specification.

[0045] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0046] A slash ( / ) or comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0047] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0048] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0049] In addition, terms such as "first," "second," etc. in this specification are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically limited. Accordingly, the first component in one embodiment of this specification may be referred to as the second component in another embodiment, and likewise, the second component in one embodiment may be referred to as the first component in another embodiment.

[0050] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0051] In this specification, information / status / parameters being "configured or pre-configured" may be interpreted as information / status / parameters being provided or pre-provided to the UE through pre-defined signaling from the BS (e.g., system information block (SIB), medium access control (MAC), radio resource control (RRC)). In this specification, information / status / parameters being "defined or pre-defined" may be interpreted as information / status / parameters being known or stored in advance by the BS and the UE without signaling between the BS and the UE.

[0052] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

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

[0054] For the convenience of explanation, the following description assumes that this specification applies to 3GPP-based communication systems, such as LTE and NR. However, the technical features of this specification are not limited thereto. For example, even though the following detailed description is based on a mobile communication system corresponding to a 3GPP LTE / NR system, it may be applied to any other mobile communication system, except for matters specific to 3GPP LTE / NR.

[0055] For terms and technologies used in this specification that are not specifically described, reference may be made to 3GPP-based standard documents, e.g., 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300 and 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.304, 3GPP TS 38.331, etc.

[0056] In the examples of this specification described below, the expression that the device "assumes" may mean that the entity transmitting the channel transmits the channel in accordance with said "assume." It may mean that the entity receiving the channel receives or decodes the channel in a form that conforms to said "assume," under the premise that the channel was transmitted in accordance with said "assume."

[0057] In this specification, UEs may be fixed or mobile and include various devices that communicate with a base station (BS) to transmit and / or receive user data and / or various control information. A UE may be referred to as Terminal Equipment, Mobile Station (MS), Mobile Terminal (MT), User Terminal (UT), Subscribe Station (SS), wireless device, Personal Digital Assistant (PDA), wireless modem, handheld device, etc. Additionally, in this specification, a BS generally refers to a fixed station that communicates with a UE and / or other BSs, and exchanges various data and control information by communicating with a UE and other BSs. A BS may be referred to by other terms such as Advanced Base Station (ABS), Node-B (NB), eNB (evolved-NodeB), Base Transceiver System (BTS), Access Point, Processing Server (PS), etc. In particular, BSs of UTRAN are called Node-Bs, BSs of E-UTRAN are called eNBs, and BSs of new radio access technology networks are called gNBs. For convenience of explanation, BSs will be collectively referred to as BSs regardless of the type or version of the communication technology.

[0058] In this specification, a node refers to a fixed point capable of transmitting or receiving wireless signals by communicating with a UE. Various types of BSs may be used as nodes regardless of their designation. For example, a BS, NB, eNB, pico-cell eNB (PeNB), home eNB (HeNB), relay, repeater, etc., may serve as a node. Additionally, a node does not have to be a BS. For example, it may be a radio remote head (RRH) or a radio remote unit (RRU). RRHs, RRUs, etc. generally have a power level lower than that of a BS. Since an RRH or RRU (or RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between an RRH / RRU and a BS can be performed more smoothly compared to cooperative communication between BSs connected via wireless lines. At least one antenna is installed at a node. This antenna may refer to a physical antenna, an antenna port, a virtual antenna, or an antenna group. Nodes are also referred to as points.

[0059] In this specification, the term "cell" refers to a specific geographical area where one or more nodes provide communication services. Accordingly, in this specification, communicating with a specific cell may mean communicating with a BS or node that provides communication services to said specific cell. Furthermore, the downlink / uplink signals of a specific cell refer to downlink / uplink signals from to or to the BS or node that provides communication services to said specific cell. A cell that provides uplink / downlink communication services to a UE is specifically referred to as a serving cell. Additionally, the channel state / quality of a specific cell refers to the channel state / quality of the channel or communication link formed between the BS or node providing communication services to said specific cell and the UE. In a 3GPP-based communication system, a UE can measure the downlink channel state from a specific node using the CRS(s) transmitted by the antenna port(s) of the specific node over the CRS (Cell-specific Reference Signal) resource assigned to the specific node and / or the CSI-RS(s) transmitted over the CSI-RS (Channel State Information Reference Signal) resource.

[0060] Meanwhile, 3GPP-based communication systems use the concept of a cell to manage wireless resources, and a cell associated with wireless resources is distinguished from a cell in a geographical area.

[0061] A “cell” of a geographical area can be understood as the coverage over which a node can provide services using a carrier wave, and a “cell” of a wireless resource is associated with the bandwidth (BW), which is the frequency range configured by said carrier wave. Since downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a valid signal can be received from a UE, depend on the carrier wave carrying the signal, the coverage of a node is also associated with the coverage of the “cell” of the wireless resource used by said node. Therefore, the term “cell” can be used to refer sometimes to the coverage of a service by a node, sometimes to a wireless resource, and sometimes to the range over which a signal using said wireless resource can reach with effective strength.

[0062] Meanwhile, 3GPP communication standards use the concept of a cell to manage radio resources. A "cell" associated with radio resources is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), that is, a combination of a DL component carrier (CC) and a UL CC. A cell can be configured as a DL resource alone or as a combination of a DL resource and a UL resource. Where carrier aggregation is supported, the linkage between the carrier frequency of a DL resource (or DL ​​CC) and the carrier frequency of a UL resource (or UL CC) can be indicated by system information. For example, the combination of DL resources and UL resources can be indicated by a System Information Block Type 2 (SIB2) linkage. Here, the carrier frequency may be equal to or different from the center frequency of each cell or CC. When Carrier Aggregation (CA) is established, the UE has only one Radio Resource Control (RRC) connection with the network. One serving cell provides Non-Access Stratum (NAS) mobility information during RRC establishment / re-establishment / handover, and one serving cell provides security input during RRC re-establishment / handover. This cell is called a primary cell (Pcell). A Pcell is a cell operating on the primary frequency where the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure.Depending on the UE capability, secondary cells (Scells) can be configured to form a set of serving cells together with Pcells. Scells can be configured after a Radio Resource Control (RRC) connection is established and are cells that provide additional radio resources in addition to the resources of special cells (SpCells). The carrier corresponding to a Pcell in the downlink is called the Downlink Primary CC (DL PCC), and the carrier corresponding to a Pcell in the uplink is called the UL Primary CC (UL PCC). The carrier corresponding to an Scell ​​in the downlink is called the DL Secondary CC (DL SCC), and the carrier corresponding to the Scell ​​in the uplink is called the UL Secondary CC (UL SCC).

[0063] In a UE where CA is configured and DC is not configured, a Pcell PUCCH group (also referred to as a primary PUCCH group) consisting of a Pcell and zero or more Scells, and an Scell ​​PUCCH group (also referred to as a secondary PUCCH group) consisting only of Scell(s) may be configured. In the case of an Scell, an Scell ​​(hereinafter referred to as a PUCCH Scell) to which a PUCCH associated with that cell is transmitted may be configured. An Scell ​​designated as a PUCCH Scell ​​belongs to the Scell ​​PUCCH group (i.e., secondary PUCCH group), and the PUCCH transmission of the associated UCI is performed on the said PUCCH Scell; an Scell ​​that is not designated as a PUCCH Scell, or an Scell ​​in which the cell designated as a PUCCH transmission cell is a Pcell, belongs to the Pcell PUCCH group (i.e., primary PUCCH group), and the PUCCH transmission of the associated UCI is performed on the said Pcell. In the following, if the UE is configured with an SCG and some implementations of this specification related to PUCCH apply to the SCG, the primary cell may refer to the PSCell of the SCG. If the UE is configured with a PUCCH Scell ​​and some implementations of this specification related to PUCCH apply to a secondary PUCCH group, the primary cell may refer to the PUCCH Scell ​​of the secondary PUCCH group.

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

[0065] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from upper layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, while the reference signal and synchronization signal are defined as downlink physical signals. The reference signal (RS), also referred to as a pilot, refers to a signal of a specific, predefined waveform known to both the BS and the UE. For example, the demodulation reference signal (DMRS), channel state information RS (CSI-RS), and positioning reference signal (PRS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from upper layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from upper layers.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), and physical random access channel (PRACH) are defined as uplink physical channels, and the demodulation reference signal (DMRS) for uplink control / data signals and the sounding reference signal (SRS) used for uplink channel measurement are defined.

[0066] In this specification, PDCCH (Physical Downlink Control Channel) refers to a set of time-frequency resources (e.g., resource elements (REs)) carrying DCI (Downlink Control Information), and PDSCH (Physical Downlink Shared Channel) refers to a set of time-frequency resources carrying downlink data. Additionally, PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), and PRACH (Physical Random Access Channel) respectively refer to sets of time-frequency resources carrying UCI (Uplink Control Information), uplink data, and random access signals. In the following, the expression that a user device transmits / receives PUCCH / PUSCH / PRACH is used to mean that the user device transmits / receives uplink control information / uplink data / random access signals on or through PUCCH / PUSCH / PRACH, respectively. In addition, the expression that BS transmits / receives PBCH / PDCCH / PDSCH is used with the same meaning as transmitting broadcast information / downlink control information / downlink data on or through PBCH / PDCCH / PDSCH, respectively.

[0067] In this specification, radio resources (e.g., time-frequency resources) scheduled or set for a UE by a BS for the transmission or reception of PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.

[0068] Since the communication device receives a synchronization signal (SS), DMRS, CSI-RS, PRS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on the cell, it is not possible to selectively receive only radio signals containing only a specific physical channel or a specific physical signal through the RF receiver, or to selectively receive only radio signals excluding only a specific physical channel or a specific physical signal through the RF receiver. In actual operation, the communication device first receives radio signals on the cell through the RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and uses one or more processors to decode the physical signals and / or physical channels within the baseband signals. Accordingly, in some implementations of this specification, not receiving a physical signal and / or physical channel may actually mean that the communication device does not receive wireless signals containing the physical signal and / or physical channel at all, but rather does not attempt to recover the physical signal and / or physical channel from the wireless signals, for example, not attempt to decode the physical signal and / or physical channel.

[0069] As more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, Massive Mobile Telecommunications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the key issues to be considered in next-generation communication. In addition, communication system designs that consider reliability and latency-sensitive services / UEs are being discussed. Accordingly, the introduction of next-generation RATs that incorporate advanced mobile broadband communication, Massive MTC, and Ultra-Reliable and Low Latency Communication (URLC) is being discussed. Currently, 3GPP is conducting studies on next-generation mobile communication systems following the EPC. For convenience, this specification refers to the technology as New RAT (NR) or 5G RAT, and systems that use or support NR are referred to as NR systems.

[0070] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification apply. Referring to FIG. 1, the communication system (1) to which the present specification applies includes a wireless device, a BS, and a network. Here, a wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, a wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, a vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, vehicles may include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, BS and networks may be implemented as wireless devices, and specific wireless devices may operate as BS / network nodes to other wireless devices.

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

[0072] Wireless communication / connection (150a, 150b) may be established between wireless devices (100a~100f) / BS (200) and BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection may be established through uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication) using various wireless access technologies (e.g., 5G NR). Through the wireless communication / connection (150a, 150b), wireless devices and BS / wireless devices may transmit / receive wireless signals to / from each other. To this end, based on various proposals of the present specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0073] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing the method according to the present specification. Referring to FIG. 2, a first wireless device (100) and a second wireless device (200) can transmit and / or receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), BS (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 1.

[0074] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the functions, procedures and / or methods described / suggested below. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). Memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the procedures and / or methods described / suggested below. Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (Radio Frequency) unit. In this specification, a wireless device may mean a communication modem / circuit / chip.

[0075] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the functions, procedures and / or methods described / suggested below. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the procedures and / or methods described / suggested below. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, a wireless device may mean a communication modem / circuit / chip.

[0076] The wireless communication technology implemented in the wireless device (100, 200) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) with consideration for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

[0077] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDU) and / or one or more service data units (SDU) according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification.

[0078] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, proposals and / or methods disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The functions, procedures, proposals and / or methods disclosed in this specification may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.

[0079] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0080] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification through one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0081] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification. Referring to FIG. 3, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 2 and may be composed of various elements, components, units / parts, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to the outside (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from the outside (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).

[0082] The additional element (140) may be configured in various ways depending on the type of wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 1, 100a), a vehicle (Fig. 1, 100b-1, 100b-2), an XR device (Fig. 1, 100c), a portable device (Fig. 1, 100d), a home appliance (Fig. 1, 100e), an IoT device (Fig. 1, 100f), a UE for digital broadcasting, a holographic device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 1, 400), a BS (Fig. 1, 200), a network node, etc. Depending on the use—e.g., service—the wireless device may be movable or used in a fixed location.

[0083] In FIG. 3, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least a portion may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, transitory memory, non-transitory memory and / or a combination thereof.

[0084] In this specification, at least one memory (e.g., 104 or 204) may store instructions or programs, and said instructions or programs may, when executed, cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.

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

[0086] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory connectable to said at least one processor. said at least one computer memory may store instructions or programs, and said instructions or programs, when executed, may cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.

[0087] In this specification, a computer program may include program code stored on at least one computer-readable (non-transient) storage medium and, when executed, perform operations according to some implementations of this specification or cause at least one processor to perform operations according to some implementations of this specification. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-transient) storage medium.

[0088] A communication device of this specification comprises at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to the examples(s) of this specification described below.

[0089] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.

[0090] The structure of the frame in Fig. 4 is merely an example, and the number of subframes, slots, and symbols in the frame can be varied. In an NR system, OFDM numerology (e.g., subcarrier spacing (SCS)) may be configured differently among multiple cells aggregated to a single UE. Accordingly, the (absolute time) duration of a time resource (e.g., subframe, slot, or transmission time interval (TTI)) consisting of the same number of symbols may be configured differently among the aggregated cells. Here, symbols may include OFDM symbols (or cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) symbols) and SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols). In this specification, symbols, OFDM-based symbols, OFDM symbols, CP-OFDM symbols, and DFT-s-OFDM Symbols can be substituted for each other.

[0091] Referring to Fig. 4, uplink and downlink transmissions in an NR system are organized into frames. Each frame is T f = (△f max *N f / 100)*T c = It has a duration of 10 ms and is divided into two half-frames, each with a duration of 5 ms. Here, T is the basic time unit for NR. c = 1 / (△fmax *N f ) and, △f max = 480*10 3 It is Hz, and N f = 4096. For reference, T is the standard time unit for LTE. s = 1 / (△f ref *N f,ref ) and, △f ref = 15*10 3 It is Hz, and N f,ref =2048. T c Wow T s is a constant κ = T s / T c It has a relationship of = 64. Each half-frame consists of 5 subframes, and the period T of a single subframe (SF) sf is 1ms. Subframes are further divided into slots, and the number of slots within a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on a cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, while for an extended CP, each slot consists of 12 OFDM symbols. The above numerology is an exponentially scalable subcarrier spacing △f = 2 u It depends on 15 kHz. The following table shows the subcarrier spacing △f = 2 for a normalized CP. u *Number of OFDM symbols per slot according to 15 kHz (N slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot It represents ).

[0092]

[0093] The following table shows the subcarrier spacing △f = 2 for extended CP.u This shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe according to *15 kHz.

[0094]

[0095] For a subcarrier interval setting u, the slots are arranged in increasing order n within the subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - 1} is numbered.

[0096] FIG. 5 illustrates a resource grid of a slot. A slot contains multiple (e.g., 14 or 12) symbols in the time domain. For each numerator (e.g., subcarrier interval) and carrier, a common resource block (CRB) N indicated by upper-layer signaling (e.g., radio resource control (RRC) signaling) start,u grid Starting from,N size,u grid,x *N RB sc individual subcarriers and N subframe,u symb A resource grid of N OFDM symbols is defined. Here, N size,u grid,x is the number of resource blocks (RB) in the resource grid, and the subscript x is DL for downlinks and UL for uplinks. RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB scis typically 12. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). Carrier bandwidth N for subcarrier spacing configuration u. size,u grid This is given to the UE by upper-layer parameters (e.g., RRC parameters) from the network. Each element within the resource grid for antenna port p and subcarrier spacing u is referred to as a resource element (RE), and one complex symbol can be mapped to each resource element. Each resource element within the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In an NR system, RBs are defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs can be classified into Common Resource Blocks (CRBs) and Physical Resource Blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing u. The center of subcarrier 0 of CRB 0 for subcarrier spacing u coincides with 'Point A', which is the common reference point for the resource block grids. The PRBs for the subcarrier spacing setting u are defined within the bandwidth part (BWP), and range from 0 to N size,u BWP,i Numbered up to -1, where i is the number of the above bandwidth part. Common resource block n u CRB and physical resource block n within bandwidth part i PRB The relationships between them are as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,iis a common resource block where the above bandwidth part starts relative to CRB 0. A BWP contains multiple consecutive RBs in the frequency domain. For example, a BWP is a given numerator u within a BWP i on a given carrier. i It is a subset of contiguous CRBs defined for. A UE may be configured to have one or more BWPs on a given component carrier. On the downlink, the UE may be configured with, for example, up to four BWPs, and only one DL BWP is active at any given time. The UE does not expect to receive PDSCH, PDCCH, or CSI-RS (except for radio resource management) outside of the active BWP. On the uplink, the UE may be configured with, for example, up to four BWPs, and only one UL BWP is active at any given time. The UE does not transmit PUSCH or PUCCH outside of the active BWP.

[0097] For each serving cell within a set of DL BWPs or UL BWPs, the network establishes at least an initial DL BWP and one initial UL BWP (if the serving cell is configured with an uplink) or two initial UL BWPs (if using a supplementary uplink). The network may also establish additional ULs and DL BWPs for the serving cell. For each DL BWP or UL BWP, the UE is provided with the following parameters for the serving cell: i) subcarrier spacing, ii) circular prefix, iii) N start BWP Assuming = 275, offset RB set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates as the resource indicator value (RIV). start BWP =O carrier +RBstart and the number of contiguous RBs N size BWP =L RB , and O provided by the RRC parameter offsetToCarrier for the subcarrier spacing carrier ; Index within the set of the above DL BWPs or UL BWPs; set of BWP-common parameters and set of BWP-exclusive parameters.

[0098] Switching between configured BWPs may occur using RRC signaling, DCI, an inactivity timer, or upon the initiation of a random connection. If an inactivity timer is configured for a serving cell, the expiration of the inactivity timer associated with said serving cell switches the active BWP to the default BWP configured by the network.

[0099] Virtual resource blocks (VRBs) are defined within the bandwidth part and range from 0 to N size,u BWP,i Numbered up to -1, where i is the number of the above bandwidth part. VRBs are mapped to physical resource blocks (PRBs) according to interleaved or non-interleaved mapping. In some implementations, for non-interleaved VRB-to-PRB mapping, VRB n can be mapped to PRB n.

[0100] NR frequency bands are defined as two types of frequency ranges, FR1 and FR2, where FR2 is also referred to as millimeter wave (mmW). The following table illustrates the frequency ranges in which NR can operate.

[0101]

[0102] Figure 7 illustrates the system information (SI) acquisition process. A UE can acquire AS- / NAS- information through the SI acquisition process. The SI acquisition process can be applied to UEs in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. RRC_CONNECTED is a state in which the UE has established an RRC connection with the network. RRC_IDLE is a state in which the UE is not registered with a specific cell and has not received the access stratum (AS) context and other information received from the network. RRC_INACTIVE is a state in which the UE remains in CM-CONNECTED, a state in which it has a signaling connection with the core network for connection management (CM), and can move within an area set by the RAN (e.g., BS(s)) without notifying the radio access network (RAN). CM_CONNECTED is a state in which the UE has a non-access stratum (NAS) signaling connection with the core network, and CM_IDLE is a state in which the UE has no NAS signaling.

[0103] In 3GPP-based systems, SI can be divided into a master information block (MIB) and multiple system information blocks (SIBs). The MIB and multiple SIBs can be further divided into minimum SI and other SI. Here, the minimum SI may consist of an MIB and SystemInformationBlock1 (SIB1), and includes basic information required for initial connection and information for obtaining other SI. Here, SIB1 may be referred to as remaining minimum system information (RMSI). For details, refer to the following.

[0104] - The MIB is always transmitted over a BCH with a periododicity of 80 ms and repetitions created within 80 ms. The MIB contains information / parameters related to SIB1 reception and is transmitted via the SSB's PBCH. During initial cell selection, the UE assumes that half-frames containing the SSB(s) are repeated with a period of 20 ms. In a 5G system, the MIB contains the common control resource set (CORESET), the common search space, the pdcch-ConfigSIB1 field used to determine necessary PDCCH parameters, and k, which represents the frequency domain offset between the SSB and the overall resource block grid in units of the number of subcarriers. SSBIt may include the ssb-SubcarrierOffset field corresponding to, SIB1, Msg2 / Msg4 for initial connection, the subCarrierSpacingCommon field regarding the subcarrier spacing for paging and broadcast system information messages, and the dmrs-TypeA-Position field regarding the position of the (first) DM-RS for the downlink (e.g., PDSCH) and uplink (e.g., PUSCH). Based on the MIB, the UE can determine whether a control resource set (CORESET) (e.g., CORESET#0) exists for the Type0-PDSCH common search space. For example, k SSB <= 23 (for FR1) or k SSB If <= 11 (for FR2), the UE can determine that a CORESET exists for the Type0-PDCCH common search space. If, k SSB > 23 (for FR1) or k SSB If > 11 (for FR2), the UE may determine that there is no CORESET for the Type0-PDCCH common seek space. The Type0-PDCCH common seek space is a type of PDCCH seek space used to transmit PDCCHs that schedule SI messages. If a Type0-PDCCH common seek space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbol(s) that constitute the CORESET, and (ii) the PDCCH time (i.e., the time domain location for receiving the PDCCH), based on information within the MIB (e.g., pdcch-ConfigSIB1). If a Type0-PDCCH common seek space does not exist, pdcch-ConfigSIB1 provides information regarding the frequency locations where SSB / SIB1 exists and the frequency ranges where SSB / SIB1 does not exist.

[0105] - SIB1 is transmitted over a downlink shared channel (DL-SCH) with a periododicity of 160 ms and a variable transmission repetition period within 160 ms. The default transmission repetition period of SIB1 is 20 ms, but the actual transmission repetition period may vary depending on the network implementation. SIB1 contains information regarding the availability and scheduling (e.g., transmission period, SI-window size) of the remaining SIBs (hereinafter SIBx, where x is an integer greater than or equal to 2). For example, SIB1 can indicate whether SIBx is broadcast periodically or provided on-demand by a UE's request. If SIBx is provided on-demand, SIB1 may contain information necessary for the UE to perform an SI request. SIB1 is a cell-specific SIB. The PDCCH scheduling SIB1 is transmitted through the Type0-PDCCH common seek space, and SIB1 is transmitted through the PDSCH directed by the said PDCCH.

[0106] - SIBx is included in SI messages and transmitted via PDSCH. Each SI message is transmitted within a time window (i.e., SI window) that occurs periodically according to SI scheduling information provided by SIB1.

[0107] FIG. 8 illustrates a random connection process that can be applied to the implementation(s) of the present specification. In particular, FIG. 8(a) illustrates a four-step random connection process, and FIG. 8(b) illustrates a two-step random connection process.

[0108] The random access process can be used for various purposes, such as initial access, uplink adjustment, resource allocation, handover, reconfiguration after a wireless link failure, and location measurement. Random access processes are classified into contention-based and dedicated (i.e., non-contention-based) processes. Contention-based random access processes are generally used for initial access, while dedicated random access processes are used for handover, when downlink data reaches the network, and when reconfiguring uplink synchronization for location measurement. In a contention-based random access process, the UE randomly selects a random access (RA) preamble. Therefore, it is possible for multiple UEs to transmit the same RA preamble simultaneously, which necessitates a subsequent contention resolution process. In contrast, in a dedicated random access process, the UE uses an RA preamble uniquely assigned to it by the BS. Consequently, the UE can perform the random access process without conflicts with other UEs.

[0109] Referring to FIG. 8(a), the contention-based random access process includes the following four steps. Hereinafter, the messages transmitted in steps 1 through 4 may be referred to as Msg1 through Msg4, respectively.

[0110] - Step 1: The UE transmits the RA preamble via PRACH.

[0111] - Step 2: The UE receives a random access response (RAR) from the BS via PDSCH.

[0112] - Step 3: The UE transmits UL data to the BS via PUSCH based on RAR. Here, the UL data includes Layer 2 and / or Layer 3 messages.

[0113] - Step 4: The UE receives a contention resolution message from the BS via PDSCH.

[0114] The UE can receive information regarding random access from the BS through system information. For example, information regarding random access channel (RACH) times associated with SSBs on the cell may be provided through system information. The UE can select an SSB among those received on the cell for which the reference signal received power (RSRP) measured based on the SSB exceeds a threshold, and transmit an RA preamble through the PRACH associated with the selected SSB. For example, if random access is required, the UE transmits Msg1 (e.g., preamble) to the BS on the PRACH. The BS can distinguish each random access preamble through the time / frequency resource (e.g., RACH time) at which the random access preamble was transmitted and the random access preamble index (PI). When the BS receives a random access preamble from the UE, the BS transmits a RAR message to the UE on the PDSCH. To receive a RAR message, the UE monitors a L1 / L2 control channel (PDCCH) masked with a cyclic redundancy check (CRC) by a Random Access-RnTI (RA-RNTI) containing scheduling information for the RAR message within a preset time window (e.g., ra-ResponseWindow). If scheduling information is received through the PDCCH masked with the RA-RNTI, the UE may receive a RAR message from the PDCCH indicated by the scheduling information. Subsequently, the UE determines whether there is a RAR for itself in the RAR message. Whether a RAR for itself exists can be determined by whether a Random Access preamble ID (RAPID) exists for the preamble transmitted by the UE. The index of the preamble transmitted by the UE and the RAPID may be the same.A RAR includes a corresponding random access preamble index, timing offset information for UL synchronization (e.g., a timing advance command (TAC)), UL scheduling information for sending Msg3 (e.g., a UL grant), and temporary UE identification information (e.g., Temporary-C-RNTI, TC-RNTI). Upon receiving the RAR, the UE sends Msg3 via PUSCH according to the UL scheduling information and timing offset values ​​within the RAR. Msg3 may include the UE's ID (or the UE's global ID). Additionally, Msg3 may include information related to an RRC connection request for initial access to the network (e.g., an RRCSetupRequest message). After receiving Msg3, the BS sends Msg4, a contention resolution message, to the UE. If the UE receives the contention resolution message and the contention is successfully resolved, TC-RNTI is changed to C-RNTI. Msg4 includes the UE's ID and / or It may include information related to the RRC connection (e.g., RRCSetup message). If the information transmitted via Msg3 does not match the information received via Msg4, or if Msg4 is not received for a certain period of time, the UE may report that the contention resolution failed and retransmit Msg3.

[0115] Meanwhile, the dedicated random access process includes the following three steps. Hereinafter, the messages transmitted in steps 0 to 2 may be referred to as Msg0 to Msg2, respectively. The dedicated random access process may be triggered by the UE by the BS using a PDCCH (hereinafter referred to as the PDCCH order) for commanding the transmission of an RA preamble.

[0116] - Step 0: BS assigns the RA preamble to the UE via dedicated signaling.

[0117] - Step 1: The UE transmits the RA preamble via PRACH.

[0118] - Step 2: The UE receives the RAR via the PDSCH from the BS.

[0119] The operations of steps 1 to 2 of a dedicated random access process may be the same as steps 1 to 2 of a contention-based random access process.

[0120] In NR systems, lower latency than in existing systems may be required. Additionally, a four-stage random access process may not be desirable, particularly for latency-sensitive services such as URLLC. A low-latency random access process may be required within various scenarios of NR systems. When the implementation(s) of this specification are performed with a random access process, to reduce latency in the random access process, the implementation(s) of this specification may be performed with the following two-stage random access process.

[0121] Referring to FIG. 8(b), the two-stage random access process may consist of two stages: the transmission of MsgA from the UE to the BS and the transmission of MsgB from the BS to the UE. The transmission of MsgA may include the transmission of an RA preamble via PRACH and the transmission of a UL payload via PUSCH. In the transmission of MsgA, PRACH and PUSCH may be transmitted using time division multiplexing (TDM). Alternatively, in the transmission of MsgA, PRACH and PUSCH may be transmitted using frequency division multiplexing (FDM).

[0122] A BS that receives MsgA may send MsgB to a UE. MsgB may include a RAR for said UE.

[0123] A message related to an RRC connection request (e.g., RRCSetupRequest message) requesting to establish a connection between the RRC layer of the BS and the RRC layer of the UE may be transmitted by being included in the payload of MsgA. In this case, MsgB may be used to transmit RRC connection-related information (e.g., RRCSetup message). Alternatively, the RRC connection request message (e.g., RRCSetupRequest message) may be transmitted via PUSCH transmitted based on a UL grant within MsgB. In this case, the RRC connection-related information (e.g., RRCSetup message) related to the RRC connection request may be transmitted via PDSCH associated with said PUSCH transmission after the PUSCH transmission based on MsgB.

[0124] Below, physical channels that can be used in 3GPP-based wireless communication systems are described in more detail.

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

[0126] The scheduling of a PDCCH on one serving cell to a PDSCH or PUSCH on another serving cell is called cross-carrier scheduling. Cross-carrier scheduling using a carrier indicator field (CIF) may allow a PDCCH on a serving cell to schedule resources on another serving cell. Meanwhile, the scheduling of a PDSCH or PUSCH on a serving cell to a serving cell is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the BS may provide the UE with information regarding the cell scheduling said cell. For example, the BS may provide the UE with whether the serving cell is scheduled by a PDCCH on another (scheduling) cell or by said serving cell, and if said serving cell is scheduled by another (scheduling) cell, which cell signals downlink assignments and uplink grants for said serving cell. In this specification, a cell carrying a PDCCH is referred to as a scheduling cell, and a cell in which the transmission of a PUSCH or PDSCH is scheduled by a DCI included in the PDCCH, that is, a cell carrying a PUSCH or PDSCH scheduled by the PDCCH, is referred to as a scheduled cell.

[0127] PDSCH is a physical layer DL channel for DL ​​data transport. PDSCH carries downlink data (e.g., DL-SCH transport blocks) and applies modulation methods such as QPSK (Quadrature Phase Shift Keying), 16 QAM (Quadrature Amplitude Modulation), 64 QAM, and 256 QAM. Codewords are generated by encoding transport blocks (TB). PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to a radio resource along with DMRS to generate an OFDM symbol signal, which is then transmitted through the corresponding antenna port.

[0128] The UE must have uplink resources available to it for UL-SCH data transmission and downlink resources available to it for DL-SCH data reception. Uplink resources and downlink resources are assigned to the UE through resource allocation by the BS. Resource allocation may include time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). In this specification, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment. Uplink grant is dynamically received by the UE on the PDCCH or within the RAR, or is semi-persistently set to the UE by RRC signaling from the BS. Downlink assignment is dynamically received by the UE on the PDCCH, or is semi-persistently set to the UE by RRC signaling from the BS.

[0129] In UL, the BS can dynamically allocate uplink resources to the UE via PDCCH(s) addressed to a cell radio network temporary Identifier (C-RNTI). The UE monitors the PDCCH(s) to find available uplink grant(s) for UL transmission. Additionally, the BS can allocate uplink resources to the UE using configured grants. Two types of configured grants, Type 1 and Type 2, may be used. In the case of Type 1, the BS directly provides the configured uplink grant (including periodicity) via RRC signaling. In the case of Type 2, the BS sets the period of the RRC-configured uplink grant via RRC signaling and can signal and activate or deactivate the configured uplink grant via a PDCCH addressed to a configured scheduling RNTI (CS-RNTI). For example, in the case of Type 2, the PDCCH addressed by CS-RNTI indicates that the corresponding uplink grant may be implicitly reused according to the period set by RRC signaling until it is deactivated.

[0130] In DL, the BS can dynamically allocate downlink resources to the UE via PDCCH(s) addressed by C-RNTI. The UE monitors the PDCCH(s) to identify potential downlink assignments. Additionally, the BS can allocate downlink resources to the UE using semi-persistent scheduling (SPS). The BS can set the period of the configured downlink assignments via RRC signaling and signal, enable, or disable the configured downlink assignments via PDCCHs addressed by CS-RNTI. For example, a PDCCH addressed by CS-RNTI indicates that the corresponding downlink assignment may be implicitly reused according to the period set by RRC signaling until it is disabled.

[0131] In this specification, a PDSCH based on DL SPS is referred to as SPS PDSCH, a PUSCH based on a UL configured grant (CG) is referred to as CG PUSCH, a PDSCH dynamically scheduled by a DCI carried by a PDCCH is referred to as DG PDSCH, and a PUSCH dynamically scheduled by a DCI carried by a PDCCH is referred to as DG PUSCH.

[0132] Figure 9 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.

[0133] The DCI carried by PDCCH to schedule PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, said TDRA field provides a value m for row index m+1 to the allocation table for PDSCH or PUSCH. A predefined default PDSCH time domain assignment is applied as the allocation table for PDSCH, or a PDSCH time domain resource assignment table set by BS via RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for PDSCH. A predefined default PUSCH time domain assignment is applied as the allocation table for PUSCH, or a PUSCH time domain resource assignment table set by BS via RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for PUSCH. The PDSCH time domain resource allocation table to be applied and / or the PUSCH time domain resource allocation table to be applied may be determined according to fixed / predefined rules (e.g., see 3GPP TS 38.214).

[0134] In the PDSCH time domain resource settings, each indexed row defines the DL allocation-to-PDSCH slot offset K0, the start and length indicator value SLIV (or directly the starting position of the PDSCH within the slot (e.g., start symbol index S) and the allocation length (e.g., number of symbols L)), and the PDSCH mapping type. In the PUSCH time domain resource settings, each indexed row defines the UL grant-to-PUSCH slot offset K2, the starting position of the PUSCH within the slot (e.g., start symbol index S) and the allocation length (e.g., number of symbols L), and the PUSCH mapping type. K0 for PDSCH or K2 for PUSCH indicates the difference between the slot containing the PDSCH and the slot containing the PDSCH or PUSCH corresponding to said PDSCH. SLIV is a joint indicator of the starting symbol S relative to the start of the slot containing the PDSCH or PUSCH and the number of consecutive symbols L counted from said symbol S. For PDSCH / PUSCH mapping types, there are two mapping types: one is mapping type A and the other is mapping type B. In the case of PDSCH / PUSCH mapping type A, the demodulation reference signal (DMRS) is mapped to the PDSCH / PUSCH resource based on the start of the slot, and depending on other DMRS parameters, one or two symbols from the PDSCH / PUSCH resource may be used as DMRS symbol(s). For example, in the case of PDSCH / PUSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot according to RRC signaling. In the case of PDSCH / PUSCH mapping type B, the DMRS is mapped based on the first OFDM symbol of the PDSCH / PUSCH resource, and depending on other DMRS parameters, one or two symbols starting from the first symbol of the PDSCH / PUSCH resource may be used as DMRS symbol(s).For example, in the case of PDSCH / PUSCH mapping type B, DMRS is located at the first symbol allocated for PDSCH / PUSCH. In this specification, PDSCH / PUSCH mapping types may be referred to as mapping types or DMRS mapping types. For example, in this specification, 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.

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

[0136] A control resource set (CORESET), which is a set of time-frequency resources that allows the UE to monitor a PDCCH, may be defined and / or configured. The CORESET consists of a set of physical resource blocks (PRBs) with a duration of one to three OFDM symbols. The PRBs constituting the CORESET and the CORESET duration may be provided to the UE via upper-layer (e.g., RRC) signaling. Within the configured CORESET(s), a set of PDCCH candidates is monitored according to the corresponding search space sets. In this specification, monitoring implies decoding (also known as blind decoding) each PDCCH candidate according to the monitored DCI formats. The master information block (MIB) on the PBCH provides the UE with parameters for monitoring the PDCCH (e.g., CORESET#0 configuration) to schedule the PDCCH carrying the system information block (SIB1). The PBCH may also indicate that there is no associated SIB1; in this case, the UE may be instructed on a frequency range where it can assume there is no SSB associated with SSB1, as well as other frequencies to search for the SSB associated with SIB1. At least CORESET#0, which is the CORESET for scheduling SIB1, can be set via MIB or dedicated RRC signaling.

[0137] One or more CORESETs can be configured for the UE, and multiple CORESETs can overlap in the time / frequency domain.

[0138] The set of PDCCH candidates monitored by the UE is defined in terms of PDCCH search space sets. A search space set can be a common search space (CSS) set or a UE-specific search space (USS) set. Each CORESET setting is associated with one or more search space sets, and each search space set is associated with one CORESET setting.

[0139] A set of PDCCH candidates can be monitored in one or more CORESETs on an active DL BWP on each active serving cell where PDCCH monitoring is configured, wherein monitoring implies receiving each PDCCH candidate and decoding it according to the monitored DCI formats.

[0140] SS sets can be configured via system information (e.g., MIB) or UE-specific upper layer (e.g., RRC) signaling. Each DL BWP in a serving cell may have up to S (e.g., 10) SS sets configured. For example, the following parameters / information may be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration may be associated with one or more SS sets.

[0141] -searchSpaceId: Represents the ID of the SS set.

[0142] -controlResourceSetId: Represents the CORESET associated with the SS set.

[0143] -monitoringSlotPeriodicityAndOffset: Represents the PDCCH monitoring period interval (in slots) and the PDCCH monitoring interval offset (in slots).

[0144] -monitoringSymbolsWithinSlot: Represents the first OFDMA symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is enabled. It is indicated by a bitmap, where each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDMA symbol within the slot. The OFDMA symbol(s) corresponding to bit(s) with a bit value of 1 correspond to the first symbol(s) of the CORESET within the slot.

[0145] -nrofCandidates: AL={1, 2, 4, 8, 16} represents the number of star PDCCH candidates (e.g., one of 0, 1, 2, 3, 4, 5, 6, 8).

[0146] -searchSpaceType: Indicates whether the SS type is CSS or USS.

[0147] - DCI Format: Indicates the DCI format of the PDCCH candidate.

[0148] Based on the CORESET / SS set configuration, the UE can monitor PDCCH candidates from one or more SS sets within the slot. The occasion (e.g., time / frequency resources) when PDCCH candidates must be monitored is defined as a PDCCH (monitoring) time. One or more PDCCH (monitoring) times can be configured within the slot.

[0149] FIG. 10 illustrates the HARQ-ACK transmission / reception process. Referring to FIG. 10, the UE can detect a PDCCH in slot n. Subsequently, the UE can receive a PDSCH in slot n+K0 according to the scheduling information received via the PDCCH in slot n, and then transmit a UCI via a PUCCH in slot n+K1. Here, the UCI includes a HARQ-ACK response to the PDSCH. In some scenarios, PUCCH feedback based on a slot consisting of 14 OFDM symbols may be performed, as well as PUCCH feedback based on a subslot consisting of fewer than 14 OFDM symbols (e.g., 2 to 7).

[0150] The DCI carried by the PDCCH scheduling the PDSCH (e.g., DCI format 1_0, DCI format 1_1) may contain the following information.

[0151] - Frequency Domain Resource Assignment (FDRA): Represents the set of RBs assigned to PDSCH.

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

[0153] - PDSCH-to-HARQ_feedback timing indicator: Represents K1.

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

[0155] In this specification, a HARQ-ACK payload consisting of HARQ-ACK bit(s) for one or more PDSCHs may be referred to as a HARQ-ACK codebook. Depending on how the HARQ-ACK payload is determined, a HARQ-ACK codebook may be distinguished into i) a semi-static HARQ-ACK codebook, ii) a dynamic HARQ-ACK codebook, and iii) a HARQ process-based HARQ-ACK codebook.

[0156] In the case of a semi-static HARQ-ACK codebook, parameters related to the HARQ-ACK payload size to be reported by the UE are semi-statically set by (UE-specific) upper layer (e.g., RRC) signals. For example, the HARQ-ACK payload size of a semi-static HARQ-ACK codebook, the (maximum) HARQ-ACK payload (size) transmitted through a single PUCCH within a single slot, can be determined based on the number of HARQ-ACK bits corresponding to the combination of all DL carriers (i.e., DL serving cells) set for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) where the HARQ-ACK transmission timing can be indicated (hereinafter, bundling window). That is, the semi-static HARQ-ACK codebook method is a method in which the size of the HARQ-ACK codebook is fixed (to a maximum value) regardless of the actual number of scheduled DL data. For example, a DL grant DCI (PDCCH) contains PDSCH-to-HARQ-ACK timing information, and the PDSCH-to-HARQ-ACK timing information may have one of a plurality of values ​​(e.g., k). For example, if a PDSCH is received in slot #m and the PDSCH-to-HARQ-ACK timing information within the DL grant DCI (PDCCH) scheduling the PDSCH indicates k, then HARQ-ACK information for the PDSCH may be transmitted in slot #(m+k). As an example, k may be given as {1, 2, 3, 4, 5, 6, 7, 8}. Meanwhile, if HARQ-ACK information is transmitted in slot #n, the HARQ-ACK information may include the maximum possible HARQ-ACK based on the bundling window. That is, the HARQ-ACK information of slot #n may include the HARQ-ACK corresponding to slot #(nk).For example, if k ∈ {1, 2, 3, 4, 5, 6, 7, 8}, the HARQ-ACK information in slot #n contains HARQ-ACKs corresponding to slots #(n-8) through #(n-1) regardless of actual DL data reception (i.e., the maximum number of HARQ-ACKs). Here, the HARQ-ACK information can be substituted with the HARQ-ACK codebook and HARQ-ACK payload. Additionally, slots can be understood / substituted as candidate occasions for DL ​​data reception. As in the example, the bundling window is determined based on the PDSCH-to-HARQ-ACK timing relative to the HARQ-ACK slot, and the PDSCH-to-HARQ-ACK timing set can have predefined values ​​(e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or be set by upper layer (RRC) signaling. A semi-static HARQ-ACK codebook is also referred to as a Type-1 HARQ-ACK codebook. In the case of a Type-1 HARQ-ACK codebook, the number of bits to be sent as a HARQ-ACK report is fixed and can be large. If many cells are configured but only a few are scheduled, a Type-1 HARQ-ACK codebook can be inefficient.

[0157] Meanwhile, in the case of a dynamic HARQ-ACK codebook, the size of the HARQ-ACK payload to be reported by the UE can change dynamically based on the DCI, etc. The dynamic HARQ-ACK codebook is also referred to as a Type-2 HARQ-ACK codebook. The Type-2 HARQ-ACK codebook can be considered a more optimized HARQ-ACK feedback because the UE sends feedback only for scheduled serving cells. However, under poor channel conditions, the UE may misidentify the number of scheduled serving cells, and to resolve this, a DAI is included as part of the DCI. For example, in the dynamic HARQ-ACK codebook method, the DL scheduling DCI may include a counter-DAI (i.e., c-DAI) and / or a total-DAI (i.e., t-DAI). Here, DAI stands for Downlink Assignment Index and is used by the BS to inform the UE of the transmitted or scheduled PDSCH(s) to be included in a single HARQ-ACK transmission. In particular, c-DAI is an index indicating the order among PDCCHs carrying DL scheduling DCIs (hereinafter, DL scheduling PDCCHs), and t-DAI is an index indicating the total number of DL scheduling PDCCHs up to the current slot where there is a PDCCH with t-DAI.

[0158] Meanwhile, in the case of a HARQ process-based HARQ-ACK codebook, the HARQ-ACK payload is determined based on all HARQ processes of all serving cells configured (or activated) within the PUCCH group. For example, the size of the HARQ-ACK payload that the UE reports via the HARQ process-based HARQ-ACK codebook is determined by the number of all serving cells configured or activated within the PUCCH group configured for the UE and the number of HARQ processes for said serving cells. A HARQ process-based HARQ-ACK codebook is also referred to as a Type-3 HARQ-ACK codebook. A Type-3 HARQ-ACK codebook can be applied to one-shot feedback. For example, when a UE receives pdsch-HARQ-ACK-OneShotFeedback through RRC signaling and the UE detects a DCI format containing a one-time HARQ-ACK request field with a value of 1 at any PDCCH monitoring time, it includes the HARQ-ACK information in the Type-3 HARQ-ACK codebook.

[0159] When a UE receives a pdsch-HARQ-ACK-CodebookList through RRC signaling, the UE may be instructed to generate one or more HARQ-ACK codebooks by the pdsch-HARQ-ACK-CodebookList. When the UE is instructed to generate one HARQ-ACK codebook, the HARQ-ACK codebook is associated with a PUCCH of priority index 0. When the UE receives a pdsch-HARQ-ACK-CodebookList, the UE multiplexes only the HARQ-ACK information associated with the same priority index into the same HARQ-ACK codebook. When the UE is instructed to generate two HARQ-ACK codebooks, the first HARQ-ACK codebook is associated with a PUCCH of priority index 0, and the second HARQ-ACK codebook is associated with a PUCCH of priority 1.

[0160] The unit of the time difference between the PUCCH transmission for HARQ-ACK feedback transmission from the DL data channel (e.g., PDSCH-to-HARQ_feedback_timing_indicator) can be determined by a pre-configured subslot length (e.g., the number of symbols constituting the subslot). For example, the unit of the time difference from the DL data channel to the PUCCH for HARQ-ACK feedback transmission can be set by the parameter "subslotLengthForPUCCH" within PUCCH-Config, which is configuration information used to set UE-specific PUCCH parameters. According to these scenarios, the length unit of the PDSCH-to-HARQ feedback timing indicator can be set per HARQ-ACK codebook.

[0161] In some scenarios, uplink or downlink scheduling may be performed dynamically or semi-statically, and the BS may set or instruct the UE to set or instruct the transmission direction (e.g., downlink, uplink, or flexible) of each symbol semi-statically using the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated message, or dynamically using DCI format 2_0. The uplink or downlink scheduling set by the transmission direction thus set or instructed may be canceled. For example, it is possible for the PUCCH set for the transmission of the SPS PDSCH HARQ-ACK (hereinafter SPS HARQ-ACK) to be canceled by the transmission direction set or instructed.

[0162] PUCCH refers to a physical layer UL channel for UCI transmission. PUCCH carries Uplink Control Information (UCI). The UCI types transmitted in PUCCH include hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information, scheduling request (SR), and channel state information (CSI). The UCI bits include HARQ-ACK information bits, SR information bits, LRR information bits, and CSI bits, if present. In this specification, the HARQ-ACK information bits correspond to the HARQ-ACK codebook. In particular, a bit sequence in which HARQ-ACK information bits are arranged according to a defined rule is referred to as the HARQ-ACK codebook.

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

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

[0165] - Channel state information (CSI): Feedback information for the downlink channel. CSI may include at least one of the following: channel quality information (CQI), rank indicator (RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH resource block indicator (SSBRI), layer indicator (LI), (L1-) may include referen signal received power (RSRP) / reference signal received quality (RSRP) / received signal strength indicator (RSSI) / signal to interference plus noise ratio (SINR), etc. If the amount of CSI is large, it may be separated into two or more parts and may be divided into CSI Part 1 and CSI Part 2 according to their importance.

[0166] - Link recovery request (LRR)

[0167] In this specification, for convenience, the PUCCH resources that BS sets and / or directs to the UE for HARQ-ACK, SR, and CSI transmission are respectively referred to as the HARQ-ACK PUCCH resource, SR PUCCH resource, and CSI PUCCH resource.

[0168] PUCCH formats can be classified as follows based on the UCI payload size and / or transmission length (e.g., the number of symbols constituting the PUCCH resource). For details regarding PUCCH formats, refer to Table 4.

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

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

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

[0172] - Transmission structure: PUCCH format 0 consists only of UCI signals without DMRS, and the UE transmits the UCI state by selecting and transmitting one of multiple sequences. For example, the UE transmits a specific UCI to the BS by transmitting one of multiple sequences through a PUCCH that is PUCCH format 0. The UE transmits a PUCCH that is PUCCH format 0 within the PUCCH resource for the corresponding SR setting only when transmitting a positive SR.

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

[0174] (1) PUCCH format 1 (PF1, F1)

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

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

[0177] - Transmission Structure: DMRS and UCI are configured / mapped in a TDM form to different OFDM symbols. That is, DMRS is transmitted in symbols where modulation symbols are not transmitted. UCI is represented by multiplying a modulation (e.g., QPSK) symbol by a specific sequence (e.g., orthogonal cover code (OCC)). Code division multiplexing (CDM) is supported between multiple PUCCH resources (following PUCCH format 1) (within the same RB) by applying cyclic shift (CS) / OCC to both UCI and DMRS. PUCCH format 1 carries a UCI of up to 2 bits, and modulation symbols are spread by an orthogonal cover code (OCC) in the time domain (configured differently depending on whether frequency hopping occurs).

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

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

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

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

[0182] - Transmission Structure: DMRS and UCI are configured / mapped in the form of Frequency Division Multiplex (FDM) within the same symbol. The UE transmits by applying only the IFFT without the DFT to the coded UCI bits. PUCCH Format 2 carries a UCI with a bit size greater than K bits, and the modulated symbol is transmitted via DMRS and FDM. For example, DMRS is located at symbol indices #1, #4, #7, and #10 within a given resource block at 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.

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

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

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

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

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

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

[0189] (4) PUCCH format 4 (PF4, F4)

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

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

[0192] - Transmission structure: DMRS and UCI are configured / mapped in the form of TDM to different symbols. PUCCH format 4 can multiplex up to 4 UEs within the same PRB by applying OCC before the DFT and applying CS (or interleaved FDM, IFDM) mapping to DMRS. In other words, the modulated symbols of UCI are transmitted by TDM (Time Division Multiplexing) with DMRS.

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

[0194] The following table provides examples of PUCCH formats. Depending on the PUCCH transmission length, they can be classified into short PUCCH (formats 0, 2) and long PUCCH (formats 1, 3, 4).

[0195]

[0196] If the UE does not have a dedicated PUCCH configuration provided by the PUCCH-ResourceSet within the RRC configuration PUCCH-Config, for example, before the UE acquires the PUCCH-Config, the PUCCH resource set is N size BWPHARQ-ACK information on PUCCH within the initial UL BWP of the PRBs can be provided by SIB-PUCCH-ResourceCommon through an index to the row of the following table for transmission.

[0197] The following table is Table 9.2.1-1 of 3GPP TS 38.213 and illustrates the sets of PUCCH resources (also referred to as initial PUCCH resource sets) and their corresponding parameters that can be used before the dedicated PUCCH resource is set. The BS sets / instructs one of the index values ​​0 through 15 in the following table cell-specifically through the parameter pucch-ResourceCommon within the SIB.

[0198]

[0199] The above PUCCH resource set each consists of the PUCCH format, first symbol, duration, PRB offset RB. offset BWP , and may include 16 resources corresponding to the circular transition index for PUCCH transmission. For a set of PUCCH resources defined by index, 16 PUCCH resources (r) using the parameters predefined in the table above. PUCCH = 0, 1, 2, ..., 15) can be formed. For example, if BS sets / indicates index 0, 1, or 4 through SIB, the parameter values ​​for each of the 16 different PUCCH resources may be as follows.

[0200]

[0201] If the UE is not provided with the RRC parameter pdsch-HARQ-ACK-Codebook regarding whether the PDSCH HARQ-ACK codebook is semi-static or dynamic, the UE generates at most one HARQ-ACK bit. If the UE provides HARQ-ACK information in a PUCCH transmission in response to detecting DCI format 1_0 or DCI format 1_1, the UE selects the PUCCH resource for the PUCCH transmission from among the 16 PUCCH resources belonging to the PUCCH resource set corresponding to the index obtained through the pucch-ResourceCommon in the SIB, and N, the number of CCEs in the CORESET of the PDCCH reception with DCI format 1_0 or DCI 1_1. CCE , index n of the first CCE for receiving the above PDCCH CCE,0 , the value of the PUCCH resource indicator (PRI) field in the above DCI format 1_0 or DCI format 1_1 △ PRI It can be determined based on. For example, if the UE provides HARQ-ACK information in a PUCCH transmission in response to detecting DCI format 1_0 or DCI format 1_1, the UE uses index r PUCCH r PUCCH resources PUCCH = floor{(2*n CCE,0 ) / N CCE} + 2*△ PRI It is determined as, where 0 ≤ r PUCCH ≤ 15. floor(r PUCCH If / 8) = 0, then the UE, at the first hop, uses the PRB index of the PUCCH transmission as RB offset BWP + floor(r PUCCH / N CS Determined as ), and in the second hop, the PRB index of the above PUCCH transmission is Nsize BWP - 1 - RB offset BWP - floor(r PUCCH / N CS Determined as ), where N CS is the total number of initial cyclic transition indices within the set of initial cyclic transition indices, and the UE is the initial cyclic transition index within the set of initial cyclic transition indices r PUCCH mod N CS It can be determined as. floor(r PUCCH If / 8) = 1, then the UE uses N as the PRB index of the PUCCH transmission at the first hop. size BWP - 1 - RB offset BWP - floor{(r PUCCH - 8) / N CS Determined as}, and in the second hop, the PRB index of the above PUCCH transmission is RB offset BWP + floor{(r PUCCH - 8) / N CS} is determined as, and the UE determines the initial cyclic transition index within the set of initial cyclic transition indices (r PUCCH - 8) mod N CS It can be determined as.

[0202] If a UE has a dedicated PUCCH resource configuration, the UE is provided with one or more PUCCH resources by upper-layer signaling. PUCCH resources may be determined by UCI type (e.g., HARQ-ACK, SR, CSI). The PUCCH resources used for UCI transmission may be determined based on the UCI (payload) size. For example, the BS configures multiple PUCCH resource sets for the UE, and the UE can select a specific PUCCH resource set corresponding to a specific range based on the range of UCI (payload) sizes (e.g., number of UCI bits). For example, the UE [selects] the number of UCI bits (N UCI You can select one of the following sets of PUCCH resources based on ).

[0203] - PUCCH resource set #0, if UCI bit count =< 2

[0204] - PUCCH resource set #1, if 2 < UCI bit count =< N1

[0205] ...

[0206] - PUCCH resource set #(K-1), if N K-2 < UCI bit count =< N K-1

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

[0208] The settings for each PUCCH resource include the PUCCH resource index, the index of the starting PRB, and the settings for one of PUCCH formats 0 through 4. The code rate for multiplexing HARQ-ACK, SR, and CSI report(s) within a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4 is set for the UE by the BS through the upper layer parameter maxCodeRate. The upper layer parameter maxCodeRate is used to determine how to feed back the UCI on the PUCCH resource for PUCCH format 2, 3, or 4.

[0209] If the UCI type is SR or CSI, the PUCCH resource to be used for UCI transmission within the PUCCH resource set can be set to the UE by the network via upper-layer signaling (e.g., RRC signaling). If the UCI type is HARQ-ACK for SPS (Semi-Persistent Scheduling) PDSCH, the PUCCH resource to be used for UCI transmission within the PUCCH resource set can be set to the UE by the network via upper-layer signaling (e.g., RRC signaling). On the other hand, if the UCI type is HARQ-ACK for PDSCH scheduled by DCI, the PUCCH resource to be used for UCI transmission within the PUCCH resource set can be scheduled based on DCI.

[0210] In the case of DCI-based PUCCH resource scheduling, the BS transmits the DCI to the UE via PDCCH and can indicate the PUCCH resources to be used for UCI transmission within a specific set of PUCCH resources through the ACK / NACK resource indicator (ARI) within the DCI. The ARI is used to indicate PUCCH resources for ACK / NACK transmission and may also be referred to as the PUCCH resource indicator (PRI). Here, the DCI is the DCI used for PDSCH scheduling, and the UCI may include HARQ-ACK for PDSCH. Meanwhile, the BS can set a set of PUCCH resources to the UE using (UE-specific) upper-layer (e.g., RRC) signals, consisting of more PUCCH resources than the number of states that the ARI can represent. In this case, the ARI indicates a subset of PUCCH resources within the PUCCH resource set, and which PUCCH resource to use within the indicated subset of PUCCH resources may be determined according to an implicit rule based on transmission resource information for the PDCCH (e.g., the index of the PDCCH's control channel element (CCE)).

[0211] In existing 5G NR, a PUCCH resource to carry HARQ-ACK (or A / N) information for a PDSCH can be allocated through a DCI that schedules the PDSCH. Specifically, the PUCCH resource index is indicated through the PUCCH resource indicator (PRI) field, and the location of the slot to which the PUCCH is to be transmitted can also be indicated through a separate field. The UE can transmit ACK information if it successfully receives the PDSCH, or NACK information otherwise, through the PUCCH indicated by the DCI that scheduled the PDSCH.

[0212] Existing 5G UEs can consider the following when transmitting A / N information via PUCCH.

[0213] Up to five PUCCH formats are defined based on the amount of A / N (and / or CSI) information, the number of symbols required for reliable PUCCH transmission, and multiplexing capacity (e.g., the number of UEs that can be code domain multiplexed on the same PUCCH resource). A UE must select and transmit one of the five PUCCH formats depending on the situation.

[0214] If multiple PUCCHs for A / N transmission exist within a single slot, or if multiple PUCCHs exist for both A / N transmission and CSI transmission, or if one or more PUSCHs exist within the same carrier / serving cell or different carrier / serving cells (within the same PUCCH group), the UE must select and transmit the PUSCH or PUCCH that serves as the final container for the A / N and / or CSI, taking into consideration processing time and other factors.

[0215] At least due to the considerations above, the implementation of A / N transmission operations in the UE may become complex. Therefore, to reduce the complexity of the UE implementation, A / N (and / or CSI) transmission via PUCCH may not be supported in 6G. Alternatively, in 6G, A / N (and / or CSI) transmission via PUCCH may be allowed only before a dedicated PUCCH resource is established or when the A / N (and / or CSI) payload size is below a certain level.

[0216] In order to solve these problems, some implementations of the present specification are described below. Some implementations of the present specification described below include a method of scheduling a PDSCH and a PUSCH to carry HARQ-ACK information for said PDSCH through a single DCI, and a method of transmitting HARQ-ACK information corresponding to the PDSCH through a CG PUSCH.

[0217] <1. Method for scheduling PDSCH and PUSCH by a single DCI>

[0218] FIG. 11 illustrates an example of scheduling PDSCH and PUSCH through a single DCI according to some implementations of the present specification.

[0219] In 6G, if the transmission of A / N (and / or CSI) via PUCCH is not supported, or if the transmission of A / N (and / or CSI) via PUCCH is allowed only before a dedicated PUCCH resource is allocated or when the A / N (and / or CSI) payload size is below a certain level, then a PUSCH resource to carry A / N information corresponding to the PDSCH must also be allocated through a DCI that schedules the PDSCH.

[0220] Accordingly, some implementations of this specification for scheduling PDSCH as well as PUSCH through a single DCI are described below. Referring to FIG. 11, PDSCH and PUSCH may be scheduled through a single DCI according to some implementations of this specification. In this case, PUSCH may include at least A / N information corresponding to PDSCH. DCI, PDSCH, and PUSCH may all be transmitted through the same carrier / BWP / serving cell / transmission and reception point (TRP), or all or part of them may be transmitted through different carrier / BWP / serving cell / TRP. Additionally, some implementations of this specification may be extended to cases where one or more PDSCH and / or one or more PUSCH are scheduled through the said DCI.

[0221] For convenience, when scheduling PDSCH and PUSCH through a single DCI in this specification, the DCI is designated as A / N-DCI. The PDSCH and PUSCH scheduled in the A / N-DCI are designated as PDSCH#A and PUSCH#A, respectively, and PUSCH#A may include at least A / N information corresponding to PDSCH#A. For PUSCH#A scheduled in the A / N-DCI, if UL-SCH is included, PUSCH#A is designated as PUSCH-data, and if UL-SCH is not included, PUSCH#A is designated as PUSCH-UCI. Unless otherwise noted, PUSCH#A may mean PUSCH-data and / or PUSCH-UCI.

[0222] In this specification, some implementations are described using the case where a dynamic grant PDSCH is scheduled via an A / N-DCI as an example; however, some implementations of this specification may be extended to cases where an SPS PDSCH is activated via the said A / N-DCI. In this case, a corresponding PUSCH#A may be scheduled from each SPS PDSCH activated via the said A / N-DCI, and the A / N information of the SPS PDSCH corresponding to each PUSCH#A may be included.

[0223] <Method #1-1> How to Interpret Fields in A / N-DCI

[0224] <1-1-1. Carrier Indicator Field>

[0225] According to current 5G standard documents, the Carrier Indicator field can be utilized to schedule PDSCH or PUSCH on other Carrier(s) / Serving Cell(s) / BWP(s) from one Carrier(s) / Serving Cell(s) / BWP. For example, if the field consists of N1 bits, up to 2 N1 Carrier(s) / serving cell(s) / BWP(s) corresponding to each of the code-point(s) can be pre-configured. 2 N1 If a specific code-point among the code-point(s) is indicated, it may mean scheduling a PDSCH or PUSCH on the carrier(s) / serving cell(s) / BWP(s) corresponding to that code-point.

[0226] In some implementations of this specification, the UE expects PDSCH#A to be transmitted on the carrier(s) / serving cell(s) / BWP(s) indicated by the corresponding carrier indicator field and may receive PDSCH#A on the indicated carrier(s) / serving cell(s) / BWP(s). For PUSCH#A, one of the following options may be applied. The selection of which option to choose may be pre-configured, and different options may be applied depending on whether it is PUSCH-data or PUSCH-UCI.

[0227] Opt 1-1: The applicable carrier indicator field (e.g., the carrier indicator field within the DCI format scheduling PDSCH) is ignored, and PUSCH#A is transmitted over a specific carrier / serving cell / BWP. The applicable carrier / serving cell / BWP may be a PCell (or PSCell) or one (or more) pre-configured carrier / serving cell / BWP. This is because it may be advantageous to utilize frequency resources that guarantee stable A / N transmission, considering that PUSCH#A contains A / N.

[0228] Opt 1-2: PUSCH#A is transmitted by the UE on the carrier(s) / serving cell(s) / BWP(s) indicated by the corresponding carrier indicator field (e.g., the carrier indicator field within the DCI format scheduling PDSCH). In this case, the carrier(s) / serving cell(s) / BWP(s) for PDSCH#A transmission and the carrier(s) / serving cell(s) / BWP(s) for PUSCH#A transmission may be configured differently for a single code-point of the carrier indicator field. For example, the value indicated by my carrier indicator field may be mapped to different carrier(s) / serving cell(s) / BWP(s) for PDSCH and PUSCH. If the corresponding code-point is indicated, the UE can receive PDSCH#A on any carrier(s) / serving cell(s) / BWP(s) and transmit PUSCH#A on another carrier(s) / serving cell(s) / BWP(s). Opt 1-2 has the advantage of being able to dynamically change the PUSCH#A transmission frequency resources compared to Opt 1-1.

[0229] In some implementations, Opt 1-2 may be applied for PUSCH-data and Opt 1-1 may be applied for PUSCH-UCI.

[0230] <1-1-2. FDRA Field>

[0231] According to current 5G standard documents, frequency resources can be allocated in the form of a bitmap in the form of a resource block group (RBG) or in the form of a resource indicator value (RIV) that indicates the start and end of the frequency resources.

[0232] Given that the resources of PDSCH#A may differ, in some implementations of this specification, the FDRA field (or block) for PDSCH#A allocation and the FDRA field (or block) for PUSCH#A allocation may be configured separately. The FDRA field (or block) for PUSCH#A allocation may be interpreted differently for PUSCH-data and PUSCH-UCI. For example, the number of RBs constituting the RGB may differ, or the unit of the number of RBs forming the RIV may differ. Alternatively, in the case of PUSCH-UCI, instead of allocating the entire amount of frequency resources (as in PUSCH-data), only the starting / ending PRB index of the frequency resources may be indicated. Based on the amount of UCI payload carried in PUSCH-UCI (and pre-set / defined modulation order, coding rate, etc.), the UE determines the number of RBs to actually occupy and can transmit PUSCH-UCI with the number of RBs corresponding to the number of RBs starting from the indicated start / end PRB index. Alternatively, even if X RB(s) are allocated using RBG or RIV forms in the case of PUSCH-UCI, if the number Y of RB(s) calculated by the UE based on the amount of UCI payload carried in PUSCH-UCI (and pre-set / defined modulation order, coding rate, etc.) is less than X, the UE can transmit PUSCH-UCI by occupying only Y RB(s) out of the X RB(s) (e.g., occupying from the lowest / highest RB index among the X RB(s).If a UE receives an instruction to transmit PUSCH-data and there is no UL-SCH to transmit, it may determine frequency resources by considering the actual transmitted PUSCH#A as PUSCH-data, even if it is PUSCH-UCI (e.g., not applying the method of indicating start / end PRB indices specialized for PUSCH-UCI as above, or the method of occupying only Y RBs among X RBs). If invalid information is indicated in the FDRA field (or block) for PDSCH#A allocation (e.g., all zeros or all ones, etc.), the UE may consider that PDSCH#A is not allocated and may interpret the fields related to PDSCH#A (e.g., TDRA, MCS, HARQ process index, new data indicator (NDI), redundancy version (RV), etc.) for PUSCH#A scheduling purposes.

[0233] <1-1-3. TDRA Field>

[0234] According to the current 5G standard document, in advance, the UE may receive N2 TDRA entries from the BS or N2 TDRA entries may be defined in the standard document. A single TDRA entry may be associated with a SLIV, DM-RS mapping type, and a slot offset value from the DCI to the slot where PUSCH / PDSCH is transmitted. Ceiling {log2(N2)} bits are allocated through the DCI, and the UE can receive PDSCH or transmit PUSCH by utilizing information such as the SLIV, DM-RS mapping type, and slot offset from the TDRA entry corresponding to the indicated code-point.

[0235] In some implementations of this specification, for a single TDRA entry, information for PDSCH#A and information for PUSCH#A may be linked at once. For example, the following information may be linked to the n-th TDRA entry. Alternatively, if there are TDRA entry(s) configured for a DL DCI for PDSCH scheduling, the index value of the entry may be linked to the TDRA entry of the A / N-DCI, or if there are TDRA entry(s) configured for a UL DCI for PUSCH scheduling, the index value of the entry may be linked to the TDRA entry of the A / N-DCI. For example, with X TDRA entries configured for PDSCH scheduling and Y TDRA entries configured for PUSCH scheduling, the TDRA entries for A / N-DCI can be configured such that the first entry for A / N-DCI is linked to PDSCH TDRA entry #0 and PUSCH TDRA entry #3, and the second entry is linked to PDSCH TDRA entry #3 and PUSCH TDRA entry #7.

[0236] PDSCH#A's {SLIV, DM-RS mapping type, K0 (DCI-to-PDSCH slot offset)

[0237] PUSCH#A's {SLIV, DM-RS mapping type, K2 (DCI-to-PUSCH slot offset) or Kx (PDSCH-to-PUSCH slot offset)}

[0238] Alternatively, information regarding PUSCH-UCI and PUSCH-data can be linked at once, and if it is determined whether it is PUSCH-UCI or PUSCH-data according to Method #1-2 described below, the TDRA entry may be interpreted differently accordingly.

[0239] PDSCH#A's {SLIV, DM-RS mapping type, K0 (DCI-to-PDSCH slot offset)

[0240] PUSCH-UCI's {SLIV, DM-RS mapping type, K2 (DCI-to-PUSCH slot offset) or Kx (PDSCH-to-PUSCH slot offset)}

[0241] PUSCH-data's {SLIV, DM-RS mapping type, K2 (DCI-to-PUSCH slot offset) or Kx (PDSCH-to-PUSCH slot offset)}

[0242] For example, if PUSCH-UCI is determined by Method #1-2, etc. described below, the UE can determine the resources of PUSCH#A based on the PUSCH-UCI information when interpreting the TDRA entry linked to the above information. Additionally, if PUSCH-data is determined by Method #1-2, etc. described below, the UE can determine the resources of PUSCH#A based on the PUSCH-data information when interpreting the TDRA entry linked to the above information.

[0243] In some TDRA entries, the information corresponding to PDSCH#A may be invalid (e.g., the TDRA entry corresponds to an invalid SLIV value, an invalid K0 value, or no information for PDSCH#A is set for the TDRA entry), and the UE may consider that PDSCH#A is not assigned and interpret the fields associated with PDSCH#A (e.g., FDRA, MCS, HARQ process index, NDI, RV, etc.) for PDSCH#A scheduling purposes.

[0244] The K2 or Kx values ​​associated with PUSCH#A, PUSCH-UCI, or PUSCH-data in the above may be omitted. Also, a single TDRA entry consisting of SLIV, DM-RS mapping type, and K0 / K2 / Kx is just one example, and a single TDRA entry may be composed of all or part of these and other parameters.

[0245] <1-1-4. K1 Timing or PDSCH-to-HARQ_Feedback Timing Indicator>

[0246] According to current 5G standard documents, this is a field that indicates the offset between the slot containing the PDSCH and the slot where the corresponding PUCCH was transmitted. If there is only one pre-set / defined K1 value, this field may be omitted, and if there are N3 pre-set / defined K1 (candidate) values, ceiling{log2(N3)} bits are allocated so that one of the N3 candidate K1 values ​​can be indicated through DCI.

[0247] In some implementations of this specification, for PUSCH#A, one of the following options may be applied. In this case, which option to select may be pre-configured, and different options may be applied depending on whether it is PUSCH-data or PUSCH-UCI.

[0248] Opt 4-1: The UE may transmit PUSCH#A by ignoring the K2 or Kx value associated with the indicated TDRA entry (or if the K2 or Kx value associated with the indicated TDRA entry is omitted) and applying the value indicated in the corresponding K1 timing field (e.g., after the K1 slot from the slot containing DCI or PDSCH).

[0249] Opt 4-2: If the slot index determined by the K2 or Kx value associated with the indicated TDRA entry is T1, the UE can transmit PUSCH#A in the slot of slot index {T1+K1}.

[0250] Opt 4-3: If the slot index determined by the K2 or Kx value associated with the indicated TDRA entry is T1, and the slot index determined by the K1 timing field (or the slot index after the K1 slot from the slot containing PDSCH) is T2, then the UE can transmit PUSCH#A through the slot that follows (or precedes) T1 or T2.

[0251] In some implementations, the UE may apply Opt 4-1 (or Opt 4-3) if PUSCH-UCI and Opt 4-2 if PUSCH-data.

[0252] <1-1-5. (Enhanced) Type-3 HARQ-ACK Codebook 1-Bit Indicator>

[0253] According to current 5G standard documents, if the (advanced) Type-3 HARQ-ACK codebook is triggered through the corresponding field in an existing NR system, there is no scheduling for PDSCH within the DCI (e.g., the FDRA field for PDSCH is signaled as invalid, with all zeros or all ones), and the UE can feed back A / N information for all / some HARQ process index(s) of all / some serving cells via PUCCH.

[0254] In some implementations of this specification, if the (enhanced) Type-3 HARQ-ACK codebook is triggered through the relevant fields, the UE may consider that PDSCH#A is not assigned and interpret the fields associated with PDSCH#A (e.g., FDRA, TDRA, MCS, HARQ process index, NDI, RV, etc.) for PUSCH#A scheduling purposes. Alternatively, if the (enhanced) Type-3 HARQ-ACK codebook is triggered through the relevant fields and the FDRA and / or TDRA fields for PDSCH#A are not valid, the UE may consider that PDSCH#A is not assigned and interpret the fields associated with PDSCH#A (e.g., FDRA, TDRA, MCS, HARQ process index, NDI, RV, etc.) for PUSCH#A scheduling purposes.

[0255] <Method #1-2> How to distinguish whether to schedule PUSCH-UCI or PUSCH-data using specific field(s) within A / N-DCI

[0256] In some implementations of this specification, the UE can determine whether PUSCH#A scheduled by the A / N DCI is PUSCH-UCI or PUSCH-data by applying at least one of the following options.

[0257] Opt A-1: ​​Identifier for DCI formats field

[0258] According to current 5G standard documents, if the field is '0', it can be signaled that it is a UL DCI scheduling UL transmission, and if it is '1', it can be signaled that it is a DL DCI scheduling DL transmission.

[0259] In some implementations of this specification, if the field indicates that it is a DL DCI, the UE knows that PDSCH#A and PUSCH-UCI can be scheduled through the A / N-DCI, and if it indicates a UL DCI, the UE knows that PDSCH#A and PUSCH-data can be scheduled. Alternatively, if the field is not set, the UE knows that only PDSCH#A and PUSCH-UCI (or PDSCH#A and PUSCH-data) can be scheduled through the A / N-DCI, or one of the following options (e.g., Opt A-2 through Opt A-5) may be applied.

[0260] Opt A-2: TDRA Field

[0261] In some implementations of this specification, a UE may be provided with a configuration from the BS in which a specific TDRA entry #1 is coupled only with (PDSCH#A and) PUSCH-UCI, and another TDRA entry #2 is coupled only with (PDSCH#A and) PUSCH-data. If TDRA entry #1 is indicated through the TDRA field, the UE can know that (PDSCH#A and) PUSCH-UCI can be scheduled through the corresponding A / N-DCI, and if TDRA entry #2 is indicated through the TDRA field, the UE can know that (PDSCH#A and) PUSCH-data can be scheduled.

[0262] Opt A-3: MCS Field

[0263] In some implementations of this specification, the MCS field (or block) for PDSCH#A and the MCS field (or block) for PUSCH#A may be assigned separately. If a specific value (e.g., 0, or such specific value may be predefined / set) is indicated through the MCS field (or block) for PUSCH#A, the UE can know that (PDSCH#A and) PUSCH-UCI may be scheduled through the A / N-DCI, and if another value is indicated, the UE can know that (PDSCH#A and) PUSCH-data may be scheduled. When (PDSCH#A and) PUSCH-UCI are scheduled through the A / N-DCI, the MCS (or modulation order, (maximum) coding rate), etc. to be applied to the A / N PUSCH may be predefined / set.

[0264] Opt A-4: UL-SCH indicator field

[0265] According to current 5G standard documents, the UL-SCH indicator field is included within the DCI format for scheduling PUSCH, and if the field is '1', it means that the UE must transmit a PUSCH containing UL-SCH, and if it is '0', it means that the UE must transmit a PUSCH without UL-SCH.

[0266] In some implementations of this specification, the UL-SCH indicator field may also be included in a DCI format capable of scheduling PDSCH. In some implementations of this specification, if the field is '0' (or '1'), the UE can know that (PDSCH#A and) PUSCH-UCI can be scheduled through the A / N-DCI, and if it is '1' (or '0'), the UE can know that (PDSCH#A and) PUSCH-data can be scheduled.

[0267] Opt A-5: If there is a UL-SCH to send, PUSCH#A scheduled via A / N-DCI is PUSCH-data, and if there is no UL-SCH to send, PUSCH-A scheduled via A / N-DCI is PUSCH-UCI, the UE may consider this.

[0268] <Method #1-3> Collision handling method when multiple PUSCH#A transmissions are scheduled through one or more A / N-DCIs

[0269] FIG. 12 illustrates a situation in which PUSCH transmissions collide due to multiple DCIs, each scheduling PDSCH and PUSCH according to some implementations of the present specification. Referring to FIG. 12, PDSCH#1 and PUSCH#1 may be scheduled via A / N-DCI #1, and PDSCH#2 and PUSCH#2 may be scheduled via A / N-DCI #2. Compared to the start / end symbol of DCI#1 (or the CORESET containing DCI#1), the start / end symbol of DCI#2 (or the CORESET containing DCI#2) may be lagging in the time axis, or even if they lie at the same time, the carrier / serving cell / BWP index may be larger. Alternatively, compared to the start / end symbol of PDSCH#1, the start / end symbol of PDSCH#2 may be lagging in the time axis, or even if they lie at the same time, the carrier / serving cell / BWP index may be larger. At this time, the UE may perform one of the following actions. The selection of an option may be pre-configured or indicated via A / N-DCI, and different options may be applied depending on whether PUSCH#1 / PUSCH#2 is PUSCH-data or PUSCH-UCI. Additionally, different options may be applied depending on whether PUSCH#1 and PUSCH#2 fall within a single slot (or a specific time interval). Furthermore, different options may be applied depending on the time interval between PDSCH and PUSCH (e.g., considering the processing time for the UE's A / N transmission).

[0270] Opt B-1: PUSCH#1 may contain A / N information corresponding to PDSCH#1, and PUSCH#2 may contain A / N information corresponding to PDSCH#2.

[0271] Opt B-2: PUSCH#1 does not carry A / N information corresponding to PDSCH#1, and PUSCH#2 may carry A / N information corresponding to PDSCH#1 and PDSCH#2. Additionally, on PUSCH#1 (especially when PUSCH#1 is PUSCH-data and / or when there is UL-SCH to be transmitted by the UE), the UE may transmit UL-SCH.

[0272] Opt B-3: PUSCH#1 does not contain A / N information corresponding to PDSCH#1, and PUSCH#2 may contain A / N information corresponding to both PDSCH#1 and PDSCH#2. Additionally, the UE may ignore the assignment information for PUSCH#1.

[0273] Opt B-4: PUSCH#2 does not carry A / N information corresponding to PDSCH#2, and PUSCH#1 may carry A / N information corresponding to PDSCH#1 and PDSCH#2. Additionally, on PUSCH#2 (especially when PUSCH#2 is PUSCH-data and / or when there is UL-SCH to be transmitted by the UE), the UE may transmit UL-SCH.

[0274] Opt B-5: PUSCH#2 does not carry A / N information corresponding to PDSCH#2, and PUSCH#1 may carry A / N information corresponding to PDSCH#1 and PDSCH#2. Additionally, the UE may ignore the allocation information for PUSCH#2.

[0275] Opt B-6: The UE does not expect PUSCH#1 and PUSCH#2, scheduled through different A / N-DCIs as illustrated in FIG. 12, to be located within a single slot (or a certain time interval), and can expect the same time / frequency resources to be allocated within that interval.

[0276] In some implementations, if PUSCH#1 is PUSCH-UCI, Opt B-3 may be applied, and if PUSCH#1 is PUSCH-data, Opt B-2 may be applied. Alternatively, if PUSCH#1 and PUSCH#2 do not belong to the same slot, Opt B-1 may be applied, and if they belong to the same slot, one of the remaining options may be applied.

[0277] FIG. 13 is an example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification. Referring to FIG. 13, the BS may provide the UE with upper-level parameters necessary for setting up the A / N-DCI (or enabling the A / N-DCI or setting it to monitor the A / N-DCI) and configuring the fields within the A / N-DCI (S1301). The BS may schedule PDSCH#A and PUSCH#A by transmitting the A / N-DCI (S1303). In some implementations, the UE may receive the A / N-DCI and obtain scheduling information for PDSCH#A and / or PUSCH#A by applying the aforementioned method #1-1 (S1303). Additionally, the UE may receive PDSCH#A (S1305) and generate A / N information depending on whether the reception was successful. In some implementations, the UE may apply the above-described method #1-2 to transmit only the A / N information if the PUSCH#A is PUSCH-UCI, and transmit the UL-SCH as well as the A / N information if the PUSCH#A is PUSCH-data (S1307).

[0278] According to some implementations of the aforementioned specification, the UE can receive scheduling information for a PDSCH and a PUSCH that can indicate whether the PDSCH has been successfully received through a single DCI. If a UL-SCH exists, the PUSCH can be configured through multiplexing between the A / N information and the UL-SCH. This can increase the efficiency of the BS's scheduling information transmission and the UE's UL-SCH transmission efficiency.

[0279] <2. Method of carrying HARQ-ACK information PDSCH on CG PUSCH>

[0280] According to some implementations of this specification described above, if a single DCI must be used to schedule not only the PDSCH but also the PUSCH carrying the HARQ-ACK information for the PDSCH, the signaling overhead of the DCI may increase. Some implementations of this specification for transmitting the HARQ-ACK of the PDSCH via the CG PUSCH are described below to avoid or minimize additional signaling overhead of the DCI. As with some implementations of this specification described above, in some implementations of this specification described below, the DCI, PDSCH, and PUSCH may all be transmitted to the same carrier / BWP / serving cell / TRP, or all or part of them may be transmitted to different carriers / BWP / serving cell / TRP. Furthermore, some implementations of this specification described below may be extended to cases where one or more PDSCHs are scheduled through the DCI.

[0281] <Method #2-1> Method for feeding back A / N information corresponding to DG PDSCH via CG-PUSCH

[0282] FIGS. 14 and FIGS. 15 are illustrated to explain some implementations of the present specification of transmitting HARQ-ACK information for DG PDSCH through a configured grant-based PUSCH.

[0283] As exemplified in Fig. 14, a single DG PDSCH can be scheduled through DCI. A UE that receives a PDSCH can transmit A / N information, which is information regarding the success of receiving the PDSCH, on a CG-PUSCH.

[0284] Among the various CG-PUSCHs transmitted at regular intervals, a rule may be required to determine exactly which CG-PUSCH resource should carry the A / N information corresponding to the PDSCH. Since this rule allows the BS to predict which CG-PUSCH resource the UE will use to transmit the A / N information, it can help the BS receive the A / N information.

[0285] A method that takes into account the processing time from the reception of the UE's PDSCH until the transmission of A / N information may be applied. For example, if the processing time according to the UE's capability and / or BS setting / instruction is X (where X can be set / instructed / defined in units of symbols / slots / subframes / frames / ms), the nearest CG-PUSCH after X from the reference point of the PDSCH may be selected. Alternatively, the CG-PUSCH belonging to the nearest slot after X from the reference point of the PDSCH may be selected. In this case, the reference point of the PDSCH may be the starting / ending boundary of the start / last symbol of the PDSCH or the starting / ending boundary of the slot in which the PDSCH is carried. As shown in the example of FIG. 15, the interval between the last time point of the PDSCH and the start time point of CG-PUSCH#3 may be T1, and the interval between the last time point of the PDSCH and the start time point of CG-PUSCH#4 may be T2. If T1 is smaller than X and T2 is larger than X, the UE can transmit A / N information corresponding to PDSCH to the CG-PUSCH#4 resource.

[0286] Multiple configured grant (CG) configuration indices may be configured and activated within a single carrier / serving cell / BWP (i.e., multiple CG configurations may be configured within a single carrier / serving cell / BWP), or one or more CG configuration indices may be configured and activated within multiple carriers / serving cells / BWPs. In this case, a rule may be required regarding which A / N information corresponding to each PDSCH can be carried in a CG-PUSCH resource linked to which CG configuration index is activated on which carrier / serving cell / BWP. At least one of the following options may be applied.

[0287] Opt 1: A single CG configuration index activated on a specific carrier / serving cell / BWP may be determined. A UE receiving a PDSCH may select a single CG-PUSCH resource from among the CG-PUSCH resources corresponding to the determined CG configuration index that satisfies the condition that it is X after the reference point of the PDSCH (or a separate condition). The specific carrier / serving cell / BWP may be defined in advance in a standard document (e.g., PCell, PSCell), defined by a rule (e.g., lowest / highest carrier / serving cell / BWP index, DCI, or a carrier / serving cell / BWP identical to the PDSCH), set / indicated by upper-level signaling, or indicated via DCI. Additionally, a single CG configuration index may be determined in advance by a rule (e.g., lowest / highest activated CG configuration index), set / indicated by upper-level signaling, or indicated via DCI. For example, the carrier / serving cell / BWP index may be set / indicated by upper-layer signaling (e.g., RRC, MAC CE, etc.) and the CG setting index may be indicated by DCI. For another example, the CG setting index may be set / indicated by upper-layer signaling (e.g., RRC, MAC CE, etc.) and the carrier / serving cell / BWP index may be indicated by DCI. In the corresponding option, DCI may be the DCI that schedules DG-PDSCH.

[0288] Opt 2: One or more carrier / serving cell / BWPs and / or one or more CG configuration indices may exist. Among these multiple candidates, a UE receiving a PDSCH may select a CG-PUSCH resource that satisfies the condition that it is X after the reference point of the PDSCH (or a separate condition). One or more carrier / serving cell / BWPs are referred to as carrier groups for convenience. Such carrier groups may be defined in a standard document in advance (e.g., all carrier / serving cell / BWPs within the same PUCCH / cell group), defined by a rule (e.g., DCI or all carrier / serving cell / BWPs within the same PUCCH / cell group as the PDSCH), established / indicated by upper-layer signaling (one of the multiple pre-established / defined carrier groups), or indicated via DCI (one of the multiple pre-established / defined carrier groups). Additionally, one or more CG configuration indices are referred to as CG groups for convenience. A CG group may be determined by a rule in advance (e.g., all (activated) CG configuration indices belonging to a specific cell (determined by Opt 1)), set / indicated by upper-level signaling (one of multiple pre-set / defined CG groups), or indicated via DCI. For example, a carrier group may be set / indicated by upper-level signaling (e.g., RRC, MAC CE, etc.) and a CG group may be indicated by DCI. For another example, a CG group may be set / indicated by upper-level signaling (e.g., RRC, MAC CE, etc.) and a carrier group may be indicated by DCI. In the relevant option, DCI may be the DCI that schedules DG-PDSCH.

[0289] <Method #2-2> Method for feeding back A / N information corresponding to SPS PDSCH via CG-PUSCH

[0290] FIGS. 16 and FIGS. 17 are illustrated to explain some implementations of the present specification of transmitting HARQ-ACK information for SPS PDSCH through a configured grant-based PUSCH.

[0291] As exemplified in FIG. 16, the UE can receive one or more SPS PDSCHs activated by the activating DCI. The UE that receives the SPS PDSCH can transmit A / N information, which indicates whether the SPS PDSCH was successfully received, on the CG-PUSCH.

[0292] Among the various CG-PUSCHs transmitted at regular intervals, a rule may be required to determine exactly which CG-PUSCH resource should carry the A / N information corresponding to each SPS PDSCH. Since this rule allows the BS to predict which CG-PUSCH resource the UE will use to transmit the A / N information, it can help the BS receive the A / N information.

[0293] A method that takes into account the processing time from the UE's reception of the SPS PDSCH until the transmission of A / N information may be applied. For example, if the processing time according to the UE's capability and / or BS setting / instruction is X (where X can be set / instructed / defined in units of symbols / slots / subframes / frames / ms), the nearest CG-PUSCH after X from the reference point of the SPS PDSCH may be selected. Alternatively, the CG-PUSCH belonging to the nearest slot after X from the reference point of the SPS PDSCH may be selected. In this case, the reference point of the SPS PDSCH may be the start / end boundary of the start / end symbol of the SPS PDSCH or the start / end boundary of the slot in which the SPS PDSCH is carried. As shown in the example of Fig. 17, when the first CG-PUSCH satisfying the corresponding condition from SPS PDSCH#1 is the CG-PUSCH#1 resource and the first CG-PUSCH satisfying the corresponding condition from SPS PDSCH#2 / 3 is the CG-PUSCH#2 resource, CG-PUSCH#1 may carry A / N information corresponding to SPS PDSCH#1 and CG-PUSCH#2 may carry A / N information corresponding to SPS PDSCH#2 / 3.

[0294] Multiple CG configuration indices may be configured and activated within a single carrier / serving cell / BWP, or one or more CG configuration indices may be configured and activated within multiple carriers / serving cells / BWPs. In this case, a rule may be required regarding which A / N information corresponding to each SPS PDSCH can be carried in a CG-PUSCH resource linked to which CG configuration index is activated on which carrier / serving cell / BWP. At least one of the following options may be applied.

[0295] Opt A: A single CG setting index activated on a specific carrier / serving cell / BWP may be determined. A UE receiving an SPS PDSCH may select a single CG-PUSCH resource from among the CG-PUSCH resources corresponding to the determined CG setting index that satisfies the condition (or a separate condition) that it is X after the reference point of the said SPS PDSCH. The said specific carrier / serving cell / BWP may be defined in advance in a standard document (e.g., PCell, PSCell), defined by a rule (e.g., lowest / highest carrier / serving cell / BWP index, DCI, or a carrier / serving cell / BWP identical to the PDSCH, etc.), set / indicated by upper-level signaling, or indicated via DCI. Additionally, a single CG setting index may be determined in advance by a rule (e.g., lowest / highest activated CG setting index), set / indicated by upper-level signaling, or indicated via DCI. For example, the carrier / serving cell / BWP index may be set / indicated by upper-layer signaling (e.g., RRC, MAC CE, etc.) and the CG setting index may be indicated by DCI. For another example, the CG setting index may be set / indicated by upper-layer signaling (e.g., RRC, MAC CE, etc.) and the carrier / serving cell / BWP index may be indicated by DCI. In the corresponding option, the DCI may be an SPS activation DCI that enables SPS PDSCH.

[0296] Opt B: One or more carrier / serving cell / BWPs and / or one or more CG configuration indices may exist. Among these multiple candidates, a UE receiving an SPS PDSCH may select a CG-PUSCH resource that satisfies the condition that it is X after the reference point of the SPS PDSCH (or a separate condition). One or more carrier / serving cell / BWPs are referred to as carrier groups for convenience. Such carrier groups may be defined in advance by a standard document (e.g., all carrier / serving cell / BWPs within the same PUCCH / cell group), defined by a rule (e.g., all carrier / serving cell / BWPs within the same PUCCH / cell group as the DCI or PDSCH), established / indicated by upper-level signaling (one of the multiple pre-established / defined carrier groups), or indicated via the DCI. Additionally, one or more CG configuration indices are referred to as CG groups for convenience. A CG group may be determined by a rule in advance (e.g., all (activated) CG configuration indices belonging to a specific cell (determined by Opt 1)), configured / directed by upper-level signaling (one of the multiple pre-configured / defined CG groups), or directed via DCI. For example, a carrier group may be configured / directed by upper-level signaling (e.g., RRC, MAC CE, etc.) and a CG group may be directed via DCI. For another example, a CG group may be configured / directed by upper-level signaling (e.g., RRC, MAC CE, etc.) and a carrier group may be directed via DCI. In the relevant option, the DCI may be an SPS-enabled DCI that enables SPS PDSCH.

[0297] Opt C: A carrier / serving cell / BWP and / or CG configuration index linked to a single SPS configuration index may be pre-configured. After the UE receives an SPS PDSCH and determines the CG configuration index on the carrier / serving cell / BWP linked to the SPS configuration index to which the SPS PDSCH belongs, the UE may select one CG-PUSCH resource from among the linked CG-PUSCH resources that satisfies the condition that it is X after the reference point of the SPS PDSCH (or a separate condition). Alternatively, a carrier group and / or CG group linked to a single SPS configuration index may be pre-configured. After the UE receives an SPS PDSCH and determines the CG group on the carrier group linked to the SPS configuration index to which the SPS PDSCH belongs, the UE may select one CG-PUSCH resource from among the linked CG-PUSCH resources that satisfies the condition that it is X after the reference point of the SPS PDSCH (or a separate condition).

[0298] Among the multiple SPS PDSCHs activated through the SPS-activated DCI, the first SPS PDSCH is considered a DG-PDSCH and Method #2-1 is applied, and subsequent SPS PDSCHs may be subject to Method #2-2.

[0299] If a UCI containing an A / N for (DG- and / or SPS) PDSCH (hereinafter, (DG- and / or SPS) PDSCH A / N) is configured / instructed to be carried on a specific CG-PUSCH and transmitted according to Method #2-1 and / or Method #2-2 (or if a UCI is configured / instructed to be carried on a specific CG-PUSCH and transmitted regardless of whether the method(s) according to some implementations of the aforementioned specification are applied), the UE may operate to transmit the said CG-PUSCH regardless of whether there is a UL-SCH to be transmitted. Additionally, when a UCI containing (DG- and / or SPS) PDSCH A / N is loaded onto a specific CG-PUSCH according to Method #2-1 and / or Method #2-2 (or when a UCI is loaded onto a specific CG-PUSCH regardless of whether the method(s) according to some implementations of the aforementioned specification are applied), the UE may signal (via the CG-PUSCH) whether the UL-SCH is included in the CG-PUSCH. In one way, a 1-bit indicator / flag may be used to signal the indicator / flag as '1' (or '0') if the UL-SCH is included on the CG-PUSCH, and the indicator / flag as '0' (or '1') if the UL-SCH is not included. The signaling may be encoded separately or jointly coded with a specific UCI type (e.g., A / N, CSI Part 1, CSI Part 2, etc.). For example, it may be signaled in the form of CG-UCI, and if the A / N is not included in the CG-PUSCH, it may be encoded separately, and if the A / N is included in the CG-PUSCH, the A / N and whether it is included in the UL-SCH may be jointly coded.

[0300] If the time / frequency resources of a PUCCH configured / instructed to carry a UCI at a specific time overlap with an (activated and valid) CG-PUSCH transmission occasion (TO), the UE may be configured to transmit the CG-PUSCH (carrying the UCI) regardless of the presence of a UL-SCH. This configuration may be set by a higher-level parameter (e.g., UCI-on-CG-PUSCH). For example, a UE configured / instructed to transmit a CSI PUCCH or an A / N PUCCH in slot n may transmit the CG-PUSCH with the UCI, regardless of the presence of a UL-SCH, if the parameter UCI-on-CG-PUSCH is configured (or enabled) when there is a CG-PUSCH TO that overlaps with the PUCCH. Alternatively, if the parameter UCI-on-CG-PUSCH is not set (or is not enabled), the UCI is carried on the CG-PUSCH only if UL-SCH exists (regardless of whether PUCCH and CG-PUSCH TO overlap), and if UL-SCH does not exist, PUCCH is transmitted (dropping CG-PUSCH).

[0301] The parameter may be configured per carrier / serving cell / BWP index and / or per CG configuration index, or its application per carrier / serving cell / BWP index and / or per CG configuration index may be indicated via DCI. For example, the corresponding upper-level parameter UCI-on-CG-PUSCH may be configured or enabled per carrier / serving cell / BWP index and per CG configuration index. For another example, the corresponding upper-level parameter UCI-on-CG-PUSCH may be configured or enabled per carrier / serving cell / BWP index, and its application per CG configuration index may be indicated via DCI. For yet another example, the corresponding upper-level parameter UCI-on-CG-PUSCH may be configured or enabled per CG configuration index, and its application per carrier / serving cell / BWP index may be indicated via DCI. Here, DCI may be a CG-enabled DCI that enables CG-PUSCH. When the UE is configured / instructed to apply the corresponding operation for a specific carrier / serving cell / BWP index and a CG configuration index, if the time / frequency resource of the PUCCH configured / instructed to carry the UCI at a specific time overlaps with the (enabled and valid) CG-PUSCH TO, the UE transmits the UCI carried on the CG-PUSCH regardless of the presence or absence of UL-SCH. On the other hand, if the UE is configured / instructed that the corresponding operation is not applied for a specific carrier / serving cell / BWP index and a CG configuration index, if the time / frequency resource of the PUCCH to which the UCI is configured / instructed to be carried at a specific time overlaps with the (active and valid) CG-PUSCH TO corresponding to it, the UE may transmit the UCI on the CG-PUSCH only if the UL-SCH exists (regardless of whether the PUCCH and the CG-PUSCH TO overlap), and if the UL-SCH does not exist, the UE may transmit the PUCCH (dropping the CG-PUSCH).

[0302] FIG. 18 is another example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification. Referring to FIG. 18, the BS can activate the CG configuration index #1 set for the UE (S1801) and transmit a DCI that schedules one PDSCH (S1803). The UE receives the PDSCH and, by applying Method #2-1 or Method #2-2, can determine one CG-PUSCH (i.e., CG-PUSCH TO or CG-PUSCH resource) among multiple CG-PUSCHs belonging to CG configuration index #1, taking into account at least the processing time required for A / N generation (S1805). The UE can transmit the CG-PUSCH (from the CG-PUSCH TO or CG-PUSCH resource), including A / N information for the received PDSCH (S1807).

[0303] According to some implementations of this specification, the UE can determine the CG-PUSCH resource to carry A / N information by receiving only the DCI that schedules the PDSCH, thereby minimizing or eliminating additional DCI signaling. This can increase the efficiency of transmitting the BS scheduling information.

[0304] The methods or implementations of the aforementioned specification may be applied independently, but may also be applied in the form of a combination (or merger) of some proposed methods. Information regarding the application of the methods / implements of the aforementioned specification (or information regarding the rules of the methods / implements of the aforementioned specification) may be provided by the BS to the UE via a predefined signal (e.g., a physical layer signal or an upper layer signal). In the aforementioned specification, the upper layer may include one or more of functional layers such as MAC, RLC, PDCP, RRC, SDAP, etc.

[0305] FIG. 19 illustrates the flow of uplink (DL) signal transmission in a UE according to some implementations of the present specification.

[0306] A UE may perform operations according to some implementations of this specification. A UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to some implementations of this specification. A processing device for a UE may include at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to some implementations of this specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by said at least one processor, cause said at least one processor to perform operations according to some implementations of this specification. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.

[0307] In a method performed by the above UE, or in the above UE, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: detecting a downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) (S1901); and transmitting the PUSCH based on the DCI format (S1903). Based on the first field in the DCI format containing a first value, the PUSCH may include uplink shared channel (UL-SCH) data and uplink control channel (UCI). Based on the first field in the DCI format containing a second value, the PUSCH may include the UCI without the UL-SCH data.

[0308] FIG. 20 illustrates the flow of receiving an uplink (DL) signal at a BS according to some implementations of the present specification.

[0309] A BS may perform operations according to some implementations of this specification. A BS may include at least one transceiver; at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to some implementations of this specification. A processing device for a BS may include at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to some implementations of this specification. A computer-readable (non-transient) storage medium may store at least one computer program that includes instructions that, when executed by said at least one processor, cause said at least one processor to perform operations according to some implementations of this specification. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.

[0310] In a method performed by the above BS, or in the above BS, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: transmitting a downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) (S2001); and receiving the PUSCH based on the DCI format (S2003). Based on the first field in the DCI format containing a first value, the PUSCH may include uplink shared channel (UL-SCH) data and uplink control channel (UCI). Based on the first field in the DCI format containing a second value, the PUSCH may include the UCI without the UL-SCH data.

[0311] In some implementations of FIG. 13, FIG. 19, or FIG. 20, the first field may be an identifier field for DCI formats, a time domain resource allocation (TDRA) field, a modulation and coding scheme (MCS) field, or a UL-SCH indicator field.

[0312] In some implementations of FIG. 13, FIG. 19 or FIG. 20, based on the fact that the first field is the identifier field for DCI formats, the first value may be '0' indicating that it is a UL DCI format and the second value may be '1'.

[0313] In some implementations of FIG. 13, FIG. 19 or FIG. 20, based on the fact that the first field is the TDRA field, the first value may be a TDRA entry value associated with PUSCH having UL-SCH data and the second value may be a TDRA entry value associated with PUSCH without UL-SCH data.

[0314] In some implementations of FIG. 13, FIG. 19, or FIG. 20, based on the fact that the first field is the MCS field, the first value may be a value other than a specific value and the second value may be the specific value.

[0315] In some implementations of FIG. 13, FIG. 19 or FIG. 20, based on the fact that the first field is the UL-SCH indicator field, the first value may be '0' and the second value may be '1'.

[0316] In some implementations of FIG. 13, FIG. 19 or FIG. 20, based on the fact that the first field is the UL-SCH indicator field, the first value may be '1' and the second value may be '0'.

[0317] In some implementations of FIG. 13, FIG. 19, or FIG. 20, the DCI format may include a frequency domain resource allocation (FDRA) field for the PDSCH. Based on the fact that the FDRA field associated with the PDSCH contains invalid information, the PDSCH may be determined not to be scheduled.

[0318] In some implementations of FIG. 13, FIG. 19, or FIG. 20, the PUSCH may be transmitted or received based on the field associated with the PDSCH, provided that the FDRA field associated with the PDSCH contains invalid information.

[0319] In some implementations of FIG. 13, FIG. 19, or FIG. 20, the DCI format may include a TDRA field for the PDSCH. Based on the fact that the TDRA field associated with the PDSCH contains invalid information, the PDSCH may be determined not to be scheduled.

[0320] In some implementations of FIG. 13, FIG. 19, or FIG. 20, based on the fact that the TDRA field associated with the PDSCH contains invalid information, the PUSCH may be transmitted or received based on the field associated with the PDSCH.

[0321] In some implementations of FIG. 13, FIG. 19, or FIG. 20, the PUSCH may be transmitted or received within a slot. The DCI format may include a PDSCH-to-HARQ_feedback_timing_indicator field, and the slot may be determined or indicated based on the PDSCH-to-HARQ_feedback_timing_indicator field.

[0322] In some implementations of FIG. 13, FIG. 19 or FIG. 20, the DCI format may include an enhanced Type-3 hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook indicator field, and based on the Type-3 HARQ-ACK codebook being triggered through the enhanced Type-3 HARQ-ACK codebook indicator field, the PUSCH may be transmitted or received based on a field associated with the PDSCH within the DCI format.

[0323] In some implementations of FIG. 13, FIG. 19 or FIG. 20, the DCI may include an enhanced Type-3 HARQ-ACK codebook indicator field, and based on the fact that the Type-3 HARQ-ACK codebook is triggered through the enhanced Type-3 HARQ-ACK codebook indicator field and the FDRA field for the PDSCH contains an invalid value, the PUSCH may be transmitted or received based on the field associated with the PDSCH within the DCI format.

[0324] As described above, the examples of this specification disclosed are provided to enable a person skilled in the art related to this specification to implement and practice this specification. Although the foregoing has been described by reference to the examples of this specification, a person skilled in the art may modify and change the examples of this specification in various ways. Accordingly, this specification is not intended to be limited to the examples described herein, but to be given the broadest possible scope consistent with the principles and novel features disclosed herein.

[0325] Implementations of this specification may be used in wireless communication systems, BS or user devices, and other equipment.

Claims

1. A method performed by user equipment (UE), Detect a downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and It includes transmitting the PUSCH based on the above DCI format, Based on the fact that the first field in the above DCI format includes a first value, the PUSCH includes uplink shared channel (UL-SCH) data and uplink control channel (UCI) data, and Based on the fact that the first field in the above DCI format includes a second value, the PUSCH includes the UCI without the UL-SCH data, method.

2. In Paragraph 1, The first field is an identifier field for DCI formats, a time domain resource allocation (TDRA) field, a modulation and coding scheme (MCS) field for the PUSCH, or a UL-SCH indicator field, method.

3. In Paragraph 2, Based on the fact that the first field is the identifier field for DCI formats, the first value is '0' indicating that it is a UL DCI format and the second value is '1', method.

4. In Paragraph 2, Based on the fact that the first field is the TDRA field, the first value is a TDRA entry value associated with PUSCH having UL-SCH data and the second value is a TDRA entry value associated with PUSCH without UL-SCH data, method.

5. In Paragraph 2, Based on the fact that the first field is the MCS field, the first value is a value other than a specific value and the second value is the specific value, method.

6. In Paragraph 2, Based on the fact that the first field is the UL-SCH indicator field, the first value is '0' and the second value is '1', method.

7. In Paragraph 2, Based on the fact that the first field is the UL-SCH indicator field, the first value is '1' and the second value is '0', method.

8. In Paragraph 1, The above DCI format includes a frequency domain resource allocation (FDRA) field for the above PDSCH, and the method is: Further comprising determining that the PDSCH is not scheduled based on the fact that the FDRA field associated with the PDSCH contains invalid information, method.

9. In Paragraph 8, Based on the fact that the FDRA field associated with the above PDSCH contains invalid information, the PUSCH is transmitted based on the field associated with the above PDSCH, method.

10. In Paragraph 1, The above DCI format includes a TDRA field for the above PDSCH, and the method is: Further comprising determining that the PDSCH is not scheduled based on the fact that the TDRA field associated with the PDSCH contains invalid information, method.

11. In Paragraph 10, Based on the fact that the TDRA field associated with the above PDSCH contains invalid information, the above PUSCH is transmitted based on the field associated with the above PDSCH, method.

12. In Paragraph 1, The above PUSCH is transmitted within the slot, and The above DCI format includes a PDSCH-to-HARQ_feedback timing indicator field, and The above slot is determined based on the above PDSCH-to-HARQ_feedback timing indicator field, method.

13. In Paragraph 1, The above DCI format includes an enhanced Type-3 hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook indicator field, and Based on the Type-3 HARQ-ACK codebook being triggered via the aforementioned enhanced Type-3 HARQ-ACK codebook indicator field, the PUSCH is transmitted based on the field associated with the PDSCH within the DCI format, method.

14. In Paragraph 1, The above DCI includes an enhanced Type-3 HARQ-ACK codebook indicator field, and Based on the fact that the Type-3 HARQ-ACK codebook is triggered through the enhanced Type-3 HARQ-ACK codebook indicator field and the FDRA field for the PDSCH contains an invalid value, the PUSCH is transmitted based on the field associated with the PDSCH within the DCI format, method.

15. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Detect a downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and It includes transmitting the PUSCH based on the above DCI format, Based on the fact that the first field in the above DCI format includes a first value, the PUSCH includes uplink shared channel (UL-SCH) data and uplink control channel (UCI) data, and Based on the fact that the first field in the above DCI format includes a second value, the PUSCH includes the UCI without the UL-SCH data, User device.

16. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Detect a downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and It includes transmitting the PUSCH based on the above DCI format, Based on the fact that the first field in the above DCI format includes a first value, the PUSCH includes uplink shared channel (UL-SCH) data and uplink control channel (UCI) data, and Based on the fact that the first field in the above DCI format includes a second value, the PUSCH includes the UCI without the UL-SCH data, Processing unit.

17. In a computer-readable non-transitory storage medium, The above storage medium stores at least one program code including instructions that cause at least one processor to perform operations when executed, and said operations are: Detect a downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and It includes transmitting the PUSCH based on the above DCI format, Based on the fact that the first field in the above DCI format includes a first value, the PUSCH includes uplink shared channel (UL-SCH) data and uplink control channel (UCI) data, and Based on the fact that the first field in the above DCI format includes a second value, the PUSCH includes the UCI without the UL-SCH data, Storage medium.

18. In a method performed by a base station (BS), Transmit downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and It includes receiving the PUSCH based on the above DCI format, Based on the fact that the first field in the above DCI format includes a first value, the PUSCH includes uplink shared channel (UL-SCH) data and uplink control channel (UCI) data, and Based on the fact that the first field in the above DCI format includes a second value, the PUSCH includes the UCI without the UL-SCH data, method.

19. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Transmit downlink control information (DCI) format capable of simultaneous scheduling of a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH); and It includes receiving the PUSCH based on the above DCI format, Based on the fact that the first field in the above DCI format includes a first value, the PUSCH includes uplink shared channel (UL-SCH) data and uplink control channel (UCI) data, and Based on the fact that the first field in the above DCI format includes a second value, the PUSCH includes the UCI without the UL-SCH data, Base station.