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

Abstract

The UE may: receive first information about a RAT associated with PUCCH resources to be used until a dedicated PUCCH configuration is acquired, and second information associated with a PUCCH resource set index; receive downlink control information (DCI) for scheduling a PDSCH; determine a PUCCH resource for HARQ-ACK information for the PDSCH on the basis of the first information, the second information, and a PUCCH resource index included in the DCI; and transmit the HARQ-ACK information on the basis of the determined PUCCH resource.

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 the efficient use of uplink resources in a spectrum where existing communication systems and new communication systems coexist.

[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 above operations may include: receiving first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) setting, and second information regarding a PUCCH resource set index; receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); determining a PUCCH resource for hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource index included in the DCI; and transmitting the HARQ-ACK information based on the determined PUCCH resource.

[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 operablely connectable to said at least one processor and, when executed, storing instructions that cause said at least one processor to perform operations. The method or said operations include: transmitting first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) configuration, and second information regarding a PUCCH resource set index; transmitting downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); and based on the first information, the second information and the PUCCH resource associated with the PUCCH resource index included in the DCI, it may include receiving hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH.

[0008] In each aspect of the specification, the first information may include a value related to the first RAT or a value related to the second RAT.

[0009] In each aspect of the specification, the value associated with the first RAT may be a value for a first table for a plurality of PUCCH resource sets for the first RAT, and the value associated with the second RAT may be a value for a second table for a plurality of PUCCH resource sets for the second RAT.

[0010] In each aspect of the specification, the value associated with the first RAT may be a value relating to a first row range in the table, and the value associated with the second RAT may be a value relating to a second row range in the table, wherein the first row range may include rows respectively associated with a plurality of PUCCH resource sets for the first RAT, and the second row range may include rows respectively associated with a plurality of PUCCH resource sets for the second RAT.

[0011] In each aspect of the present specification, the first information may be received / transmitted through a system information block 1 (SIB) or a DCI that schedules system information.

[0012] In each aspect of the specification, the second information may be received / transmitted through system information block 1 (SIB).

[0013] In each aspect of the present specification, the first information may be received / transmitted through a random access response (RAR) of a random access process or a DCI that schedules a PDSCH carrying message 4 of the random access process.

[0014] In each aspect of the present specification, the PUCCH resource set associated with the PUCCH resource set index may include a plurality of PUCCH resources for the first RAT and a plurality of PUCCH resources for the second RAT, and the value associated with the first RAT may be a value associated with the plurality of PUCCH resources for the first RAT, and the value associated with the second RAT may be a value associated with the plurality of PUCCH resources for the second RAT.

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

[0016] According to some implementations of the present specification, methods and devices for the efficient use of uplink resources in a spectrum where existing communication systems and new communication systems coexist may be provided.

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

[0018] 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:

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

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

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

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

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

[0024] 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;

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

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

[0027] Fig. 9 illustrates the hybrid automatic repeat request - acknowledgment (HARQ-ACK) transmission / reception process;

[0028] FIG. 10 is an example of a signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification;

[0029] FIG. 11 is another example of a signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification;

[0030] FIG. 12 is another example of a signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification;

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

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

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

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

[0035] 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."

[0036] 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."

[0037] 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."

[0038] 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."

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

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

[0041] 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 base station and the UE.

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

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

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

[0045] 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.321, 3GPP TS 38.331, etc.

[0046] 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."

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

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

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

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

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

[0052] 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).

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

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

[0055] 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 (PCCH), 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.

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

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

[0058] Since the communication device receives the synchronization signal (SS), demodulation reference signal (DMRS), channel state information reference signal (CSI-RS), positioning reference signal (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.

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

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

[0061] 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).

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

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

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

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

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

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

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

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

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

[0071] 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).

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

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

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

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

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

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

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

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

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

[0081] 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 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 ).

[0082]

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

[0084]

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

[0086] 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. The carrier may contain up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the enabled BWPs, and only a predetermined number (e.g., 1) of the BWPs configured for the UE may be enabled on the carrier.

[0087] 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 +RB start 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.

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

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

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

[0091]

[0092] Figure 6 illustrates physical channels used in a 3GPP-based communication system, which is an example of a wireless communication system, and the signal transmission / reception process using them.

[0093] A UE that has been turned on again after being turned off or has lost connection with a wireless communication system first performs an initial cell search process, such as searching for a suitable cell to camp on and synchronizing with said cell or the BS of said cell (S11). During the initial cell search process, the UE receives a synchronization signal block (SSB) (also called an SSB / PBCH block) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). Based on the PSS / SSS, the UE synchronizes with the BS and obtains information such as the cell identifier (ID). Additionally, the UE can obtain broadcast information within the cell based on the PBCH. Meanwhile, during the initial cell search process, the UE can receive a downlink reference signal (DL RS) to check the downlink channel status.

[0094] After completing the initial cell search, the UE can camp on the cell. After camping on the cell, the UE monitors the PDCCH on the cell and receives the PDSCH according to the downlink control information (DCI) carried by the PDCCH to obtain more specific system information (S12).

[0095] Subsequently, the UE may perform a random access procedure to complete access to the BS (S13 to S16). For example, during the random access procedure, the UE may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble through a PDCCH and a corresponding PDSCH (S14). If the reception of the RAR for the UE fails, the UE may attempt to re-transmit the preamble. In the case of contention-based random access, a contention resolution procedure (S16) may be performed, which includes transmitting a PUSCH based on the UL resource allocation included in the RAR (S15) and receiving a PDCCH and a corresponding PDSCH.

[0096] A UE that has performed the procedure described above may subsequently perform the reception of PDCCH / PDSCH (S17) and the transmission of PUSCH / PUCCH (S18) as part of a general uplink / downlink signal transmission process. The control information transmitted by the UE to the BS is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK) (also called HARQ-ACK), scheduling request (SR), channel state information (CSI), etc. CSI may include channel quality indicator (CQI), precoding matrix indicator (PMI), and / or rank indicator, etc. UCI is generally transmitted via PUCCH, but may be transmitted via PUSCH if control information and traffic data need to be transmitted simultaneously. In addition, the UE can transmit UCI atypically via PUSCH based on network requests / instructions.

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

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

[0099] - 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) repeat with a period of 20 ms. Based on the MIB, the UE can determine whether a control resource set (CORESET) exists for the Type0-PDCCH common search space. For example, the field ssb-SubcarrierOffset within the MIB is k, which is a frequency domain offset in units of the number of subcarriers between the SSB and the overall resource block grid. SSB Corresponds to. Upon detection of an SS / PBCH block, the UE, in the case of FR1, k SSB If < 24, or in the case of FR2, k SSBIf < 12, it can be determined that a CORESET exists for the Type-0 PDCCH common search space (CSS) set, and for FR1, k SSB If > 23, or in the case of FR2, k SSB If > 11, it can be determined that a Type-0 PDCCH CSS set does not exist. The Type-0 PDCCH common seek space is a type of PDCCH seek space and is used to transmit PDCCHs that schedule SI messages. If a Type-0 PDCCH common seek space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbols that constitute a 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 Type-0 PDCCH common seek space does not exist, pdcch-ConfigSIB1 provides information regarding frequency locations where SSB / SIB1 exists and frequency ranges where SSB / SIB1 does not exist.

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

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

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

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

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

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

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

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

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

[0109] The UE can receive information regarding random access from the BS through system information. For example, information regarding 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 (RA Occasion, RO) and the random access preamble index (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.

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

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

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

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

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

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

[0116] 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).

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

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

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

[0120] 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).

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

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

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

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

[0125] 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 and 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.

[0126] 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).

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

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

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

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

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

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

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

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

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

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

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

[0138] -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).

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

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

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

[0142] FIG. 9 illustrates the HARQ-ACK transmission / reception process. Referring to FIG. 9, 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).

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

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

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

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

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

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

[0149] 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 for the 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.

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

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

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

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

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

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

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

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

[0158] - Channel state information (CSI): Feedback information for downlink channels. CSI may include channel quality information (CQI), rank indicator (RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH resource block indicator (SSBRI), layer indicator (LI), etc.

[0159] - Link recovery request (LRR)

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

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

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

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

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

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

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

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

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

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

[0170] - 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).

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

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

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

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

[0175] - Transmission Structure: DMRS and UCI are configured / mapped within the same symbol in the form of Frequency Division Multiplex (FDM). 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.

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

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

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

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

[0180] - 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).

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

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

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

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

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

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

[0187] 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).

[0188]

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

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

[0191]

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

[0193]

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

[0195] 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 ).

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

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

[0198] ...

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

[0200] 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).

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

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

[0203] 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)).

[0204] As previously mentioned, before receiving the configuration regarding the dedicated PUCCH resource, the UE may receive an index value corresponding to one of the rows in Table 5 from the BS via SIB1 (or upper-layer signaling). Each row (or index) in Table 5 corresponds to a set of PUCCH resources, and one resource set consists of a total of 16 PUCCH resources. The value △ indicated by the DCI scheduling the PDSCH carrying Msg4 (hereinafter, Msg4 PDSHC) during the random access process, or the DCI scheduling the PDSCH. PRI∈ {0,1,...,7} and the first CCE index n of PDCCH CCE,0 ∈ {0,1,...,N CCE Combination of {-1} (e.g., r PUCCH = floor{(2*n CCE,0 ) / N CCE} + 2*△ PRI One of the 16 PUCCH resources may be determined by ). In this specification, the PUCCH resources used by the UE before the settings for the dedicated PUCCH resources are provided are referred to as the initial PUCCH resources, and the set of PUCCH resources consisting of the initial PUCCH resources is referred to as the initial PUCCH resource set.

[0205] Typically, a specific spectrum is utilized exclusively for a specific radio access technology (RAT) (e.g., LTE spectrum, 5G spectrum, etc.). The non-access stratum (NAS) layer of a UE, which has been powered off and then turned back on or disconnected from the wireless communication system, selects a public land mobile network (PLMN) (or standalone non-public network (SNPN)) to access the network and transmits information regarding the selected PLMN (or SNPN) and its associated RAT (e.g., NR, LTE, etc.) to the access stratum (AS) layer to control which RAT is used for initial search during cell discovery. The AS layer of the UE scans specific frequency bands (e.g., all radio frequency (RF) channels in the NR band) suitable for the corresponding RAT according to its supported capabilities. The UE detects synchronization signals and broadcast channels suitable for the specific RAT and performs synchronization. A UE that has successfully synchronized with a cell can receive broadcast system information (e.g., SIB) transmitted by the cell, and the broadcast system information includes one or more PLMN identifiers or SNPN identifiers. The AS layer of the UE aggregates the list of PLMNs (or SNPNs) received via the broadcast channel and the RAT information associated with the corresponding network and reports it to the upper layer, the NAS. If the BS is shared by multiple operators, the cell broadcasts a list of core network operators that the UE(s) can select via the broadcast system information, and the UE decodes this system information to identify available network operators and RAT environments and utilizes a network selection procedure.A UE is configured with PUCCH resources limited to the RAT associated with the network it has connected to. For example, a UE connected to a network via a 5G RAT is provided with initial PUCCH resource(s) for 5G and performs PUCCH transmissions based on said initial PUCCH resource(s) until it is provided with dedicated PUCCH resource configurations.

[0206] As candidates for spectrum for 6G communication, methods such as refarming spectrum used by 5G systems or using new spectrum not utilized by existing cellular networks are being discussed. Considering that spectrum used by existing 5G systems offers benefits in terms of securing coverage, a method in which 5G and 6G systems coexist within that spectrum (especially from a BS perspective) is receiving attention. This method of spectrum sharing is called multi-RAT spectrum sharing (MR-SS).

[0207] When a BS reallocates legacy RAT spectrum (e.g., 5G spectrum) to simultaneously service legacy UEs (e.g., 5G UEs) and UEs connected to a new RAT (e.g., 6G UEs), it may be more efficient for the BS to use the initial PUCCH resources for legacy RATs (hereinafter referred to as legacy initial PUCCH resources) for new RAT UEs rather than using them only for legacy RAT UEs. For example, in a band that supports both 5G and 6G, if there are few 5G UEs and many 6G UEs among the UEs connected or attempting to connect, the BS can allocate some of the 5G initial PUCCH resources to 6G UEs, allowing more UEs to be serviced in that band compared to when it is proposed to allocate only the initial PUCCH resources for 6G to 6G UEs.

[0208] As such, in an MR-SS situation, for example, where 5G spectrum is reallocated to allow a BS to service 5G UEs and 6G UEs simultaneously, it may be advantageous in terms of resource efficiency to have the BS transmit PUCCH (particularly, initial PUCCH) to the 5G UE and 6G UE in the same / adjacent frequency / time domain. For example, if the same time / frequency resources can be provided identically as the initial PUCCH resources used by the 5G UE and the initial PUCCH resources used by the 6G UE, resource efficiency can be increased because the initial PUCCH resource #1 from the 5G UE and the initial PUCCH resource #2 from the 6G UE can be code division multiplexed (CDM) within the same time / frequency resources. Furthermore, from the perspective of BS reception and UE transmission, separate additional implementation may not be required for 6G PUCCH reception / transmission (compared to 5G PUCCH), thus reducing the complexity of 6G implementation.

[0209] Accordingly, some implementations of this specification regarding efficient initial PUCCH transmission / reception considering MR-SS operation are described below. For convenience of explanation, some implementations of this specification are described below using the example where the legacy RAT is 5G and the new RAT is 6G, but some implementations of this specification may also be applied to spectrums where different RATs coexist.

[0210] <Method #1> Semi-static Initial PUCCH Setup

[0211] (For the purpose of efficient MR-SS operation of BS) Table #A for the initial PUCCH resource set configuration identical to Table 5 and a separate Table #B for 6G UEs may be defined. Here, Table #A may be designed / defined for 6G UEs to overcome the limitations of existing 5G initial PUCCH resources (e.g., a fixed number of symbols, a fixed start symbol index, etc.).

[0212] In some implementations, BS may set a 1-bit indicating whether it is Table #A or Table #B via SIB1 (or higher-layer signaling such as PBCH / RRC) and additionally set an initial PUCCH resource set index corresponding to a row within the configured table. Whether it is Table #A or Table #B may be signaled explicitly as a 1-bit within SIB1 (or higher-layer signaling such as RRC) (or within the DCI scheduling SI), or may be implicitly signaled if the UE can recognize whether it is a 5G-6G MR-SS situation in PSS / SSS / PBCH / sync raster, etc. For example, if table #A is set via a 1-bit within SIB1 (or upper-layer signaling such as PBCH / RRC) (or within the DCI scheduling system information (SI)) and index #k is set, the UE can assume an initial PUCCH resource set corresponding to index #k of table 5 and perform a HARQ feedback operation using one of the 16 initial PUCCH resources within that resource set until a dedicated PUCCH resource is provided from the BS. For another example, if table #B is set via a 1-bit within SIB1 (or upper-layer signaling such as PBCH / RRC) (or within the DCI scheduling SI) and index #k is set, the UE can assume an initial PUCCH resource set corresponding to index #k of the new table defined for 6G initial PUCCH and perform a HARQ feedback operation using one of the 16 initial PUCCH resources within that resource set until a dedicated PUCCH resource is provided from the BS.As another example, when a UE determines whether a 5G-6G MR-SS situation exists in PSS / SSS / PBCH / sync raster, etc. (e.g., when the UE determines that it is an MR-SS situation based on the cell index value corresponding to PSS / SSS or the sync raster frequency value being N), if index #k is set / indicated within SIB1 (or upper layer signaling such as PBCH / RRC, etc.) (or within the DCI scheduling SI), the UE can assume an initial PUCCH resource set corresponding to index #k in Table 5 and perform a HARQ feedback operation using one of the 16 initial PUCCH resources within that resource set until a dedicated PUCCH resource is provided from the BS.

[0213] Alternatively, BS may construct a new table for the initial PUCCH resource sets, wherein some of the initial PUCCH resource sets within the new table may consist of all or part of the rows of Table 5 (for efficient MR-SS operation) and the remainder may be defined as separate row(s) for 6G UEs. Here, the separate row(s) for 6G UEs may be designed / defined for 6G UEs to overcome the limitations of existing 5G initial PUCCH resources (e.g., a fixed number of symbols, a fixed starting symbol index, etc.). For example, row indices 0 through 15 of the new table may be configured identically to 0 through 15 of Table 5, and row indices 16 through 31 of the new table may consist of new initial PUCCH resource sets for 6G. For example, if index #k1 (e.g., k1 is an integer value between 0 and 15) is set from within SIB1 (or upper-level signaling such as PBCH / RRC) (or within the DCI scheduling SI), the UE can assume an initial PUCCH resource set corresponding to index #k1 in Table 5 (i.e., an initial PUCCH resource set corresponding to the row with index #k1 among the rows of the new table) and perform a HARQ feedback operation using one of the 16 initial PUCCH resources in that resource set until a dedicated PUCCH resource is provided from BS. As another example, if index #k2 (e.g., k2 is an integer value between 16 and 31) is set within SIB1 (or upper-layer signaling such as PBCH / RRC) (or within the DCI scheduling SI), the UE can assume an initial PUCCH resource set defined for 6G initial PUCCH (i.e., an initial PUCCH resource set corresponding to the row with index #k2 among the rows of the new table) and perform a HARQ feedback operation using one of the 16 initial PUCCH resources within that resource set until a dedicated PUCCH resource is provided from the BS.

[0214] <Method #2> Dynamic switching

[0215] When 5G initial PUCCH transmission is established using a semi-static method as in Method #1, there may be a disadvantage that even if only the 6G UE transmits the initial PUCCH (at a specific time point) in an MR-SS environment, the 6G UE will transmit the 5G initial PUCCH. However, if the BS can operate the spectrum by utilizing separate resources between the 5G UE and the 6G UE through methods such as time division multiplex (TDM) even in an MR-SS environment, it becomes possible to maximize resource efficiency by transmitting the 5G initial PUCCH that is CDM-enabled between the 5G UE and the 6G UE at time point #1, and transmitting only the 6G initial PUCCH at time point #2. Therefore, in some implementations of this specification, dynamic switching between the 5G initial PUCCH and the 6G initial PUCCH (compared to Method #1) may be allowed to support such BS operation. Some implementations of this specification regarding dynamic switching between initial PUCCH resources for different RATs are described below.

[0216] In some implementations of this specification, two tables may be defined as in Method #1. For example, Table #A for configuring an initial PUCCH resource set identical to Table 5 and a separate Table #B for 6G UEs may be defined (for the purpose of efficient MR-SS operation of the BS). Here, Table #B may be designed / defined for 6G UEs to overcome the limitations of existing 5G initial PUCCH resources (e.g., a fixed number of symbols, a fixed starting symbol index, etc.). The BS may set an initial PUCCH resource set index corresponding to a single row in Table #A or Table #B via SIB1 (or higher-layer signaling such as PBCH / RRC). Whether it is Table #A or Table #B can be indicated by a random access response (RAR) (e.g., a DCI scrambled with RA-RNTI (having CRC) or a PDSCH scheduled by said DCI), or a DCI scheduling a PDSCH carrying Msg4 (hereinafter referred to as Msg4 PDSCH), or a DCI scheduling a PDSCH. For example, if index #k is set within SIB1 (or upper layer signaling such as PBCH / RRC) (or within the DCI scheduling SI), and the UE is indicated by a 1-bit indicator within RAR (e.g., a DCI scrambled with RA-RNTI (with CRC) or a PDSCH scheduled by that DCI), or a DCI scheduling Msg4 PDSCH, or a DCI scheduling PDSCH, then the UE may assume an initial PUCCH resource set corresponding to index #k in Table #A (e.g., Table 5) and perform a HARQ feedback operation using one of the 16 initial PUCCH resources within that resource set (until a dedicated PUCCH resource is provided from BS).As another example, if index #k is set within SIB1 (or upper layer signaling such as PBCH / RRC) (or within a DCI scheduling SI), and the UE is indicated by a 1-bit indicator within RAR (e.g., a DCI scrambled with RA-RNTI (with CRC) or a PDSCH scheduled by that DCI), or a DCI scheduling Msg4 PDSCH, or a DCI scheduling PDSCH, the UE may assume an initial PUCCH resource set corresponding to index #k of Table #B defined for 6G initial PUCCH and perform a HARQ feedback operation using one of the 16 initial PUCCH resources within that resource set (until a dedicated PUCCH resource is provided from the BS).

[0217] Alternatively, in some implementations, a method may be considered where 5G initial PUCCH and 6G initial PUCCH are distinguished at the initial PUCCH resource level rather than through signaling at the initial PUCCH resource set level. In some implementations, the number of initial PUCCH resources included within a single initial PUCCH resource set may be increased to X (e.g., X > 16) (instead of 16 in 5G NR). In this case, initial PUCCH resources #0 through #15 are configured identically to 5G NR, while initial PUCCH resources #16 through {X-1} may be defined separately for 6G UEs. The BS can set the initial PUCCH resource set index #k via SIB1 (or higher-layer signaling such as PBCH / RRC). RAR (e.g., DCI scrambled with RA-RNTI (with CRC) or PDSCH scheduled by said DCI), or Msg4 DCI scheduling PDSCH, or DCI scheduling PDSCH, may indicate whether the initial PUCCH resource index is within indices #0 to 15 or within indices #16 to {X-1}. For example, if index #k is set within SIB1 (or upper layer signaling such as PBCH / RRC) (or within a DCI scheduling SI), and '0' (or '1') is indicated by a 1-bit indicator within a RAR (e.g., a DCI scrambled with RA-RNTI (with CRC) or a PDSCH scheduled by that DCI), or a DCI scheduling Msg4 PDSCH, or a DCI scheduling PDSCH, the UE may assume an initial PUCCH resource set corresponding to index #k (in Table 5) and perform a HARQ feedback operation using one of the initial PUCCH resource indices #0 through #15 within that resource set (until a dedicated PUCCH resource is provided from BS).As another example, if index #k is set within SIB1 (or upper layer signaling such as PBCH / RRC) (or within the DCI scheduling SI), and the UE receives '1' (or '0') through a 1-bit indicator within RAR (e.g., a DCI scrambled with RA-RNTI (with CRC) or a PDSCH scheduled by that DCI), or a DCI scheduling Msg4 PDSCH, or a DCI scheduling PDSCH, the UE may assume an initial PUCCH resource set corresponding to index #k (in Table 5 or a new table defined for 6G UEs) and perform a HARQ feedback operation using one of the initial PUCCH resource indices #16 to {X-1} within that resource set (until a dedicated PUCCH resource is provided from the BS).

[0218] Alternatively, in some implementations, even if 5G initial PUCCH and 6G initial PUCCH are distinguished at the initial PUCCH resource level, the number of initial PUCCH resources within a single initial PUCCH resource set may be maintained at 16. In this case, initial PUCCH resource indices #0 to {Y-1} are configured identically to some Y of the initial PUCCH resource indices #0 to 15 defined in 5G NR, and initial PUCCH resource indices #Y to 15 may be defined separately for 6G UE use. The initial PUCCH resources corresponding respectively to initial PUCCH resource indices #0 to {Y-1} may be defined as the first Y initial PUCCH resources belonging to each initial PUCCH resource set (of Table 5). Alternatively, a correspondence relationship between initial PUCCH resource indices #0 to {Y-1} and the initial PUCCH resources of Table 5 may be defined separately. For example, the first Y even indices (or odd indices) among the 5G initial PUCCH resources may be defined or set as the initial PUCCH resource indices #0 to {Y-1}. In the case of existing 5G initial PUCCH resources, the PUCCH resources of the first 8 indices are mapped sequentially from the lower index PRB to the higher index PRB, and the PUCCH resources of the last 8 indices are mapped sequentially from the higher index PRB to the lower index PRB. Therefore, if the 5G PUCCH resources of the even (or odd) indices are mapped sequentially to the initial PUCCH resource indices #0 to {Y-1} rather than the existing 5G initial PUCCH resources being mapped sequentially to the initial PUCCH resource indices #0 to {Y-1}, there may be an effect of evenly distributing the hopping direction. BS can set the initial PUCCH resource set index #k through SIB1 (or higher-layer signaling such as PBCH / RRC).RAR (e.g., DCI scrambled with RA-RNTI (with CRC) or PDSCH scheduled by said DCI), or Msg4 DCI scheduling PDSCH, or DCI scheduling PDSCH, may indicate whether the initial PUCCH resource index is within indexes #0 to {Y-1} or indexes #Y to 15. For example, if index #k is set within SIB1 (or upper layer signaling such as PBCH / RRC) (or within the DCI scheduling SI), and the UE determines the value of one of the initial PUCCH resource indices #0 to {Y-1} through RAR (e.g., the DCI scrambled with RA-RNTI (having CRC) or the PDSCH scheduled by that DCI), or the DCI scheduling Msg4 PDSCH, or the DCI scheduling PDSCH, then the UE can perform a HARQ feedback operation by utilizing one of the initial PUCCH resources defined in 5G within the initial PUCCH resource set corresponding to index #k (of Table 5) (until a dedicated PUCCH resource is provided from the BS). As another example, if index #k is set within SIB1 (or upper-layer signaling such as PBCH / RRC) (or within the DCI scheduling SI), and the UE determines a value among the initial PUCCH resource indices #Y to 15 through RAR (e.g., the DCI scrambled with RA-RNTI (with CRC) or the PDSCH scheduled by that DCI), or the DCI scheduling Msg4 PDSCH, or the DCI scheduling PDSCH, then (until a dedicated PUCCH resource is provided from the BS) the UE can perform a HARQ feedback operation by utilizing one of the newly defined initial PUCCH resources in 6G within the initial PUCCH resource set corresponding to index #k (of Table 5 or the new table defined for 6G UE).

[0219] Alternatively, in some implementations, even if 5G initial PUCCH and 6G initial PUCCH are distinguished at the initial PUCCH resource level, the number of initial PUCCH resources within a single initial PUCCH resource set may be maintained at 16. In this case, the PUCCH resources of the even indices (e.g., indices #0, 2, 4, 6, 8, 10, 12, 14) (or odd indices (e.g., indices #1, 3, 5, 7, 9, 11, 13, 15)) among the initial PUCCH resources are configured identically to the 5G initial PUCCH resources of the even (or odd) indices among the initial PUCCH resource indices #0–15 defined in 5G NR, and the PUCCH resources of the remaining odd (or even) indices may be defined separately for 6G UEs.

[0220] FIG. 10 is an example of a signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification. Referring to FIG. 10, the network (e.g., BS) may provide the UE(s) with first information regarding which RAT the initial PUCCH resources on the cell are associated with, and second information regarding an index of the initial PUCCH resource set (S1001). The BS may provide third information regarding an index of the PUCCH resource for transmitting HARQ-ACK information for the PDSCH through a DCI that schedules the PDSCH (S1003). A UE that does not have a dedicated PUCCH setting may determine an initial PUCCH resource for transmitting HARQ-ACK information for the PDSCH based on the first to third information (S1005), and may transmit the HARQ-ACK information for the PDSCH through the determined initial PUCCH resource (S1007).

[0221] FIG. 11 is another example of a signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification. In particular, FIG. 11 is an example of a signal transmission / reception flow according to FIG. 10 embodied according to some implementations of the present specification regarding initial PUCCH resource set level signaling. Referring to FIG. 11, the BS can set one of Table #A (for a 5G UE in MR-SS) or Table #B (for a 6G UE) via a SIB (e.g., SIB1) and set one of the row indices of the corresponding table (i.e., initial PUCCH resource set index) (S1101). When the UE receiving this receives a DCI scheduling Msg4 PDSCH while performing a random access procedure, a PUCCH resource index #m can be determined based on the said DCI (S1103). A UE can determine one initial PUCCH resource based on the table index obtained from the SIB, the initial PUCCH resource set index, and the PUCCH resource index #m determined from the DCI (S1105). A UE that has successfully received Msg4 PDSCH can transmit the corresponding HARQ-ACK information through the determined initial PUCCH resource (S1107).

[0222] FIG. 12 is another example of a signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification. In particular, FIG. 12 is an example of a signal transmission / reception flow according to FIG. 10 embodied according to some implementations of the present specification regarding initial PUCCH resource level signaling. Referring to FIG. 12, the BS may provide second information related to an index of an initial PUCCH resource set for a cell via a SIB (e.g., SIB1) (S1201), and may provide first information related to which initial PUCCH resources associated with a RAT a UE (e.g., 6G UE) should use via a RAR (e.g., a DCI scrambled with RA-RNTI (having CRC) or a PDSCH scheduled by said DCI) or a DCI scheduling a Msg4 PDSCH or a DCI scheduling a PDSCH (S1202). The above UE may obtain third information related to a PUCCH resource index from a DCI that schedules the PDSCH (S1203). Here, the DCI containing the third information may be a DCI containing the second information, or a different DCI that schedules a different PDSCH. A UE without a dedicated PUCCH setting may determine an initial PUCCH resource for HARQ-ACK information for a PDSCH scheduled by the DCI containing the third information based on the first and second information until it receives a dedicated PUCCH setting (S1205). The UE may transmit HARQ-ACK information for a PDSCH scheduled by the DCI containing the third information through the determined initial PUCCH resource (S1207).

[0223] 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. For example, Method #1 and Method #2 may each be applied independently, or two or more may be applied together. 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 stipulated to be communicated 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, and SDAP.

[0224] According to some implementations of this specification, in an MR-SS environment, the initial PUCCH resources used by legacy UEs (e.g., 5G UEs) and the initial PUCCH resources used by new UEs (e.g., 6G UEs) may be provided in the same spectrum. This allows the initial PUCCH resources from legacy UEs and new UEs to be code division multiplexed (CDM) within the same time / frequency resources, thereby increasing resource efficiency. Additionally, according to some implementations of this specification, separate additional implementation may not be required for PUCCH reception / transmission of new RATs (e.g., 6G) from the perspective of BS reception and UE transmission (compared to 5G PUCCH), thus reducing the implementation complexity of the new RAT. Alternatively, according to some implementations of this specification, the BS may utilize resources more flexibly than the PUCCH resources for legacy RATs by setting separate initial PUCCH resources in an environment where only new UEs exist.

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

[0226] A UE may perform operations according to some implementations of this specification in relation to UL signal transmission. 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.

[0227] 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 are: receiving first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) setting, and second information regarding a PUCCH resource set index (S1301); receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) (S1303); determining a PUCCH resource for hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource index contained in the DCI; and may include transmitting the HARQ-ACK information based on the determined PUCCH resource (S1307).

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

[0229] A BS may perform operations according to some implementations of this specification in relation to receiving a UL signal. 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 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.

[0230] 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 first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) setting, and second information regarding a PUCCH resource set index (S1401); transmitting downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) (S1403); and receiving hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the PUCCH resources associated with the PUCCH resource index included in the first information, the second information, and the DCI (S1407).

[0231] In some implementations related to FIG. 13 or FIG. 14, the first information may include a value related to the first RAT or a value related to the second RAT.

[0232] In some implementations related to FIG. 13 or FIG. 14, the value related to the first RAT may be a value related to a first table for a plurality of PUCCH resource sets for the first RAT, and the value related to the second RAT may be a value related to a second table for a plurality of PUCCH resource sets for the second RAT.

[0233] In some implementations related to FIG. 13 or FIG. 14, the value related to the first RAT may be a value related to a first row range in the table, and the value related to the second RAT may be a value related to a second row range in the table, the first row range may include rows related respectively to a plurality of PUCCH resource sets for the first RAT, and the second row range may include rows related respectively to a plurality of PUCCH resource sets for the second RAT.

[0234] In some implementations related to FIG. 13 or FIG. 14, the first information may be received / transmitted through a system information block 1 (SIB) or a DCI that schedules system information.

[0235] In some implementations related to FIG. 13 or FIG. 14, the second information may be received / transmitted through system information block 1 (SIB).

[0236] In some implementations related to FIG. 13 or FIG. 14, the first information may be received / transmitted through a DCI that schedules a random access response (RAR) of a random access process or a PDSCH carrying message 4 of the random access process.

[0237] In some implementations related to FIG. 13 or FIG. 14, the PUCCH resource set associated with the PUCCH resource set index may include a plurality of PUCCH resources for the first RAT and a plurality of PUCCH resources for the second RAT, and the value associated with the first RAT may be a value associated with the plurality of PUCCH resources for the first RAT, and the value associated with the second RAT may be a value associated with the plurality of PUCCH resources for the second RAT.

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

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

Claims

1. In a method performed by user equipment (UE), The above UE receives first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) setting are associated with, and second information regarding a PUCCH resource set index; Receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); Determining a PUCCH resource for hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource index included in the DCI; and including transmitting the HARQ-ACK information based on the PUCCH resource determined above, method.

2. In Paragraph 1, The above first information includes a value related to the first RAT or a value related to the second RAT, method.

3. In Paragraph 2, The value associated with the first RAT is a value relating to a first table for a plurality of PUCCH resource sets for the first RAT, and the value associated with the second RAT is a value relating to a second table for a plurality of PUCCH resource sets for the second RAT. method.

4. In Paragraph 2, The value related to the first RAT above is a value regarding the first row range within the table, and the value related to the second RAT above is a value regarding the second row range within the table, and The first row range includes rows respectively associated with a plurality of PUCCH resource sets for the first RAT, and the second row range includes rows respectively associated with a plurality of PUCCH resource sets for the second RAT. method.

5. In Paragraph 2, The above first information is received through system information block 1 (SIB) or a DCI that schedules system information, method.

6. In Paragraph 2, The above second information is received through system information block 1 (SIB), method.

7. In Paragraph 6, The above first information is received via a DCI that schedules a random access response (RAR) of a random access process or a PDSCH carrying message 4 of the said random access process, method.

8. In Paragraph 7, The PUCCH resource set associated with the above PUCCH resource set index includes a plurality of PUCCH resources for the first RAT and a plurality of PUCCH resources for the second RAT, and The value associated with the first RAT is a value associated with the plurality of PUCCH resources for the first RAT, and the value associated with the second RAT is a value associated with the plurality of PUCCH resources for the second RAT, method.

9. 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: The above UE receives first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) setting are associated with, and second information regarding a PUCCH resource set index; Receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); Determining a PUCCH resource for hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource index included in the DCI; and including transmitting the HARQ-ACK information based on the PUCCH resource determined above, User device.

10. 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: The above UE receives first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) setting are associated with, and second information regarding a PUCCH resource set index; Receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); Determining a PUCCH resource for hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource index included in the DCI; and including transmitting the HARQ-ACK information based on the PUCCH resource determined above, Processing unit.

11. 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: The above UE receives first information regarding which radio access technology (RAT) the PUCCH resources to be used until the UE acquires a dedicated physical uplink control channel (PUCCH) setting are associated with, and second information regarding a PUCCH resource set index; Receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); Determining a PUCCH resource for hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource index included in the DCI; and including transmitting the HARQ-ACK information based on the PUCCH resource determined above, Storage medium.

12. In a method performed by a base station (BS), Transmits first information regarding which radio access technology (RAT) the PUCCH resources to be used until the user equipment (UE) acquires a dedicated physical uplink control channel (PUCCH) configuration are associated with, and second information related to a PUCCH resource set index; Transmit downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); and Comprising receiving hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource associated with the PUCCH resource index included in the DCI, method.

13. 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: Transmits first information regarding which radio access technology (RAT) the PUCCH resources to be used until the user equipment (UE) acquires a dedicated physical uplink control channel (PUCCH) configuration are associated with, and second information related to a PUCCH resource set index; Transmit downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); and Comprising receiving hybrid automatic repeat request - acknowledgment (HARQ-ACK) information for the PDSCH based on the first information, the second information, and the PUCCH resource associated with the PUCCH resource index included in the DCI, Base station.

Images