Method and device for performing channel state information reporting in wireless communication system

Abstract

Disclosed are a method and a device for performing channel state information reporting in a wireless communication system. The method according to an embodiment of the present disclosure may include the steps of: receiving, by a terminal, a configuration for a channel state information (CSI) report from a base station; reporting, by the terminal, first information on whether an event related to the CSI report is detected, to the base station; and reporting, by the terminal, second information on a report quantity related to the CSI report to the base station on the basis of the detection of the event.

Description

Method and device for performing channel state information reporting in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for performing channel state information (CSI) reporting in a wireless communication system.

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users' demand for higher-speed services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] The technical problem of the present disclosure is to provide a method and device for performing channel state information (CSI) reporting in a wireless communication system.

[0005] The technical problem of the present disclosure is to provide a method and device for setting / managing CPU (CSI processing unit) occupancy when a beam report is initiated by a terminal.

[0006] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0007] A method according to one aspect of the present disclosure may include: receiving, by a terminal, a setting for channel state information (CSI) reporting from a base station; reporting, by the terminal, first information regarding whether an event related to the CSI report has been detected to the base station; and reporting, by the terminal, second information regarding a report quantity related to the CSI report to the base station based on the event being detected. Here, the report quantity is related to a power measurement value for a reference signal set as a measurement resource based on the setting, and a CSI processing unit (CPU) occupancy time for the CSI report may be based on at least one of a first CPU occupancy time for reporting the first information or a second CPU occupancy time for reporting the second information.

[0008] A method according to an additional aspect of the present disclosure may include: transmitting, by a base station, a configuration for channel state information (CSI) reporting to a terminal; receiving, by the base station, first information from the terminal regarding whether an event related to the CSI report has been detected; and receiving, by the base station, second information regarding a report quantity related to the CSI report from the terminal based on detection of the event. Here, the report quantity is related to a power measurement value for a reference signal set as a measurement resource based on the configuration, and a CSI processing unit (CPU) occupancy time for the CSI report may be based on at least one of a first CPU occupancy time for reporting the first information or a second CPU occupancy time for reporting the second information.

[0009] According to various embodiments of the present disclosure, a method and apparatus for performing channel state information (CSI) reporting in a wireless communication system may be provided.

[0010] According to various embodiments of the present disclosure, a method and device for setting / managing CPU (CSI processing unit) occupancy when a beam report is initiated by a terminal may be provided.

[0011] According to various embodiments of the present disclosure, there is a technical effect in which a base station can clearly recognize the CPU occupancy status of a terminal in relation to a beam report initiated by the terminal, and can efficiently manage / utilize CPU resources.

[0012] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0013] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0014] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0015] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0016] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0017] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied.

[0018] FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0019] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

[0020] Figure 7 illustrates a general functional architecture related to functionality-based LCM and model-based LCM.

[0021] Figure 8 illustrates signaling operations for procedures related to AI / ML.

[0022] FIG. 9 illustrates an example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0023] FIG. 10 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0024] FIG. 11 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0025] FIG. 12 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0026] FIG. 13 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0027] FIG. 14 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0028] FIG. 15 illustrates a configuration of CPU occupancy time in a two-step-based terminal initiation beam report according to an embodiment of the present disclosure.

[0029] FIG. 16 illustrates an example of a CPU occupancy time configuration for a two-step-based terminal-initiated beam report according to an embodiment of the present disclosure.

[0030] FIG. 17 illustrates another example of CPU occupancy time configuration for a two-step based terminal initiation beam report according to an embodiment of the present disclosure.

[0031] FIG. 18 is a drawing for explaining the operation of a terminal according to an embodiment of the present disclosure.

[0032] FIG. 19 is a diagram for explaining the operation of a base station according to an embodiment of the present disclosure.

[0033] FIG. 20 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0034] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

[0035] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0036] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0037] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0038] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0039] The present disclosure describes a wireless communication network or a wireless communication system, and an operation performed in a wireless communication network may be performed in a process of controlling the network and transmitting or receiving a signal from a device (e.g., a base station) that manages the wireless communication network, or may be performed in a process of transmitting or receiving a signal to or between terminals connected to the wireless network.

[0040] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

[0041] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0042] The technology described in this specification can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0043] The technology described in this specification can be implemented with 6G wireless technology and applied to various 6G systems. For example, the 6G system can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0044] For clarity, the description is based on 3GPP communication systems (e.g., LTE-A, NR, 6G), but the technical spirit of the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR / 6G may be referred to as a 3GPP system. “xxx” refers to a standard document detail number. LTE / NR / 6G may be collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published prior to the present disclosure. For example, reference may be made to the following documents.

[0045] For 3GPP LTE, see TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

[0046] For 3GPP NR, see TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (Overall description of NR and New Generation-Radio Access Network (NG-RAN)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0047] Abbreviations for terms that may be used in this disclosure are defined as follows.

[0048] - BM: beam management

[0049] - CQI: Channel Quality Indicator

[0050] - CRI: Channel state information - reference signal resource indicator

[0051] - CSI: Channel State Information

[0052] - CSI-IM: Channel State Information - Interference Measurement

[0053] - CSI-RS: Channel state information - reference signal

[0054] - DMRS: Demodulation Reference Signal

[0055] - FDM: frequency division multiplexing

[0056] - FFT: fast Fourier transform

[0057] - IFDMA: interleaved frequency division multiple access

[0058] - IFFT: inverse fast Fourier transform

[0059] - L1-RSRP: Layer 1 reference signal received power

[0060] - L1-RSRQ: Layer 1 reference signal received quality

[0061] - MAC: Medium Access Control

[0062] - NZP: non-zero power

[0063] - OFDM: orthogonal frequency division multiplexing

[0064] - PDCCH: Physical downlink control channel

[0065] - PDSCH: Physical downlink shared channel

[0066] - PMI: precoding matrix indicator

[0067] - RE: resource element

[0068] - RI: Rank indicator

[0069] - RRC: Radio Resource Control

[0070] - RSSI: Received signal strength indicator

[0071] - Rx: Reception

[0072] - QCL: quasi co-location

[0073] - SINR: signal to interference and noise ratio

[0074] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))

[0075] - TDM: Time Division Multiplexing

[0076] - TRP: transmission and reception point

[0077] - TRS: Tracking Reference Signal

[0078] - Tx: transmission

[0079] - UE: user equipment

[0080] - ZP: Zero Power

[0081] System General

[0082] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing radio access technologies (RATs) is emerging. Furthermore, massive machine type communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, these technologies are referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0083] As mentioned above, the NR system, a successor to LTE (long term evolution), is a new clean-slate mobile communications system characterized by high performance, low latency, and high availability. NR systems can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. Based on the underlying technology of the NR system, the 6G mobile communications system (hereinafter referred to as the 6G system) is being developed.

[0084] The 6G system aims to provide (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0085] New RAT systems, including NR systems and 6G systems (hereinafter referred to as "next-generation RAT systems"), utilize OFDM transmission schemes or similar transmission schemes. Next-generation RAT systems may follow OFDM parameters different from those of LTE. Alternatively, next-generation RAT systems may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies. That is, terminals operating under different numerologies may coexist within a single cell.

[0086] A numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0087] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0088] Referring to Fig. 1, the NG-RAN consists of gNBs that provide NG-RA (NG-Radio Access) user plane (i.e., new AS (access stratum) sublayer / PDCP (packet data convergence protocol) / RLC (radio link control) / MAC / PHY) and control plane (RRC) protocol termination for UE. The gNBs are interconnected via Xn interfaces. The gNBs are also connected to the NGC (New Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via the N2 interface and to the UPF (User Plane Function) via the N3 interface.

[0089] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0090] Next-generation RAT systems can support multiple numerologies. Numerologies can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band. Furthermore, next-generation RAT systems can support various frame structures corresponding to multiple numerologies.

[0091] Below, we examine OFDM numerologies and frame structures that can be considered in next-generation RAT systems. The various OFDM numerologies supported in next-generation RAT systems can be defined as shown in Table 1 below.

[0092] μΔf=2 μ ·15 [kHz]CP015 Normal 130 Normal 260 Normal, Extended 3120 Normal 4240 Normal

[0093] Next-generation RAT systems support multiple numerologies (or subcarrier spacings (SCS)) to support various 5G / 6G services. For example, an SCS of 15 kHz supports a wide area in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense-urban, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports a bandwidth greater than 24.25 GHz to overcome phase noise. Although not described in Table 1, an SCS of 480 kHz / 960 kHz may be additionally supported for 6G systems.

[0094] The frequency bands of next-generation RAT systems are defined by various types of frequency ranges (e.g., FR1, FR2, etc.). For example, FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 can refer to millimeter wave (mmW).

[0095] Frequency Range Designation Corresponding Frequency Range Subcarrier Spacing FR1410MHz - 7125MHz 15, 30, 60kHz FR224250MHz - 52600MHz 60, 120, 240kHz

[0096] Regarding the frame structure in the next-generation RAT system, the sizes of various fields in the time domain are T c =1 / (Δf max ·N f ) is expressed as a multiple of the time unit. Here, Δf max =480·10 3 Hz, and N f =4096. Downlink and uplink transmissions are T f =1 / (Δf max N f / 100)·T c = It is organized into radio frames with a duration of 10ms. Here, each radio frame is T sf =(Δf max N f / 1000)·T c It consists of 10 subframes with a duration of 1ms. In this case, there may be one set of frames for the uplink and one set of frames for the downlink.

[0097] Additionally, transmission at uplink frame number i from the terminal is T earlier than the start of the corresponding downlink frame from the terminal. TA =(N TA +N TA,offset )T c It should start before. For the subcarrier spacing configuration μ, slots are n within a subframe. s μ ∈{0,..., N slotsubframe,μ-1} are numbered in increasing order, and n within a radio frame. s,f μ ∈{0,..., N slot frame,μ -1} are numbered in increasing order. One slot is N symb slot It consists of consecutive OFDM symbols, and N symb slot is determined by CP. Slot n in subframe s μ The start of OFDM symbol n in the same subframe s μ N symb slot are aligned temporally with the start of the OFDM signal. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be utilized.

[0098] Table 3 shows the number of OFDM symbols per slot in a general CP (N symb slot ), the number of slots per wireless frame (N slot frame,μ ), number of slots per subframe (N slot subframe,μ), and Table 4 shows the number of OFDM symbols per slot in the extended CP, the number of slots per radio frame, and the number of slots per subframe.

[0099] μN symb slot N slot frame,μ N slot subframe,μ01410111420221440431480841416016

[0100] μN symb slot N slot frame,μ N slot subframe,μ212404

[0101] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, 1 subframe can include 4 slots. 1 subframe={1,2,4} slot illustrated in FIG. 2 is an example, and the number of slot(s) that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols.

[0102] Regarding physical resources in a next-generation RAT system, antenna ports, resource grids, resource elements, resource blocks, and carrier parts may be considered. Below, the physical resources that may be considered in a next-generation RAT system will be examined in detail.

[0103] First, with respect to antenna ports, antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0104] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0105] Referring to Figure 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In the next-generation RAT system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ ≤N RB max,μ is. The above N RB max,μ represents the maximum transmission bandwidth, which may vary between uplink and downlink as well as between numerologies. In this case, one resource grid may be configured for μ and antenna port p. Each element of the resource grid for μ and antenna port p is referred to as a resource element and is uniquely identified by an index pair (k, l'), where k=0,...,N. RB μ N sc RB -1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 indicates the position of the symbol within the subframe. When referring to a resource element in a slot, an index pair (k,l) is used. Here, l=0,...,N symb μ-1. The resource element (k,l') for μ and antenna port p is a complex value a k,l' (p,μ) . If there is no risk of confusion or if a particular antenna port or numerology is not specified, the indices p and μ can be dropped, resulting in a complex value of a k,l' (p) or a k,l' This can be. Also, a resource block (RB) is N in the frequency domain. sc RB =12 is defined as consecutive subcarriers.

[0106] Point A serves as a common reference point of the resource block grid and is obtained as follows.

[0107] - offsetToPointA for the Primary Cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0108] - absoluteFrequencyPointA represents the frequency-position of point A expressed as ARFCN (absolute radio-frequency channel number).

[0109] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between the resource elements (k, l) and the subcarrier spacing setting μ is given by the following mathematical expression 1.

[0110]

[0111] In Equation 1, k is defined relative to point A such that k = 0 corresponds to the subcarrier centered at point A. Physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ - Numbered from 1 to 1, where i is the number of the BWP. Physical resource block n in BWP i PRB and common resource block n CRB The relationship between them is given by the mathematical formula 2 below.

[0112]

[0113] N BWP,i start,μ is a common resource block where BWP starts relative to common resource block 0.

[0114] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0115] Referring to FIGS. 4 and 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot includes seven symbols, but in the case of an extended CP, one slot includes six symbols.

[0116] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical) resource blocks in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can comprise up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0117] Next-generation RAT systems can support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, when considering multiple use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Alternatively, each terminal may have different maximum bandwidth capabilities. Considering this, the base station can instruct the terminal to operate only in a portion of the bandwidth of the wideband CC, rather than the entire bandwidth. This portion of bandwidth is conveniently defined as the bandwidth part (BWP). A BWP can be composed of consecutive RBs on the frequency axis and can correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / mini-slot interval).

[0118] Meanwhile, a base station can configure multiple BWPs even within a single CC configured for a terminal. For example, a BWP occupying a relatively small frequency domain can be configured in a PDCCH monitoring slot, while the PDSCH indicated by the PDCCH can be scheduled on a larger BWP.

[0119] Alternatively, if UEs are concentrated in a specific BWP, some UEs can be assigned to different BWPs for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, some spectrum in the middle of the total bandwidth can be excluded and both BWPs can be assigned within the same slot. In other words, the base station can assign at least one DL / UL BWP to UEs associated with a wideband CC.

[0120] The base station can activate at least one DL / UL BWP among the DL / UL BWP(s) configured at a specific point in time (by L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). In addition, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, switching to a designated DL / UL BWP may be performed when a timer value expires based on a timer. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, since the UE may not receive the configuration for the DL / UL BWP when performing the initial access process or before the RRC connection is set up, the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

[0121] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

[0122] In wireless communication systems, terminals receive information from a base station via the downlink and transmit it to the base station via the uplink. The information transmitted and received between the base station and terminals includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0123] The second node of FIG. 6 supports dynamic spectrum sharing (DSS), which can provide connectivity not only to nodes implementing 6G technology but also to nodes implementing pre-6G wireless communication technologies (e.g., 5G, 4G). That is, the first node of FIG. 6 can implement either 6G technology or pre-6G wireless communication technologies (e.g., 5G, 4G). Furthermore, the first node and / or the second node can support full duplex mode as well as non-overlapping full duplex mode.

[0124] In Fig. 6, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and operations of transmitting and / or receiving data by the terminal (110) and the base station (120) and operations performed prior thereto are illustrated. However, the operations of Fig. 6 are not limited to operations between the terminal and the base station, and may be interpreted as operations between the first node and the second node. In addition, although Fig. 6 illustrates direct wireless signal transmission and reception operations between the terminal (110) and the base station (120), one or more intermediate points may exist between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0125] Referring to FIG. 6, in step 101, the terminal (110) and the base station (120) perform synchronization. For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect a synchronization signal for connection to at least one base station transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals classified according to structure or purpose (e.g., a first synchronization signal (e.g., a primary synchronization signal), a second synchronization signal (e.g., a secondary synchronization signal), etc.). Through this, the terminal (110) can confirm the boundary of a unit (e.g., a frame, a subframe, a slot, and / or a symbol) constituting a wireless signal transmission of the base station (120) and obtain information (e.g., a cell identifier) ​​about the base station (120).

[0126] In step 103, the terminal (110) obtains system information transmitted from the base station (120). The system information is information related to the properties, characteristics, and / or capabilities of the base station (120) required to access the base station (120) and use the service, and may be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., channel used, whether provided on-demand), etc., and may be classified into, for example, first system information (e.g., master information block (MIB), primary system information), second system information (e.g., system information block (SIB), secondary system information), etc. If necessary, the terminal (110) may transmit a signal requesting system information before receiving the system information. However, the request and provision of the system information may be performed after the random access procedure described below.

[0127] In step 105, the terminal (110) and the base station (120) perform a random access procedure. The terminal (110) may transmit and / or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for the random access procedure based on information related to a channel for the random access procedure of the base station (120) obtained through system information (e.g., a channel position, a channel structure, a structure of a supported preamble, etc.). For example, the terminal (110) may transmit a first message (e.g., a preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., an RAR message, MSG2), transmit a third message (e.g., MSG3) including information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the second message, and receive a fourth message (e.g., MSG4) for contention resolution and / or connection establishment. As another example, the first and third messages may be sent and received as one message, or the second and fourth messages may be sent and received as one message.

[0128] In step 107, the terminal (110) and the base station (120) perform signaling of control information. Here, the control information may be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) may perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

[0129] In step 109, the terminal (110) and the base station (120) transmit and / or receive data. In other words, the terminal (110) and the base station (120) can process, transmit, and / or receive data based on the signaling of the control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0130] Table 5 shows an example of DCI format in the next-generation RAT system.

[0131] DCI Format Utilization 0_0 Scheduling of PUSCH within a cell 0_1 Scheduling of one or multiple PUSCH within a cell, or indicating cell group (CG: cell group) downlink feedback information to the UE 0_2 Scheduling of PUSCH within a cell 1_0 Scheduling of PDSCH within a DL cell 1_1 Scheduling of PDSCH within a cell 1_2 Scheduling of PDSCH within a cell

[0132] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to scheduling of PUSCH (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for scheduling of PUSCH in one cell. Information included in DCI format 0_0 is transmitted after being CRC (cyclic redundancy check) scrambled by C-RNTI (cell radio network temporary identifier, Cell RNTI), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI). DCI format 0_1 ​​is used to indicate scheduling of one or more PUSCHs in one cell, or configured grant (CG) downlink feedback information to a UE. Information included in DCI format 0_1 ​​is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.DCI format 0_2 is used for scheduling PUSCH in a cell. The information contained in DCI format 0_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0133] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to scheduling of PDSCH (e.g., frequency resource allocation, time resource allocation, virtual resource block (VRB)-physical resource block (PRB) mapping, etc.), transport block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., antenna port, transmission configuration indicator (TCI), sounding reference signal (SRS) request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format may be predefined.

[0134] DCI format 1_0 is used for scheduling PDSCH in a DL cell. The information contained in DCI format 1_0 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0135] DCI format 1_1 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_1 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0136] DCI format 1_2 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0137] Quasi-Co Location (QCL)

[0138] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried.

[0139] Here, the channel characteristics include one or more of delay spread, Doppler spread, frequency / Doppler shift, average received power, received timing / average delay, and spatial Rx parameter. Here, the spatial Rx parameter refers to a spatial (reception) channel characteristic parameter such as angle of arrival.

[0140] A terminal may be configured with a list of up to M TCI-State settings in the upper layer parameter PDSCH-Config to decode PDSCHs based on detected PDCCHs having DCI intended for the terminal and a given serving cell. M depends on the UE capability.

[0141] Each TCI-State contains parameters for establishing a quasi co-location relationship between one or two DL reference signals and the DM-RS port of the PDSCH.

[0142] The quasi-colocation relationship is established by the upper-layer parameters qcl-Type1 for the first DL RS and qcl-Type2 (if set) for the second DL RS. For two DL RSs, the QCL types are not the same, regardless of whether the references are the same DL RS or different DL RSs.

[0143] The quasi co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info, and can take one of the following values:

[0144] - 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

[0145] - 'QCL-TypeB': {Doppler shift, Doppler spread}

[0146] - 'QCL-TypeC': {Doppler shift, average delay}

[0147] - 'QCL-TypeD': {Spatial Rx parameter}

[0148] For example, if a target antenna port is a specific NZP CSI-RS, the corresponding NZP CSI-RS antenna port(s) can be instructed / configured to be QCL with a specific TRS from a QCL-Type A perspective and with a specific SSB from a QCL-Type D perspective. A terminal that has received such an instruction / configuration can receive the corresponding NZP CSI-RS using the Doppler and delay values ​​measured at the QCL-TypeA TRS, and apply the reception beam used for QCL-TypeD SSB reception to the corresponding NZP CSI-RS reception.

[0149] The UE can receive an activation command by MAC CE signaling, which is used to map up to eight TCI states to codepoints in the DCI field 'Transmission Configuration Indication'.

[0150] CSI-related actions

[0151] In NR (New Radio) systems, CSI-RS (channel state information-reference signal) is used for time / frequency tracking, CSI computation, L1 (layer 1)-RSRP (reference signal received power) computation, and mobility. Here, CSI computation is related to CSI acquisition, and L1-RSRP computation is related to beam management (BM).

[0152] CSI (channel state information) is a general term for information that can indicate the quality of the wireless channel (or link) formed between the terminal and the antenna port.

[0153] - In order to perform one of the purposes of the CSI-RS as described above, a terminal (e.g., user equipment, UE) receives configuration information related to CSI from a base station (e.g., general Node B, gNB) through RRC (radio resource control) signaling.

[0154] The configuration information related to the above CSI may include at least one of CSI-IM (interference management) resource related information, CSI measurement configuration related information, CSI resource configuration related information, CSI-RS resource related information, or CSI report configuration related information.

[0155] i) CSI-IM resource-related information may include CSI-IM resource information, CSI-IM resource set information, etc. A CSI-IM resource set is identified by a CSI-IM resource set ID (identifier), and one resource set includes at least one CSI-IM resource. Each CSI-IM resource is identified by a CSI-IM resource ID.

[0156] ii) CSI resource configuration related information can be expressed as CSI-ResourceConfig IE. The CSI resource configuration related information defines a group including at least one of a non-zero power (NZP) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the CSI resource configuration related information includes a CSI-RS resource set list, and the CSI-RS resource set list can include at least one of 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 one resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID.

[0157] Parameters indicating the purpose of CSI-RS (e.g., BM-related 'repetition' parameter, tracking-related 'trs-Info' parameter) can be set for each NZP CSI-RS resource set.

[0158] Additionally, measurement resources may be configured for CSI reporting. For example, the corresponding measurement resources may be configured through CSI reporting configuration. Here, the measurement resources may include resources for channel measurement (e.g., channel measurement resources (CMR)) and resources for interference measurement (e.g., interference measurement resources (IMR)). RS resources configured as measurement resources (e.g., CSI-RS resources, SSB resources, etc.) may be located in measurement opportunity(s) based on the configuration for CSI reporting.

[0159] iii) Information related to the CSI report configuration includes a report configuration type parameter (reportConfigType) indicating time domain behavior and a report quantity parameter (reportQuantity) indicating the CSI-related quantity to be reported. The time domain behavior may be periodic, aperiodic, or semi-persistent.

[0160] - The terminal measures CSI based on configuration information related to the above CSI.

[0161] The above CSI measurement may include (1) a process of receiving a CSI-RS of a terminal, and (2) a process of calculating CSI using the received CSI-RS, which will be described in detail later.

[0162] CSI-RS sets the RE (resource element) mapping of CSI-RS resources in the time and frequency domains by the higher layer parameter CSI-RS-ResourceMapping.

[0163] - The terminal reports the measured CSI to the base station.

[0164] Here, if the quantity of CSI-ReportConfig is set to 'none (or No report)', the terminal can skip the report. However, even if the quantity is set to 'none (or No report)', the terminal can still report to the base station. The case where the quantity is set to 'none' is when aperiodic TRS is triggered or repetition is set. Here, the terminal's report can be skipped only when repetition is set to 'ON'.

[0165] Artificial intelligence (AI) / machine learning (ML) related operations

[0166] AI / ML can be introduced / applied to the next-generation RAT system described in this disclosure.

[0167] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). 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.

[0168] Below, we describe a functional framework for AI / ML operations.

[0169] Below, to explain AI (or AI / ML) more specifically, the terms can be defined as follows.

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

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

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

[0173] - AI / ML Inference: The process of making predictions or inducing decisions based on collected data and the AI ​​model using a trained AI model.

[0174] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updates, etc.) can be divided 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 / switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified by the network, and the network / terminal can activate / deactivate / select / switch AI / ML models based on the model ID.

[0175] Figure 7 illustrates a general functional architecture relevant to both Functionality-based LCM and Model-based LCM. Some of the functions or some of the data / information / command flows (i.e., arrows) illustrated in Figure 7 may be omitted.

[0176] Referring to FIG. 7, a general functional framework can 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).

[0177] 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) can perform data preparation based on raw data and provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals 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., terminal, network node, etc.) or may be performed by multiple entities.

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

[0179] 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 the AI / ML model testing procedure. The Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming, and transformation) based on the Training Data (11) transferred from the Data Collection function (10), if necessary.

[0180] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to pass a trained, validated and tested AI / ML model to the Model Storage function (50) or to pass an updated version of the model to the Model Storage function (50).

[0181] The Management function (30) is a function that supervises the operation of the AI / ML model or AI / ML function. In addition, the Management function (30) may perform decisions to ensure appropriate inference operations based on data received from the Data Collection function (10) (i.e., Monitoring Data (12)) and / or data received from the Inference function (40) (i.e., Inference Output (41)).

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

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

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

[0185] The Inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., Inference Data (13)) provided by 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 Data Collection (10). If necessary, the Inference function (40) may also perform data preparation (e.g., data preprocessing and cleaning, forming, and transformation) based on the Inference Data (13) provided by Data Collection function (10).

[0186] 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 the AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0187] The Model Storage function (50) stores a learned / updated model that can be used to perform the Inference function (40). The Model Storage function (50) illustrated in FIG. 7 can be used as a reference point (if any) when applicable to protocol termination, model transmission / delivery, and related processes. Furthermore, the Model Storage function (50) is merely an example and is not intended to limit the storage location of actual AI / ML models, and may be omitted.

[0188] Model Transfer / Delivery (51) is used to transfer AI / ML models to inference functions.

[0189] The level of cooperation can be defined as follows depending on the capability of AI / ML functions between multiple nodes, and variations due to combination of multiple levels or separation of any one level are also possible.

[0190] Cat 0a) No collaboration framework: AI / ML algorithms are purely implementation-based and do not require any changes to the wireless interface.

[0191] Cat 0b) This level corresponds to a framework with a modified wireless interface tailored to efficient implementation-based AI / ML algorithms, but without collaboration.

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

[0193] Category 2) Joint AI / ML tasks can be performed across multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

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

[0195] AI / ML models can be divided 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.

[0196] A one-side model can refer to an AI / ML model in which inference is performed entirely by a single node (e.g., a terminal or network). Here, AI / ML model training can also be performed entirely by a single node. AI / ML model training and inference can be performed by the same node, or they can be performed by separate nodes.

[0197] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference refers to inference being performed jointly across multiple nodes. For example, the first part of the inference may be performed by a first node, and the remaining part by a second node. Two-side models can be categorized into several types depending on the training method of the AI / ML model, as follows:

[0198] - First type: AI / ML models 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 / objects.

[0199] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation part) 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 (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).

[0200] - Third type: Separate training of AI / ML models can be performed on multiple nodes (e.g., networks and terminals). Separate training may mean that training begins sequentially on one node and continues on other nodes. In this case, the first node first performs the AI / ML model and shares the training data with the second node. The second node can then use the shared training data to perform the AI / ML model. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0201] The operations described in the present disclosure described below can be described / interpreted based on the AI / ML model as shown in FIG. 8 below, even without separate mention (i.e., without explicit mention of being by / based on / for the AI / ML model).

[0202] Additionally, unless specifically limited in the description of the present disclosure, the AI / ML model may correspond to a one-side model in which inference is entirely performed by one node or a two-side model in which joint inference is performed by multiple nodes.

[0203] Step 1: In the description of the present disclosure described below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., a terminal, a network, etc.) and another node may be interpreted as the signaling or set of signaling of Step 1 used to perform an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to training data for training (i.e., generation and / or reconstruction) the AI / ML model of FIG. 7, or correspond to inference data used for inference of the AI / ML model, or correspond to feedback for the AI / ML model, etc. If signaling between nodes is not required prior to an operation based on an AI / ML model in the present disclosure, Step 1 may be omitted. If a one-side model is used in the present disclosure, the unidirectional / bidirectional signaling (set) in the present disclosure may correspond to the signaling of Step 1. In addition, when a two-side model is used in the present disclosure, the one-way / two-way signaling in the present disclosure may correspond to one-stage signaling, and also, a repetitive signaling operation may correspond to one-stage signaling.

[0204] For example, in AI / ML model-based beam management (BM), if a base station predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from a terminal. Furthermore, if a terminal predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0205] Step 2: In the description of the present disclosure described below, an operation (e.g., calculation, selection, prediction, etc.) in a specific node (e.g., terminal, network, etc.) or a joint operation (e.g., calculation, selection, prediction, etc.) in multiple nodes (e.g., terminal, network, etc.) may correspond to a step 2 operation based on one or more functions in the functional framework of the AI / ML model, even if not mentioned separately. For example, it may correspond to training (i.e., generation and / or reconstruction) of the AI / ML model in FIG. 7 or inference of the AI / ML model, etc. When a one-side model is used, an operation performed by a single node in the present disclosure may correspond to a step 2 operation, and also, when a two-side model is used, a joint operation performed by multiple nodes in the present disclosure may correspond to a step 2 operation.

[0206] For example, in an AI / ML model-based BM, the base station can use quality / intensity information for multiple beams received from the terminal as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model. Furthermore, the terminal can measure multiple beams received from the base station and use the measurement results as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model.

[0207] Step 3: In the description of the present disclosure described below, the signaling (e.g., information / data / channel / signal, etc.) or set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as a three-step signaling or set of signaling generated due to (as a result of) an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to an output resulting from inference of the AI / ML model in FIG. 7. If signaling between nodes is not required as a result of an operation based on an AI / ML model in the present disclosure, Step 3 may be omitted. If a one-side model is used in the present disclosure, the one-way / two-way signaling (set) in the present disclosure may correspond to the three-step signaling. In addition, if a two-side model is used in the present disclosure, the one-way / two-way signaling in the present disclosure may correspond to the three-step signaling, and furthermore, a repetitive signaling operation may correspond to the three-step signaling.

[0208] For example, in an AI / ML model-based BM, the base station can transmit to the terminal the beam(s) predicted based on the AI / ML model as candidates so that the terminal can determine the optimal beam. Furthermore, the terminal can report to the base station the beam(s) predicted based on the AI / ML model to request the base station to transmit the candidate beams as candidates for determining the optimal beam.

[0209] CPU (CSI processing unit) occupancy in beam reports initiated by terminals

[0210] In a wireless communication system, beam reporting may be supported as a form of CSI reporting / feedback, in which a terminal reports to a base station the values ​​of RSRP (e.g., L1-RSRP) and / or SINR (e.g., L1-SINR) based on measurements (e.g., measured power) of DL reference signals (e.g., SSB, CSI-RS, etc.). That is, the beam reporting may be performed by utilizing a framework for CSI measurement and reporting configuration. In this regard, the base station may pre-configure UL resources and configurations for beam reporting and provide them to the terminal, and the terminal may report information about the beam to the base station based on the configurations.

[0211] In wireless communication systems, uplink control information of layer 1 (e.g., the physical layer) has the advantage of shorter transmission delay than control information of higher layers. For example, in order for a terminal to transmit some information to a base station via a MAC-CE or RRC message, the terminal may need an SR (scheduling request) procedure and the base station's PUSCH allocation procedure (based on the SR), which may result in delay and overhead. In addition, in general, the higher the layer information, the longer the time required to decode the information (e.g., decoding time, processing time). Furthermore, in order to transmit UL control information of layer 1, UL physical channel resources (e.g., PUCCH, PUSCH) need to be configured / allocated (in advance) to the corresponding terminal. In other words, as the number of terminals (UEs) on the network (NW) (or base station) side increases, the amount of UL resources that must be allocated to each terminal increases, which may increase the overhead for overall UL resource utilization.

[0212] Therefore, in wireless communication systems, information that must be transmitted relatively urgently for the operation of the physical layer, such as SR (for PUSCH allocation), HARQ-ACK (for retransmission), CSI (for scheduling, MCS, and precoder determination), and beam information (for digital / analog beam determination) is transmitted as physical layer uplink control information (UCI). Among the information in this example, excluding SR, the network (or base station) determines / controls the timing of information reporting by the terminal.

[0213] However, network-initiated / triggered reporting has limitations in that it requires the UE to be configured / instructed to frequently transmit UCI in environments where the wireless channel is likely to change rapidly / highly. This means that in such environments, the UL resource overhead for UCI reporting and the associated DL measurement RS overhead increase, and the UE's power consumption may also increase due to frequent UL transmission. Furthermore, as the number of UEs within cell / TRP coverage increases, the UL resource overhead also increases, as each UE must be allocated UL resources.

[0214] To overcome the limitations of network-initiated / triggered reporting as described above, terminal-initiated / triggered reporting and / or event-based / triggered reporting may be considered. In the case of terminal-initiated / triggered reporting and / or event-based / triggered reporting, whether and / or when to report can be determined by the terminal. This allows the terminal to perform the corresponding report (e.g., UCI reporting) only when necessary (e.g., when a specific event occurs), thereby reducing UL resource overhead and terminal power consumption. Furthermore, because information is reported based on a lower layer (e.g., Layer 1), there is also the technical advantage of enabling rapid reporting to the network.

[0215] In relation to the reporting method initiated / triggered by the terminal, a method may be considered in which a specific event for beam reporting is defined, and the terminal determines whether the event has occurred and performs beam reporting only when the event has occurred. For clarity of explanation, the present disclosure refers to the beam reporting method as a UE-initiated beam report.

[0216] In this disclosure, various methods are proposed for setting / managing the time for which a CPU is occupied / used for a terminal-initiated beam report (e.g., CPU occupancy time) and the number of CPUs occupied / used.

[0217] Unlike conventional CSI reporting, in the case of terminal-initiated beam reporting, since only the terminal knows whether an event has occurred (until it is reported), the base station cannot recognize whether terminal-initiated beam reporting is performed. Therefore, it may be ambiguous for the base station to determine the CPU occupancy time for terminal-initiated beam reporting. For example, the base station may assume that terminal-initiated beam reporting has occurred for a specific UL channel and thus assume that the CPU is used during the CPU occupancy time calculated based on the specific UL channel, but in reality, no event may have occurred. In another example, the base station may assume that terminal-initiated beam reporting has not occurred for a specific UL channel and thus assume that the CPU is not used during the CPU occupancy time calculated based on the specific UL channel, but in reality, an event may have occurred.

[0218] In the present disclosure, a specific UL channel may refer to / mean a (pre-configured) potential UL channel through which a terminal initiated beam report is transmitted / performed when an event occurs.

[0219] Hereinafter, with respect to terminal initiation beam reporting, a method for setting / determining CPU occupancy time (hereinafter, Embodiment 1), a method for setting the number of CPUs to be occupied during CPU occupancy time (hereinafter, Embodiment 2), and a method for setting / determining CPU occupancy time in a 2-step-based terminal initiation beam reporting (hereinafter, Embodiment 3) are described through specific examples.

[0220] Example 1

[0221] This embodiment relates to a method for setting / determining CPU occupancy time for terminal initiation beam reporting.

[0222] In this regard, to address the aforementioned issues in the present disclosure, the base station may operate to determine the CPU occupancy time by assuming that a terminal-initiated beam report is performed for a specific UL channel (regardless of whether an actual event occurs). Here, the specific UL channel may refer to / mean a (pre-configured) potential UL channel on which a terminal-initiated beam report is transmitted / performed when an event occurs.

[0223] In this case, if the event does not actually occur and the terminal-initiated beam report is not performed, the CPU may be wasted because it is occupied even though it is not actually used. However, in a situation where the base station cannot recognize whether an event has occurred, it may be desirable for the base station to allocate the CPU assuming that the terminal-initiated beam report is performed as a worst-case scenario. This is because, if the base station does not allocate the CPU assuming that the terminal-initiated beam report is not performed, the base station may omit the CPU actually used by the terminal when counting the CPU.

[0224] Below, we describe specific methods for determining CPU occupancy time.

[0225] (Example 1-1)

[0226] CPU occupancy time can be determined from the time terminal initiation beam reporting is set / activated to the time it is released / deactivated.

[0227] For example, terminal-initiated beam reporting can be set / released via RRC signals / messages, or activated / deactivated via MAC-CE / DCI, etc. In this case, the terminal can monitor the event satisfaction condition from the time terminal-initiated beam reporting is set / activated to the time it is released / deactivated. During this period, a CPU for terminal-initiated beam reporting can be allocated.

[0228] FIG. 9 illustrates an example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0229] Referring to Figure 9, the CPU occupancy time can be determined as the time interval from the time when the terminal-initiated beam report is set / activated to the time when it is released / deactivated. Furthermore, for convenience of explanation, it is assumed that one periodic CSI-RS is set in the CMR.

[0230] With this allocation method, the base station and terminal can simply count the number of CPUs currently occupied. However, with this allocation method, CPUs can be occupied even when the terminal is not actually using them.

[0231] For example, a terminal can perform a terminal beam initiation report using a channel measured through a measurement resource (e.g., CMR and / or IMR) (configured for terminal initiation beam reporting). If the measurement resource is transmitted periodically, the terminal does not use the CPU after performing a terminal initiation beam report using the measurement resource at time t1 until receiving the measurement resource at the next time t1+P. This is because no new measured channel exists during that period. However, if the aforementioned allocation method is applied, the CPU may continue to be occupied even during that period.

[0232] (Example 1-2)

[0233] To address the shortcomings of Example 1-1, a method may be considered in which the CPU occupancy time is determined by linking it to the reception time of measurement resources (e.g., CMR and / or IMR).

[0234] For example, the CPU occupancy time may be determined as the time interval from the first symbol of the earliest of each CSI-RS / CSI-IM / SSB resource for channel measurement or interference measurement to the last symbol of the next (e.g., the nearest future) potential UL channel, for the earliest CSI-RS / CSI-IM / SSB opportunity that is later than the last symbol of the previous (e.g., the nearest past) potential UL channel.

[0235] FIG. 10 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0236] Referring to FIG. 10, unlike FIG. 9, the CPU is not always occupied (from the time the terminal initiation beam report is set / activated), but may be occupied or returned depending on the measurement resources (e.g., CMR and / or IMR) and potential UL channels.

[0237] For this method, CPU occupancy time may increase when the time interval between potential UL channels becomes longer and the time interval between measurement resources becomes shorter.

[0238] (Example 1-3)

[0239] To solve the shortcomings in Example 1-1 and / or Example 1-2, a method of determining CPU occupancy time using a CSI reference resource may be considered.

[0240] In the present disclosure, a CSI reference resource may mean a group of (downlink) resources in the frequency domain and time domain established in relation to derivation / reporting / feedback of CSI.

[0241] For example, the CSI reference resource of the serving cell can be specifically defined as follows. In the frequency domain, the CSI reference resource can be defined as a group of DL physical resource blocks corresponding to the band in which the derived CSI is related. In addition, in the time domain, the CSI reference resource for CSI reporting in UL slot n' can be defined as a single DL slot nn. CSI_ref -K offset *(2^μ_DL / 2^μ_K offset ) can be defined by.

[0242] Here, K offset is a parameter set by the upper layer, and μ_K offset K has a value of 0 for frequency range 1. offset is the subcarrier spacing for periodic CSI reporting and semi-persistent CSI reporting. In addition, for periodic CSI reporting and semi-persistent CSI reporting, if a single CSI-RS / SSB resource is set for channel measurement, n CSI_ref can be the smallest value greater than or equal to 4*2^(μ_DL) corresponding to a valid DL slot, and n when multiple CSI-RS / SSB resources are configured for channel measurement. CSI_ref can be the smallest value greater than or equal to 5*2^(μ_DL) corresponding to a valid DL slot. Also, in case of aperiodic CSI reporting, if the terminal is instructed by DCI to report CSI in the same slot as the CSI request, n CSI_ref ensures that the reference resource is in the same valid DL slot as the corresponding CSI request, otherwise n CSI_ref is slot nn CSI_refis the smallest value greater than or equal to floor(Z' / N^slot_symb) corresponding to a valid DL slot, where Z' may correspond to a delay requirement. In addition, when periodic or semi-persistent CSI-RS / CSI-IM or SSB is used for channel / interference measurement, the UE may not expect to measure channel / interference on the CSI-RS / CSI-IM / SSB for which the last OFDM symbol was received until Z' symbols before the transmission time of the first OFDM symbol of the aperiodic CSI report. In addition, if there is no valid DL slot for the CSI reference resource corresponding to the CSI reporting configuration of the serving cell, the CSI reporting for the serving cell in UL slot n' may be omitted.

[0243] In this regard, the CPU occupancy time may be determined as the time interval from the first symbol of the earliest of each CSI-RS / CSI-IM / SSB resource for channel measurement or interference measurement to the last symbol of the next (e.g., nearest future) potential UL channel, for the latest CSI-RS / CSI-IM / SSB opportunity that is not later than the corresponding CSI reference resource.

[0244] FIG. 11 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0245] Referring to Figure 11, the time interval between the most recent CMR and the subsequent potential UL channel, which is not later than the CSI reference resource, can be determined as the CPU occupancy time. In this case, the CPU occupancy time can be reduced somewhat compared to the case of Figure 10.

[0246] In addition, the existing method of determining CPU occupancy time using CSI reference resources does not consider terminal-initiated beam reporting, and therefore differs from the proposed method of the present disclosure in that the CPU is occupied until the last symbol of the UL channel carrying the CSI report, which is not a potential UL channel.

[0247] (Example 1-4)

[0248] In the case of the aforementioned embodiments 1-3, CPU occupancy time can be determined using CSI reference resources, similar to the existing method. However, in the case of terminal-initiated beam reporting, CPU occupancy time can be defined to be determined regardless of the CSI reference resources.

[0249] For example, the aforementioned CSI reference resources can be used for testing requirements for CQI (e.g., RAN 4 requirement tests). That is, the CSI reference resources can be used to test whether the CQI calculated and reported by the UE satisfies the target BLER / BER when used to determine the MCS of the PDSCH transmitted on the CSI reference resources. In addition, the CSI reference resources can be used to determine the end point of channel / interference measurements to secure sufficient time to perform CSI processing from the channel / interference measurements until the UE performs CSI reporting. For example, CSI processing can mean the process of calculating and encoding the CSI quantity, buffering it, and transmitting it over the UL channel to empty the buffer.

[0250] Since terminal-initiated beam reporting assumes PDSCH reception and reports only the measured channel / interference RSRP and / or SINR values, regardless of the calculated CQI, the aforementioned requirement tests may not be performed. Furthermore, terminal-initiated beam reporting can be processed more quickly than standard CSI reporting due to its simpler computational complexity.

[0251] Based on the above-mentioned reasons, a method for determining CPU occupancy time independent of CSI reference resources may be applied for terminal-initiated beam reporting. Specifically, the CPU occupancy time may be determined as the time interval from the first symbol of the earliest of each CSI-RS / CSI-IM / SSB resource for channel measurement or interference measurement to the last symbol of the next (e.g., the nearest future) potential UL channel, for the latest CSI-RS / CSI-IM / SSB opportunity that is earlier than the first symbol of the next (e.g., the nearest future) potential UL channel.

[0252] FIG. 12 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0253] Referring to FIG. 12, regardless of the CSI reference resource, the CPU occupancy time can be determined as the time interval from the first symbol of the closest CMR preceding the potential UL channel to the last symbol of the potential UL channel. In this case, the CPU occupancy time can be reduced somewhat compared to the case of FIG. 11.

[0254] Additionally, in order to prevent the CPU occupancy time from becoming too small, the CPU occupancy time may be determined as the time interval from the first symbol of the earliest of each CSI-RS / CSI-IM / SSB resource for channel measurement or interference measurement to the last symbol of the next (e.g., the nearest future) potential UL channel, for the latest CSI-RS / CSI-IM / SSB opportunity that is earlier than X symbols before the first symbol of the next (e.g., the nearest future) potential UL channel. In this case, the CPU occupancy time may start at least X+1 symbols before the start of the potential UL channel. Here, the value of X may be reported by the terminal as capability information, set / provided to the terminal by the base station, or determined / defined as a fixed value. The CPU occupancy time illustrated in FIG. 12 may be for the case where the value of X is 0.

[0255] (Example 1-5)

[0256] As described above in Example 1-4, the terminal-initiated beam report assumes PDSCH reception and reports only the RSRP and / or SINR values ​​of the measured channel / interference, regardless of the calculated CQI. Therefore, the aforementioned requirement test may not be performed. Furthermore, the terminal-initiated beam report may be processed more quickly than a typical CSI report due to its simpler calculations.

[0257] Based on this, the method proposed in Example 1-3 may be applied, but a method of defining CSI reference resources closer to potential UL channels than the existing method by taking these characteristics into account may be additionally considered.

[0258] For example, the existing CSI reference resource is slot nn based on CSI reporting slot n. CSI_ref can be determined using n CSI_refcan be set to a minimum value of 4*2^(μ_DL), 5*2^(μ_DL), or floor(Z' / N^slot_symb) depending on the CSI reporting conditions. In the present disclosure, n is set to a value smaller than this minimum value (e.g., 1*2^(μ_DL), 2*2^(μ_DL), etc.). CSI_ref By setting / defining the minimum value of , the CSI reference resource can be defined closer to the potential UL channel than in the conventional case. Additionally or alternatively, by omitting the check for whether it is a valid DL slot (e.g., by always assuming it is valid), the CSI reference resource can be defined closer to the potential UL channel than in the conventional case.

[0259] FIG. 13 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0260] Referring to FIG. 13, compared to the case of FIG. 11, the CSI reference resource can be defined closer to the potential UL channel. As a result, the CPU occupancy time can be reduced compared to the case of FIG. 11.

[0261] (Example 1-6)

[0262] In the proposed schemes described above (e.g., embodiments 1-3 to 1-5), the CPU occupancy time can be determined using the latest CSI-RS / CSI-IM / SSB opportunity that exists at or before a specific point in time (e.g., the first symbol of a CSI reference resource or a potential UL channel).

[0263] In this regard, if the start point of CPU occupancy is determined solely by the most recent opportunity, terminal-initiated beam reporting may be somewhat unreliable. This is because the event determination and report quantity are calculated for each measurement resource (e.g., CMR / IMR resource) based on the most recent opportunity.

[0264] For example, suppose that the RSRP of a CMR measured in the most recent opportunity exceeds a threshold (e.g., because an event condition is met), causing a UE-initiated beam report to be performed. In this case, if the most recent opportunity met the event condition, but the event condition was not consistently met prior to the most recent opportunity, the value reported by the UE-initiated beam report may not be a stable value. This is simply because the event may have been met only once, exceptionally, in the most recent opportunity.

[0265] Therefore, it may be stable / desirable to perform event determination and report calculation by monitoring multiple opportunities for a time interval with a longer term. Considering this, in the methods for determining CPU occupancy time described above in the present disclosure, a method of changing "the most recent CSI-RS / CSI-IM / SSB opportunity" to "the kth most recent CSI-RS / CSI-IM / SSB opportunity" may be applied. Based on this, the start point of the CPU occupancy time may be determined using the kth most recent CSI-RS / CSI-IM / SSB opportunity.

[0266] FIG. 14 illustrates another example of CPU occupancy time for terminal initiation beam reporting according to an embodiment of the present disclosure.

[0267] Referring to Figure 14, the start point of the CPU occupancy time can be determined using the second most recent CSI-RS / CSI-IM / SSB opportunity. In this case, the CPU occupancy time increases compared to the case of Figure 12, and the terminal can perform event determination and report volume calculation using two CMR opportunities existing within the CPU occupancy time.

[0268] (Example 1-7)

[0269] To address the shortcomings of the aforementioned proposed methods (e.g., Embodiments 1-1 and 1-2), the CPU occupancy time may be determined as the time interval from X symbols before the last symbol of the next (e.g., the nearest future) potential UL channel to the last symbol of the next potential UL channel. Consequently, the CPU may be occupied for X symbols.

[0270] In this regard, the base station needs to configure the measurement resources (e.g., CMR and / or IMR) to have more than one opportunity per resource during the CPU occupancy time so that the terminal can detect events and calculate the amount of reporting during the CPU occupancy time. In addition, the X value can be reported by the terminal as capability information, or can be configured / provided to the terminal by the base station, or can be determined / defined as a fixed value.

[0271] At this time, the X value can be set differently depending on the CSI and / or beam reporting settings. For example, a large X value can be applied when a high amount of association is required, and a small X value can be applied when a low amount of computation is required. The amount of computation can vary depending on the event or the number of measurement RSs of the measurement resource (e.g., CMR and / or IMR).

[0272] For the proposed methods described in Example 1, the base station can basically count CPU usage assuming an event has occurred regardless of whether the event actually occurred. However, if the base station can predict when an event will not occur, a method of counting CPU usage only when an event has occurred can be considered. Based on this, the terminal can utilize the CPU for other purposes before the actual event occurs. To this end, the base station can configure behavior / information regarding whether to count CPU usage assuming an event has occurred regardless of whether the event actually occurred, or only when an event has occurred.

[0273] Example 2

[0274] This embodiment relates to a method for setting the number of CPUs to be occupied during a CPU occupancy time for one terminal initiation beam report setting.

[0275] (Example 2-1)

[0276] Sets Y CPUs to be occupied for one terminal-initiated beam report configuration, and the Y value can be reported as capability information by the terminal, set / provided to the terminal by the base station, or determined / defined as a fixed value. For example, in the case of a conventional beam report (e.g., network-initiated beam report), the Y value is set to 1.

[0277] For terminal-initiated beam reports, since additional operations are required for the terminal to perform event monitoring, it may be efficient / desirable for the Y value to be set to a value greater than or equal to 1 or a value greater than 1. Additionally, when multiple terminal-initiated beam reports are set and the complexity of the events in each report is different, a different Y value may be set for each report.

[0278] Additionally, the terminal may report information about the number of terminal-initiated beam reports that can be configured or activated simultaneously as terminal capability information. In the case of terminal-initiated beam reporting, the terminal must continuously perform event monitoring and, if necessary, store the event result and report amount values ​​in a buffer (until reported via the UL channel). This operation may be more complex compared to conventional beam reporting, and the complexity may increase as the number of terminal-initiated beam reports that must be managed simultaneously increases. Therefore, the terminal may report information about the number of terminal-initiated beam reports that can be configured simultaneously to the base station as terminal capability information, and the base station may configure / provide terminal-initiated beam reports to the terminal in a number that can be supported by the terminal (e.g., a value less than or equal to the number reported by the terminal) based on the information.

[0279] (Example 2-2)

[0280] In addition, instead of the existing CPU, a processing unit for UE initiated beam report purposes (hereinafter referred to as UPU (UE initiated beam report Processing Unit) for convenience of explanation) may be separately set up, and may be set to occupy one or more UPUs for each UE initiated beam report. In this case, the method for determining the CPU occupancy time described above in the present disclosure (e.g., embodiment 1) may be replaced and applied to the UPU occupancy time.

[0281] Because terminal-initiated beam reporting requires additional computation for the terminal to perform event monitoring, it may be efficient to define a UPU separate from the existing CPU.

[0282] In this regard, the terminal can report UPU capability information to the base station separately from CPU capability information. The aforementioned UPU can be utilized for occupancy handling between various types of event-based reports (e.g., beam / CSI / UCI reports). For example, if more UPUs are simultaneously used / occupied than the maximum UPU value, some reports may be dropped.

[0283] Example 3

[0284] This embodiment relates to a method for setting / determining CPU occupancy time in a 2-step based terminal initiation beam report.

[0285] Specifically, the terminal initiated beam report reports whether an event has occurred (1 st Step) and report on the quantity of beam reports when an event occurs (2 nd Step) can be performed in two stages by time division multiplexing (TDM). For example, the amount of beam reporting can include CRI, SSB index, L1-RSRP, and / or L1-SINR.

[0286] In this regard, 1 st Step 2 nd 1 from the potential UL channel for reporting beam quantity of the step st It may mean the end of the potential UL channel for reporting the presence or absence of an event in the step, or (if it is the first potential UL channel) from the first measurement resource (e.g., CMR and / or IMR) to the end of the potential UL channel for reporting the presence or absence of an event. In addition, 2 nd Step 1 st 2 After the potential UL channel for reporting the presence or absence of an event in the step nd This may mean the end point of a potential UL channel for reporting beam quantity of a step.

[0287] For example, when an event occurs, the terminal can request the base station to schedule beam reporting (via SR or RACH, etc.). Thereafter, the base station can schedule a UL channel for beam quantity reporting via DCI, and the terminal can perform beam reporting via the corresponding UL channel. Alternatively, when an event occurs, the terminal can report whether the event has occurred to the base station (via SR, RACH, PUCCH, PUSCH, etc.), and if the event has occurred, can perform beam reporting later via a UL channel (pre-configured or determined by the terminal) (e.g., a potential UL channel described above in the present disclosure).

[0288] Below, various methods for setting CPU occupancy time in the aforementioned two-step based terminal initiation beam reporting are described.

[0289] (Example 3-1)

[0290] 1 st The CPU occupancy time can be determined by applying the method described in Example 1 in step 2. nd At this stage, the terminal does not occupy the CPU, and the CPU occupancy time can be 0.

[0291] Terminal 1 st Event detection is performed using the CPU in step 2, and calculations for the beam amount are completed. nd In step 1 st Since the calculated value in the step is reported as is, separate CPU usage may not be necessary.

[0292] (Example 3-2)

[0293] Contrary to Example 3-1, 1 st For steps, the terminal does not occupy the CPU, and the CPU occupancy time can be 0.

[0294] In this regard, 1 stIn this step, the terminal can perform event detection using a separate processing unit (e.g., EPU) for event detection. The terminal can report information on the number of simultaneously detectable events to the base station as capability information, and the base station can configure the terminal-initiated beam reporting to enable simultaneous event detection within that limit.

[0295] 2 nd In step 2, the CPU occupancy time can be determined by applying the method described in Example 1. The terminal that reported the occurrence of the event is 2 nd The calculation of the beam quantity can be performed using the CPU at step 2. Alternatively, nd In step 1, instead of the method described in Example 1 st Immediately after completing the potential UL channel transmission of step 2 nd The time interval to the potential UL channel of the step may also be determined by the CPU occupancy time.

[0296] (Example 3-3)

[0297] 1 st The starting point of CPU occupancy time can be determined by applying the method described in Example 1 in step 2. nd The end point of the CPU occupancy time can be determined by applying the method described in Example 1 in step 1.

[0298] That is, 1 st Occupancy of the CPU begins at step 2 nd The CPU may be occupied up to the potential UL channel where the step report is performed.

[0299] (Example 3-4)

[0300] 1 st The start and end points of CPU occupancy time can be determined by applying the method described in Example 1 in step 2. ndThe start and end points of the CPU occupancy time can be determined by applying the method described in Example 1 in step 1.

[0301] That is, 1 st Step and 2 nd For each step, the CPU occupancy time can be determined by applying the method described in Example 1. At this time, 1 st From the UL channel report in step 2 nd It can be returned in the time interval before the step starts occupying the CPU.

[0302] FIG. 15 illustrates a configuration of CPU occupancy time in a two-step-based terminal initiation beam report according to an embodiment of the present disclosure.

[0303] Referring to FIG. 15, a case in which the CPU occupancy time determination method of the aforementioned embodiment 1-6 is applied to a two-step-based terminal initiation beam reporting method is described as a representative example.

[0304] For example, in the case of Example 3-1, the CPU occupancy time for terminal initiation beam reporting can be determined as the time interval up to the potential UL channel based on the second most recent CMR before the potential UL channel for event reporting.

[0305] For example, in the case of Example 3-2, the CPU occupancy time for terminal initiation beam reporting can be determined as the time interval up to the potential UL channel based on the second most recent CMR before the potential UL channel for beam quantity reporting.

[0306] For example, in the case of Example 3-3, the CPU occupancy time for terminal initiated beam reporting can be determined as the time interval from the second most recent CMR before the potential UL channel for event reporting to the potential UL channel for beam quantity reporting.

[0307] For example, in the case of embodiment 3-4, the CPU occupancy time for terminal-initiated beam reporting may include a first CPU occupancy time related to event reporting and a second CPU occupancy time related to beam quantity reporting. The first CPU occupancy time may be determined as a time interval to the potential UL channel based on the second most recent CMR prior to the potential UL channel for event reporting. In addition, the second CPU occupancy time may be determined as a time interval to the potential UL channel based on the second most recent CMR prior to the potential UL channel for beam quantity reporting.

[0308] With respect to the proposed method of Example 3, each step (e.g., 1 st Step 2 nd The potential UL channel used to determine the CPU occupancy time of a step may be a UL channel reporting the presence or absence of an event or a UL channel reporting the amount of beams.

[0309] Also, with respect to the proposed method of Example 3, 1 st In step 2, the terminal reported the event to the base station. nd At this stage, the base station can already know whether an event has occurred. Therefore, if an event has occurred, the proposed method of Example 3 is used / applied, and if an event has not occurred, 1 st From the start of the CPU occupancy of the step 1 st The CPU is occupied until the UL channel report of the step is finished, 2 nd During this stage, the CPU may not be occupied.

[0310] Also, with respect to the proposed method of Example 3, 1 st Step and 2 nd When applying the method of Example 1 and / or Example 2 to each step, the specific method may be different. For example, 1 st Step and 2 ndIn each step, Examples 1-6 and 1-5 may be applied, and Examples 2-2 and 2-1 may be applied, respectively. In addition, 1 st Step and 2 nd The number of CPUs occupied by a step (e.g., the Y value) can also be set differently. For example, 1 st A high Y value (e.g. greater than 1) is set in the step, and 2 nd A step may have a low Y value (or vice versa). This is because the computation required to monitor an event and the computation required to calculate the amount of reporting when an event occurs may differ. If Y values ​​for both steps are restricted to be the same, this can waste CPU time, as each step must determine the maximum Y value actually required.

[0311] In addition, in relation to the proposed method of the present disclosure, for the 2-step based terminal initiated beam reporting, the measurement resources (e.g., CMR and / or IMR) for verifying / detecting whether an event has occurred (e.g., event monitoring) and the measurement resources (e.g., CMR and / or IMR) for calculating beam quantity may be different. Here, the verification / detection of whether an event has occurred may be performed in one of the 2-step based terminal initiated beam reporting. st corresponds to the step, and the beam quantity calculation is 2 nd It corresponds to the stage.

[0312] For example, event(s) related to terminal initiation beam reporting may be defined as follows:

[0313] - Event 1: Current beam quality is worse / lower than a certain threshold.

[0314] - Event 2: At least one new beam, such as L1-RSRP, has a better / higher threshold quality than the current beam.

[0315] - Event 3: The quality of the new beam is better / higher than a certain threshold.

[0316] - Event 4: The quality of the current beam is worse / lower than threshold 1, and the quality of at least one new beam is better / higher than threshold 2.

[0317] - Event 7: At least one new beam, such as L1-RSRP, has a quality better / higher threshold than the RS derived from the activated TCI state with the Qth best quality.

[0318] In relation to the above-mentioned event(s), the current beam refers to the beam currently in use, which may correspond to a QCL source RS set in the TCI state indicated by the base station to the terminal, or an SSB in a QCL relationship with the QCL source RS. In addition, a new beam may be separately set by the base station to the terminal for event inspection (e.g., detecting / monitoring whether an event has occurred).

[0319] For example, for event 1, the CMR for event monitoring is set to the current beam, but the CMR for beam quantity calculation can be set to a beam set (e.g., CSI-RS for beam management, or SSB) that may or may not include the current beam. In this case, beam quantity calculation is not performed in the event monitoring phase, and beam quantity calculation for beam reporting can be performed only when an event occurs. Therefore, in this case, 1 st Number of CPUs and occupancy time of the step and 2 nd Even if the number of CPUs and the occupancy time of the steps are determined in different (or the same) ways, 2 nd The number of CPUs and the time taken for each step are 1 st Determined as a non-zero value only if an event occurred in the step, and 1 st If no event occurs at a step, it can be determined as 0.

[0320] In addition, in the 2-step based terminal initiated beam report, if the measurement resources for event monitoring (e.g., CMR and / or IMR) and the measurement resources for beam quantity calculation are the same, the beam quantity calculation for event monitoring may have already been completed, so 1 as in the aforementioned embodiment 3-1. st The CPU can be occupied only in step 2 nd In this case, the CPU may not be occupied.

[0321] Additionally, in relation to the proposed methods of the present disclosure, measurement resources (e.g., CMR and / or IMR) may be directly configured for terminal-initiated beam reporting, but other than that, the current beam, etc. may be used as measurement resources for event monitoring / verification and beam reporting. For example, the base station may directly configure measurement resources (e.g., CMR and / or IMR) in the CSI report configuration information element (CSI report config IE) for terminal-initiated beam reporting.

[0322] FIG. 16 illustrates an example of a CPU occupancy time configuration for a two-step-based terminal-initiated beam report according to an embodiment of the present disclosure.

[0323] Referring to Fig. 16, 1 st The CPU occupancy time for the step is determined / set based on Example 1-2, and 2 nd The CPU occupancy time for a step can be determined / set based on Example 1-3.

[0324] Specifically, 2 nd For the step, the proposed method of Example 1-3 can be applied since it can be similar to the existing periodic beam report, and the number of occupied CPUs can also be assumed to be 1.

[0325] Also, 1 st For the step, the proposed method of Example 1-2 may be applied efficiently since event monitoring / verification can be performed in multiple measurement resource opportunities. That is, 1st For the step, it may be efficient / desirable to set / determine the CPU occupancy time as the time interval from the first measurement resource opportunity after the potential UL channel before the event reporting (or from the first measurement resource opportunity if the event reporting is performed for the first time) until the event reporting is performed. 1 st For each step, we can also assume that the number of CPUs occupied is 1.

[0326] FIG. 17 illustrates another example of CPU occupancy time configuration for a two-step based terminal initiation beam report according to an embodiment of the present disclosure.

[0327] Referring to Fig. 17, a method of applying the proposed method of the aforementioned embodiment 3-3 for a longer period of time may be considered.

[0328] Specifically, the start point of CPU occupancy can be determined based on the time of event reporting, which can be determined as the first measurement resource opportunity following a potential UL channel prior to the event reporting (or the first measurement resource opportunity if the event is first reported). Furthermore, the end point of CPU occupancy can be determined based on the completion of reporting on the beam quantity.

[0329] Based on this, the terminal performs event monitoring / verification and beam quantity calculation using the first measurement resource that appears / exists after the beam quantity report is completed, and can return the CPU once the beam quantity report is completed.

[0330] The base station recognizes the CPU occupancy status of the terminal based on the method / operation described above in the present disclosure, and can perform efficient and stable CPU allocation / operation based on this.

[0331] FIG. 18 and FIG. 19 illustrate terminal operation and base station operation in relation to a method of defining / setting / determining CPU occupancy time and / or CPU occupancy count according to the embodiments of the present disclosure described above.

[0332] FIG. 18 is a drawing for explaining the operation of a terminal according to an embodiment of the present disclosure.

[0333] Referring to FIG. 18, the terminal can receive settings for CSI reporting from the base station (S1810).

[0334] For example, the configuration for the corresponding CSI report may include configuration information for the terminal initiated beam report described above in the present disclosure.

[0335] The terminal can report first information on whether an event related to the corresponding CSI report is detected to the base station (S1820).

[0336] For example, the report of the first information is 1 in the terminal initiated beam report based on the 2-step described above in the present disclosure. st It may correspond to a stage.

[0337] When an event is detected, the terminal can report second information about the report quantity related to the corresponding CSI report to the base station (S1830).

[0338] For example, the reporting of the second information is 2 in the 2-step based terminal initiated beam reporting described above in the present disclosure. nd It may correspond to a stage.

[0339] The reporting quantity may correspond to a power measurement value for a reference signal set as a measurement resource based on a setting for CSI reporting. That is, the reporting quantity may correspond to a received power measurement value (e.g., L1-RSRP, L1-SINR, etc.) based on a beam / spatial filter (e.g., CSI-RS resource indicator (CRI), SSB index (or SSB resource indicator). For example, in a measurement based on the present disclosure, a spatial filter may be associated with at least one of an index / ID / indicator of a CSI-RS resource (based on a QCL relationship) or an SSB index (or an index / ID / indicator of a SSB resource).

[0340] In this regard, the CPU occupancy time for the corresponding CSI report may be based on at least one of the first CPU occupancy time for reporting the first information in step S1820 or the second CPU occupancy time for reporting the second information in step S1830.

[0341] For example, according to the present disclosure, the CPU occupancy time for CSI reporting corresponds to the first CPU occupancy time, and the CPU for reporting the second information may not be occupied by the terminal (see, e.g., Example 3-1). That is, in this case, the second CPU occupancy time is 0. Such CPU occupancy time may be efficient when the measurement resource settings for reporting the first information and the measurement resource settings for reporting the second information are the same.

[0342] For another example, according to the present disclosure, the CPU occupancy time for CSI reporting corresponds to the second CPU occupancy time, and the CPU for reporting the first information may not be occupied by the terminal (see, for example, embodiment 3-2). That is, in this case, the second CPU occupancy time is 0. In this regard, at least one (separate) processing unit for detecting the aforementioned event may be set for the terminal, and the at least one processing unit may be set based on capability information regarding the number of events that can be detected simultaneously by the terminal.

[0343] As another example, according to the present disclosure, the CPU occupancy time for CSI reporting may correspond to a time interval from the start time of the first CPU occupancy time to the end time of the second CPU occupancy time (see, e.g., Example 3-3).

[0344] As another example, according to the present disclosure, the CPU occupancy time for CSI reporting may correspond to the first CPU occupancy time and the second CPU occupancy time (see, e.g., Example 3-4). In this case, the terminal does not occupy the CPU during the time period between the end of the first CPU occupancy time and the start of the second CPU occupancy time.

[0345] In relation to the above-described operations and examples(s), the CPU occupancy time may be determined / set based on a predefined rule (e.g., the method(s) proposed in Embodiment 1) for at least one of the first CPU occupancy time or the second CPU occupancy time.

[0346] In this regard, the same rules may apply to the first CPU occupancy time and the second CPU occupancy time, or different rules may apply.

[0347] For example, at least one of the first CPU occupancy time or the second CPU occupancy time may be based on a rule that defines the CPU occupancy time as the time from the first symbol of the earliest measurement resource located after the last symbol of the uplink channel on which the first report was performed in the time domain to the last symbol of the uplink channel on which the second report following the first report is to be performed (see, for example, embodiment 1-2).

[0348] For example, at least one of the first CPU occupancy time or the second CPU occupancy time may be based on a rule that defines the CPU occupancy time as the time from the first symbol of the closest measurement resource that is not later than the CSI reference resource associated with the report in the time domain to the last symbol of the uplink channel on which the report is to be performed (see, for example, embodiment 1-3).

[0349] Additionally, according to the present disclosure, the number of CPUs to be occupied for CSI reporting may be set to a value greater than or equal to 1 based on the complexity of the aforementioned event. In this regard, the number of CPUs to be occupied for reporting the first information may be set differently from the number of CPUs to be occupied for reporting the second information.

[0350] The method described in the example of FIG. 18 can be performed by the first device (100) of FIG. 20. That is, the terminal of FIG. 18 can be implemented as the first device (100). For example, one or more processors (102) of the first device (100) of FIG. 20 can be configured to receive settings for CSI reporting through one or more transceivers (106), report first information on whether an event related to the corresponding CSI report is detected, and report second information on the amount of reporting related to the corresponding CSI report when the event is detected.

[0351] Furthermore, one or more memories (104) of the first device (100) may store instructions for performing the method described in the example of FIG. 18 or the examples described above when executed by one or more processors (102).

[0352] FIG. 19 is a diagram for explaining the operation of a base station according to an embodiment of the present disclosure.

[0353] Referring to FIG. 19, the base station can transmit settings for CSI reporting to the terminal (S1910).

[0354] For example, the configuration for the corresponding CSI report may include configuration information for the terminal initiated beam report described above in the present disclosure.

[0355] The base station can receive first information from the terminal regarding whether an event related to the corresponding CSI report has been detected (S1920).

[0356] For example, the report of the first information is 1 in the terminal initiated beam report based on the 2-step described above in the present disclosure. st It may correspond to a stage.

[0357] If an event is detected, the base station can receive second information about the report quantity related to the corresponding CSI report from the terminal (S1930).

[0358] For example, the reporting of the second information is 2 in the 2-step based terminal initiated beam reporting described above in the present disclosure. nd It may correspond to a stage.

[0359] The reporting quantity may correspond to a power measurement value for a reference signal set as a measurement resource based on a setting for CSI reporting. That is, the reporting quantity may correspond to a measurement value (e.g., L1-RSRP, L1-SINR, etc.) based on a beam / spatial filter (e.g., CSI-RS resource indicator (CRI), SSB index (or SSB resource indicator). For example, in a measurement based on the present disclosure, a spatial filter may be associated with at least one of an index / ID / indicator of a CSI-RS resource (based on a QCL relationship) or an SSB index (or an index / ID / indicator of a SSB resource).

[0360] In this regard, the CPU occupancy time for the corresponding CSI report may be based on at least one of the first CPU occupancy time for reporting the first information in step S1920 or the second CPU occupancy time for reporting the second information in step S1930.

[0361] Specific characteristics such as CPU occupancy time, CPU occupancy count, and measurement resources for reporting are the same as those described with reference to Fig. 18, so redundant descriptions are omitted.

[0362] The base station can recognize the CPU occupancy status of the terminal based on the method / operation described above, and can allocate / operate the CPU efficiently and stably based on this.

[0363] The method described in the example of FIG. 19 can be performed by the second device (200) of FIG. 20. That is, the base station of FIG. 19 can be implemented as the second device (200). For example, one or more processors (202) of the second device (200) of FIG. 20 can be configured to transmit, through one or more transceivers (206), a setting for a CSI report, receive first information regarding whether an event related to the corresponding CSI report has been detected, and, if an event has been detected, receive second information regarding a report amount related to the corresponding CSI report.

[0364] Furthermore, one or more memories (204) of the second device (200) may store instructions for performing the method described in the example of FIG. 19 or the examples described above when executed by one or more processors (202).

[0365] While the proposed methods of this disclosure have been described using beam reporting as a representative example, they can also be extended and applied to CSI reporting (e.g., CRI, RI, PMI, CQI reporting, etc.). That is, the methods proposed in this disclosure can be utilized even when UE-initiated CSI reporting is supported in addition to UE-initiated beam reporting. Furthermore, the methods proposed in this disclosure can also be utilized when calculating / reporting CSI, beam, and / or other UCI in new wireless communication technologies (e.g., 6G, etc.).

[0366] Additionally, in the proposed methods of the present disclosure, when a terminal requests the base station to schedule a UL channel for a specific CSI report or beam report upon occurrence of an event related to the CSI report or beam report, this can be interpreted as the terminal notifying the base station that the event has occurred. At this time, whether or not actual UL channel scheduling is performed can be determined by the base station.

[0367] Additionally, in the proposed methods of the present disclosure, ID may be interpreted as having the same meaning as an index, and CMR and / or IMR may mean a CMR and / or IMR set for terminal-initiated beam reporting.

[0368] Additionally, in the proposed methods of the present disclosure, ' / ' can be interpreted as 'and', 'or', or 'and / or' depending on the context.

[0369] Additionally, the 'beam' described in the proposed methods of the present disclosure may mean a source RS for a spatial filter or a spatial relation, and may be interpreted as a QCL (type-D) RS, a (DL / UL / joint) TCI state, or a spatial relation RS (in case of UL).

[0370] General devices to which the present disclosure may be applied

[0371] FIG. 20 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0372] Referring to FIG. 20, the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G).

[0373] A first 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 memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure.

[0374] For example, the processor (102) may process information in the memory (104) to generate first information / signal and then transmit a wireless signal including the first information / signal through the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal through the transceiver (106) and then store information obtained from signal processing of the second information / signal in the memory (104).

[0375] The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0376] The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0377] Hereinafter, the hardware elements of the 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 PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.

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

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

[0380] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, 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 received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0381] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0382] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics of the present disclosure. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0383] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

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

[0385] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A, 5G, and 6G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A, 5G, and 6G systems.

Claims

1. A step of receiving, by a terminal, a setting for reporting channel state information (CSI) from a base station; A step of reporting first information on whether an event related to the CSI report is detected to the base station by the terminal; and Based on the detection of the above event, the terminal comprises a step of reporting second information about the report quantity related to the CSI report to the base station, The above reporting quantity relates to the power measurement value for the reference signal set as the measurement resource based on the above settings, A method wherein the CSI processing unit (CPU) occupancy time for the above CSI report is based on at least one of the first CPU occupancy time for the report of the first information or the second CPU occupancy time for the report of the second information.

2. In paragraph 1, A method wherein the CPU occupancy time for the above CSI report corresponds to the first CPU occupancy time, and the CPU for reporting the second information is not occupied by the terminal.

3. In paragraph 2, A method in which the measurement resource settings for reporting the first information and the measurement resource settings for reporting the second information are set identically.

4. In paragraph 1, A method wherein the CPU occupancy time for the above CSI report corresponds to the second CPU occupancy time, and the CPU for reporting the first information is not occupied by the terminal.

5. In paragraph 4, At least one processing unit is set for detecting the event for the above terminal, A method wherein said at least one processing unit is set based on capability information about the number of events that can be simultaneously detected by said terminal.

6. In paragraph 1, A method wherein the CPU occupancy time for the above CSI report corresponds to a time interval from the start time of the first CPU occupancy time to the end time of the second CPU occupancy time.

7. In paragraph 1, The CPU occupancy time for the above CSI report corresponds to the first CPU occupancy time and the second CPU occupancy time, A method wherein the CPU is not occupied by the terminal during a time period between the end time of the first CPU occupancy time and the start time of the second CPU occupancy time.

8. In paragraph 1, A method wherein at least one of the first CPU occupancy time or the second CPU occupancy time is based on a rule that defines the CPU occupancy time as the time from the first symbol of the earliest measurement resource located after the last symbol of the uplink channel on which the first report was performed in the time domain to the last symbol of the uplink channel on which the second report following the first report is to be performed.

9. In paragraph 1, A method wherein at least one of the first CPU occupancy time or the second CPU occupancy time is based on a rule that defines the CPU occupancy time as the time from the first symbol of the closest measurement resource that is not later than the CSI reference resource related to the report in the time domain to the last symbol of the uplink channel on which the report is to be performed.

10. In paragraph 1, A method wherein the number of CPUs to be occupied for the above CSI report is set to a value greater than or equal to 1 based on the complexity of the above event.

11. In paragraph 10, A method wherein the number of CPUs to be occupied for reporting the first information is set differently from the number of CPUs to be occupied for reporting the second information.

12. In paragraph 1, Based on the CSI-RS being set as a measurement resource for the above CSI report, the spatial filter for the above reference signal is related to the index of the CSI-RS resource, A method wherein, based on SSB being set as a measurement resource for the above CSI report, a spatial filter for the above reference signal is related to an index of the SSB resource.

13. One or more transceivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Receives a setting for channel state information (CSI) reporting from a base station through one or more of the above transceivers; Reporting first information on whether an event related to the CSI report is detected to the base station through the one or more transceivers; Based on the detection of the above event, the second information about the report quantity related to the CSI report is set to be reported to the base station through the one or more transceivers, The above reporting quantity relates to the power measurement value for the reference signal set as the measurement resource based on the above settings, A device wherein the CSI processing unit (CPU) occupancy time for the above CSI report is based on at least one of the first CPU occupancy time for the report of the first information or the second CPU occupancy time for the report of the second information.

14. A step of transmitting settings for reporting channel state information (CSI) to a terminal by a base station; A step of receiving, by the base station, first information on whether an event related to the CSI report is detected from the terminal; and Based on the detection of the above event, the step of receiving, by the base station, second information about the report quantity related to the CSI report from the terminal, The above reporting quantity relates to the power measurement value for the reference signal set as the measurement resource based on the above settings, A method wherein the CSI processing unit (CPU) occupancy time for the above CSI report is based on at least one of the first CPU occupancy time for the report of the first information or the second CPU occupancy time for the report of the second information.

15. One or more transceivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Transmitting a setting for reporting channel state information (CSI) to a terminal through one or more of the above transceivers; Through said one or more transceivers, receiving from said terminal first information on whether an event related to said CSI report has been detected; Based on the detection of the above event, the second information on the report quantity related to the CSI report is set to be received from the terminal through the one or more transceivers, The above reporting quantity relates to the power measurement value for the reference signal set as the measurement resource based on the above settings, A device wherein the CSI processing unit (CPU) occupancy time for the above CSI report is based on at least one of the first CPU occupancy time for the report of the first information or the second CPU occupancy time for the report of the second information.

16. One or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 12 based on execution by said one or more processors.

17. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to perform a method according to any one of claims 1 to 12.

Images