Method and apparatus for transmitting and receiving channel state information

Abstract

A method according to an embodiment of the present disclosure comprises the steps of: receiving configuration information; receiving information indicating a first resource for measurement among a plurality of resources; receiving information indicating a second resource for reporting; and transmitting channel state information (CSI). The plurality of resources related to different numbers of ports are configured on the basis of the configuration information. The CSI includes i) information related to the second resource and / or ii) information related to UE preference at a future time point.

Description

Method for transmitting and receiving channel status information and apparatus thereof

[0001] This specification relates to a method for transmitting and receiving channel status information and an apparatus thereof.

[0002] Mobile communication systems were developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include data services as well as voice. Currently, due to the explosive increase in traffic leading to resource shortages and users demanding higher-speed services, more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems largely include the ability to accommodate explosive data traffic, a dramatic increase in transmission rates per user, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, such as dual connectivity, massive multiple input multiple output (MMIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] Meanwhile, in Rel-18 NES (Network Energy Saving), the concept of sub-configuration was introduced into CSI report settings, and standardization was carried out to help with power domain and spatial domain energy saving at the base station side.

[0005] The aforementioned sub-configuration-based CSI reporting presents the following problems. In the case of periodic reporting, there are overhead and terminal complexity issues as the terminal must perform CSI reporting for all sub-configurations. In the case of semi-persistent and aperiodic reporting, the base station must configure or instruct the terminal via MAC CE / DCI on which sub-configuration to report CSI for; however, it is difficult for the base station to determine which sub-configuration has a favorable channel environment.

[0006] The purpose of this specification is to propose a method for solving the aforementioned problems.

[0007] The technical problems to be solved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0008] A method according to one embodiment of the present specification for solving the aforementioned problem comprises the steps of receiving configuration information, receiving information representing a first resource for measurement among a plurality of resources, receiving information representing a second resource for reporting, and transmitting Channel State Information (CSI). Based on the configuration information, the plurality of resources associated with different numbers of ports are configured. The CSI is characterized by including i) information associated with the second resource and / or ii) information associated with a future terminal preference (UE preference).

[0009] Therefore, compared to cases where measurement and CSI reporting are performed for all resources (e.g., sub-configuration(s) based resources) (directed / activated by the base station) according to the existing method, signaling overhead can be reduced, and subsequent DL operations based on the CSI can be improved in terms of channel quality.

[0010] According to the embodiments of this specification, since a first resource for measurement and a second resource for reporting are indicated, the RS overhead required for terminal measurement can be reduced. Additionally, the base station can manage / determine the on / off of antenna ports of the resources and transmission power at a current or future point in time based on the second resource or information related to terminal preference, thereby contributing to network energy saving (NES).

[0011] The effects obtainable in this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0012] Figure 1 is a diagram illustrating the overall functions from the perspective of an AI / ML model.

[0013] Figure 2 illustrates a general form of an AI / ML-related procedure performed between a network and a terminal.

[0014] Figure 3 illustrates an example of AI / ML-based beam management operation.

[0015] Figure 4 illustrates an example of an AI / ML-based CSI measurement / reporting operation.

[0016] Figure 5 illustrates an example of an AI / ML-based positioning operation.

[0017] Figure 6 is a flowchart showing an example of a CSI-related procedure.

[0018] Figure 7 is a diagram illustrating a UE initiated reporting.

[0019] FIG. 8 is a flowchart illustrating a method according to one embodiment of the present specification.

[0020] FIG. 9 is a flowchart illustrating a method according to another embodiment of the present specification.

[0021] FIG. 10 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

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

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

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

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

[0026] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

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

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

[0029] Hereinafter, preferred embodiments according to the present specification will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present specification and is not intended to represent the only embodiment in which the present specification may be practiced. The following detailed description includes specific details to provide a complete understanding of the present specification.

[0030] In this specification, a terminal is a user-side device (user equipment, UE) or a consumer-side device, and may also be referred to as a first node that receives / transmits signals from / to a base station / second node / IAB node / Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to a user-side endpoint or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a terminal may correspond to a served node. A terminal may be a fixed-location node or a non-fixed-location (or mobile) node.

[0031] In this specification, a Base Station (BS) is a device on the network side and may also be referred to as a second node / IAB node / x-NodeB (x-NodeB, where x may be an abbreviation related to Radio Access Technology (RAT)) / Transmission-Reception Point (TRP). A Base Station may correspond to a physical node or a logical node. A Base Station may correspond to an endpoint on the network side or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a Base Station may correspond to a serving node. A Base Station may be a node with a fixed location or a node with an indefinite location.

[0032] In this specification, higher layer parameters may be set for the terminal, pre-set, or pre-defined. For example, a base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capability to the base station as higher layer parameters. For example, higher layer parameters may be transmitted via RRC (radio resource control) signaling or MAC (medium access control) signaling.

[0033] In this specification, information / state / parameters being "configured" or "pre-configured" may be interpreted as the information / state / parameters being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, information / state / parameters being "defined" or "pre-defined" may be interpreted as being known or stored in advance by the base station and the terminal without signaling between the base station and the terminal.

[0034] < AI / ML for Wireless Communication >

[0035] With the advancement of computing technology, artificial intelligence (AI) and machine learning (ML) are being adopted across various industries and technological fields. In the field of wireless communication, various discussions are underway regarding the application of AI models trained on ML; notably, the 3GPP standardization process refers to this as AI / ML. In this specification, we use the term "AI / ML" following the terminology currently in use during the 3GPP standardization discussions; however, "AI / ML" may be referred to by various other terms depending on the progress of standardization and implementation in the future. For example, it may be referred to as a "transmission / reception mode" or a "signal / channel / operation / transmission / reception configuration" set for AI / ML, but is not limited thereto. The meanings of the terms currently used in the 3GPP standardization process are briefly summarized as follows.

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

[0037] - Data collection: This is the process of collecting data necessary for AI / ML model training, data analysis, and inference from network nodes, management entities, or terminals.

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

[0039] - AI / ML Inference: This is the process of making predictions or deriving decisions based on collected data and AI models using trained AI models. Meanwhile, depending on whether the AI / ML model is configured on both the transmitting and receiving devices or on only one, it can be classified into (i) two-sided models and (ii) one-sided models. In the case of (i) two-sided models, cooperative inference is performed through paired AI / ML models. Cooperative inference refers to cooperation between the network and the UE, where one side performs part of the inference and the other performs the remainder. (ii) One-sided models are divided into UE-side models and network-side models. In the case of one-sided models, inference is performed entirely by the UE / network-side models.

[0040] 1. Life Cycle Management (LCM) for AI / ML models

[0041] For AI / ML models, LCM is a concept that encompasses all overall procedures for the model, such as data collection, model training, model deployment, model inference, model monitoring, and model updates.

[0042] Figure 1 is a diagram illustrating the overall functions from the perspective of an AI / ML model.

[0043] Referring to FIG. 1, a general AI / ML 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).

[0044] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) performs data preparation and can provide input data processed through data preparation.

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

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

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

[0048] The Management function (30) is a function that monitors the operation of an AI / ML model or an AI / ML function.

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

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

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

[0052] 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 the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (13) provided by the data collection function (10).

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

[0054] The Model Storage function (50) is a function that stores a trained / updated model that can be used to perform the Inference function (40).

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

[0056] 2. General AI / ML related procedures between the network and the terminal

[0057] Figure 2 illustrates the general form of AI / ML-related procedures performed between a network and a terminal. While Figure 1 examined the LCM from the perspective of an AI / ML model, Figure 2 describes the general form of procedures performed between a terminal and a network from the perspective of signaling / protocols.

[0058] (1) AI / ML related setup procedure

[0059] Referring to FIG. 2, an AI / ML-related configuration procedure may be performed between the network and the terminal (B05). The AI / ML-related configuration procedure may include information exchange through at least one upper-layer signaling between the terminal and the network, and / or prior preparation / subsequent operations at the terminal / network respectively before / after the upper-layer signaling.

[0060] Specifically, the configuration procedure related to AI / ML may include, but is not limited to, at least one of the following: (i) reporting the capability of the AI / ML-related terminal, (ii) data collection, (iii) model training, (iv) model delivery / transmission, (v) selection of AI / ML functions / models, and (vi) configuration of various operations performed based on the AI / ML model (e.g., AI / ML-based CSI / Positioning / Beam Management).

[0061] (i) The terminal can inform the network of its capabilities, such as models and functions related to AI / ML, that it supports through UE Capability reporting. The network can provide AI / ML-related settings to the terminal based on the terminal's capabilities related to AI / ML reported by the terminal.

[0062] (ii) AI / ML-related configuration procedures may include data collection related to the training / inference of AI / ML models and / or the provision of configuration information regarding data collection. The configuration information regarding data collection may relate to how to configure the method / operation of data collection.

[0063] (iii) AI / ML-related configuration procedures may include training AI / ML models online or offline and / or providing configuration information for AI / ML model training. The configuration information for AI / ML model training may relate to how to configure the method / behavior, etc., of training the AI / ML model.

[0064] (iv) AI / ML-related configuration procedures may include transmitting / transmitting configuration information for a model. The configuration information for a model may include parameters that constitute the AI / ML model and / or an identifier (ID) for the AI / ML model.

[0065] The provided AI / ML model may be a model trained by the network or a model that requires self-training at the terminal. Even when a model trained by the network is provided, the terminal may perform fine-tuning or retraining as necessary. Meanwhile, if a model trained by the network is provided, the terminal may provide data for training to the network.

[0066] (v) The configuration procedure related to AI / ML may include the configuration of how to select AI / ML Functionality / models and / or the selection process for AI / ML Functionality / models. In UE-side AI / ML models or two-sided AI / ML models, the selection of the UE part may be performed through instructions / signaling from the network or the terminal may select it itself. The selection of AI / ML Functionality / models may be performed when multiple AI / ML Functionality / models are configured / provided.

[0067] (vi) The configuration procedure related to AI / ML may include configuration information for various inference operations performed based on AI / ML models, e.g., AI / ML-based CSI measurement / reporting, AI / ML-based positioning, and / or AI / ML-based beam management.

[0068] (2) Operation based on inference by AI / ML models

[0069] Referring again to FIG. 2, the network and / or terminal can perform inference of the AI / ML model through the trained AI / ML model and perform various operations based on the inference of the AI / ML model (B10). If the AI / ML model is a one-sided model, the inference of the AI / ML model can be performed at either the network or the terminal where the AI / ML model is configured. If the AI / ML model is a two-sided model, each part of the inference of the AI / ML model can be performed at the network and the terminal, and depending on the implementation, such inference can be performed cooperatively between the network and the terminal.

[0070] (i) Actions performed based on the inference of an AI / ML model may include AI / ML-based CSI measurement / reporting. AI / ML-based CSI measurement / reporting is intended to improve CSI feedback and may be related to overhead reduction / CSI compression, accuracy improvement, and / or CSI prediction.

[0071] (ii) Actions performed based on the inference of an AI / ML model may include AI / ML-based beam management. AI / ML-based beam management may be related to beam prediction in the time domain, reduction of overhead / latency in the spatial domain, and / or improvement of beam selection accuracy.

[0072] (iii) Actions performed based on the inference of an AI / ML model may include AI / ML-based positioning. AI / ML-based positioning may be relevant to improving positioning accuracy in various scenarios, for example, in non-line-of-sight environments.

[0073] (3) Procedures for AI / ML management

[0074] The network and / or terminal can perform procedures for the management of AI / ML Functionality / model or the settings therefor (B15).

[0075] The network and / or terminal may perform monitoring of AI / ML Functionality / model during the AI / ML model inference or operation based thereon (B10) for the management procedure (B15).

[0076] The management procedure may include, for example, at least one of activation / deactivation, switching, model update, and / or fallback operation for AI / ML Functionality / model. For the signaling of the management procedure, various 3GPP signaling schemes, such as RRC, MAC-CE, DCI, etc., may be used.

[0077] As an example of model switching, multiple model groups are configured, and switching between them can be performed based on models having a common model structure or partially common substructures, and models within the same group may be associated with different input / output formats or processing.

[0078] Model updating involves modifying the parameters used by the model to suit channel conditions that change over time, and fine-tuning is an example of model updating.

[0079] Fallback: In a wireless communication system using an AI / ML model, this may refer to the operation of not using the AI / ML model or operating in a pre-configured / defined default mode when the reliability of the AI / ML model decreases due to internal or external environmental factors.

[0080] For example, the decision on whether to perform a management procedure can be made by the network. For instance, the network may decide to perform the management procedure upon network initiation, or the network may decide to perform the management procedure upon terminal initiation and request.

[0081] As another example, the decision on whether to perform a management procedure can be made by the terminal. For instance, the terminal's decision on the management procedure may be triggered when an event condition set by the network is satisfied, performed by reporting the terminal's decision to the network, or performed autonomously by the terminal.

[0082] 3. Specific operation examples based on AI / ML model inference

[0083] (1) Beam management

[0084] Figure 3 illustrates an example of AI / ML-based beam management operation.

[0085] Referring to FIG. 3, the network / terminal can perform a configuration procedure related to AI / ML-based beam management (C05). The network / terminal can perform a configuration procedure for an AI / ML model to be used for AI / ML-based beam management, and an exchange of configuration information for upper-layer signaling for AI / ML-based beam management. For example, at least one of information related to model inference, configuration for a first set / second set beam, monitoring performance, and assistance information for data collection and beam measurement may be signaled.

[0086] The network / terminal can perform measurements on the first set of beams (C10). The beam measurements may be related to RSRP measurements.

[0087] A network / terminal can obtain information about a second set of beams based on measurement results for a first set of beams (C15). For example, the network / terminal can perform AI / ML inference by using the measurement results for the first set of beams as AI / ML input data. Beam ID information may also be additionally provided as AI / ML input data. Information about the second set of beams may correspond to AI / ML output data. The AI / ML output data may be related to, for example, the probability that each beam will become a top-N beam, the predicted RSRP, etc., for predicting future beam quality, but is not limited thereto.

[0088] According to an embodiment, the network / terminal can transmit and receive information about the acquired second set of beams.

[0089] Specifically, AI / ML-based beam management operations may include at least one of the following BM-Case 1 and BM-Case 2.

[0090] - BM-Case 1: Prediction of the second set of DL beams in the spatial domain through the first set of beam measurements

[0091] - BM-Case 2: Prediction of the second set of DL beams in the time domain through the first set of beam measurements

[0092] In BM-Case 1 and / or 2, both AI / ML model training and inference may be performed on the network or on the terminal. The first set of beams and the second set of beams may be different beams. Or the first set of beams may be a subset of the second set of beams. Or, particularly in BM-Case 2, the first set of beams and the second set of beams may be the same beam.

[0093] The report corresponding to the inference of the UE-side model for BM-Case 1 may relate to the RSRP for the predicted top N beams. The report may include, for example, the predicted RSRP values, and as an example, the predicted RSRP values ​​may be reported together with the actual measured RSRP.

[0094] UE-side AI / ML model inference for BM-Case 2 can report inference results for N future time points through a single report. The report for each time point can correspond to the report in BM-Case 1.

[0095] For performance monitoring of the UE-side model for BM-Case 1 / 2, (i) network-side performance monitoring and / or (ii) UE-assisted performance monitoring may be supported. (i) For network-side performance monitoring, the terminal may report information necessary for the network to calculate performance metrics, for example, by reporting measurement results (e.g., RSRP) and / or RS index for a set of resources for monitoring. (ii) For UE-assisted performance monitoring, the terminal may calculate performance metrics.

[0096] With respect to the NW-side model for BM-Case 1 / 2, quantization of the reported RSRP may be supported, for example, differential RSRP reporting may be supported along existing quantization steps and ranges. The reported content may include information on the RSRP and the corresponding upper N beam, where N can be set by the network.

[0097] With respect to the configuration of the first set of beams and the second set of beams of the UE-side model of BM Case-1, two resource sets may be configured separately for each of the first set and the second set, and the resource sets may be provided through CSI reporting settings. The terminal may perform inference / measurement on the resource set of the first set of beams. The terminal may not be expected to perform measurement / inference on the resource set of the second set of beams. The beam information in the inference report may include resource set information for the first set.

[0098] In relation to the UE-side model, the associated ID may be provided through the CSI framework. The terminal may assume identical / similar characteristics for DL ​​transmit beams / sets (lists) for the same associated ID.

[0099] Regarding UE-assisted performance monitoring for the UE-side models of BM-Case 1 and 2, the following methods may be considered.

[0100] i) Compare prediction results based on resources for monitoring and use the top 1 or top K beam prediction accuracy.

[0101] ii) Use RSRP difference information based on RSRP measurements of resources for monitoring and actual RSRP measurements for at least one of the top N prediction beams.

[0102] iii) Use the difference information between the measured RSRP and the predicted RSRP for the corresponding beam of the resources for monitoring.

[0103] iv) Probability information that the predicted beam will become one of the top 1 or N beams

[0104] For reporting inference results for the UE-side model, quantization of RSRP may be supported, and differential RSRP with existing quantization steps may be supported. The scope of RSRP reporting is such that differential RSRP among multiple beams is supported in the case of BM-case 1, and differential RSRP among multiple beams at multiple time points is supported in the case of BM-case 2.

[0105] For BM-Case 2 of the UE-side model, the network can be configured to report inferences about N future times to the terminal.

[0106] (2) CSI prediction and / or compression

[0107] Figure 4 illustrates an example of an AI / ML-based CSI measurement / reporting operation.

[0108] Referring to FIG. 4, the network / terminal can perform a configuration procedure related to AI / ML-based CSI (D05). The network / terminal can perform a configuration procedure for an AI / ML model to be used for AI / ML-based CSI, and for the exchange of configuration information for upper-layer signaling for AI / ML-based CSI measurement / reporting. For example, at least one of information related to model inference, settings for RS / resources to be used for CSI measurement, monitoring performance, data collection, and conditions / resources for CSI reporting may be signaled.

[0109] The terminal can perform CSI measurements based on AI / ML model inference (D10). The AI / ML model used by the terminal for CSI measurements may be a UE-side AI / ML model corresponding to a one-side AI / ML model, or an AI / ML model corresponding to the terminal part of a two-side AI / ML model.

[0110] The terminal may report CSI to the network based on the results of CSI measurements (D15). CSI reporting may be performed periodically or non-periodically depending on the configuration, and in the case of non-period CSI reporting, network instructions (not shown), such as DCI, that trigger it may be additionally signaled. CSI reporting may include AI / ML-based CSI content and may additionally include legacy CSI content (e.g., non-AI / ML-based RI, PMI, CQI, etc.) (depending on the configuration / scheduling). AI / ML-based CSI content may be related to at least one of 1) CSI compression to reduce the overhead of CSI reporting and 2) CSI prediction for future time points in the time domain.

[0111] The network can acquire CSI based on the terminal's CSI report.

[0112] If a two-sided AI / ML model is configured, the network can reconstruct the CSI by using the terminal's CSI report as input data to the AI / ML model configured in the network (D20). The inference (output) of the AI / ML model configured in the network may be the reconstructed CSI. In such a two-sided AI / ML model, the terminal-side AI / ML model part can be understood as a CSI encoder, and the network-side AI / ML model part can be understood as a concept similar to a CSI decoder.

[0113] CSI compression is CSI compression in the spatial-frequency domain and can primarily be based on two-sided AI / ML models. CSI prediction can primarily be based on one-sided, specifically UE-side AI / ML models.

[0114] In CSI compression based on a two-sided AI / ML model, AI / ML model training may include at least one of the following: (i) Type 1, in which the two-sided AI / ML model is jointly trained at either the terminal or the network; (ii) Type 2, in which the terminal and the network each jointly train the corresponding parts of the two-sided AI / ML model; and (iii) Type 3, in which the terminal and the network each separately train the corresponding parts of the two-sided AI / ML model, wherein the training of the terminal is mainly related to CSI generation and the training of the network is mainly related to CSI reconstruction. Joint training means that the CSI generation / reconstruction models are trained in the same loop for forward / backward delays, and separate training may mean a sequential method in which one of the terminals or the network starts training first, and then the other performs training.

[0115] (3) Positioning

[0116] Figure 5 illustrates an example of an AI / ML-based positioning operation.

[0117] Referring to FIG. 5, the network / terminal can perform a setup procedure related to AI / ML-based positioning (E05). The network / terminal can perform measurements for positioning (E10). The measurements for positioning may be related to PRS and / or SRS measurements. Based on the measurement results, the network / terminal can obtain information regarding terminal positioning (E15). For example, the network / terminal can perform AI / ML inference by using the measurement results for PRS / SRS as AI / ML input data. The information regarding terminal positioning may correspond to AI / ML output data. The AI / ML output data may be, for example, terminal location or assistance information that serves as the basis for determining terminal location, but is not limited thereto.

[0118] < CSI Related Operations >

[0119] Channel state information (CSI) may include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), Layer 1-RSRP (Layer 1-Reference Signal Received Power), and / or Layer 1-SINR (Layer 1-Signal-to-Interference-plus-Noise Ratio).

[0120] In the case of CSI prediction, the CSI related to the prediction may include at least one of the predicted CQI (predicted CQI, P-CQI), predicted PMI (predicted PMI, P-PMI), predicted CRI (predicted CRI, P-CRI), predicted SSBRI (predicted SSBRI, P-SSBRI), predicted LI (predicted LI, P-LI), predicted RI (predicted RI, P-RI), predicted L1-RSRP (predicted L1-RSRP, P-L1-RSRP) and / or predicted L1-SINR (predicted L1-SINR, P-L1-SINR).

[0121] When monitoring the performance / accuracy of the above CSI prediction, the CSI related to prediction accuracy may include a Prediction Accuracy Indicator (PAI). For example, the PAI may indicate the accuracy of predicted downlink reference signal(s) (e.g., predicted CRI(s) and / or predicted SSBRI(s)), and the PAI may be interpreted / replaced as a Reference Signal-Prediction Accuracy Indicator (RS-PAI). For example, the PAI may indicate the accuracy of predicted CSI (e.g., predicted PMI), and the PAI may be interpreted / replaced as a Channel State Information-Prediction Accuracy Indicator (CSI-PAI).

[0122] Figure 6 is a flowchart showing an example of a CSI-related procedure.

[0123] Referring to FIG. 6, to perform one of the uses of CSI-RS, a terminal (e.g., user equipment, UE) receives configuration information related to CSI from a base station (e.g., general Node B, gNB) via radio resource control (RRC) signaling (S610).

[0124] The configuration information related to the above CSI may include at least one of CSI-IM (interference management) resource information, CSI measurement configuration information, CSI resource configuration information, CSI-RS resource information (e.g., M≥1 CSI-ResourceConfig resource setting), or CSI report configuration information (e.g., N≥1 CSI-ReportConfig reporting setting). As an example, the configuration information may include at least one of one or more CSI resource settings and / or one or more CSI reporting settings.

[0125] For example, the configuration information may include a first CSI resource setting for measurement and a second CSI resource setting for prediction. As a specific example, the measurement related to the prediction of CSI described below may be performed based on the first CSI resource setting. The terminal may perform L1-RSRP measurements on CSI-RS resources or SS / PBCH block resources associated with the first CSI resource setting. As a specific example, the prediction of CSI described below may be performed based on the second CSI resource setting. Based on the L1-RSRP measurements, the terminal may perform predictions on CSI-RS resources or SS / PBCH block resources associated with the second CSI resource setting. In other words, using L1-RSRPs as measurement metrics, the best CRI / best SSBRI (e.g., P-CRI(s), P-SSBRI(s)) may be predicted.

[0126] For example, the above configuration information may include a first CSI reporting setting related to prediction and a second CSI reporting setting related to prediction accuracy.

[0127] Information related to CSI resource configuration can be expressed as CSI-ResourceConfig IE. Information related to CSI resource configuration defines a group including at least one of an NZP (non-zero power) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the information related to CSI resource configuration includes a CSI-RS resource set list, and the CSI-RS resource set list may 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.

[0128] Information related to CSI report configuration (e.g., CSI-ReportConfig IE) includes a reportConfigType parameter representing time domain behavior and a reportQuantity parameter representing the CSI-related quantity to be reported. The time domain behavior may be periodic, aperiodic, or semi-persistent.

[0129] The above reportQuantity parameter includes the channel quality indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), L1-RSRP (Layer 1-Reference Signal Received Power), L1-SINR (Layer 1-Signal-to-Interference-plus-Noise Ratio), predicted CQI (P-CQI), predicted PMI (P-PMI), predicted CRI (P-CRI), predicted SSBRI (P-SSBRI), predicted LI (P-LI), predicted RI (P-RI), predicted L1-RSRP (P-L1-RSRP), and / or predicted L1-SINR (predicted It can be set to a value representing at least one of L1-SINR, P-L1-SINR) and / or Prediction Accuracy Indicator (PAI) (or RS-PAI).

[0130] For example, the reportQuantity parameter can be set to cri, ssb-Index, cri-RSRP, or ssb-Index-RSRP. cri represents the CSI-RS resource indicator (CRI). RSRP represents the L1-RSRP (Layer 1-Reference Signal Received Power). ssb-Index represents the SS / PBCH block resource indicator (SSBRI).

[0131] For example, the reportQuantity parameter can be set to p-cri, p-ssb-index, p-cri-RSRP, or p-ssb-index-RSRP. p-cri represents the predicted CRI (predicted CRI, P-CRI). p-ssb-index represents the predicted SSBRI (predicted SSBRI, P-SSBRI). p-cri-RSRP represents the predicted CRI (predicted CRI, P-CRI) and predicted L1-RSRP (predicted L1-RSRP, P-L1-RSRP). p-ssb-index-RSRP represents the predicted SSBRI (predicted SSBRI, P-SSBRI) and predicted L1-RSRP (predicted L1-RSRP, P-L1-RSRP).

[0132] For example, the reportQuantity parameter can be set to pai (or rs-pai). pai (or rs-pai) represents PA (or RS-PAI).

[0133] The measurement resource may include settings for downlink signals and / or downlink resources for which the terminal will perform measurements to determine feedback information. The measurement resource may be set as a set of ZP and / or NZP CSI-RS resources associated with a CSI reporting setting. The NZP CSI-RS resource set may include a CSI-RS set or an SSB set. For example, L1-RSRP may be measured against a CSI-RS set or against an SSB set.

[0134] The terminal measures the CSI based on configuration information related to the above CSI (S620). The CSI measurement may include (1) a process of receiving the terminal's CSI-RS (S621) and (2) a process of computing the CSI through the received CSI-RS (S622). The terminal reports the CSI to the base station (S630).

[0135] resource setting

[0136] Each CSI resource setting 'CSI-ResourceConfig' contains a configuration for S≥1 CSI resource sets (given by the higher layer parameter csi-RS-ResourceSetList). The CSI resource setting corresponds to the CSI-RS-resourcesetlist, where S represents the number of configured CSI-RS resource sets. Here, the list of S≥1 CSI resource sets includes either or both of the NZP CSI-RS resource set(s) and the SS / PBCH block (SSB) set(s) used for L1-RSRP computation, or includes CSI-IM resource set(s).

[0137] Next, one or more CSI resource settings for channel measurement (CM) and interference measurement (IM) are established through higher layer signaling.

[0138] - CSI-IM resource for interference measurement.

[0139] - NZP CSI-RS resources for interference measurement.

[0140] - NZP CSI-RS resources for channel measurement.

[0141] That is, the CMR (channel measurement resource) may be an NZP CSI-RS for CSI acquisition, and the IMR (Interference measurement resource) may be an NZP CSI-RS for CSI-IM and IM.

[0142] Here, CSI-IM (or ZP CSI-RS for IM) is primarily used for inter-cell interference measurements.

[0143] Also, the NZP CSI-RS for IM is mainly used for intra-cell interference measurement from multi-users.

[0144] A UE can assume that the CSI-RS resource(s) for channel measurement set for one CSI reporting and the CSI-IM / NZP CSI-RS resource(s) for interference measurement (when NZP CSI-RS resource(s) are used for interference measurement) have a QCL relationship with respect to 'QCL-TypeD' on a resource-by-resource basis.

[0145] As examined, resource setting can refer to a resource set list.

[0146] For aperiodic CSI, each trigger state set using the higher layer parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, and each CSI-ReportConfig is linked to a periodic, semi-persistent, or aperiodic resource setting.

[0147] One reporting setting (e.g., CSI-ReportConfig) can be associated with up to three resource settings (e.g., CSI-ResourceConfig). For example, one CSI reporting setting may include the ID (e.g., CSI-ResourceConfigId) of at least one CSI resource setting. The at least one CSI resource setting may include a CSI resource setting associated with a measurement.

[0148] Beam Management (BM)

[0149] BM procedures are L1 (layer 1) / L2 (layer 2) procedures for acquiring and maintaining a set of base station (e.g., gNB, TRP, etc.) and / or terminal (e.g., UE) beams that can be used for downlink (DL) and uplink (UL) transmission / reception, and may include the following procedures and terms.

[0150] - Beam measurement: An operation in which a base station or UE measures the characteristics of a received beamforming signal.

[0151] - Beam determination: The operation in which a base station or UE selects its transmit beam (Tx beam) / receive beam (Rx beam).

[0152] - Beam sweeping: An operation that covers a spatial area using transmitting and / or receiving beams for a set time interval in a predetermined manner.

[0153] - Beam report: An operation in which the UE reports information about the beam-formed signal based on beam measurements.

[0154] The BM procedure can be divided into (1) a DL BM procedure using an SS (synchronization signal) / PBCH (physical broadcast channel) Block or CSI-RS, and (2) a UL BM procedure using an SRS (sounding reference signal).

[0155] In addition, each BM procedure may include Tx beam sweeping to determine the Tx beam and Rx beam sweeping to determine the Rx beam.

[0156] DL BM

[0157] The DL BM procedure may include (1) transmission to beamformed DL RS (reference signals) of the base station (e.g., CSI-RS or SS Block (SSB)) and (2) beam reporting of the terminal.

[0158] Here, beam reporting may include preferred DL RS ID(identifier)(s) and the corresponding L1-RSRP(Reference Signal Received Power).

[0159] The above DL RS ID may be SSBRI (SSB Resource Indicator) or CRI (CSI-RS Resource Indicator).

[0160] An example of beam forming using SSB and CSI-RS will be examined in detail below.

[0161] SSB beams and CSI-RS beams can be used for beam measurement. The measurement metric is L1-RSRP per resource / block. SSB is used for coarse beam measurement, while CSI-RS can be used for fine beam measurement. SSB can be used for both Tx beam sweeping and Rx beam sweeping.

[0162] Rx beam sweeping using SSBs can be performed as the UE changes the Rx beam across multiple SSB bursts for the same SSBRI. Here, one SS burst includes one or more SSBs, and one set of SS bursts includes one or more SSB bursts.

[0163] The DL BM procedure is examined below.

[0164] Configuration for beam reporting using SSB is performed during CSI / beam configuration in the RRC connected state (or RRC connected mode).

[0165] - The terminal receives configuration information from the base station. As a specific example, the terminal receives from the base station a CSI-ResourceConfig IE containing a CSI-SSB-ResourceSetList containing SSB resources used for BM.

[0166] Table 1 shows an example of CSI-ResourceConfig IE. As shown in Table 1, BM configuration using SSB is not defined separately, and SSB is configured like a CSI-RS resource.

[0167]

[0168] In Table 1, the csi-SSB-ResourceSetList parameter represents a list of SSB resources used for beam management and reporting in a single CSI-RS resource set. Here, the SSB resource set can be set to {SSBx1, SSBx2, SSBx3, SSBx4, …}. For example, the SSB index can be defined from 0 to 63.

[0169] - The terminal receives a DownLink Reference Signal (DL RS) from the base station. As a specific example, the terminal receives an SSB resource from the base station based on the CSI-SSB-ResourceSetList.

[0170] - The terminal transmits a beam report to the base station. As a specific example, if a CSI-ReportConfig related to reporting on SSBRI (SSB Resource Indicator) and L1-RSRP is configured, the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station.

[0171] That is, if the reportQuantity of the above CSI-ReportConfig IE is set to 'ssb-Index-RSRP', the terminal reports the best SSBRI and the corresponding L1-RSRP to the base station.

[0172] And, if the terminal has a CSI-RS resource configured in the same OFDM symbol(s) as the SSB (SS / PBCH Block) and 'QCL-TypeD' is applicable, the terminal can assume that the CSI-RS and SSB are quasi-co-located in terms of 'QCL-TypeD'.

[0173] Here, the above QCL Type D may mean that the antenna ports are QCL-connected in terms of spatial Rx parameters. When a terminal receives multiple DL antenna ports that are in a QCL Type D relationship, it is acceptable to apply the same receiving beam. Additionally, the terminal does not expect CSI-RS to be established in an RE that overlaps with the RE of the SSB.

[0174] The configuration for beam reporting using CSI-RS is performed in the same manner as the configuration for beam reporting using SSB described above, so a redundant explanation is omitted. The operation of the beam reporting procedure using CSI is described below.

[0175] - The terminal receives configuration information from the base station. As a specific example, the terminal receives from the base station a CSI-ResourceConfig IE containing a CSI-SSB-ResourceSetList containing CSI resources used for BM (e.g., NZP CSI-RS resource set IE).

[0176] - The terminal receives CSI-RS resources within the NZP CSI-RS resource set through different Tx beams (DL spatial domain transmission filters) of the base station.

[0177] - The terminal selects (or determines) the best beam.

[0178] - The terminal reports the ID and associated quality information (e.g., L1-RSRP) for the selected beam to the base station. In this case, the reportQuantity of the CSI report config can be set to 'cri-RSRP'.

[0179] Explanation regarding Rel-17 / 18 beam management >

[0180] In Rel-17, DL DCI (e.g., DCI format 1-1 or 1-2) can indicate both the DL TCI state and the UL TCI state, or it can indicate only the UL TCI state without specifying the DL TCI state. Consequently, the methods used in the existing R15 / R16 for configuring UL beam and power control (PC) are replaced in Rel-17 by the aforementioned method of indicating the UL TCI state. More specifically, in R17, a single UL TCI state can be indicated through the TCI field of the DL DCI; this UL TCI state is applied to all PUSCHs and all PUCCHs after a certain period known as the beam application time, and can be applied to some or all of the indicated SRS resource sets. Additionally, the base station can utilize DCI and / or MAC-CE to perform a terminal common beam update, which performs indication / updates for multiple specific DL / UL channel / RS combinations using a single beam (utilizing joint or separate TCI states). For the target channel / RS of the common beam update, UE-dedicated CORESET and UE-dedicated reception on PDSCH are available for DL, and DG / CG-PUSCH and all or subset of dedicated PUCCH are available for UL, and additionally, AP CSI-RS for tracking / BM and SRS can be set as target channel / RS.In Rel-18, considering the M-TRP environment, the method of indicating multiple UL TCI states (and / or DL ​​TCI states) through the TCI field of DL DCI was standardized, and depending on the S-DCI based M-TRP environment and the M-DCI based M-TRP environment, uplink and downlink resources to which each indicated TCI is applied can be defined / configured.

[0181] In this document, ' / ' means 'and', 'or', or 'and / or' depending on the context.

[0182] In this specification, 'beam' may refer to a source RS for a 'spatial filter' or 'spatial relation', and may be interpreted as a QCL (type-D) RS, a TCI state, or (in the case of an uplink) a spatial relation RS.

[0183] For example, in this specification, 'beam' may refer to a spatial filter determined based on the reference RS or the source RS. The spatial filter may include a spatial domain filter, a spatial domain transmission filter, and a spatial domain receive filter. For example, in this specification, 'beam' may be interpreted or substituted with a reference signal index (RS index), a reference signal resource index (RS resource index), and / or a resource indicator (e.g., RS index, SSB index, CSI-RS resource index, SRS resource index, SSB Resource Indicator (SSBRI), CSI-RS Resource Indicator (CRI), etc.).

[0184] For example, a beam associated with a UL may be referred to as i) a spatial filter (for uplink transmission or uplink reception), ii) a spatial domain filter (for uplink transmission or uplink reception), iii) an uplink spatial domain transmission filter, iv) an uplink spatial domain receive filter, v) an uplink transmission spatial filter (UL Tx spatial filter) or vi) an uplink receive spatial filter (UL Rx spatial filter).

[0185] For example, a beam associated with DL may be referred to as i) a spatial filter (for downlink transmission or downlink reception), ii) a spatial domain filter (for downlink transmission or downlink reception), iii) a downlink spatial domain transmission filter, iv) a downlink spatial domain receive filter, v) a downlink transmission spatial filter (DL Tx spatial filter), or vi) a downlink receive spatial filter (DL Rx spatial filter).

[0186] In NR standards, QCL configuration via TCI state settings and spatial relation configuration are utilized to configure the UL / DL transmit / receive beams of a terminal. In the Rel-15 NR standard, RRC and MAC CE signaling are primarily used for uplink and downlink transmit / receive beams. Dynamic signaling has been permitted only for the PDSCH receive beam by utilizing the TCI state field of the DL grant DCI. A unified TCI framework was introduced through the Rel-17 / 18 NR standards. Specifically, a method was introduced to dynamically manage the common beam by using DCI to indicate the indicated TCI for the receive / transmit beams. Meanwhile, in the Rel-18 AI / ML study item, a study was conducted on performance evaluation and specification impact regarding spatial beam prediction and temporal beam prediction sub-use cases in the field of beam management. This study discussed NW / UE-side AI / ML operations that predict the best beam of Set A based on Set B measurements. In the case of UE-side AI / ML, the behavior of the terminal measuring Set B and reporting the predicted Set A beam can be discussed in the Rel-19 AI / ML work item. In this case, if the terminal's beam prediction performance is poor, actions such as switching the terminal-side AI / ML model / functionality or falling back to non-AI / ML-based conventional beam management instead of AI / ML-based beam management (measurement / reporting) are necessary.

[0187] This specification proposes a method for performance monitoring of an AI / ML model on the terminal side, and proposes an operation in which the terminal reports performance monitoring results to the base station when a specific event occurs.

[0188] < Rel-19 UE Initiated Standardization Progress >

[0189] In the following, 'beam' may refer to a source RS for a 'spatial filter' or 'spatial relation', and can be interpreted as a QCL (type-D) RS, a (DL / UL / joint) TCI state, or a spatial relation RS (in the case of an uplink).

[0190] In wireless communication systems, Layer 1 (physical layer) uplink control information has the advantage of having a smaller transmission delay compared to control information from higher layers. For example, for a terminal to transmit information to a base station via MAC-CE or RRC messages, the terminal's scheduling request (SR) procedure and the base station's PUSCH allocation procedure (based on the SR) may be required, resulting in delay and overhead. Additionally, generally, the higher the layer of information, the longer the time required to decode it (e.g., decoding time, processing time). On the other hand, since uplink physical channel resources (e.g., PUCCH, PUSCH) must be configured or allocated to the terminal in advance to send Layer 1 uplink control information, from the perspective of the base station / network, as the number of terminals / UEs increases, the amount of UL (uplink) resources that must be allocated to each terminal / UE increases, which can lead to a greater overall overhead burden on UL resources. Therefore, in wireless communication systems, information that must be transmitted relatively urgently for the operation of the physical layer, such as SR (e.g., for PUSCH allocation), HARQ-ACK (e.g., for retransmission), CSI (e.g., for scheduling / MCS / precoder determination), and beam information (e.g., for (analog) beam determination), is transmitted as physical layer uplink control information (UCI). Among this information, excluding SR, the base station / network determines / controls the timing of information reporting by the terminal.

[0191] These network-initiated / triggered reports have a limitation in that terminals must be configured or instructed to send UCIs frequently in environments where the wireless channel is likely to change rapidly. In such environments, problems arise where the overhead of UL resources for UCI reporting and related DL measurement RS increases, and the terminal's power consumption also increases due to frequent uplink transmissions. Furthermore, the more terminals there are within the cell / TRP coverage area, the greater the UL resource overhead becomes, as UL resources must be allocated to each terminal. To overcome these limitations of network-initiated / triggered reports, a method recently emerging is the UE-initiated / triggered report (UCI) method or the event-based / triggered report method.

[0192] In UE-initiated / triggered (UCI) reporting or event-based / triggered reporting methods, the terminal decides whether to report and when to report. By performing the relevant (UCI) report only when necessary (e.g., only when a specific event occurs), there is a potential benefit of being able to perform rapid reporting to the network because information is reported based on layer-1 / low layer, while reducing UL resource overhead and terminal power consumption.

[0193] With the motivation mentioned above, standardization of UE-initiated / triggered beam reports is underway in NR Rel-19. Additionally, in 6G communication systems, to efficiently utilize uplink resources, UE-initiated / triggered or event-based transmission methods can be more actively extended and applied to the transmission of control information, transport blocks, user-plan data, etc., which were previously transmitted via the existing UCI and / or MAC-CE.

[0194] <Existing UE-initiated / triggered report>

[0195] In NR systems, representative reporting methods for event-based or UE-initiated / triggered information include SR (scheduling request) and BFR (beam failure recovery). SR reports whether PUSCH allocation is required for UL-SCH transmission, while BFR reports whether a BF has occurred and information related to the new beam. This information is transmitted to the base station via explicit or implicit means (e.g., delivering the new beam index as PRACH resource selection information). The aforementioned SR / BFR information is transmitted either simultaneously or in installments through one or two UL resources (e.g., BFRQ on PUCCH + beam information via MAC-CE on PUSCH).

[0196] In this specification, information transmitted to the network based on the event of the terminal and / or through the UE-initiated / triggered transmission method as described above (e.g., SR, BFRQ, new beam information, etc.) is referred to as 'event information' for the convenience of explanation.

[0197] < UE-initiated / triggered CSI report >

[0198] The CSI reporting method supported by existing 4G / 5G systems is the NW-initiated / triggered method. As communication systems continue to evolve, increasingly high-precision CSI reporting is supported; however, due to the high precision and granularity, the amount of CSI information that must be sent at once increases, resulting in a large amount of UL resources (e.g., PUCCH / PUSCH) required for CSI reporting.

[0199] (Method 1)

[0200] Event-based CSI reporting can be performed based on UCI or MAC-CE. When CSI is reported via UCI or MAC-CE, if a UL resource capable of sending the information (e.g., available UL SCH) is not allocated or configured, the terminal may request PUSCH / PUCCH allocation from the base station through a procedure such as a scheduling request (SR). For convenience, the UL resource requesting the above PUSCH / PUCCH allocation is referred to as the first resource, and the UL resource performing the CSI report is referred to as the second resource.

[0201] (Method 2)

[0202] Alternatively, the base station may pre-configure / allocate UL resources (e.g., PUCCH / PUSCH) for the above-mentioned event-based reporting to the terminal. When performing UCI / MAC-CE-based CSI reporting through these UL resources, the base station may need to constantly monitor the terminal because the terminal can perform CSI reporting through the said UL resources at any time. To alleviate or eliminate this burden, the terminal may notify the base station in advance that it will perform transmission through the said UL resources using a separate UL resource (with small overhead) (e.g., short PUCCH, SR PUCCH, PRACH). For convenience, the separate UL resource supporting a small payload size is referred to as the first resource, and the UL resource performing CSI reporting is referred to as the second resource. As the first resource, a PUCCH or PRACH resource capable of transmitting information of about 1 to several bits may be considered, and as the second resource, a PUCCH or (configured grant or semi-persistent CSI) PUSCH resource capable of transmitting information of tens of bits or more may be considered. As described above, the first resource is not always required, and CSI reporting using only the second resource is possible when the base station is not burdened with UL resource monitoring and / or the amount of the second resource is not large.

[0203] The quantity of the above CSI may refer not only to traditional channel state information such as CRI / RI / PMI / CQI / LI, but also to beam information such as CSIRS index and / or L1-RSRP, CSIRS index and / or L1-SINR, SSB index and / or L1-RSRP, and SSB index and / or L1-SINR. Additionally, the quantity of the above CSI may refer to explicit feedback information regarding the measured channel / interference. For example, the explicit feedback information may be a quantized value of the eigenvector and eigenvalue of the measured channel, or a value obtained by appropriately decomposing the measured channel to quantize only the meaningful channel information. The explicit feedback information may be a quantized value obtained by compressing the aforementioned channel information to save payload. Furthermore, the quantity of the above CSI may be defined by including the events discussed at the RAN1 116 conference and the quantity information corresponding to each event (see Table 2 below).

[0204]

[0205] Figure 7 is a diagram illustrating a UE initiated reporting.

[0206] Specifically, FIG. 7 illustrates a 2-step UEI (UE initiated) report. Referring to FIG. 7, the first resource (UL), the second resource (UL), T, and X are defined and will be explained in detail below.

[0207] 1st Resource (UL): Notifies whether an event has occurred (maybe 1 bit) (e.g., short PUCCH, SR PUCCH, PRACH)

[0208] Second Resource (UL): Select one of the preconfigured TOs to report the event quantity report for the First Resource event (select the 4th TO in the figure above).

[0209] T: Select the earliest 2nd resource after the "1st resource transfer end time + T" symbol and report the quantity.

[0210] The reason for including the T symbol is as follows. The T symbol is defined to secure time for quantity calculation on the UE side and to secure time for scheduling a second resource to another UE in the gNB (when no event trigger occurs).

[0211] X: Number of symbols between the 1st and 2nd resources

[0212] In FIG. 7, the first resource is transmitted from the base station via a pre-secured UL channel of a fixed period without separate dynamic scheduling, and after a signal based on the first resource is transmitted, a detailed quantity of the corresponding event is transmitted via the second resource. For example, in FIG. 7, the second resource is determined using time T, but there are various other methods for determining the second resource, and the proposal of this specification may also be applied in such cases. For example, the following method may be considered to determine the second resource. The second resource may be indicated / determined through the DCI received by the UE as a response to the first resource after the transmission of the first resource. For example, the second resource may be indicated / determined from the first resource.

[0213] Rel-18 NES Standardization Background

[0214] In Rel-18 NES, energy-saving technologies were introduced in the spatial and power domains at the base station level. As described below, the sub-configurations introduced for CSI reporting in the Rel-18 NES standardization are summarized as follows.

[0215] Sub-configuration(s) may be configured for a specific CSI report configuration. Sub-configuration may be configured based on at least one of the following i) to iii).

[0216] i) Some resource(s) of the NZP CSI-RS resources within the CMR set of the CSI resource configuration connected to the CSI report configuration may be configured to be included in the sub-configuration.

[0217] ii) Only specific subset ports of multi-port CSI-RS resources (having the same number of ports) within the CMR set of the CSI resource configuration connected to the CSI report configuration can be configured to be included in the sub-configuration.

[0218] iii) By setting the powerOffset parameter in the sub-configuration, the existing powerControlOffset, which has relative power offsets between CSI-RS and PDSCH, can be configured to include additional offset values.

[0219] A sub-configuration based on i) above and a sub-configuration based on ii) above cannot be set together in a single CSI report configuration. A sub-configuration(s) based on a combination of i) and iii) or a sub-configuration(s) based on a combination of ii) and iii) can be set together in a single CSI report configuration.

[0220] Through i) and ii) above, the base station can configure a CSI-RS resource with simplified port virtualization (via the configured sub-configuration) or a CSI-RS resource with a reduced number of ports (via the configured sub-configuration). Subsequently, after receiving a CSI report related to the above sub-configuration from the terminal, the base station can determine whether to switch to a CSI report configuration that applies energy saving in the spatial domain. The base station can transmit CSI-RS by utilizing a sub-configuration in which CSI-RS with an additional power offset applied based on iii) above is configured. The base station can determine whether energy saving in the power domain is applied by receiving a CSI report related to the above sub-configuration from the terminal.

[0221] Meanwhile, when a sub-configuration is set in a specific CSI report configuration as described above, in the case of a periodic CSI report, the terminal must perform the CSI report including all of one or more sub-configurations, and in the case of an SP / AP CSI report, the base station instructs the terminal via MAC CE / DCI which of the set sub-configurations the terminal should report on. Since CSI reports for multiple set sub-configurations must be performed in this way (especially in the case of a periodic CSI report), the base station must also transmit CSI-RS for various settings (related to multiple sub-configuration settings), and the terminal may experience a problem where CSI reporting overhead increases and UL resources are occupied.

[0222] The existing operation for the sub-configuration described above is explained below.

[0223] CSI-ReportConfig may include a list of sub-configurations provided by the upper layer parameter csi-ReportSubConfigToAddModList, each sub-configuration identified by CSI-ReportSubConfigId and set to nzp-CSI-RS-ResourceList corresponding to one or more CSI-RS resource lists, or set to portSubsetIndicator corresponding to a subset of CSI-RS antenna ports, or set to powerOffset corresponding to the power offset of PDSCH for CSI-RS in addition to powerControlOffset of CSI-RS resources.The UE does not expect a CSI-ReportConfig to be configured that includes a mix of sub-configurations configured with nzp-CSI-RS-ResourceList corresponding to one or more CSI-RS resource lists and other sub-configurations configured with portSubsetIndicator corresponding to a CSI-RS antenna port subset ( A CSI-ReportConfig can contain a list of sub-configurations, provided by the higher layer parameter csi-ReportSubConfigToAddModList, where each sub-configuration is identified by CSI-ReportSubConfigId and configured with nzp-CSI-RS-ResourceList which corresponds to a list of one or more CSI-RS resources or configured with portSubsetIndicator which corresponds to a CSI-RS antenna port subset, and / or configured with powerOffset which corresponds to a power offset for PDSCH relative to CSI-RS additionally to powerControlOffset of the CSI-RS resource(s).A UE is not expected to be configured with a CSI-ReportConfig that contains a mix of sub-configuration(s) each configured with nzp-CSI-RS-ResourceList which corresponds to a list of one or more CSI-RS resources and some other sub-configuration(s) each configured with portSubsetIndicator which corresponds to CSI-RS antenna port subset).

[0224] If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-CQI',

[0225] - If the upper-tier parameter non-PMI-PortIndication included in the CSI-ReportConfig is configured on the UE, ports r are indicated in a hierarchical order for rank r, and each CSI-RS resource of the CSI resource configuration is connected to the CSI-ReportConfig according to the order of the associated NZP-CSI-RS-ResourceId of the connected CSI resource configuration for channel measurement provided by the upper-tier parameter resourcesForChannelMeasurement. The configured upper-tier parameter non-PMI-PortIndication includes the port index sequence is included, and here It is a CSI-RS port index associated with rank v. and, here is the number of ports of the CSI-RS resource. The UE must report only the RIs corresponding to the configured fields of PortIndexFor8Ranks. If the UE configures CSI-ReportConfig containing a list of sub-configurations with a portSubsetIndicator configured for each sub-configuration, and the upper-level parameter non-PMI-PortIndication is provided separately for the sub-configurations, corresponds to the number of bits with a value of 1 in the portSubsetIndicator bitmap of the lower setting, and CSI-RS port indices are derived by mapping the antenna ports corresponding to all bits with a value of 1 in the portSubsetIndicator to consecutive antenna ports starting from CSI-RS port index 0 in increasing order of the bit positions of the portSubsetIndicator (if the UE is configured with a higher layer parameter non-PMI-PortIndicationcontained in aCSI-ReportConfig, ports are indicated in the order of layer ordering for rank and each CSI-RS resource in the CSI resource setting is linked to the CSI-ReportConfig based on the order of the associated NZP-CSI-RS-ResourceIdin the linked CSI resource setting for channel measurement given by a higher layer parameter resourcesForChannelMeasurement. The configured higher layer parameter non-PMI-PortIndicationcontains a sequence of port indices, where are the CSI-RS port indices associated with rank v and where is the number of ports in the CSI-RS resource. The UE shall only report RI corresponding to the configured fields ofPortIndexFor8Ranks. If the UE is configured with aCSI-ReportConfigthat contains a list of sub-configurations withportSubsetIndicatorconfigured in each sub-configuration, and the higher layer parameternon-PMI-PortIndicationis separately provided for a sub-configuration, then corresponds to the number of bits with value 1 in the bitmapportSubsetIndicatorfor the sub-configuration and the CSI-RS port indices are derived by mapping antenna ports corresponding to all bits with value of 1 inportSubsetIndicatoras consecutive antenna ports starting at CSI-RS port index 0 in increasing order of the bit position inportSubsetIndicator).

[0226] - UE에 상위 계층 파라미터 non-PMI-PortIndication가 설정되지 않은 경우, UE는 CSI-ReportConfig에 연결된 CSI 자원 설정의 각 CSI-RS 자원에 대해 CSI-RS 포트 인덱스 This rank It is assumed that it is related to. Here is the number of ports of the CSI-RS resource. If CSI-ReportConfig containing a list of sub-configurations is configured in the UE, portSubsetIndicator is configured for each sub-configuration, and the upper-level parameter non-PMI-PortIndication is not provided for the sub-configuration, ... corresponds to the number of bits with a value of 1 in the portSubsetIndicator bitmap of the lower setting, and the CSI-RS port index is derived by mapping the antenna ports corresponding to all bits with a value of 1 in the portSubsetIndicator to consecutive antenna ports starting from CSI-RS port index 0 in increasing order of the bit positions in the portSubsetIndicator (if the UE is not configured with higher layer parameter non-PMI-PortIndication, the UE assumes, for each CSI-RS resource in the CSI resource setting linked to theCSI-ReportConfig, that the CSI-RS port indices are associated with ranks where is the number of ports in the CSI-RS resource. If the UE is configured with aCSI-ReportConfigthat contains a list of sub-configurations withportSubsetIndicatorconfigured in each sub-configuration and the higher layer parameternon-PMI-PortIndicationis not provided for a sub-configuration, then corresponds to the number of bits with value 1 in the bitmapportSubsetIndicatorfor the sub-configuration and the CSI-RS port indices are derived by mapping antenna ports corresponding to all bits with value of 1 inportSubsetIndicatoras consecutive antenna ports starting at CSI-RS port index 0 in increasing order of the bit position inportSubsetIndicator).

[0227] When calculating the CQI for a rank, the UE must use the port specified for that rank for the selected CSI-RS resource. The precoder for the indicated port is (When calculating the CQI for a rank, the UE shall use the ports indicated for that rank for the selected CSI-RS resource. The precoder for the indicated ports shall be assumed to be the identity matrix scaled by ).

[0228] Under the NR standard, the base station transmits CSI-RS to the terminal for channel estimation for downlink scheduling. The terminal performs CSI reporting by measuring CSI-RS. To perform this operation, the base station transmits RRC configurations, including CSI-ReportConfig and CSI-ResourceConfig, to the terminal. When the terminal performs CSI reporting related to a specific CSI-ReportConfig, the following operations are performed. The terminal performs measurements on one or more CSI-RS(s) within the NZP CSI-RS resource set related to the CSI-ResourceConfig associated with the configuration (specific CSI-ReportConfig). Subsequently, the terminal performs CSI reporting related to a specific CRI through CRI selection.

[0229] As described above, CSI reporting was fundamentally performed in NR in relation to a specific single CRI. With the progress of Rel-18 NES standardization, the concept of sub-configuration was introduced, and terminals became able to report on one or more sub-configurations (e.g., multiple CRIs) based on base station configuration / instructions. However, in the case of such sub-configuration-related reporting, reporting must be performed on all configured sub-configurations according to time domain behavior. Consequently, the base station may incur some overhead when configuring uplink resources for the terminal's CSI reporting, which can adversely affect the uplink multi-UE multiple access capacity. Furthermore, according to the existing method, in the CSI-ResourceConfig related to a specific CSI-ReportConfig, only CSI-RS resources with the same number of ports can be configured within the configured NZP CSI-RS resource set.

[0230] Based on the above background, the present specification proposes a method for a terminal to perform CSI reporting by utilizing multiple channel estimation resources having different numbers of ports, and proposes a subsequent base station / terminal operation.

[0231] In this specification, ' / ' may be interpreted as 'and', 'or', or 'and / or' depending on the context.

[0232] Proposal 1

[0233] When a base station sets multiple channel estimation resources with different port numbers to a terminal so that the terminal can perform DL CSI reporting, the terminal can perform CSI reporting based on the following base station settings / instructions (below [1] and / or [2]).

[0234] [1] The base station may set / instruct the channel estimation resource(s) that the terminal must measure among the plurality of channel estimation resources and / or the channel estimation resource(s) that the terminal can measure (at least one).

[0235] [2] The base station can set / instruct the terminal on which of the above channel estimation resources the CSI report should be performed based on.

[0236] In the above, the channel estimation resource serving as the standard for CSI reporting among the channel estimation resources may be i) one of the plurality of channel estimation resources set for CSI reporting, or ii) a channel estimation resource having a different number of ports than the plurality of channel estimation resources. Additionally, the statement that the base station sets / instructs the channel estimation resource that the terminal must measure or / and the channel estimation resource that the terminal can measure may mean that the base station will perform downlink transmission only for the channel estimation resource set / instructed and will not perform transmission for other resources (the terminal may not expect transmission / reception for resources other than the channel estimation resource set / instructed).

[0237] In the above, i) channel estimation resources that the terminal must measure or / and channel estimation resources that the terminal can measure, and ii) channel estimation resources among the plurality of channel estimation resources that serve as the basis for CSI reporting, may be set / instructed by the base station based on signaling such as RRC / MAC CE / DCI.

[0238] <Example 1>

[0239] Example 1) A base station may set N1 port CSI-RS resource, N2 port CSI-RS resource, and N3 port CSI-RS resource to a terminal (e.g., N1≠N2≠N3, or N1⊆N2⊆N3, or N1≤N2≤N3). The base station may set / instruct the terminal to i) measure the N1 port CSI-RS resource and ii) perform CSI reporting for the N3 port CSI-RS resource. Or / and, in the above settings, the base station may set / instruct the terminal to i) measure the N2 port CSI-RS resource and ii) perform CSI reporting for the N4 port CSI-RS resource (e.g., N1≠N4, or N1⊆N4, or N1≤N4). At this time, the CSI report of the terminal may always include a CSI report for the channel estimation resource measured by the terminal (i.e., N1 port CSI-RS resource and N2 port CSI-RS resource in the two operation examples above).

[0240] In particular, since the channel estimation resources that the terminal can measure may be switched by base station settings / instructions, the channel estimation resources related to the CSI report that the terminal mentioned above must always include may be the channel estimation resources most recently measured by the terminal (for the most recent measurement of port(s). Alternatively, information regarding whether to include information / CSI parameters about the most recently measured channel estimation by the terminal in the CSI report may be set / instructed in advance by the base station.

[0241] In the above examples, since the channel estimation resources (e.g., N3 port CSI-RS resource and N4 port CSI-RS resource) that serve as the basis for terminal CSI reporting are CSI-RS resources having a greater number of ports than the number of ports (e.g., N1 and N2) of the channel estimation resources measured by the terminal, the terminal may need to predict and report CSI reports for the channel estimation resources having a greater number of ports based on a UE-side AI / ML model (by utilizing channel information / CSI information regarding the channel estimation resources measured by the terminal as input data for model inference).

[0242] More specifically, based on whether to include information / CSI parameters regarding the most recently measured channel estimate as described above in the CSI report, the following operations may be performed.

[0243] If the information / CSI parameters regarding the most recently measured channel estimate are included in the CSI report, the CSI report may be a measured CSI report + a predicted CSI report (e.g., a CSI report for the measured port(s) + the predicted port(s)); otherwise, it may be an only predicted CSI report (e.g., a CSI report where all predictions were performed on the target port(s).

[0244] At this time, for a channel estimation resource having a number of ports that have not been pre-configured, such as the N4 port CSI-RS resource mentioned above, information regarding a specific (downlink) port combination may be provided / configured from the base station to the terminal for mutual understanding between the base station and the terminal. Specifically, the terminal may perform CSI reporting to the base station regarding the corresponding DL port combination by including the previously provided / configured port combination (subset of) in addition to the N1 / N2 / N3 CSI-RS resources.

[0245] Example 2) Among the N1 port CSI-RS resource, N2 port CSI-RS resource, and N3 port CSI-RS resource (e.g., N1≠N2≠N3, or N1⊆N2⊆N3, or N1≤N2≤N3) set by the base station to the terminal, the base station may set / instruct the terminal to i) measure the N3 port CSI-RS resource and ii) perform a CSI report for the N1 port CSI-RS resource.

[0246] When a terminal performs a report related to the N1 / N2 / N3 port CSI-RS resource as per the above settings, the base station configures / activates / triggers the report and can also set / instruct information / scenarios indicating which of the two examples above is related to or what purpose it is related to.

[0247] For example, the base station may configure / activate / trigger the above report to the terminal and set / instruct information indicating one of the following i) and / or ii).

[0248] i) Perform CSI reporting for channel estimation resources having a large number of ports compared to the channel estimation resources that the terminal must measure or / and the channel estimation resources that the terminal can measure.

[0249] ii) Perform CSI reporting for channel estimation resources that have a smaller number of ports compared to the channel estimation resources that the terminal must measure or / and the channel estimation resources that the terminal can measure.

[0250] In the two examples above, the cases where channel estimation resources having different number of ports are configured in the CSI reporting settings configured by the base station are mainly described, but this is not intended to limit the scope of application of the embodiments of this specification. Specifically, the two examples of Embodiment 1 above may also be applied in cases where channel estimation resource(s) having the same number of ports are configured / associated in the CSI reporting settings configured for the terminal. For example, in the configuration for the terminal's CSI reporting, the base station may configure CSI-RS resource(s) having the same number of ports and configure / instruct to perform CSI reporting related to a number of ports different from the configured number of ports (or CSI reporting related to a CSI-RS resource having a different number of ports).

[0251] From the perspective of base station NES, the following two effects can be expected from the first embodiment above.

[0252] - Although the base station transmits only some of the ports (N1 port) of the N3 port CSI-RS resources, by having the terminal measure / report N3 (>N1) port-based CSI (using UE-side AI / ML), the number of ports required for the base station's CSI-RS transmission at the current time can be minimized / optimized, thereby saving energy.

[0253] - The base station transmits only all or part of the N3 port CSI-RS resources (N1 port), but N1 to the terminal ( <N2 or <N3) port 기반의 CSI를 측정 / 보고하게 함으로써, 추후에 기지국이 실제 N1개 만의 port로 PDSCH / CSI-RS 전송을 하고 싶은 경우에 활용할 수 있다. 구체적으로, N1개의 port로 DL 전송이 원활할 경우 실제로 추후 CSI-RS 전송 및 PDSCH 전송은 N1 port에 기반하도록 RRC / MAC CE / DCI 등을 통해 update할 수 있다.

[0254] <Example 2>

[0255] Example 1) A base station may set N1 port CSI-RS resource, N2 port CSI-RS resource, and N3 port CSI-RS resource to a terminal (e.g., N1≠N2≠N3, or N1⊆N2⊆N3, or N1≤N2≤N3). The base station may set / instruct the terminal to i) measure the N1 port CSI-RS resource and ii) report a preferred CSI-RS resource for DL ​​transmission (e.g., N1 port CSI-RS resource, N2 port CSI-RS resource, N3 port CSI-RS resource, and / or N4 port CSI-RS resource (e.g., N1≠N4, or N1⊆N4, or N1≤N4)). Since the N4 port CSI-RS resource is a resource not set by the base station, the following embodiments may be considered to represent this third resource.

[0256] For example, related reporting can be performed by representing an N4 port CSI-RS resource as a linear combination of pre-configured CSI-RS resources. Specifically, an N4 port CSI-RS resource can be expressed as W1*N1 port CSI-RS resource + W2*N2 port CSI-RS resource, where W1 and W2 can be weight vectors / matrices composed of real and / or imaginary numbers.

[0257] For example, for a channel estimation resource having a number of ports that have not been pre-configured, such as an N4 port CSI-RS resource, information regarding a specific (downlink) port combination may be configured / provided to the terminal from the base station for mutual understanding between the base station and the terminal. Specifically, the terminal may report to the base station a preferred port combination for DL ​​transmission (at a specific future time), including the N1 / N2 / N3 CSI-RS resource plus a subset of the pre-configured / provided port combinations.

[0258] Example 2) A base station may set N1 port CSI-RS resource, N2 port CSI-RS resource, and N3 port CSI-RS resource for a terminal (e.g., N1≠N2≠N3, or N1⊆N2⊆N3, or N1≤N2≤N3). The base station may set / instruct the terminal to i) measure the N3 port CSI-RS resource and ii) report a preferred CSI-RS resource for DL ​​transmission (e.g., N1 port CSI-RS resource, N2 port CSI-RS resource, and / or N3 port CSI-RS resource, where the reported resource has a subset port of N3 port CSI-RS resource) (at a specific future time). At this time, as a method for reporting a subset of ports of the N1 / N2 / N3 port CSI-RS resource, the terminal can use a full bitmap with a number of bits of Max(N1, N2, N3) to report a preferred CSI-RS / PDSCH port combination for DL ​​transmission (at a specific future time).

[0259] When a terminal performs a report related to the N1 / N2 / N3 port CSI-RS resource as per the above settings, the base station configures / activates / triggers the report and can also set / instruct information / scenarios indicating which of the two examples above is related to or what purpose it is related to.

[0260] For example, the base station can configure / activate / trigger the above report to the terminal and set / instruct whether to perform CSI reporting for a channel estimation resource having a large number of ports compared to the channel estimation resource that the terminal must measure or / and the channel estimation resource that the terminal can measure, or to perform CSI reporting for a channel estimation resource having a small number of ports.

[0261] In the two examples above, the cases where channel estimation resources having different port numbers are configured in the CSI reporting settings configured by the base station are mainly described, but this is not intended to limit the scope of application of the embodiments of this specification. Specifically, the two examples of Embodiment 2 above may also be applied in cases where channel estimation resource(s) having the same number of ports are configured / associated in the CSI reporting settings configured for the terminal. For example, in the configuration for the terminal's CSI reporting, the base station may configure CSI-RS resource(s) having the same number of ports and configure / instruct to perform CSI reporting (preferred at a specific future time) related to a number of ports different from the configured number of ports (or CSI reporting related to a CSI-RS resource having a different number of ports (preferred at a specific future time)).

[0262] In the above Example 2, since the purpose is for the terminal to report a preferred port combination for DL ​​transmission (at a specific future point in time), the terminal may predict and report the preferred port combination for DL ​​transmission (e.g., full bitmap, and / or specific CSI-RS resource indicator(s)) based on a UE-side AI / ML model (using channel information / CSI information (corresponding to multiple past time instances) regarding the channel estimation resources measured by the terminal as input data for model inference).

[0263] In the above, the specific future point in time may be a predefined point in time or a point in time set / instructed by the base station. For example, the specific future point in time may be a slot X slots after the slot in Example 2 where the N1 / N2 / N3 CSI-RS resource was (most recently) received. For example, the specific future point in time may be a slot X slots after the slot corresponding to the CSI reference resource at the time of reporting for the N1 / N2 / N3 CSI-RS resource. For example, the specific future point in time may be a slot X slots after the slot in which the report for the N1 / N2 / N3 CSI-RS resource is performed. In the above examples, X may be a natural number. X may be a predefined value or a value set / instructed by the base station.

[0264] The effects of the second embodiment described above are similar to the two effects of the first embodiment described above, but the following effects can be expected, particularly at a future point in time. Specifically, by reporting a port combination preferred by the terminal for DL ​​serving, the base station can adaptively set / instruct the optimal CSI-RS / PDSCH port combination to the terminal by pre-lightening (with less port CSI-RS resource) or heavyening (with more port CSI-RS resource) the channel estimation resources used for CSI reporting based on the terminal's report.

[0265] <Example 3>

[0266] The base station can instruct the terminal to perform the operations of Examples 1 and 2 above by utilizing the sub-configuration settings introduced in the Rel-18 NES standardization.

[0267] - For example, a base station may set up a sub-configuration corresponding to the N1 port CSI-RS resource, N2 port CSI-RS resource, and N3 port CSI-RS resource in the examples of Examples 1 and 2 for a specific CSI-ReportConfig. The base station may set up / instruct the terminal to perform the operations of the examples of Examples 1 and 2. For example, the base station may set up the N3 port CSI-RS resource for the terminal for a specific CSI-ReportConfig. Even if a port subset of N3 or lower is set up in the relevant sub-configuration(s) (although each sub-configuration is still linked with the corresponding N3-port CSI-RS resource), the base station may set up / instruct the terminal to perform the operations of the examples of Examples 1 and 2.

[0268] - At this time, the base station may configure / activate / trigger the CSI report and simultaneously set / instruct which scenario among the examples of Embodiments 1 and 2 is being used (setting / instructing whether the report is for a channel estimation resource having a number of ports greater than the number of ports of the channel estimation resource being measured, or for a channel estimation resource having a number of ports less than the number of ports of the channel estimation resource).

[0269] - Or / and, the base station may set different scenarios related to the examples of Examples 1 and 2 for each sub-configuration related to the specific CSI report. Different sub-configurations may have different purposes for which the terminal may perform reporting.

[0270] As a specific example, the base station may configure the specific CSI report to include a smaller number of ports for a specific sub-configuration compared to the channel estimation resources set in the CSI report configuration. After receiving an RS based on the specific sub-configuration (for DL ​​CSI reporting), the terminal may perform a CSI report related to channel estimation resources having a larger number of ports.

[0271] As a specific example, the base station may configure the specific sub-configuration in the aforementioned specific CSI report to include a number of ports equal to or greater than the number of channels estimated resources set in the CSI report configuration. After receiving an RS based on the said specific sub-configuration (for DL ​​CSI reporting), the terminal may perform a CSI report related to channels estimated resources having a smaller number of ports.

[0272] - Or / and, the base station may configure / instruct a specific sub-configuration related to the specific CSI report to support one or more scenarios related to the examples of Examples 1 and 2. In this case, when the base station configures / activates / triggers the terminal to perform reporting for the specific sub-configuration related to the specific CSI report, it may also signal which scenario the reporting related to is configured / instructed.

[0273] The CSI report of Proposal 1 above may include periodic, semi-persistent, and aperiodic CSI reports. Additionally, the CSI report of Proposal 1 above may be transmitted to the base station in the form of a UE-initiated report depending on whether an event occurs. For example, in Examples 1 to 3 related to Proposal 1 above, the terminal may perform a CSI report to the base station only when there is a change / switching of the preferred channel estimation resource. For example, the terminal may perform a CSI report to the base station only when the content of the CSI report predicted using the terminal's UE-side AI / ML differs from the previous measurement / report / inference by more than a specific value (PMI / RI / CQI). In such a case, the terminal may signal the presence or absence of the second UL resource using the first UL resource in the background mentioned above regarding the UE-initiated report, and perform a report related to Examples 1 to 3 at the second UL resource.

[0274] The base station configures / activates / triggers the CSI report of the above proposal 1 and can also set / instruct the terminal on which of embodiments 1 to 3 the report related to is to be performed.

[0275] The above embodiments may be operated by a combination of specific embodiments.

[0276] An example of a terminal (or base station) operation based on at least one of the aforementioned embodiments (e.g., at least one of the embodiments of Proposal 1) is as follows.

[0277] 1) The terminal (base station) receives (transmits) settings related to the CSI report.

[0278] The above settings may include settings for CSI reporting of the terminal (e.g., CSI-ReportConfig, CSI-ResourceConfig, sub-configuration, etc.) based on Proposal 1.

[0279] 2) The terminal (base station) receives (transmits) a message scheduling the transmission of the above CSI report.

[0280] In the case of UE-triggered operation, the transmission and reception of the above message may be omitted.

[0281] 3) The terminal (base station) transmits (receives) a CSI report based on the above message.

[0282] The transmission of the above CSI report may be based on the embodiments of Proposal 1.

[0283] The above terminal / base station operation is merely an example, and each operation (or step) is not necessarily essential; depending on the terminal / base station implementation method, the beam measurement / reporting operation of the terminal according to the aforementioned embodiments may be omitted or added.

[0284] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations based on at least one of the embodiments of Proposal 1) can be processed by the device of FIG. 10 (e.g., the processor (110, 210) of FIG. 10).

[0285] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations based on at least one of the embodiments of Proposal 1) may be stored in memory (e.g., 140, 240 of FIG. 10) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 10).

[0286] The embodiments described above will be explained in detail below with reference to FIGS. 8 and FIG. 9 regarding the operation of the terminal and base station. The methods described below are distinguished only for convenience of explanation, and it is understood that a part of one method may be substituted with a part of another method or combined with one another and applied.

[0287] FIG. 8 is a flowchart illustrating a method according to one embodiment of the present specification.

[0288] Referring to FIG. 8, a method according to one embodiment of the present specification includes a setting information receiving step (S810), an information receiving step (S820) indicating a first resource for measurement, an information receiving step (S830) indicating a second resource for reporting, and a CSI transmission step (S840).

[0289] In S810, the terminal receives configuration information from the base station.

[0290] For example, the above configuration information may include configurations according to the CSI-related operations described above. As a specific example, the above configuration information may include i) one or more CSI reporting configurations (e.g., N≥1 CSI-ReportConfig reporting setting) and ii) one or more CSI resource configurations (e.g., M≥1 CSI-ResourceConfig resource setting).

[0291] For example, the above-mentioned configuration information may include information based on at least one of the embodiments of Proposal 1. As a specific example, a plurality of resources related to different number of ports may be configured based on the above-mentioned configuration information. As a specific example, a plurality of resources based on the same number of ports may be configured based on the above-mentioned configuration information. The plurality of resources may be based on the plurality of channel estimation resources of Proposal 1 described above.

[0292] In S820, the terminal receives information from the base station indicating a first resource for measurement among the plurality of resources.

[0293] For example, the first resource may include at least one of the resource(s) that the terminal must measure among the plurality of resources and / or the resource(s) that the terminal can measure.

[0294] For example, the information representing the first resource may be based on an RRC message, MAC-CE, or DCI.

[0295] In S830, the terminal receives information from the base station indicating a second resource for reporting.

[0296] For example, the second resource mentioned above may refer to a resource that serves as the standard for the CSI reporting described above.

[0297] For example, the information representing the second resource may be based on an RRC message, MAC-CE, or DCI.

[0298] According to one embodiment, the information representing the first resource and the information representing the second resource may be set / instructed together based on an RRC message, MAC-CE, or DCI. In this case, S820 and S830 may be performed as a single step. Specifically, the terminal may receive information (e.g., an RRC message, MAC-CE, or DCI) from a base station that includes the information representing the first resource and the information representing the second resource.

[0299] In S840, the terminal transmits Channel State Information (CSI) to the base station.

[0300] According to one embodiment, the CSI may include information based on at least one of the embodiments of Proposal 1 described above. Specifically, the CSI may include i) information related to the second resource and / or ii) information related to a future terminal preference (UE preference).

[0301] According to one embodiment, the second resource may be one of the plurality of resources. The number of first ports associated with the first resource (e.g., N1 or N3) may differ from the number of second ports associated with the second resource (e.g., N3 or N1). The present embodiment may be based on Example 1) or Example 2) in Example 1 of Proposal 1.

[0302] For example, the number of the second ports (e.g., N3) may be greater than the number of the first ports (e.g., N1).

[0303] For example, the number of the second ports (e.g., N1) may be smaller than the number of the first ports (e.g., N3).

[0304] According to one embodiment, the second resource may be a preferred resource associated with the future point in time. The second resource may be based on a linear combination associated with one or more of the plurality of resources. This embodiment may be based on Example 1) of Embodiment 2 of Proposal 1.

[0305] According to one embodiment, the CSI may include a bitmap having a number of bits (e.g., Max(N1, N2, N3)) based on the largest value among the different number of ports. Preferred ports may be indicated based on the bitmap. This embodiment may be based on Example 2) of Embodiment 2 of Proposal 1.

[0306] According to one embodiment, the plurality of resources may be based on a plurality of sub-configurations based on a reporting setting within the setting information. This embodiment may be based on Embodiment 3 of Proposal 1.

[0307] According to one embodiment, the CSI may include at least one of i) predicted information related to the second resource (e.g., predicted CSI (predicted CRI, predicted SSBRI and / or other predicted CSI parameters) and / or ii) information based on the measurement (e.g., measured CSI (CRI, SSBRI and / or other CSI parameters)). This embodiment may be based on Embodiment 1 and / or Embodiment 2 of Proposal 1.

[0308] According to one embodiment, information related to a scenario may be indicated together with respect to the second resource based on at least one of embodiments 1 to 3 of the above-described proposal 1. Specifically, based on the information indicating the second resource, it may be indicated whether the number of second ports associated with the second resource is greater than the number of first ports associated with the first resource. For example, based on the information indicating the second resource, it may be indicated that the number of second ports is greater than the number of first ports. For example, based on the information indicating the second resource, it may be indicated that the number of second ports is less than the number of first ports.

[0309] According to one embodiment, the future point in time may be based on a slot after X slots from a defined slot. X may be a natural number. This embodiment may be based on Embodiment 2 of Proposal 1. For example, X may be a predefined value or a value set / instructed by a base station.

[0310] For example, the slot defined above may be the latest slot in which a reference signal (RS) based on the plurality of resources is received.

[0311] For example, the slot defined above may be a slot based on a CSI reference resource associated with the CSI.

[0312] For example, the slot defined above may be a slot to which the CSI is transmitted.

[0313] According to one embodiment, the CSI may be transmitted based on the event described above. For example, the CSI may be transmitted based on a change in the preferred resource associated with the future point in time. For example, the CSI may be transmitted based on the difference between the predicted information associated with the second resource and the previously reported predicted information being greater than or equal to a predetermined value.

[0314] Operations based on S810 to S840 described above can be implemented by the device of FIG. 10. For example, referring to FIG. 10, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S810 to S840.

[0315] The embodiments described above will be explained in detail below in terms of base station operation.

[0316] S910 to S940 described below correspond to operations based on S810 to S840 described in FIG. 8. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below can be replaced by the description / embodiment of FIG. 8 corresponding to the operation.

[0317] FIG. 9 is a flowchart illustrating a method according to another embodiment of the present specification.

[0318] Referring to FIG. 9, a method according to another embodiment of the present specification includes a setting information transmission step (S910), an information transmission step (S920) indicating a first resource for measurement, an information transmission step (S930) indicating a second resource for reporting, and a CSI reception step (S940).

[0319] In S910, the base station transmits configuration information to the terminal.

[0320] For example, the above-mentioned configuration information may include information based on at least one of the embodiments of Proposal 1. As a specific example, a plurality of resources related to different number of ports may be configured based on the above-mentioned configuration information. As a specific example, a plurality of resources based on the same number of ports may be configured based on the above-mentioned configuration information. The plurality of resources may be based on the plurality of channel estimation resources of Proposal 1 described above.

[0321] In S920, the base station transmits information to the terminal indicating a first resource for measurement among the plurality of resources.

[0322] In S930, the base station transmits information to the terminal indicating a second resource for reporting.

[0323] According to one embodiment, the information representing the first resource and the information representing the second resource may be set / instructed together based on an RRC message, MAC-CE, or DCI. In this case, S920 and S930 may be performed as a single step. Specifically, a base station may transmit information (e.g., an RRC message, MAC-CE, or DCI) including the information representing the first resource and the information representing the second resource to a terminal.

[0324] In S940, the base station receives Channel State Information (CSI) from the terminal.

[0325] According to one embodiment, the CSI may include information based on at least one of the embodiments of Proposal 1 described above. Specifically, the CSI may include i) information related to the second resource and / or ii) information related to a future terminal preference (UE preference).

[0326] Operations based on the above-described S910 to S940 can be implemented by the device of FIG. 10. For example, referring to FIG. 10, a base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S910 to S940.

[0327] The operations / terms based on the embodiments described above are described under the assumption of an existing system (e.g., a 5G system). However, this is for the convenience of explanation and is not intended to limit the scope of application of the technical problems and means for solving problems that are to be solved by this specification to a specific system. That is, the technical problems / technical issues / problems mentioned in this specification may exist in other systems (e.g., a 6G system). It is evident that the embodiments of this specification can be extended to solve problems that exist in other systems as well. Therefore, for the extended application of the embodiments of this specification to other systems, terms defined / described based on a 5G system may be replaced / changed with terms defined in said other systems (or generalized terms not specific to one system). For example, PRACH, PUSCH, PUCCH, or SRS may be replaced / changed to uplink signals (or uplink channels). For example, SSB, CSI-RS, PDSCH, and PDCCH may be replaced / changed to downlink signals (or downlink channels).

[0328] Hereinafter, an apparatus to which the embodiments of the present specification can be applied (an apparatus implementing the method / operation according to the embodiments of the present specification) will be described with reference to FIG. 10.

[0329] FIG. 10 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0330] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0331] The processor (110) performs baseband-related signal processing and may include an upper layer processing unit (111) and a physical layer processing unit (115). The upper layer processing unit (111) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (115) may process operations of the PHY layer. For example, if the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, if the first device (100) is a first terminal device in terminal-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

[0332] The antenna section (120) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110) and software, operating systems, applications, etc. related to the operation of the first device (100), and may include components such as a buffer.

[0333] The processor (110) of the first device (100) may be configured to implement the operation of the base station in base station-terminal communication (or the operation of the first terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0334] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0335] The processor (210) performs baseband-related signal processing and may include an upper layer processing unit (211) and a physical layer processing unit (215). The upper layer processing unit (211) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (215) may process operations of the PHY layer. For example, if the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, if the second device (200) is a second terminal device in terminal-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0336] The antenna section (220) may include one or more physical antennas, and may support MIMO transmission and reception if it includes multiple antennas. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210) and software, operating systems, applications, etc. related to the operation of the second device (200), and may include components such as a buffer.

[0337] The processor (210) of the second device (200) may be configured to implement the operation of the terminal in base station-terminal communication (or the operation of the second terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0338] In the operation of the first device (100) and the second device (200), the details described in the examples of the present disclosure regarding the base station and terminal (or the first terminal and the second terminal in terminal-to-terminal communication) in base station-to-terminal communication may be applied in the same way, and redundant descriptions are omitted.

[0339] Here, the wireless communication technology implemented in the device of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above.

[0340] Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above.

[0341] Additionally or generally, the wireless communication technology implemented in the device of the present disclosure may include at least one of ZigBee, Bluetooth, and a Low Power Wide Area Network (LPWAN) for low-power communication, but is not limited to the names mentioned above. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

Claims

1. Regarding the method, A step of receiving configuration information, wherein a plurality of resources related to different number of ports are configured based on the configuration information; A step of receiving information representing a first resource for measurement among the plurality of resources above; A step of receiving information representing a second resource for reporting; and The method includes the step of transmitting Channel State Information (CSI), A method characterized in that the above CSI includes i) information related to the second resource and / or ii) information related to future terminal preference (UE preference).

2. In Paragraph 1, The second resource mentioned above is one of the plurality of resources, and A method characterized in that the number of first ports associated with the first resource is different from the number of second ports associated with the second resource.

3. In Paragraph 2, A method characterized in that the number of the second ports is greater than the number of the first ports.

4. In Paragraph 2, A method characterized in that the number of the second ports is smaller than the number of the first ports.

5. In Paragraph 1, The above second resource is a preferred resource related to the above future point in time, and A method characterized in that the second resource is based on a linear combination related to one or more of the plurality of resources.

6. In Paragraph 1, The above CSI includes a bitmap having a number of bits based on the largest value among the number of different ports, and A method characterized by indicating preferred ports based on the above bitmap.

7. In Paragraph 1, A method characterized in that the above plurality of resources are based on a plurality of sub-configurations based on a reporting setting within the above setting information.

8. In Paragraph 1, A method characterized in that the above CSI comprises at least one of i) predicted information related to the second resource and / or ii) information based on the measurement.

9. In Paragraph 1, A method characterized by indicating whether the number of second ports associated with the second resource is greater than the number of first ports associated with the first resource, based on the information representing the second resource.

10. In Paragraph 1, A method characterized in that the above future point in time is based on a slot after X slots from a defined slot, and X is a natural number.

11. In Paragraph 10, A method characterized in that the slot defined above is the latest slot in which a reference signal (RS) based on the plurality of resources is received.

12. In Paragraph 10, A method characterized in that the slot defined above is a slot based on a CSI reference resource associated with the CSI.

13. In Paragraph 10, A method characterized in that the slot defined above is a slot to which the CSI is transmitted.

14. In Paragraph 1, A method characterized in that the above CSI is transmitted based on a change in the preferred resource associated with the above future point in time.

15. In Paragraph 1, A method characterized in that the above CSI is transmitted based on the difference between the predicted information related to the second resource and the previously reported predicted information being greater than or equal to a predetermined value.

16. In the terminal, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A terminal characterized by the above instructions enabling the terminal to perform all steps of the method according to any one of claims 1 to 15, based on execution by the one or more processors.

17. A device comprising one or more memories and one or more processors connected to the one or more memories, An apparatus characterized in that the above one or more memories store instructions that cause the apparatus to perform all steps of the method according to any one of claims 1 to 15, based on execution by the above one or more processors.

18. In a non-transitory computer-readable storage medium for storing instructions, A non-transitory computer-readable storage medium characterized by instructions executable by one or more processors such that the terminal performs all steps of the method according to any one of claims 1 to 15.

19. Regarding the method, A step of transmitting configuration information, wherein a plurality of resources related to different numbers of ports are configured based on the configuration information; A step of transmitting information representing a first resource for measurement among the plurality of resources above; A step of transmitting information representing a second resource for reporting; and The method includes the step of receiving Channel State Information (CSI), A method characterized in that the above CSI includes i) information related to the second resource and / or ii) information related to future terminal preference (UE preference).

20. Regarding base stations, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A base station characterized by the above instructions, based on execution by one or more processors, causing the base station to perform all steps of the method according to claim 19.

Images