Method by device, device, storage medium, method by base station, and base station

Abstract

A UE may comprise: receiving a measurement gap-related configuration, wherein the measurement gap-related configuration comprises information about a periodicity and an offset and information about a measurement gap time length; determining measurement gaps on the basis of the measurement gap-related configuration; performing neighbor cell measurement during the measurement gaps, during which predetermined operations are not allowed; and performing channel state information (CSI) measurement among the predetermined operations during a measurement gap cancelled on the basis of reception of measurement gap cancellation information.

Description

Method by device, device and storage medium, and method by base station, and base station

[0001] This specification relates to wireless communication systems.

[0002] Various devices and technologies, such as machine-to-machine (M2M) communication, machine-type communication (MTC), and smartphones and tablet PCs (personal computers) that require high data transmission rates, are emerging and becoming widespread. Consequently, the amount of data required to be processed on cellular networks is rapidly increasing. To meet this rapidly increasing data processing demand, technologies such as carrier aggregation and cognitive radio are being developed to efficiently utilize more frequency bands, while multi-antenna technology and multi-BS cooperation technology are being developed to increase the data capacity transmitted within a limited frequency range.

[0003] As more and more communication devices demand greater capacity, the need for enhanced mobile broadband (eMBB) communications is emerging, surpassing legacy radio access technology (RAT). Furthermore, massive machine type communication (mMTC), which connects multiple devices and objects to provide diverse services anytime, anywhere, is a key issue to be considered in next-generation communications.

[0004] Additionally, discussions are underway on communication systems designed to accommodate reliability- and latency-sensitive services and user equipment (UE). The introduction of next-generation wireless access technologies is being discussed, including enhanced mobile broadband (eMBB), mMTC, and ultra-reliable and low latency communication (URLLC).

[0005] There is a need for a method that can efficiently process data packets with strict latency requirements and / or schedule the data packets even during the measurement gap period.

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

[0007] In one aspect of the present disclosure, a method performed by a device is provided. In another aspect of the present disclosure, a device is provided, comprising: at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In another aspect of the present disclosure, a computer-readable, non-transitory storage medium is provided, storing at least one program code comprising instructions that, when executed, cause the at least one processor to perform operations. The method or the operations include: receiving a radio resource configuration message including a measurement gap-related setting, the measurement gap-related setting including information about a period and an offset and information about a measurement gap time length; determining measurement gaps for neighboring cell measurements based on the measurement gap-related setting; performing the neighboring cell measurements during the measurement gaps, wherein predetermined operations are not allowed during the measurement gaps; The method may include omitting neighboring cell measurements during a cancelled measurement gap based on the reception of measurement gap cancellation information. During the cancelled measurement gap, second predetermined operations, excluding first predetermined operations among the predetermined operations, may be allowed. The first predetermined operations may include channel state information (CSI) measurements.

[0008] In each aspect of this specification, the CSI measurement may be allowed based on the measurement gap cancellation information being received via downlink control information.

[0009] In each aspect of the present specification, the method or the operations may include: determining that a CSI reference resource within the cancelled measurement gap is valid based on the measurement gap cancellation information being received via the downlink control information.

[0010] In each aspect of the present specification, the method or the operations may include: determining that the CSI reference resource within the cancelled measurement gap is invalid based on the measurement gap cancellation information being received via a radio resource control signal.

[0011] In each aspect of this specification, the predetermined operations may include at least: transmitting a hybrid automatic repeat request (HARQ) feedback, a scheduling request (SR), or channel state information (CSI); reporting a sounding reference signal (SRS); transmitting on an uplink shared channel; monitoring a physical downlink control channel; or receiving on a downlink shared channel.

[0012] In another aspect of the present disclosure, a method performed by a base station is provided. In another aspect of the present disclosure, a base station is provided, comprising: at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In another aspect of the present disclosure, a computer-readable, non-transitory storage medium is provided, storing at least one program code comprising instructions that, when executed, cause the at least one processor to perform operations. The method or the operations may include: transmitting a radio resource control message including a measurement gap-related setting, the measurement gap-related setting including information about a periodicity and an offset and information about a measurement gap time length; and receiving a report related to the measurement gap-related setting. The measurement report may be based on neighboring cell measurements performed during measurement gaps determined based on the measurement gap-related setting. The above measurement report may not include measurement information related to a measurement gap that has been canceled by measurement gap cancellation information. During the canceled measurement gap, second predetermined operations, excluding the first predetermined operations among the predetermined operations, may be permitted. The first predetermined operations may include channel state information (CSI) measurements.

[0013] In each aspect of this specification, the CSI measurement may be permitted to the device based on the measurement gap cancellation information being transmitted via downlink control information.

[0014] In each aspect of the present specification, the method or the operations may include: determining that a CSI reference resource within the cancelled measurement gap is valid based on the measurement gap cancellation information being transmitted via the downlink control information.

[0015] In each aspect of the present specification, the method or the operations may include: determining that the CSI reference resource within the cancelled measurement gap is invalid based on the measurement gap cancellation information being transmitted via a radio resource control signal.

[0016] In each aspect of the present specification, the predetermined operations may include at least: receiving a hybrid automatic repeat request (HARQ) feedback, a scheduling request (SR), or channel state information (CSI); receiving a sounding reference signal (SRS) report; receiving on an uplink shared channel; transmitting on a physical downlink control channel; or transmitting on a downlink shared channel.

[0017] 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 a person having ordinary knowledge in the relevant technical field based on the detailed description below.

[0018] According to some implementations of this specification, data packets with strict latency requirements and / or scheduling of said data packets can be efficiently processed even during measurement gap periods.

[0019] Some implementations of this specification can ensure constant resource availability and quality of service that is sensitive to latency.

[0020] According to some implementations of this specification, scheduling restrictions for measurement gap intervals can be minimized.

[0021] According to some implementations of this specification, delay / latency occurring during wireless communication between communicating devices can be reduced.

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

[0023] To aid in understanding implementations of this specification, the accompanying drawings, which are included as part of the detailed description, provide examples of implementations of this specification and, together with the detailed description, illustrate implementations of this specification:

[0024] Figure 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied;

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

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

[0027] Figure 4 is the 3rd generation partnership project (3 rd It illustrates an example of a frame structure available in a wireless communication system based on the 3rd Generation Partnership Project (3GPP);

[0028] Figure 5 illustrates a resource grid of slots;

[0029] FIG. 6 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH;

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

[0031] Figure 8 illustrates discontinuous reception (DRX) operation;

[0032] Figure 9 illustrates a flow of UE operations to which some implementations of this specification may be applied;

[0033] Figure 10 illustrates a flow of BS operations to which some implementations of the present specification may be applied;

[0034] FIGS. 11 to 13 illustrate some implementations of this specification for handling channel state information (CSI) reference resources when a CSI reference resource and a measurement gap (MG) overlap;

[0035] FIG. 14 illustrates an MG-related operation flow of a UE according to some implementations of this specification;

[0036] Figure 15 illustrates the MG-related operation flow of the BS according to some implementations of this specification.

[0037] Hereinafter, implementations according to this specification will be described in detail with reference to the attached drawings. The detailed description provided below, together with the attached drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only possible implementations of this specification. The detailed description below includes specific details to provide a thorough understanding of this specification. However, one of ordinary skill in the art will appreciate that this specification may be practiced without these specific details.

[0038] In some cases, to avoid ambiguity in the concepts of this specification, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device. Furthermore, identical components are described using the same drawing reference numerals throughout this specification.

[0039] 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, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented in wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented in wireless technologies such as Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE) (i.e., GERAN). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved-UTRA). UTRA is part of UMTS (Universal Mobile Telecommunication System), and 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS that uses E-UTRA.3GPP LTE adopts OFDMA for the downlink (DL) and SC-FDMA for the uplink (UL). LTE-A (LTE-advanced) is an evolved form of 3GPP LTE.

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

[0041] For terms and technologies used in this specification that are not specifically explained, reference may be made 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.

[0042] In the examples of this specification described below, the expression "assumes" that a device "assumes" that the entity transmitting the channel transmits the channel in a manner consistent with the "assume." The entity receiving the channel may mean that, under the assumption that the channel was transmitted in a manner consistent with the "assume," the entity receiving the channel receives or decodes the channel in a manner consistent with the "assume."

[0043] In this specification, ' / ' can mean 'and / or'.

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

[0045] In this specification, a node refers to a fixed point that can transmit / receive radio signals by communicating with a UE. Various types of BSs can be used as nodes regardless of their names. For example, BSs, NBs, eNBs, pico-cell eNBs (PeNBs), home eNBs (HeNBs), relays, and repeaters can be nodes. Furthermore, a node may not be a BS. For example, it can be a radio remote head (RRH) or a radio remote unit (RRU). RRHs, RRUs, etc. generally have a lower power level than the BS. Since an RRH or RRU (hereinafter referred to as RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between an RRH / RRU and a BS can be performed more smoothly than cooperative communication between BSs that are generally connected via a wireless line. Each node is equipped with at least one antenna. The antenna may be a physical antenna, an antenna port, a virtual antenna, or an antenna group. A node is also called a point.

[0046] 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. In addition, 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 a UE is specifically referred to as a serving cell. In addition, the channel state / quality of a specific cell refers to the channel state / quality of a channel or communication link formed between a BS or node that provides communication services to the specific cell and the UE. In a 3GPP-based communication system, a UE can measure a downlink channel state from a specific node using CRS (Cell-specific Reference Signal) resources transmitted by antenna port(s) of the specific node on CRS resources allocated to the specific node and / or CSI-RS (Channel State Information Reference Signal) resources transmitted.

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

[0048] A "cell" in a geographical area can be understood as the coverage over which a node can provide a service using a carrier, and a "cell" in a radio resource is associated with a bandwidth (BW), which is a frequency range configured by the carrier. Since downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a node can receive a valid signal from a UE, depend on the carrier carrying the signal, the coverage of a node is also associated with the coverage of the "cell" of the radio resource used by the node. Therefore, the term "cell" can sometimes be used to mean the coverage of a service by a node, sometimes a radio resource, and sometimes the range over which a signal using the radio resource can reach with a valid intensity.

[0049] Meanwhile, the 3GPP communication standard uses the concept of a cell to manage radio resources. A "cell" associated with radio resources is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), i.e., a combination of a DL component carrier (CC) and an UL CC. A cell can be configured with DL resources alone or a combination of DL resources and UL resources. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. For example, the combination of DL resources and UL resources can be indicated by a System Information Block Type 2 (SIB2) linkage. Here, the carrier frequency can be the same as or different from the center frequency of each cell or CC. When carrier aggregation (CA) is established, the UE has only one radio resource control (RRC) connection with the network. One serving cell provides non-access stratum (NAS) mobility information during RRC connection establishment / re-establishment / handover, and one serving cell provides security input during RRC connection re-establishment / handover. Such a cell is called a primary cell (Pcell). A Pcell is a cell operating on the primary frequency where the UE performs initial connection establishment procedures or initiates connection re-establishment procedures.Depending on the UE capability, secondary cells (Scells) can be configured to form a set of serving cells together with Pcells. An Scell ​​can be configured after an RRC (Radio Resource Control) connection establishment has been made, and is a cell that provides additional radio resources in addition to the resources of a special cell (SpCell). The carrier corresponding to a Pcell in downlink is called a downlink primary CC (DL PCC), and the carrier corresponding to a Pcell in uplink is called an UL primary CC (UL PCC). The carrier corresponding to an Scell ​​in downlink is called a DL secondary CC (DL SCC), and the carrier corresponding to the Scell ​​in uplink is called an UL secondary CC (UL SCC).

[0050] For dual connectivity (DC) operation, the term special cell (SpCell) refers to a Pcell of a master cell group (MCG) or a primary secondary cell (PSCell) of a secondary cell group (SCG). A SpCell supports PUCCH transmission and contention-based random access and is always activated. An MCG is a group of serving cells associated with a master node (e.g., BS) and consists of a SpCell (Pcell) and optionally one or more Scells. For a UE configured for DC, an 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. A PSCell is a primary Scell ​​of an SCG. For a UE in RRC_CONNECTED state that is not configured for CA or DC, there is only one serving cell consisting of Pcells. For a UE in RRC_CONNECTED state that is configured for CA or DC, the term serving cells refers to the set of cells consisting of SpCell(s) and all Scell(s). In DC, two medium access control (MAC) entities are configured in the UE: one for the MCG and one for the SCG.

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

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

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

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

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

[0056] Since the communication device receives a synchronization signal block (SSB), DMRS, CSI-RS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on a cell, it cannot selectively receive through an RF receiver only radio signals including only a specific physical channel or only a specific physical signal, or selectively receive through an RF receiver only radio signals excluding only a specific physical channel or only a physical signal. In actual operation, the communication device first receives radio signals on a cell through an RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and decodes a physical signal and / or a physical channel within the baseband signals using one or more processors. Thus, in some implementations of the present specification, not receiving a physical signal and / or a physical channel may not actually mean that the communication device does not receive wireless signals containing the physical signal and / or physical channel at all, but rather that it does not attempt to recover the physical signal and / or physical channel from the wireless signals, e.g., does not attempt to decode the physical signal and / or the physical channel.

[0057] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, massive MTC, which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / UEs is being discussed. The introduction of next-generation RATs that take advanced mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) into account is currently under discussion. 3GPP is currently conducting studies on next-generation mobile communication systems beyond EPC. For convenience, this technology is referred to as new RAT (NR) or 5G RAT, and a system that uses or supports NR is referred to as an NR system.

[0058] FIG. 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied. Referring to FIG. 1, the communication system (1) applied to the present specification includes a wireless device, a BS, and a network. Here, the wireless device refers to a device that performs communication using a 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, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. Mobile devices may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. Home appliances may include a TV, a refrigerator, a washing machine, etc. IoT devices may include sensors, smart meters, etc. For example, a BS or network may also be implemented as a wireless device, and a specific wireless device may act as a BS / network node to other wireless devices.

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

[0060] Wireless communication / connection (150a, 150b) can be performed between wireless devices (100a~100f) / BS (200) - BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection can be performed through various wireless access technologies (e.g., 5G NR) for uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication). Through the wireless communication / connection (150a, 150b), the wireless device and the BS / wireless device can transmit / receive wireless signals to / from each other. To this end, at least some of 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.), and resource allocation processes can be performed based on various proposals of this specification.

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

[0062] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (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 / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). In addition, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals 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, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0063] 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). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the functions, procedures, and / or methods described / suggested below. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals 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, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

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

[0065] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification, and provide the signals 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 obtain PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification.

[0066] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, 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) and executed by one or more processors (102, 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.

[0067] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0068] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or 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., as described in the functions, procedures, proposals, methods and / or flowcharts of this specification, from one or more other devices. For example, one or more transceivers (106, 206) may be coupled to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, or the like, as referred to in the functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this specification, via one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals for processing using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0069] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification. Referring to FIG. 3, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 2 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation 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) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

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

[0071] In FIG. 3, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed 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, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, transitory memory, non-transitory memory, and / or a combination thereof.

[0072] In this specification, at least one memory (e.g., 104 or 204) can store instructions or programs that, when executed, cause at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0073] In this specification, a computer-readable (non-transitory) storage medium can store at least one instruction or computer program, which when executed by at least one processor causes the at least one processor to perform operations according to some embodiments or implementations of this specification.

[0074] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory operatively connected to the at least one processor. The at least one computer memory may store instructions or programs, which, when executed, cause at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

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

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

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

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

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

[0080]

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

[0082]

[0083] For a subcarrier spacing setting u, slots are n in increasing order within a subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - Numbered as 1}.

[0084] Figure 5 illustrates the resource grid of a slot. A slot contains multiple symbols (e.g., 14 or 12) in the time domain. For each numeral (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N is indicated by higher layer signaling (e.g., radio resource control (RRC) signaling). start,u grid Starting from,N size,u grid,x *N RB sc Dog subcarriers and N subframe,u symb A resource grid of OFDM symbols is defined, where N size,u grid,x is the number of resource blocks (RBs) 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 3GPP-based wireless communication systems, N RB scis typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid is given to the UE by higher layer parameters (e.g., RRC parameters) from the network. Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE 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 an NR system, an 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 configuration u. The center of subcarrier 0 of CRB 0 for the subcarrier spacing configuration u coincides with 'Point A', which is a common reference point for the resource block grids. PRBs for subcarrier spacing u are defined within the bandwidth part (BWP) and range from 0 to N. size,u BWP,i -1, where i is the number of the bandwidth part. Common resource block n u CRB and bandwidth part i within physical resource block n PRB The relationship between the two is as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,iis a common resource block (BRB) whose bandwidth part starts relative to CRB 0. A BWP comprises multiple consecutive RBs in the frequency domain. For example, a BWP may be a given numeral u within a BWP i on a given carrier. i A subset of contiguous CRBs defined for a carrier. A carrier may include up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the activated BWPs, and only a predetermined number (e.g., 1) of BWPs configured for the UE may be activated on the carrier.

[0085] For each serving cell in a set of DL BWPs or UL BWPs, the network configures at least an initial DL BWP and one (if the serving configuration is configured with uplink) or two (if supplementary uplink is used) initial UL BWPs. The network may also 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, and iii) N start BWP = Offset RB with the assumption of 275 set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates the resource indicator value (RIV). start BWP =O carrier +RB start and the number of contiguous RBs N size BWP =L RB , and the subcarrier spacing is provided by the RRC parameter offsetToCarrierO carrier; an index within the set of DL BWPs or UL BWPs; a set of BWP-common parameters and a set of BWP-specific parameters.

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

[0087] A UE configured with carrier aggregation may be configured to use one or more cells. If the UE is configured to have multiple serving cells, the UE may be configured to have one or more cell groups. The 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 configured with PUCCH resources. The PUCCH cell may be a Pcell or an 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 cell groups of the UE and does not belong to multiple cell groups.

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

[0089]

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

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

[0092] When a PDCCH on one serving cell schedules a PDSCH or PUSCH on another serving cell, this is called cross-carrier scheduling. Cross-carrier scheduling using the carrier indicator field (CIF) can allow the PDCCH of a serving cell to schedule resources on another serving cell. On the other hand, when a PDSCH on a serving cell schedules a PDSCH or PUSCH on the serving cell, this is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the BS can provide the UE with information about the cell that schedules the cell. For example, the BS can provide the UE with information about whether the serving cell is scheduled by a PDCCH on another (scheduling) cell or by the serving cell, and if the serving cell is scheduled by another (scheduling) cell, which cell signals downlink assignments and uplink grants for the serving cell. In this specification, a cell that carries a PDCCH is called a scheduling cell, and a cell in which transmission of a PUSCH or PDSCH is scheduled by DCI included in the PDCCH, i.e., a cell that carries a PUSCH or PDSCH scheduled by the PDCCH, is called a scheduled cell.

[0093] The PDSCH is a physical layer UL channel for UL data transport. PDSCH carries downlink data (e.g., DL-SCH transport blocks) and employs modulation methods such as Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM. Transport blocks (TBs) are encoded to generate codewords. PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to radio resources along with the DMRS, generating an OFDM symbol signal and transmitting it through the corresponding antenna port.

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

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

[0096] - Hybrid automatic repeat request (HARQ)-acknowledgement (ACK): This is a response to a downlink data packet (e.g., a codeword) on the PDSCH. It indicates whether the downlink data packet was successfully received by the communication device. One HARQ-ACK bit may be transmitted in response to a single codeword, and two HARQ-ACK bits may be transmitted in response to two codewords. HARQ-ACK responses include 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.

[0097] - Channel state information (CSI): This is feedback information for the downlink channel. CSI may include channel quality information (CQI), a rank indicator (RI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH resource block indicator (SSBRI), a layer indicator (LI), etc. CSI may be divided into CSI Part 1 and CSI Part 2 according to the UCI type included in the CSI. For example, CQI for the CRI, RI, and / or the first codeword may be included in CSI Part 1, and CQI for the LI, PMI, and the second codeword may be included in CSI Part 2.

[0098] - Link recovery request (LRR)

[0099] In this specification, for convenience, the PUCCH resources set and / or instructed 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.

[0100] PUCCH formats can be categorized as follows based on the UCI payload size and / or transmission length (e.g., the number of symbols constituting the PUCCH resource). For more information on PUCCH formats, please refer to Table 4.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0119] - Transmission structure: DMRS and UCI are configured / 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 for the same time-frequency resources (e.g., the same PRB).

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

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

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

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

[0124] - Transmission Structure: DMRS and UCI are configured / 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 by TDM (Time Division Multiplexing) with DMRS.

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

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

[0127]

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

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

[0130] - PUCCH resource set #1, if 2< UCI bits =< N1

[0131] ...

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

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

[0134] The configuration for each PUCCH resource includes a PUCCH resource index, an index of a starting PRB, and a configuration for one of PUCCH formats 0 to 4. The UE is configured by the BS via a higher layer parameter maxCodeRate to multiplex HARQ-ACK, SR, and CSI report(s) within a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4. The higher layer parameter maxCodeRate is used to determine how to feed back UCI on the PUCCH resource for PUCCH format 2, 3, or 4.

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

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

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

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

[0139] In DL, the BS can dynamically allocate downlink resources to the UE via PDCCH(s) addressed with the C-RNTI. The UE monitors the PDCCH(s) to discover possible downlink assignments. Additionally, the BS can allocate downlink resources to the UE using semi-static scheduling (SPS). The BS can set the period of the configured downlink assignments via RRC signaling, and signal and activate or deactivate the configured downlink assignments via the PDCCH addressed with the CS-RNTI. For example, a PDCCH addressed with the CS-RNTI implicitly indicates that the corresponding downlink assignment can be reused according to the period set by the RRC signaling until it is deactivated.

[0140] Below, resource allocation by PDCCH and resource allocation by RRC are explained in more detail.

[0141] * Resource allocation by PDCCH: Dynamic grant / assignment

[0142] The PDCCH can be used to schedule DL transmission on the PDSCH or UL transmission on the PUSCH. The DCI on the PDCCH that schedules DL transmission includes the modulation and coding format (e.g., modulation and coding scheme (MCS) index) associated with the DL-SCH. MCS), may include DL resource allocation including at least resource allocation and HARQ information. The DCI on the PDCCH for 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. The HARQ information for the DL-SCH or for the UL-SCH may include a new data indicator (NDI), a transport block size (TBS), a redundancy version (RV), and a HARQ process ID (i.e., a HARQ process number). The size and purpose of the 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 the PUSCH, and DCI format 1_0, DCI format 1_1, or DCI format 1_2 may be used for scheduling the PDSCH. In particular, DCI format 0_2 and DCI format 1_2 can be used to schedule transmissions with higher transmission reliability and lower latency requirements than those guaranteed by DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. Some implementations of this specification can be applied to UL data transmission based on DCI format 0_2. Some implementations of this specification can be applied to DL data reception based on DCI format 1_2.

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

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

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

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

[0147] * Resource allocation by RRC

[0148] As mentioned above, for uplink, there are two types of transmissions without dynamic grants: configured grant type 1 and configured grant type 2. For configured grant type 1, the UL grant is provided by RRC signaling and stored as a configured grant. For configured grant type 2, the UL grant is provided by PDCCH and 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 configured by RRC signaling on a per-serving cell and per-BWP basis. Multiple configurations can be activated simultaneously on different serving cells.

[0149] When Grant Type 1 is configured, the UE can receive the following parameters from the BS via RRC signaling:

[0150] - cs-RNTI, CS-RNTI for retransmission;

[0151] - Periodicity of the set grant type 1;

[0152] - timeReferenceSFN, which indicates the system frame number (SFN) used to determine the offset of the resource in the time domain;

[0153] -timeDomainOffset, which is the offset relative to the reference SFN pointed to by -timeReferenceSFN;

[0154] - A timeDomainAllocation value m, which provides a row index m+1 pointing to an allocation table, representing a combination of a start symbol S, a length L, and a PUSCH mapping type;

[0155] - frequencyDomainAllocation, which provides frequency domain resource allocation; and

[0156] - I indicating the modulation order, target code rate, and transport block size MCS mcsAndTBS provides.

[0157] When configuring a 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 initializes or re-initializes the configured uplink grant to start at a symbol according to timeDomainOffset and S (derived from SLIV) and to recur with periodicity. After an uplink grant is configured for Grant Type 1, the UE may consider that the uplink grant is recurring associated with each symbol satisfying: [(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 represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Tables 1 and 2).

[0158] When Grant Type 2 is configured, the UE can receive the following parameters from the BS via RRC signaling:

[0159] - cs-RNTI, which is a CS-RNTI for activation, deactivation, and retransmission; and

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

[0161] The actual uplink grant is provided to the UE by the PDCCH (addressed by the CS-RNTI). After the uplink grant is configured for Grant Type 2, the UE may consider the uplink grant to be recurring in association with each symbol satisfying: [(SFN *numberOfSlotsPerFrame*numberOfSymbolsPerSlot) + (slot number in the frame *numberOfSymbolsPerSlot) + symbol number in the slot] = [(SFN start time *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+ slotstart time*numberOfSymbolsPerSlot+ symbolstart time) + N *periodicity] modulo (1024 *numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N >= 0, where SFN start time , slotstart time, and symbolstart time represent the SFN, slot, and symbol of the first transmission opportunity of the PUSCH after the above-configured grant is (re-)initialized, respectively, and numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Tables 1 and 2).

[0162] ConfiguredGrantConfig, an RRC setting used to configure a configured grant type 1 or type 2, may include a parameter configuredGrantTimer that indicates the initial value of a grant timer set to a multiple of the periodicity.

[0163] In some scenarios, the parameters harq-ProcID-Offset and / or harq-ProcID-Offset2 may be further provided by the BS to the UE to derive HARQ process IDs for the configured uplink grants. harq-ProcID-Offset is the offset of the HARQ process for the configured grant for operation with shared spectrum channel access, and harq-ProcID-Offset2 is the offset of the HARQ process for the configured grant. In this specification, cg-RetransmissionTimer is a duration during which the UE should not autonoumously perform a retransmission using the HARQ process of the (re)transmission after a (re)transmission based on a configured grant, and is a parameter that can be provided to the UE by the BS when a retransmission on the configured uplink grant is configured. For configured grants for which 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)] modulonrofHARQ-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)] modulonrofHARQ-Processes+harq-ProcID-Offset2, where CURRENT_symbol = (SFN *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+ slot number in the frame *numberOfSymbolsPerSlot+ symbol number in the slot), where numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively. For configured UL grants with cg-RetransmissionTimer, the UE may arbitrarily select a HARQ process ID from among the available HARQ process IDs for the configured grant.

[0164] For downlink, the UE can be configured with semi-persistent scheduling (SPS) on a per-serving cell and per-BWP basis via RRC signaling from the BS. For DL ​​SPS, DL assignments are provided to the UE via PDCCH and stored or removed based on L1 signaling indicating SPS activation or deactivation. When SPS is configured, the UE can receive the following parameters from the BS via RRC signaling (e.g., SPS configuration) used to configure semi-persistent transmission:

[0165] - cs-RNTI, CS-RNTI for activation, deactivation, and retransmission;

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

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

[0168] - n1PUCCH-AN providing HARQ resources for PUCCH for SPS (the network configures the HARQ resources as format 0 or format 1, and the actual PUCCH-resources are configured in PUCCH-Config and referred to in n1PUCCH-AN by their ID).

[0169] Multiple downlink SPS configurations can be configured within the BWP of a serving cell. After a downlink assignment is configured for SPS, the UE can sequentially consider the Nth downlink assignment to occur in a slot satisfying: (numberOfSlotsPerFrame*SFN + slot number in the frame) = [(numberOfSlotsPerFrame*SFN start time + slotstart time) + N *periodicity*numberOfSlotsPerFrame / 10] modulo(1024 *numberOfSlotsPerFrame), where SFN start time and slotstart time represent the SFN, slot, and symbol of the first transmission of the PDSCH after the configured downlink allocation is (re-)initialized, respectively, and 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).

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

[0171] If the cyclic redundancy check (CRC) of the corresponding DCI format is scrambled with the CS-RNTI provided by the RRC parameter cs-RNTI and the new data indicator field for the enabled transport block is set to 0, the UE validates the DL SPS assignment PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or descheduling. Validation 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 validation, and Table 6 illustrates special fields for DL ​​SPS and UL grant type 2 scheduling release PDCCH validation.

[0172]

[0173]

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

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

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

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

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

[0179] - Frequency domain resource assignment (FDRA): Indicates the set of RBs allocated to the PDSCH.

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

[0181] - PDSCH-to-HARQ_Feedback Timing Indicator: Indicates K1.

[0182] When the PDSCH is configured to transmit at most 1 TB, the HARQ-ACK response may consist of 1 bit. When the PDSCH is configured to transmit at most 2 transport blocks (TB), the HARQ-ACK response may consist of 2 bits when spatial bundling is not configured, and may consist of 1 bit when spatial bundling is configured. When the HARQ-ACK transmission time for multiple PDSCHs is designated as slot n+K1, the UCI transmitted in slot n+K1 includes HARQ-ACK responses for multiple PDSCHs.

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

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

[0185] Meanwhile, in the case of a dynamic HARQ-ACK codebook, the HARQ-ACK payload size to be reported by the UE can be dynamically changed by DCI, etc. The dynamic HARQ-ACK codebook is also referred to as a Type-2 HARQ-ACK codebook. The Type-2 HARQ-ACK codebook can be considered a more optimized HARQ-ACK feedback because the UE sends feedback only for the scheduled serving cells. However, in bad channel conditions, the UE may misunderstand the number of scheduled serving cells, and to address this, the DAI is included as part of the DCI. For example, in the dynamic HARQ-ACK codebook scheme, the DL scheduling DCI may include a counter-DAI (i.e., c-DAI) and / or a total-DAI (i.e., t-DAI). Here, the DAI stands for a 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 indicating the order among PDCCHs carrying DL scheduling DCI (hereinafter, DL scheduling PDCCHs), and t-DAI is an index indicating the total number of DL scheduling PDCCHs up to the current slot in which there is a PDCCH having t-DAI.

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

[0187] UE uses DRX to reduce power consumption. UE operating based on DRX repeats ON / OFF for reception operation. The features of DRX utilized for the purpose of reducing unnecessary power consumption of UE are as follows. DRX defines a structure for UE in RRC_IDLE state where RRC connection between UE and BS is not established (hereinafter referred to as I-DRX) and a structure for UE in RRC_CONNECTED state where RRC connection between UE and BS is established (hereinafter referred to as C-DRX). Both DRX structures are designed to reduce unnecessary power consumption in other periods by defining a period (e.g., active time period or on-duration period) in which UE can expect reception of DL signals to occur periodically. For reference, in the case of C-DRX, the start position of On-duration occurs periodically in the Rel-16 standard, and the size of the cycle that can be configured at this time (i.e., DRX cycle) can be determined / set through upper layer signaling, such as RRC signaling, provided by the BS to the UE.

[0188] Figure 8 illustrates discontinuous reception (DRX) operation. In particular, Figure 8 illustrates a DRX cycle for a UE in RRC_CONNECTED state.

[0189] Referring to FIG. 8, a DRX cycle consists of an ON period and an Opportunity for DRX. A DRX cycle defines a time interval in which an ON period is periodically repeated, followed by a possible period of inactivity. The ON period represents a time interval during which the UE performs PDCCH monitoring to receive a PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the ON period. If a PDCCH is successfully detected during PDCCH monitoring, the UE starts an inactivity timer and remains awake. On the other hand, if no PDCCH is successfully detected during PDCCH monitoring, the UE enters a sleep state after the ON period ends. Therefore, when DRX is configured, the UE may perform PDCCH monitoring / reception discontinuously in the time domain when performing a process and / or method according to the implementation(s) of this specification. For example, when DRX is configured, the PDCCH reception occasion (e.g., slot having PDCCH search space) in this specification may be configured discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, the UE may perform PDCCH monitoring / reception continuously in the time domain. For example, when DRX is not configured, the PDCCH reception occasion (e.g., slot having PDCCH search space) may be configured continuously. On the other hand, regardless of whether DRX is configured, PDCCH monitoring may be restricted in the time period configured as the measurement gap. DRX configuration information is received via upper layer (e.g., RRC) signaling, and whether DRX is turned on / off is controlled by the DRX command of the MAC layer. When DRX is configured, the UE may perform PDCCH monitoring discontinuously, as illustrated in FIG. 8.

[0190] The following table illustrates the UE processes related to DRX. Referring to the following table, DRX configuration information is received via upper layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by the DRX command of the MAC layer. When DRX is configured, the UE can perform PDCCH monitoring discontinuously, as illustrated in FIG. 8.

[0191]

[0192] Here, MAC-CellGroupConfig contains configuration information required to set MAC parameters for a cell group. MAC-CellGroupConfig may also contain configuration information related to DRX. For example, MAC-CellGroupConfig may contain DRX-related information as follows.

[0193] - Value of drx-onDurationTimer: Sets the duration at the start of the DRX cycle.

[0194] - Value of drx-SlotOffset: Sets the delay before starting drx-onDurationTimer.

[0195] - Value of drx-InactivityTimer: Sets the period after which a PDCCH epoch indicates a new UL or DL ​​transmission to the MAC entity.

[0196] - Value of drxRetransmissionTimerDL (per DL HARQ process except for the broadcast process): Sets the maximum duration until a DL retransmission is received.

[0197] - Value of drxRetransmissionTimerUL (per UL HARQ process): Sets the maximum duration until a grant for UL retransmission is received.

[0198] - Value of drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): Sets the maximum period of time after a DL initial transmission is received until a DL assignment for HARQ retransmission is received.

[0199] - Value of drx-HARQ-RTT-TimerUL (per UL HARQ process): Sets the maximum period from when a grant for UL initial transmission is received until a grant for UL retransmission is received.

[0200] - drx-LongCycleStartOffset: Sets the Long DRX cycle and drx-StartOffset, which defines the subframe where the Long and Short DRX cycles start.

[0201] - drx-ShortCycle (optional): Sets the short DRX cycle.

[0202] - drx-ShortCycleTimer (optional): Sets the duration for which the UE should follow the Short DRX cycle. For example, a value in multiples of the Short DRX cycle can be set by drx-CylceTimer. For example, the value of n can correspond to n*drx-ShortCycle.

[0203] A UE may perform PDCCH monitoring on serving cells within a DRX group when the DRX group is within its active time. Here, a DRX group is a group of serving cells configured by RRC and having the same DRX active time. Here, the active time is a total duration for which the UE monitors the PDCCH, and may include an ON period of a DRX cycle, a time for which the UE performs continuous reception while an inactivity timer has not expired, and a time for which the UE performs continuous reception while waiting for a retransmission opportunity. For example, when DRX is configured, the active time for serving cells within a DRX group is i) while drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or ii) while drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell within the DRX group; or ra-ContentionResoultionTimer or msgB-RsponseWindow is running; or a PDCCH indicating a new transmission addressed to a C-RNTI addressed to the MAC entity of the UE is not received after successful reception of a random access response to a random access preamble that is not selected by the MAC entity among the contention-based random access preambles.

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

[0205] Extended reality (XR) is a hyper-realistic technology and service that utilizes virtual reality (VR), augmented reality (AR), mixed reality (MR), and holograms to provide users with an environment where they can communicate and live without spatial or temporal constraints in a virtual space similar to reality. XR is one of the key services to be introduced in NR wireless communication systems. XR is typically characterized by specific traffic with one or more downlink video streams that are tightly synchronized with frequent uplink pose / control updates. Additionally, XR has a high data rate and a strict packet delay budget (PDB). The PDB defines the 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, the PDB is a value that determines how long a generated packet must be transmitted.

[0206] In NR, one or more SPS PDSCHs or CG PUSCHs can be configured for a UE for periodic transmission and reception or for low latency and PDCCH overhead. The configured / indicated resources can be repeated in the time domain with a period according to each SPS / CG configuration. For example, the initially configured / indicated resource allocation is repeated with a period set by the SPS / CG configuration, and the UE can perform downlink reception / uplink transmission on the corresponding resources without a separate PDCCH reception process. Meanwhile, the types of data that can be generated in XR are diverse. Among these data, the transmission of UE sensor and location information and video data, which are generally reported with a specific period, are considered to be transmitted and received on SPS / CG resources. The traffic arrival time of these data may be inconsistent and jittery due to reasons such as video encoding time, sensor measurement time, upper layer operation, or routing changes in the network through which they are transmitted.

[0207] NR introduces a priority system at the PHY layer for multiple services, allowing the UE to perform uplink transmission or downlink reception using only one of the overlapping radio resources, or to perform uplink multiplexing by dividing the overlapping uplink transmissions into multiple groups. This is because XR requires that images be displayed accurately on the screen over time, and as soon as the time when XR data is required to be provided passes, previous data may become useless.

[0208] To support mobility and to identify the best serving cell, intra-cell or inter-cell measurements are performed by the UE. If the UE cannot simultaneously measure the target carrier frequency while transmitting / receiving on the serving cell, measurement gaps are required to perform the measurements. Measurement gaps may be required for intra-frequency, inter-frequency, and inter-RAT measurements. For example, measurement gap repetition periods of 20, 40, 80, and 60 ms and measurement gap lengths of 1.5, 3, 3.5, 4, 5.5, and 6 ms may be used for the measurement gaps. During the measurement gap (MG), the UE may switch to the target cell, perform signal quality measurements, and then return to the current cell. In some scenarios, the RF retuning time is 0.5 ms for carrier frequency measurements within the FR1 range and 0.25 ms for the FR2 range. During MGs, measurements may be performed on the SSBs of neighboring cells. For example, upon receiving an MG configuration, the UE may assume that the first subframe of each gap occurs in a system frame number (SFN) and subframe that meets the following conditions:

[0209] > SFN mod (MGRP / 10) = Floor (gapOffset / 10);

[0210] > subframe = gapOffset mod 10.

[0211] Here, MGRP and gapOffset can be provided from the network by the parameter mgrp indicating the MG repetition period within the MG configuration and the parameter gapOffset indicating the gap offset of the gap pattern within the MGRP indicated by the parameter mgrp.

[0212] A network (e.g., BS) can provide measurement timing for neighboring cells using SS / PBCH block measurement timing configurations (SMTCs). For example, a UE can set up the first SS / PBCH block measurement timing configuration based on the periodicityAndOffset parameter (which provides Periodicity and Offset values) within the SSB-MTC configuration. The first subframe of each SMTC period occurs in the SFN and subframe of an NR SpCell that meets the following conditions:

[0213] > SFN mod CEIL(Periodicity / 10) = (Floor (Offset / 10));

[0214] >ifPeriodicityis larger than sf5: subframe =Offsetmod 10;

[0215] > Else: subframe =Offsetor (Offset+ 5).

[0216] The SSB-MTC configuration is used to set measurement timing settings, e.g., timing occasions, for the UE to measure SSBs, and may include a parameter duration indicating the duration of the measurement window for receiving SS / PBCH blocks, a parameter periodicityAndOffset indicating the period and offset of the measurement window for receiving SS / PBCH blocks, etc.

[0217] The MG and SMTC durations can be configured to enable the UE to identify and measure SSBs within the SMTC. The network can provide the MG pattern to the UE via RRC signaling (e.g., IEMeasGapConfig in RRC configuration MeasConfig). The RRC configuration IEMeasGapConfig is used to specify MG configuration and control the setup / teardown of MGs (see 3GPP TS 38.331). MGs are periodic, and a UE can be configured with multiple MGs.

[0218] MG configuration is required to support mobility and allow the UE to identify the best serving cell, but it also causes the suspension of signal transmission / reception to allow the UE to perform measurements for intra / inter-frequency handover and / or beam management. For example, according to 3GPP TS 38.321 Release 17, during an activated MG, the UE:

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

[0220] > Without reporting a sounding reference signal (SRS);

[0221] > No transmission on UL-SCH except for Msg3 or MSGA payload, which is the first scheduled transmission in the random access process;

[0222] > If ra-ResponseWindow, which is a time window for monitoring random access response(s) on SpCell, ra-ContentionResolutionTimer, which is a contention resolution timer for SpCell, or msgB-ResponseWindow, which is a time window for monitoring random access response(s) for 2-stage random access type on SpCell, is running, PDCCH is monitored, otherwise PDCCH is not monitored and is not received on 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 via RRC signaling.

[0223] MG configuration is required for XR applications that support mobility or delay-sensitive services such as URLLC. However, according to current standards, the corresponding measurements according to MG have a higher priority than PDSCH receptions or PUSCH transmissions that carry the data of these services, so these services are interrupted during the MG period. However, for services with strict latency requirements such as XR services or URLLC services, the data or scheduling information for the data must be provided in a timely manner. Therefore, for XR or URLLC, which are sensitive to latency, MG, which is a time period during which scheduling information cannot be provided, can cause major problems.

[0224] In some scenarios (e.g., NR systems), a UE may be provided with an MG configuration from a BS for intra-cell or inter-cell measurements. As mentioned earlier, under current NR standards, a UE that has been explicitly provided with an MG configuration is not expected to transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / CSI-RS during the MG period, especially for measurements based on SSB reception. If the BS configures the MG to the UE based on the UE's SSB reception timing(s), the UE can typically have an MG period every 20 ms, and each MG period can have a length of 1 to 5 ms. If the MG period is 5 ms for 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 may affect the availability of the UE. For example, a UE that has been set with semi-persistent scheduling (SPS) / configured grant (CG) radio resources from a BS to receive or transmit periodic sensor information may not be able to perform SPS-based reception / CG-based transmission if the MG section and the SPS-based reception / CG-based transmission overlap in time.

[0225] One solution to these problems might be to define a mechanism that prevents scheduling of XR / URLLC packets and overlapping between MG segments. However, considering that MG segments are quasi-static according to RRC configuration (MG settings), while the generation and scheduling of XR / URLLC data are dynamic, preventing overlap between MG segments and XR / URLLC data generation and scheduling is either impractical or requires a very complex mechanism. Therefore, defining a mechanism that allows scheduling of MG segments and data transmission / reception to overlap in time may be undesirable or impractical.

[0226] Below, several implementations of this specification are described to address the aforementioned issues. Some implementations of this specification may consider behavior between a UE and a BS that allows transmission / reception on the MG based on certain criteria.

[0227] For convenience of explanation, some implementations of this specification are described below based on the NR system. However, implementations of this specification are not limited to specific transmission / reception formats of NR unless otherwise specified. Furthermore, for convenience of explanation, some implementations of this specification are described below based on the characteristics and structure of XR services. However, implementations of this specification are not limited to specific support of XR services unless otherwise specified.

[0228] In this specification, MG is used to encompass not only MG for inter-cell measurements, but also SMTC settings for intra-cell and / or intra-frequency measurements, and / or time intervals according to time window settings that cause scheduling restrictions. For example, MG may encompass the following intervals:

[0229] > Measurement gaps in NR inter / intra-frequency in measurement resource gap (RRM) measurement;

[0230] > Measurement gaps in inter RAT RRM measurement;

[0231] > Scheduling restriction in NR inter / intra-frequency RRM measurement without measurement gap;

[0232] > Scheduling restriction in L1 reference signal received power (L1-RSRP) measurement for reporting;

[0233] > Radio link monitoring (RLM) measurements;

[0234] > beam failure detection measurements;

[0235] > network controlled small gap (NCSG) where there are two interruptions in each NCSG occasion and scheduling restrictions apply during measurement length (ML) of the NCSG occasion;

[0236] > multi-USIM (MUSIM) gaps resulting from one or more per-UE MUSIM gap patterns and used for MUSIM purpose; and / or

[0237] > UL gaps for Tx power management, applicable only for NR FR2.

[0238] Below, some implementations of this specification are described that handle scheduling when, for example, a UE is provided with MG configuration(s) for intra-cell or inter-cell measurements from a BS, and is instructed or configured to receive one or more scheduling on the MG for delay-sensitive services such as XR / URLLC, when the UE needs to perform measurements on the MG periodically for adjacent cells or the current serving cell for purposes such as radio resource management (RRM).

[0239] Some implementations of the present specification described below may include a method for a BS to allocate PDSCH / PUSCH radio resources to a UE and a method for a UE to perform downlink reception and uplink transmission on the allocated radio resources, a method for transmitting a HARQ-ACK PUCCH response in response to a PDSCH reception result, and a method for receiving a retransmission DCI of a base station via a PDCCH after a PUSCH transmission. In addition, some implementations of the present specification described below may include a process in which a UE transmits a signal and channel to inform its capabilities and / or service requirements, and a BS receives the same.

[0240] In some implementations of this specification, a transmission occasion may refer to a radio resource (e.g., an SPS PDSCH resource or a CG PUSCH resource) that occurs based on an SPS / CG configuration. A transmitter (e.g., a BS for downlink or a UE for uplink) that performs transmission may attempt to transmit a physical channel / signal at a transmission occasion, and a corresponding receiver (e.g., a UE for downlink or a BS for uplink) may expect that the transmitter will transmit at each transmission occasion and attempt to receive it. In this specification, the term transmission occasion is used interchangeably with the term transmission opportunity. In addition, in this specification, a transmission occasion is also referred to as a reception occasion from the receiver's perspective. Alternatively, the term 'occasion' may be used instead of the terms 'transmission occasion' and 'reception occasion'.

[0241] Figure 9 illustrates a flow of UE operations to which some implementations of this specification may be applied.

[0242] The UE can be configured with an MG interval for RRM, etc. from the BS through RRC signaling (e.g., RRC configuration MeasConfig and / or RRC configuration MeasGapConfig) (S901). For example, one or more MG configurations can be provided to the UE by the BS. In some implementations of the present specification, information about the configured MG intervals (e.g., MG configurations) may include information about the priority of each MG interval, or index(es) of PDCCH, CSI-RS, SR, and / or SPS / CG configurations associated therewith, etc. For example, in some implementations of the present specification, each MG configuration may include priority information for the corresponding MG(s), or index(es) of PDCCH, CSI-RS, SR, and / or SPS / CG configurations associated therewith.

[0243] If the PDSCH reception timing based on explicit PDSCH scheduling via L1 signaling (e.g., PDCCH) or SPS configuration or the PUSCH transmission timing based on explicit PUSCH scheduling via L1 signaling (e.g., PDCCH) or CG configuration does not overlap (in time) with the MG according to the MG configuration (S903, No), the UE may perform operation A1 (S904). The operation A1 may include performing measurements configured via RRC configuration MeasConfig associated with the MG configuration within the MG, and attempting to receive a PDSCH at the PDSCH reception timing or performing a PUSCH transmission at the PUSCH transmission timing. If the PDSCH reception time based on explicit scheduling via L1 signaling (e.g., PDCCH) or SPS configuration, or the PUSCH transmission time based on explicit scheduling via L1 signaling (e.g., PDCCH) or CG configuration, or the PDCCH monitoring time overlaps (in time) with the MG according to the MG configuration (S803, Yes), i) the UE may perform operation A2 (S906) if specific condition(s) are not satisfied (S905, No), and ii) if the specific condition(s) are satisfied (S905, Yes), the UE may attempt to receive a PDSCH at the PDSCH reception time within the MG, attempt to transmit a PUSCH at the PUSCH transmission time, or perform PDCCH monitoring at the PDCCH monitoring time within the MG (S907). The operation A2 may include:

[0244] i) Perform measurements set through RRC configuration MeasConfig associated with the above MG configuration within the MG; and

[0245] ii) On the serving cell(s) within the corresponding frequency range of the above MG:

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

[0247] > Without reporting a sounding reference signal (SRS);

[0248] > No transmission on UL-SCH except for Msg3 or MSGA payload, which is the first scheduled transmission in the random access process;

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

[0250] In some implementations, if the above-mentioned specific condition(s) are satisfied (S905, Yes), the UE may perform measurements related to the MG within the MG. Alternatively, in some implementations, if the above-mentioned specific condition(s) are satisfied (S905, Yes), the UE may not perform measurements related to the MG within the MG.

[0251] In some implementations, the specific condition(s) may mean a condition(s) that may allow operations (e.g., operation A2) specified (in a specific standard document (e.g., 3GPP TS 38.321)) to be performed within the MG on serving cell(s) within the corresponding frequency range of the MG configured (and / or activated) by an RRC configuration (e.g., the RRC configuration measGapConfig described in 3GPP TS 38.331) not to be performed by the UE. The specific condition(s) may include condition(s) according to one or more of implementations 1 to 7 described below.

[0252] For example, in some implementations of the present specification, a UE may receive a scheduling message or SPS / CG configuration from a BS for PDSCH reception or PUSCH transmission on an MG interval. A UE that is instructed to perform PDSCH reception or PUSCH transmission on an MG interval via an explicit scheduling message via L1 signaling (e.g., PDCCH) may, for example, perform the instructed PDSCH reception or PUSCH transmission without performing adjacent cell measurement in the corresponding MG interval. A UE that has an SPS reception opportunity (i.e., an SPS PDSCH reception time) and / or a CG transmission opportunity (i.e., a CG PUSCH transmission time) on the MG interval may perform SPS reception or CG transmission according to the characteristics of the corresponding MG interval. For example, if the MG configuration includes information about a priority for the MG interval, the configured or instructed PDSCH reception or PUSCH transmission may be performed without performing adjacent cell measurement in the corresponding MG interval if the information about the priority is less than or equal to a certain value. As another example, if the MG configuration includes information about an SPS configuration and / or a CG configuration associated with the MG configuration, and if PDSCH reception / PUSCH transmission according to an SPS / CG configuration having the same index as the associated SPS / CG configuration overlaps with an MG according to the MG configuration, the UE may perform the PDSCH reception or the PUSCH transmission without performing adjacent cell measurement in the corresponding MG section.

[0253] Figure 10 illustrates the flow of BS operations to which some implementations of this specification may be applied.

[0254] The BS may configure an MG interval for RRM, etc. to the UE via RRC signaling (e.g., RRC configurationMeasConfig and / or RRC configurationMeasGapConfig) (S1001). For example, one or more MG configurations may be provided by the BS to the UE. In some implementations of the present specification, information about the configured MG intervals (e.g., MG configurations) may include information about the priority of each MG interval, or index(es) of PDCCH, CSI-RS, SR, and / or SPS / CG configurations associated therewith, etc. For example, in some implementations of the present specification, each MG configuration may include priority information for the corresponding MG(s), or index(es) of PDCCH, CSI-RS, SR, and / or SPS / CG configurations associated therewith.

[0255] If the PDSCH transmission timing based on explicit scheduling via L1 signaling (e.g., PDCCH) or SPS configuration or the PUSCH reception timing based on explicit scheduling via L1 signaling (e.g., PDCCH) or CG configuration does not overlap (in time) with the MG according to the MG configuration (S1003, No), the BS may assume that the UE will perform operation A1 illustrated in FIG. 9 and may perform operation B1 (S1004). The operation B1 may assume that the measurements configured via the RRC configuration MeasConfig associated with the MG configuration will be performed within the MG and may receive a measurement report related to the MG from the UE, and may assume that the UE will receive the PDSCH at the PDSCH transmission timing or transmit the PUSCH at the PUSCH reception timing and may perform the PDSCH transmission at the PDSCH transmission timing and attempt to receive the PUSCH at the PUSCH reception timing.If the PDSCH transmission time based on explicit scheduling via L1 signaling (e.g., PDCCH) or SPS configuration, or the PUSCH reception time based on explicit scheduling via L1 signaling (e.g., PDCCH) or CG configuration, or the PDCCH monitoring time set for the UE(s) overlaps (in time) with the MG according to the MG configuration (S1003, Yes), i) the BS may perform operation B2 (S1006) assuming that the UE will perform operation A2 illustrated in FIG. 9 if the specific condition(s) are not satisfied (S1005, No), and ii) if the specific condition(s) are satisfied (S1005, Yes), the BS may perform PDSCH transmission at the PDSCH transmission time assuming that the UE will receive a PDSCH in the MG or transmit a PUSCH at the PUSCH reception time, or attempt to receive a PUSCH at the PUSCH reception time, or may perform PDCCH monitoring at the PDCCH monitoring time. Transmission can be performed (S1007). The above operation B2 may include:

[0256] i) assuming that the UE will perform measurements configured through the RRC configuration MeasConfig associated with the MG configuration within the MG, and receives a measurement report related to the MG from the UE; and / or

[0257] ii) On the serving cell(s) within the corresponding frequency range of the above MG:

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

[0259] > Not expecting or attempting to report a sounding reference signal (SRS) from the UE;

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

[0261] > If ra-ResponseWindow, which is a time window for monitoring random access response(s) on SpCell, or ra-ContentionResolutionTimer, which is a contention resolution timer for SpCell, or msgB-ResponseWindow, which is a time window for monitoring random access response(s) for 2-stage random access type on SpCell, is running, then PDCCH is transmitted to the UE, otherwise, PDCCH is not transmitted and no transmission is made on DL-SCH to the UE.

[0262] 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 satisfied (S1005, Yes). Alternatively, 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 satisfied (S1005, Yes).

[0263] The above specific condition(s) may include condition(s) according to one or more of Implementations 1 to 7 described below.

[0264] For example, in some implementations of the present specification, a BS may transmit a scheduling message or SPS / CG configuration to a UE for PDSCH reception or PUSCH transmission on an MG interval. If a UE is instructed to perform PDSCH reception or PUSCH transmission on an MG interval through an explicit scheduling message via L1 signaling (e.g., PDCCH), the BS may, for example, expect or assume that the UE will receive the instructed PDSCH or transmit the PUSCH without performing adjacent cell measurement on the MG interval, and perform the PDSCH transmission or attempt to receive the PUSCH. If an SPS transmission opportunity (i.e., an SPS PDSCH transmission time) and / or a CG reception opportunity (i.e., a CG PUSCH reception time) occurs for the UE on the MG interval, the BS may operate under the expectation or assumption that the UE will perform SPS reception or CG transmission according to the characteristics of the MG interval. For example, if the MG configuration includes information about priorities in the MG section, the BS may expect / assume and operate that the UE will perform the configured or instructed PDSCH reception or PUSCH transmission without performing adjacent cell measurement in the MG section if the information about the priorities is below a certain value. As another example, if the MG configuration includes information about associated SPS configurations and / or CG configurations, the BS may expect / assume and operate that the UE will perform the configured or instructed PDSCH reception or PUSCH transmission without performing adjacent cell measurement in the MG section if the PDSCH transmission / PUSCH reception according to the SPS / CG configuration having the same index as the associated SPS / CG configuration overlaps with the MG according to the MG configuration.

[0265] In FIGS. 9 and 10, the UE operation flow and the BS operation flow are described using the case where the PDSCH / PUSCH period overlaps with the MG as an example, but the UE and the BS can also operate in the same manner as described in FIGS. 9 and 10 for the SRS period, the CSI-RS period, and the PUCCH period.

[0266] Some of the methods according to Implementations 1 to 7 of this specification described below may be selected and applied. Alternatively, each method may be applied independently without any separate combination, or one or more methods may be combined and operated in a linked manner.

[0267] Some implementations of this specification may be specified to apply only when the UE has received relevant configuration information from the BS (or core network). In this case, the configuration information may be provided to the UE via a higher layer signal (e.g., a system information block (SIB) or RRC signaling), or a method in which the configuration information is activated / deactivated via separate signaling (e.g., a DCI or MAC control element) may be used together. Furthermore, in some implementations of this specification, the UE may be specified to report information (e.g., capabilities) regarding whether the method(s) described below can be supported and receive this from the BS (or core network).

[0268] 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 overlap according to the MG configuration.

[0269] <Implementation 1: Ignore / disable MG based on search space>

[0270] When a PDCCH having the following characteristics overlaps with an MG or when a resource scheduled by a DCI received on such a PDCCH overlaps with an MG, the UE may detect the DCI on the PDCCH or give priority to transmission or reception of radio resources indicated by the received scheduling DCI (e.g., PUSCH transmission or PDSCH reception) without performing measurements on the MG. The characteristics may be at least one of the following. For example, at least one of the following may be a specific condition mentioned in FIG. 9 or FIG. 10, and when a PDCCH satisfying the following characteristics overlaps with an MG, the PDCCH and / or the PUSCH / PDSCH transmission / reception scheduled by the PDCCH may be performed instead of operation A2 / B2 within the MG.

[0271] > PDCCH received through Type-0 common search space (CSS)

[0272] > A PDCCH received through a searchspace with a specific flag setting. The flag setting may be included in an information element (IE) searchspace, which is an RRC setting, and may indicate whether scheduling restrictions such as MG / SMTC are applied.

[0273] > PDCCH in DRX On duration state (e.g. PDCCH transmitted / received during the time when the retransmission timer configured for DRX is running) via retransmission timer. For example, the UE may prioritize PDCCH for receiving retransmission scheduling of that transmission / reception over MG / SMTC after previous other PUSCH transmission / PDSCH reception.

[0274] In some implementations, the application of Implementation 1 may be limited to downlink reception scheduling (e.g., a PDCCH scheduling PDSCH reception) or to uplink transmission scheduling (e.g., a PDCCH scheduling PUSCH transmission). In this case, for example, if Implementation 1 is limited to downlink reception scheduling, Implementation 1 may not be applicable to transmitting a HARQ-ACK response to a PDSCH received during downlink reception on PUCCH / PUSCH.

[0275] In some implementations, whether or not Implementation 1 is applied may vary depending on the MG configuration. For example, measurements may not be performed on the MG and / or transmission or reception of radio resources indicated by the scheduling DCI may be performed only when an explicit scheduling DCI with the above characteristics overlaps with a specific MG. This specific MG may be determined by the presence or absence of a certain parameter in the MG configuration, or by the value of a certain parameter. For example, the specific MG may be determined based on the value of the parameter mgl or mgl-r16 indicating the length of the MG interval (within the MG configuration) being greater than a certain size, or the presence or absence of the parameter mgl-r16.

[0276] <Implementation 2: Scheduling restriction handling for slot aggregation>

[0277] A method is being considered for ignoring scheduling restrictions on the MG / SMTC and receiving PDSCH / PDCCH on the MG / SMTC under certain conditions using Implementation 1 of this specification or a similar method. However, if repeated transmissions are used on the PDSCH, some implementations may consider performing inter-frequency or intra-frequency measurements on the MG / SMTC as before, rather than ignoring the MG / SMTC and performing reception, and continuing to receive the PDSCH in another slot. For example, the following may be considered:

[0278] > When scheduling restrictions of MG / SMTC are ignored and PDSCH is scheduled within the MG / SMTC interval using Implementation 1 of this specification or a similar method, and the UE performs PDSCH reception on the MG / SMTC, the UE does not receive the PDSCH on the MG / SMTC if repetitive transmission is configured for the PDSCH. For example, the UE may not receive repetitive transmissions of PDSCH that overlap at least one symbol with the MG / SMTC. This may mean that when repetitive transmission is configured for the PDSCH, scheduling the PDSCH within the MG / SMTC interval is allowed, but the UE is not required / expected to receive and decode transmissions according to the scheduling within the MG / SMTC interval.

[0279] > This behavior may be applied only to scheduling of PDSCH where repeated transmissions are performed in a period longer than the typical length of SMTC (e.g., SMTC window duration). The SMTC window duration may be set from 1 ms to 5 ms, and a typical SMTC window duration may be 4-5 ms for 15 kHz subcarrier spacing or 2-3 ms for 30 kHz subcarrier spacing to allow the UE to receive all SSB(s) of the neighboring cell. For example, Implementation 2 may be applied only to PDSCH where 5 or more repeated transmissions are used, or when the total duration of the PDSCH is 5 ms or longer (e.g., 10 or more repeated transmissions in 30 kHz SCS), the total duration of slots with PDSCH repetitions, such that PDSCH reception on MG / SMTC may be excluded. If this is not the case (e.g., if the repetitive transmission is performed in a period that is not longer than the normal SMTC window period), the UE may not attempt to receive the corresponding PDSCH without performing measurements within the MG / SMTC period or may not expect such scheduling (e.g., if the PDSCH with the repetitive transmission is scheduled in a short period on the MG / SMTC).

[0280] <Implementation 3: How to guarantee MG / SMTC after prioritization>

[0281] For continuous transmission of XR traffic, transmission may need to occur over the SMTC / MG to meet PDB requirements, but measurements over the SMTC / MG may also be important. Considering this, methods that allow some transmission over the SMTC / MG while ensuring inter- and intra-frequency measurements over the SMTC / MG may be considered. For example, the following may be considered:

[0282] When a UE receives a PDSCH / PDCCH, etc. without performing a measurement in a SMTC window or MG using Implementation 1 of this specification or a similar method, the UE may perform a measurement in the next SMTC window or MG period after the SMTC window or MG period without giving priority to other transmissions. For example, when a UE receives a PDSCH / PDCCH, etc. without performing a measurement in a previous SMTC window or MG period, the UE may perform a measurement in the adjacent (next) SMTC window or MG period without receiving the PDSCH / PDCCH even if the PDSCH / PDCCH is scheduled in the period.

[0283] <Implementation 4: Fallback measurement resource for disabled SMTC / MG>

[0284] To enable the UE to receive PDSCH / PDCCH in the SMTC / MG interval, a method of temporarily disabling the SMTC / MG interval via L1 signaling and allowing the UE to receive scheduled / configured PDSCH / PDCCH may be considered. In some implementations of this specification, disabling the SMTC / MG interval may correspond to specific conditions described in FIG. 9 or FIG. 10 .

[0285] When temporarily disabling the SMTC / MG interval via L1 signaling and the UE receives scheduled / configured PDSCH / PDCCH, in some implementations, the UE may be configured with a separate SMTC / MG interval and reference signal (RS) resources that can be used as an alternative to compensate for measurements made on the disabled SMTC / MG interval. For example, the following may be considered:

[0286] When a BS deactivates an SMTC / MG interval to a UE via L1 signaling and the UE receives a PDSCH / PDCCH (if any) scheduled / configured on the SMTC / MG interval, the BS may configure in advance information about an alternative SMTC / MG interval that the UE can use for intra-frequency / inter-frequency measurements during the time that the SMTC / MG interval is deactivated and information about RS resources for alternative measurements that can be used in the interval.

[0287] <Implementation 5: Ignore / disable MG in slot-level>

[0288] The UE may, under certain conditions, ignore the scheduling restrictions of the MG / SMTC only in some slot(s) within the MG lasting for N slots (or N ms) in accordance with the other implementations (e.g., implementation 1 and / or implementation 3) or similar methods, and prioritize other downlink reception or uplink transmission (e.g., general downlink reception or uplink transmission rather than reception for measurement or measurement reporting) on ​​the MG / SMTC and, if necessary, also skip measurements. In this case, a UE operation may be supported in which measurements are not performed on the MG only in those slots (e.g., some of the slots constituting the MG), while measurements and transmission / reception are continuously restricted in the remaining slots.

[0289] To this end, the BS may transmit slot information regarding slot(s) to which the other implementations (e.g., implementation 1 and / or implementation 3) or a similar method are applied in the MG section for N slots via RRC signaling to the UE. The slot information may be expressed in the form of a bitmap, each bit indicating whether the other implementations (e.g., implementation 1 and / or implementation 3) are applied in the corresponding slot. For example, when N=10, the bitmap "1010100010" may mean that the other implementations are applied only in the first, third, seventh, and tenth slots. Alternatively, other downlink reception or uplink transmission may be given priority in the slot(s) indicated by the slot information, and measurement may also be omitted if necessary.

[0290] In another additional way, with the N slots divided into M (M < N) slot groups, the UE behavior in each slot group (e.g., whether to skip measurement and perform / monitor uplink / downlink transmission / reception and / or scheduling, or to prioritize performing measurements without expecting uplink / downlink transmission / reception and / or scheduling as before) can be indicated using an M-bit bitmap. Alternatively, in some implementations, with the N slots divided into three slot groups - front, middle, and back - one of the following four behaviors can be indicated to the UE using a 2-bit field.

[0291] 1) Omit measurements in the front slot group and perform / monitor uplink / downlink transmission / reception and / or scheduling (in the remaining slot groups, perform measurements first without expecting uplink / downlink transmission / reception and / or scheduling as before).

[0292] 2) Omit measurements in the rear slot group and perform / monitor uplink / downlink transmission / reception and / or scheduling (in the remaining slot groups, priority is given to performing measurements without expecting uplink / downlink transmission / reception and / or scheduling as before).

[0293] 3) Omit measurements in the front and rear two slot groups and perform / monitor uplink / downlink transmission / reception and / or scheduling (in the remaining slot groups, priority is given to performing measurements without expecting uplink / downlink transmission / reception and / or scheduling as before).

[0294] 4) In all three slot groups, measurements are performed first without expecting uplink / downlink transmission / reception and / or scheduling as before.

[0295] In addition, even without setting a bitmap, the UE may perform an operation in which measurements are not performed on the MG only in the slots scheduled by the DCI to which the other implementation or a similar method is applied, and measurements are performed and transmission / reception is restricted in the remaining slots. For example, if the UE receives a DCI to which the other implementation or a similar method is applied within the MG section, the UE may not perform measurements only in the slots scheduled by the DCI, but may prioritize transmission / reception, and perform measurements or restrict transmission / reception as before in the remaining slots.

[0296] In some implementations, Implementation 5 may only be applied to certain MG configurations. The application of Implementation 5 may be indicated via an additional parameter within the MG configuration. Alternatively, the bitmap configuration may be applied to each MG configuration configurable via RRC signaling.

[0297] Using Implementation 5, the UE can prioritize transmission / reception over N slots in the MG interval, without performing measurements, only in slots scheduled by the DCI to which the other implementations or similar methods are applied, and perform measurements as before or restrict transmission / reception in the remaining slots. This allows PDCCH monitoring and / or PDCCH-scheduled transmission / reception to be guaranteed in certain slots within the MG interval, while maintaining measurement performance in the remaining slots.

[0298] <Implementation 6: Ignore / disable MG in symbol-level>

[0299] The UE may, under certain conditions, ignore the scheduling restrictions of the MG / SMTC only during some symbol(s) on the MG lasting for N symbols, in accordance with the other implementations (e.g., implementation 1 and / or implementation 3) or similar methods, and prioritize other downlink reception or uplink transmission (e.g., general downlink reception or uplink transmission rather than reception for measurement or measurement reporting) on ​​the MG / SMTC and, if necessary, also skip measurements. In this case, a UE operation may be supported in which measurements are not performed on the MG only during the corresponding symbol, and measurements and transmission / reception are continuously restricted during the remaining symbols.

[0300] To this end, the BS may transmit to the UE, via RRC signaling, symbol information regarding symbol(s) for which other downlink reception or uplink transmission may be given priority in the MG interval for N symbols, and for which measurement may also be omitted if necessary. The symbol information may be expressed in the form of a bitmap, with each bit indicating whether different implementations (e.g., implementation 1 and / or implementation 3) are applied to the corresponding symbol. For example, if N=14, the bitmap "10101000100010" may mean that different implementations are applied only to the first, third, fifth, tenth, and thirteenth symbols.

[0301] In another additional way, the N symbols may be divided into M (M < N) symbol groups, and an M-bit bitmap may be used to indicate the UE's action in each symbol group (e.g., whether to skip measurement and perform / monitor uplink / downlink transmission / reception and / or scheduling, or to prioritize measurement without expecting uplink / downlink transmission / reception and / or scheduling as before). Alternatively, in some implementations, the N symbols may be divided into three symbol groups - front, middle, and back - and a 2-bit field may be used to indicate one of the following four actions to the UE:

[0302] 1) Omit measurements in the front symbol group and perform / monitor uplink / downlink transmission / reception and / or scheduling (in the remaining symbol groups, perform measurements first without expecting uplink / downlink transmission / reception and / or scheduling as before).

[0303] 2) Omit measurements in the rear symbol group and perform / monitor uplink / downlink transmission / reception and / or scheduling (in the remaining symbol groups, perform measurements first without expecting uplink / downlink transmission / reception and / or scheduling as before).

[0304] 3) Omit measurements in the front and rear two symbol groups and perform / monitor uplink / downlink transmission / reception and / or scheduling (in the remaining symbol groups, priority is given to performing measurements without expecting uplink / downlink transmission / reception and / or scheduling as before).

[0305] 4) In all three slot symbols, measurements are performed first without expecting uplink / downlink transmission / reception and / or scheduling as before.

[0306] In addition, even without setting a bitmap, the UE can perform an operation in which measurements are not performed on the MG only in the symbols scheduled by the DCI to which the other implementation or a similar method is applied, and measurements are performed and transmission / reception is restricted in the remaining symbols. For example, if the UE receives a DCI to which the other implementation or a similar method is applied within the MG section, the UE may not perform measurements only in the symbols scheduled by the DCI, but may prioritize transmission / reception, and perform measurements or restrict transmission / reception as before in the remaining symbols.

[0307] In some implementations, Implementation 6 may only be applied to certain MG configurations. The application of Implementation 6 may be indicated through an additional parameter within the MG configuration. Alternatively, the bitmap configuration may be applied to each MG configuration configurable via RRC signaling.

[0308] Using Implementation 6, the UE can prioritize transmission / reception during the MG interval for N symbols, without performing measurements only on symbols scheduled by the DCI to which the other implementations or similar methods are applied, and perform measurements as before or limit transmission / reception during the remaining symbols. This allows PDCCH monitoring and / or PDCCH-scheduled transmission / reception to be guaranteed during certain symbols within the MG interval, while maintaining measurement performance during the remaining slots.

[0309] <Implementation 6-1: Partially ignore / disable MG in symbol-level>

[0310] In Implementation 6, when MG is ignored or disabled on a symbol-by-symbol basis, the question arises as to how to handle scheduled transmissions / receptions in cases where only some symbols of the scheduled transmissions / receptions are allowed and the remaining symbols are restricted. In cases where some symbols of the scheduled transmissions / receptions are allowed and the remaining symbols are restricted, at least one of the following may be supported as a handling method for the scheduled transmissions / receptions.

[0311] > A method that only allows scheduling where all symbols can transmit / receive without MG restrictions

[0312] > A method that allows scheduling if at least one symbol can be transmitted / received without MG restrictions.

[0313] > A method of allowing transmission / reception only when all symbols can be transmitted / received without MG restrictions during scheduling dynamically instructed by the BS (e.g., PUSCH transmission, PUCCH transmission, and / or PDSCH reception).

[0314] > A method of allowing scheduling (e.g., transmission / reception) dynamically indicated by the BS if at least one symbol among the scheduling (e.g., PUSCH transmission, PUCCH transmission, and / or PDSCH reception) can be transmitted / received without MG restriction.

[0315] One or more of these methods may be configured to the UE via higher layer signaling and may be selectively applied as needed between the UE and the BS.

[0316] In some implementations, if some symbols in a scheduled transmission / reception cannot be transmitted / received due to MG constraints, techniques such as rate matching or puncturing can be used to improve resource utilization. This ensures measurement performance in the MG interval while maximizing the utilization of available symbols.

[0317] By adding an action plan for allowing partial scheduling when the MG unit is disabled, the content of Implementation 6 is expected to become clearer and support flexible and efficient operation between the BS and UE while minimizing measurement performance degradation in the MG section.

[0318] <Implementation 7: Ignore / disable MG considering CSI reference resource>

[0319] The UE may, under certain conditions, ignore the scheduling restrictions of the MG / SMTC and give priority to other downlink reception or uplink transmission (e.g., general downlink reception or uplink transmission rather than reception for measurement or measurement reporting) on ​​the MG / SMTC only for some symbol(s) on the MG lasting for N symbols, in accordance with the other implementations (e.g., implementation 1 and / or implementation 3) or similar methods, and may also skip measurements if necessary. In this case, UE operation considering the CSI reference resource and the previously configured measurement gap may be required.

[0320] For reference, according to Rel-16 of 3GPP TS 38.214, the CSI reference resources for the serving cell are defined as follows:

[0321] > In the frequency domain, the CSI reference resource is defined by a group of downlink PRBs corresponding to the bands to which the derived CSI is related.

[0322] > In the time domain, the CSI reference resource for reporting CSI in slot n' is a single DL slot n - n CSI_ref is defined by,

[0323] >> Here n=floor{n'*(2^u DL / 2^u UL )} + floor{(n CA slot,offset,UL / 2^u offset,UL ) - (n CA slot,offset,DL / 2^u offset,DL )}, and u DL and u UL are the subcarrier spacing settings for DL ​​and UL, respectively, and n CA slot, offset, and u offset is determined by the upper-layer set ca-SlotOffset for cells transmitting uplink and downlink.

[0324] >> About periodic and semi-continuous CSI reporting here

[0325] >>> When a single CSI-RS / SSB resource is configured for channel measurement, n CSI_ref , which corresponds to a valid downlink slot, 4*2^u DL The smallest value greater than or equal to, or

[0326] >>> When multiple CSI-RS / SSB resources are configured for channel measurement, n CSI_ref 5*2^u, which makes it correspond to a valid downlink slot DL The smallest value greater than or equal to .

[0327] >> For aperiodic CSI reporting here, if the UE is instructed by DCI to report CSI in the same slot as the CSI request, n CSI_ref is to ensure that the reference resource is in the same valid downlink slot as the corresponding CSI request, otherwise n CSI_ref Silver slot n - n CSI_reffloor(Z' / N) to ensure that it is a valid downlink slot. slot symb ) is the smallest value greater than or equal to , where Z' corresponds to the delay requirement (see Table 8 or Table 9).

[0328] >> When periodic or quasi-persistent CSI-RS / CSI interference measurement (CSI-IM) or SSB is used for channel / interference measurements, the UE is not expected to measure channel / interference on CSI-RS / CSI-IM / SSB received up to Z' symbols before the transmission time of the first OFDM symbol of the aperiodic CSI report, where the last OFDM symbol is received.

[0329] Table 8 exemplifies CSI calculation delay requirement 1, and Table 9 exemplifies CSI delay requirement 2. For example, according to Rel-16 of 3GPP TS 38.214, Z, Z', and u can be defined as Z = maxm=0,...,M-1(Z(m)) and Z' = maxm=0,...,M-1(Z'(m)), where M is the number of updated CSI report(s), and (Z(m),Z'(m)) corresponds to the m-th updated CSI report and is defined as (Z1,Z1') in Table 8, (Z1,Z1') in Table 9, (Z3,Z3') in Table 9, or (Z2,Z2') in Table 9, depending on the predefined conditions.

[0330]

[0331]

[0332] u in Table 8 and Table 9 is min(u PDCCH , u CSI-RS , u UL ) corresponds to, where u PDCCH corresponds to the subcarrier spacing of the PDCCH on which the DCI is transmitted, and u UL corresponds to the subcarrier spacing of the PUSCH where the CSI report will be transmitted, u CSI-RScorresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by the above DCI. In Table 9, X u is based on UE reported capability beamReportTiming, KB l is based on the UE reported capability beamSwitchTiming (see 3GPP TS 38.306).

[0333] A slot within a serving cell may be considered a valid downlink slot if the slot contains at least one higher layer configured downlink or flexible symbol and if the slot does not fall within the configured measurement gap for the UE. If there is no valid downlink slot for a CSI reference resource corresponding to the CSI reporting setting in the serving cell, CSI reporting is omitted for the serving cell in uplink slot n'.

[0334] After CSI reporting (re)establishment, serving cell activation, BWP change, or activation of semi-persistent (SP)-CSI, the UE reports the CSI report only after receiving at least one CSI-RS occasion for channel measurement and CSI-RS and / or CSI-IM occasion for interference measurement that is not later than the CSI reference resource, otherwise it drops the CSI report.

[0335] The UE derives, for example, for each CQI value reported in uplink slot n, the highest CQI index satisfying the following conditions: a single PDSCH transport block, corresponding to the CQI index, having a combination of modulation scheme, target code rate and transport block size, and occupying a group of downlink physical resource blocks called CSI reference resources, can be received with a transport block error probability not exceeding a predefined value. According to higher layer parameter values ​​provided by the BS: the UE derives channel measurements for computing the CSI value reported in uplink slot n based only on the timing of a non-zero power (NZP) CSI-RS associated with the CSI resource setting, which is not later than the CSI reference resource; the UE derives channel measurements for computing the CSI value reported in uplink slot n based only on the timing of a most recent NZP CSI-RS associated with the CSI resource setting, which is not later than the CSI reference resource; The UE derives an interference measurement for calculating a CSI value reported in uplink slot n based only on a CSI-IM and / or NZP CSI-RS for interference measurement that is not later than the CSI reference resource associated with the CSI resource setting; or the UE derives an interference measurement for calculating a CSI value reported in uplink slot n based on a most recent CSI-IM and / or NZP CSI-RS for interference measurement that is not later than the CSI reference resource associated with the CSI resource setting.

[0336] In some implementations, when configured to report a CQI index, the UE assumes certain conditions for the purpose of deriving the CQI index and also, if configured, for deriving the PMI and RI in the CSI reference resource. For example, the UE assumes the following in the CSI reference resource: the first two OFDM symbols are occupied by control signaling; the number of PDSCH and DM-RS symbols is 12; the same bandwidth part subcarrier spacing as that configured for PDSCH reception; the bandwidth configured for the corresponding CQI reporting; the reference resource uses the CP length and subcarrier spacing configured for PDSCH reception; no resource elements are used for primary or secondary synchronization signals or PBCH; redundancy version 0, etc.

[0337] In some scenarios, a CSI report is triggered via RRC and / or DCI, the CSI report is associated with a CSI report configuration, the CSI report configuration indicates PUCCH resource(s) and CSI-RS resource configuration to be used for the CSI report, and the UE determines a CSI reference resource to be used for the triggered CSI report. This can be basically described as a process of finding the nearest CSI-RS / CSI-IM / SSB that satisfies a required processing time Z or Z' for the CSI report.

[0338] Figures 11 to 13 illustrate some implementations of the present specification for handling CSI reference resources when a CSI reference resource overlaps with an MG. Figures 11 to 13 illustrate a case where gapOffset = 24, MGRP = 40 ms, and gap length (e.g., mgl) = 4 ms are provided through MG configuration, and it is assumed that subframes #4, #5, #6, and #7 among subframes #0 to #9 in frames with SFN #22 and SFN #26, respectively, become MGs.

[0339] In implementation 7, the UE may ignore the scheduling restrictions of the MG / SMTC, taking into account the CSI reference resource and the previously configured MG, and give priority to other downlink reception or uplink transmission in the MG / SMTC, and may also omit measurements (e.g., measurements according to the MG / SMTC configuration and / or CSI measurements) if necessary. For example, the UE may not perform downlink reception for CSI measurements if it ignores the scheduling restrictions of the MG / SMTC. This behavior may be performed only if the signaling indicating to ignore the scheduling restrictions of the MG / SMTC is delivered without sufficient time to resume CSI measurements. For example, CSI measurements during the MG may be enabled or disabled on a separate timeline. More specifically, if a signaling to the UE to skip measurements in a certain MG / SMTC and ignore scheduling restrictions is not received before the start of a CSI reference resource or before the time T required to resume CSI measurements from the start time of the corresponding MG / SMTC, the UE may not perform CSI reference resource measurements in the corresponding MG / SMTC from which measurements were skipped. For example, referring to FIG. 11, if a CSI reference resource exists in an MG of SFN #26, the UE and the BS may determine that the MG of SFN #26 is deactivated and determine the CSI reference resource in the MG as valid if a signaling to ignore or deactivate the MG of SFN #26 is received before the start of the MG of SFN #26 by the time T (see FIG. 11(a)), otherwise, the MG of SFN #26 may be determined not to be deactivated and determine the CSI reference resource in the MG as invalid (see FIG. 11(b)).

[0340] Additionally, in some implementations, if an MG is canceled (e.g., if measurements are canceled on a certain MG (e.g., an MG that has been instructed to be canceled / deactivated among multiple MGs according to MG configuration or an MG(s) after the cancellation / deactivation instruction) and other downlink reception or uplink transmission is given priority), the CSI reference resources within that MG may still be considered invalid. To this end, as illustrated in FIG. 12, the UE determines the validity of the CSI reference resources based on the original MG configuration regardless of whether the MG is canceled. By doing so, the problem that the CSI reference resources suddenly become valid due to MG cancellation can be prevented.

[0341] Also, in some implementations, if the MG cancellation indication was delivered via RRC, the UE may resume CSI measurements on the cancelled MG and assume that the CSI reference resources included in the MG interval may be valid (see FIG. 13(a)), whereas if the MG cancellation (e.g., MG deactivation) was indicated via DCI, the UE may skip CSI measurements on the cancelled MG as before and assume that the CSI reference resources included in the MG interval are invalid (see FIG. 13(b)). Alternatively, if the MG cancellation was indicated, the UE may resume CSI measurements on the cancelled MG and assume that the CSI reference resources included in the MG interval are valid, regardless of whether the MG cancellation was indicated via RRC or DCI. Some implementations of this specification allow the UE to operate flexibly during an MG as needed, and utilize resources efficiently by skipping unnecessary measurements while maintaining the accuracy of the CSI measurements. In addition, the issue of validity of CSI reference resources due to MG cancellation can be addressed.

[0342] The implementations of this specification described above may be applied individually or in combination of two or more.

[0343] Some implementations of this specification can efficiently schedule XR services even during the MG period. Some implementations of this specification can improve UE resource availability and ensure the quality of delay-sensitive services. Some implementations of this specification can minimize scheduling constraints during the MG period, and XR can be applied to various wireless communication transmission / reception structures and services.

[0344] Figure 14 illustrates the MG-related operation flow of a UE according to some implementations of this specification.

[0345] A UE may perform operations according to some implementations of the present disclosure. The UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the UE may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0346] In the method of the UE, or in the UE, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations may include: receiving a radio resource configuration message including a measurement gap related setting (S1401), wherein the measurement gap related setting includes information about a period and an offset and information about a measurement gap time length; determining measurement gaps for neighboring cell measurement based on the measurement gap related setting; performing the neighboring cell measurement during the measurement gaps (S1403), wherein predetermined operations are not allowed during the measurement gaps; and omitting the neighboring cell measurement during the cancelled measurement gap based on receiving measurement gap cancellation information (S1405) (S1407). During the cancelled measurement gap, second predetermined operations excluding first predetermined operations among the predetermined operations may be allowed. The first predetermined operations may include channel state information (CSI) measurement.

[0347] In some implementations, the CSI measurement may be allowed based on the measurement gap cancellation information being received via downlink control information.

[0348] In some implementations, the method or the operations may include: determining that a CSI reference resource within the cancelled measurement gap is valid based on the measurement gap cancellation information being received via the downlink control information.

[0349] In some implementations, the method or the operations may include: determining that the CSI reference resource within the cancelled measurement gap is invalid based on the measurement gap cancellation information being received via a radio resource control signal.

[0350] In some implementations, the predetermined actions may include at least: transmitting a hybrid automatic repeat request (HARQ) feedback, a scheduling request (SR), or channel state information (CSI); reporting a sounding reference signal (SRS); transmitting on an uplink shared channel; monitoring a physical downlink control channel; or receiving on a downlink shared channel.

[0351] Figure 15 illustrates the MG-related operation flow of the BS according to some implementations of this specification.

[0352] A BS may perform operations according to some implementations of the present disclosure. The BS may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the BS may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0353] In the method of the BS, or the BS, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations may include: transmitting a radio resource control message including a measurement gap-related setting (S1501), wherein the measurement gap-related setting includes information about a period and an offset and information about a measurement gap time length; and receiving a report related to the measurement gap-related setting (S1503). The measurement report may be based on neighboring cell measurements performed during measurement gaps determined based on the measurement gap-related setting. The measurement report may not include measurement information related to a measurement gap canceled by measurement gap cancellation information. During the canceled measurement gap, second predetermined operations among the predetermined operations, excluding first predetermined operations, may be allowed. The first predetermined operations may include channel state information (CSI) measurement.

[0354] In some implementations, the CSI measurement may be permitted to the device based on the measurement gap cancellation information being transmitted via downlink control information.

[0355] In some implementations, the method or the operations may include: determining that a CSI reference resource within the cancelled measurement gap is valid based on the measurement gap cancellation information being transmitted via the downlink control information.

[0356] In some implementations, the method or the operations may include: determining that the CSI reference resource within the cancelled measurement gap is invalid based on the measurement gap cancellation information being transmitted via a radio resource control signal.

[0357] In some implementations, the predetermined actions may include at least: receiving a hybrid automatic repeat request (HARQ) feedback, a scheduling request (SR), or channel state information (CSI); receiving a sounding reference signal (SRS) report; receiving on an uplink shared channel; transmitting on a physical downlink control channel; or transmitting on a downlink shared channel.

[0358] As described above, the examples disclosed in this specification are provided to enable those skilled in the art to implement and practice the disclosure. While the examples have been described above with reference to the examples of this specification, those skilled in the art will appreciate that various modifications and variations may be made to the examples of this specification. Accordingly, this disclosure is not intended to be limited to the examples described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0359] Implementations of this specification can be used in wireless communication systems, BSs, UEs, and other equipment.

Claims

1. In the method using a device, Receive a radio resource configuration message including measurement gap related settings, wherein the measurement gap related settings include information about a periodicity and an offset and information about a measurement gap time length; Determine measurement gaps for neighboring cell measurements based on the above measurement gap related settings; During the above measurement gaps, the neighboring cell measurements are performed, and predetermined operations are not allowed during the above measurement gaps; Including omitting the neighboring cell measurement during the cancelled measurement gap based on the reception of the measurement gap cancellation information, During the above-mentioned cancelled measurement gap, the second predetermined actions, excluding the first predetermined actions among the above-mentioned predetermined actions, are allowed, The above first predetermined operations include measuring channel state information (CSI). method.

2. In paragraph 1, The above CSI measurement is allowed based on the measurement gap cancellation information being received through downlink control information. method.

3. In paragraph 2, Including determining that the CSI reference resource within the cancelled measurement gap is valid based on the measurement gap cancellation information being received through the downlink control information. method.

4. In paragraph 3, Including determining that the CSI reference resource within the cancelled measurement gap is invalid based on the measurement gap cancellation information being received via a radio resource control signal. method.

5. In paragraph 1, The above predetermined actions are at least: Performs transmission of hybrid automatic repeat request (HARQ) feedback, scheduling request (SR), or channel state information (CSI); Reporting the sounding reference signal (SRS); Transmission on the uplink shared channel; Physical downlink control channel monitoring; or Including receiving on a downlink shared channel, method.

6. At least one processor; and At least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Receive a radio resource configuration message including measurement gap related settings, wherein the measurement gap related settings include information about a periodicity and an offset and information about a measurement gap time length; Determine measurement gaps for neighboring cell measurements based on the above measurement gap related settings; During the above measurement gaps, neighbor cell measurements are performed, and predetermined operations are not allowed during the above measurement gaps; Including omitting the neighboring cell measurement during the cancelled measurement gap based on the reception of the measurement gap cancellation information, During the above-mentioned cancelled measurement gap, the second predetermined actions, excluding the first predetermined actions among the above-mentioned predetermined actions, are allowed, The above first predetermined operations include measuring channel state information (CSI). machinery and tools.

7. In a computer-readable non-transitory storage medium, The storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations, the operations comprising: Receive a radio resource control message including measurement gap related settings, wherein the measurement gap related settings include information about a periodicity and an offset and information about a measurement gap time length; Determine measurement gaps based on the above measurement gap related settings; During the above measurement gaps, neighbor cell measurements are performed, and predetermined operations are not allowed during the above measurement gaps; Including omitting the neighboring cell measurement during the cancelled measurement gap based on the reception of the measurement gap cancellation information, During the above-mentioned cancelled measurement gap, the second predetermined actions, excluding the first predetermined actions among the above-mentioned predetermined actions, are allowed, The above first predetermined operations include measuring channel state information (CSI). Storage media.

8. In the method by the base station, Transmitting a radio resource control message including measurement gap related settings, wherein the measurement gap related settings include information about a periodicity and an offset and information about a measurement gap time length; Including receiving a measurement report related to the above measurement gap related settings, The above measurement report includes measurement information based on neighbor cell measurements performed by the device during measurement gaps determined based on the above measurement gap related settings, The above measurement report does not include measurement information related to measurement gaps cancelled by measurement gap cancellation information. During the above measurement gaps, predetermined operations of the device are not permitted; During the above-mentioned cancelled measurement gap, the second predetermined actions, excluding the first predetermined actions among the above-mentioned predetermined actions, are allowed, The above first predetermined operations include measuring channel state information (CSI). method.

9. At least one transmitter / receiver; at least one processor; and At least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Transmitting a radio resource control message including measurement gap related settings, wherein the measurement gap related settings include information about a periodicity and an offset and information about a measurement gap time length; Including receiving a measurement report related to the above measurement gap related settings, The above measurement report includes measurement information based on neighbor cell measurements performed by the device during measurement gaps determined based on the above measurement gap related settings, The above measurement report does not include measurement information related to measurement gaps cancelled by measurement gap cancellation information. During the above measurement gaps, predetermined operations of the device are not permitted; During the above-mentioned cancelled measurement gap, the second predetermined actions, excluding the first predetermined actions among the above-mentioned predetermined actions, are allowed, The above first predetermined operations include measuring channel state information (CSI). Base station.

Images