WO2024105645A1

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

Info

Publication number: WO2024105645A1
Application number: PCT/IB2023/062229
Authority: WO
Inventors: 배덕현; 황승계; 이영대; 김재형
Original assignee: 엘지전자 주식회사
Priority date: 2022-11-14
Filing date: 2023-12-05
Publication date: 2024-05-23

Abstract

This UE can receive a measurement gap configuration. The UE may comprise, on the basis that a measurement gap according to the measurement gap configuration and a downlink reception period overlap, i) performing measurement within the measurement gap and skipping downlink reception during the downlink reception period within the measurement gap on the basis of that a specific condition is not satisfied, and ii) performing downlink reception during a downlink transmission period within the measurement gap on the basis that a specific condition is satisfied.

Description

Method for receiving a downlink signal, user device, processing device, and storage medium, and method and base station for transmitting a downlink signal

This specification relates to a wireless communication system.

Various devices and technologies such as machine-to-machine (M2M) communication, machine type communication (MTC), and smart phones and tablet PCs (personal computers) that require high data transmission have emerged and become widespread. there is. Accordingly, the amount of data required to be processed in a cellular network is increasing very rapidly. In order to meet this rapidly increasing data processing demand, carrier aggregation technology and cognitive radio technology to efficiently use more frequency bands are used to increase the data capacity transmitted within limited frequencies. Multi-antenna technology and multi-BS cooperation technology are developing.

As more communication devices require greater communication capacity, there is a need for enhanced mobile broadband (eMBB) communications compared to legacy radio access technology (RAT). In addition, massive machine type communication (mMTC), which is designed to provide various services anytime, anywhere by connecting multiple devices and objects, is one of the major issues to be considered in next-generation communication.

Additionally, discussions are underway on a communication system that will be designed in consideration of services/user equipment (UE) that are sensitive to reliability and waiting time. The introduction of next generation wireless access technology is being discussed considering eMBB communication, mMTC, ultra-reliable and low latency communication (URLLC), etc.

There is a need for a method to timely transmit/receive data packets with strict latency requirements and/or scheduling information for the data packets in a wireless communication system.

The technical challenges that this specification aims to achieve are not limited to the technical challenges mentioned above, and other technical challenges that are not mentioned can be clearly understood by those skilled in the art related to this specification from the detailed description below. It could be.

In one aspect of the present specification, a method for a user device to receive a downlink signal in a wireless communication system is provided. The method includes: receiving measurement gap settings; And based on the overlap between the measurement gap and the downlink reception time according to the measurement gap setting: i) Based on that a specific condition is not met, measurement is performed within the measurement gap and the downlink is transmitted within the measurement gap. It may include omitting downlink reception at the reception time, and ii) performing the downlink reception at the downlink transmission time within the measurement gap based on the specific condition being met.

In another aspect of the present specification, a user device for receiving a downlink signal in a wireless communication system is provided. The user device includes: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising: : Receive measurement gap settings; And based on the overlap between the measurement gap and the downlink reception time according to the measurement gap setting: i) Based on that a specific condition is not met, measurement is performed within the measurement gap and the downlink is transmitted within the measurement gap. It may include omitting downlink reception at the reception time, and ii) performing the downlink reception at the downlink transmission time within the measurement gap based on the specific condition being met.

In another aspect of the present disclosure, a processing device is provided. The processing device may include: at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising: : Receive measurement gap settings; And based on the overlap between the measurement gap and the downlink reception time according to the measurement gap setting: i) Based on that a specific condition is not met, measurement is performed within the measurement gap and the downlink is transmitted within the measurement gap. It may include omitting downlink reception at the reception time, and ii) performing the downlink reception at the downlink transmission time within the measurement gap based on the specific condition being met.

In another aspect of the present disclosure, a computer-readable storage medium is provided. The storage medium stores at least one program code that includes instructions that, when executed, cause at least one processor to perform operations, the operations comprising: receiving a measurement gap setting; And based on the overlap between the measurement gap and the downlink reception time according to the measurement gap setting: i) Based on that a specific condition is not met, measurement is performed within the measurement gap and the downlink is transmitted within the measurement gap. It may include omitting downlink reception at the reception time, and ii) performing the downlink reception at the downlink transmission time within the measurement gap based on the specific condition being met.

In another aspect of the present specification, a method for transmitting a downlink signal from a base station to a user device in a wireless communication system is provided. The method: transfers the measurement gap settings; And based on the overlap between the measurement gap and the downlink transmission timing according to the measurement gap setting: i) omitting downlink transmission at the downlink transmission timing within the measurement gap based on a specific condition not being met, and ii) performing the downlink transmission at the downlink transmission time within the measurement gap, based on the specific condition being met.

In another aspect of the present specification, a base station that transmits a downlink signal to a user device in a wireless communication system is provided. The base station may include: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising: : Transfer measurement gap settings; And based on the overlap between the measurement gap and the downlink transmission timing according to the measurement gap setting: i) omitting downlink transmission at the downlink transmission timing within the measurement gap based on a specific condition not being met, and ii) performing the downlink transmission at the downlink transmission time within the measurement gap, based on the specific condition being met.

In another aspect of the present disclosure, a processing device is provided. The processing device may include: at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising: : Transfer measurement gap settings; And based on the overlap between the measurement gap and the downlink transmission timing according to the measurement gap setting: i) omitting downlink transmission at the downlink transmission timing within the measurement gap based on a specific condition not being met, and ii) performing the downlink transmission at the downlink transmission time within the measurement gap, based on the specific condition being met.

In another aspect of the present disclosure, a computer-readable storage medium is provided. The storage medium stores at least one program code containing instructions that, when executed, cause at least one processor to perform operations, the operations comprising: transmitting a measurement gap setting; And based on the overlap between the measurement gap and the downlink transmission timing according to the measurement gap setting: i) omitting downlink transmission at the downlink transmission timing within the measurement gap based on a specific condition not being met, and ii) performing the downlink transmission at the downlink transmission time within the measurement gap, based on the specific condition being met.

In each aspect of the present specification, the specific conditions may include the following: The downlink reception/transmission timing is based on a specific semi-static scheduling (SPS) setting on the SPS physical downlink shared channel ( physical downlink shared channel (PDSCH) time, and the specific SPS setting is an SPS setting with a priority index greater than a threshold, or SPS PDSCH reception/transmission at the SPS PDSCH time when the SPS PDSCH time overlaps the measurement gap. This is an SPS setting with an acceptable value.

For each aspect of the present specification, the specific conditions may include the following. The downlink reception/transmission timing is a physical downlink control channel based on a search space or control resource set (CORESET) setting including a specific radio resource control (RRC) parameter. PDCCH) timing or PDCCH monitoring/transmission timing based on search space settings for a specific downlink control information format.

In each aspect of the present specification, the measurement gap setting includes first priority information for scheduling by downlink control information carried by a physical downlink control channel (PDCCH) and radio resource control. It may include second priority information for scheduling by control (RRC). The specific condition may include the following: Based on the downlink reception/transmission time being scheduled by the downlink control information format, the priority set by the first priority information in the measurement gap setting is the It is lower than the priority of downlink reception/transmission, and based on the downlink reception/transmission timing being scheduled by an RRC message, the priority set by the second priority information in the measurement gap setting is the downlink reception /is less than the above priority of transmission.

In each aspect of the present specification, the specific conditions may include the following: the user device uses a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) is waiting for downlink control information scheduling retransmission for and the downlink reception/transmission time is the physical downlink control channel monitoring/transmission time.

In each aspect of the present specification, the specific condition may further include the following: the transport block carried by the PDSCH or the PUSCH has a packet data budget less than a certain threshold value, or has a higher priority index value. It is scheduled by the downlink control information format, or is based on semi-persistent scheduling settings or established grant settings.

In each aspect of the present specification, the specific conditions may include the following: a downlink control information format in which the downlink reception/transmission timing has a higher priority index value, and a downlink indicating activation of quasi-persistent scheduling. It is scheduled by a control information format or a downlink control information format indicating the downlink reception/transmission.

The above problem solving methods are only some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by those with ordinary knowledge in the relevant technical field based on the detailed description below. .

According to some implementations of the present specification, data packets with strict latency requirements and/or scheduling information for the data packets may be transmitted/received in a timely manner in a wireless communication system.

According to some implementations of the present specification, delay/latency occurring during wireless communication between communication devices can be reduced.

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

The accompanying drawings, which are included as part of the Detailed Description to facilitate understanding of implementations of the present specification, provide examples of implementations of the present specification and, together with the detailed description, describe implementations of the present specification:

1 shows an example of communication system 1 to which implementations of the present specification are applied;

2 is a block diagram showing examples of communication devices capable of performing a method according to the present specification;

3 illustrates another example of a wireless device capable of implementing implementation(s) of the present specification;

Figure 4 shows an example of a frame structure available in a wireless communication system based on the ^3rd generation partnership project (3GPP);

Figure 5 illustrates a resource grid of slots;

Figure 6 shows an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH;

Figure 7 illustrates a hybrid automatic repeat request-acknowledgement (HARQ-ACK) transmission/reception process;

Figure 8 illustrates the flow of UE operation to which several implementations of the present specification may be applied;

Figure 9 illustrates the flow of BS operation to which several implementations of this specification can be applied.

Hereinafter, implementations according to the present specification will be described in detail with reference to the attached drawings. The detailed description set forth below along with the accompanying drawings is intended to describe exemplary implementations of the present specification and is not intended to represent the only implementation form in which the present specification may be implemented. The following detailed description includes specific details to provide a thorough understanding of the disclosure. However, one skilled in the art will understand that the present disclosure may be practiced without these specific details.

In some cases, in order to avoid ambiguity in the concepts of this specification, well-known structures and devices may be omitted or may be shown in block diagram form focusing on the core functions of each structure and device. In addition, the same components are described using the same reference numerals throughout this specification.

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

For convenience of explanation, the description below assumes that this specification is applied to a 3GPP-based communication system, for example, LTE and NR. However, the technical features of this specification are not limited thereto. For example, although the detailed description below is described based on a mobile communication system corresponding to the 3GPP LTE/NR system, it is also applicable to any other mobile communication system except for matters specific to 3GPP LTE/NR. do.

For terms and technologies used in this specification that are not specifically described, refer to 3GPP-based standard documents, such as 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.321, 3GPP TS 38.331, etc. You can refer to it.

In the examples of this specification described later, the expression that the device “assumes” may mean that the entity transmitting the channel transmits the channel to comply with the “assumption.” This may mean that the subject receiving the channel receives or decodes the channel in a form that conforms to the “assumption,” under the premise that the channel was transmitted in compliance with the “assumption.”

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

In this specification, a node refers to a fixed point that can transmit/receive wireless signals by communicating with the UE. Various types of BSs can be used as nodes regardless of their names. For example, a BS, NB, eNB, pico-cell eNB (PeNB), home eNB (HeNB), relay, repeater, etc. may be nodes. Additionally, the node may not be a BS. For example, it may be a radio remote head (RRH) or a radio remote unit (RRU). RRH, RRU, etc. generally have a power level lower than that of the BS. Since RRH or RRU (hereinafter referred to as RRH/RRU) is generally connected to the BS through a dedicated line such as an optical cable, compared to cooperative communication by BSs generally connected through wireless lines, RRH/RRU and BS Collaborative communication can be performed smoothly. At least one antenna is installed in one node. The antenna may refer to a physical antenna, an antenna port, a virtual antenna, or an antenna group. Nodes are also called points.

In this specification, a cell refers to a certain geographical area where one or more nodes provide communication services. Therefore, in this specification, communicating with a specific cell may mean communicating with a BS or node that provides communication services to the specific cell. Additionally, the downlink/uplink signal of a specific cell refers to a downlink/uplink signal from/to a BS or node that provides communication services to the specific cell. A cell that provides uplink/downlink communication services to the UE is specifically called a serving cell. Additionally, the channel status/quality of a specific cell refers to the channel status/quality of a channel or communication link formed between a BS or node providing a communication service to the specific cell and the UE. In a 3GPP-based communication system, the UE determines the downlink channel status from a specific node through the antenna port(s) of the specific node and the CRS (Cell-specific Reference Signal) transmitted on the CRS (Cell-specific Reference Signal) resource allocated to the specific node. /Or it can be measured using CSI-RS (Channel State Information Reference Signal) resources transmitted on CSI-RS (Channel State Information Reference Signal) resources.

Meanwhile, 3GPP-based communication systems use the concept of cells to manage radio resources, and cells associated with radio resources are distinguished from cells in a geographic area.

A “cell” in a geographic area can be understood as the coverage through which a node can provide services using a carrier, and a “cell” in a wireless resource can be understood as the bandwidth (bandwidth), which is the frequency range configured by the carrier. It is related to bandwidth, BW). Downlink coverage, which is the range within which a node can transmit a valid signal, and uplink coverage, which is the range within which a valid signal can be received from the UE, depend on the carrier that carries the signal, so the node's coverage is used by the node. It is also associated with the coverage of a “cell” of wireless resources. Accordingly, the term "cell" can sometimes be used to mean coverage of a service by a node, sometimes a radio resource, and sometimes a range within which a signal using the radio resource can reach with effective strength.

Meanwhile, the 3GPP communication standard uses the concept of a cell to manage radio resources. A “cell” associated with a radio resource 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 may be configured with DL resources alone or a combination of DL resources and UL resources. When carrier aggregation is supported, the linkage between the carrier frequency of DL resources (or, DL CC) and the carrier frequency of UL resources (or, UL CC) is indicated by system information. It can be. For example, the combination of DL resources and UL resources may be indicated by System Information Block Type2 (SIB2) linkage. Here, the carrier frequency may be the same as or different from the center frequency of each cell or CC. When carrier aggregation (CA) is set up, 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 connection establishment/re-establishment/handover, and one serving cell Provides security input during RRC connection re-establishment/handover. These cells are called primary cells (Pcells). A Pcell is a cell that operates on the primary frequency where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. Depending on UE capabilities, secondary cells (Scells) may be configured to form a set of serving cells together with the Pcell. An Scell is a cell that can be set up after RRC (Radio Resource Control) connection establishment and provides additional radio resources in addition to the resources of a special cell (SpCell). The carrier corresponding to the Pcell in the downlink is called the downlink primary CC (DL PCC), and the carrier corresponding to the Pcell in the uplink is called the UL primary CC (UL PCC). The carrier corresponding to the Scell in the downlink is called a DL secondary CC (DL SCC), and the carrier corresponding to the Scell in the uplink is called a UL secondary CC (UL SCC).

For dual connectivity (DC) operation, the term special cell (SpCell) refers to the Pcell of a master cell group (MCG) or the primary of a secondary cell group (SCG). It is called a primary secondary cell (PSCell). SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node (e.g., BS) and consists of an SpCell (Pcell) and optionally one or more Scells. For a UE configured as DC, the SCG is a subset of serving cells associated with a secondary node and consists of a primary secondary cell (PSCell) and zero or more Scells. PSCell is the primary Scell of SCG. For a UE in RRC_CONNECTED state that is not configured as CA or DC, there is only one serving cell consisting of only Pcells. For a UE in RRC_CONNECTED state set to CA or DC, the term serving cells refers to the set of cells consisting of SpCell(s) and all Scell(s). In DC, two MAC entities are configured in the UE, one medium access control (MAC) entity for MCG and one MAC entity for SCG.

For UEs where CA is configured and DC is not configured, a Pcell PUCCH group (also known as primary PUCCH group) consisting of a Pcell and zero or more Scells and a Scell PUCCH group (also referred to as secondary PUCCH group) consisting of only Scell(s) are configured. You can. In the case of Scell, the Scell (hereinafter referred to as PUCCH Scell) through which the PUCCH associated with the cell is transmitted may be set. The Scell for which the PUCCH Scell is indicated belongs to the Scell PUCCH group (i.e., secondary PUCCH group), and PUCCH transmission of the related UCI is performed on the PUCCH Scell. If the PUCCH Scell is not indicated, or the cell indicated as the cell for PUCCH transmission is a Pcell. The Scell belongs to the Pcell PUCCH group (i.e., primary PUCCH group), and PUCCH transmission of the relevant UCI is performed on the Pcell. Hereinafter, when the UE is configured with an SCG, and some implementations of the present specification related to PUCCH are applied to the SCG, the primary cell may refer to the PSCell of the SCG. If the UE is configured with a PUCCH Scell and some implementations of the present specification related to PUCCH are applied to the secondary PUCCH group, the primary cell may refer to the PUCCH Scell of the secondary PUCCH group.

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

The 3GPP-based communication standard includes downlink physical channels corresponding to resource elements carrying information originating from the upper layer, and downlink physical channels corresponding to resource elements used by the physical layer but not carrying information originating from the upper layer. Defines link physical signals. For example, a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc. are downlink physical channels. It is defined, and the reference signal and synchronization signal (SS) are defined as downlink physical signals. A reference signal (RS), also called a pilot, refers to a signal with a predefined special waveform that is known to both the BS and the UE. For example, a demodulation reference signal (DMRS), channel state information RS (CSI-RS), etc. are defined as downlink reference signals. The 3GPP-based communication standard has uplink physical channels corresponding to resource elements that carry information originating from the upper layer, and uplink physical channels corresponding to resource elements that are used by the physical layer but do not carry information originating from the upper layer. Link physical signals are defined. For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are used as uplink physical channels. A demodulation reference signal (DMRS) for uplink control/data signals, a sounding reference signal (SRS) used for uplink channel measurement, etc. are defined.

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. In addition, PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), and PRACH (Physical Random Access CHannel) are time-frequency signals that respectively (respectively) carry UCI (Uplink Control Information), uplink data, and random access signals. It refers to a set of resources. Hereinafter, the expression that the user device transmits/receives PUCCH/PUSCH/PRACH is used with the same meaning as transmitting/receiving uplink control information/uplink data/random access signal on or through PUCCH/PUSCH/PRACH, respectively. do. In addition, the expression that the BS transmits/receives PBCH/PDCCH/PDSCH is used in the same meaning as transmitting broadcast information/downlink control information/downlink data on or through PBCH/PDCCH/PDSCH, respectively.

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

The communication device receives synchronization signal block (SSB), DMRS, CSI-RS, PBCH, PDCCH, PDSCH, PUSCH, and/or PUCCH in the form of wireless signals on the cell, so that a specific physical channel or specific physical signal It is not possible to select only wireless signals that include only and receive them through an RF receiver, or select and receive only wireless signals that exclude specific physical channels or physical signals and receive them through an RF receiver. In actual operation, the communication device receives wireless signals on a cell through an RF receiver, converts the wireless signals, which are RF band signals, into baseband signals, and uses one or more processors to convert the wireless signals to baseband signals. Decode physical signals and/or physical channels within the signals. Accordingly, in some implementations of the present specification, not receiving a physical signal and/or physical channel does not actually mean that the communication device does not receive wireless signals including the physical signal and/or physical channel, but rather the wireless signal. This may mean not attempting to restore the physical signal and/or the physical channel, for example, not attempting to decode the physical signal and/or the physical channel.

As more communication devices require greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Additionally, massive MTC, which connects multiple devices and objects to provide a variety of services anytime, anywhere, is also one of the major issues to be considered in next-generation communications. In addition, communication system design considering services/UEs sensitive to reliability and latency is being discussed. As such, the introduction of next-generation RAT considering advanced mobile broadband communications, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed. Currently, 3GPP is conducting studies on the next-generation mobile communication system after EPC. In this specification, for convenience, the technology is referred to as new RAT (new RAT, NR) or 5G RAT, and a system that uses or supports NR is referred to as an NR system.

Figure 1 shows an example of communication system 1 to which implementations of the present specification are applied. Referring to FIG. 1, the communication system 1 to which this 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, wireless devices include robots (100a), vehicles (100b-1, 100b-2), XR (eXtended Reality) devices (100c), hand-held devices (100d), and home appliances (100e). ), IoT (Internet of Thing) device (100f), and AI device/server (400). For example, vehicles may include vehicles equipped with wireless communication functions, autonomous vehicles, vehicles capable of inter-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone). XR devices include AR (Augmented Reality)/VR (Virtual Reality)/MR (Mixed Reality) devices, HMD (Head-Mounted Device), HUD (Head-Up Display) installed in vehicles, televisions, smartphones, It can be implemented in the form of computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches, smart glasses), and computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, a BS,network may also be implemented with wireless devices, and a,specific wireless device may operate as a BS/network node to,other wireless devices.

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

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

Figure 2 is a block diagram showing examples of communication devices capable of performing a method according to the present specification. Referring to FIG. 2, the first wireless device 100 and the second wireless device 200 may transmit and/or receive wireless signals through various wireless access technologies (eg, LTE, NR). Here, {first wireless device 100, second wireless device 200} refers to {wireless device 100x, BS 200} and/or {wireless device 100x, wireless device 100x) in FIG. } can be responded to.

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. Processor 102 controls memory 104 and/or transceiver 106 and may be configured to implement functions, procedures and/or methods described/suggested below. For example, the processor 102 may process information in the memory 104 to generate first information/signal and then transmit a wireless signal including the first information/signal through the transceiver 106. Additionally, the processor 102 may receive a wireless signal including the second information/signal through the transceiver 106 and then store information obtained from signal processing of the second information/signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, memory 104 may perform some or all of the processes controlled by processor 102 or store software code containing instructions for performing the procedures and/or methods described/suggested below. there is. Here, the processor 102 and memory 104 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR). Transceiver 106 may be coupled to processor 102 and may transmit and/or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and/or receiver. The transceiver 106 can be used interchangeably with an RF (Radio Frequency) unit. In this specification, a wireless device may mean a communication modem/circuit/chip.

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

Wireless communication technologies implemented in the

wireless devices

100 and 200 of this specification may include Narrowband Internet of Things for low-power communication as well as LTE, NR, and 6G. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is limited to the above-mentioned names. no. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. At this time, as an example, LTE-M technology may be an example of LPWAN technology, and may be called various names such as enhanced Machine Type Communication (eMTC). For example, LTE-M technologies include 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. It can be implemented in at least one of various standards such as Type Communication, and/or 7) LTE M, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification is at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication. It may include any one, and is not limited to the above-mentioned names. As an example, ZigBee technology can create personal area networks (PAN) related to small/low-power digital communications based on various standards such as IEEE 802.15.4, and can be called by various names.

Hereinafter, the hardware elements of the

wireless devices

100 and 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 operate on one or more layers (e.g., a physical (PHY) layer, a medium access control (MAC) layer, and a radio link control (RLC) layer. , functional layers such as packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP)) can be implemented. One or

more processors

102, 202 may process one or more protocol data units (PDUs) and/or one or more service data units (SDUs) according to the functions, procedures, proposals and/or methods disclosed herein. ) can be created. One or

more processors

102, 202 may generate messages, control information, data or information according to the functions, procedures, suggestions and/or methods disclosed herein. One or

more processors

102, 202 may process signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data or information in accordance with the functions, procedures, proposals and/or methods disclosed herein. Can be generated and provided to one or more transceivers (106, 206). One or

more processors

102, 202 may receive signals (e.g., baseband signals) from one or

more transceivers

106, 206 and transmit a PDU, SDU, or PDU according to the functions, procedures, proposals, and/or methods disclosed herein. , messages, control information, data or information can be obtained.

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. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) May be included in one or

more processors

102 and 202. The functions, procedures, suggestions 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, suggestions 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) to enable one or more processors (102, 202). 202). The functions, procedures, suggestions and or methods disclosed in this specification may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.

One or

more memories

104, 204 may be connected to one or

more processors

102, 202 and may store various types of data, signals, messages, information, programs, codes, instructions, and/or instructions. One or

more memories

104, 204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof. One or

more memories

104, 204 may be located internal to and/or external to 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.

One or

more transceivers

106, 206 may transmit user data, control information, wireless signals/channels, etc. mentioned in the methods and/or operational flowcharts 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. referred to in the functions, procedures, proposals, methods and/or operational flowcharts disclosed in this specification, etc. from one or more other devices. For example, one or

more transceivers

106, 206 may be coupled with 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. In addition, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may perform the functions and procedures disclosed in this specification through one or more antennas (108, 208). , may be set to transmit and/or receive user data, control information, wireless signals/channels, etc. mentioned in the proposals, methods and/or operation flowcharts, etc. In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (eg, antenna ports). One or more transceivers (106, 206) process the received user data, control information, wireless signals/channels, etc. using one or more processors (102, 202), and process the received wireless signals/channels, etc. in the RF band signal. It can be converted to a baseband signal. One or more transceivers (106, 206) may convert user data, control information, wireless signals/channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or

more transceivers

106, 206 may comprise (analog) oscillators and/or filters.

3 illustrates another example of a wireless device capable of implementing implementation(s) of the present specification. Referring to FIG. 3, the

wireless devices

100 and 200 correspond to the

wireless devices

100 and 200 of FIG. 2 and include various elements, components, units/units, and/or modules. It can be composed of (module). For example, the

wireless devices

100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit may include communication circuitry 112 and transceiver(s) 114. For example, communication circuitry 112 may include one or

more processors

102, 202 and/or one or

more memories

104, 204 of FIG. 2. For example, transceiver(s) 114 may include one or

more transceivers

106, 206 and/or one or

more antennas

108, 208 of FIG. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls overall operations of the wireless device. For example, the control unit 120 may control the electrical/mechanical operation of the wireless device based on the program/code/command/information stored in the memory unit 130. In addition, the control unit 120 transmits the information stored in the memory unit 130 to the outside (e.g., another communication device) through the communication unit 110 through a wireless/wired interface, or to the outside (e.g., to another communication device) through the communication unit 110. Information received through a wireless/wired interface from another communication device may be stored in the memory unit 130.

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, wireless devices include robots (FIG. 1, 100a), vehicles (FIG. 1, 100b-1, 100b-2), XR devices (FIG. 1, 100c), portable devices (FIG. 1, 100d), and home appliances. (Figure 1, 100e), IoT device (Figure 1, 100f), digital broadcasting UE, hologram device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate/environment device, It can be implemented in the form of an AI server/device (Figure 1, 400), BS (Figure 1, 200), network node, etc. Wireless devices can be mobile or used in fixed locations depending on the usage/service.

In FIG. 3 , various elements, components, units/parts, and/or modules within the

wireless devices

100 and 200 may be entirely interconnected through a wired interface, or at least a portion may be wirelessly connected through the communication unit 110. For example, within the

wireless devices

100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (e.g., 130 and 140) are connected through the communication unit 110. Can be connected wirelessly. Additionally, each element, component, unit/part, and/or module within the

wireless devices

100 and 200 may further include one or more elements. For example, the control unit 120 may be comprised of one or more processor sets. 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, and a memory control processor. As another example, the memory unit 130 includes random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and/or a combination thereof.

In the present specification, at least one memory (e.g., 104 or 204) can store instructions or programs, wherein the instructions or programs, when executed, are operably coupled to the at least one memory. A single processor can be enabled to perform operations according to several embodiments or implementations of the present specification.

In the present specification, a computer-readable (non-volatile) storage medium can store at least one instruction or computer program, and the at least one instruction or computer program is executed by at least one processor. When executed, it may cause the at least one processor to perform operations according to several embodiments or implementations of the present specification.

In the present specification, a processing device or apparatus may include at least one processor and at least one computer memory connectable to the at least one processor. The at least one computer memory may store instructions or programs that, when executed, cause at least one processor operably coupled to the at least one memory to perform some of the instructions or programs of the present disclosure. Operations according to embodiments or implementations may be performed.

In this specification, a computer program is stored in at least one computer-readable (non-volatile) storage medium and, when executed, performs operations in accordance with some implementations of this specification or causes at least one processor to perform some implementations of this specification. It may include program code that performs operations according to the instructions. 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-volatile) storage medium.

The communication device of the present specification includes at least one processor; and at least storing instructions operably connectable to the at least one processor and, when executed, causing the at least one processor to perform operations according to example(s) of the present disclosure described below. Contains one computer memory.

Figure 4 shows an example of a frame structure available in a 3GPP-based wireless communication system.

The structure of the frame in FIG. 4 is only an example, and the number of subframes, number of slots, and number of symbols in the frame can be changed in various ways. In the NR system, OFDM numerology (e.g., subcarrier spacing (SCS)) may be set differently between a plurality of cells aggregated to one UE. Accordingly, the same number of symbols The (absolute time) duration of time resources (e.g., subframes, slots, or transmission time intervals (TTI)) configured as may be set differently between the aggregated cells. Symbol (or, cyclic prefix - orthogonal frequency division multiplexing (CP-OFDM) symbol), SC-FDMA symbol (or, discrete Fourier transform-spread-OFDM, In this specification, the symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbol can be replaced with each other.

Referring to FIG. 4, in the NR system, uplink and downlink transmissions are organized into frames. Each frame has a duration of T _f = (Δf _max *N _f /100)*T _c = 10 ms and is divided into two half-frames, each of 5 ms duration. Here, the basic time unit for NR is T _c = 1/(△f _max *N _f ), △f _max = 480*10 ³ Hz, and N _f =4096. For reference, the basic time unit for LTE is T _s = 1/(△f _ref *N _f,ref ), △f _ref = 15*10 ³ Hz, and N _f,ref =2048. T _c and T _f have a relationship of the constant κ = T _c /T _f = 64. Each half-frame consists of 5 subframes, and the period T _sf of a single subframe is 1 ms. 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. In a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, and in the case of an extended CP, each slot consists of 12 OFDM symbols. The numerology depends on the exponentially scalable subcarrier spacing Δf = 2 ^u * 15 kHz. The following table shows the number of OFDM symbols per slot ( N ^slot _symb ), the number of slots per frame ( N ^frame,u _slot ), and the number of slots per subframe according to the subcarrier spacing △f = 2 ^u *15 kHz for regular CP. ( N ^subframe,u _slot ).

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

For a subcarrier spacing setting u, the slots are arranged in increasing order within a subframe as n ^u _s ∈ {0, ..., n ^subframe,u _slot - 1} and in increasing order within a frame as n ^u _s,f ∈ { Numbered as 0, ..., n ^{frame, u} _slot - 1}.

Figure 5 illustrates a resource grid of slots. A slot includes a plurality of symbols (eg, 14 or 12) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N ^start, indicated by higher layer signaling (e.g., radio resource control (RRC) signaling), Starting from ^u _grid , a resource grid of N ^size,u _grid,x * N ^RB _sc subcarriers and N ^subframe,u _symb 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 downlink and UL for uplink. N ^RB _sc is the number of subcarriers per RB, and in a 3GPP-based wireless communication system, N ^RB _sc is usually 12. There is one resource grid for a given antenna port p , subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth N ^size,u _grid for the subcarrier spacing setting u is given to the UE by upper layer parameters (e.g., RRC parameters) from the network. Each element in the resource grid for the antenna port p and the subcarrier spacing setting u is called a resource element (RE), and one complex symbol may be mapped to each resource element. Each resource element in 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 the NR system, RB is 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 the subcarrier spacing setting u . The center of subcarrier 0 of CRB 0 for the subcarrier spacing setting u coincides with 'point A', which is a common reference point for resource block grids. PRBs for subcarrier spacing setting u are defined within a bandwidth part (BWP) and are numbered from 0 to N ^size,u _BWP,i -1, where i is the number of the bandwidth part. The relationship between common resource block n ^u _CRB and physical resource block n _PRB in bandwidth part i is as follows: n ^u _PRB = n ^u _CRB + N ^start,u _BWP,i , where N ^start,u _BWP,i is the bandwidth. This is a common resource block whose parts start relative to CRB 0. BWP includes multiple consecutive RBs in the frequency domain. For example, a BWP is a subset of contiguous CRBs defined for a given numerology u _i within BWP i on a given carrier. A carrier wave may contain up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through activated BWPs, and among the BWPs configured for the UE, only a predetermined number (e.g., one) of BWPs can be activated on the corresponding carrier.

For each serving cell in a set of DL BWPs or UL BWPs, the network must have at least an initial DL BWP and one (if the serving plan is set up with uplink) or two (if using supplementary uplink). Set the initial UL BWP. The network may configure additional UL 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) cyclic prefix, iii) resource offset RB _set and length L _RB with the assumption that N ^start _BWP = 275. CRB N ^start _BWP = O _carrier + RB _start and the number of contiguous RBs N ^size _BWP = L _RB , provided by the RRC parameter locationAndBandwidth indicated by the resource indicator value (RIV), and for the subcarrier spacing. O _carrier provided by RRC parameter offsetToCarrier ; Index within the set of DL BWPs or UL BWPs; A set of BWP-common parameters and a set of BWP-specific parameters.

Virtual resource blocks (VRBs) are defined within a bandwidth part and numbered from 0 to N ^size,u _BWP,i -1, where i is the number of the bandwidth part. VRBs are mapped to physical resource blocks (PRBs) according to interleaved mapping or non-interleaved mapping. In some implementations, for non-interleaved VRB-to-PRB mapping, VRB n may be mapped to PRB n.

A UE with carrier aggregation configured may be configured to use one or more cells. When a UE is configured to have multiple serving cells, the UE may be configured to have one or multiple cell groups. A UE may be configured to have multiple cell groups associated with different BSs. Alternatively, the UE may be configured to have multiple cell groups associated with a single BS. Each cell group of the UE consists of one or more serving cells, and each cell group includes a single PUCCH cell with PUCCH resources configured. The PUCCH cell may be a Pcell or a Scell configured as a PUCCH cell among the Scells of the corresponding cell group. Each serving cell of the UE belongs to one of the UE's cell groups and does not belong to multiple cell groups.

NR frequency bands are defined in two types of frequency ranges, FR1 and FR2, with FR2 also called millimeter wave (mmW). The following table illustrates the frequency ranges in which NR can operate.

Hereinafter, physical channels that can be used in a 3GPP-based wireless communication system will be described in more detail.

PDCCH carries DCI. For example, PDCCH (i.e., DCI) includes transmission format and resource allocation for a downlink shared channel (DL-SCH), resource allocation information for an uplink shared channel (UL-SCH), Located above the physical layer among the protocol stacks of the UE/BS, such as paging information on the paging channel (PCH), system information on the DL-SCH, and random access response (RAR) transmitted on the PDSCH. It carries resource allocation information for control messages of the layer (hereinafter, upper layer), transmission power control commands, activation/deactivation of configured scheduling (CS), etc. 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. 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 usage of the PDCCH. Example For example, if the PDCCH is for a specific UE, the CRC is masked with the UE identifier (e.g., cell RNTI (C-RNTI)), and if the PDCCH is for paging, the CRC is masked with the paging RNTI (P-RNTI). If the PDCCH relates to system information (e.g., system information block (SIB)), the CRC is masked with a system information RNTI (SI-RNTI). If the PDCCH relates to a random access response, the CRC is masked with It is masked with random access RNTI (RA-RATI).

When the PDCCH on one serving cell schedules the PDSCH or PUSCH on another serving cell, it is called cross-carrier scheduling. Cross-carrier scheduling using a carrier indicator field (CIF) may allow the PDCCH of a serving cell to schedule resources on other serving cells. Meanwhile, scheduling the PDSCH or PUSCH on the serving cell to the serving cell is called self-carrier scheduling. If cross-carrier scheduling is used in a cell, the BS can provide the UE with information about the cell scheduling the cell. For example, the BS tells the UE whether the serving cell is scheduled by the PDCCH on another (scheduling) cell or by the serving cell, and if the serving cell is scheduled by another (scheduling) cell, which cell is it? It is possible to provide signaling of downlink assignments and uplink grants for the serving cell. In this specification, a cell that carries the PDCCH is called a scheduling cell, and a cell in which transmission of the PUSCH or PDSCH is scheduled by the DCI included in the PDCCH, that is, a cell that carries the PUSCH or PDSCH scheduled by the PDCCH. is called a scheduled cell.

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

PUCCH refers to the physical layer UL channel for UCI transmission. PUCCH carries UCI (Uplink Control Information). UCI types transmitted on PUCCH include hybrid automatic repeat request (HARQ) - acknowledgment (ACK) information, scheduling request (SR), and channel state information (CSI). do. The UCI bits include hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information bits, if present, SR information bits, if present, 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 established rules is called a HARQ-ACK codebook.

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

- Hybrid automatic repeat request (HARQ)-acknowledgement (ACK): A response to a downlink data packet (e.g., codeword) on the PDSCH. Indicates whether the downlink data packet has been successfully received by the communication device. 1 bit of HARQ-ACK may be transmitted in response to a single codeword, and 2 bits of HARQ-ACK may be transmitted in response to two codewords. The HARQ-ACK response includes positive ACK (simply ACK), negative ACK (NACK), DTX or NACK/DTX. Here, the term HARQ-ACK is used interchangeably with HARQ ACK/NACK, ACK/NACK, or A/N.

- Channel state information (CSI): Feedback information for the downlink channel. CSI includes channel quality information (CQI), rank indicator (RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CSI-RS resource indicator, CRI), and SS. /PBCH may include resource block indicator (SSBRI), layer indicator (LI), etc. CSI can be divided into CSI Part 1 and CSI Part 2 depending on the UCI type included in the CSI. For example, CRI, RI, and/or CQI for the first codeword may be included in CSI Part 1, and LI, PMI, and CQI for the second codeword may be included in CSI Part 2.

- Link recovery request (LRR)

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

PUCCH formats can be classified as follows depending on UCI payload size and/or transmission length (e.g., number of symbols constituting PUCCH resources). For details on the PUCCH format, please refer to Table 4.

(0) PUCCH format 0 (PF0, F0)

- Supportable UCI payload size: up to K bits (e.g. K = 2)

- Number of OFDM symbols making up a single PUCCH: 1 to X symbols (e.g., X = 2)

- Transmission structure: PUCCH format 0 consists of only a UCI signal without DMRS, and the UE transmits the UCI status by selecting and transmitting one of a plurality of sequences. For example, the UE transmits one sequence among a plurality of sequences through PUCCH, which is PUCCH format 0, and transmits a specific UCI to the BS. The UE transmits a PUCCH with PUCCH format 0 within the PUCCH resource for SR configuration only when transmitting a positive SR.

- Settings for PUCCH format 0 include the following parameters for the corresponding PUCCH resource: index for initial cyclic transition, number of symbols for PUCCH transmission, and first symbol for the PUCCH transmission.

(1) PUCCH format 1 (PF1, F1)

- Supportable UCI payload size: up to K bits (e.g. K = 2)

- Number of OFDM symbols making up a single PUCCH: Y to Z symbols (e.g. Y = 4, Z = 14)

- Transmission structure: DMRS and UCI are set/mapped to different OFDM symbols in TDM format. That is, DMRS is transmitted in a symbol in which no modulation symbol is transmitted. UCI is expressed by multiplying a specific sequence (e.g., orthogonal cover code, OCC) by a modulation (e.g., QPSK) symbol. Cyclic shift (CS)/OCC is applied to both UCI and DMRS ( Code division multiplexing (CDM) is supported between multiple PUCCH resources (within the same RB) (following PUCCH format 1). PUCCH format 1 carries UCI of up to 2 bits in size, and the modulation symbol is in the time domain. It is spread by an orthogonal cover code (OCC) (set differently depending on whether the frequency hopping occurs).

- Settings for PUCCH format 1 include the following parameters for the corresponding PUCCH resource: index for initial cyclic transition, number of symbols for PUCCH transmission, first symbol for PUCCH transmission, orthogonal cover code ) index for.

(2) PUCCH format 2 (PF2, F2)

- Supportable UCI payload size: more than K bits (e.g. K = 2)

- Number of OFDM symbols making up a single PUCCH: 1 to X symbols (e.g., X = 2)

- Transmission structure: DMRS and UCI are set/mapped in the form of frequency division multiplex (FDM) within the same symbol. The UE transmits by applying only IFFT without DFT to the coded UCI bits. PUCCH format 2 carries UCI with a bit size larger than K bits, and modulation symbols are transmitted using DMRS and FDM. For example, DMRS is located at symbol indices #1, #4, #7, and #10 within a given resource block at a density of 1/3. A pseudo noise (PN) sequence is used for the DMRS sequence. Frequency hopping can be activated for 2-symbol PUCCH format 2.

- Settings for PUCCH format 2 include the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, and the first symbol for the PUCCH transmission.

(3) PUCCH format 3 (PF3, F3)

- Supportable UCI payload size: more than K bits (e.g. K = 2)

- Transmission structure: DMRS and UCI are set/mapped to different symbols in TDM format. The UE applies DFT to the coded UCI bits and transmits them. PUCCH format 3 does not support UE multiplexing on the same time-frequency resource (e.g., same PRB).

- Settings for PUCCH format 3 include the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, and the first symbol for the PUCCH transmission.

(4) PUCCH format 4 (PF4, F4)

- Supportable UCI payload size: more than K bits (e.g. K = 2)

- Transmission structure: DMRS and UCI are set/mapped to different symbols in TDM format. PUCCH format 4 can multiplex up to 4 UEs within the same PRB by applying OCC in the DFT front end and CS (or interleaved FDM (IFDM) mapping) to DMRS. In other words, UCI modulation symbols are transmitted through DMRS and TDM (Time Division Multiplexing).

- Settings for PUCCH format 4 include the following parameters for the corresponding PUCCH resource: the number of symbols for PUCCH transmission, the length for the orthogonal cover code, the index for the orthogonal cover code, and the first symbol for the PUCCH transmission.

The following table illustrates PUCCH formats. Depending on the PUCCH transmission length, it can be divided into short PUCCH (formats 0, 2) and long PUCCH (formats 1, 3, 4).

PUCCH resources may be determined for each UCI type (e.g., A/N, SR, CSI). PUCCH resources used for UCI transmission can be determined based on UCI (payload) size. For example, the BS configures a plurality of PUCCH resource sets to the UE, and the UE may select a specific PUCCH resource set corresponding to a specific range according to the range of UCI (payload) size (e.g., number of UCI bits). For example, the UE may select one of the following PUCCH resource sets according to the number of UCI bits (N _UCI ).

- PUCCH resource set #0, if UCI bit number =< 2

- PUCCH resource set #1, if 2< UCI number of bits =< N ₁

...

- PUCCH resource set #(K-1), if N _K-2 < Number of UCI bits =< N _K-1

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

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

PUCCH format

2, 3 or 4.

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

In the case of DCI-based PUCCH resource scheduling, the BS transmits DCI to the UE through PDCCH, and determines the PUCCH to be used for UCI transmission within a specific PUCCH resource set through the ACK/NACK resource indicator (ARI) in the DCI. Resources can be directed. ARI is used to indicate PUCCH resources for ACK/NACK transmission, and may also be referred to as a PUCCH resource indicator (PRI). Here, DCI is a DCI used for PDSCH scheduling, and UCI may include HARQ-ACK for PDSCH. Meanwhile, the BS can set a PUCCH resource set consisting of more PUCCH resources than the number of states that can be expressed by ARI to the UE using a (UE-specific) higher layer (e.g., RRC) signal. At this time, ARI indicates a PUCCH resource sub-set within the PUCCH resource set, and which PUCCH resource to use within the indicated PUCCH resource sub-set is determined by transmission resource information for the PDCCH (e.g., PDCCH start control channel element (control channel element) It can be determined according to implicit rules based on (element, CCE) index, etc.

The UE must have uplink resources available to the UE in order to transmit UL-SCH data, and must have downlink resources available to the UE in order to receive DL-SCH data. 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 an uplink grant, and downlink resource allocation is also referred to as downlink allocation. The uplink grant is received dynamically by the UE on the PDCCH or within the RAR, or is set semi-persistently to the UE by RRC signaling from the BS. The downlink assignment is received dynamically by the UE on the PDCCH or set semi-persistently to the UE by RRC signaling from the BS.

In UL, the BS can dynamically allocate uplink resources to the UE through PDCCH(s) addressed to a temporary identifier (cell radio network temporary identifier, C-RNTI). The UE monitors the PDCCH(s) to find possible uplink grant(s) for UL transmission. Additionally, the BS can allocate uplink resources using the grant set to the UE. Two types of established grants can be used: Type 1 and Type 2. For type 1, the BS directly provides a configured uplink grant (including period) through RRC signaling. In the case of type 2, the BS sets the period of the RRC-configured uplink grant through RRC signaling, and configures the configured scheduling RNTI (CS-RNTI) through PDCCH (PDCCH addressed to CS-RNTI). The uplink grant can be signaled and activated or deactivated. For example, in the case of type 2, the PDCCH addressed to CS-RNTI indicates that the corresponding uplink grant can be implicitly reused according to the period set by RRC signaling until deactivated.

In DL, BS can dynamically allocate downlink resources to the UE through PDCCH(s) addressed with C-RNTI. The UE monitors the PDCCH(s) to find possible downlink assignments. Additionally, the BS can allocate downlink resources to the UE using semi-static scheduling (SPS). The BS sets the period of downlink assignments set through RRC signaling, and signals and activates or deactivates the set downlink assignments through PDCCH addressed to CS-RNTI. For example, the PDCCH addressed to CS-RNTI indicates that the corresponding downlink assignment can be implicitly reused according to the period set by RRC signaling until deactivated.

Hereinafter, resource allocation by PDCCH and resource allocation by RRC are described in more detail.

* Resource allocation by PDCCH: Dynamic grant/allocation

PDCCH can be used to schedule DL transmission on PDSCH or UL transmission on PUSCH. The DCI on the PDCCH scheduling DL transmission may include DL resource allocation, including at least modulation and coding format (e.g., modulation and coding scheme (MCS) index I _MCS ), resource allocation, and HARQ information related to the DL-SCH. You can. The DCI on the PDCCH scheduling UL transmission may include an uplink scheduling grant, including at least modulation and coding format, resource allocation, and HARQ information related to the UL-SCH. HARQ information for DL-SCH or for UL-SCH includes new data indicator (NDI), transport block size (TBS), redundancy version (RV), and HARQ process ID ( That is, it may include a HARQ process number). The size and use of DCI carried by one PDCCH vary depending on the DCI format. For example, DCI format 0_0, DCI format 0_1, or DCI format 0_2 may be used for scheduling of PUSCH, and DCI format 1_0, DCI format 1_1, or DCI format 1_2 may be used for scheduling of PDSCH. In particular, DCI format 0_2 and DCI format 1_2 have higher transmission reliability and lower latency than the transmission reliability and latency requirements guaranteed by DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. It can be used to schedule transmissions with requirements. Some implementations of this specification can be applied to UL data transmission based on DCL format 0_2. Several implementations of this specification can be applied to DL data reception based on DCI format 1_2.

Figure 6 shows an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.

The DCI carried by the PDCCH for scheduling the PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, where the TDRA field is a row in an allocation table for the PDSCH or PUSCH. ) Provides the value m for index m +1. A predefined default PDSCH time domain allocation is applied as the allocation table for PDSCH, or a PDSCH time domain resource allocation table set by the BS through RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for PDSCH. A predefined default PUSCH time domain allocation is applied as the allocation table for PUSCH, or a PUSCH time domain resource allocation table set by the BS through RRC signaling pusch-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).

In the PDSCH time domain resource settings, each indexed row has a DL assignment-to-PDSCH slot offset K ₀ , a start and length indicator value SLIV (or directly the start position of the PDSCH within the slot (e.g., start symbol index S ), and an assignment length. (e.g. number of symbols L )), defines the PDSCH mapping type. In the PUSCH time domain resource settings, each indexed row includes the UL grant-to-PUSCH slot offset K ₂ , the start position of the PUSCH in the slot (e.g., start symbol index S ) and allocation length (e.g., number of symbols L ), and PUSCH mapping. Define the type. K ₀ for PDSCH or K ₂ for PUSCH indicates the difference between a slot with a PDCCH and a slot with a PDSCH or PUSCH corresponding to the PDCCH. SLIV is a joint indication of a start symbol S relative to the start of a slot with PDSCH or PUSCH and the number L of consecutive symbols counted from the symbol S. For PDSCH/PUSCH mapping type, 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, a 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 of the symbols of the PDSCH/PUSCH resource or Two symbols can be used as the DMRS symbol(s). For example, for PDSCH/PUSCH mapping type A, the DMRS uses the third symbol (symbol #2) or the fourth symbol (symbol #2) in the slot depending on the 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, starting from the first symbol of the PDSCH/PUSCH resource depending on other DMRS parameters. Two symbols can be used as DMRS symbol(s). For example, for PDSCH/PUSCH mapping type B, the DMRS is located in the first symbol allocated for PDSCH/PUSCH. 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. It is also referred to as Type B.

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

* Resource allocation by RRC

As mentioned earlier, for uplink, there are two types of transmission without dynamic grant: Configured Grant Type 1 and Configured Grant Type 2. For Configured Grant Type 1, the UL grant is provided by RRC signaling to be used as the configured grant. It is saved. In the case of configured grant type 2, the UL grant is provided by PDCCH and is stored or cleared as a configured uplink grant based on L1 signaling indicating activation or deactivation of the configured uplink grant. Type 1 and Type 2 can be set by RRC signaling for each serving cell and each BWP. Multiple settings may be active simultaneously on different serving cells.

When configured grant type 1 is configured, the UE can receive the following parameters from the BS through RRC signaling:

- cs- RNTI, CS-RNTI for retransmission;

- periodicity , which is the period of the set grant type 1;

- timeReferenceSFN indicating the system frame number (SFN) used for determining the offset of the resource in the time domain;

- timeDomainOffset , the offset relative to the reference SFN indicated by timeReferenceSFN ;

- a timeDomainAllocation value m , giving a row index m +1 pointing to the allocation table, representing a combination of start symbol S , length L , and PUSCH mapping type;

- frequencyDomainAllocation , which provides frequency domain resource allocation; and

- mcsAndTBS which provides I _MCS indicating the modulation order, target code rate and transport block size.

When configuring the configuration grant type 1 for a serving cell by RRC, the UE stores the UL grant provided by RRC as a configured uplink grant for the indicated serving cell, and stores it in timeDomainOffset and S (derived from SLIV ) Initialize or re-initialize so that the set uplink grant starts at the corresponding symbol and recurs with periodicity . After an uplink grant is configured for configured grant type 1, the UE may consider that the uplink grant is recurrent in association with each symbol that satisfies the following: [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + (slot number in the frame * numberOfSymbolsPerSlot ) + symbol number in the slot] = ( timeReferenceSFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + timeDomainOffset * numberOfSymbolsPerSlot + S + N * periodicity ) modulo (1024 * numberOfSlotsPerFrame * numberOfSymbolsPerSlot ), for N >= 0, where numberOfSlotsPerFrame and numberOfSymbolsPerSlot represents the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Table 1 and Table 2).

When configured grant type 2 is configured, the UE can receive the following parameters from the BS through RRC signaling:

- cs-RNTI , which is the CS-RNTI for activation, deactivation, and retransmission; and

- Periodicity providing the period of grant type 2 set above.

The actual uplink grant is provided to the UE by PDCCH (addressed with CS-RNTI). After an uplink grant is configured for configured grant type 2, the UE may consider that the uplink grant recurs associated with each symbol that satisfies the following: [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot ) + (slot number in the frame * numberOfSymbolsPerSlot ) + symbol number in the slot] = [(SFN _{start time} * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + slot _{start time} * numberOfSymbolsPerSlot + symbol _{start time} ) + N * periodicity ] modulo (1024 * numberOfSlotsPerFrame * numberOfSymbolsPerSlot ), for all N >= 0, where SFN _{start time} , slot _{start time} , and symbol _{start time} are respectively (respectively) SFN, slot, and symbol of the first transmission opportunity of PUSCH after the set grant is (re-)initialized. numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols for each slot, respectively (see Tables 1 and 2).

ConfiguredGrantConfig , an RRC setting used to set configured grant type 1 or type 2, may include a parameter configuredGrantTimer indicating the initial value of the grant timer set as a multiple of periodicity .

In some scenarios, parameters harq-ProcID-Offset and/or harq-ProcID-Offset2 used to derive HARQ process IDs for configured uplink grants may be further provided to the UE by the BS. harq-ProcID-Offset is the offset of the HARQ process with respect to the configured grant for operation with shared spectrum channel access, and harq-ProcID-Offset2 is the offset of the HARQ process with respect to the configured grant. In this specification , cg-RetransmissionTimer is the duration during which the UE should not automatically perform retransmission using the HARQ process of the (re)transmission after (re)transmission based on the configured grant, and on the configured uplink grant This is a parameter that can be provided to the UE by the BS when retransmission of is set. For configured grants where neither harq-ProcID-Offset nor cg-RetransmissionTimer is configured, the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following equation: HARQ Process ID = [floor( CURRENT_symbol/ periodicity )] modulo nrofHARQ-Processes . For configured uplink grants with harq-ProcID-Offset2 , the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following equation: HARQ Process ID = [floor(CURRENT_symbol / periodicity )] modulo nrofHARQ- Processes + harq-ProcID-Offset2 , where CURRENT_symbol = (SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + slot number in the frame * numberOfSymbolsPerSlot + symbol number in the slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot are the number of consecutive slots per frame and the number of consecutive slots per slot. Indicates the number of OFDM symbols, respectively. For UL grants configured with cg-RetransmissionTimer , the UE may select a HARQ process ID from among HARQ process IDs available for randomly configured grant configuration.

In the case of downlink, the UE can be configured with semi-persistent scheduling (SPS) for each serving cell and each BWP by RRC signaling from the BS. For DL SPS, DL allocation is provided to the UE by PDCCH and stored or removed based on L1 signaling indicating SPS activation or deactivation. When SPS is configured, the UE may receive the following parameters from the BS via RRC signaling (e.g. SPS configuration), which are used to configure semi-persistent transmission:

- cs-RNTI, which is the CS-RNTI for activation, deactivation, and retransmission;

- nrofHARQ-Processes, which provides the number of HARQ processes configured for SPS;

- periodicity, which provides the set period of downlink allocation for SPS;

- n1PUCCH-AN providing HARQ resources for PUCCH for SPS (the network sets the HARQ resources as format 0 or format 1, the actual PUCCH-resource is set in PUCCH-Config , and n1PUCCH-AN by its ID (referred to in AN ).

Multiple downlink SPS settings may be set within the BWP of the serving cell. After downlink assignment is established for SPS, the UE may sequentially consider that the Nth downlink assignment occurs in a slot that satisfies the following: ( numberOfSlotsPerFrame * SFN + slot number in the frame ) = [( numberOfSlotsPerFrame * SFN _{start time} + slot _{start time} ) + N * periodicity * numberOfSlotsPerFrame / 10] modulo (1024 * numberOfSlotsPerFrame ), where SFN _{start time} and slot _{start time} are (re-)initialized downlink assignments. After representing the SFN, slot, and symbol of the first transmission of the PDSCH, respectively, numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Table 1 and Table 2). .

In some scenarios, the parameter harq-ProcID-Offset used to derive HARQ process IDs for configured downlink assignments may be further provided to the UE by the BS. harq-ProcID-Offset is the offset of the HARQ process for SPS. For established downlink assignments without harq-ProcID-Offset , the HARQ process ID associated with the slot where DL transmission starts can be determined from the following equation: HARQ Process ID = [floor (CURRENT_slot * 10 / ( numberOfSlotsPerFrame * periodicity ) )] modulo nrofHARQ-Processes , where CURRENT_slot = [(SFN * numberOfSlotsPerFrame ) + slot number in the frame], and numberOfSlotsPerFrame means the number of consecutive slots per frame. For established downlink assignments with harq-ProcID-Offset , the HARQ process ID associated with the slot where DL transmission starts can be determined from the following equation: HARQ Process ID = [floor (CURRENT_slot / periodicity )] modulo nrofHARQ-Processes + harq-ProcID-Offset , where CURRENT_slot = [(SFN * numberOfSlotsPerFrame ) + slot number in the frame], and numberOfSlotsPerFrame means the number of consecutive slots per frame.

The cyclic redundancy check (CRC) of the DCI format is scrambled with the CS-RNTI provided by the RRC parameter cs-RNTI and the New Data Indicator field for enabled transport blocks is set to 0. If present, the UE validates the DL SPS assigned PDCCH or the configured UL grant type 2 PDCCH as valid for scheduling activation or scheduling release. Validity confirmation of the DCI format is achieved if all fields for the DCI format are set according to Table 5 or Table 6. Table 5 illustrates special fields for DL SPS and UL grant type 2 scheduling activation PDCCH validity confirmation, and Table 6 illustrates special fields for DL SPS and UL grant type 2 scheduling release PDCCH validity confirmation.

The actual DL allocation or UL grant for DL SPS or UL grant type 2, and the corresponding modulation and coding scheme are resource allocation fields in the DCI format carried by the corresponding DL SPS or UL grant type 2 scheduling activation PDCCH ( e.g., a TDRA field providing the TDRA value m, an FDRA field providing frequency resource block allocation, and a modulation and coding scheme field). Once validation is achieved, the UE considers the information in the DCI format to be a valid activation or valid release of the DL SPS or configured UL Grant Type 2.

In this specification, the PDSCH based on DL SPS is sometimes called SPS PDSCH, the PUSCH based on UL CG is sometimes called CG PUSCH, the PDSCH dynamically scheduled by the DCI carried by the PDCCH is sometimes called DG PDSCH, and the PDCCH is called DG PDSCH. The PUSCH dynamically scheduled by the carrying DCI is also called DG PUSCH.

Figure 7 illustrates the HARQ-ACK transmission/reception process.

Referring to FIG. 7, the UE can detect the PDCCH in slot n. Thereafter, the UE may receive a PDSCH in slot n+K0 according to the scheduling information received through the PDCCH in slot n, and then transmit UCI through PUCCH in slot n+K1. Here, UCI includes a HARQ-ACK response to PDSCH.

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

- Frequency domain resource assignment (FDRA): Indicates the RB set assigned to the PDSCH.

- Time domain resource assignment (TDRA): DL assignment-to-PDSCH slot offset K0, start position (e.g., symbol index S) and length (e.g., number of symbols L) of the PDSCH in the slot, PDSCH mapping type represents. PDSCH mapping type A or PDSCH mapping type B may be indicated by TDRA. In the case of PDSCH mapping type A, the DMRS is located in the third symbol (symbol #2) or fourth symbol (symbol #3) in the slot. For PDSCH mapping type B, the DMRS is located in the first symbol allocated for the PDSCH.

- PDSCH-to-HARQ_feedback timing indicator: indicates K1.

If the PDSCH is set to transmit up to 1 TB, the HARQ-ACK response may consist of 1-bit. When the PDSCH is set to transmit up to two transport blocks (TB), the HARQ-ACK response will consist of 2-bits if spatial bundling is not set, and 1-bit if spatial bundling is set. You can. If the HARQ-ACK transmission point for a plurality of PDSCHs is designated as slot n+K1, UCI transmitted in slot n+K1 includes a HARQ-ACK response for a plurality of PDSCHs.

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

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 set semi-statically by a (UE-specific) higher layer (e.g., RRC) signal. For example, the HARQ-ACK payload size of the semi-static HARQ-ACK codebook is, the (maximum) HARQ-ACK payload (size) transmitted through one PUCCH in one slot is all DL carriers configured for the UE. (i.e., DL serving cells) and the number of HARQ-ACK bits corresponding to a combination (hereinafter, bundling window) of all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) for which the HARQ-ACK transmission timing can be indicated. It can be decided based on . In other words, the semi-static HARQ-ACK codebook method is a method in which the size of the HARQ-ACK codebook is fixed (to the maximum value) regardless of the actual number of scheduled DL data. For example, the DL grant DCI (PDCCH) includes PDSCH to HARQ-ACK timing information, and the PDSCH-to-HARQ-ACK timing information may have one of multiple values (e.g., k). For example, when a PDSCH is received in slot #m, and the PDSCH to HARQ-ACK timing information in the DL grant DCI (PDCCH) scheduling the PDSCH indicates k, the HARQ-ACK information for the PDSCH is slot # Can be transmitted at (m+k). As an example, k ∈ {1, 2, 3, 4, 5, 6, 7, 8}. Meanwhile, when 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 HARQ-ACK corresponding to slot #(n-k). For example, if k ∈ {1, 2, 3, 4, 5, 6, 7, 8}, the HARQ-ACK information in slot #n is from slot #(n-8)~, regardless of actual DL data reception. Contains HARQ-ACK corresponding to slot #(n-1) (i.e., maximum number of HARQ-ACK). Here, HARQ-ACK information can be replaced with HARQ-ACK codebook and HARQ-ACK payload. Additionally, a slot can be understood/replaced as a candidate occasion for receiving DL data. As an example, the bundling window is determined based on the PDSCH-to-HARQ-ACK timing based on the HARQ-ACK slot, and the PDSCH-to-HARQ-ACK timing set has a pre-defined value (e.g., { 1, 2, 3, 4, 5, 6, 7, 8}), can be set by upper layer (RRC) signaling. The semi-static HARQ-ACK codebook is also referred to as type-1 HARQ-ACK codebook. In the case of Type-1 HARQ-ACK codebook, the number of bits to be sent as a HARQ-ACK report is fixed and can be large. If many cells are configured but only a few cells are scheduled, the Type-1 HARQ-ACK codebook may be inefficient.

Meanwhile, in the case of a dynamic HARQ-ACK codebook, the HARQ-ACK payload size to be reported by the UE may dynamically change depending on DCI, etc. The dynamic HARQ-ACK codebook is also referred to as type-2 HARQ-ACK codebook. Type-2 HARQ-ACK codebook can be said to be a more optimized HARQ-ACK feedback because the UE sends feedback only for scheduled serving cells. However, in bad channel conditions, the UE may incorrectly determine the number of scheduled serving cells, and to solve this, DAI is included as part of DCI. For example, in the dynamic HARQ-ACK codebook method, the DL scheduling DCI may include counter-DAI (i.e., c-DAI) and/or total-DAI (i.e., t-DAI). Here, DAI means downlink assignment index, and is used by the BS to inform the UE of the transmitted or scheduled PDSCH(s) to be included in one HARQ-ACK transmission. In particular, c-DAI is an index that indicates the order between PDCCHs (hereinafter referred to as DL scheduling PDCCHs) carrying DL scheduling DCI, and t-DAI is the total number of DL scheduling PDCCHs up to the current slot where there is a PDCCH with t-DAI. It is an index representing .

Meanwhile, in the case of the HARQ process-based HARQ-ACK codebook, the HARQ-ACK payload is determined based on all HARQ processes of all serving cells configured (or activated) in the PUCCH group. For example, the HARQ-ACK payload size to be reported by the UE through the HARQ process-based HARQ-ACK codebook depends on the number of all configured or activated serving cells in the PUCCH group configured for the UE and the number of HARQ processes for the serving cells. is determined by The HARQ process-based HARQ-ACK codebook is also referred to as Type-3 HARQ-ACK codebook. Type-3 HARQ-ACK codebook can be applied to one-shot feedback.

Extended reality (XR) provides users with a virtual reality similar to reality by utilizing virtual reality (VR), augmented reality (AR), mixed reality (MR), and holograms. It is an ultra-realistic technology and service that provides an environment where one can communicate and live in space without restrictions of time and space. XR is one of the main services to be introduced in the NR wireless communication system. XR is typically characterized by specific traffic with one or more downlink video streams closely synchronized with frequent uplink pose/control updates. Additionally, XR has a high data rate and tight packet delay budget (PDB). The PDB defines an upper bound on the time that a packet can be delayed between the UE and the user plane function (UPF) of the core network. In other words, PDB can be said to be a value regarding how much time the generated packet must be transmitted.

In NR, one or more SPS PDSCH or CG PUSCH may be configured to the UE for periodic transmission and reception or low delay time and PDCCH overhead. The set/indicated resource may repeat in the time domain with a cycle according to each SPS/CG setting. For example, the initially set/indicated resource allocation is repeated at a period set by SPS/CG settings, and the UE can perform downlink reception/uplink transmission on the corresponding resource without a separate PDCCH reception process. Meanwhile, the types of data that can be generated from XR are diverse. Among these data, it is considered that the transmission of UE's sensor and location information and video data, which are generally reported at a specific period, are transmitted and received on SPS/CG resources. The traffic arrival time of such data may be inconsistent and jitter may occur due to reasons such as video encoding time, sensor measurement time, upper layer operation, or routing changes in the network being transmitted.

In NR, priority in the PHY layer was introduced for multiple services, and because of this, the UE performs uplink transmission or downlink reception using only one of the non-overlapping radio resources, or performs multiple overlapping uplink transmissions. It is also possible to perform uplink multiplexing by dividing into groups. This is because XR has the characteristic of displaying images on the screen accurately over time, so previous data may become useless after the point at which XR data is required to be provided.

To support mobility and for the UE to identify the best serving rate, intra-cell or inter-cell measurements are performed by the UE. If the UE cannot transmit/receive on the serving cell and simultaneously measure the target carrier frequency, measurement gaps are needed to perform measurements. Measurement gaps may be required for intra-frequency, inter-frequency and inter-RAT measurements. For example, measurement gap repetition periodicities such as 20, 40, 80, 60 ms and measurement gap lengths such as 1.5, 3, 3.5, 4, 5.5, 6 ms can be used for measurement gaps. there is. The UE may switch to the target cell during the measurement gap (MG) to perform signal quality measurements and return to the current cell. In some scenarios, the RF re-tuning time is 0.5 ms for carrier frequency measurements in the FR1 range and 0.25 ms for the FR2 range. During MGs, measurements may be performed on the SSBs of neighboring cells. A network (e.g., BS) may provide measurement timing of adjacent cells using SS/PBCH block measurement timing configuration (SMTC). MG and SMTC periods can be set so that the UE can identify and measure SSBs in the SMTC. The network can provide the MG pattern to the UE through RRC signaling (e.g., IE MeasGapConfig in the RRC setting MeasConfig ). RRC Configuration IE MeasGapConfig is used to specify MG configuration and control setup/teardown of MGs (see 3GPP TS 38.331 document). The MGs are periodic and the UE can be configured with multiple MGs.

MG configuration supports mobility and is required for the UE to identify the best serving cell, but also requires the UE to perform measurements for intra/inter-frequency handover and/or beam management, etc. This results in suspension of transmission/reception. For example, according to 3GPP TS 38.321 Release 17, during an activated MG, the UE may :

> Does not transmit HARQ feedback, scheduling request (SR), and channel state information (CSI);

> Without reporting sounding reference signal (SRS);

> Do not transmit on UL-SCH except Msg3 or MSGA payload, which is the first scheduled transmission of the random access process;

> ra-ResponseWindow, a time window for monitoring random access response(s) on SpCell or ra-ContentionResolutionTimer , a contention resolution timer for SpCell or random access response for two-stage random access type on SpCell ( If msgB-ResponseWindow , which is a time window for monitoring, is running, the PDCCH is monitored, otherwise (else) the PDCCH is not monitored and is not received on the DL-SCH. Here, the length of ra-ResponseWindow , the value of ra-ContentionResolutionTimer , and the length of msgB-ResponseWindow are provided to the UE by the network through RRC signaling.

MG configuration is required for delay-sensitive services such as XR applications or URLLC that support mobility, but current standards state that the corresponding measurements according to MG are based on PDSCH receptions or PUSCH transmissions carrying data for these services. Because they have higher priority, these services are interrupted during the MG period. However, in the case of services with strict latency requirements, such as XR service or URLLC service, it is required that the data or scheduling information for the data be provided in a timely manner. Therefore, in the case of XR or URLLC, which are sensitive to delay time, MG, which is a time section in which scheduling information cannot be provided, can cause a big problem.

In some scenarios (e.g., NR system), the UE may be provided with MG settings for intra-cell or inter-cell measurements from the BS. As mentioned earlier, according to the current NR standards, a UE that has been explicitly provided with MG settings transmits PUCCH/PUSCH/SRS or PDCCH/PDSCH/D during the corresponding MG period, especially in the case of measurements based on SSB reception. CSI-RS is not expected to be received. When the BS sets the MG to the UE according to the UE's SSB reception period(s), typically the UE may have an MG section every 20 ms, and each MG section may have a length of 1 to 5 ms. If there is an MG section of 5 ms every 20 ms period, the UE may not be able to perform PUCCH/PUSCH/SRS transmission or PDCCH/PDSCH/CSI-RS reception for 5 ms every 20 ms, which affects the availability of the UE. It can have an impact. For example, in order for the UE to receive or transmit periodic sensor information, the UE that has received semi-persistent scheduling (SPS)/configured grant (CG) radio resources from the BS uses the MG section and SPS. If the time-based reception time/CG-based transmission time overlap in time, SPS-based reception/CG-based transmission may not be performed.

As a way to solve these problems, defining a mechanism for scheduling XR/URLLC packets and preventing overlap between MG sections can be considered. However, considering that the MG sections according to the MG setting, which is the RRC setting, are quasi-static, the generation and scheduling of XR/URLLC data are dynamic, preventing overlap between MG sections and the generation and scheduling of XR/URLLC data. This is either realistically impossible or requires a very complicated mechanism. Therefore, it may be undesirable or realistically difficult to define a mechanism where the scheduling of MG sections and data transmission/reception overlap in time.

Several implementations of this specification are described below to solve the problems mentioned above. In some implementations of this specification, operation between the UE and BS that allows transmission/reception on the MG according to certain criteria may be considered.

Below, for convenience of explanation, some examples of implementations of this specification are described based on the NR system, but implementations of this specification are not limited by specifying the transmission/reception form of NR unless otherwise explained. In addition, below, for convenience of explanation, several implementations of this specification are described based on the characteristics and structure of the XR service, but implementations of this specification are not specifically limited to support of the XR service unless otherwise stated.

Hereinafter, for example, the UE is provided with MG configuration(s) for intra-cell or inter-cell measurements from the BS, and periodically configures adjacent MG settings for purposes such as radio resource management (RRM). When it is necessary to perform measurements on a cell or the current serving cell, when the MG is instructed or set to receive one or more scheduling for delay-sensitive services such as XR/URLLC from the BS, some of the specifications in this specification process the corresponding scheduling. Implementations are described.

Some implementations of the present specification described below may include a method for the BS to allocate PDSCH/PUSCH radio resources to the UE and a method for the UE to perform downlink reception and uplink transmission on the allocated radio resources, and PDSCH reception It may include a method of transmitting a HARQ-ACK PUCCH response for the result and a method of receiving the base station's retransmitted DCI through the PDCCH after PUSCH transmission. In addition, some implementations of this specification described later may include a process in which the UE transmits a signal and a channel to announce its capabilities and/or service requirements, and the BS receives them.

In some implementations of this specification, the transmission occasion may mean a radio resource (eg, SPS PDSCH or CG PUSCH) that occurs based on SPS/CG settings. The transmitter, which is the entity performing the transmission (e.g., BS in the downlink, UE in the uplink), may attempt to transmit a physical channel/signal at the transmission time, and the corresponding receiver (e.g., UE in the downlink, UE in the uplink) may attempt to transmit a physical channel/signal at the transmission time. In the case of a link, the BS) may expect the transmitter to transmit at each transmission time and attempt to receive. In this specification, the term transmission timing is used interchangeably with the term transmission opportunity. In addition, in this specification, the transmission time is also referred to as the reception time from the receiver's perspective. Alternatively, the term 'timing' may be used instead of the terms 'transmission time' and 'reception time'.

Figure 8 illustrates the flow of UE operation to which several implementations of the present specification may be applied.

The UE can receive the MG section for RRM, etc. from the BS through RRC signaling (e.g., RRC setting MeasConfig and/or RRC setting MeasGapConfig ) (S801). For example, one or multiple MG settings may be provided to the UE by the BS. In some implementations of the present specification, information about the configured MG interval (e.g., MG configuration) includes information about the priority of each MG interval, or the PDCCH, CSI-RS, SR, and/or SPS/CG settings associated therewith. Index(s), etc. may be included. For example, in some implementations of this specification, each MG configuration includes priority information for the corresponding MG(s), or index(s) of the PDCCH, CSI-RS, SR, and/or SPS/CG configuration associated with it. It can be included.

The PDSCH reception timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or SPS settings, or the PUSCH transmission timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or CG settings is the MG and ( If there is no overlap (in time) (S803, No), the UE can perform operation A1 (S804). The operation A1 may include performing measurements set within the MG through the RRC setting MeasConfig associated with the MG configuration, attempting to receive PDSCH at the PDSCH reception time, or performing PUSCH transmission at the PUSCH transmission time. The PDSCH reception timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or SPS settings, or the PUSCH transmission timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or CG settings is the MG and ( (in time) overlap (S803, Yes), the UE may perform operation A2 (S806) if the specific condition(s) is not satisfied (S805, No), and if the specific condition(s) are satisfied (S805) , Yes) Within the MG, PDSCH reception may be attempted at the PDSCH reception time or PUSCH transmission may be attempted at the PUSCH transmission time (S807). The operation A2 may include:

i) perform measurements set within the MG through the RRC setting MeasConfig associated with the MG setting; and

ii) On the serving cell(s) within the relevant frequency range of said MG:

> Without reporting sounding reference signal (SRS);

> ra-ResponseWindow, a time window for monitoring random access response(s) on SpCell or ra-ContentionResolutionTimer , a contention resolution timer for SpCell or random access response for two-stage random access type on SpCell ( If msgB-ResponseWindow , which is a time window for monitoring, is running, the PDCCH is monitored, otherwise (else) the PDCCH is not monitored and is not received on the DL-SCH.

In some implementations, if the specific condition(s) are satisfied (S805, Yes), the UE may perform measurements within the MG and related to the MG. Alternatively, in some implementations, if the specific condition(s) is satisfied (S805, Yes), the UE may not perform measurements related to the MG within the MG.

The specific condition(s) may include condition(s) according to any one or two or more of Implementations 1 to 5 described below.

In other words, in some implementations of this specification, the UE may receive a scheduling message or SPS/CG configuration for PDSCH reception or PUSCH transmission on the MG interval from the BS. A UE that has been instructed to perform PDSCH reception or PUSCH transmission on the MG section through an explicit scheduling message through L1 signaling (e.g., PDCCH), for example, receives the instructed PDSCH without performing adjacent cell measurement in the MG section. Alternatively, PUSCH transmission can be performed. A UE that has an SPS reception opportunity (i.e., SPS PDSCH reception time) and/or CG transmission opportunity (i.e., CG PUSCH transmission time) in the MG section may perform SPS reception or CG transmission depending on the characteristics of the MG section. For example, when the MG setting includes information about the priority in the MG section, if the information about the priority is below a certain value, the set or indicated PDSCH is received or the PUSCH is transmitted without performing adjacent cell measurement in the corresponding MG section. can be performed. As another example, when the MG setting includes information about the associated SPS setting and/or CG setting, PDSCH reception/PUSCH transmission according to the SPS/CG setting with the same index as the associated SPS/CG setting is transmitted in the MG setting. If it overlaps with the corresponding MG, the UE can receive the PDSCH or transmit the PUSCH without performing adjacent cell measurement in the corresponding MG section.

The BS may configure the MG section for RRM, etc. to the UE through RRC signaling (e.g., RRC setting MeasConfig and/or RRC setting MeasGapConfig ) (S901). For example, one or multiple MG settings may be provided to the UE by the BS. In some implementations of the present specification, information about the configured MG interval (e.g., MG configuration) includes information about the priority of each MG interval, or the PDCCH, CSI-RS, SR, and/or SPS/CG settings associated therewith. Index(s), etc. may be included. For example, in some implementations of this specification, each MG configuration includes priority information for the corresponding MG(s), or index(s) of the PDCCH, CSI-RS, SR, and/or SPS/CG configuration associated with it. It can be included.

The PDSCH transmission timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or SPS settings, or the PUSCH reception timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or CG settings is the MG and ( If there is no overlap (in time) (S903, No), the BS may assume that the UE will perform operation A1 illustrated in FIG. 8 and perform operation B1 (S904). The operation B1 may receive a measurement report related to the MG from the UE, assuming that measurements set through the RRC setting MeasConfig associated with the MG configuration will be performed within the MG, and the UE may receive a measurement report related to the MG at the time of transmitting the PDSCH. Assuming that PDSCH will be received or PUSCH transmitted at the PUSCH reception time, PDSCH transmission may be performed at the PDSCH transmission time and PUSCH reception may be attempted at the PUSCH reception time. The PDSCH transmission timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or SPS settings, or the PUSCH reception timing based on explicit scheduling through L1 signaling (e.g., PDCCH) or CG settings is the MG and ( (in time) overlap (S903, Yes), the BS may perform operation B2 assuming that the UE will perform operation A2 illustrated in FIG. 8 if certain condition(s) are not met (S905, No) (S906), if the specific condition(s) is satisfied (S905, Yes), assuming that the UE will receive the PDSCH at the PDSCH transmission time within the MG or transmit the PUSCH at the PUSCH reception time, PDSCH transmission may be performed or PUSCH reception may be attempted at the PUSCH reception time (S907).

The operation B2 may include:

i) Assuming that the UE will perform measurements set within the MG through the RRC setting MeasConfig associated with the MG setting, receive a measurement report related to the MG from the UE; and/or

ii) On the serving cell(s) within the relevant frequency range of said MG:

> Does not expect or attempt to receive HARQ feedback, scheduling request (SR), and channel state information (CSI) from the UE;

> Without expecting or attempting to report a sounding reference signal (SRS) from the UE;

> Does not expect or attempt to receive on UL-SCH from the UE except Msg3 or MSGA payload, which is the first scheduled transmission of the random access process;

> ra-ResponseWindow, a time window for monitoring random access response(s) on SpCell or ra-ContentionResolutionTimer , a contention resolution timer for SpCell or random access response for two-stage random access type on SpCell ( If msgB-ResponseWindow , which is a time window for monitoring the UE, is running, the PDCCH is transmitted to the UE. Otherwise (else), the PDCCH is not transmitted and is not transmitted to the UE on the DL-SCH.

In some implementations, the BS may expect/assume that the UE will perform measurements related to the MG within the MG if the specific condition(s) are met (S905, Yes). Or, in some implementations, the BS may expect/assume that the UE will not perform measurements related to the MG within the MG if the specific condition(s) are met (S905, Yes).

In other words, in some implementations of this specification, the BS may transmit a scheduling message or SPS/CG configuration for PDSCH reception or PUSCH transmission on the MG interval to the UE. When the UE is instructed to perform PDSCH reception or PUSCH transmission on the MG section through an explicit scheduling message through L1 signaling (e.g., PDCCH), the BS, for example, allows the UE to measure a neighboring cell in the corresponding MG section. It is possible to perform the PDSCH transmission or attempt to receive the PUSCH, expecting or assuming that the indicated PDSCH will be received or the PUSCH will be transmitted without performing the PDSCH. If an SPS transmission opportunity (i.e., SPS PDSCH transmission timing) and/or CG reception opportunity (i.e., CG PUSCH reception timing) occurs to the UE on the MG section, the BS allows the UE to receive SPS or It may operate with the expectation or assumption that CG transmission will be performed. For example, when the MG configuration includes information about the priority in the MG section, the BS does not perform adjacent cell measurement in the MG section if the UE's information about the priority is below a certain value and uses the configured or indicated PDSCH. It can operate with the expectation/assumption that reception or PUSCH transmission will be performed. As another example, when the MG settings include information about the associated SPS settings and/or CG settings, the BS determines that PDSCH transmission/PUSCH reception according to the SPS/CG settings with the same index as the associated SPS/CG settings is transmitted to the MG. If it overlaps with the MG according to the settings, the UE may operate with the expectation/assumption that it will perform the PDSCH reception or the PUSCH transmission without performing adjacent cell measurement in the corresponding MG section.

In FIGS. 8 and 9, the UE operation flow and the BS operation flow are explained by taking the case where the PDSCH/PUSCH period overlaps with the MG as an example, but the SRS period, CSI-RS period, and PUCCH period are also explained in FIGS. 8 and 9. The UE and BS can operate in the same manner.

Some of the methods according to Implementation 1 to Implementation 5 of the present specification, which will be described later, may be selected and applied. Alternatively, each method can be applied independently without any separate combination, or one or more methods can be combined and operated in a linked form.

Some implementations of this specification may be specified to apply only when the UE receives relevant configuration information from the BS (or core network). At this time, the configuration information may be provided to the UE through a higher layer signal (e.g., system information block (SIB) or RRC signaling), or the configured information may be provided to the UE through separate signaling (e.g., DCI or MAC control element). ) can also be used together with a method in which activation/deactivation is indicated. Additionally, in some implementations of the present specification, the UE may be specified to report information (e.g., capability) regarding whether it can support the method(s) described below and receive this from the BS (or core network). .

The following implementations may be considered regarding how to handle the MG and/or the physical channel when the MG and the physical channel/signal according to the MG setting overlap.

<구현 1: 명시적 스케줄링 DCI를 통해 MG를 무시/불능화(ignore/disable MG via explicit scheduling DCI)><Implementation 1: ignore/disable MG via explicit scheduling DCI>

When the UE receives an explicit scheduling DCI with the following characteristics, if the resource scheduled by the DCI overlaps with the MG, it does not perform measurement on the MG and/or transmits or receives radio resources indicated by the scheduling DCI (i.e. Transmission or reception on the wireless resource) may be given priority. The feature may be at least one of the following:

> DCI indicating higher priority (HP) PUCCH/PUSCH/SRS transmission or HP PDCCH/PDSCH/CSI-RS reception. For example, implementation 1 can be used for reception/transmission scheduled by DCI that includes a priority index with a value greater than a certain threshold (e.g., 0). The threshold value may be indicated through L1 signaling or higher layer signaling of the BS when the UE has three or more available priorities, and may be 0 when the UE has two available priorities.

> DCI directing SPS/CG activation

> DCI instructing downlink reception

> DCI directing uplink transmission

In some implementations, Implementation 1 may be limited to only downlink reception scheduling, or only uplink transmission scheduling. If Implementation 1 is limited to downlink reception scheduling, the UE may not apply Implementation 1 to transmitting a HARQ-ACK response to the PDSCH received in the downlink reception process on PUCCH/PUSCH. If Implementation 1 is limited to downlink transmission scheduling, the BS may not apply Implementation 1 to receiving on PUCCH/PUSCH the HARQ-ACK response to the PDSCH transmitted during the downlink transmission process.

In some implementations, whether implementation 1 behavior applies may differ between MG settings. For example, the UE does not perform measurements on the MG only if an explicit scheduling DCI with the above characteristics overlaps with a specific MG and/or transmits or receives a radio resource indicated by the scheduling DCI (i.e., transmits on the radio resource) or reception) can be performed. This specific MG may be determined by the presence or absence of a certain parameter in the MG settings, or may be determined by the value of a certain parameter. For example, the size of the RRC parameter mgl or mgl-r16 value indicating the length of the MG section (i.e., MG length) is greater than or equal to a certain size, or the above specific MG can be determined.

<구현 2: 특정 SPS/CG에 대해 MG를 무시/불능화(ignore/disable MG for specific SPS/CG)><Implementation 2: Ignore/disable MG for specific SPS/CG>

When the UE receives an SPS/CG setting with the following characteristics, the radio resource reception/transmission opportunity of the SPS/CG setting (i.e., the transmission/reception opportunity on the radio resource) and the MG overlap in time, measure on the MG. Without performing scheduling, priority may be given to transmission or reception of radio resources indicated by the DCI (i.e., transmission or reception on the radio resources). The feature may be at least one of the following:

> SPS/CG settings with HP set. For example, Implementation 2 can be used for receive/transmit opportunities obtained from an SPS/CG setting where a priority index is set with a value greater than some threshold (e.g., 0). The threshold may be indicated through L1 signaling or higher layer signaling of the BS when the UE has three or more available priorities, and may be 0 when the UE has two available priorities.

>> SPS/CG settings including specific RRC parameters. In some implementations, the specific RRC parameter may be a parameter for configuring whether to use implementation 2.

>> SPS settings to indicate downlink reception

>> CG settings that direct uplink transmission

In some implementations, applying Implementation 2 may be limited to only downlink received SPS or only uplink transmitted CG. If Implementation 2 is limited to only downlink reception SPS, the UE may not apply Implementation 2 to transmitting the HARQ-ACK response for the PDSCH received at the corresponding SPS reception opportunity on PUCCH/PUSCH. If Implementation 2 is limited to downlink transmission SPS, the BS may not apply Implementation 2 to receiving the HARQ-ACK response for the PDSCH transmitted at the corresponding SPS transmission time on PUCCH/PUSCH.

In some implementations, whether implementation 2 behavior applies may differ between MG settings. For example, the UE does not perform measurements on the MG only when the PDSCH reception opportunity based on the SPS setting with the above characteristics and/or the PUSCH transmission opportunity based on the CG setting overlaps with a specific MG and/or transmits radio resources according to the setting. Alternatively, reception (i.e., transmission or reception on the radio resource) may be performed. The BS does not perform measurement on the MG only when the PDSCH transmission opportunity based on the SPS setting with the above characteristics and/or the PUSCH reception opportunity based on the CG setting overlaps with a specific MG, and/or transmits or receives radio resources according to the setting. It may operate with the expectation/assumption that (i.e., transmission or reception on the radio resource) will be performed. This specific MG may be determined by the presence or absence of a certain parameter in the MG settings, or may be determined by the value of a certain parameter. For example, the size of the RRC parameter mgl or mgl-r16 value indicating the length of the MG section (i.e., MG length) is greater than or equal to a certain size, or the above specific MG can be determined.

<구현 3: 특정 탐색 공간/CORESET에 대해 MG를 무시/불능화(ignore/disable MG for specific search space/CORESET)><Implementation 3: ignore/disable MG for specific search space/CORESET>

When the UE receives a search space (SS) and/or CORESET setting with the following characteristics (i.e., when it receives a search space setting and/or CORESET setting with the following characteristics), the corresponding SS/CORESET settings If this indicated PDCCH monitoring opportunity (i.e., PDCCH monitoring timing) and the MG overlap in time, PDCCH monitoring for PDCCH reception/detection may be prioritized without performing measurement on the MG. The feature may be at least one of the following:

> SS/CORESET settings including specific RRC parameters. In some implementations, the specific RRC parameter may be a parameter for configuring whether to use implementation 3.

> SS settings to receive specific DCI format. In some implementations, the specific DCI format is a group common DCI or It may be DCI format 0_2, 1_2. The BS may transmit a group common DCI to UEs communicating in the frequency range associated with the MG to prioritize PDCCH monitoring over the MG. DCI format 0_2, 1_2 is a compact DCI that can increase transmission reliability by making the payload size relatively small compared to other scheduling DCI formats, so BS can utilize DCI format 0_2, 1_2 to prioritize scheduling for specific services over MG. You can.

In some implementations, whether implementation 3 behavior applies may differ between MG settings. For example, the UE may not perform measurement on the MG only when the PDCCH monitoring period according to the SS setting and/or CORESET setting having the above characteristics overlaps with a specific MG, and/or may perform PDCCH monitoring at the PDCCH monitoring period. . The BS expects that the UE will not perform measurement on the MG and/or perform PDCCH monitoring at the PDCCH monitoring time only if the PDCCH monitoring time according to the SS setting and/or CORESET setting with the above characteristics overlaps with the specific MG. You can assume and operate. This specific MG may be determined by the presence or absence of a certain parameter in the MG settings, or may be determined by the value of a certain parameter. For example, the size of the RRC parameter mgl or mgl-r16 value indicating the length of the MG section (i.e., MG length) is greater than or equal to a certain size, or the above specific MG can be determined.

Even if it is not a time window for receiving a random access response or contention resolution message in the random access process, the UE determines the PDCCH monitoring timing according to the search space (set) and/or CORESET that satisfies specific conditions according to Implementation 3 within the MG. It can be monitored.

<구현 4: 우선화를 가진 향상된 측정 설정(enhanced measurement configuration with prioritization)><Implementation 4: enhanced measurement configuration with prioritization>

The UE may receive one or more MGs from the BS. Each MG configuration determines the priority for type 1 scheduling, which is explicit scheduling (e.g., dynamic scheduling through L1 messages) for PUCCH/PUSCH/SRS transmission or PDSCH/CSI-RS reception of the BS, and implicit scheduling (e.g., It may have priority for the second type of scheduling, which is semi-static scheduling through L2 messages (e.g., RRC configuration) or PDCCH monitoring opportunity configuration through search space/CORESET configuration. For example, each MG setting may include priority information for first type scheduling and priority information for second type scheduling. MG settings that have a lower priority than each type of scheduling allow the corresponding type of scheduling on the MG section indicated by the MG setting, and the UE allows scheduling in the corresponding MG section if scheduling with a higher priority than the corresponding MG setting overlaps in time. The transmission or reception may be performed and measurement may not be performed on the MG section. That is, when two levels of priorities, lower priority and higher priority, can be used, the MG setting may not include a priority index, or may include a lower priority index or a higher priority index. For a certain scheduling type, an MG setting with a higher priority index does not allow all transmission/reception of that type, and an MG setting with a lower priority index allows a priority index/indicator higher than the upper priority index. It can be stipulated that only transmission/reception with is allowed. For example, DCI or SPS settings/CG settings are transmitted including a priority indicator/index, and MG settings are also transmitted including a priority index (hereinafter, first priority index) for DCI-based scheduling and SPS settings/CG settings. It may include a priority index (hereinafter referred to as a second priority index), and when a DCI is received, the UE sets the priority index within the DCI and the MG settings for the MG that overlaps the transmission/reception scheduled by the DCI. Compare the first priority index, and when the SPS setting / CG setting is received, compare the priority index in the SPS setting / CG setting with the second priority index to perform scheduled transmission or reception in the MG. You can decide whether to do it or not. Even if the UE performs the transmission or reception within the MG, measurements on the MG section can be performed under the following conditions:

> Downlink reception scheduled to be performed on the MG section, for example, in the case of PDCCH/PDSCH/CSI-RS reception; and/or

> When transmission/reception scheduled to be performed on the MG section does not overlap in time with the target (e.g., SSB) measured by the UE in the MG section.

The BS may expect/assume that the UE will perform measurements within the MG under the above conditions and perform corresponding BS operations.

<구현 5: 재전송을 스케줄링하는 DCI에 대해 MG를 무시/불능화(ignore/disable MG for DCI scheduling re-transmission)><Implementation 5: ignore/disable MG for DCI scheduling re-transmission>

When the UE performs PDSCH reception or PUSCH transmission, the UE can expect to receive a DCI (hereinafter referred to as retransmission scheduling DCI) scheduling retransmission for the reception/transmission from the BS for a certain period of time after the reception/transmission. there is. For example, the UE may expect to receive a retransmission scheduling DCI while the DRX retransmission timer for the corresponding HARQ process is running after performing PDSCH reception or PUSCH transmission. In some scenarios, where the DRX retransmission timer for DL starts when the DRX HARQ RTT timer for DL expires starting from the first symbol after the UE transmits a NACK for PDSCH reception, the DRX retransmission timer for UL is It starts when the DRX HARQ RTT timer for UL, which starts from the first symbol after the UE transmits the PUSCH, expires, and each DRX retransmission timer stops when the UE detects DL reception or UL transmission for the corresponding HARQ process. do. The value of the DRX HARQ RTT timer for DL, the value of the DRX retransmission timer for DL, the value of the HARQ RTT timer for UL, and the value of the DRX retransmission timer for UL can be provided by the BS to the UE through RRC signaling.

Alternatively, additional retransmission opportunities may be considered by considering the packet delay budget (PDB) of the transport block (TB) transmitted on the corresponding PDSCH/PUSCH. For example, if the general time required for retransmission is X ms, it can be determined whether additional retransmission is possible by considering the PDB of the corresponding transport block. If additional retransmission is possible, the UE responds with NACK due to failure of downlink reception of the corresponding transport block, or ignores MG settings in the upcoming PDCCH monitoring period to receive retransmission scheduling DCI from BS after performing PUSCH transmission. and attempt to receive PDCCH. Considering these cases, if the MG section and the PDCCH monitoring opportunity to receive the scheduling DCI overlap in time while expecting a retransmission scheduling DCI, the UE attempts to monitor the PDCCH and receive the PDCCH without performing measurements on the MG section. can do. In this case, not only the retransmission scheduling DCI but also other DCIs can be monitored within the MG section. In some implementations, this operation may be limited to PDSCH reception and/or PUSCH transmission with the following characteristics. That is, the UE may perform PDCCH monitoring in the PDCCH monitoring time(s) overlapping with the MG while waiting for the retransmission scheduling DCI for PDSCH reception and/or PUSCH transmission with the following characteristics, and the BS may perform the PDCCH monitoring time(s) ) can perform PDCCH transmission.

> PDSCH/PUSCH carrying a PDB with a PDB value less than a certain threshold (e.g., 10 ms) or a transport block with a remaining PDB value. Information about the PDB may be provided from the BS to the UE through an L2 signal, or may be provided from the UE to the BS in the case of uplink. For example, in the case of uplink, the UE can receive PDB information from the upper layer of its protocol stack and send the PDB information as a scheduling request (SR) or buffer status report (BSR). It can be provided to BS through. In the case of downlink, the BS can receive PDB information from the upper layer of its protocol stack and use DL allocation to share it with the UE. This PDB information may be based on each logical channel on the MAC layer. For example, in the case of uplink, when the BS sets up a PDB for each logical channel, or when the UE informs the BS of the logical channel or logical channel group of UL data that has become available for transmission (via BSR, etc.) When the PDB is provided together, or the UE informs the BS of the logical channel or logical channel group of UL data made available for transmission in the UE (through BSR, etc.), the BS transmits the UL data of the logical channel or logical channel group. An uplink grant for the UE may be provided to the UE together with the corresponding PDB. Alternatively, this PDB information may be based on a transport block generated at the MAC layer or may be based on a packet given at a higher layer (eg, RLC layer, PDCP layer, or application layer).

> DCI instructing HP PUSCH transmission or HP PDSCH reception. For example, Implementation 5 may be used for reception opportunities and/or transmission opportunities scheduled by a DCI or SPS/CG setting that includes a priority index with a value greater than a certain threshold (e.g., 0). The threshold value may be indicated through L1 signaling or higher layer signaling of the BS when the UE has three or more available priorities, and may be 0 when the UE has two available priorities.

> PDSCH/PUSCH received/transmitted via SPS/CG settings.

In some implementations, application of Implementation 5 may be limited to only downlink reception scheduling, or only uplink transmission scheduling. If Implementation 5 is limited to downlink reception scheduling, the UE may not apply Implementation 5 to transmitting a HARQ-ACK response to the PDSCH received in the downlink reception process on PUCCH/PUSCH. If Implementation 5 is limited to downlink transmission scheduling, the BS may not apply Implementation 5 to receiving the HARQ-ACK response to the PDSCH transmitted during the downlink transmission process on PUCCH/PUSCH.

In some implementations, whether implementation 5 behavior applies may differ between MG settings. For example, the UE may not perform measurements on the MG only when the retransmission scheduling DCI overlaps with a specific MG and/or may perform PDCCH monitoring at the PDCCH monitoring timing that overlaps the MG while expecting the retransmission scheduling DCI. The BS may perform PDCCH transmission at a PDCCH monitoring period that overlaps with the MG while the UE is waiting for the retransmission scheduling DCI. This specific MG may be determined by the presence or absence of a certain parameter in the MG settings, or may be determined by the value of a certain parameter. For example, the size of the RRC parameter mgl or mgl-r16 value indicating the length of the MG section (i.e., MG length) is greater than or equal to a certain size, or the above specific MG can be determined.

The implementations of the above-described specification may be applied individually or in combination of two or more.

According to some implementations of the present specification, a scheduling message or SPS/CG configuration that allows the UE to perform PDSCH/CSI-RS reception or PUCCH/PUSCH/SRS transmission within the MG is provided to the UE, or PDSCH/CSI- PDCCH for scheduling/triggering RS reception or PUCCH/PUSCH/SRS transmission may be provided to the UE within the MG. Through this, various resource allocations required for services with delay requirements can be provided to the UE even in the presence of MG settings. According to some implementations of this specification, according to some implementations of this specification, according to the MG settings, the UE can perform measurement and receive scheduling information or transmit/receive data/signals only for services that satisfy certain conditions. You can do it.

The UE may perform operations according to several implementations of this specification in relation to downlink signal reception. The UE has at least one transceiver; at least one processor; and at least one computer operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations in accordance with some implementations of the present specification. May contain memory. A processing device for a UE includes at least one processor; and at least one computer operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations in accordance with some implementations of the present specification. May contain memory. A computer-readable (non-volatile) storage medium may store at least one computer program that, when executed by at least one processor, includes instructions that cause the at least one processor to perform operations in accordance with some implementations of the present specification. You can. A computer program or computer program product is recorded on at least one computer-readable (non-volatile) storage medium and includes instructions that, when executed, cause (at least one processor) to perform operations in accordance with some implementations of the present specification. can do.

In the method of the UE, or in the UE, the processing device, the computer-readable (non-volatile) storage medium, and/or the computer program product, the operations include: receiving MG settings; And based on the overlap between the MG and the downlink reception period according to the MG setting: i) Based on that a specific condition is not met, measurement is performed within the MG and downlink is received at the downlink reception period within the MG. It may include omitting link reception, and ii) performing the downlink reception at the downlink transmission time within the MG based on the specific condition being met.

In some implementations, the specific conditions may include the following: The downlink reception timing is based on a specific semi-static scheduling (SPS) setting. PDSCH) period, and the specific SPS setting is an SPS setting with a priority index greater than the threshold value, or an SPS setting with a value that allows reception of the SPS PDSCH at the SPS PDSCH period when the SPS PDSCH period overlaps the MG. .

In some implementations, the specific condition may include the following: the downlink reception timing is a PDCCH based on a search space or CORESET setting including a specific RRC parameter) or a PDCCH based on a search space setting for a specific DCI format. It is monitoring time.

In some implementations, the MG configuration may include first priority information for scheduling by DCI carried by PDCCH and second priority information for scheduling by RRC. The specific condition may include the following: Based on the downlink reception time being scheduled by DCI format, the priority set by the first priority information in the MG setting is the priority of the downlink reception. is smaller, and based on the downlink reception time being scheduled by the RRC message, the priority set by the second priority information in the MG setting is smaller than the priority of the downlink reception.

In some implementations, the specific condition may include the following: the user device is waiting for a DCI scheduling retransmission for the received PDSCH or the transmitted PUSCH, and the downlink reception time is a physical downlink control channel monitoring time. am.

In some implementations, the specific condition may include the following: the transport block carried by the PDSCH or the PUSCH has a packet data budget less than a certain threshold, or by DCI format has a higher priority index value. Either scheduled or based on SPS settings or CG settings.

In some implementations, the specific condition may include the following: the downlink reception timing is in a DCI format with a higher priority index value, a DCI format indicating SPS activation, or a DCI format indicating the downlink reception. It is scheduled by.

The BS may perform operations according to several implementations of this specification with respect to downlink signal transmission. BS has at least one transceiver; at least one processor; and at least one computer operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations in accordance with some implementations of the present specification. May contain memory. The processing device for the BS includes at least one processor; and at least one computer operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations in accordance with some implementations of the present specification. May contain memory. A computer-readable (non-volatile) storage medium may store at least one computer program that, when executed by at least one processor, includes instructions that cause the at least one processor to perform operations in accordance with some implementations of the present specification. You can. A computer program or computer program product is recorded on at least one computer-readable (non-volatile) storage medium and includes instructions that, when executed, cause (at least one processor) to perform operations in accordance with some implementations of the present specification. can do.

In the method of the BS, or in the BS, the processing device, the computer-readable (non-volatile) storage medium, and/or the computer program product, the operations include: sending MG settings; And based on the overlap between MG and downlink transmission timing according to the MG setting: i) omitting downlink transmission at the downlink transmission timing within the MG based on a specific condition not being met, and ii) Based on the specific condition being met, it may include performing the downlink transmission at the downlink transmission time within the MG.

In some implementations, the specific condition may include the following: the downlink transmission timing is an SPS PDSCH timing based on a specific SPS setting, and the specific SPS setting is an SPS setting with a priority index greater than a threshold value, or This is an SPS setting with a value that allows SPS PDSCH transmission in the SPS PDSCH period when the SPS PDSCH period overlaps the MG.

In some implementations, the specific condition may include the following: PDCCH timing in which the downlink transmission timing is based on a search space or CORESET setting including a specific RRC parameter, or PDCCH monitoring based on a search space setting for a specific DCI format. It's time.

In some implementations, the specific condition may include the following: The MG configuration may include first priority information for scheduling by DCI carried by the PDCCH and second priority information for scheduling by RRC. You can. In some implementations, the specific condition may include the following: Based on the downlink transmission time being scheduled by DCI format, the priority set by the first priority information in the MG setting is the downlink It is smaller than the priority of link transmission, and based on the downlink transmission timing being scheduled by the RRC message, the priority set by the second priority information in the MG setting is smaller than the priority of the downlink transmission. .

In some implementations, the specific condition may include the following: the user device is waiting for a DCI scheduling retransmission for PDSCH or PUSCH and the downlink transmission time is the PDCCH monitoring time.

In some implementations, the specific condition may include the following: the downlink transmission timing is in a DCI format with a higher priority index value, a DCI format indicating SPS activation, or a DCI format indicating the downlink transmission. It is scheduled by.

The examples of the present specification disclosed as described above are provided to enable those skilled in the art to implement and practice the specification. Although the description has been made above with reference to examples of the present specification, those skilled in the art may modify and change the examples of the present specification in various ways. Accordingly, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Implementations of this specification can be used in a wireless communication system, BS or UE, or other equipment.

Claims

When a user device receives a downlink signal in a wireless communication system,

Receive measurement gap settings; and

Based on the overlap between the measurement gap and the downlink reception period according to the measurement gap setting:

i) Based on a specific condition not being met, performing measurement within the measurement gap and omitting downlink reception at the downlink reception time within the measurement gap, and

ii) Comprising performing the downlink reception at the downlink transmission time within the measurement gap, based on the specific condition being met,

How to receive downlink signals.
According to paragraph 1,

The above specific conditions include:

The downlink reception time is an SPS physical downlink shared channel (PDSCH) time based on a specific semi-static scheduling (SPS) setting,

The specific SPS setting is an SPS setting with a priority index greater than a threshold value, or an SPS setting with a value that allows SPS PDSCH reception in the SPS PDSCH period when the SPS PDSCH period overlaps the measurement gap.

How to receive downlink signals.
According to paragraph 1,

The above specific conditions include:

The downlink reception time is a physical downlink control channel (PDCCH) based on a search space or control resource set (CORESET) setting including a specific radio resource control (RRC) parameter. Timing or PDCCH monitoring timing based on search space settings for a specific downlink control information format,

How to receive downlink signals.
According to paragraph 1,

The measurement gap setting is based on first priority information for scheduling by downlink control information carried by a physical downlink control channel (PDCCH) and scheduling by radio resource control (RRC). Contains second priority information about,

The above specific conditions include:

Based on the downlink reception time being scheduled by the downlink control information format, the priority set by the first priority information in the measurement gap setting is lower than the priority of the downlink reception,

Based on the downlink reception time being scheduled by the RRC message, the priority set by the second priority information in the measurement gap setting is smaller than the priority of the downlink reception,

How to receive downlink signals.
According to paragraph 1,

The above specific conditions include:

The user device is waiting for downlink control information scheduling retransmission for the received physical downlink shared channel (PDSCH) or the transmitted physical uplink shared channel (PUSCH) and the downlink The link reception time is the physical downlink control channel monitoring time,

How to receive downlink signals.
According to clause 5,

The above specific conditions further include:

The transport block carried by the PDSCH or the PUSCH has a packet data budget smaller than a certain threshold, is scheduled by a downlink control information format with a higher priority index value, or has semi-persistent scheduling or a set grant. Based on settings,

How to receive downlink signals.
According to paragraph 1,

The above specific conditions include:

The downlink reception time is scheduled by a downlink control information format with a higher priority index value, a downlink control information format indicating activation of quasi-persistent scheduling, or a downlink control information format indicating the downlink reception. person,

How to receive downlink signals.
When a user device receives a downlink signal in a wireless communication system,

at least one transceiver;

at least one processor; and

At least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising:

Receive measurement gap settings; and

Based on the overlap between the measurement gap and the downlink reception period according to the measurement gap setting:

i) Based on a specific condition not being met, performing measurement within the measurement gap and omitting downlink reception at the downlink reception time within the measurement gap, and

ii) Comprising performing the downlink reception at the downlink transmission time within the measurement gap, based on the specific condition being met,

User device.
In a processing device in a wireless communication system,

at least one processor; and

At least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising:

Receive measurement gap settings; and

Based on the overlap between the measurement gap according to the measurement gap setting and the downlink reception time:

i) Based on a specific condition not being met, performing measurement within the measurement gap and omitting downlink reception at the downlink reception time within the measurement gap, and

ii) Comprising performing the downlink reception at the downlink transmission time within the measurement gap, based on the specific condition being met,

processing device.
In a computer-readable storage medium,

The storage medium stores at least one program code containing instructions that, when executed, cause at least one processor to perform operations, the operations comprising:

Receive measurement gap settings; and

Based on the overlap between the measurement gap and the downlink reception period according to the measurement gap setting:

i) Based on a specific condition not being met, performing measurement within the measurement gap and omitting downlink reception at the downlink reception time within the measurement gap, and

ii) Comprising performing the downlink reception at the downlink reception time within the measurement gap, based on the specific condition being met,

storage media.
When a base station transmits a downlink signal to a user device in a wireless communication system,

Transfer measurement gap settings; and

Based on the overlap between the measurement gap and downlink transmission timing according to the measurement gap setting:

i) Omitting downlink transmission at the downlink transmission time within the measurement gap based on a specific condition not being met, and

ii) Comprising performing the downlink transmission at the downlink transmission timing within the measurement gap, based on the specific condition being met,

Downlink signal transmission method.
When a base station transmits a downlink signal to a user device in a wireless communication system,

at least one transceiver;

at least one processor; and

At least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising:

Transfer measurement gap settings; and

Based on the overlap between the measurement gap and downlink transmission timing according to the measurement gap setting:

i) Omitting downlink transmission at the downlink transmission time within the measurement gap based on a specific condition not being met, and

ii) Comprising performing the downlink transmission at the downlink transmission timing within the measurement gap, based on the specific condition being met,

Base station.
According to clause 12,

The above specific conditions include:

The downlink transmission time is an SPS physical downlink shared channel (PDSCH) time based on a specific semi-static scheduling (SPS) setting,

The specific SPS setting is an SPS setting with a priority index greater than a threshold value, or an SPS setting with a value that allows SPS PDSCH transmission in the SPS PDSCH period when the SPS PDSCH period overlaps the measurement gap.

Base station.
According to clause 12,

The above specific conditions include:

The downlink transmission timing is a physical downlink control channel (PDCCH) based on a search space or control resource set (CORESET) configuration including a specific radio resource control (RRC) parameter. Timing or PDCCH monitoring timing based on search space settings for a specific downlink control information format,

Base station.
According to clause 12,

The measurement gap setting is based on first priority information for scheduling by downlink control information carried by a physical downlink control channel (PDCCH) and scheduling by radio resource control (RRC). Contains second priority information about,

The above specific conditions include:

Based on the downlink transmission timing being scheduled by the downlink control information format, the priority set by the first priority information in the measurement gap setting is lower than the priority of the downlink transmission,

Based on the downlink transmission timing being scheduled by the RRC message, the priority set by the second priority information in the measurement gap setting is smaller than the priority of the downlink transmission,

Base station.
According to clause 12,

The above specific conditions include:

The user device is waiting for downlink control information scheduling retransmission for a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH), and the downlink transmission timing is When monitoring the physical downlink control channel,

Base station.
According to clause 16,

The above specific conditions further include:

The transport block carried by the PDSCH or the PUSCH has a packet data budget smaller than a certain threshold, is scheduled by a downlink control information format with a higher priority index value, or has semi-persistent scheduling or a set grant. Based on settings,

Base station.
According to clause 12,

The above specific conditions include:

The downlink transmission timing is scheduled by a downlink control information format with a higher priority index value, a downlink control information format indicating activation of quasi-persistent scheduling, or a downlink control information format indicating the downlink transmission. person,

Base station.