Method for beam failure prediction and apparatus therefor

The method predicts beam failures in mobile communication systems to minimize delays and enhance reliability by preemptively updating beams, addressing the inefficiencies of conventional methods.

WO2026235492A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096669
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Conventional beam management methods in mobile communication systems fail to predict beam failures proactively, leading to significant delays in recovery, which disrupt data transmission and increase latency, packet loss, and control signal overhead.

Method used

A method for predicting beam failure by receiving configuration information and a reference signal, allowing for a preemptive beam update based on a future time point, thereby minimizing delays and improving communication reliability and resource efficiency.

Benefits of technology

Preemptive beam updates reduce recovery delays, enhance data transmission continuity, decrease packet loss and control signal overhead, and improve link stability, especially in environments with high mobility or changing radio wave conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096669_12112026_PF_FP_ABST
    Figure KR2026096669_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method, according to one embodiment of the present specification, comprises the steps of: receiving configuration information; receiving a reference signal; and transmitting information based on a future time point. The future time point related to beam failure is predicted on the basis of the reference signal. On the basis of the future time point being within a first time interval, the information includes information related to a new beam update performed by a terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for predicting beam failure

[0001] This specification relates to a method and apparatus for predicting beam failure.

[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] In 6G, operations between base station terminals utilizing AI / ML are expected to expand further. Regarding beams, discussions on standardization for beam failure prediction may proceed.

[0005] In the case of the beam failure operation of the existing NR, since it is a procedure to recover after a beam failure occurs, there is a possibility that a significant delay may occur in completing beam recovery depending on whether a new beam is found.

[0006] In other words, conventional beam management methods have limitations in that recovery procedures are performed only after a beam failure actually occurs, so subsequent operations are initiated when communication quality has already degraded or the link is disconnected. For example, since a terminal must perform procedures to search for a new beam, select a suitable beam, and transmit and receive relevant control signals if necessary after a beam failure occurs, additional time delay may occur until a new beam is found.

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

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

[0009] A method according to one embodiment of the present specification for solving the aforementioned problem comprises the steps of receiving configuration information, receiving a reference signal, and transmitting information based on a future time point. Based on the reference signal, the future time point related to a beam failure is predicted. Based on the fact that the future time point is within a first time interval, the information is characterized by including information related to a new beam update performed by the terminal. Accordingly, since a beam failure can be preemptively responded to through a beam update based on the predicted time point, the impact caused by a delay that may occur due to the beam failure can be minimized.

[0010] According to the embodiments of this specification, a beam failure can be preemptively addressed through a beam update between the base station and the terminal before the beam failure occurs. Furthermore, delays associated with new beam search can be reduced, data transmission continuity can be improved, and packet loss and retransmission can be reduced.

[0011] In addition, service continuity can be ensured by minimizing interruption time. In other words, link stability and communication reliability can be improved.

[0012] Furthermore, since the frequency of recovery procedures performed after a beam failure can be reduced, control signal overhead can be decreased, the processing burden on terminals and base stations can be alleviated, and the efficiency of system resource utilization can be improved. In particular, it can support more stable beam-based communication even in environments with high mobility or situations where the radio wave environment changes frequently.

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

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

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

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

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

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

[0019] FIG. 6 is a diagram illustrating a beam failure recovery operation to which the method proposed in this specification can be applied.

[0020] FIG. 7 is a diagram illustrating terminal operation according to an embodiment of the present specification.

[0021] FIG. 8 illustrates a terminal operation based on an embodiment of the present specification.

[0022] FIG. 9 illustrates base station operation based on an embodiment of the present specification.

[0023] FIG. 10 is a flowchart illustrating base station / terminal operation based on an embodiment of the present specification.

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

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

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

[0027] 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."

[0028] 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."

[0029] 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."

[0030] 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."

[0031] 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."

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

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

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

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

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

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

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

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

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

[0041] < AI / ML for Wireless Communication >

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0068] (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.

[0069] (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.

[0070] (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.

[0071] (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.

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

[0073] (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.

[0074] (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.

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

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

[0077] (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.

[0078] (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.

[0079] (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.

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

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

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

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

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

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

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

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

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

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

[0090] (1) Beam management

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0122] (3) Positioning

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

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

[0125] < Explanation regarding Rel-18 / 19 AI / ML beam management >

[0126] In the Rel-18 AI / ML study item, performance analysis and potential specification impact were studied through evaluation when NW and / or UE-side AI / ML models were operating in three use cases: CSI compression / prediction, beam management, and positioning. In particular, for the beam management use case, the study was conducted by dividing the sub-use cases into BM-case1 and BM-case2 to analyze performance and potential specification impact regarding spatial domain beam prediction and temporal beam prediction. The WID objectives of the AI / ML BM, as well as BM-case1 and BM-case2, are summarized in Tables 1 through 3 below.

[0127] - WID goals for AI / ML BM

[0128]

[0129] - BM-case1: Spatial domain downlink beam prediction for beam set A based on measurement results of beam set B

[0130]

[0131] - BM-case2: Temporal downlink beam prediction for Beam Set A based on historical measurement results of Beam Set B

[0132]

[0133] In addition, an example of the operation for data collection of an AI / ML model in a beam management use case is shown in Table 4 below.

[0134]

[0135] In addition, an example of the operation for inference of an AI / ML model in a beam management use case is shown in Table 5 below.

[0136]

[0137] Meanwhile, the Rel-18 AI / ML study discussed NW / UE-sided AI / ML operations that predict the best beam of Set A based on Set B measurements. In the case of UE-sided AI / ML, the terminal needs to measure Set B and report the predicted Set A beam, whereas in the case of NW-sided AI / ML, the terminal needs to report the Set B measurements.

[0138] Rel-19 AI / ML beam management is divided into spatial domain DL Tx beam prediction and temporal DL Tx beam prediction. Regarding the former, standardization discussions are underway on what information (e.g., predicted top-K beam, predicted RSRP of predicted top-K beam, etc.) the terminal should report when reporting the predicted Set A beam, and regarding the latter, what beam-related information (e.g., beam ID, RSRP, beam pattern ID, beam group ID, and bitmap information, etc.) should be included when the terminal performs Set B measurement / report. Furthermore, standardization discussions are also underway regarding the configuration of CSI reporting for data collection, inference, and performance monitoring, particularly in terms of the life cycle management of UE-side AI / ML models.

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

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

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

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

[0143] < Explanation regarding Rel-15 / 16 / 17 beam failure recovery >

[0144] 1. Beam failure recovery (in 3GPP NR Rel-15)

[0145] During the DL / UL beam management process, beam mismatch issues may occur depending on the configured beam management cycle. In particular, if the wireless channel environment changes due to the terminal moving, rotating, or the movement of surrounding objects (e.g., switching from a Line of Sight (LOS) environment to a Non-LoS environment due to a beam block), the optimal DL / UL beam pair may change. Since this change is typically handled by the beam management process guided by network instructions, a beam failure event can be said to have occurred when tracking fails. The terminal can determine whether such a beam failure event has occurred based on the reception quality of the downlink RS, and a report message regarding this situation or a message requesting beam recovery (let's call it a beam failure recovery request (BFRQ) message) must be transmitted from the terminal. Upon receiving such a message, the base station can perform beam recovery through various processes, such as transmitting a beam RS or requesting a beam reporting. This series of beam recovery processes is called beam failure recovery (BFR). Rel-15 NR standardized the beam failure recovery (BFR) process for PCells or PScells (collectively referred to as special cells or SpCells) where contention-based PRACH resources are always available. This procedure consists of the terminal's beam failure detection (BFD) process, the BFRQ process, and the terminal monitoring the base station's response to the BFRQ as operations within the serving cell, as follows (Reference: 3GPP TS38.213, TS38.321, TS38.331).

[0146] 1-1. Beam Failure Detection (BFD)

[0147] If all PDCCH beams fall below a defined quality value (Q_out), it is said that a beam failure instance has occurred (where quality is based on the hypothetical BLER (block error rate): that is, the probability of failing to demodulate control information assuming it was transmitted to the PDCCH).

[0148] Here, "all PDCCH beams" refers to the case where one or more search spaces for monitoring PDCCH can be configured on the terminal, and beams can be configured differently for each search space, and all beams fall below the BLER threshold. The following two methods are supported as criteria for the terminal to determine BFD RS.

[0149] [Implicit configuration of BFD RSs] In each search space, a control resource set ID (CORESET [refer to TS38.213, TS38.214, TS38.331]) is configured, which is a resource area where PDCCH can be transmitted. For each CORESET ID, RS information that is QCLed in terms of spatial RX parameters (e.g., CSI-RS resource ID, SSB ID) can be indicated / configured (in NR standards, the QCLed RS is indicated / configured through TCI (transmit configuration information) instructions). Here, an RS that is QCLed in terms of spatial RX parameters (e.g., QCL Type D in TS38.214) means a method in which the base station informs the terminal to use (or is allowed to use) the same beam that was used for receiving the spatially QCLed RS when receiving the corresponding PDCCH DMRS. Ultimately, from the base station's perspective, this is a method of informing the terminal that the same or similar transmission beam (e.g., cases where the beam direction is the same or similar but the beam width is different) will be applied for transmission between spatially QCLed antenna ports.

[0150] [explicit configuration of BFD RSs] The base station may explicitly configure beam RS(s) for the above purpose (beam failure detection), in which case the corresponding beam RS(s) correspond to the 'all PDCCH beams'.

[0151] Whenever an event occurs in which the hypothetical BLER measured based on BFD RS(s) at the terminal physical layer degrades above a specific threshold, the MAC sublayer is notified that a 'beam failure instance (BFI)' has occurred. The terminal MAC sublayer determines that a beam failure has occurred and initiates a related RACH operation if a BFI occurs a certain number of times (beamFailureInstanceMaxCount) within a certain time (BFD timer).

[0152] Below, we examine the MAC layer operations related to BFD.

[0153] The MAC entity is:

[0154] 1> When a beam failure instance indication is received in lower layers:

[0155] 2> Start or restart beamFailureDetectionTimer

[0156] 2> Increase BFI_COUNTER by 1.

[0157] 2> If BFI_COUNTER > = beamFailureInstanceMaxCount:

[0158] 3> Initiate the random access procedure in SpCell.

[0159] 1> If beamFailureDetectionTimer has expired; or

[0160] 1> If beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any of the reference signals used for beam failure detection is reset by the upper layer:

[0161] 2> Set BFI_COUNTER to 0.

[0162] 1> If the random access procedure is successfully completed:

[0163] 2> Set BFI_COUNTER to 0.

[0164] 2> Stop the (configured) beamFailureRecoveryTimer.

[0165] 2> The beam failure recovery procedure is considered to have been successfully completed.

[0166] 1-2. BFRQ (based on PRACH): New beam identification + PRACH transmission

[0167] As described above, when a certain number of BFIs occur, the terminal determines that a beam failure has occurred and can perform a beam failure recovery operation. As an example of a beam failure recovery operation, a beam failure recovery request (BFRQ) operation based on a RACH procedure (i.e., PRACH) can be performed. The BFRQ procedure will be examined in detail below.

[0168] The base station can configure the RS list (candidateBeamRSList) corresponding to candidate beams that can replace the corresponding terminal in the event of a BF (Block Break) via RRC, and dedicated PRACH resources can be configured for these candidate beams. These dedicated PRACH resources are characterized as non-contention-based PRACH resources (also known as contention-free PRACH); if a beam is not found in the list, a contention-based PRACH is transmitted by selecting one from the pre-configured SSB resources. The specific procedure is as follows.

[0169] Step 1) The terminal searches for a beam with a defined quality value (Q_in) or higher among the RSs configured by the base station as the candidate beam RS set.

[0170] If a single beam RS exceeds the threshold, select that beam RS.

[0171] If multiple beam RSs exceed the threshold, select a random one among them.

[0172] If there are no beams exceeding the threshold, perform Step 2.

[0173] Note 1: Beam quality here is based on RSRP.

[0174] Note 2: The RS beam set configured by the above base station has the following three cases.

[0175] All beam RSs within the RS beam set are composed of SSBs.

[0176] All beamRSs within the RS beam set are composed of CSI-RS resources.

[0177] The beamRSs within the RS beam set consist of SSBs and CSI-RS resources.

[0178] Step 2) The terminal searches for a beam among the SSBs (connected to the contention-based PRACH resource) that has a quality value (Q_in) or higher.

[0179] If one SSB exceeds the threshold, select the corresponding beam RS.

[0180] If multiple SSBs exceed the threshold, select a random one among the corresponding beam RSs.

[0181] If there are no beams exceeding the threshold, perform Step 3.

[0182] Step 3) The terminal selects an arbitrary SSB among the SSBs (connected to the contention-based pRACH resource).

[0183] The terminal transmits the PRACH resource and preamble, which are directly or indirectly connected to the beam RS (CSI-RS or SSB) selected in the above process, to the base station.

[0184] Here, the direct connection setting is used in the following cases 1) or 2).

[0185] 1) When contention-free PRACH resource & preamble are configured for a specific RS within a candidate beam RS set separately configured for BFR purposes

[0186] 2) In cases where a (contention-based) PRACH resource & preamble is configured and mapped one-to-one with SSBs configured for other purposes such as random access

[0187] Here, indirect connection settings are used in the following cases.

[0188] If contention-free PRACH resource & preamble are not configured for a specific CSI-RS within a candidate beam RS set separately configured for BFR purposes

[0189] At this time, the terminal selects a (contention-free) PRACH resource & preamble connected to an SSB that is designated as being receivable in the same receiving beam as the corresponding CSI-RS (i.e., quasi-co-located (QCLed) with respect to spatial Rx parameter).

[0190] 1-3. Monitoring of gNB's response to the BFRQ

[0191] The terminal monitors the reply from the base station (gNB) regarding the PRACH transmission.

[0192] Here, the response to the contention-free PRACH resource & preamble is transmitted to the PDCCH masked with C-RNTI, and is received in a search space that is separately configured with RRC for BFR.

[0193] The above search space is set to a specific CORESET (for BFR).

[0194] The response to Contention PRACH reuses the CORESET (e.g., CORESET 0 or CORESET 1) and search space set for the general contention PRACH-based random access process.

[0195] If there is no response for a certain period of time, the terminal repeats the New beam identification & selection process and the BFRQ & monitoring gNB's response process.

[0196] The above process can be performed until the preset maximum number of PRACH transmissions N_max is reached or the set timer (BFR timer) expires.

[0197] When the above timer expires, the terminal stops contention-free PRACH transmission, but contention-based PRACH transmission based on SSB selection can be performed until N_max is reached.

[0198] FIG. 6 is a diagram illustrating a beam failure recovery operation to which the method proposed in this specification can be applied. Specifically, FIG. 6 illustrates a beam failure recovery operation in a primary cell (PCell).

[0199] 2. Beam failure recovery (in 3GPP NR Rel-16)

[0200] As mentioned above, the PRACH-based BFR process was standardized in Rel-15 NR. However, due to technical limitations—such as the fact that during Carrier Aggregation (CA), some SCells may not have a UL carrier, and even if they do, contention-based PRACH cannot be configured—this process is applied only to PCells or PSCells. This limitation is particularly problematic when operating PCells in low-frequency bands (e.g., below 6 GHz) while intending to operate SCells in high-frequency bands (e.g., 30 GHz); in such cases, BFR cannot be supported in the high-frequency band where it is actually needed. For this reason, standardization for BFR support for SCells is currently underway in the Rel-16 NR MIMO work item. As a result of standardization discussions to date, it is planned to configure (dedicated) PUCCH resource(s) used to notify the base station that a SCell failure has occurred in the SpCell, at least for DL-only SCells, since UL transmission to the SCell is impossible, and to use these to perform BFRQ for the SCell. For convenience, the above PUCCH will be referred to as BFR-PUCCH below.

[0201] As explained in the previous chapter, if the role of BFR-PRACH standardized in Rel-15 was to transmit 'beam failure occurrence + new beam RS (set) information' together to the base station, the role of BFR-PUCCH is to report only 'beam failure occurrence for SCell(s)', and to report to the subsequent MAC-CE (or UCI) which SCell(s) the beam failure occurred in (e.g., CC index(s)), whether a new beam exists for the SCell(s), and if a new beam exists, the corresponding beam RS ID (+its / their quality / qualities (e.g., RSRP or SINR)). The subsequent beam report does not always have to be triggered, and it is also possible for the base station to deactivate the SCell(s) that have BFR settings configured for the terminal after receiving BFR-PUCCH. The reason for designing it this way is that there may be cases where dozens of SCells are connected to a single PCell / PSCell, and from the base station's perspective, there may be many terminals sharing a single PCell / PSCell UL. Considering these cases, it is desirable to minimize the amount of UL resources reserved for each terminal in the PCell / PSCell for SCell BFRQ purposes.

[0202] 3. Beam failure recovery for M-TRP (in 3GPP NR Rel-17)

[0203] In the Rel-17 beam failure recovery enhancement, standardization was carried out to detect TRP-specific beam failures and perform beam failure recovery in S-DCI-based M-TRP scenarios and M-DCI-based M-TRP scenarios within a specific CC / BWP, taking into account the M-TRP environment. A major enhancement is that up to two BFD-RS sets (TRP-specifically) and up to two BFR-PUCCH sets can be configured within the CC / BWP, allowing the terminal to notify the base station of the occurrence of a beam failure for one or two TRPs within the specific CC / BWP and perform BFRQ. In the case of SCell, as described above, BFR operations for up to 2 TRPs can be performed via (BFR-PUCCH +) BFR MAC CE, similar to Rel-16 BFR operations; in the case of PCell, if a BF occurs in a specific TRP among the 2 TRPs, operations can be performed via (BFR-PUCCH +) BFR MAC CE, or if a BF occurs in both TRPs, PRACH-based BFR operations can be performed, similar to Rel-15 BFR. When the base station fully receives the BFR MAC CE (when the terminal performs a new beam indication via the corresponding BFR MAC CE), the terminal can update the CORESET(s) beam associated with the TRP that reported the BF occurrence to the previously reported new beam. Through this operation, the terminal is able to report TRP-specific BF occurrence and new beam indication to the base station and update the DL reception beam for the TRP where the failure occurred.

[0204] The symbols / abbreviations / terms used in this specification are as follows.

[0205] BM: beam management

[0206] CQI: channel quality indicator

[0207] CRI: CSI-RS (channel state information - reference signal) resource indicator

[0208] CSI: channel state information

[0209] CSI-IM: channel state information - interference measurement

[0210] CSI-RS: channel state information - reference signal

[0211] DMRS: demodulation reference signal

[0212] FDM: frequency division multiplexing

[0213] FFT: fast Fourier transform

[0214] IFDMA: interleaved frequency division multiple access

[0215] IFFT: inverse fast Fourier transform

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

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

[0218] MAC: medium access control

[0219] NZP: non-zero power

[0220] OFDM: orthogonal frequency division multiplexing

[0221] PDCCH: physical downlink control channel

[0222] PDSCH: physical downlink shared channel

[0223] PMI: precoding matrix indicator

[0224] RE: resource element

[0225] RI: Rank indicator

[0226] RRC: radio resource control

[0227] RSSI: received signal strength indicator

[0228] Rx: Reception

[0229] QCL: quasi co-location

[0230] SINR: signal to interference and noise ratio

[0231] SSB (or SS / PBCH block): synchronization signal block (including primary synchronization signal, secondary synchronization signal and physical broadcast channel)

[0232] TDM: time division multiplexing

[0233] TRP: transmission and reception point

[0234] TRS: tracking reference signal

[0235] Tx: transmission

[0236] UE: user equipment

[0237] ZP: zero power

[0238] In NR standards, QCL configuration via TCI state settings and spatial relation configuration are utilized to configure the uplink and downlink receiver and transmitter beams of a terminal. In the Rel-15 NR standard, RRC and MAC CE signaling were primarily used for uplink receiver and transmitter beams, and dynamic signaling was permitted only for the PDSCH receiver beam by utilizing the TCI state field of the DL grant DCI. With the introduction of the unified TCI framework through the Rel-17 / 18 NR standards, a method for dynamically managing the common beam was introduced by indicating the TCI using DCI for receiver and transmitter beams. Meanwhile, in the Rel-18 AI / ML study item, a study was conducted on the 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 the operation of NW / UE-sided AI / ML that predicts the best beam of Set A based on Set B measurements. In the case of UE-sided AI / ML, the terminal needs to measure Set B and report the predicted Set A beam, and in the case of NW-sided AI / ML, the terminal needs to report the Set B measurement. Additionally, BM-case1 and BM-case2 are supported for UE-sided AI / ML operations, where BM-case1 is an operation for spatial domain DL Tx beam prediction and BM-case2 is an operation for temporal DL Tx beam prediction.

[0239] Meanwhile, in Rel-19, regarding the CSI report configuration for the inference result report in the BM-case1 and BM-case2 scenarios, Set A and Set B can be configured, and an agreement was reached on the time domain behavior of CSI-RS that can be configured as Set B. In addition, it was agreed that the report configuration for performance monitoring during the DL Tx beam prediction operation of UE-sided AI / ML can be configured separately from the CSI report configuration for the inference result report.

[0240] In the RAN2 standardization discussions, studies are being conducted on operations in which terminals utilize UE-side AI / ML to perform predictions regarding events that affect terminal mobility during operations such as RRM (Radio Resource Monitoring). Discussions are underway regarding operations such as using an AI / ML model to predict the probability of a specific event, such as RLF (Radio Link Failure), occurring within a specific time window and reporting it to the base station (e.g., direct prediction in RAN2 discussion), or using an AI / ML model to predict the time of occurrence of a specific event and reporting it to the base station (e.g., indirect prediction in RAN2 discussion).

[0241] In the RAN1 standardization discussions, in the field of Rel-19 AI / ML beam management, discussions were held regarding operations such as predicting and reporting to the base station the occurrence of Beam Failure (BF) or RLF using UE-side AI / ML, as well as predicting and reporting to the base station the new beam using UE-side AI / ML, as mentioned in the explanation regarding beam failure recovery in section G above.

[0242] The NR BFR operation introduced in RAN1 is a recovery procedure performed after a beam failure has already occurred, so there is a possibility of significant delay in completing beam recovery depending on whether a new beam has been found. Furthermore, as mentioned above, although proposals regarding beam failure prediction operations were made in the Rel-19 AI / ML beam management field, the terminal may need to perform the beam recovery procedure more proactively to reduce the delay in recovery as described above, rather than simply reporting beam failure predictions. Based on this background, the following examines a method for a terminal to perform beam failure prediction and report it using UE-sided AI / ML, as well as subsequent terminal operations.

[0243] Problem: As mentioned in the explanation regarding beam failure recovery above, BFR operations have been introduced in NR standardization; however, since these BFR operations are procedures for recovery after a beam failure has already occurred, there is a possibility of significant delay in completing beam recovery depending on whether a new beam has been found. Furthermore, as mentioned above, although there have been proposals in the Rel-19 AI / ML beam management field regarding beam failure prediction operations, the terminal may need to perform the beam recovery procedure more preemptively to reduce the delay in such recovery compared to a simple beam failure prediction reporting operation. A method to solve this problem will be described in Proposal 1 below.

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

[0245] Below, beam may refer to a DL, UL, or / and joint TCI state. Below, TRP may refer to a CORESET pool index, CORESET group, CORESET(s), a specific beam(s) or / and beam group(s).

[0246] Proposal 1

[0247] The terminal may receive DL reference signal(s) (RS(s)) for beam / TRP / cell failure detection or / and beam / TRP / cell failure prediction for a specific CC / BWP. For example, the terminal may receive one or more transmission instances / occasions for the DL RS. For example, the DL RS(s) may be based on DL RS resource(s) configured for beam failure prediction. For example, the DL RS(s) may be based on DL RS resource(s) previously configured for beam failure detection. For example, the DL RS(s) may be based on DL RS resource(s) configured for prediction. For example, the DL RS(s) may be based on DL RS resource(s) associated with the indicated TCI(s). The foregoing examples are for convenience of explanation only and do not imply that the scope of DL RS(s) to which the embodiments of this specification may be applied is limited to the foregoing examples. The terminal can predict the presence or absence of a beam / TRP / cell failure or / and the time at which a beam / TRP / cell failure occurs at a future point in time by utilizing a UE-side AI / ML model. Based on the predicted time at which a beam / TRP / cell failure occurs, the terminal can perform an operation based on at least one of the following embodiments. Embodiments 1) to 3) will be described below with reference to FIG. 7.

[0248] FIG. 7 is a drawing illustrating terminal operation according to an embodiment of the present specification. Specifically, FIG. 7 is a drawing illustrating terminal operation according to each of the following embodiments 1) to 3).

[0249] Example 1)

[0250] If a beam / TRP / cell failure is predicted to occur within the first time point to the second time point, the terminal can update the receiving / transmitting beam for the DL / UL channel(s) / RS(s) with a new beam (predicted) for the CC / BWP / TRP where the beam failure is predicted.

[0251] According to one embodiment, the first time point may be based on i) the time point of receiving a DL reference signal(s) (RS(s)) for beam / TRP / cell failure detection or / and beam / TRP / cell failure prediction, ii) the time point of completing beam / TRP / cell failure prediction, or iii) the time point of reporting (scheduled) beam / TRP / cell failure prediction. For example, the time point of receiving may be based on the most latest transmission occasion before the CSI reference resource.

[0252] According to one embodiment, the second time point may be a time point T1 [ms and / or slots] after the first time point.

[0253] The point in time when the above terminal performs an update with a (predicted) new beam may be a point in time when T1 has elapsed from the above first point in time or a point in time set / instructed by the base station.

[0254] For an immediate new beam update at the terminal side, the base station also needs to know whether the terminal is performing a new beam update. According to one embodiment, a (low latency) UL channel / RS (e.g., PRACH, (SR-)PUCCH, SRS, PUSCH, etc.) for notifying the base station of the new beam update operation of Embodiment 1 may be separately configured by the base station on the terminal. Additionally, the said UL channel / RS may include information regarding which beam the terminal will perform a new beam update with. Such a UL channel / RS notifying the terminal of the new beam update may be reported to the base station within T1 from the first time point. For example, the said UL channel / RS may be transmitted based on the beam prior to the terminal updating to the new beam. Subsequently, the base station may transmit confirmation information to the terminal that it has received the report regarding the terminal's new beam update via the said UL channel / RS without issue. Based on the receipt of the confirmation information, the terminal may perform a (predicted) new beam update. The statement that the above terminal performs an update with a (predicted) new beam may mean that the terminal utilizes the new beam for downlink and uplink transmission / reception from the time when T1 has elapsed from the first time point or from the time set / instructed by the base station.

[0255] According to one embodiment, information regarding which new beam the terminal should update to can be agreed upon, defined, or set between the base station and the terminal. This information can be agreed upon, defined, or set in the form of a default new beam. More specifically, the default new beam can be extended to the concept of a default new beam set. The default new beam set may include one or more beam information. Beam information within the default new beam set can be updated by base station settings or instructions. When the default new beam set is set, the terminal can perform a (predicted) new beam update on one of the new beams included in the beam set according to Embodiment 1.

[0256] For example, the operation of Embodiment 1 above may be performed only when uplink transmission of the terminal is not available prior to the predicted beam / TRP / cell failure time. More specifically, if the TDD DL / UL slot configuration of a radio frame in 10 ms units of a specific terminal is configured as DDDDUDDDDU by base station configuration / instruction, and the predicted beam / TRP / cell failure time in the 6th slot of the configuration is the 9th slot, it is expected that uplink transmission will be impossible prior to the predicted failure time. In such a case, as in the operation of Embodiment 1, the terminal may preemptively perform an update to a new beam and notify the base station that such an operation has been performed. When notifying the base station that such an operation (new beam update) has been performed, the terminal may report to the base station using the updated new beam (i.e., DL / UL receiving / transmitting beam).

[0257] Effect of Example 1) The above Example 1 can be performed when the time at which a beam / TRP / cell failure is predicted, as shown in FIG. 7, is a time in the near future compared to the time according to Example 2 / Example 3 (time based on T2 / T2), thereby reducing the delay caused by the failure. As a specific example, if a failure occurs or the terminal's uplink transmission is not available prior to the time at which a beam / TRP / cell failure is predicted, the terminal can predict the beam / TRP / cell failure preemptively and update / switch to a new beam / TRP / cell rather than reporting the beam failure to the base station, such as in legacy NR BFR operation.

[0258] Example 2)

[0259] If a beam / TRP / cell failure is predicted to occur within the third time point from the first time point (or within the third time point from the second time point (a time point after T1 elapsed from the first time point)), the terminal may report to the base station (similar to the beam failure recovery operation of 5G NR) information that a (beam / cell / TRP-specific) beam failure has occurred for a specific CC / BWP (including SpCell and SCell) through UL resources such as BFR-PUCCH (+ BFR MAC CE) or PRACH (e.g., information about the CC / BWP / TRP(s) where the beam failure occurred, or / and information about (predicted) (candidate) new beam(s), etc.) that a beam failure has occurred for a specific CC / BWP (including SpCell and SCell).

[0260] According to one embodiment, the third time point may be a time point T2 [ms and / or slots] after the first time point.

[0261] For example, the above reporting operation may be based on the beam failure recovery operation of Rel-15 / 16 / 17.

[0262] For example, the operation of Embodiment 2 above may be performed only when uplink transmission of the terminal is not available prior to the predicted beam / TRP / cell failure time (based on TDD DL / UL configuration). More specifically, if the TDD DL / UL slot configuration of a radio frame in 10 ms units of a specific terminal is configured as DDDDUDDDDU by base station configuration / instruction, and the predicted beam / TRP / cell failure time in the 6th slot in that configuration is the 9th slot, it is expected that uplink transmission will be impossible prior to the predicted failure time. After determining the actual failure, the terminal may report actual BFR information to the base station via PUCCH / PUSCH.

[0263] Effect of Example 2) As shown in FIG. 7, Example 2 is performed when the time at which a beam / TRP / cell failure is predicted is a time further in the future than Example 1 and a time closer in the future than Example 3, thereby reducing the delay caused by the failure. As a specific example, if the uplink transmission of the terminal is not available before the predicted time of beam / TRP / cell failure, the beam / TRP / cell failure occurs, so the terminal can report the beam failure similarly to legacy BFR operation. The terminal reports this information to the base station, and when the base station notifies the terminal that it has correctly received the BFR / BFRQ, the receiving / transmitting beams of the DL / UL channel(s) / RS(s) of the beam / TRP / cell where the failure occurred can be updated with the new beam(s) reported by the terminal (predicted) (candidate).

[0264] Example 3)

[0265] If a beam / TRP / cell failure is predicted to occur within the first time point to the fourth time point (or within the fourth time point from the third time point (a time point after T2 elapsed from the second time point)), the terminal may report to the base station information related to the predicted beam failure (e.g., information about the CC / BWP / TRP(s) where the beam failure is predicted, ii) the predicted time of the beam failure, or / and iii) information about the predicted (candidate) new beam(s), etc., by utilizing UL resources such as i) PUCCH (e.g., UCI, SR-PUCCH, BFR-PUCCH) or / and PUSCH (e.g., UCI, BFR MAC CE).

[0266] According to one embodiment, the fourth time point may be a time point T3 [ms and / or slots] after the first time point.

[0267] The operation of Example 3 above can be performed only when uplink transmission of the terminal is available before the predicted beam / TRP / cell failure time (based on TDD DL / UL configuration).

[0268] Effect of Example 3) Example 3 can be performed when the time at which a beam / TRP / cell failure is predicted, as shown in FIG. 7, is a time in the distant future compared to Examples 1 and 2, or when uplink transmission of the terminal is available before the time at which a beam / TRP / cell failure is predicted, thereby reducing the delay caused by the failure. Specifically, Example 3 has the purpose of reporting information related to a predicted beam / TRP / cell failure to the base station. More specifically, since a beam / TRP / cell failure has not yet occurred, if the terminal reports this information to the base station, the base station can perform preemptive follow-up measures (e.g., beam / TRP / cell change / update).

[0269] According to one embodiment, the terminal reporting operation may vary depending on which cell corresponds to the cell where the predicted beam / TRP / cell failure occurs.

[0270] For example, if the cell where a specific terminal’s predicted beam / TRP / cell failure occurs is a SpCell (i.e., PCell, PSCell), and the SpCell’s uplink transmission is not available prior to the predicted failure time (based on TDD DL / UL configuration), the terminal may perform PRACH-based BFR (e.g., based on legacy SpCell BFR) (if the SpCell’s uplink transmission is available prior to the predicted failure time, the terminal may report the predicted beam failure information to the base station via the SpCell’s UL resource).

[0271] On the other hand, if the cell where a predicted beam / TRP / cell failure occurs for a specific terminal is a SCell, the following actions may be performed. For example, if uplink transmission for the SCell is available prior to the predicted failure time, the terminal may send the predicted beam / TRP / cell failure information via the SCell PUSCH. For example, if uplink transmission for the SCell is not available prior to the predicted failure time, the terminal may send actual BFR information (e.g., based on legacy SCell BFR) via the SpCell PUCCH / PUSCH or SCell PUSCH.

[0272] According to one embodiment, when a terminal performs a report on temporal DL Tx beam prediction, the base station may be configured to always report predicted result values ​​for one or more serving beams (indicated TCI(s)), BFD-RS(s), and / or candidate new beam(s), etc. of the terminal (in this case, set A and / or B may include DL reference signal(s) (RS(s)) for beam / TRP / cell failure detection or / and beam / TRP / cell failure prediction). For example, within the predicted Top-K beam reported by the terminal, a natural number M set by the base station ( <K)개 beam의 경우, 단말은 기지국이 지정한 빔(e.g., 하나 이상의 serving beam(indicated TCI(s)), BFD-RS(s), and / or candidate new beam(s))에 대한 예측 결과 보고를 수행할 수 있다. 상기 M개 beam의 경우, 기지국으로부터 설정 / 지시된 prediction instance 모두에 있어서 보고가 수행될 수 있다. 만약, 상기 temporal DL Tx beam에 대한 report에 있어서 N번 이상(N은 자연수이며 기지국으로부터 설정 / 지시되거나 specification에 의해 정의되는 값)의 prediction instance에 있어서 하나 이상의 serving beam(indicated TCI(s)) 또는 / 및 BFD-RS(s)의 품질 / 순위가 일정 threshold 이하로 떨어지는 일이 발생하는 경우, 단말은 beam / TRP / cell-level failure가 prediction된 것으로 판단하고 상기 제안 1의 실시예 1 내지 3의 동작을 수행할 수 있다.More specifically, depending on the time of the prediction instance in which the quality / ranking of one or more serving beams (indicated TCI(s)) or / and BFD-RS(s) falls below a certain threshold (e.g., depending on which time interval T1, T2, and T3 the prediction instance time falls into from the prediction report time), the terminal may distinguish and perform the operations of Examples 1 to 3.

[0273] For example, T1 associated with the second time point, T2 associated with the third time point, and T3 associated with the fourth time point may be values ​​reported to the base station by the terminal. As a specific example, T1, T2, and T3 may be values ​​based on UE capability.

[0274] For example, T1 related to the second time point, T2 related to the third time point, and T3 related to the fourth time point can be set / instructed to the terminal by the base station.

[0275] For example, T1 associated with the second time point, T2 associated with the third time point, and T3 associated with the fourth time point may be predefined values.

[0276] In the case of the above embodiments, operation may be performed by a combination of one or more embodiments.

[0277] 1) Receiver (Entity A):

[0278] FIG. 8 illustrates a terminal operation based on an embodiment of the present specification.

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

[0280] 1) The terminal receives settings related to beam / TRP / cell failure prediction.

[0281] The above settings may include measurement / reporting settings related to BFD-RS, Set B Beam, or / and Set A Beam to be used as input data during the inference operation of an AI / ML model / functionality for beam / TRP / cell failure prediction or an AI / ML model / functionality for beam prediction of a base station / terminal.

[0282] 2) The terminal performs beam / TRP / cell failure prediction and then performs a report based on Examples 1 to 3 of Proposal 1.

[0283] The transmission of the report described above may have periodic / semi-persistent / aperiodic / event-triggered time domain behavior, and beam / TRP / cell failure prediction may be based on Examples 1 to 3 of Proposal 1 depending on the time at which the failure occurs.

[0284] 3) Based on the above report, the terminal changes the assumptions (e.g., QCL assumption, TCI state) for the receiving / transmitting beam of the base station DL / UL channel(s) / RS(s).

[0285] Changes to the assumptions regarding the above beam can be performed based on settings / instructions from the base station.

[0286] After the change in the assumption regarding the above beam is performed by the terminal, the terminal may report the performance of the operation to the base station.

[0287] 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 management operation of the terminal according to the aforementioned embodiments may be omitted or added.

[0288] 2) Transmitter(Entity B):

[0289] FIG. 9 illustrates base station operation based on an embodiment of the present specification.

[0290] An example of 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.

[0291] 1) The base station transmits settings related to beam / TRP / cell failure prediction.

[0292] The above settings may include measurement / reporting settings related to BFD-RS, Set B Beam, or / and Set A Beam to be used as input data during the inference operation of an AI / ML model / functionality for beam / TRP / cell failure prediction or an AI / ML model / functionality for beam prediction of a base station / terminal.

[0293] 2) The base station receives a report based on embodiments 1 to 3 of Proposal 1.

[0294] The transmission of the report described above may have periodic / semi-persistent / aperiodic / event-triggered time domain behavior, and beam / TRP / cell failure prediction may be based on Examples 1 to 3 of Proposal 1 depending on the time at which the failure occurs.

[0295] 3) Based on the above beam report, the base station changes the Tx / Rx spatial filter for the base station DL / UL Tx / Rx beam.

[0296] Changes to the above beam can be set / instructed to the terminal by the base station.

[0297] Changes to the above beam may be reported from the terminal to the base station. For example, the base station may change the Tx / Rx spatial filter for the beam according to a beam change performed by the terminal (e.g., a new beam update operation).

[0298] 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 management operation of the terminal according to the aforementioned embodiments may be omitted or added.

[0299] 3) Receiver & Transmitter (Between Receiver and Transmitter)

[0300] FIG. 10 is a flowchart illustrating base station / terminal operation based on an embodiment of the present specification.

[0301] Specifically, FIG. 10 is a flowchart illustrating the operation of a terminal / base station according to FIG. 8 and FIG. 9 described above. Referring to FIG. 10, after the operations of (1) and (2), the base station / terminal can perform beam setting / instruction / change. In the case of the beam update of (3), it may be omitted as mentioned in the embodiments above.

[0302] The effects derived according to the embodiments of the present specification are as follows.

[0303] By utilizing terminal-side AI / ML models to perform beam / TRP / cell failure prediction, the terminal can proactively perform a new beam update, request beam failure recovery, or report a predicted beam failure depending on the timing of the failure. Accordingly, the delay required for recovery in the event of a beam / TRP / cell failure can be adaptively managed and reduced.

[0304] 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. 13 (e.g., the processor (110, 210) of FIG. 13).

[0305] 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. 13) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 13).

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

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

[0308] Referring to FIG. 11, a method according to one embodiment of the present specification may include a step of receiving setting information (S1110), a step of receiving a reference signal (S1120), and a step of transmitting information based on a future point in time (S1130).

[0309] In S1110, the terminal receives configuration information from the base station. For example, the configuration information may include information based on the embodiments of the above-described proposal 1.

[0310] For example, the above setting information may include at least one of information related to the time intervals (first to third time intervals) described below (e.g., at least one of a reference time point, T1, T2, and / or T3) and / or settings related to beam failure prediction (e.g., reference signal settings related to the prediction of a future time point, UL resource settings for transmitting information based on a future time point, etc.). As a specific example, information not included in the above setting information (e.g., at least one of a reference time point, T1, T2, T3, reference signal settings related to the prediction of a future time point, and / or UL resource settings for transmitting information based on a future time point) may be defined in advance.

[0311] In S1120, the terminal receives a reference signal from the base station. For example, a future point in time related to a beam failure can be predicted based on the reference signal. Specifically, the reference signal may be associated with downlink reference signal resource(s) set for beam failure prediction. Specifically, the reference signal may be associated with downlink reference signal resource(s) for BM-case2. Specifically, the reference signal may be associated with i) downlink reference signal resource(s) set for beam failure prediction and ii) downlink reference signal resource(s) for BM-case2.

[0312] In S1130, the terminal transmits information based on the future time point to the base station. At this time, the information may be information according to one of Embodiments 1) to 3) of the above-described Proposal 1. This will be explained in detail below.

[0313] According to one embodiment, based on the fact that the future time point is within a first time interval, the information may include information related to a new beam update performed by the terminal. This embodiment may be based on Embodiment 1) of Proposal 1.

[0314] For example, the first time interval may be an interval from the first-1 time point (e.g., the first time point of Example 1 of Proposal 1 described above) to the first-2 time point (e.g., the second time point of Example 1 of Proposal 1 described above). Specifically, the first-1 time point may be a reference time point. The first-2 time point may be a time point T1 after the first time point. The T1 may be a value in slot units or in ms units. In other words, the T1 may mean T1 slot(s) or T1 ms.

[0315] For example, the above information can be transmitted based on the beam prior to the update. Assuming the case where the first beam is updated to the second beam by a new beam update, the above information can be transmitted based on the first beam.

[0316] For example, the new beam update may be performed by the terminal alone or by the terminal based on instructions from the base station.

[0317] As a specific example, the new beam update can be performed after the transmission of the above information.

[0318] As a specific example, the new beam update may be performed based on receiving instructions (e.g., confirmation information) from the base station after the transmission of the above information. As an example, the new beam update may refer to an update of the default beam set. As a specific example, beam information within the default beam set (e.g., information about one or more beams) may be updated by the new beam update.

[0319] According to one embodiment, based on the future time point being within a second time interval, the information may include at least one of i) information indicating a cell associated with the beam failure, ii) information indicating a Transmission and Reception Point (TRP) associated with the beam failure, and / or iii) information regarding a candidate RS for new beam identification. This embodiment may be based on Embodiment 2) of Proposal 1.

[0320] For example, the second time interval may be the interval from the second time point (e.g., the second time point of Example 2 of Proposal 1 described above) to the second time point (e.g., the third time point of Example 2 of Proposal 1 described above). The second time point may be a time point T1 after the reference time point. The second time point may be a time point T2 after the reference time point. The T2 may be a value in slot units or in ms units. In other words, the T2 may mean T2 slot(s) or T2 ms.

[0321] For example, based on the fact that the future time point is within the second time interval and uplink transmission is impossible before the future time point: the information may be transmitted based on uplink resources after the future time point.

[0322] According to one embodiment, based on the fact that the future time point is within a third time interval, the information may include at least one of i) information indicating a cell associated with the beam failure, ii) information indicating a Transmission and Reception Point (TRP) associated with the beam failure, iii) information about the future time point and / or iv) information about a predicted new beam. This embodiment may be based on Embodiment 3) of Proposal 1.

[0323] For example, the third time interval may be the interval from the third-1 time point (e.g., the third time point of Example 3 of Proposal 1 described above) to the third-2 time point (e.g., the fourth time point of Example 3 of Proposal 1 described above). The third-1 time point may be a time point T2 after the reference time point. The third-2 time point may be a time point T3 after the reference time point. The T3 may be a value in slot units or in ms units. In other words, the T3 may mean T3 slot(s) or T3 ms.

[0324] For example, based on the fact that the future time point is within the third time interval and uplink transmission is possible before the future time point, the information may be transmitted based on uplink resources prior to the future time point.

[0325] According to one embodiment, based on the beam failure being related to a special cell (SpCell) (e.g., PCell or PSCell):

[0326] i) Based on the fact that uplink transmission is impossible prior to the above future point in time, the information may be transmitted based on a random access procedure initiated for beam failure recovery, and

[0327] ii) Based on the fact that uplink transmission is possible prior to the above future point in time, the information may be transmitted based on uplink resources associated with the SpCell prior to the above future point in time.

[0328] According to one embodiment, based on the beam failure being related to a secondary cell (SCell):

[0329] i) Based on the fact that uplink transmission is impossible prior to the above future point in time, the information may be transmitted based on an uplink channel associated with a Special Cell (SpCell), and

[0330] ii) Based on the fact that uplink transmission is possible prior to the above future point in time, the information may be transmitted based on uplink resources associated with the SCell prior to the above future point in time.

[0331] According to one embodiment, the method may further include a report transmission step. Specifically, the terminal may transmit to a base station a report (e.g., a CSI report) containing predicted information for each of one or more future time instances. The report may be based on a report on the temporal DL Tx beam prediction of Proposal 1 described above (e.g., a report related to BM-case2).

[0332] For example, the predicted information may include information related to at least one reference signal for beam failure prediction. As a specific example, the predicted information may include i) K beams (K RS indices) and / or ii) at least one of quality values ​​associated with the K beams. In this case, M of the K beams may be based on RS indices set / defined for beam failure prediction.

[0333] For example, the above report transmission step may be performed before S1130 or after S1130.

[0334] For example, the report transmission step may be based on S1130. More specifically, the information based on the predicted time point may be transmitted as the report. In this case, the information based on the predicted time point may include the predicted information. In other words, the report may include the information based on the predicted time point.

[0335] According to one embodiment, one or more values ​​(e.g., at least one of T1, T2, and / or T3) related to the determination of the time interval to which the future point in time belongs may be predefined or set by the base station. For example, the one or more values ​​may be predefined. For example, the one or more values ​​may be set based on the setting information.

[0336] The operation based on the above-described S1110 to S1130 and report transmission steps can be implemented by the device of FIG. 13. For example, referring to FIG. 13, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform the operation based on S1110 to S1130 and report transmission steps.

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

[0338] The steps S1210 to S1230 and the report reception step described below correspond to the operations based on the steps S1110 to S1130 and the report transmission step described in FIG. 11. 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. 11 corresponding to the operation.

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

[0340] Referring to FIG. 12, a method according to another embodiment of the present specification may include a setting information transmission step (S1210), a reference signal transmission step (S1220), and an information reception step based on a future point in time (S1230).

[0341] In S1210, the base station transmits configuration information to the terminal. For example, the configuration information may include information based on the embodiments of Proposal 1 described above.

[0342] In S1220, the base station transmits a reference signal to the terminal. For example, based on the reference signal, a future time point related to a beam failure can be predicted by the terminal.

[0343] In S1230, the base station receives information from the terminal based on the future time point.

[0344] According to one embodiment, based on the fact that the future time point is within a first time interval, the information may include information related to a new beam update performed by the terminal. This embodiment may be based on Embodiment 1) of Proposal 1.

[0345] According to one embodiment, the method may further include a step of receiving a report. Specifically, the base station may receive a report (e.g., a CSI report) containing predicted information for each of one or more future time instances from a terminal. The report may be based on a report on the temporal DL Tx beam prediction of Proposal 1 described above (e.g., a report related to BM-case2).

[0346] For example, the predicted information may include information related to at least one reference signal for beam failure prediction.

[0347] For example, the above report receiving step may be performed before S1230 or after S1230.

[0348] For example, the step of receiving the report may be based on S1230. More specifically, the information based on the predicted time point may be received as the report. In this case, the information based on the predicted time point may include the predicted information. In other words, the report may include the information based on the predicted time point.

[0349] The operation based on the above-described S1210 to S1230 and the report reception step can be implemented by the device of FIG. 13. For example, referring to FIG. 13, a base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform the operation based on S1210 to S1230 and the report reception step.

[0350] 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. 13.

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

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

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

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

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

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

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

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

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

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

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

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

[0363] 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 from a base station by a terminal; The step of receiving a reference signal from the base station by the terminal, and predicting a future point in time related to a beam failure based on the reference signal; and The method includes the step of transmitting information based on the future time point to the base station by the terminal, A method characterized by including information related to a new beam update performed by the terminal, based on the fact that the future time point is within a first time interval.

2. In Paragraph 1, The above first time interval is the interval from time point 1-1 to time point 1-2, and The above 1-1 point in time is the reference point, and A method characterized in that the above first and second time points are time points T1 after the first time point.

3. In Paragraph 1, A method characterized by including at least one of the following based on the fact that the future time point is within a second time interval: i) information indicating a cell associated with the beam failure, ii) information indicating a Transmission and Reception Point (TRP) associated with the beam failure, and / or iii) information regarding a candidate RS for new beam identification.

4. In Paragraph 3, The above second time interval is the interval from time point 2-1 to time point 2-2, and The above 2-1 point in time is a point in time T1 after the reference point, and A method characterized in that the above 2-2 point in time is a point in time T2 after the above reference point in time.

5. In Paragraph 3, Based on the fact that the aforementioned future time point is within the aforementioned second time interval and that uplink transmission is impossible before the aforementioned future time point: A method characterized by the above information being transmitted based on uplink resources after the above future point in time.

6. In Paragraph 1, A method characterized by including at least one of the following based on the fact that the future time point is within a third time interval: i) information indicating a cell associated with the beam failure, ii) information indicating a Transmission and Reception Point (TRP) associated with the beam failure, iii) information about the future time point and / or iv) information about a predicted new beam.

7. In Paragraph 6, The above third time interval is the interval from time point 3-1 to time point 3-2, and The above 3-1 point in time is a point in time T2 after the reference point, and A method characterized in that the above 3-2 point in time is a point in time T3 after the above reference point in time.

8. In Paragraph 6, Based on the fact that the aforementioned future time point is within the aforementioned third time interval and that uplink transmission is possible before the aforementioned future time point: A method characterized by the above information being transmitted based on uplink resources prior to the above future point in time.

9. In Paragraph 1, Based on the fact that the above beam failure is related to a special cell (SpCell): i) Based on the fact that uplink transmission is impossible prior to the above future point in time, the information is transmitted based on a random access procedure initiated for beam failure recovery, and ii) A method characterized by the fact that, based on the possibility of uplink transmission prior to the future point in time, the information is transmitted based on uplink resources associated with the SpCell prior to the future point in time.

10. In Paragraph 1, Based on the fact that the above beam failure is related to the secondary cell (SCell): i) Based on the fact that uplink transmission is impossible prior to the above future point in time, the information is transmitted based on an uplink channel associated with a Special Cell (SpCell), and ii) A method characterized by the fact that, based on the possibility of uplink transmission prior to the future point in time, the information is transmitted based on uplink resources associated with the SCell prior to the future point in time.

11. In Paragraph 1, The method further comprises the step of transmitting a report containing predicted information for each of one or more future time instances to the base station by the terminal; A method characterized by the above-mentioned predicted information including information related to at least one reference signal for beam failure prediction.

12. In Paragraph 1, A method characterized in that one or more values ​​related to the determination of the time interval to which the above future point in time belongs are predefined or set by the base station.

13. 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 12, based on execution by the one or more processors.

14. 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 12, based on execution by the above one or more processors.

15. 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 12.

16. Regarding the method, A step of transmitting configuration information to a terminal by a base station; The step of transmitting a reference signal to the terminal by the base station, and predicting a future point in time related to a beam failure by the terminal based on the reference signal; and The method includes the step of receiving information based on the future time point from the terminal by the base station, A method characterized by including information related to a new beam update performed by the terminal, based on the fact that the future time point is within a first time interval.

17. 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, having the base station perform all steps of the method according to claim 16.