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

By transmitting UCI and UL-SCH data over a single PUSCH across multiple carriers using optimized resource allocation, the method addresses 5G limitations, enhancing communication efficiency and reliability while reducing energy consumption.

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

Patent Information

Application Number
PCT/KR2026/005796
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-01-13
Filing Date
2026-04-30
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face limitations in achieving very high data speeds, large numbers of connected devices, global connectivity, low latency, reduced energy consumption, ultra-reliable connectivity, and machine learning capabilities, particularly in managing control information over discontinuous frequency resources.

Method used

The method involves transmitting and receiving uplink control information (UCI) and uplink shared channel (UL-SCH) data over a single physical uplink shared channel (PUSCH) across multiple carriers, utilizing beta and alpha values for resource allocation, and designating carriers based on resource blocks, modulation and coding schemes, or carrier types to optimize communication.

Benefits of technology

This approach enhances communication efficiency by optimizing resource utilization and reducing latency, enabling high-speed data transmission and reliable connectivity across multiple devices with reduced energy consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005796_12112026_PF_FP_ABST
    Figure KR2026005796_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This UE may receive scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers and transmit uplink control information (UCI) over the single PUSCH, wherein the UCI may be transmitted on at least one of the N carriers.
Need to check novelty before this filing date? Find Prior Art

Description

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

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

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

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

[0004] One technical objective of the present specification is to provide methods and apparatus for transmitting control information over a single radio channel scheduled on a cell / carrier / BWP when discontinuous frequency resources are combined to form a single cell or carrier or bandwidth part (BWP).

[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 operations may include: receiving scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, where N is an integer greater than 1; and transmitting uplink control information (UCI) over the single PUSCH.

[0007] In one aspect of the present specification, a method by means of a base station (BS) is provided. In another aspect of the present specification, a BS is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. The method or the operations may include: transmitting scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, wherein N is an integer greater than 1; and receiving uplink control information (UCI) on the single PUSCH.

[0008] In each aspect of the present specification, the UCI may be mapped to at least one of the N carriers and transmitted or received.

[0009] In each aspect of the specification, the UCI may be transmitted or received on the single PUSCH based on the single PUSCH overlapping in time with the physical uplink control channel (PUCCH) carrying the UCI.

[0010] In each aspect of the present specification, the method or operation may further include transmitting or receiving uplink shared channel (UL-SCH) data over the single PUSCH.

[0011] In each aspect of the present specification, the UCI may be mapped to the single PUSCH, and the UL-SCH data may be mapped to a resource within the single PUSCH where the UCI is not mapped.

[0012] In each aspect of the specification, the UCI can be mapped to the single PUSCH across the N carriers based on the respective (respective) beta offset values ​​for the N carriers.

[0013] In each aspect of the specification, the UCI can be mapped to the single PUSCH across the N carriers based on the respective alpha values ​​for the N carriers.

[0014] In each aspect of the specification, the UCI may be mapped to a PUSCH resource on a single carrier among the PUSCH resources for the single PUSCH over the N carriers, and the single carrier may be i) the carrier with the largest number of resource blocks (RB) or resource elements (RE) occupied by the single PUSCH among the N carriers, ii) the carrier with the largest MCS value among the modulation and coding scheme (MCS) values ​​for each of the N carriers, iii) a carrier designated by a base station, iv) an anchor carrier, or v) a carrier of the lowest index.

[0015] In each aspect of the present specification, the UCI may include a UCI of a first UCI type, and the UCI of the first UCI type may be mapped to a PUSCH resource on a first carrier associated with the first UCI type among the PUSCH resources for the PUSCH on the N carriers.

[0016] In each aspect of the present specification, the UCI may further include a UCI of a second UCI type, and the UCI of the second UCI type may be mapped to a PUSCH resource on a second carrier associated with the second UCI type among the PUSCH resources on the N carriers.

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

[0018] According to some implementations of the present specification, methods and devices may be provided for transmitting control information over a single radio channel scheduled on such cell / carrier / BWP when discontinuous frequency resources are combined to form a single cell or carrier or bandwidth part (BWP).

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

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

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

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

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

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

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

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

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

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

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

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

[0031] FIG. 11 illustrates the processing process at the transmission end for a transport block (TB);

[0032] FIG. 12 shows an example of multiplexing UCI to PUSCH;

[0033] FIG. 13 illustrates a multi-carrier single cell (MCSC) structure;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0049] For terms and technologies used in this specification that are not specifically described, reference may be made to 3GPP-based standard documents, e.g., 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300 and 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.304, 3GPP TS 38.331, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0086]

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

[0088]

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

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

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

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

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

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

[0095]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0160] - Link recovery request (LRR)

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

[0162] FIG. 11 illustrates the processing process at the transmitting end for a transport block (TB). In order for the receiving end to correct errors that the wireless signal experiences in the wireless channel, the transmitting end codes the information to be sent using a forward error correction code and then transmits it. At the receiving end, the received signal is demodulated, and then the transmitted information is restored after undergoing the decoding process of the error correction code. During this decoding process, errors in the received signal caused by the wireless channel are corrected.

[0163] Data reaches the coding block in the form of up to two transport blocks per DL / UL cell every TTI. The following coding steps can be applied to each transport block of the DL / UL cell:

[0164] - Add cyclic redundancy check (CRC) code to transport block;

[0165] - Code block segmentation and code block CRC attachment;

[0166] - Channel coding;

[0167] - Rate matching;

[0168] - Code block concatenation.

[0169] In actual communication systems, for the convenience of implementation, transport blocks exceeding a certain size are divided into multiple smaller data blocks for encoding. These divided smaller data blocks are called code blocks.

[0170] Referring to FIG. 11, for example, a TB CRC may be attached to a TB. The TB CRC may be used to confirm the TB during the decoding process. If the TB CRC-attached TB is not larger than a predetermined size, the TB CRC-attached TB is encoded by a (channel) encoder. If the TB CRC-attached TB is larger than the predetermined size, the TB CRC-attached TB may be divided into multiple code blocks (CBs). When the TB CRC-attached TB is divided into multiple CBs, in some scenarios, CB CRCs may be attached to each CB. This allows for the acquisition of multiple CB CRC-attached CBs. The CB CRCs may be used to confirm the CBs during the decoding process by a receiver. Each of the multiple CB CRC-attached CBs may be encoded through a (channel) encoder. While CBs generally have the same size, one CB among multiple CBs may have a different size due to size limitations of the channel encoder's internal interleaver. The aforementioned multiple CBs with attached CRCs may be encoded in parallel through respective (channel) encoders or one by one through a single (channel) encoder. In some implementations, interleaving may be performed to reduce the impact of burst errors occurring during transmission over the wireless channel after error correction coding is performed in CB units of a fixed interleaver size. Then, they are mapped to the actual wireless resources and transmitted. Since the amount of wireless resources used during actual transmission is constant, rate matching must be performed on the encoded code blocks to match this. Generally, rate matching is achieved through puncturing or repetition.For example, if the amount of a wireless resource, e.g., the number of transmission bits that can be transmitted by said wireless resource, is M, and the coded bit sequence, i.e., the number of output bits of the encoder, is N, then if M and N are different, rate matching is performed to adjust the length of the coded bit sequence to match M. If M > N, all or part of the bits of the coded bit sequence are repeated so that the length of the rate-matched sequence becomes equal to M. M <N이면, 레이트 매칭된 시퀀스의 길이가 M과 같아지도록, 코딩된 비트 시퀀스의 비트들 중 일부가 펑처링되며, 펑처링된 비트는 전송에서 제외된다.

[0171] In a wireless communication system, the transmitting end encodes the data to be transmitted using channel coding with a specific code rate, and then adjusts the code rate of the data to be transmitted through a rate matching process consisting of puncturing and repetition.

[0172] The output bit sequence after rate matching and code block concatenation is modulated into modulation symbols through a modulator according to the modulation scheme. The following table exemplifies modulation schemes and corresponding modulation orders.

[0173]

[0174] For each codeword, for example, Q m One complex-value modulation symbol can be generated per block of bits. Coded bits can be modulated by a modulation mapper in 5G NR, for example, as follows.

[0175] In the case of quadrature phase shift keying (QPSK) modulation, pairs of bits, b(2i) and b(2i+1), are mapped to (complex-valued) modulation symbols d(i) according to the following.

[0176]

[0177] In the case of 16QAM modulation, four pairs of bits (quadruplets of bits), b(4i), b(4i+1), b(4i+2), b(4i+3), are mapped to (complex-value) modulation symbols d(i) according to the following.

[0178]

[0179] In the case of 64QAM modulation, six pairs of bits (hextuplets of bits), b(6i), b(6i+1), b(6i+2), b(6i+3), b(6i+4), b(6i+5), are mapped to (complex-value) modulation symbols d(i) according to the following.

[0180]

[0181] In the modulation schemes mentioned above, even-numbered input bits are mapped to the in-phase channel (I-channel), and odd-numbered input bits are mapped to the quadrature channel (Q-channel).

[0182] The above modulation symbols are mapped to radio resources allocated by the base station and transmitted to the receiver via said radio resources. The decoding process of the channel code is the reverse of the encoding process, and a decoder corresponding to each encoder of the transmitter is used in the decoding process performed at the receiver. After performing decoding for each code block (CB), the receiver constructs a TB and finally checks whether the TB CRC passes for said TB. In current 3GPP-based systems, the CB CRC is used for fast decoding termination. For example, if the CB CRC fails, the receiver may generate a NACK without decoding other CBs.

[0183] FIG. 12 illustrates an example of multiplexing a UCI onto a PUSCH. When a PUCCH resource(s) and a PUSCH resource overlap within a slot and PUCCH-PUSCH simultaneous transmission is not configured, the UCI can be transmitted over the PUSCH as illustrated. Transmitting a UCI over the PUSCH is referred to as UCI piggyback or PUSCH piggyback. FIG. 12 illustrates a case where a HARQ-ACK and channel state information (CSI) are carried on the PUSCH resource.

[0184] When a UE transmits UCIs such as HARQ-ACK and CSI by piggybacking them to a PUSCH, the amount of resources for the UCI carried on the PUSCH can be determined by the alpha value and / or the beta_offset value.

[0185] For a description of the alpha value, refer to Section 6.3 of the NR standard document 3GPP TS 38.212. The alpha value can be set by the upper layer parameter scaling (to one of 0.5, 0.65, 0.8, or 1) and is used to limit the maximum number of resource elements (RE) allocated for UCI purposes. For example, through the RRC information element (IE) PUSCH-Config used to set UE-specific PUSCH parameters, a parameter scaling regarding a scaling factor for limiting the number of resource elements assigned to UCI on PUSCH is provided, and α can be set by said parameter scaling.

[0186] Referring to Section 9.3 of the NR standard document 3GPP TS 38.213, beta_offset value(s) are described in relation to reporting UCIs over PUSCH. UCIs transmitted over PUSCH may include, for example, at least one of (i) HARQ-ACK, (ii) scheduling request (SR), (iii) CSI (e.g., RI, CQI, PMI and / or CRI, etc.), (iv) CG-UCI for configured grant (CG) PUSCH transmission over shared spectrum, and (v) unused transmission occasion-uplink control information (UTO-UCI) to notify the network of unused CG PUSCH occasions. Offset values ​​are set / defined to determine the number of resources required for the UE to multiplex HARQ-ACK information and / or CSI reports on PUSCH. Additionally, offset values ​​are set / defined to determine the number of resources required for the UE to multiplex CG-UCI and / or UTO-UCI on CG-PUSCH. These set / defined offset values ​​are provided to the UE via the DCI format scheduling the PUSCH transmission or higher-layer signaling (e.g., IEBetaOffset in PUSCH-Config), and these offset values ​​are referred to as beta offsets. At least one beta offset value may be provided for each UCI type (i) through (v). For example, the beta offset values ​​provided for HARQ-ACK may include a beta offset for cases where the size of the HARQ-ACK payload is 2 bits or less, a beta offset for cases where it is greater than 2 bits and less than or equal to 11 bits, and a beta offset for cases where it is greater than 11 bits.The beta offset values ​​provided for the CSI may include beta offset values ​​for Part 1 CSI and beta offset values ​​for Part 2 CSI. If a priority index (e.g., priority index 1 or 0 for supporting URLLC) is associated with the UCI, beta offset values ​​may be provided more finely for each priority index. The UE may use the beta offset values ​​of the corresponding UCI to perform rate matching for the PUSCH for multiplexing the UCI.

[0187] For example, referring to Section 6.3.2.4.1.1 of 3GPP TS 38.212, the number of REs for HARQ-ACKs to be carried on a PUSCH with an uplink-shared channel (UL-SCH) can be determined by the following:

[0188]

[0189] As another example, referring to Section 6.3.2.4.1.1 of 3GPP TS 38.212, the number of REs for HARQ-ACKs to be carried on a PUSCH without UL-SCH can be determined by the following.

[0190]

[0191] Q' in Equations 4 and 5 ACK This may correspond to the number of coded modulation symbols per layer for HARQ-ACK transmission on PUSCH.

[0192] O in mathematical formulas 4 and 5 ACK is the number of HARQ-ACK bits. L ACKis the number of cyclic redundancy check (CRC) bits. β PUSCH offset = β HARQ-ACK offset and, here β HARQ-ACK offset is the beta_offset value for HARQ-ACK, and C UL-SCH is the number of code blocks (CBs) for the UL-SCH of the above PUSCH transmission, and K r is the r-th code block size for the UL-SCH of the above PUSCH transmission, R is the code rate of the above PUSCH, and Q m is the modulation order of the above PUSCH. M UCI sc (l) is within the above PUSCH transmission, l = 0,1,2,...,N PUSCH symb,all For -1, it is the number of REs that can be used for the transmission of UCI within OFDM symbol l, and N PUSCH symb,all is the total number of OFDM symbols of the above PUSCH, and for any OFDM symbol carrying the DMRS of the above PUSCH, M UCI sc (l) = 0, and for any OFDM symbol that does not carry the DMRS of the above PUSCH, M UCI sc (l) = M PUSCH sc - M PT-RS sc (l) and here M PUSCH sc is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers, and M PT-RS scis the number of subcarriers in OFDM symbol l that carry the phase tracking reference signal (PTRS) within the PUSCH transmission. α is the alpha value provided by the upper layer parameter scaling, and l0 is the symbol index of the first OFDM symbol that does not carry the DMRS of the PUSCH (after the first DMRS symbol(s).

[0193] As another example, referring to Section 6.3.2.4.1.2 of 3GPP TS 38.212, the number of REs for CSI Part 1 to be carried on a PUSCH with UL-SCH can be determined by the following.

[0194]

[0195] As another example, referring to Section 6.3.2.4.1.2 of 3GPP TS 38.212, the number of REs for CSI Part 1 to be carried in PUSCH without UL-SCH can be determined by Equation 7 if there is CSI Part 2, and by Equation 8 otherwise.

[0196]

[0197]

[0198] In mathematical formulas 6, 7, and 8, Q' CSI-1 This may correspond to the number of coded modulation symbols per layer for CSI part 1 transmission on PUSCH.

[0199] In mathematical formulas 6, 7, and 8, O CSI-1 is the number of bits for CSI Part 1, and L CSI-1is the number of CRC bits for CSI Part 1. β PUSCH offset = β CSI-part1 offset and, here β CSI-part1 offset is the beta_offset value for CSI Part 1, and C UL-SCH is the number of code blocks (CBs) for the UL-SCH of the above PUSCH transmission, and K r is the r-th code block size for the UL-SCH of the above PUSCH transmission, R is the code rate of the above PUSCH, and Q m is the modulation order of the above PUSCH, and Q' ACK is the number of modulated symbols for which the HARQ-ACK is transmitted, and M UCI sc (l) is within the above PUSCH transmission, l = 0,1,2,...,N PUSCH symb,all For -1, it is the number of REs that can be used for the transmission of UCI within OFDM symbol l, and N PUSCH symb,all is the total number of OFDM symbols of the above PUSCH, and for any OFDM symbol carrying the DMRS of the above PUSCH, M UCI sc (l) = 0, and for any OFDM symbol that does not carry the DMRS of the above PUSCH, M UCI sc (l) = M PUSCH sc - M PT-RS sc (l) and here M PUSCH sc is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers, and M PT-RS scis the number of subcarriers within OFDM symbol l carrying the phase tracking reference signal (PTRS) in the above PUSCH transmission. α is the alpha value provided by the upper layer parameter scaling.

[0200] As another example, referring to Section 6.3.2.4.1.3 of 3GPP TS 38.212, the number of REs for CSI Part 2 to be carried on a PUSCH with UL-SCH can be determined by the following.

[0201]

[0202] As another example, referring to Section 6.3.2.4.1.3 of 3GPP TS 38.212, the number of REs for CSI Part 2 to be included in PUSCH without UL-SCH can be determined by the following.

[0203]

[0204] In mathematical equations 9 and 10, Q' CSI-2 This may correspond to the number of coded modulation symbols per layer for CSI part 2 transmission on PUSCH.

[0205] In mathematical formulas 9 and 10, O CSI-2 is the number of bits for CSI Part 2, and L CSI-2 is the number of CRC bits for CSI Part 2. β PUSCH offset = β CSI-part2 offset and, here β CSI-part2 offset is the beta_offset value for CSI Part 2. Q' ACK and Q' CSI-1are, respectively, the number of modulation symbols for HARQ-ACK and the number of modulation symbols for CSI. C UL-SCH is the number of code blocks (CBs) for the UL-SCH of the above PUSCH transmission, and K r is the r-th code block size for the UL-SCH of the above PUSCH transmission, R is the code rate of the above PUSCH, and M UCI sc (l) is within the above PUSCH transmission, l = 0,1,2,...,N PUSCH symb,all For -1, it is the number of REs that can be used for the transmission of UCI within OFDM symbol l, and N PUSCH symb,all is the total number of OFDM symbols of the above PUSCH, and for any OFDM symbol carrying the DMRS of the above PUSCH, M UCI sc (l) = 0, and for any OFDM symbol that does not carry the DMRS of the above PUSCH, M UCI sc (l) = M PUSCH sc - M PT-RS sc (l) and here M PUSCH sc is the scheduled bandwidth of the PUSCH transmission, expressed as the number of subcarriers, and M PT-RS sc is the number of subcarriers within OFDM symbol l carrying the phase tracking reference signal (PTRS) in the above PUSCH transmission. α is the alpha value provided by the upper layer parameter scaling.

[0206] As can be seen from the mathematical formulas above, the larger the beta_offset value, the greater the number of REs allocated to the UCI, and the alpha value can determine the limit on the number of REs that can be carried in the UCI.

[0207] FIG. 13 illustrates a multi-carrier single cell (MCSC) structure. In 6G systems, non-contiguous frequency resources can be aggregated to form a single cell / carrier / BWP for efficient utilization of the (fragmented) spectrum. A carrier group composed of specific multiple carriers can be defined / configured, and multiple carriers belonging to the same carrier group can be composed of carriers that operate based on the same synchronization raster (sync raster) and / or have the same SIB information applied and / or have the same paging information applied, and a single carrier group can be defined / configured as a single serving cell. For convenience, a structure in which a single serving cell is composed of one or more carriers can be named a multi-carrier single cell (MCSC) structure.

[0208] For example, as illustrated in FIG. 13, two discontinuous carriers in a frequency resource may be configured as a single cell, and a PUSCH may be scheduled / configured / instructed to be transmitted over one or more carriers. The UE may receive scheduling / resource allocation information for the PUSCH through one or more DCIs (and / or higher-level signaling), and information such as the size of the time / frequency resources allocated per carrier and / or modulation and coding (MCS) values ​​may be the same or different.

[0209] Some implementations of this specification that piggyback a UCI when a single PUSCH is transmitted over a frequency resource composed of one or more carriers, as in the example of FIG. 13, are described below. For convenience, FIG. 13 provides examples where a serving cell is composed of two carriers or where a single PUSCH is transmitted over two carriers, but the implementations of this specification may be extended to cases where a serving cell is composed of two or more carriers or where a single PUSCH is transmitted over two or more carriers. In some implementations of this specification, a carrier may be replaced with terms such as cell / BWP. Also, in some implementations of this specification, a carrier may be replaced with a "group of carriers (composed of one or more carriers)" indicated by the same FDRA and / or MCS field. In addition, in some implementations of this specification, PUSCH may mean a DG PUSCH that is dynamically scheduled by a UL grant, or a configured grant PUSCH (where the UL grant is not transmitted every time and the PUSCH resource can be pre-configured by a BS or activated by an activation DCI).

[0210] <Method #1> A method to piggyback UCIs to all carriers when a single PUSCH spans one or more carriers

[0211] Even if a PUSCH spans multiple discontinuous carriers, the UE can piggyback the UCI based on the entire PUSCH.

[0212] In one way, common values ​​for the beta_offset and / or alpha values ​​can be utilized during UCI piggyback. For example, referring to FIG. 13, even if a single PUSCH is split between Carrier #1 and Carrier #2, the UE can perform UCI piggyback by applying a common beta_offset value and / or a common alpha value, treating it as if it were a single PUSCH. In this case, the common beta_offset value and / or the common alpha value may be values ​​that are predefined / set or set / instructed through upper-layer signaling or DCI.

[0213] Alternatively, the beta_offset and / or alpha values ​​may be defined, set, or specified differently for each carrier mapped to a single PUSCH. Or, the entire UCI payload may be divided into carrier-specific sub-payloads, and separate UCI encoding and mapping (with beta_offset and / or alpha values ​​applied) may be performed by the UE for each carrier.

[0214] For example, as shown in FIG. 13, when a single PUSCH is spread across two carriers and transmitted, and the HARQ-ACK payload consists of a total of O bits, O1 bits can be mapped onto Carrier #1 and O2 bits (where O = O1 + O2) can be mapped onto Carrier #2. In this case, the ratio of O1 to O2 can be defined in advance (e.g., divided into n equal parts for a PUSCH spanning n carriers, the ratio of the number of symbols / RBs / REs occupying each carrier, the ratio of PUSCH data bits mapped to each carrier), or can be set / indicated by the BS. Equation 4 or Equation 5 may be applied to calculate the number of REs occupied by the O1 bits on Carrier #1. The number of bits of PUSCH resources or code blocks carried on the corresponding Carrier #1 (e.g., C UL-SCH is the number of code blocks on Carrier #1 of UL-SCH, K ris the r-th code block size on Carrier #1, Q m is the modulation order of carrier #1 phase of PUSCH, M UCI sc (l) is the number of REs that can carry a UCI among the REs assigned to the l-th symbol for PUSCH on carrier #1, N PUSCH symb,all Based on (which may refer to the number of symbols allocated to the PUSCH on Carrier #1), the number of corresponding REs is calculated, and based on the number of REs in the PUSCH allocated on Carrier #1, a limit on the maximum number of REs that can carry O1 HARQ-ACK bits can be determined. Similarly, Equation 4 or Equation 5 may be applied to calculate the number of REs occupied by O2 bits on Carrier #2. The number of bits of PUSCH resources or code blocks carried on Carrier #2 (e.g., C UL-SCH is the number of carrier #2 phase code blocks of UL-SCH, K r is the r-th code block size of carrier #2, Q m is the modulation order of carrier #2 phase of PUSCH, M UCI sc (l) is the number of REs that can carry a UCI among the REs assigned to the l-th symbol for PUSCH on carrier #2, N PUSCH symb,all Based on (which may mean the number of symbols assigned to PUSCH on Carrier 2), the number of corresponding REs is calculated, and based on the number of REs of PUSCH assigned to Carrier 2, a limit on the maximum number of REs that can carry O2 HARQ-ACK O2 bits can be determined. The same method can be extended to each UCI type (e.g., CSI Part 1 or CSI Part 2).

[0215] <Method #2> Method to piggyback UCI on only a specific carrier when a single PUSCH spans one or more carriers

[0216] Given that channel conditions may vary by carrier, it may be reliable to piggyback the UCI only on a specific carrier. The specific carrier may be determined by at least one of the following options. In some implementations, which option is applied may be set by the BS.

[0217] Opt 1: The carrier to which UCI will be piggybacked is determined based on the resource area occupied by PUSCH. For example, the carrier with the largest number of RBs occupied by PUSCH may be selected. In the case of HARQ-ACK, considering its importance and the fact that it is mapped near PUSCH DM-RS, it may be advantageous to select a carrier with a relatively large amount of frequency resources. Alternatively, when the number of symbols / REs occupied by each carrier may differ, the carrier with the largest (or smallest) number may be selected. This is because if the number of symbols / REs is relatively large when UL-SCH and UCI are multiplexed, there may be sufficient resources available for multiplexing.

[0218] Opt 2: If different MCS values ​​are set for each carrier, the carrier to which the UCI will piggyback may be determined based on the MCS value. For example, a carrier with a large (or small) assigned MCS value may be selected. This is because a large MCS value may indicate that the channel conditions are relatively better compared to other carriers, and that the number of REs occupied by the UCI may be small.

[0219] Opt 3: A specific carrier to which the UCI will be piggybacked is determined by a rule, or a specific carrier is set or designated by the base station. For example, a specific carrier may be designated or a specific carrier may be set in advance in the DCI scheduling the PUSCH. Alternatively, a priority among multiple carriers may be set by the BS or a rule may be defined. For example, when there is an anchor carrier that provides functions such as initial access, system information transmission, paging, and random access for a UE in IDLE mode, that anchor carrier may have a high (or low) priority. As another example, when there is an index value defined / set for each carrier, a rule is established that the lower the index value (or the higher the index value), the higher the priority, and in the case of a PUSCH spread across Carrier #1 and Carrier #2 as exemplified in FIG. 13, the UCI may be piggybacked through Carrier #1, which has a low index.

[0220] When a specific carrier is determined by applying Method #2 and the UE piggybacks a HARQ-ACK on that carrier, the number of bits of PUSCH resources or code blocks carried on that carrier (or the entire carrier mapped to PUSCH) (e.g., C UL-SCH is the number of code blocks on the corresponding carrier of UL-SCH (or the entire carrier mapped to PUSCH), K r is the size of the r-th code block on the carrier (or the entire carrier mapped to PUSCH), Q m is the modulation order of the PUSCH on the corresponding carrier (or the entire carrier to which the PUSCH is mapped), M UCI sc (l) is the number of REs that can carry a UCI among the REs assigned to the l-th symbol of PUSCH on the corresponding carrier (or the entire carrier mapped to PUSCH), N PUSCH symb,allBased on the number of symbols assigned to PUSCH on the carrier (or the entire carrier mapped to PUSCH), the number of corresponding REs is calculated, and a limit on the maximum number of REs that can carry HARQ-ACK bits can be determined based on the number of REs of PUSCH assigned on the carrier (or the entire carrier mapped to PUSCH). The same method can be extended to each UCI type (e.g., CSI Part 1 or CSI Part 2).

[0221] <Method #3> Method for determining the carrier performing piggyback differently by UCI type when a single PUSCH spans one or more carriers

[0222] Given that channel conditions may differ by carrier and the importance of each UCI type varies, it may be advantageous to determine the UCI type piggybacked differently for each carrier. A specific carrier for each UCI type may be determined by at least one of the following options. Which option to apply may be set by the BS. Although the examples below for each option are explained separately for HARQ-ACK and CSI, this method can be extended to determine different carriers for HARQ-ACK, CSI Part 1, and CSI Part 2, respectively.

[0223] Opt A: The carrier for the UCI type is determined based on the resource area occupied by PUSCH. For example, the carrier with the largest number of RBs occupied by PUSCH is determined as the carrier for HARQ-ACK piggyback, and other carrier(s) may be selected as carriers for CSI piggyback. In the case of HARQ-ACK, considering its importance and mapping it near PUSCH DM-RS, it may be advantageous to select a carrier with a relatively large amount of frequency resources. Alternatively, when the number of symbols / REs occupied by each carrier may vary, the carrier with the largest (or smallest) number may be determined as the carrier for HARQ-ACK piggyback, and other carrier(s) may be selected as carriers for CSI piggyback. This is because the relatively larger the number of symbols / REs allocated for PUSCH, the more sufficient resources there may be for multiplexing.

[0224] Opt B2: If different MCS values ​​are set for each carrier, the carrier for the UCI type is determined based on the MCS value. For example, a carrier with a large (or small) assigned MCS value may be determined as the carrier for HARQ-ACK piggyback, while other carrier(s) may be selected as the carrier for CSI piggyback. This is because a large MCS value may indicate relatively better channel conditions compared to other carriers and may mean that the number of REs occupied by the UCI is small.

[0225] Opt C: The carrier to carry a specific UCI type is determined by a rule, or the carrier to carry a specific UCI type is set or indicated by the BS. For example, in a DCI scheduling PUSCH, the carrier on which piggyback for each UCI type will be performed may be indicated or a specific carrier may be set in advance. Alternatively, the priority among multiple carriers may be set by the BS or a rule may be defined. For example, when there is an anchor carrier that provides functions such as initial connection, system information transmission, paging, or random access for a UE in IDLE mode, that anchor carrier may have a high (or low) priority. As another example, when there is an index value defined / set for each carrier, a rule is established that the lower the index value (or the higher the index value), the higher the priority. In the case of PUSCH spread across carrier #1 and carrier #2 as shown in Fig. 13, HARQ-ACK can be piggybacked through carrier #1, which has a lower index, and CSI can be piggybacked through carrier #2.

[0226] When a specific carrier is determined by applying Method #3 and the UE piggybacks a HARQ-ACK on that carrier, the number of bits of PUSCH resources or code blocks carried on that carrier (or the entire carrier mapped to PUSCH) (e.g., C UL-SCH is the number of code blocks on the corresponding carrier of UL-SCH (or the entire carrier mapped to PUSCH), K r is the size of the r-th code block on the carrier (or the entire carrier mapped to PUSCH), Q m is the modulation order of the PUSCH on the corresponding carrier (or the entire carrier to which the PUSCH is mapped), M UCI sc (l) is the number of REs that can carry a UCI among the REs assigned to the l-th symbol of PUSCH on the corresponding carrier (or the entire carrier mapped to PUSCH), N PUSCH symb,allBased on the number of symbols assigned to PUSCH on the carrier (or the entire carrier mapped to PUSCH), the number of corresponding REs is calculated, and a limit on the maximum number of REs that can carry HARQ-ACK bits can be determined based on the number of REs of PUSCH assigned on the carrier (or the entire carrier mapped to PUSCH). The same method can be extended to each UCI type (e.g., CSI Part 1 or CSI Part 2).

[0227] In applying the aforementioned Method #1, Method #2, and Method #3, the beta_offset value and / or alpha value for each carrier may be the same or different. If different beta_offset values ​​and / or alpha values ​​may be available for each carrier, the beta_offset value and / or alpha value for each carrier may be separately set / indicated by the BS, or a relative offset value based on the beta_offset value and / or alpha value of a specific carrier may be set / indicated by the BS. The specific carrier may be a carrier that is predefined (e.g., a carrier of the lowest / highest index, an anchor carrier that provides functions such as initial connection / system information transmission / paging / random connection for a UE in IDLE mode) or configured.

[0228] In some implementations of this specification, different methods among the above may be applied depending on the UCI type. For example, Method #1 may be applied for HARQ-ACK (or CSI Part 1) to map as many UCI bits as possible near DM-RS, and Method #2 or Method #3 may be applied for the remaining CSI (or CSI Part 2).

[0229] When an aperiodic CSI is triggered through a UL grant, and the PUSCH scheduled in the UL grant spans multiple carriers, the DCI may indicate which carrier to piggyback the UCI (or whether or not there is a UL-SCH on the PUSCH on which carrier). For carrier(s) indicated for piggybacking the UCI or for which there is no UL-SCH, all UCI types may be mapped to the carrier(s) by applying the aforementioned Method #2, or specific UCI types may be mapped to the carrier(s) and the remaining UCI types to other carrier(s) by applying the aforementioned Method #3. Meanwhile, in this case, the transport block size (TBS) of the PUSCH can be calculated / determined based on the resources allocated to carrier(s) for use without piggybacking the UCI or carrier(s) indicated to have UL-SCH.

[0230] When frequency hopping is performed by the UE for a PUSCH that piggybacks the UCI, the UCI mapping method for each frequency hop may be the same or different. For example, the aforementioned Method #1, Method #2, or Method #3 may be applied regardless of the frequency hop or commonly. In this case, when applying Method #1, the beta_offset value and / or alpha value applied between the first hop and the second hop may be different; when applying Method #2, the carrier on which UCI piggyback is performed between the first hop and the second hop may be different; or when applying Method #3, the carrier on which piggyback is performed between the first hop and the second hop may be different depending on the UCI type. As another example, Method #2 may be applied to the first hop and Method #3 may be applied to the second hop. In this case, which method to apply for each jump can be defined in advance or signaled to the UE from the BS.

[0231] In determining the PUSCH that piggybacks the UCI, if there is a PUSCH that spans multiple carriers as shown in FIG. 13 and a PUSCH that does not span multiple carriers but belongs to a single carrier, a rule can be defined to preferentially select the PUSCH belonging to a single carrier.

[0232] For a PUSCH spanning multiple carriers as shown in Fig. 13, frequency hopping can be set / instructed. In this case, a different method may be applied for each hop, or a method determined based on the first hop may be applied identically to the second hop.

[0233] In each method of this specification, multiple carriers constituting a cell based on an MCSC structure may be replaced with multiple subbands or multiple (sub-)BWPs configured within a cell, a single carrier, a single system bandwidth (BW), or a single channel BW. Accordingly, in each method of this specification, a carrier (within an MCSC-based cell) may be replaced with a subband or (sub-)BWP (within a cell, within a carrier, within a system BW, or within a channel BW). In the above, multiple carriers (within the MCSC-based cell) or multiple subbands (within the cell or within the carrier or within the system BW or within the channel BW) or multiple (sub-)BWPs may be defined / configured / instructed so that each operates as an individual / independent radio frequency (RF) chain and / or an individual / independent baseband processor / module (or each operates as an individual / independent duplexing scheme and / or an individual / independent DL / UL symbol / slot type).

[0234] FIG. 14 is an example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification. Referring to FIG. 14, the BS can set up Carrier #1 and Carrier #2 within a single serving cell for the UE and schedule a single PUSCH spanning Carrier #1 and Carrier #2 (S1401). The UE can perform piggybacking of the UCI to both Carrier #1 and Carrier #2 by applying the aforementioned method #1, perform piggybacking only to a specific carrier (e.g., Carrier #1 or Carrier #2) by applying the aforementioned method #2, or perform piggybacking to different carriers depending on the UCI type by applying the aforementioned method #3 (S1403).

[0235] According to some implementations of this specification, when a single PUSCH is configured / instructed to span one or more carriers, efficient UCI piggyback through said PUSCH is possible. This allows for an increased UCI transmission success rate.

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

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

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

[0239] In a method performed by the above UE, or in the above UE, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: receiving scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers (S1501), where N is an integer greater than 1; and transmitting uplink control information (UCI) over the single PUSCH (S1503).

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

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

[0242] 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 scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers (S1601), where N is an integer greater than 1; and receiving uplink control information (UCI) on the single PUSCH (S1603).

[0243] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the UCI may be mapped to at least one of the N carriers and transmitted or received.

[0244] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the UCI may be transmitted or received on the single PUSCH based on the single PUSCH overlapping in time with the physical uplink control channel (PUCCH) carrying the UCI.

[0245] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the method or operation may further include transmitting or receiving uplink shared channel (UL-SCH) data over the single PUSCH.

[0246] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the UCI may be mapped to the single PUSCH, and the UL-SCH data may be mapped to a resource within the single PUSCH where the UCI is not mapped.

[0247] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the UCI may be mapped to the single PUSCH across the N carriers based on respective beta offset values ​​for the N carriers.

[0248] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the UCI may be mapped to the single PUSCH across the N carriers based on respective alpha values ​​for the N carriers.

[0249] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the UCI may be mapped to a PUSCH resource on a single carrier among the PUSCH resources for the single PUSCH over the N carriers, and the single carrier may be i) the carrier with the largest number of resource blocks (RB) or resource elements (RE) occupied by the single PUSCH among the N carriers, ii) the carrier with the largest MCS value among the modulation and coding scheme (MCS) values ​​for each of the N carriers, iii) a carrier designated by the base station, iv) an anchor carrier, or v) a carrier of the lowest index.

[0250] In some implementations related to FIG. 14, FIG. 15, or FIG. 16, the UCI may include a UCI of a first UCI type, and the UCI of the first UCI type may be mapped to a PUSCH resource on a first carrier associated with the first UCI type among the PUSCH resources for the PUSCH on the N carriers.

[0251] In some implementations related to FIG. 14, FIG. 15 or FIG. 16, the UCI may further include a UCI of a second UCI type, and the UCI of the second UCI type may be mapped to a PUSCH resource on a second carrier associated with the second UCI type among the PUSCH resources on the N carriers.

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

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

Claims

1. A method performed by user equipment (UE), Receive scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, where N is an integer greater than 1; and It includes transmitting uplink control information (UCI) over the single PUSCH, and The above UCI is transmitted over at least one of the N carriers, method.

2. In Paragraph 1, The above UCI is transmitted over the single PUSCH based on the fact that the single PUSCH overlaps in time with the physical uplink control channel (PUCCH) carrying the UCI, method.

3. In Paragraph 1, Further comprising transmitting uplink shared channel (UL-SCH) data over the single PUSCH. method.

4. In Paragraph 3, The above UCI is mapped to the above single PUSCH, and the above UL-SCH data is mapped to a resource within the above single PUSCH where the UCI is not mapped, method.

5. In Paragraph 1, The above UCI is mapped to the single PUSCH across the N carriers based on the respective (respective) beta offset values ​​for the N carriers, method.

6. In Paragraph 1, The above UCI is mapped to the single PUSCH across the N carriers based on respective alpha values ​​for the N carriers, method.

7. In Paragraph 1, The above UCI is mapped to a PUSCH resource on a single carrier among the PUSCH resources for the single PUSCH over the above N carriers, and The single carrier mentioned above is among the N carriers i) the carrier having the largest number of resource blocks (RBs) or resource elements (REs) occupied by the single PUSCH, ii) the carrier having the largest MCS value among the modulation and coding scheme (MCS) values ​​for each of the N carriers, iii) the carrier designated by the base station, iv) the anchor carrier, or v) the carrier of the lowest index, method.

8. In Paragraph 1, The above UCI includes a UCI of a first UCI type, and the UCI of the first UCI type is mapped to a PUSCH resource on a first carrier associated with the first UCI type among the PUSCH resources for the PUSCH on the N carriers. method.

9. In Paragraph 8, The above UCI further includes a UCI of a second UCI type, wherein the UCI of the second UCI type is mapped to a PUSCH resource on a second carrier associated with the second UCI type among the PUSCH resources on the N carriers. method.

10. 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: Receive scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, where N is an integer greater than 1; and It includes transmitting uplink control information (UCI) over the single PUSCH, and The above UCI is transmitted over at least one of the N carriers, User device.

11. 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: Receive scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, where N is an integer greater than 1; and It includes transmitting uplink control information (UCI) over the single PUSCH, and The above UCI is transmitted over at least one of the N carriers, Processing unit.

12. 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: Receive scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, where N is an integer greater than 1; and It includes transmitting uplink control information (UCI) over the single PUSCH, and The above UCI is transmitted over at least one of the N carriers, Storage medium.

13. In a method performed by a base station (BS), Transmit scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, where N is an integer greater than 1; and It includes receiving uplink control information (UCI) on the single PUSCH, and The above UCI is received on at least one of the N carriers, method.

14. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Transmit scheduling information for scheduling a single physical uplink shared channel (PUSCH) across N carriers, where N is an integer greater than 1; and It includes receiving uplink control information (UCI) on the single PUSCH, and The above UCI is received on at least one of the N carriers, Base station.