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

Abstract

This UE may: receive a transmission occasion (TO)-related configuration for CSI reporting; determine a TO window including an unused TO from among multiple TOs of the TO-related configuration; and transmit CSI in a TO not included in the TO window.

Description

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

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

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

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

[0004] One technical objective of this specification is to provide methods and devices for the efficient use of uplink radio resources.

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

[0006] In one aspect of the present specification, a method by a user device (UE) is provided. In another aspect of the present specification, a UE is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In yet another aspect of the present specification, a processing device is provided comprising at least one processor; and at least one computer memory operably connected to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that cause the at least one processor to perform operations when executed. The method or the operations include: receiving a transmission occasion (TO) related setting for channel state information (CSI) reporting; Determining unused TOs or a TO window including unused TOs among multiple TOs in the above TO-related settings; and transmitting CSI from a TO that is not an unused TO or a TO not included in the above TO window.

[0007] In one aspect of the present specification, a method by means of a base station (BS) is provided. In another aspect of the present specification, a BS is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The method or the operations may include: transmitting a transmission occasion (TO) related setting for channel state information (CSI) reporting to a UE; determining unused TOs or a TO window including unused TOs among a plurality of TOs of the TO related setting; and receiving a CSI from the UE at a TO that is not an unused TO or a TO not included in the TO window.

[0008] In each aspect of this specification, the method or operation may include: omitting the CSI reporting or receiving the CSI in the TO of the TO-related setting included in the TO window.

[0009] In each aspect of the present specification, the method or operation may further include transmitting or receiving TO window information regarding the TO window.

[0010] In each aspect of the present specification, the TO window information may be transmitted from TO #n of the TO-related setting preceding the TO window.

[0011] In each aspect of the present specification, the TO window information may be transmitted or received through an uplink channel established for TO window reporting.

[0012] In each aspect of the present specification, the method or operation may further include performing a CSI prediction, and the TO window may be determined based on the CSI prediction.

[0013] In each aspect of the present specification, the method or operation may further include transmitting or receiving CSI #n at TO #n of the TO-related setting. Based on the fact that CSI #n and CSI #(n+k) of the TO-related setting satisfy a predetermined condition, the TO window may include CSI #(n+k), wherein CSI #(n+k) is a CSI to be transmitted or received at TO #(n+k).

[0014] In each aspect of the present specification related to the above UE, the method or operation may further include receiving a TO window setting from the BS, and the TO window may be determined based on the TO window setting.

[0015] In each aspect of the present specification related to the above UE, within the TO window, the CSI processing unit (CSI processing unit, CPU) associated with each TO of the above TO-related settings may not be occupied.

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

[0017] According to some implementations of this specification, methods and devices for the efficient use of uplink radio resources can be provided for one technical problem of this specification.

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

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

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

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

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

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

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

[0025] FIG. 6 illustrates a general functional architecture for an artificial intelligence (AI) / machine learning (ML) model;

[0026] FIG. 7 illustrates a communication procedure between a first node (e.g., user equipment (UE)) and a second node (e.g., base station (BS)) to which an AI / ML model is applied;

[0027] FIG. 8 illustrates the flow of a process related to channel state information (CSI);

[0028] FIG. 9 illustrates a two-sided model among A / ML models related to AI / ML model inference;

[0029] FIG. 10 illustrates a unilateral model among AI / ML models related to AI / ML model inference;

[0030] FIG. 11 illustrates an example of unused transmission occasion - uplink control information (UTO-UCI) transmission;

[0031] FIG. 12 illustrates non-use transmission time signaling according to some implementations of the present specification;

[0032] FIG. 13 illustrates a signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0084]

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

[0086]

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

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

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

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

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

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

[0093]

[0094] Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block (SSB)

[0095] In 3GPP-based systems, each SSB is associated with each beam. For example, during a half-frame, different SSBs may be transmitted in different spatial directions (using different beams that span the cell's coverage area). The possible time positions of SSBs within a half-frame are determined by the subcarriers, and the periododicity of the half-frames in which the SSBs are transmitted is set by the network. Multiple SSBs may be transmitted within the carrier frequency span. Different indices of SSBs transmitted / detected on a single cell may correspond to different BS (wide) Tx beams. Multiple SSBs may be transmitted within the carrier frequency span. The physical (layer) cell identifiers (PCIs) of SSBs transmitted at different frequency locations do not need to be unique, and different SSBs in the frequency domain may have different PCIs. When an SSB is associated with remaining minimum system information (RMSI), the SSB is referred to as a cell-defining SSB (CD-SSB), and the PCell is always associated with a CD-SSB located on a synchronization raster (sync raster).If an SSB is not associated with an RMSI, the said SSB is referred to as a non-cell defining SSB (NCD-SSB), which can be used to perform radio link monitoring (RLM), beam failure detection (BFD), and radio resource management (RRM) measurements, and measurements for random access resource selection within an active DL BWP if the active DL BWP does not include the said CD-SSB. In 3GPP-based systems, multi-beam operation is based on beam switching / beam scanning, which transmits / receives signals while changing the beam direction over time. Beam sweeping refers to the transmission and reception point (TRP) (e.g., BS / cell) changing the beam (direction) of the radio signal over time. In this specification, beam and beam direction may be used interchangeably. An SSB may be transmitted periodically using beam sweeping. In this case, the SSB index is implicitly linked to the SSB beam. The SSB beam can be changed by an SSB (index) unit or by an SSB (index) group unit. In the latter case, the SSB beam remains the same within the SSB (index) group. For example, a set of SSBs can be transmitted within a 5 ms half-frame. A set of SSBs transmitted within a 5 ms half-frame is called an SSB burst, and the entire set of bursts that repeat at a period set by the BS is called an SSB burst set. SSBs within an SSB burst can be transmitted in different beam directions. L. max is the maximum number of SSB indices within a cell, and the maximum number of SSBs transmitted within a half-frame is L. max is. The maximum number of SSB transmissions L within an SSB burst. maxhas a value of 4, 8, or 64 depending on the frequency band to which the carrier belongs. For example, L is the maximum number of SSBs in an SSB burst set. max It can be given as follows.

[0096] - For frequency range up to 3 GHz, L max = 4

[0097] - For frequency range from 3GHz to 6 GHz, L max = 8

[0098] - For frequency range from 6 GHz to 52.6 GHz, L max = 64

[0099] The actual number of transmitted SSBs can be configured, with a maximum number L max It can be smaller. If multi-beam transmission is not applied, the number of SSB beams is 1.

[0100] The UE can perform DL synchronization acquisition (e.g., OFDM symbol / slot / half-frame boundary detection), cell ID (Identifier) ​​acquisition (e.g., Physical Cell Identifier, PCID), beam alignment for initial connection, MIB acquisition, DL measurement, etc. based on the SSB. The UE can identify the frame number to which the detected SSB belongs using system frame number (SFN) information within the PBCH, and identify the half-frame number to which the detected SSB belongs using PBCH DMRS and / or half-frame indication information (hereinafter HF) within the PBCH. For example, if the UE detects a PBCH DMRS generated based on HF=0 or a PBCH containing HF=0, it can determine that the SSB to which the PBCH belongs belongs to the first half-frame within the frame, and if the UE detects a PBCH DMRS generated based on HF=1 or a PBCH containing HF=1, it can determine that the SSB to which the PBCH belongs belongs to the second half-frame within the frame.

[0101] Maximum L within SSB burst max SSBs may be transmitted, and the number / locations of the SSBs actually transmitted may vary depending on the BS / cell. The number / locations of the SSBs actually transmitted are used for rate-matching and measurement, and information regarding the SSBs actually transmitted (e.g., RRC setting ssb-PositionsInBurst) may be indicated as follows.

[0102] - In the case of rate-matching: This may be indicated via UE-specific RRC signaling or RMSI. UE-specific RRC signaling includes a full (e.g., length L) bitmap in both the below 6 GHz and above 6 GHz frequency ranges. On the other hand, the remaining minimum system information (RMSI) (i.e., SIB1) includes a full bitmap in the below 6 GHz range and a bitmap in a compressed form as described above 6 GHz. Specifically, information regarding the SSB actually transmitted may be indicated using a group-bitmap (8-bit) and an in-group bitmap (8-bit). Here, the resources indicated via UE-specific RRC signaling or RMSI (e.g., resource elements (REs)) are reserved for SSB transmission, and PDSCH / PUSCH, etc., may be rate-matched with respect to the SSB resources.

[0103] - In relation to measurement: When in RRC_CONNECTED mode, the network (e.g., BS) can specify the set of SSBs to be measured within the measurement interval. The set of SSBs can be specified by frequency layer. If no specification is given for the set of SSBs, the default set of SSBs is used. The default set of SSBs includes all SSBs within the measurement interval. The set of SSBs is the full of RRC signaling (e.g., length L max It can be specified using a bitmap. In RRC_IDLE mode, the default SSB set is used.

[0104] Physical Channels

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0129] Artificial Intelligence (AI) / Machine Learning (ML)

[0130] Artificial intelligence (AI) and machine learning (ML) technologies can be adopted as core implementation technologies for 6G systems.

[0131] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in machine-to-machine (M2M), machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in brain-computer interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0132] The following describes a functional framework for AI / ML operations.

[0133] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.

[0134] - Data collection: Data collected from network nodes, management entities, or UEs, etc., as a basis for AI model training, data analysis, and inference.

[0135] - AI Model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.

[0136] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.

[0137] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and AI models using trained AI models.

[0138] Life cycle management (LCM) procedures for AI / ML models (e.g., model training, model deployment, model inference, model monitoring, model updates, etc.) can be classified into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identified by the network, and the network can direct the activation, deactivation, fallback, or switching of AI / ML functionality. In model identifier (ID)-based LCM, AI / ML models can be identified by the network, and the network / UE can activate, deactivate, select, or switch AI / ML models via the model ID.

[0139] FIG. 6 illustrates a general functional architecture for an AI / ML model. In particular, FIG. 6 illustrates a general functional architecture relevant to both function-based LCMs and model-based LCMs. Some functions or some data / information / command flows (i.e., arrows) illustrated in FIG. 6 may be omitted.

[0140] Referring to FIG. 6, a general functional framework may be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).

[0141] The data collection function (10) is a function that provides input data to the model training function (20), management function (30), and inference function (40). The data collection function (10) performs data preparation based on raw data and can provide input data processed through data preparation. Examples of raw data may include received data / measurement data from UEs or other network entities, inference / output of AI / ML models, etc. The data collection function (10) may be performed by a single entity (e.g., UE, network node, etc.) but may also be performed by multiple entities.

[0142] Here, training data (11) refers to data required as input for the AI / ML model training function (20). monitoring data (12) refers to data required as input for the management (30) of the AI / ML model or AI / ML function. inference data (13) refers to data required as input for the AI / ML inference function (30).

[0143] The model training function (20) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of an AI / ML model testing procedure. If necessary, the model training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on training data (11) transmitted from the data collection function (10).

[0144] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).

[0145] The management function (30) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the management function (30) may make decisions to ensure appropriate inference operations based on data received from the data collection function (10) (e.g., monitoring data (12)) and / or data received from the inference function (40) (i.e., inference output (41)).

[0146] Management Instruction (32) is information required as input to manage the inference function (40). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).

[0147] A Model Transfer / Delivery Request (33) can be used to request the model(s) from the Model Storage Function (50).

[0148] Performance Feedback / Retraining Request (31) refers to information required as input to Model Training function (20) (e.g., for the purpose of retraining or updating the model).

[0149] The inference function (40) is a function that provides an output from the process of applying an AI / ML model or an AI / ML function using data (e.g., inference data (13)) provided by the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data preprocessing and cleaning, formatting and transformation) based on the inference data (13) provided by the data collection function (10).

[0150] Inference Output (41) is data used in the management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of an AI / ML model generated by the inference function (30), and the details of the inference output may vary depending on the use case.

[0151] The model storage function (50) is a function that stores a trained / updated model that can be used to perform the inference function (40). The model storage function (50) exemplified in FIG. 6 can be used as a reference point (if any) applicable to protocol termination, model transmission / delivery, and related processes. Additionally, the model storage function (50) is an example and is not intended to restrict the storage location of the actual AI / ML model and may be omitted.

[0152] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.

[0153] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of multiple levels or the separation of any one level are also possible.

[0154] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.

[0155] Cat 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.

[0156] Cat 1) Inter-node support is involved to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from other nodes (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0157] Cat 2) Collaborative AI / ML tasks can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0158] FIG. 6 is a diagram illustrating an overall functional framework for an AI / ML model, and all functions and / or all data / information / command signals illustrated in FIG. 6 may not be performed within a specific node, and only some may be performed.

[0159] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.

[0160] A unilateral model can refer to an AI / ML model where inference is performed entirely by a single node (e.g., a UE or a network). Here, the training of the AI / ML model can also be performed entirely by a single node. The training and inference of the AI / ML model may be performed by the same node, or they may be performed by different nodes.

[0161] A two-sided model may refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., UEs and networks). Joint inference means that inference is performed jointly across multiple nodes; for example, a first part of the inference may be performed by a first node, and the remainder of the inference may be performed by a second node. Depending on the training method of the AI / ML model, two-sided models can be classified into various types as follows.

[0162] - First type: An AI / ML model can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / entities.

[0163] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and UEs). Joint training can mean that model generation (e.g., CSI generation) and model reconstruction (CSI compression by sub-use case) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (e.g., model generation training and model reconstruction training performed simultaneously) and sequential training (e.g., model reconstruction training performed after model generation training).

[0164] - Third Type: Separate training of AI / ML models can be performed on multiple nodes (e.g., network and UE). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node executes the AI / ML model first and shares the training data with the second node, the second node can execute the AI / ML model using the shared training data. For example, training for the CSI generation part can be performed by the UE, while CSI reconstruction can be performed by the network.

[0165] FIG. 7 illustrates a communication procedure between a first node (e.g., UE) and a second node (e.g., BS) to which an AI / ML model is applied.

[0166] The operations described below may be explained / interpreted based on an AI / ML model as shown in Figure 7 below, even without separate mention (e.g., without explicit mention of being by / based on / for an AI / ML model). Additionally, unless specifically limited, the AI / ML model may correspond to a unilateral model in which inference is performed entirely by a single node or a bilateral model in which joint inference is performed by multiple nodes.

[0167] First signaling (S701): In the following description, the signaling (e.g., information / data / channel / signal, etc.) or set of signaling between a specific node (e.g., UE, network, etc.) and another node may be interpreted as the signaling or set of signaling of the first signaling (S701) used to perform operations based on an AI / ML model, even without separate mention. For example, it may correspond to training data for training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 6, or to inference data used for inference of the AI / ML model, or to feedback to the AI / ML model. If, in this specification, signaling between nodes is not required prior to operations based on an AI / ML model, the first signaling (S701) may be omitted. If a unidirectional model is used in this specification, the unidirectional / bidirectional signaling (set) in this specification may correspond to the signaling of the first signaling (S701). Additionally, when a bidirectional model is used in this specification, unidirectional / bidirectional signaling in this specification may correspond to the first signaling (S701), and repetitive signaling operation may also correspond to the first signaling (S701). For example, in AI / ML model-based beam management (BM), when a high-quality beam(s) are predicted (i.e., inferred) by a BS based on an AI / ML model, the BS may receive quality / intensity information for multiple beams from the UE. Additionally, when a high-quality beam(s) are predicted (i.e., inferred) by a UE based on an AI / ML model, the UE may receive multiple beams from the BS.

[0168] AI / ML Model-Based Operation (S702): In the description below, an operation (e.g., computation, selection, prediction, etc.) at a specific node (e.g., UE, network, etc.) or a joint operation (e.g., computation, selection, prediction, etc.) at multiple nodes (e.g., UE, network, etc.) may correspond to an AI / ML model-based operation (S702) based on one or more functions in the functional framework of the AI / ML model, even without separate mention. For example, it may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5 or to the inference of the AI / ML model. When a unilateral model is used, an operation performed by a single node in this specification may correspond to an AI / ML model-based operation (S702), and when a bilateral model is used, a joint operation performed by multiple nodes in this specification may correspond to an AI / ML model-based operation (S702).

[0169] For example, in an AI / ML model-based BM, the BS can use quality / intensity information for multiple beams received from the UE as inference data to predict (i.e., infer) high-quality beam(s) based on the AI / ML model. Additionally, the UE can measure multiple beams received from the BS and use the measurement results as inference data to predict (i.e., infer) high-quality beam(s) based on the AI / ML model.

[0170] Second signaling (S703): In the following description, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., UE, network, etc.) and another node may be interpreted as the second signaling (S703) or a set of signaling generated as a result of an operation based on an AI / ML model, even without separate mention. For example, it may correspond to the output resulting from the inference of the AI / ML model of FIG. 6. If signaling between nodes is not required as a result of an operation based on an AI / ML model in this specification, the second signaling (S703) may be omitted. If a unidirectional model is used in this specification, the unidirectional / bidirectional signaling (set) in this specification may correspond to the second signaling (S703). Additionally, if a two-way model is used in this specification, unidirectional / bidirectional signaling in this specification may correspond to the second signaling (S703), and a repetitive signaling operation may also correspond to the second signaling (S703).

[0171] For example, in an AI / ML model-based BM, the BS can transmit beam(s) predicted based on the AI / ML model as candidates to the UE so that the UE can determine the optimal beam. Additionally, the UE can report the beam(s) predicted based on the AI / ML model to the BS in order to request the BS to transmit candidate beams as candidates for determining the optimal beam.

[0172] <Reporting Channel State Information (CSI)>

[0173] CSI reporting is used for the UE to measure radio channel conditions and report them to the network. The time and frequency resources available to the UE for CSI reporting are controlled by the BS. In 3GPP-based systems, CSI may consist of the following indicators / reports: Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSSBRI), Layer Indicator (LI), Rank Indicator (RI), Layer-1 Reference Signal Received Power (L1-RSRP), or Layer-1 Signal to Interference and Noise Ratio (L1-SINR).

[0174] In 3GPP-based systems (e.g., NR), CSI-RS is used for time and / or frequency tracking, CSI computation, L1-RSRP computation, and mobility management. Here, CSI computation is related to CSI acquisition, and L1-RSRP computation is related to beam management (BM).

[0175] CSI is a collective term for information that can indicate the quality of the wireless channel (also called a link) formed between the UE and the antenna port(s).

[0176] FIG. 8 illustrates the flow of a process related to channel state information (CSI). Referring to FIG. 8, the UE can receive configuration information related to CSI from the BS via RRC signaling (S810). The configuration information related to CSI may include at least information related to CSI interference management (CSI-IM) resources, information related to CSI measurement configuration, information related to CSI resource configuration, information related to CSI-RS resources, or information related to CSI report configuration.

[0177] Information related to CSI resource configuration can be expressed as CSI-ResourceConfig IE. Information related to CSI resource configuration defines a group including at least a non-zero power (NZP) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the information related to CSI resource configuration includes a list of CSI-RS resource sets, and the list of CSI-RS resource sets may include at least an NZP CSI-RS resource set list, a CSI-IM resource set list, or a CSI-SSB resource set list. A CSI-RS resource set is identified by a CSI-RS resource set ID, and a CSI-RS resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID.

[0178] As shown in the following table, which is an example of NZP-CSI-RS-ResourceSet IE, parameters indicating the use of CSI-RS (e.g., BM-related 'repetition' parameter, tracking-related 'trs-Info' parameter) can be set for each NZP CSI-RS resource set.

[0179]

[0180] Here, the repetition parameter corresponding to the upper layer parameter corresponds to the L1 parameter 'CSI-RS-ResourceRep'.

[0181] The following table is part of the NZP-CSI-RS-Resource IE defined in 3GPP TS 38.331.

[0182]

[0183] Information regarding CSI reporting settings includes a reportConfigType parameter representing time domain behavior and a reportQuantity parameter representing the CSI-related quantity to be reported. The time domain behavior may be periodic, non-periodic, or semi-continuous.

[0184] Information related to CSI report configuration can be expressed as CSI-ReportConfig IE (see CSI-ReportConfig IE in 3GPP TS 38.331).

[0185] Additionally, the following table is an example of CSI-ResourceConfigIE, where CSI-ResourceConfigIE defines one or more groups of NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet, and / or CSI-SSB-ResourceSet.

[0186]

[0187] The UE performs CSI measurement based on configuration information related to CSI (S820).

[0188] The above CSI measurement may include (1) a process of receiving CSI-RS of the UE (S821) and (2) a process of performing CSI computation through the received CSI-RS (S822).

[0189] In CSI-RS, the mapping of resource elements (REs) of CSI-RS resources in the time and frequency domains is established by the upper-level parameter CSI-RS-ResourceMapping. The following table illustrates CSI-RS-ResourceMappingIE.

[0190]

[0191] In the table above, density represents the density of CSI-RS resources measured at RE / Port / PRB, and nrofPorts represents the number of antenna ports.

[0192] The UE can transmit a CSI report based on the calculated CSI (S730). Here, if the parameter quantity of CSI-ReportConfig is set to 'none (or No report)', the UE may omit the transmission of the CSI report. However, even if the parameter quantity is set to 'none (or No report)', the UE may still transmit the CSI report to the BS. The case where the parameter quantity is set to 'none' is when a non-periodic tracking reference signal (TRS) is triggered or when repetition is set. Here, the transmission of the CSI report may be omitted only when repetition is set to 'ON' (see Table 4).

[0193] CSI measurement

[0194] 3GPP-based systems (e.g., NR systems) support more flexible and dynamic CSI measurement and CSI reporting. Here, the CSI measurement may include a process in which a UE receives CSI-RS and obtains CSI by performing CSI calculation based on the received CSI-RS.

[0195] As time domain behaviors for CSI measurement and CSI reporting, non-periodic / quasi-continuous / periodic channel measurement (CM) and interference measurement (IM) are supported. A 4-port NZP CSI-RS resource element (RE) pattern can be used for setting up CSI-IM.

[0196] BS can transmit precoded NZP CSI-RS to the UE on each port of the configured NZP CSI-RS-based IM resource (IM resource, IMR).

[0197] The UE can assume channel / interference layers for each port in the CSI-RS resource set and perform interference measurements.

[0198] A set of multiple CSI-RS resources may be configured, and the BS or network may indicate a set of NZP CSI-RS resources for channel / interference measurements via the DCI.

[0199] resource setting

[0200] Each CSI resource set 'CSI-ResourceConfig' includes a configuration of a list of S ≥ 1 CSI resource sets (given by the upper layer parameter csi-RS-ResourceSetList), said list consisting of references to one or both of non-zero power (NZP) CS-RS resource set(s) and SS / PBCL block set(s), or said list consisting of references to CSI interference measurement (CSI-IM) resource set(s). The configuration for S ≥ 1 CSI resource sets includes each CSI resource set containing CSI-RS resources (configured as NZP CSI-RS or CSI-IM) and SS / PBCH block (SSB) resources used in L1-RSRP calculation.

[0201] The time domain behavior of CSI-RS resource(s) within the CSI resource settings included in CSI-ResourceConfig IE is dictated by the upper-level parameter resourceType and can be set to non-periodic, periodic, or semi-continuous. For periodic and semi-continuous CSI resource settings, the number of configured CSI-RS resource sets S is limited to '1'. For periodic and semi-continuous CSI resource settings, the configured periodicity and slot offset are determined based on the numeral of the associated DL BWP (e.g., subcarrier interval) given by bwp-id.

[0202] When a UE is configured with multiple CSI-ResourceConfigs containing the same NZP CSI-RS resource ID, the same time domain behavior is configured for the CSI-ResourceConfigs.

[0203] When a UE is configured with multiple CSI-ResourceConfigs containing the same CSI-IM resource ID, the same time domain behavior is configured for the CSI-ResourceConfigs.

[0204] resource setting configuration

[0205] As previously mentioned, CSI resource settings can be provided by a list of CSI resource sets. For non-periodic CSI, each trigger state configured using the upper-level parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, each of which is linked to a periodic, semi-continuous, or non-periodic resource setting. A single report setting can be associated with up to three resource settings.

[0206] CSI computation

[0207] When interference measurements are performed on CSI-IM, each CSI-RS resource for channel measurement is associated resource-wise with a CSI-IM resource within corresponding resource sets in the order of that CSI-RS resource and CSI-IM resource. The number of CSI-RS resources for channel measurement is equal to the number of CSI-IM resources. For CSI measurements, the UE assumes the following.

[0208] Each NZP CSI-RS port configured for interference measurement corresponds to the interference transport layer.

[0209] - All interference transmission layers on NZP CSI-RS ports for interference measurement consider the associated energy per resource element (EPRE) ratios.

[0210] - Other interference signals on resource elements of an NZP CSI-RS resource for channel measurement, an NZP CSI-RS resource for interference measurement, or a CSI-IM resource for interference measurement.

[0211] For L1-SINR with dedicated interference measurement resources, the UE assumes the following:

[0212] - The total received power on the dedicated NZP CSI-RS resource for interference measurement or the dedicated CSI-IM resource for interference measurement corresponds to interference and noise.

[0213] CSI Report

[0214] For CSI reporting, the time and frequency resources available to the UE are controlled by the BS.

[0215] CSI may include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSSBRI), a layer indicator (LI), a rank indicator (RI), or an L1-RSRP.

[0216] For CQI, PMI, CRI, SSBRI, LI, RI, and L1-RSRP, the UE is configured by N≥1 CSI-ReportConfig reporting settings, M≥1 CSI-ResourceConfig resource settings, and a list of one or two trigger states (e.g., upper-level parameters aperiodicTriggerStateList and semiPersistentOnPUSCH-TriggerStateList). In the aperiodicTriggerStateList, each trigger state includes an associated list of CSI-ReportConfigs indicating the channel and optionally resource set IDs for interference. In the semiPersistentOnPUSCH-TriggerStateList, each trigger state includes one associated CSI-ReportConfig.

[0217] In addition, the time domain behavior of CSI reporting supports periodic, semi-continuous, and non-periodic.

[0218] i) Periodic CSI reporting is performed on short PUCCH and long PUCCH. The periododicity and slot offset of periodic CSI reporting can be set to RRC, and refer to CSI-ReportConfigIE.

[0219] ii) Semi-persistent (SP) CSI reporting is performed on a short PUCCH, a long PUCCH, or a PUSCH. When SP CSI is performed on a short / long PUCCH, the periododicity and slot offset are set to RRC, and activation / deactivation of CSI reporting is performed by a separate MAC control element (CE). When SP CSI is performed on a PUSCH, the periododicity of SP CSI reporting is set to RRC, but the slot offset is not set to RRC, and SP CSI reporting is activated / deactivated by a DCI (e.g., DCI format 0_1). For SP CSI reporting on a PUSCH, a separate RNTI (e.g., SP-CSI C-RNTI) may be used. The initial CSI reporting timing follows the PUSCH time domain allocation value specified in the DCI, and subsequent CSI reporting timing follows the period set by the RRC. DCI format 0_1 ​​includes a CSI request field and can enable / disable a specific configured SP-CSI trigger state. SP CSI reporting can be enabled / disabled in the same or similar manner as the mechanism with data transmission on the SPS PUSCH.

[0220] iii) Aperiodic (AP) CSI reporting is performed on PUSCH and can be triggered by DCI. In this case, information related to the trigger of aperiodic CSI reporting can be transmitted / instructed / set via MAC CE. For AP CSI with AP CSI-RS, AP CSI-RS timing is set by RRC, and timing for AP CSI reporting can be dynamically controlled by DCI.

[0221] NR does not apply the method of splitting CSIs across multiple reporting instances (e.g., transmitting in the order of RI, WB PMI / CQI, SB PMI / CQI) that was applied to PUCCH-based CSI reporting in LTE. Instead, NR restricts the setting of specific CSI reports in short / long PUCCHs, and CSI omission rules are defined. Regarding AP CSI reporting timing, the PUSCH symbol / slot position is dynamically indicated by the DCI. Candidate slot offsets can be set by the RRC. For CSI reporting, the slot offset Y can be set per reporting setting. For UL-SCH, the slot offset K2 can be set separately.

[0222] Two CSI latency classes (e.g., low latency class, high latency class) can be defined in terms of CSI computational complexity. Low latency CSI is a wideband (WB) CSI that includes up to 4-port Type-I codebooks or up to 4-port non-PMI feedback CSIs. High latency CSI refers to any CSI other than low latency CSI. For a normal UE, (Z, Z') is defined in units of OFDM symbols. Here, Z represents the minimum CSI processing time from receiving a non-periodic CSI-triggering DCI until performing a CSI report. Additionally, Z' represents the minimum CSI processing time from receiving a CSI-RS for a channel / measurement until performing a CSI report.

[0223] Additionally, the UE can report the number of CSIs that can be computed simultaneously.

[0224] The UE calculates the CSI parameters (if reported) by assuming the following dependencies between the CSI parameters (if reported).

[0225] - LI is calculated based on the reported CQI, PMI, RI, and CRI.

[0226] - CQI is calculated based on the reported PMI, RI, and CRI.

[0227] - PMI is calculated based on reported RI and CRI.

[0228] - RI is calculated based on the reported CRI.

[0229] Reporting settings for CSI may be non-periodic (using PUSCH), periodic (using PUCH), or semi-continuous (using PUCH and DCI-enabled PUCH). CSI-RS resources may be periodic, semi-continuous, or non-periodic. Semi-continuous CSI-RS may be enabled and disabled as described in Section 5.2.1.5.2 of 3GPP TS 38.214, and non-periodic CSI-RS may be enabled and triggered / enabled as described in Section 5.2.1.5.1 of 3GPP TS 38.214. The following table, illustrating triggering / enablement for possible CSI-RS settings, shows supported combinations of CSI reporting settings and CSI-RS resource settings, and how said CSI reporting is triggered for each CSI-RS resource setting.

[0230]

[0231] Referring to 3GPP TS 38.321, the network can select the CSI reporting state(s) to be reported from among the aperiodic CSI trigger states of a serving cell configured in aperiodiTriggerStateList, which includes trigger states for dynamically selecting one or more aperiodic and semi-continuous reporting settings and / or for triggering one or more sets of aperiodic CSI-RS resources for channel and / or interference measurements, by sending an Aperiodic CSI Trigger State Subselection MAC CE.

[0232] <AI / ML 기반의 CSI 보고>

[0233] FIG. 9 illustrates a two-way model among AI / ML models related to AI / ML model inference. Referring to FIG. 9, the UE is equipped with an AI encoder and the BS is equipped with an AI decoder, and the UE and the BS can perform AI / ML model inference. An AI / ML model that performs AI / ML model inference at two nodes in this manner is called a two-way model. In this specification, "two-way AI / ML" means that an AI / ML model is deployed / configured on the UE and the network (e.g., BS), respectively, and performs inference on each. For example, an AI / ML model such as an auto-encoder may be configured for CSI reporting, and the UE side (e.g., CSI encoder side) calculates an AI / ML model inference output by using channel information (e.g., channel matrix / channel covariance matrix / channel eigenvector) as input, or by using information that has undergone pre-processing as input, and feeds this output information to the BS after or without specific pre-processing, and the BS (e.g., CSI decoder) calculates an inference output by using the feedback information, after or without pre-processing, as an input to the AI / ML model, and performs CSI decoding to obtain the final CSI by performing pre-processing on the inference output or without pre-processing.

[0234] FIG. 10 illustrates a unilateral model among AI / ML models related to AI / ML model inference. Among AI / ML models for AI / ML-based CSI reporting, there may be UE-side models. In particular, FIG. 10 illustrates a CSI prediction method based on a UE-side model. Referring to FIG. 10, an AI / ML model is deployed / configured only on the UE side, so that the AI / ML model deployed / configured on the UE side can perform model inference. The above MI / ML model uses multiple historical measurements (e.g., t -x By applying CSI measurement results during the time interval from t0 to t0 as AI / ML input, AI / ML-based channel estimation can be performed to estimate a single or multiple (e.g., K+1) future CSIs as the AI / ML model output.

[0235] FIG. 11 illustrates an example of unused transmission occasion - uplink control information (UTO-UCI) transmission. In FIG. 11, "TO" indicates the transmission occasion.

[0236] In Rel-18 XR, the transmission of unused transmission occasion-uplink control information (UTO-UCI) via CG-PUSCH was introduced. Referring to Section 9.3.1 of Release 18 of 3GPP TS 38.213, within the configuredGrantConfig of the configured grant-PUSCH (CG-PUSCH) configuration configured by the UE, O UTO-UCI If nrofBitsInUTO-UCI having the same value as is provided, the UE within each CG-PUSCH transmission for the CG-PUSCH setup O UTO-UCIMultiplexes the UTO-UCI represented by a bitmap of bits. The above O of the UTO-UCI UTO-UCI Dog beats O of the above CG-PUSCH settings in ascending order of start time UTO-UCI It is mapped one-to-one to subsequent CG-PUSCH transmission occasions (TO). In the case of unpaired spectrum (e.g., TDD) operation, the above O UTO-UCI Subsequent CG-PUSCH TOs exclude invalid TOs in which the UE does not transmit the PUSCH because it conflicts with the DL symbol(s) indicated by tdd-UL-DL-ConfigurationCommon or provided by tdd-UL-DL-ConfigurationDedicated, or the symbol(s) of an SS / PBCH block having an index provided by ssb-PositionsInBurst. Here, tdd-UL-DL-ConfigurationCommon is an RRC parameter containing the information element (IE) TDD-UL-DL-ConfigCommon, which determines the cell-specific uplink / downlink time division duplex (TDD) configuration; tdd-UL-DL-ConfigurationDedicated is an RRC parameter containing the IETDD-UL-DL-ConfigDedicated, which determines the UE-specific uplink / downlink TDD configuration; and ssb-PositionsInBurst is an RRC parameter regarding the time domain positions of SSBs transmitted within an SS burst.

[0237] A bit value of '0' in the UTO-UCI indicates that the UE may transmit a CG-PUSCH at the corresponding CG-PUSCH TO, and a bit value of '1' in the UTO-UCI indicates that the UE will not transmit a CG-PUSCH at the corresponding CG-PUSCH TO. If the UE indicates a value of '1' for the CG-PUSCH TO by the UTO-UCI, the UE continues to indicate a value of '1' for the CG-PUSCH TO by the UTO-UCI that is multiplexed for subsequent CG-PUSCH transmissions, and the UE does not transmit a CG-PUSCH at the CG-PUSCH TO.

[0238] To summarize, O UTO-UCI If denoted as N, the UE can signal via a bitmap in the UTO-UCI whether N future (valid) CG-PUSCH TOs are (un)used. The BS can achieve the UL capacity enhancement effect by scheduling the CG-PUSCH TOs that the UE has signaled as unused to other UEs. When N = 3, referring to Fig. 11, unused or used information for TO#A(n+1), TO#A(n+2), and TO#A(n+3) at time TO#An can be loaded onto the CG-PUSCH as the UTO-UCI. For each TO, 'O' indicates that the UE is transmitting a CG-PUSCH at that TO, and 'X' indicates that the UE is not transmitting a CG-PUSCH at that TO. By transmitting '001' in TO#A1, the UE can inform the BS that CG-PUSCH transmission via TO#A4 will not be performed, and based on this information, the BS can schedule TO#A4 for uplink transmission of another UE, thereby gaining the advantage of improved system yield.

[0239] When periodic or semi-persistent PUCCH (or PUSCH) resources are set / assigned to a UE for CSI reporting, the UE performs CSI reporting on each set / assigned PUCCH (or PUSCH) resource, and the BS attempts to receive UCI containing CSI reporting on each PUCCH (or PUSCH) resource set / assigned by the BS. Once uplink resources for CSI reporting are set / assigned, the UE may transmit CSI reporting on those uplink resources until the uplink resources are deactivated or released, so the BS cannot use those uplink resources for uplink reception from the UE or other UEs.

[0240] Meanwhile, the introduction of UE-initiated or event-driven beam management is being considered. In this case, when an event occurs, the UE notifies the BS via a scheduling request (SR) resource and subsequently reports the beam quality to the BS via CG-PUSCH or DG-PUSCH. However, the BS, which does not know the timing of the UE's event, faces the problem of having to keep SR resources ready indefinitely.

[0241] As previously explained, the introduction of AI / ML enables prediction of future CSIs based on historical CSIs. By utilizing such CSI predictions, it is possible to predict in advance that the CSI value will remain constant for a certain period following a specific point in time when a UE transmits a CSI. Even in this case, transmitting or receiving CSI reports at every configured / reported CSI reporting time may be unnecessary or, furthermore, inefficient. Therefore, in some implementations of this specification, the BS may be notified that the UE will not transmit a CSI during that time period (e.g., non-use of uplink resources allocated / configured for CSI reporting). If the BS is aware of the time period during which the UE will not perform CSI reporting, despite having uplink resources available for CSI reporting, the BS can efficiently utilize resources by allocating the uplink resources during that time period to the UE or another UE. Additionally, the UE that has not transmitted a CSI for a certain period can benefit from reduced power consumption. Therefore, some implementations of this specification in which the UE notifies the BS of whether uplink resources for CSI reporting will be unused during a future time interval based on CSI prediction are described in more detail below.

[0242] In this specification, TO for CSI reporting may mean TO set / directed from BS for CSI reporting via (periodic or semi-persistent) PUCCH (or PUSCH). In some implementations, TO(s) for CSI reporting may mean TO(s) that have been assigned / set as TO for CSI reporting but are not used for transmission due to at least one of the following reasons.

[0243] A CSI PUCCH or PUSCH that overlaps with a signal / channel for time / frequency synchronization acquisition, such as an SS / PBCH block (and / or control resource set (CORESET) #0), in the time and / or frequency axis domain (e.g., a PUCCH / PUSCH that conflicts with the symbol(s) of an SS / PBCH block with an index provided by ssb-PositionsInBurst).

[0244] PUCCH / PUSCH that overlaps in the time and / or frequency axis domains with regions signaled as semi-static DL, such as RRC signaling (e.g., PUCCH / PUSCH that conflicts with DL symbol(s) indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if provided)

[0245] A PUCCH / PUSCH configured as an inactive period of Cell discontinuous reception (DRX) or overlapping with a non-active period in the time and / or frequency domain. Cell DRX may be a network energy saving (NES) feature to reduce the uplink reception active period of a BS, and the BS may provide a Cell DRX configuration containing information on the periodic pattern of active and non-active periods for the cell, and enable or deactivate the Cell DRX configuration via RRC signaling or layer 1 (L1) signaling (e.g., DCI). Certain uplink transmissions are restricted during the non-active period of an enabled Cell DRX.

[0246] In this specification, various CSIs are referred to as CSI reports for convenience, but a CSI may include at least one of the following components.

[0247] Rank indicator (RI)

[0248] Layer indicator (LI)

[0249] Precoding Matrix Indicator (PMI)

[0250] Channel Quality Indicator (CQI)

[0251] (L1-) Reference signal received power (RSRP) / Reference signal received quality (RSRQ) / Received signal strength indicator (RSSI) / Signal to interference plus noise ratio (SINR)

[0252] Here, RSRP may refer to a value measured by the UE based on the received signal strength of signals such as SSB or CSI-RS. RSSI may refer to the signal strength, including noise, received by the UE through a specific time / frequency resource. RSRQ may refer to the ratio between RSRP and RSSI.

[0253] * Method #1) Signaling method for non-use of PUCCH / PUSCH resources for CSI reporting purposes

[0254] To signal the non-use of PUCCH / PUSCH resource(s) configured / directed for CSI reporting, similar to the previously described UTO-UCI, in some implementations of this specification, a bitmap may be transmitted at each TO for CSI reporting (hereinafter, TO refers to a TO for CSI reporting). In this case, each bit of the bitmap may correspond to one of the future TOs. For each bit of the bitmap, a bit value of '1' may indicate that the corresponding TO is non-use, and a bit value of '0' may indicate that the corresponding TO is available for use. While this method has the advantage of indicating non-use for each TO, it may not adequately serve the purpose of indicating the non-use of PUCCH / PUSCH resources for CSI reporting due to the CSI remaining the same for a certain period. This is because, when non-use regarding TOs for CSI reporting needs to be indicated, the number of non-use TOs varies depending on how long the channel state remains at a similar level. If the non-use status of TOs for CSI reporting is signaled in a manner similar to conventional UTO-UCI, once a bitmap length is set, a bitmap of that set length must be used. Since a bitmap of the same length is used even if the number of non-use TOs is much shorter or longer than the bitmap length, this can result in significant overhead in signaling non-use TOs depending on the situation.

[0255] FIG. 12 illustrates signaling of non-use transmission times according to some implementations of the present specification. In FIG. 12, Window #An represents non-use transmission time information transmitted from TO #An. Referring to FIG. 12, if PUCCH / PUSCH resources for CSI reporting are periodically allocated / configured, the UE can signal the non-use status of future TO(s) at each TO (or some TOs). For example, the UE can signal that PUCCH / PUSCH resource(s) for CSI reporting are non-use up to TO#A7 by signaling Window #A3 at TO#A3, and signal that PUCCH / PUSCH resource(s) for CSI reporting are non-use up to TO#A11 by signaling Window #A8 at TO#A8. Additionally, the UE can omit CSI reporting for the four TOs in Window #A3 and the three TOs in Window #A8. The background of this signaling may imply that the UE determined, based on its CSI prediction, that there is no difference between the CSI reported in TO#A3 and the CSI during the Window #A3 time period (or between the CSI reported in TO#A8 and the CSI during the Window #A8 time period), or that even if there is, the difference is insignificant. The criteria for such a judgment are explained in detail in Method #2 below.

[0256] In some implementations of this specification, the window period during which the UE skips reporting CSI may be signaled through one (or a combination of two or more) of the following methods.

[0257] The window interval may refer to a time interval of K symbols / slots / subframes / frames / msec from the reference time thereafter, and a code-point corresponding to the value of K may be reported by the UE. Here, the reference time may be the start or end symbol of the TO where the said K value is signaled, or the starting / ending boundary of the slot / subframe / frame containing said TO. For example, if the said signaling consists of 3 bits and K is the number of slots, K = 0 / 1 / 2 / 3 / 4 / 5 / 6 / 7 may respectively be linked to code-points 000 / 001 / 010 / 011 / 100 / 101 / 110 / 111. For example, if TO is set to every slot period in FIG. 12, the UE may signal '000' in TO#A1 and TO#A2 (or omit signaling) to indicate that there are no unused TOs, signal '100' in TO#A3 to indicate that TOs will be unused for the 4 slots after TO#A3, and signal '011' in TO#A8 to indicate that TOs will be unused for the 3 slots after TO#A8. The mapping relationship between the K value and the code-point may be predefined or set for the UE(s) by BS.

[0258] The window interval may refer to M TOs following the corresponding TO in which information regarding the window interval is signaled, and a code-point corresponding to the value of M may be reported by the UE. For example, if the signaling consists of 3 bits, M = 0 / 1 / 2 / 3 / 4 / 5 / 6 / 7 may be respectively linked to the code-points 000 / 001 / 010 / 011 / 100 / 101 / 110 / 111. For example, referring to FIG. 12, the UE may signal '000' in TO#A1 and TO#A2 (or omit signaling) to indicate that there are no unused TOs, signal '100' in TO#A3 to indicate that 4 TOs following TO#A3 are unused, and signal '011' in TO#A8 to indicate that 3 TOs following TO#A8 are unused. The mapping relationship between M values ​​and code-points can be predefined or set for the UE(s) by BS.

[0259] While the aforementioned window-related signaling (e.g., K or M values) may be transmitted via the PUSCH / PUCCH configured / assigned for CSI reporting, in some implementations, given that the signaling overhead of the K or M values ​​is not significant, they may also be transmitted via a separate uplink signal / channel (capable of carrying short information) such as a separately configured / assigned PUSCH / PUCCH (or sequence (e.g., Zadoff-Chu sequence, constant amplitude zero autocorrelation (CAZAC) sequence, computer-generated sequence)). This separate uplink signal / channel may be configured with a period longer than that of the PUSCH / PUCCH configured / assigned for CSI reporting.

[0260] After transmitting window-related signaling (or signaling regarding resource non-use for CSI PUSCH / PUCCH) via the PUSCH / PUCCH configured / assigned for CSI reporting or a separate uplink signal / channel, an ACK or confirmation may be transmitted from the BS. Such ACK / confirmation may be transmitted in the form of a PDCCH or as a sequence in the form of CSI-RS / DM-RS. In some implementations, the UE may skip CSI transmission during the TO belonging to the window only if it receives such ACK / confirmation after transmitting the window-related signaling (or signaling regarding resource non-use for CSI PUSCH / PUCCH); if it does not receive such ACK / confirmation, it may perform transmission as usual without skipping CSI transmission.

[0261] In some implementations, window-related signaling (e.g., K or M values) may be instructed / set by the BS to the UE. This may be the case where CSI prediction is performed using a BS-sided model (or a two-sided model). Such window-related signaling may be instructed / set to the UE via downlink signals / channels such as a DCI that schedules the transmission of DL / UL data, or a group-common DCI or MAC control element (CE) and / or RRC (introduced for window-related signaling). For example, a UE that receives signaling for window #A3 via a DCI / MAC-CE before / after TO#A3 (or a UE that sends a HARQ-ACK corresponding to that DCI / MAC-CE) may skip reporting CSI during the TO(s) belonging to window #A3.

[0262] In some implementations, it is possible to apply a combination of the aforementioned BS-based and UE-based methods for window-related signaling. For example, as shown in FIG. 12, the UE may signal Window #A3 at TO#A3, but the BS may set / instruct the UE to only Window #A3', which includes only TO#A4. Upon receiving the signaling for Window #A3' from the BS, the UE may omit CSI reporting only at TO#A4 and perform CSI reporting at TO#A5. Conversely, although the BS instructed the UE to omit CSI reporting during Window #A3, the UE may decide to signal Window #A3' and perform the action of omitting CSI reporting only at that Window #A3'. In this way, if the non-use of TO is determined based on a two-way handshake, a more accurate CSI prediction-based CSI omission action can be performed.

[0263] * Method #2) How to determine if a UE can skip CSI reporting for one or more TOs

[0264] In some implementations of the present specification, if at least one of the following conditions is satisfied between CSI_n to be transmitted to TO#n and CSI_(n+k) to be transmitted to TO#(n+k), the UE may determine that it is permissible to transmit CSI_n only at TO#n and omit the transmission of CSI_n+k at TO#n+k.

[0265] If the RI value included in CSI_n and the RI value to be included in CSI_n+k are the same, or the difference between those values ​​is less than or equal to X1;

[0266] If the CQI value included in CSI_n and the CQI value to be included in CSI_n+k are the same, or the difference between them is less than or equal to X2;

[0267] If the (wideband (WB)) PMI value included in CSI_n and the (WB) PMI value included in CSI_n+k are equal, or if the difference between them is less than or equal to X3;

[0268] If the (L1-)RSRP value included in CSI_n and the (L1-)RSRP value included in CSI_n+k are the same, or the difference between them is less than or equal to X4;

[0269] If the (L1-)RSRQ value included in CSI_n and the (L1-)RSRQ value included in CSI_n+k are the same, or the difference between them is less than or equal to X5;

[0270] If the (L1-)RSSI value included in CSI_n and the (L1-)RSSI value included in CSI_n+k are equal, or the difference between them is less than or equal to X6;

[0271] If the (L1-)SINR value included in CSI_n is the same as the (L1-)SINR value included in CSI_n+k, or if the difference between those values ​​is less than or equal to X7;

[0272] If the difference between each component of the channel matrix H_n measured during CSI_n calculation and the channel matrix H_n+k predicted for CSI_n+k calculation (or its magnitude / absolute value or the mean / variance of its magnitudes / absolute values) is less than or equal to X8; or

[0273] If the criteria (e.g., accuracy, confidence, etc.) for the CSI_n+k predicted at time TO#n are greater than or equal to X9

[0274] The X1 / X2 / X3 / X4 / X5 / X6 / X7 / X8 / X9 value(s) may be predefined or value(s) set by BS. In some implementations, BS may set whether the UE can determine that it is acceptable to omit the CSI_n+k transmission in TO#(n+k) when any of the above conditions(s) are satisfied.

[0275] * Method #3) UE / BS operation details related to CSI PUSCH / PUCCH TO non-use

[0276] When the aforementioned window-related signaling (e.g., K or M value) is transmitted via a PUSCH / PUCCH set / assigned for CSI reporting, in some implementations, the UE may apply the following transmission technique to increase the probability that the signaling is successfully received by the BS.

[0277] When a CSI consists of two or more parts, window-related signaling can be jointly encoded with the information in CSI Part 1. This is because CSI Part 1 contains relatively important information.

[0278] Alternatively, window-related signaling may be encoded separately from CSI. In this case, in some implementations, a code rate separate from CSI (e.g., the beta offset value of 3GPP TS 38.213) may be applied to window-related signaling. For example, transmission reliability can be improved by applying a code rate lower than the CSI code rate to window-related signaling.

[0279] Alternatively, window-related signaling can be jointly encoded with HARQ-ACK information (in the case where HARQ-ACK is multiplexed).

[0280] If a PUSCH / PUCCH resource configured / assigned for CSI reporting is a semi-persistent (SP) resource, for example, if the activation of such resource is configured / directed via RRC signaling or DCI, in some implementations of this specification, the UE may request the release of such SP resource (via such PUSCH / PUCCH resource or a separate uplink signal / channel). This may occur when the UE determines, based on CSI forecasting, that the CSI has not changed for a significant period, and the UE may omit CSI reporting via such PUSCH / PUCCH resource until it is reactivated after the release request.

[0281] After the UE transmits the aforementioned window-related signaling (e.g., K or M values), CSI measurement can continue to be performed during the window period even if the UE omits reporting CSI during the window. For example, referring to FIG. 12, the UE can continue to perform CSI measurement even if it omits reporting CSI at TO#A4, TO#A5, TO#A6, and TO#A7, which belong to window #A3. This may be done to determine the error between the predicted CSI and the actual measured CSI at time TO#3 and to update the AI / ML model (or related parameter(s), etc.). Additionally, whether to continue performing CSI measurements during the window period signaled by the UE (or while skipping CSI reporting) may be set / instructed in advance by the BS, determined by whether criteria for the UE's AI / ML operation are met (for example, if the accuracy of AI / ML-based CSI prediction based on the UE history is above a threshold, CSI measurements are skipped during that window, otherwise CSI measurements are continued), or determined by the UE implementation.

[0282] In some implementations, it is also possible to omit the reception of CSI-RS or the transmission of a sounding reference signal (SRS) corresponding to a TO where the UE can omit reporting CSI. Assuming that the CSI can be constant during the interval of one or more TO(s), additional energy consumption savings of the BS / UE can be achieved by omitting the transmission of CSI-RS of the coupled BS and / or the transmission of SRS of the UE.

[0283] If the UE omits CSI measurement for the TO associated with the window after transmitting the aforementioned window-related signaling (e.g., K or M values), the following additional UE behavior may be considered.

[0284] The UE may release CPU occupancy for CSI report(s) associated with CSI reporting. A CSI processing unit (CPU) refers to a unit required by the UE to simultaneously process / update CSI reports at a given time, and the maximum number of CPUs per carrier or for all carrier(s) may be determined based on the UE's reporting capability. For example, the number of CPUs occupied for CSI reporting may be determined in accordance with clause 5.2.1.6 of Document 3GPP TS 38.214. The UE N CPU If simultaneous CSI calculations are supported, the UE processes N CSI reports. CPU It can be said that it has CSI processing units. If L CPUs are occupied for the calculation of CSI reports within a given OFDM symbol, the UE (N CPU- It can be said that there are L) unoccupied CPUs. Referring to FIG. 12, if the UE omits CSI measurements for TO#A4, TO#A5, TO#A6, and TO#A7 belonging to window #A3, and the total number of CPUs for CSI report(s) associated with each TO is N, then the UE can consider the N CPUs to be unoccupied during the window period (or the period corresponding to TO#A4, TO#A5, TO#A6, and TO#A7). As a result, the remaining CPUs can be utilized for other CSI report(s).

[0285] The UE can release the APU occupancy of CSI report(s) associated with CSI reporting. An AI / ML processing unit (APU) may refer to a unit required by the UE to process AI / ML processes concurrently at a specific time, and the maximum number of APUs per carrier or for all carrier(s) may be determined based on the UE's reporting capability. The UE N APU If simultaneous AI / ML processes are supported, the above UE has a total of N APU It can be said that it has APUs. If L APUs are occupied for computing CSI reports within a given OFDM symbol, the UE (N APU- It can be said that there are L) unoccupied APUs. Referring to FIG. 12, if a UE omits CSI measurements for TO#A4, TO#A5, TO#A6, and TO#A7 belonging to window #A3, and the total number of APUs for CSI report(s) associated with each TO is N, then the UE can consider the N APUs as unoccupied during the window interval (or the interval corresponding to TO#A4, TO#A5, TO#A6, and TO#A7). As a result, the remaining APUs can be utilized for other CSI report(s).

[0286] The UE may exclude CSI-RS(s) linked to CSI report(s) associated with CSI reporting from the active CSI-RS resource / port counting. In 5G NR standard documents (e.g., 3GPP TS 38.214), the BS must ensure that the number of CSI-RS resources / ports linked to CSI reporting is counted by default and that the sum is less than or equal to a certain number (e.g., the maximum value of which (e.g., the number of CSI-RS resources / ports associated with CSI reporting (sub)setting(s) per BWP / Carrier / Serving Cell or per UE)) the maximum value may be limited by the UE's capability). In this case, if a CSI-RS resource is referenced N times by one or more CSI Reporting Settings, the corresponding CSI-RS resource and the corresponding CSI-RS ports within said CSI-RS resource are counted N times. If the UE also omits CSI measurements for TO#A4, TO#A5, TO#A6, and TO#A7 belonging to window #A3, the UE may exclude the CSI-RS resource(s) linked to the CSI report(s) associated with each TO from the active CSI-RS resource / port counting, and the remaining number of active CSI-RS resource(s) / port(s) may be utilized for other CSI reporting purposes.

[0287] FIG. 13 illustrates the signal transmission / reception flow between a UE and a network (e.g., BS) according to some implementations of the present specification. Referring to FIG. 13, the network (e.g., BS) may assign / configure a PUCCH (or PUSCH) to UE#A for periodic (or semi-persistent) CSI reporting (S1301). In some implementations, when assigning / configuring the PUCCH / PUSCH for CSI reporting, or when providing a configuration for window-related signaling that allows CSI reporting to be omitted, the BS may provide the UE with a configuration regarding the mapping relationship between M (or K) and code-point. The UE may utilize the corresponding mapping relationship in each or some PUCCH (or PUSCH) TO to signal whether resources are unused for future TO(s) (S1303). If a UE signals a window corresponding to M future TO(s) or K time intervals in a specific TO, the UE may omit CSI reporting in the M TO(s) or in the window (S1305a). In some implementations, if necessary, the BS may utilize the uplink resources for which CSI reporting was omitted for the same UE or a different UE (S1305b).

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

[0289] According to some implementations of this specification, when a UE notifies a BS that it will not transmit CSI for a certain period of time (e.g., non-use of uplink resources allocated / configured for CSI reporting), the BS can allocate the uplink resources for that period of time to the UE or another UE, thereby enabling efficient utilization of resources. Additionally, the UE that has not transmitted CSI for a certain period of time can enjoy the benefit of reduced power consumption.

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

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

[0292] In a method performed by the above UE, or in the above UE, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: receiving a transmission occasion (TO) related setting for reporting channel state information (CSI) (S1401); determining unused TOs or a TO window including unused TOs among a plurality of TOs of the TO related setting (S1403); and transmitting a CSI report at a TO that is not an unused TO or a TO not included in the TO window (S1405).

[0293] In some implementations, the above methods or operations may include: omitting the CSI reporting in the TO of the TO-related settings included in the TO window.

[0294] In some implementations, the above method or operation may further include transmitting TO window information regarding the TO window.

[0295] In some implementations, the TO window information may be transmitted from TO #n of the TO-related settings preceding the TO window.

[0296] In some implementations, the TO window information may be transmitted through an uplink channel configured for TO window reporting.

[0297] In some implementations, the above methods or operations may further include performing a CSI prediction, and the TO window may be determined based on the CSI prediction.

[0298] In some implementations, the above methods or operations may further include transmitting CSI #n at TO #n of the TO-related settings. Based on the fact that CSI #n and CSI #(n+k) of the TO-related settings satisfy predetermined conditions, the TO window may include CSI #(n+k), where CSI #(n+k) is the CSI to be transmitted at TO #(n+k).

[0299] In some implementations, the above methods or operations may further include receiving a TO window setting from BS, and the TO window may be determined based on the TO window setting.

[0300] In some implementations, within the TO window, the CSI processing unit (CPU) associated with each TO of the TO-related settings may not be occupied.

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

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

[0303] In a method performed by the above BS, or in the above BS, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: transmitting a transmission occasion (TO) related setting for reporting channel state information (CSI) to the UE (S1501); determining unused TOs or a TO window including unused TOs among a plurality of TOs of the TO related setting (S1503); and receiving a CSI report from the UE in a TO that is not an unused TO or a TO not included in the TO window (S1505).

[0304] In some implementations, the above methods or operations may include: omitting the reception of CSI reports in the TO of the TO-related settings included in the TO window.

[0305] In some implementations, the above method or operation may further include receiving TO window information regarding the TO window from the UE.

[0306] In some implementations, the TO window may be determined based on the TO window information received from the UE.

[0307] In some implementations, the TO window information may be received at TO #n of the TO-related setting preceding the TO window.

[0308] In some implementations, the TO window information may be received through an uplink channel configured for TO window reporting.

[0309] In some implementations, the above methods or operations may further include performing a CSI prediction, and the TO window may be determined by the BS based on the CSI prediction.

[0310] In some implementations, the above method or operation may further include transmitting TO window information regarding the TO window to the UE.

[0311] In some implementations, the above methods or operations may further include receiving CSI #n at TO #n of the TO-related settings. Based on the fact that CSI #n and CSI #(n+k) of the TO-related settings satisfy a predetermined condition, the TO window may include CSI #(n+k), wherein CSI #(n+k) is a CSI to be received at TO #(n+k).

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

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

Claims

1. In a method performed by user equipment (UE), Receive settings related to the transmission occasion (TO) for channel state information (CSI) reporting; Determining a TO window including unused TOs among multiple TOs in the above TO-related settings; and Includes transmitting CSI from a TO not included in the above TO window, method.

2. In Paragraph 1, Including omitting the CSI reporting in the TO of the TO-related settings included in the above TO window, method.

3. In Paragraph 1, Further including transmitting TO window information regarding the above TO window, method.

4. In Paragraph 3, The above TO window information is transmitted from TO #n of the above TO-related settings preceding the above TO window, method.

5. In Paragraph 3, The above TO window information is transmitted via an uplink channel configured for TO window reporting, method.

6. In Paragraph 1, It further includes performing CSI prediction, The above TO window is determined based on the above CSI prediction, method.

7. In Paragraph 6, It further includes transmitting CSI #n from TO #n of the above TO-related settings, and Based on the fact that the above CSI #n and the CSI #(n+k) of the above TO-related setting satisfy predetermined conditions, the above TO window includes the above CSI #(n+k), wherein the above CSI #(n+k) is the CSI to be transmitted from the above TO #(n+k). method.

8. In Paragraph 1, It further includes receiving TO window settings from the base station, and The above TO window is determined based on the above TO window settings, method.

9. In Paragraph 1, Within the above TO window, the CSI processing unit (CSI processing unit, CPU) associated with each TO of the above TO-related settings is not occupied. method.

10. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receive settings related to the transmission occasion (TO) for channel state information (CSI) reporting; Determining a TO window including unused TOs among multiple TOs in the above TO-related settings; and Includes transmitting CSI from a TO not included in the above TO window, User device.

11. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receive settings related to the transmission occasion (TO) for channel state information (CSI) reporting; Determining a TO window including unused TOs among multiple TOs in the above TO-related settings; and Includes transmitting CSI from a TO not included in the above TO window, Processing unit.

12. In a computer-readable non-transitory storage medium, The above storage medium stores at least one program code including instructions that cause at least one processor to perform operations when executed, and said operations are: Receive settings related to the transmission occasion (TO) for channel state information (CSI) reporting; Determining a TO window including unused TOs among multiple TOs in the above TO-related settings; and Includes transmitting CSI from a TO not included in the above TO window, Storage medium.

13. In a method performed by a base station (BS), Transmit settings related to the transmission occasion (TO) for channel state information (CSI) reporting to the user device (UE); Determining a TO window including unused TOs among multiple TOs in the above TO-related settings; and including receiving CSI from the UE in a TO not included in the above TO window, method.

14. In Paragraph 13, Including omitting the reception of CSI reports in the TO of the TO-related settings included in the above TO window, method.

15. In Paragraph 13, Further comprising receiving TO window information regarding the above TO window from the UE, method.

16. In Paragraph 15, The above TO window is determined based on the TO window information received from the UE, method.

17. In Paragraph 15, The above TO window information is received from TO #n of the above TO-related settings preceding the above TO window, method.

18. In Paragraph 15, The above TO window information is received through an uplink channel configured for TO window reporting, method.

19. In Paragraph 13, It further includes performing CSI prediction, The above TO window is determined by the above BS based on the above CSI prediction, method.

20. In Paragraph 19, Further comprising transmitting TO window information regarding the above TO window to the UE, method.

21. In Paragraph 19, It further includes receiving CSI #n from TO #n of the above TO-related settings, and Based on the fact that the above CSI #n and the CSI #(n+k) of the above TO-related setting satisfy predetermined conditions, the above TO window includes the above CSI #(n+k), wherein the above CSI #(n+k) is the CSI to be received at the above TO #(n+k). method.

22. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Transmit settings related to the transmission occasion (TO) for channel state information (CSI) reporting to the user device (UE); Determining a TO window including unused TOs among multiple TOs in the above TO-related settings; and including receiving CSI from the UE in a TO not included in the above TO window, Base station.

Images