Apparatus and method for communication

Abstract

Embodiments of the present disclosure provide a beam management solution. In one solution, a terminal device determines at least one set of reference signals (RSs) corresponding to at least one future duration, one of the at least one set of RSs comprising one or more RSs for measurement, where the at least one set of RSs is associated with at least one of beam failure detection (BFD), candidate beam measurements, or candidate beam measurements. Or Radio Link Monitoring (RLM). The terminal device then performs RS measurements on the at least one set of RSs in at least one respective future duration.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein relate generally to the field of communication technology, and more specifically to devices and methods for beam management. Background Technology

[0002] As communication networks and services grow in scale, complexity, and user numbers, operations within these networks can become increasingly complex. To improve communication performance, the use of machine learning (ML) / artificial intelligence (AI) techniques in wireless communication networks has been proposed. For example, terminal devices and network devices can use different ML models to assist in communication-related functionalities such as beam management (BM).

[0003] As an example scenario, the ML / AL model can be deployed at either a terminal device or a network device, and information about the predicted beams corresponding to multiple future time instances can be output as the result of the ML / AL model. Furthermore, information about the predicted beams can be transmitted between the terminal device and the network device. In current wireless communication systems, the terminal device performs beam failure detection (BFD) by measuring the reference signal (RS) from the network device. Additionally, when the terminal device detects a beam failure, it can announce the failure to the network device and trigger beam failure recovery (BFR). However, to date, neither the BFD nor BFR procedures have adequately considered this predicted beam information, leading to unnecessary signaling overhead and communication interruptions. Summary of the Invention

[0004] In a first aspect, a terminal device is provided, the terminal device comprising: a processor configured to cause the terminal device to: determine at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RSs including one or more RSs for measurement, the at least one set of RSs being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and perform RS measurement on the at least one set of RSs during at least one corresponding future duration.

[0005] In a second aspect, a network device is provided, the network device comprising: a processor configured to cause the network device to: generate configuration information indicating at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RS including one or more RS for measurement, the at least one set of RS being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and transmit the configuration information to a terminal device.

[0006] In a third aspect, a terminal device is provided, the terminal device comprising: a processor configured to cause the terminal device to: determine at least one first beam set to be used for communication between the terminal device and a network device over at least a first future duration; and send to the network device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set; or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0007] In a fourth aspect, a network device is provided, the network device comprising: a processor configured such that the network device: receives from a terminal device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0008] In a fifth aspect, a communication method performed by a terminal device is provided. The method includes: determining at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RSs including one or more RSs for measurement, the at least one set of RSs being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and performing RS measurements on the at least one set of RSs during at least one corresponding future duration.

[0009] In a sixth aspect, a communication method performed by a network device is provided. The method includes: generating configuration information indicating at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RSs including one or more RSs for measurement, the at least one set of RSs being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and transmitting the configuration information to a terminal device.

[0010] In a seventh aspect, a communication method performed by a terminal device is provided. The method includes: determining at least one first beam set to be used for communication between the terminal device and a network device over at least a first future duration; and sending to the network device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set; or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0011] In an eighth aspect, a communication method performed by a network device is provided. The method includes: receiving from a terminal device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0012] In a ninth aspect, a computer-readable medium is provided that stores instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the fifth, sixth, seventh, or eighth aspect.

[0013] Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0014] The above and other objects, features, and advantages of this disclosure will become more apparent from a more detailed description of some exemplary embodiments thereof in the accompanying drawings, wherein: Figure 1 An example communication environment in which an example implementation of the present disclosure can be carried out is illustrated; Figure 2A The signaling flow of the BFR procedure is illustrated; Figure 2BA block diagram of BFD is shown; Figure 2C A graph illustrating beam quality is shown. Figure 3 An example of timing based on AI / ML temporal beam prediction is shown; Figure 4 Signaling flows of communications according to some embodiments of this disclosure are illustrated; Figures 5A to 5D Examples of configuration information according to some embodiments of this disclosure are shown; Figures 6A to 6D Examples of configuration information according to some embodiments of this disclosure are shown; Figure 7 The timing of time beam prediction is illustrated; Figure 8 The timing of time beam prediction is illustrated; Figure 9 Examples of configuration information according to some embodiments of this disclosure are shown; Figure 10 The timing of time beam prediction is illustrated; Figure 11 Examples of configuration information according to some embodiments of this disclosure are shown; Figures 12A to 12C Signaling flows of communications according to some embodiments of this disclosure are illustrated; Figure 13 Examples of configuration information according to some embodiments of this disclosure are shown; Figures 14A to 14C Examples of configuration information according to some embodiments of this disclosure are shown; Figure 15 The timing of time beam prediction is illustrated; Figure 16 The timing of time beam prediction is illustrated; Figure 17 The timing of time beam prediction is illustrated; Figure 18 The timing of time beam prediction is illustrated; Figure 19 Flowcharts illustrating methods implemented at a terminal device according to some example embodiments of this disclosure are shown; Figure 20 Flowcharts illustrating methods implemented at a network device according to some example embodiments of this disclosure are shown; Figure 21 Flowcharts illustrating methods implemented at a terminal device according to some example embodiments of this disclosure are shown; Figure 22Flowcharts illustrating methods implemented at a network device according to some example embodiments of this disclosure are shown; and Figure 23 A simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure is shown.

[0015] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0016] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art to understand and implement this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0017] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0018] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE); personal computers; desktop computers; mobile phones; cellular phones; smartphones; personal digital assistants (PDAs); portable computers; tablets; wearable devices; Internet of Things (IoT) devices; Ultra-reliable and Low-Latency Communication (URLLC) devices; Internet of Everything (IoE) devices; machine-type communication (MTC) devices; devices on vehicles for V2X communication, where X refers to pedestrians, vehicles, or infrastructure / networks; devices for Integrated Access and Backhaul (IAB); spacecraft or aerospace vehicles in non-terrestrial networks (NTNs), including satellites and high-altitude platforms (HAPs) covering Unmanned Aircraft Systems (UAS); and different types of reality (such as Augmented Reality (AR), Mixed Reality (MR)). Extended Reality (XR) devices, including those for Virtual Reality (VR) and Virtual Reality (VR); unmanned aerial vehicles (UAVs), often referred to as drones (aircraft without human pilots); devices on high-speed trains (HSTs); or image capture devices such as digital cameras and sensors; gaming devices; music storage and playback equipment; or internet devices enabling wireless or wired internet access and browsing. "Terminal devices" may also have "multicast / broadcast" capabilities to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, wireless software delivery, group communication, and IoT applications. "Terminal devices" may also incorporate one or more Subscriber Identity Modules (SIMs), a situation known as multi-SIM. The term "terminal device" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0019] The term "network device" refers to a device that provides or hosts a cell or coverage area for terminal devices to communicate. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), next-generation NodeBs (gNBs), transmission reception points (TRPs), remote radio units (RRUs), radioheads (RHs), remote radio heads (RRHs), IAB nodes, low-power nodes (such as femtonodes and piconodes), reconfigurable intelligent surfaces (RISs), etc.

[0020] Terminal devices or network devices may have artificial intelligence (AI) or machine learning capabilities. Terminal devices or network devices typically include models that have been trained on specific functions based on a large amount of collected data and can be used to predict some information.

[0021] Terminal or network devices can operate within several frequency ranges, such as FR1 (e.g., 450MHz to 6000MHz), FR2 (e.g., 24.25GHz to 52.6GHz), bands greater than 100GHz, and terahertz (THz). Terminal or network devices can also operate on licensed / unlicensed / shared spectrum. In Multi-Radio Dual Connectivity (MR-DC) applications, terminal devices may connect to more than one network device. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-division duplex modes.

[0022] The embodiments of this disclosure can be executed in test equipment (e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal equipment, test network equipment, channel simulator). In some embodiments, the terminal equipment can be connected to a first network equipment and a second network equipment. One of the first network equipment and the second network equipment can be a master node, and the other can be a slave node. The first network equipment and the second network equipment can use different Radio Access Technologies (RATs). In some embodiments, the first network equipment can be a first RAT device, and the second network equipment can be a second RAT device. In some embodiments, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs can be sent to the terminal equipment from at least one of the first network equipment or the second network equipment. In some embodiments, first information can be sent from the first network equipment to the terminal equipment, and second information can be sent from the second network equipment directly or via the first network equipment to the terminal equipment. In some embodiments, information configured by the second network equipment and related to the configuration of the terminal equipment can be sent from the second network equipment via the first network equipment. Information configured by the second network device and related to the reconfiguration of the terminal device can be sent directly from the second network device or via the first network device to the terminal device.

[0023] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one implementation” and “implementation” should be understood as “at least one implementation.” The term “another implementation” should be understood as “at least one other implementation.” The terms “first,” “second,” etc., may refer to different or the same objects. Other explicit and implicit definitions are given below.

[0024] In some examples, values, programs, or devices are described as “best,” “lowest,” “highest,” “smallest,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many alternative functionalities used, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0025] As used herein, the terms “resource,” “transmission resource,” “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as a resource in the time domain, a resource in the frequency domain, a resource in the spatial domain, a resource in the code domain, or any other resource used to implement communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources to describe some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0026] Traditional beam management incorporates BFD and BFR processes to address congestion issues. As described above, to improve communication performance, the use of ML / AI technologies in wireless communication networks has been proposed. For example, terminal devices and network devices can use different ML models to assist in communication-related functionalities, such as beam management (BM).

[0027] For AI / ML-based beam management, the industry has reached a consensus to support the following BM scenario 1 and BM scenario 2: BM Scenario 1: Based on the measurement results of beam set B, perform spatial domain downlink beam prediction on beam set A.

[0028] BM Scenario 2: Based on the historical measurement results of beam set B, perform time downlink L beam prediction for beam set A.

[0029] Furthermore, for BM scenario 1 and BM scenario 2, the beams in the aforementioned sets A and B can be in the same frequency range (FR).

[0030] In BM scenario 2, the following alternative beam prediction schemes are supported: downlink transmit (TX) beam prediction, downlink receive (RX) beam prediction, and beam pair prediction (a beam pair consists of a downlink TX beam and a corresponding downlink RX beam).

[0031] For the sub-use cases of BM Scenario 1 and BM Scenario 2, the following alternative schemes for AI / ML output can be supported: TX and / or RX beam identifiers IDs and / or predicted Layer 1 (L1) reference signal received power (RSRP) for N predicted downlink TX and / or RX beams, for example, the N predicted beams can be the first N predicted beams; TX and / or RX beam IDs and other information (e.g., probability that the beam is the best beam, associated confidence, beam application time / dwell time, predicted beam failure) for N predicted downlink TX and / or RX beams, where the N predicted beams can be the first N predicted beams; TX and / or RX beam angles and / or predicted L1-RSRP for N predicted DL TX and / or RX beams, where the N predicted beams can be the first N predicted beams.

[0032] Generally speaking, time-domain prediction can provide useful information to improve BFR and BFD correlation processes. However, to date, neither the BFD nor BFR processes have fully considered this predicted beam information, leading to unnecessary signaling overhead and communication interruptions.

[0033] According to an example embodiment of this disclosure, a solution for beam management is proposed. In this solution, a terminal device determines at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RSs including one or more RSs for measurement, wherein the at least one set of RSs is associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM). The terminal device then performs RS measurements on the at least one set of RSs during at least one corresponding future duration.

[0034] By identifying at least one set of RS corresponding to at least one future duration, unnecessary beam failure reports can be reduced, and the BFD-related process / BFR-related process / RLM-related process can be improved accordingly.

[0035] For ease of description, the following is a list of some terms used in this article: AI / ML model: refers to a data-driven algorithm that uses AI / ML technology to generate a set of outputs based on a set of inputs; AI / ML Model Delivery: This is a general term referring to the delivery of AI / ML models from one entity to another in any way. Note: Entity can refer to network nodes / functions (e.g., gNB, LMF, etc.), UE, proprietary servers, etc. AI / ML model inference: refers to the process of using a trained AI / ML model to produce a set of outputs based on a set of inputs; AI / ML model testing refers to a sub-process of training that uses a different dataset than that used for model training and validation to evaluate the performance of the final AI / ML model. Unlike AI / ML model validation, testing does not assume subsequent model tuning. AI / ML model training refers to the process of training an AI / ML model in a data-driven manner [by learning the input / output relationship] and obtaining a trained AI / ML model for inference. AI / ML model transmission: This refers to the delivery of AI / ML models via the air interface in a manner opaque to 3GPP signaling. The delivered content can be model parameters with a known structure at the receiving end, or a new model containing parameters. The delivery can include a complete model or a partial model. AI / ML model validation refers to a sub-process of training used to evaluate the quality of AI / ML models using a dataset different from the dataset used for model training, in order to help select model parameters that can demonstrate good generalization ability outside the model training dataset. Data collection refers to the process by which network nodes, management entities, or UEs collect data for the purposes of AI / ML model training, data analysis, and inference. Federated learning / federated training is a machine learning technique that trains AI / ML models on multiple decentralized edge nodes (e.g., UE, gNB), with each node performing local model training using local data samples. This technique requires multiple interactions between models but does not exchange local data samples. Function identification: refers to the process / method of identifying AI / ML functions for mutual understanding between the network and the UE. Note: AI / ML function-related information can be shared during the function identification process. The location where AI / ML functions reside depends on specific use cases and sub-use cases; Model activation: refers to enabling AI / ML models for specific AI / ML-enabled features; Model deactivation: refers to disabling AI / ML models for specific AI / ML-enabled features; Model download: refers to transferring the model from the network to the user interface (UE); Model identification: refers to the process / method of identifying AI / ML models for mutual understanding between the network and the UE. Note: The process / method of model identification may or may not be applicable; Information about AI / ML models can be shared during model identification; Model monitoring: refers to the process of monitoring the inference performance of AI / ML models; Model parameter update: refers to the process of updating the model parameters; Model selection: This refers to the process of choosing one AI / ML model from multiple models to activate the same AI / ML-enabled feature. Note: Model selection can be performed simultaneously with model activation, or they can be performed at different times. Model switching: refers to deactivating the currently active AI / ML model and activating a different AI / ML model for a specific AI / ML-enabled feature; Model update: refers to the process of updating the model parameters and / or model structure; Model upload: refers to the transmission of the model from the UE to the network; Network-side (AI / ML) models: These refer to AI / ML models where inference is performed entirely on the network. Offline field data: refers to data collected from the field and used for offline training of AI / ML models; Offline training: refers to the AI / ML training process in which a model is trained based on a collected dataset, and the trained model is later used or delivered for inference. Note: This definition is for guidance only. There may be some cases that, while not perfectly conforming to this definition, can still be classified as offline training according to generally accepted conventions. Online field data: refers to data collected from the field and used for online training of AI / ML models; Online training: refers to an AI / ML training process in which the model used for inference is trained (usually continuously) in (near) real-time as new training samples arrive. Note: The concepts of (near) real-time and non-real-time depend on the context and are relative to the inference timescale. Note: This definition is for guidance only. There may be cases that, while not perfectly fitting this definition, can still be classified as online training according to generally accepted conventions. Note: Fine-tuning / retraining can be performed through online or offline training. (This note may be removed after defining the term "fine-tuning"). Reinforcement learning (RL) refers to the process of training an AI / ML model in an environment in which the model interacts, based on feedback signals (also known as rewards) generated by the model's input (also known as state) and the model's output (also known as action). Semi-supervised learning: The process of training a model using a mixture of labeled and unlabeled data; Supervised learning refers to the process of training a model based on the input and its corresponding labels. Two-sided (AI / ML) model: refers to a paired AI / ML model on which joint inference is performed, where joint inference includes AI / ML inference, which is jointly performed across the UE and the network. That is, the first part of the inference is first performed by the UE, and then the remaining part is performed by the gNB, and vice versa. UE-side (AI / ML) model: refers to an AI / ML model where inference is performed entirely on the UE; Unsupervised learning refers to the process of training a model without using labeled data. From a 3GPP perspective, proprietary format models are vendor / device-specific proprietary ML models. These models are not mutually recognizable between different vendors and hide model design information from other vendors when shared. Note: An example is a device-specific binary executable format; Open format models: From a 3GPP perspective, these are ML models with a specified format that can be mutually recognized and interoperable across different vendors. Such models are mutually recognizable across different vendors and do not hide model design information from other vendors when shared.

[0036] In this disclosure, The terms “ML model”, “AI model”, “ML function”, “AI function” and “algorithm” are used interchangeably.

[0037] The terms “model”, “function”, and “model / function” are used interchangeably.

[0038] The terms “ID”, “index”, “indicator”, and “identifier” are used interchangeably.

[0039] The terms "duration" and "time instance" are used interchangeably.

[0040] The terms “future,” “prediction,” and “forecast” are used interchangeably.

[0041] The terms “BFD”, “BFR”, “Link Failure Recovery (LFR)”, “Radio Link Monitoring (RLM)”, and “Candidate Beam Measurement” are used interchangeably.

[0042] The principles and specific implementations of this disclosure will now be described in detail with reference to the accompanying drawings.

[0043] In this disclosure, a beam may correspond to a channel state information-reference signal (CSI-RS), a synchronization signal and physical broadcast channel (PBCH) block (SSB), a CSI-RS resource, or an SSB resource. Therefore, the beam identifier (ID) may be a CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI), or an RS ID. It should also be understood that, in fact, a beam refers to a resource that enables space-oriented communication, and therefore may be identified by other suitable parameters in other embodiments. This disclosure is not limited in this respect.

[0044] It should be noted that when using the term "a set of...", it can refer to one or more elements / items, and the term can be replaced by the terms "at least one", "a group", or "a list of...". For example, "a set of X" means "at least one X" or "one or more X".

[0045] In the following description, the BFR / BFD procedure will be used as an example of a BM procedure to illustrate some specific example implementations of this disclosure. It should be noted that the example implementations described with respect to the BFR / BFD procedure are equally applicable to other types of BMs, such as candidate beam measurement procedures, RLM procedures, etc.

[0046] The principles and specific implementations of this disclosure will now be described in detail with reference to the accompanying drawings.

[0047] Example Environment Figure 1 A schematic diagram of an example communication environment 100 in which an example embodiment of the present disclosure may be implemented is illustrated. In the communication environment 100, multiple communication devices (including terminal device 110 and network device 120) can communicate with each other.

[0048] Furthermore, the communication environment 100 supports multiple-input multiple-output (MIMO), enabling network device 120 and terminal device 110 to communicate with each other via different beams to achieve directional communication.

[0049] exist Figure 1 In some embodiments, terminal device 110 may include a terminal device, and network device 120 may include a network device serving the terminal device. In this particular example embodiment, the link from terminal device 110 to network device 120 is referred to as an uplink, and the link from network device 120 to terminal device 110 is referred to as a downlink.

[0050] In the downlink, network device 120 is a transmitting (TX) device (or transmitter) and terminal device 110 is a receiving (RX) device (or receiver), and network device 120 can transmit downlink data to terminal device 110 via one or more beams. Figure 1 As shown, network device 120 transmits downlink data to terminal device 110 via one or more of beams 140-1, 140-2, and 140-3. For discussion purposes, beams 140-1 to 140-3 are collectively or individually referred to as beam 140.

[0051] Correspondingly, in the uplink, network device 120 is an RX device (or receiver) and terminal device 110 is a TX device (or transmitter), and terminal device 110 can transmit uplink data to network device 120 via one or more beams. Figure 1 As shown, terminal device 110 transmits uplink data to network device 120 via beams 130-1 to 130-3. For discussion purposes, beams 130-1 to 130-3 are collectively or individually referred to as beam 130.

[0052] In some implementations, one or more models may be deployed at terminal device 110 and / or network device 120. For example... Figure 1As shown, model 115 can be deployed at terminal device 110. Alternatively or otherwise, model 125 can be deployed at terminal device 110. When both model 115 and model 125 are deployed, model 115 and model 125 can operate collaboratively with each other.

[0053] In addition, hybrid model monitoring is supported in the communication environment 100. Specifically, the terminal device 110 monitors performance metrics, while the network device 120 makes decisions on model-related operations, such as selection, activation, deactivation, switching, and rollback.

[0054] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the example embodiments of this disclosure.

[0055] In some implementations, terminal device 110 and network device 120 communicate via a channel, such as a wireless communication channel over an air interface (e.g., a Uu interface). The wireless communication channel may include a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical random-access channel (PRACH), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a physical broadcast channel (PBCH). Of course, any other suitable channel is also possible.

[0056] The communications in communication environment 100 may conform to any suitable standard, including but not limited to Global System for Mobile Communication (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. The embodiments of this disclosure may be implemented according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, 5G-Advanced Networks, or sixth-generation (6G) networks.

[0057] As described above, a Beam Failure Detection (BFR) procedure is introduced to address congestion issues. The BFR procedure primarily includes Beam Failure Detection (BFD), New Beam Identification, Beam Failure Recovery Request (BFRQ), and BFRQ response. During the BFR procedure, the UE monitors the quality of the serving beam, and if the quality degrades to a certain condition, the UE can notify the network of the beam failure and / or information about a new beam available for subsequent transmission. The network device can then respond to the UE, indicating that it has received this information.

[0058] Now for reference Figure 2A and Figure 2B ,in Figure 2A The signaling flow 200A of the BFR procedure is illustrated, and Figure 2B The BFD system block 200B is shown as an example.

[0059] In some implementations, radio resource control (RRC) is used to configure relevant information, where RadioLinkMonitoringConfig The information element (IE) includes configurations on how beam failure is detected (such as BFD RS and beam failure thresholds, timers, counter information, etc.). BeamFailureRecoveryConfig The IE includes configurations for candidate beams and BFRQ (such as candidate beam detection (CBD) RS and candidate beam thresholds, the association between CBD RS and PRACH, or PUCCH SR for BFRQ, and a dedicated search space / CORESET for monitoring network response).

[0060] In some implementations, upon receiving RRC configuration for BFR, the UE may perform beam failure detection (BFD) based on periodic 1-port CSI-RS for BM (such as resources in set q0, which may be explicitly configured or implicitly derived from PDCCH quasico-location (QCL) information). In some implementations, the radio link quality threshold Q... out, LR (The assumed PDCCH block error rate (BLER) is used for beam failure declaration.)

[0061] In some implementations, candidate beam detection (CBD) may be based on the synchronization signal and PBCH block (SSB) and CSI-RS used for the beam BM, and the set of CBDs may be represented as set q1. In some implementations, the resources in set q1 may be cross-carrier.

[0062] In some implementations, the radio link quality threshold Q in, LR (It is L1-RSRP) can be used to detect new beams / target beams, where the identified new beam / target beam can be represented as q new .

[0063] In some implementations, in the case of special cell (spCell) BFR, the beam failure recovery request (BFRQ) can be carried by a contention-free random access channel (RACH), and the BFRQ response can be configured with... recoverySearchSpaceId The PDCCH is carried in the associated dedicated control resource set (CORESET) / search space.

[0064] In some implementations, in the case of secondary cell (SCell) BFR, the UE can transmit a BFR MAC CE to the gNB, which can convey the following information: the failed component carrier (CC) index, whether a new beam has been identified, and the RS resource ID indicating the index of the identified new beam.

[0065] In some implementations, the UE transmits a scheduling request (SR) via the PUCCH used for BFR (which can be specifically configured) to indicate beam failure and request resources for reporting to the BFR media access control (MAC) control element (CE), where the SR can be specifically configured. Alternatively, if the SR is not configured, a contention-based PRACH can be used. Therefore, the gNB's response can be the same as in a normal SR procedure.

[0066] In some implementations, upon receiving a BFR MAC CE, the gNB may transmit a PDCCH to schedule a new transmission for the same hybrid automatic repeat request (HARQ) procedure used to send the BFR MAC CE. Then, after a specific duration (e.g., 28 symbols) since the UE received the response, the UE may apply the newly identified beam to all CORESET and PUCCH resources.

[0067] In some implementations, for multiple transmit and receive points (TRPs), the BFR process can be performed per TRP to achieve BFD, CBD, and BFR for each TRP.

[0068] In some implementations, the UE MAC layer may be responsible for receiving indications from the UE physical (PHY) layer, maintaining counters and timers to determine whether to declare beam failure, triggering relevant PHY layer procedures, etc.

[0069] In some implementations, the UE PHY layer can be responsible for measuring all configured BFD RS and CBD RS, transmitting beam failure instance indications to the UE MAC layer, sending BFRQs, monitoring network responses, etc.

[0070] Figure 2C A graph illustrating beam quality is shown. Figure 2C In this context, beam #1 is the serving beam, beam #2 is the indicated beam based on predictions for future time instances, and switching point 280 is the indicated time point for applying beam #2.

[0071] like Figure 2C As shown, when the serving beam (such as...) Figure 2C When beam #1 in the network becomes worse, the traditional method is used to announce beam failure detection on the UE side. This triggers BFR-related procedures (which may include, for example, candidate RS measurement, new beam identification, BFRQ transmission, and BFRQ response reception) to inform the network device that beam failure has occurred and request a switch to a new beam. This BFR procedure may take a relatively long time.

[0072] However, if the beam to be used in the near future is known through time prediction, and if the time required for the BFR process is longer than the remaining time for the next beam switching ( Figure 2C If the duration Tr 260 in the time frame is less than or equal to the time frame, then the traditional BFR procedure is not required. Therefore, it would be beneficial if beam failure detection could be performed while taking into account time beam prediction.

[0073] Furthermore, it's a common scenario where the network doesn't strictly adhere to the beams reported by the UE for beam indication. That is, the UE may report some future beam predictions, but the network may not always assign the reported predicted beams in these future time instances. In other words, the network scheduling algorithm may assign a different beam than the reported beam, or a reported beam with the best reported beam quality. Therefore, the beam scheduled by the network for the UE may fail.

[0074] Therefore, if the AI / ML model on the UE side can predict beam failure, it is useful to provide this information to the network so that the network can avoid assigning a beam that is about to fail to the terminal device.

[0075] Now for reference Figure 3 This example illustrates timing 300 based on AI / ML temporal beam prediction.

[0076] In some implementations, AI / ML models can be used to predict beam and beam quality for future time instances, including predicting beam failure information. By applying AI / ML-based temporal beam prediction, RS overhead and / or RS measurement overhead can be reduced; for example, the RS period in set B can be longer than the RS period for non-AI beam management applications. Furthermore, applying AI / ML-based temporal beam prediction can also reduce beam indication signaling overhead; for example, a beam indication can provide information needed for several future transmissions.

[0077] Example process It should be understood that the operations at terminal device 110 and network device 120 should be coordinated. In other words, network device 120 and terminal device 110 should have a common understanding regarding configuration, parameters, etc. This common understanding can be achieved through any suitable interaction between network device 120 and terminal device 110, or by both network device 120 and terminal device 110 applying the same rules / policies. Although some operations are described below from the perspective of terminal device 110, it should be understood that the corresponding operations should be performed by network device 120. Similarly, although some operations are described from the perspective of network device 120, it should be understood that the corresponding operations should be performed by terminal device 110. For the sake of brevity, some identical or similar content is omitted here.

[0078] Furthermore, in the following description, some interactions (such as configuration exchange) are performed between terminal device 110 and network device 120. It should be understood that these interactions may be implemented in a single signaling / message / configuration or multiple signaling / message / configurations (including system information, RRC messages, downlink control information (DCI) messages, uplink control information (UCI) messages, MAC CE, etc.). This disclosure is not limited thereto.

[0079] refer to Figure 4 This illustrates a signaling stream 400 for transmitting information about the number of predicted beams according to some embodiments of this disclosure. For discussion purposes, reference will be made to... Figure 1 The signaling flow 400 is discussed, for example, by using terminal device 110 and network device 120.

[0080] exist Figure 4 In this context, it is assumed that the future beam can be obtained through prediction on the network device 120 side or on the terminal device 110 side.

[0081] In some implementations, time beam prediction can be used to improve the process for configuring the RS to be measured.

[0082] In operation, terminal device 110 may determine 420 at least one set of RSs corresponding to at least one future duration (wherein each set of RSs includes one or more RSs for measurement). In some embodiments, the at least one set of RSs may be associated with at least one of: BFD, candidate beam measurement, or RLM. For example, the at least one set of RSs includes: a first set of RSs denoted as RS#1, a second set of RSs denoted as RS#2, and a third set of RSs denoted as RS#3; and the at least one future duration includes: a first future duration denoted as duration #1, a second future duration denoted as duration #2, and a third future duration denoted as duration #3.

[0083] In some implementations, the RS included in the at least one RS set may be an RS with the same RS ID as the RS included in set B of BM scenario 2, or an RS associated with one or more sets B RS of BM scenario 2.

[0084] Next, the terminal device 110 may perform 430 RS measurements on the at least one set of RSs in at least one corresponding future duration. For example, the terminal device may measure RS#1 in duration #1, RS#2 in duration #2, and RS#3 in duration #3.

[0085] That is, at least one set of (BFD / candidate beam measurement / RLM) RSs can be determined for different future durations, wherein each set of RSs includes one or more RSs. In other words, the set of (BFD / candidate beam measurement / RLM) RSs determined for a first time instance may include a set of (BFD / candidate beam measurement / RLM) RSs associated with a second time instance, wherein the second time instance may be a future time instance.

[0086] It should be noted that when the number of RSs to be measured during each duration is one, the terminal device 110 may determine a set of RSs including different RSs for different future durations. For example, the terminal device 110 may determine a set of RSs including a first RS and a second RS, wherein the first RS is measured during a first future duration and the second RS is measured during a second future duration.

[0087] The following discusses how to determine this at least one set of RS. For example... Figure 4 As shown, in some embodiments, terminal device 110 may receive 410 configuration information from network device 120, wherein the configuration information may indicate the at least one RS set and at least one future duration corresponding to the at least one RS set.

[0088] Furthermore, the at least one RS set may be indicated by any suitable parameter, including but not limited to the identifier of the RS, the identifier of the beam associated with the RS, the transmission configuration indicator (TCI) associated with the RS, or the quasi-co-address (QCL) information associated with the RS.

[0089] Furthermore, this at least one future duration can be indicated by any suitable parameter, including but not limited to: At least one starting time point corresponding to the at least one future duration, At least one end time point corresponding to the at least one future duration, At least one time length corresponding to the at least one future duration The starting time point corresponding to the first future duration in at least one future duration, or The common time length corresponding to each of the at least one future duration.

[0090] In some implementations, the configuration information may also indicate at least one of the following: prediction quality information about the at least one RS set, or prediction failure information about the at least one RS set.

[0091] In some implementations, if no BFDRS set is specified, a default BFDRS assumption may be used for future durations.

[0092] It should be noted that the at least one RS set can be configured explicitly or implicitly. In other words, network device 120 can send configuration information explicitly indicating the at least one RS set to terminal device 110, or terminal device 110 can determine the at least one RS set based on another configuration not specifically used to configure the RS set. Example procedures are discussed below.

[0093] In some embodiments, the at least one RS set can be configured via explicit configuration of a BFD RS set. In this case, the terminal device 110 may be configured with a BFD RS set configuration that includes both duration information (indicating the at least one future duration) and RS information (indicating the at least one RS set). In some embodiments, this explicit configuration can be transmitted via any of RRC, MAC CE, or DCI.

[0094] In some implementations, a list of BFD RS sets of RS resource configuration indexes can be provided to the UE. ， This list corresponds to a list of future time instances of radio link quality measurements on the BWP of the serving cell.

[0095] In some implementations, the RS information may be an RS ID. Alternatively, the RS information may also be beam information in the form of TCI status ID, beam ID, QCL information, etc. This disclosure is not limited thereto.

[0096] In some implementations, the duration information can be counted in units such as symbols, time slots, subframes, frames, or in milliseconds, seconds, etc. Alternatively, the duration information can also be counted in terms of the number of PDCCH monitoring opportunities, PDSCH transmission opportunities, etc.

[0097] In some implementations, the duration information may be at least one start time point (also referred to as the first switching time point) corresponding to the at least one future duration. Now refer to... Figure 5A This example illustrates configuration information 500A. In Figure 5A In this process, terminal device 110 is configured to start / switch at time point #1 to measure a first RS set RS#1, start / switch at time point #2 to measure a second RS set RS#2, and so on.

[0098] Alternatively, in some embodiments, the duration information may be at least one end time point (also referred to as a second switching time point) corresponding to the at least one future duration. This may mean monitoring a first RS set RS#1 before time point #1, monitoring a second RS set RS#2 between time point #1 and time point #2, and so on. Additionally, in some embodiments, it is necessary to signal or define the start time point for monitoring the first RS set RS#1.

[0099] Alternatively, in some embodiments, the duration information may be at least one time length (also referred to as at least one duration, or at least one beam dwell time) corresponding to the at least one future duration. Now refer to Figure 5B This example illustrates configuration information 500B. In Figure 5B In this configuration, terminal device 110 is configured to monitor a first RS set RS#1 during duration #1, a second RS set RS#2 during duration #2, and so on. In some implementations, this may mean that durations #1 and #2 are adjacent. Additionally, in some implementations, it is necessary to signal or define the start / end time points for monitoring the first RS set RS#1.

[0100] Alternatively, in some implementations, the duration information may be at least one start time point and at least one end time point. In this way, the indicated future beam can be used in a discontinuous manner.

[0101] Alternatively, in some embodiments, the duration information may be at least one start time point and at least one time length corresponding to at least one future duration. Now refer to Figure 5C The example provided illustrates configuration information 500C.

[0102] In addition to explicitly indicating each future BFD RS set, it is also possible to signal or define duration information for all RS sets, such as the same time interval T and start time point t0. Now refer to Figure 5D The example provided illustrates configuration information 500D.

[0103] In some implementations, the at least one RS set may be implicitly determined. In some implementations, the UE may determine that the BFD RS set during a first duration includes an RS resource configuration index associated with an RS index in the RS set indicated by a TCI state, which is used by the UE to monitor the corresponding CORESET of the PDCCH during a second duration.

[0104] In some implementations, if no TCI state set is specified, a default TCI state can be used for future durations. For example, a TCI state associated with the earliest or latest time information can be used as the default TCI.

[0105] Unlike explicit configuration, in some implementations, the BFD RS set can be determined based on the RS set used for PDCCH monitoring and time information.

[0106] In some implementations, the RS set used for PDCCH monitoring can be obtained based on the TCI status indication used for CORESET.

[0107] In some implementations, the TCI status indication for a CORESET for a future time instance may include a list of TCI status information and duration information.

[0108] In some implementations, TCI status information may be presented in the following forms: TCI status ID, RS ID, beam ID, etc.

[0109] In some implementations, TCI status information may be associated with predicted beam quality information (e.g., RSRP, SINR, etc.). Alternatively, in some implementations, TCI status information may also include predicted beam failure information.

[0110] In some implementations, the TCI status information can be a unified TCI status for PDCCH and other channels / signals (such as PDSCH), or a dedicated TCI status for PDCCH, etc.

[0111] In some implementations, the duration information can be counted in units such as symbols, time slots, subframes, frames, or in milliseconds, seconds, etc. Alternatively, the duration information can also be counted in terms of the number of PDCCH monitoring opportunities, PDSCH transmission opportunities, etc.

[0112] In some implementations, the duration information may be at least one start time point (also referred to as the first switching time point) corresponding to the at least one future duration. Now refer to... Figure 6A This example illustrates configuration information 600A. In Figure 6A In this process, terminal device 110 is configured to start / switch at time point #1 to measure a first TCI set TCI#1, start / switch at time point #2 to measure a second TCI set TCI#2, and so on.

[0113] Alternatively, in some embodiments, the duration information may be at least one end time point (also referred to as a second switching time point) corresponding to the at least one future duration. This may mean monitoring a first TCI set TCI#1 before time point #1, monitoring a second TCI set TCI#2 between time point #1 and time point #2, and so on. Additionally, in some embodiments, it is necessary to signal or define the start time point for monitoring the first TCI set TCI#1.

[0114] Alternatively, in some embodiments, the duration information may be at least one time length (also referred to as at least one duration, or at least one beam dwell time) corresponding to the at least one future duration. Now refer to Figure 6B This example illustrates configuration information 600B. In Figure 6B In this configuration, terminal device 110 is configured to monitor a first TCI set TCI#1 during duration #1, a second TCI set TCI#2 during duration #2, and so on. In some implementations, this may mean that durations #1 and #2 are adjacent. Additionally, in some implementations, it is necessary to signal or define the start / end time points for monitoring the first TCI set TCI#1.

[0115] Alternatively, in some implementations, the duration information may be at least one start time point and at least one end time point. In this way, the indicated future beam can be used in a discontinuous manner.

[0116] Alternatively, in some embodiments, the duration information may be at least one start time point and at least one time length corresponding to at least one future duration. Now refer to Figure 6C The example provided illustrates configuration information 600C.

[0117] In addition to explicitly indicating each future TCI state, it is also possible to signal or define duration information for the entire set of TCI states, such as the same time interval T and start time t0. Now refer to Figure 6D The example provided illustrates configuration information 600D.

[0118] In some implementations, if an RS / TCI state set is associated with prediction failure information, the terminal device 110 / network device 120 may exclude that RS / TCI state set from the at least one RS set (i.e., exclude it from the at least one RS set). Prediction beam failure information may be determined by AI / ML model inference performed in the network device 120 or the terminal device 110.

[0119] In some embodiments, the at least one RS set includes a first RS set corresponding to a first duration and a second RS set corresponding to a second duration following the first duration, wherein the second RS set is at least partially different from the first RS set. In this case, the terminal device 110 can measure both the first RS set and the second RS set during a third duration before the end of the first duration (and / or before the start of the second duration).

[0120] In some implementations, the third duration can be defined as a default value. As an example, the third duration is predefined by a communications organization (such as 3GPP) or by a network operator or service provider. In this way, no additional signaling interaction is required between the terminal device and the network device 210.

[0121] Alternatively, in some implementations, the third duration can be configured dynamically or semi-statically. For example, the third duration can be configured by network device 120 or reported by terminal device 110.

[0122] Now for reference Figure 7 This exemplifies timing 700 for time beam prediction. Figure 7 In the process, both the first BFD RS set RS#1 and the second BFD RS set RS#2 can be evaluated during a duration of 710 Ts (i.e., the third duration) prior to the switching time point, wherein the first BFD RS set is associated with the first time information and the second BFD RS set is associated with the second time information.

[0123] In some implementations, radio link quality assessment can be improved. For example, the period for BFD RS assessment and beam failure instance (BFI) indication to higher layers can be based on descriptions such as RS period and AI / ML models. Specifically, in some implementations, terminal device 110 can notify higher layers of beam failure based on a period determined by at least one of the following: The period of the RS included in at least one RS set, Predefined time length, The length of time associated with the model (i.e., the AI / ML model description, denoted as "X"), The scaling factor configured for Discontinuous Reception (DRX) mode, or DRX loop length.

[0124] In some implementations, AI / ML models can be used to predict beams, and the time duration can be correlated with the model's predictive power. Specifically, AI / ML models can be used for temporal beam prediction (or to predict beams for future time instances).

[0125] In some implementations, the first value of the time length associated with the DRX mode may be different from the second value of the time length associated with the non-DRX mode.

[0126] In some implementations, the period can be determined as the maximum of at least one of the following: {the minimum period of RS, a predefined time length, or a time length associated with the model}.

[0127] In some implementations, if the terminal device 110 is in DRX mode, the period can be determined as the maximum of at least one of the following: {the minimum value of the scaled period of RS, the scaled time length associated with the model, or the scaled DRX cycle length}.

[0128] In some implementations, during BFI indication management, the period for BFD RS evaluation and BFI indication to higher layers can be based on the RS period and an AI / ML model description (denoted as "X", i.e., the time length associated with the model). In some implementations, for better-performing AI / ML models, the evaluation period can be longer, e.g., every X ms, where X is given by the AI / ML model description. In some implementations, for the AI / ML model used to predict beams for future time instances, X can be based on the time interval between future time instances; for example, X is a function of the time interval.

[0129] In some implementations, the AI / ML model description X can be determined based on time information (e.g., duration, or time interval T of future durations). Furthermore, the AI / ML model description X can be configured independently.

[0130] In some implementations, the first value of the AI / ML model description X associated with the DRX mode may be different from the second value of the AI / ML model description X associated with the non-DRX mode.

[0131] According to traditional solutions, the period is max {shortest RS period, 2 milliseconds}. In some implementations of this disclosure, the AI / ML model description X is considered, so the period can be max {shortest RS period, 2 milliseconds, X milliseconds}. Furthermore, considering that X should generally be greater than 2 ms, the period can also be max {shortest RS period, X milliseconds}.

[0132] In some implementations, in DRX mode, the cycle can be based on the DRX cycle length, AI / ML model description X, RS cycle, and / or UE category.

[0133] In some implementations, in DRX mode, if the DRX loop length is ≤ a threshold in ms, the period can be max(scaling factor × DRX loop length, scaling factor × RS period, scaling factor × X). In some implementations, if the DRX loop length is > a threshold in ms, the period can be the DRX loop length. In some implementations, the scaling factor can be, for example, 1.5, and the threshold can be, for example, 320 ms.

[0134] In some implementations, during AI / ML mode operation, the radio link quality ratio has a threshold Q determined by the maximum value between the shortest period in the SS / PBCH block on the PCell or PSCell and / or the periodic CSI-RS configuration in the BFD RS set used by the UE to evaluate radio link quality and X milliseconds. out,LR In worse cases, the physical layer notifies the higher layers, where X is described based on an AI / ML model.

[0135] In the case of BFR, if the radio link quality of the beam is assessed as worse than a threshold, the physical layer of terminal device 110 can notify the higher layers of terminal device 110 of beam failure by using a BFI indication. If the beam failure counter (BFI_COUNTER) is equal to or greater than... beamFailureInstanceMaxCount If this occurs, the BFR-related process can be triggered by the terminal device 110. Therefore, to optimize the BFR process, the maintenance procedure for the beam failure counter can be improved.

[0136] In some implementations, the BFI counter reset process can be improved. For example... Figure 4As shown, terminal device 110 can reset the 440 beam failure counter according to some rules. As a general rule, if a future BFD RS is known and the switch will be made to that future BFD RS, the beam failure counter of the BFD RS / BFD-RS (which may be represented as BFI_COUNTER) can be set to "0".

[0137] In some implementations, terminal device 110 may reset the beam failure counter at a first time point based on determining that the target beam will be applied at a second time point, wherein the first time point is earlier than the second time point.

[0138] In some implementations, the value of the fourth duration can be "0". In this case, the terminal device 110 may not need to determine the fourth duration and can reset the beam failure counter at the first / second time point.

[0139] In some implementations, a fourth duration between the first and second time points can be defined as a default value. As an example, this fourth duration is predefined by a communications organization (such as 3GPP) or by a network operator or service provider. In this way, no additional signaling interaction is required between the terminal device and network device 210.

[0140] Alternatively, in some implementations, the fourth duration can be configured dynamically or semi-statically. For example, the fourth duration can be configured by network device 120 or reported by terminal device 110.

[0141] Alternatively, in some implementations, terminal device 110 may reset the beam failure counter at a third time point earlier than the fourth time point, based on the determination that a different RS or RS set will be measured at a fourth time point.

[0142] In some implementations, the value of the fifth duration can be "0". In this case, the terminal device 110 may not need to determine the fourth duration and can reset the beam failure counter at the third / fourth time point.

[0143] In some implementations, a fifth duration between the third and fourth time points can be defined as a default value. As an example, the fifth duration is predefined by a communications organization (such as 3GPP) or by a network operator or service provider. In this way, no additional signaling interaction is required between the terminal device and network device 210.

[0144] Alternatively, in some implementations, the fifth duration can be configured dynamically or semi-statically. For example, the fifth duration can be configured by network device 120 or reported by terminal device 110.

[0145] In some implementations, if the future BFD RS set is known and the switch will be performed to that future BFD RS set, the associated beam failure counter BFI_COUNTER for the BFD-RS can be set to 0. This means that if the predicted beam is known and a beam switch is to be performed, the BFI counter can be reset.

[0146] Now for reference Figure 8 This illustrates timing 800 for time beam prediction. In some implementations, the "to be switched" BFD RS set / beam (i.e., Figure 8 RS#2 in the data is monitored and is superior to the BFD threshold, and is also different from the current BFD RS set / beam (i.e., Figure 8 RS#1 in the middle.

[0147] like Figure 8 As shown, at time point 810, a beam / BFD RS handover will be performed in the next duration Tr (i.e., the fourth / fifth duration). In some implementations, the duration Tr may be less than a threshold, which may be predefined, network-configured, or reported by the UE. In some implementations, the duration Tr may be less than the time required for BFR.

[0148] In some implementations, the at least one RS set includes a first RS set corresponding to a first duration and a second RS set corresponding to a second duration following the first duration. In this case, the terminal device 110 may start the beam failure counter at the beginning of the first duration; and based on the determination that the first RS set and the second RS set at least partially overlap, the terminal device 110 may continue the beam failure counter during the second duration without resetting it.

[0149] In some implementations, if the same BFD RS / TCI status (or overlapping or partially overlapping RS / TCI status lists) is monitored / applied over different consecutive durations, it is not necessary to set the BFI counter to 0. For example, RS#1 and RS#2 point to the same RS or the same RS list, or they partially overlap, and the BFI counter may not be set to 0 when switching from RS#1 to RS#2.

[0150] In some implementations, the BFI counter can be reset at the start time point of monitoring different BFD RS (sets). In some implementations, the terminal device 110 can reset the beam failure counter when the measurement of an RS set is completed or when the measurement of a different RS set begins. Alternatively, in some implementations, the terminal device 110 can reset the beam failure counter when the measurement of at least one RS set is completed.

[0151] Alternatively, in some implementations, the BFI counter is not reset until a new BFD RS set configuration or beam indication is received (e.g., Figure 9 As shown, it illustrates an example of configuration information 900 according to some embodiments of this disclosure. Figure 9 When the UE switches from monitoring RS#1 to monitoring RS#2, the UE does not set the BFI counter to 0, and only sets the BFI counter to 0 when all predicted future beams (BFD RS) are applied / monitored.

[0152] In some implementations, the maximum value of the beam failure counter is associated with at least one of the following: the number of future durations in the at least one future duration, or the number of RSs included in the RS set.

[0153] In some implementations, when beam prediction is enabled, the maximum value of the beam failure counter is... beamFailureInstanceMaxCount It can be configured to a larger value, for example, , where N can be the number of sets of RS.

[0154] In some implementations, if the serving cell is configured with a BFD-RS set, and if the reference signal associated with the BFD-RS set of the serving cell used for beam failure detection has changed or will change in the next Tr time, then the BFD-RS set is... BFI_COUNTER Set to 0.

[0155] In some implementations, the BFD process can be temporarily suspended if time beam prediction is provided. Specifically, if terminal device 110 or network device 120 predicts that at least one beam will be used for at least one future duration, terminal device 110 can stop executing the BFD process.

[0156] In addition to the beam failure counter, BFD timer management can also be improved.

[0157] The BFD timer controls the duration of evaluation after the higher layer first receives the BFI indication but before declaring the BFD. When the BFD timer expires, the BFI_COUNTER of the BFD-RS set is set to 0.

[0158] In view of this, in some implementations, the BFD timer can be reset if a future BFD RS is known and the system will switch to that future BFD RS.

[0159] Now for reference Figure 10 This exemplifies timing 1000 for time beam prediction. In some implementations, the "to be switched" BFD RS set / beam (i.e., Figure 10RS#2 in the spectrum is monitored and is superior to the BFD threshold, and is also different from the current beam.

[0160] In some implementations, the BFD timer can be configured to have a value greater than the predicted total time length. For example, if... Figure 11 (As illustrated in the example of configuration information 1000), if time information is provided as shown, then the BFD timer >= This means that BFD assessments need to cover all predicted beams. For example, with beam prediction enabled, beamFailureDetectionTimer = Sum {Ti}, where i=1,...,N.

[0161] In some implementations, the BFD timer can be configured to have a value less than the duration of a prediction beam, for example, if... Figure 11 If time information is provided as in the example, then the BFD timer <= T, meaning that BFD evaluation is performed for each beam as indicated sequentially. For example, with beam prediction enabled, beamFailureDetectionTimer = max {Ti}, where i=1,...,N.

[0162] In some implementations, if the serving cell is configured with a BFD-RS set, and if a beam failure instance indication for the BFD-RS set has been received from a lower layer, then the BFD-RS set is started or restarted. beamFailureDetectionTimer In some implementations, if the serving cell is configured with a BFD-RS set, and if the reference signal associated with the BFD-RS set of the serving cell used for beam failure detection has changed or will change in the next Tr time, then the beamFailureDetectionTimer of that BFD-RS set is set to timeout / stop, and the BFD-RS set's... BFI_COUNTER Set to 0.

[0163] As mentioned above, the discussion on BFR also applies to candidate beam measurements and RLM.

[0164] In the case of candidate beam measurement, the UE can determine that the candidate beam RS set includes different RS as candidate beam RS for different durations.

[0165] In some implementations, the UE may be provided with a candidate beam RS set configuration that includes both duration information and RS information. How to indicate this duration information and RS information has been thoroughly discussed. For the sake of brevity, identical or similar details are omitted here.

[0166] In some implementations, the UE may be provided with a list of candidate beam RS sets for RS resource indexes used for radio link quality measurements on the BWP of the serving cell, which corresponds to a list of future time instances.

[0167] By utilizing the above process, unnecessary beam failure recovery processes can be minimized / avoided by leveraging future beam information, thereby reducing resources dedicated to BFR configuration and correspondingly shortening BFR latency.

[0168] refer to Figure 12A This illustrates a signaling stream 1200A for transmitting information about the number of predicted beams according to some embodiments of this disclosure. For discussion purposes, reference will be made to... Figure 1 The signaling flow 1200A is discussed, for example, by using terminal device 110 and network device 120.

[0169] In operation, terminal device 110 may determine at least one first beam set that will be used for communication between terminal device 110 and network device 120 for at least a first future duration. Then, terminal device 110 may send a first message 1220 to network device 120.

[0170] In some implementations, the second beam set includes at least one of the following: The beam with the highest failure probability, or At least one beam whose failure probability is higher than or equal to the threshold probability.

[0171] In some implementations, this threshold probability can be defined as a default value. As an example, this threshold probability is predefined by a communications organization (such as 3GPP) or by a network operator or service provider. In this way, no additional signaling interaction is required between the terminal device and the network device 210.

[0172] Alternatively, in some implementations, the threshold probability can be configured dynamically or semi-statically. For example, the threshold probability can be configured by network device 120 or reported by terminal device 110.

[0173] In some implementations, the first message may indicate predicted beam failure information for at least one second beam set corresponding to the at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set.

[0174] Alternatively, the first message may indicate at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure. The at least one recommended beam set may imply that the beam set has been predicted to be associated with beam failure.

[0175] In some implementations, terminal device 110 may determine the at least one first beam set based on the output of a model used to predict beams and deployed at terminal device 110.

[0176] In some implementations, the at least one first beam set may be indicated by network device 120. In this case, terminal device 110 may receive configuration information from network device 120, wherein the configuration information indicates the at least one first beam set and the at least one first future duration.

[0177] In some implementations, after sending the first message, the terminal device 110 may postpone the application timing or configuration information application timing for at least a second future duration.

[0178] In some implementations, upon receiving configuration information, the terminal device 110 may anticipate not receiving additional configuration information indicating at least one additional first beam set for at least one first future duration.

[0179] Alternatively or otherwise, upon receiving configuration information, terminal device 110 may ignore at least one additional first beam set included in the additional configuration information for at least one first future duration.

[0180] In some implementations, the first message may indicate the at least one second beam set and the at least one second future duration.

[0181] In some implementations, the at least one second future duration may be indicated by one of the following: At least one starting time point corresponding to at least one corresponding future duration, At least one end time point corresponding to at least one corresponding future duration, At least one time length corresponding to at least one corresponding future duration The starting time point corresponding to the first future duration in at least one corresponding future duration, or The common time length corresponding to each future duration in at least one corresponding future duration.

[0182] In some implementations, the beams in the at least one second beam set may be indicated by one of the following: Beam identification, The identifier of the RS associated with the beam. Transmission Configuration Indicator (TCI) associated with the beam, or Quasi-co-address (QCL) information associated with the beam.

[0183] In some implementations, the first message may indicate at least one recommended beam set and the at least one third future duration.

[0184] In some implementations, the at least one third future duration may be indicated by one of the following: At least one starting time point corresponding to at least one corresponding future duration, At least one end time point corresponding to at least one corresponding future duration, At least one time length corresponding to at least one corresponding future duration The starting time point corresponding to the first future duration in at least one corresponding future duration, or The common time length corresponding to each future duration in at least one corresponding future duration.

[0185] In some implementations, the beams in the at least one recommended beam set may be indicated by one of the following: Beam identification, The identifier of the RS associated with the beam. Transmission Configuration Indicator (TCI) associated with the beam, or Quasi-co-address (QCL) information associated with the beam.

[0186] In some implementations, the predicted beam failure information may indicate at least one first indication, each first indication indicating beam failure information corresponding to a beam set or a future duration.

[0187] Alternatively, in some implementations, the predicted beam failure information may indicate a plurality of second indications, each indicating beam failure information corresponding to a RS.

[0188] In some implementations, the predicted beam failure information includes at least one of the following: Indicates whether there is an indication of predicted beam failure. Predicted beam failure probability, or Predicted quality information.

[0189] In some implementations, after sending the first message, terminal device 110 may receive a second message from network device 120, the second message indicating at least one of the following: A beam indicator that indicates at least one beam that will be used over a future duration. Used to update at least one fourth beam set of the at least one second beam set. Confirmation information regarding the at least one recommended beam set, or Used to update at least one fifth beam set of at least one rejected recommended beam set.

[0190] Reference Figure 12B and Figure 12C Further details are discussed regarding how to indicate predicted beam failure information. Figure 12B In this process, terminal device 110 can provide beam prediction failure information to network device 120, where the beam can be one or more beams reported in a beam report used for prediction result reporting on the UE side. Figure 12C In this context, terminal device 110 can provide network device 120 with beam prediction failure information, which may be one or more beams indicated via beam indication for future time instances.

[0191] Therefore, terminal device 110 can provide useful information about potential beam quality to avoid incorrect configurations that could lead to beam failure of network device 120.

[0192] Now for reference Figure 12B .like Figure 12BAs shown, terminal device 110 provides prediction failure information in its prediction result report on the UE side. Specifically, network device 120 can configure set B measurements to terminal device 110, and terminal device 110 can perform beam prediction. Then, terminal device 110 reports the prediction result (i.e., the first message) to the network device, which includes prediction beam information, time information, and prediction failure labels for one or more beams in the prediction beam at one or more time instances. Based on the first message, the network device can transmit beam indications for future time instances.

[0193] In some implementations, in one reporting instance, terminal device 110 needs to report a prediction based on the output of an AI / ML model, wherein the report may include both beam information (i.e., prediction beam failure information) and duration information.

[0194] In some implementations, beam information may be in the following forms: TCI status ID, RS ID, beam ID, etc. Beam information may also include predicted beam quality information (e.g., RSRP, SINR, etc.) and / or predicted beam failure information. In some implementations, this information may be a 1-bit indicator (e.g., ... Figure 13 The F label shown in the diagram illustrates an example of configuration information 1300.

[0195] In some implementations, beam information can be the predicted failure probability or likelihood or confidence level, for example, within the range of 0 and 1.

[0196] In some implementations, beam information may be determined per beam or per future time instance, or only for the beam with the highest prediction failure probability, or for the beam with a prediction failure probability above a threshold.

[0197] In some implementations, whether and how prediction failure information is reported can be based on network configuration.

[0198] In some implementations, whether and how to report prediction failure information can be based on the probability or confidence level of prediction failure, for example, reporting only when a specific probability or confidence threshold is met.

[0199] In some implementations, information on whether a UE can predict failure can be described based on UE capabilities and / or AI / ML models.

[0200] In some implementations, beam information can be uniform across all channels / signals or dedicated to specific channels / signals.

[0201] In some implementations, the duration information may be in one or more of the following forms: Start time pointBeam #1 is the first predicted beam starting from time point #1, beam #2 is the first predicted beam starting from time point #2, and so on; additionally, the UE can report the first K predicted beams instead of just one; (e.g.) Figure 14A As shown, it illustrates an example of configuration information 1400A). Duration: Beam #1 is the first predicted beam during duration #1, beam #2 is the first predicted beam during duration #2, and so on; this may mean that durations #1 and #2 are adjacent. Furthermore, a signal is needed to notify or define the start time of beam #1; (e.g.) Figure 14B As shown, it illustrates an example of configuration information 1400B). End time Beam #1 is the first predicted beam at cutoff time #1, beam #2 is the first predicted beam at cutoff time #2, and so on. Additionally, a signal needs to be sent to notify or define the start time of beam #1.

[0202] In some implementations, the reported future beam can also be used over discontinuous durations; that is, for each reported future beam, it is necessary to signal the start point and duration, or to signal the start and end points, such as... Figure 14C As shown, it illustrates an example of configuration information 1400C.

[0203] In some implementations, time information can be explicitly indicated for each reported future beam. Alternatively, time information can be signaled or defined for all beams.

[0204] like Figure 12C As shown, terminal device 110 can provide beam indication prediction failure information feedback information.

[0205] Network device 120 can configure set B measurements to the UE, and the UE can perform beam prediction. The UE then reports the prediction results to the network device. Based on a first message, the network device can transmit beam indications for future time instances. Next, the UE reports a beam prediction failure for one or more indicated beams in the future time instance, i.e., the first message. Below, the network device updates the beam indications for the future time instances.

[0206] In some implementations, the beam indication for future time instances includes a list of beam information and duration information. In some implementations, the beam information may be in the form of: TCI status ID, RS ID, beam ID, etc.

[0207] In some implementations, if beam prediction is performed on the network side, the beam information may also include predicted beam quality information (e.g., RSRP, SINR, etc.) and / or predicted beam failure information.

[0208] In some implementations, beam information can be uniform across all channels / signals or dedicated to specific channels / signals.

[0209] In some implementations, the duration information may be at least one start time point (also referred to as the first switching time point) corresponding to the at least one future duration. Now refer to... Figure 14A This example illustrates configuration information 1400A. In Figure 14A In this process, terminal device 110 is configured to start / switch at time point #1 to measure the first beam #1, start / switch at time point #2 to measure the second beam #2, and so on.

[0210] Alternatively, in some embodiments, the duration information may be at least one end time point (also referred to as a second switching time point) corresponding to the at least one future duration. This may mean applying the first beam #1 before time point #1, applying the second beam #2 between time point #1 and time point #2, and so on. Additionally, in some embodiments, it is necessary to signal or define the start time point for applying the first beam #1.

[0211] Alternatively, in some embodiments, the duration information may be at least one time length (also referred to as at least one duration, or at least one beam dwell time) corresponding to the at least one future duration. Now refer to Figure 14B This example illustrates configuration information 1400B. In Figure 14B In this configuration, terminal device 110 is configured to apply a first beam #1 during duration #1, a second beam #2 during duration #2, and so on. In some implementations, this may mean that durations #1 and #2 are adjacent. Additionally, in some implementations, it is necessary to signal or define the start / end time points for applying the first beam #1.

[0212] Alternatively, in some implementations, the duration information may be at least one start time point and at least one end time point. In this way, the indicated future beam can be used in a discontinuous manner.

[0213] Alternatively, in some embodiments, the duration information may be at least one start time point and at least one time length corresponding to at least one future duration. Now refer to Figure 14C The example provided illustrates configuration information 1400C.

[0214] In addition to explicitly indicating each future beam, you can also signal or define duration information for all beams, such as the same time interval T and start time point t0.

[0215] In some implementations, beam indication for future time instances can be configured via RRC and activated / indicated via MACCE, DCI, or a combination thereof.

[0216] In some implementations, feedback (i.e., the first message) may be carried in the acknowledgement information of the beam indication reception.

[0217] In some implementations, the predicted beam failure label can be a 1-bit indicator for each indicated beam or each time instance, for example, in the form of a bitmap with an N-bit length.

[0218] Alternatively, the predicted beam failure information can be an indicator with a bit length ceil(log2(N)), where N is the number of future beams indicated, or the number of future time instances indicated.

[0219] Alternatively, the predicted beam failure information can also be the predicted failure probability, likelihood, or confidence level, for example, within the range of 0 and 1.

[0220] In some implementations, beam failure prediction information may be determined on a per-beam or per-future-time-instance basis, or only for the beam with the highest predicted failure probability, or for the beam with a predicted failure probability above a threshold.

[0221] In some implementations, whether and how prediction failure information is reported can be based on network configuration.

[0222] In some implementations, whether and how to report prediction failure information can be based on the prediction failure probability or confidence level, for example, reporting only when a specific probability or confidence threshold is met.

[0223] In some implementations, information on whether a UE can predict failure can be described based on UE capabilities and / or AI / ML models.

[0224] In some implementations, the UE may recommend a suitable beam to replace a beam that is predicted to fail.

[0225] In some implementations, the update information carries updated beam information, and in addition, it carries selection information to select which future beam needs to be updated, or which time information corresponding to a beam needs to be updated.

[0226] In some implementations, when the UE provides feedback regarding beam indication, including a predicted failure label, the UE may further postpone the timing of beam indication application to: 1) the reception time of the indication + Tf, where Tf is the waiting time window for the network to update the beam indication; or, the time when the UE transmits feedback regarding the reception of the indication + Tf, such as... Figure 15 As shown, it illustrates the timing of time beam prediction at 1500.

[0227] In some implementations, terminal device 110 may postpone the application of the beam associated with a predicted failure or the beam associated with a predicted failure as indicated in the first message.

[0228] In some implementations, if beam indication is provided for future time instances, the UE expects the DCI to not carry TCI information for a certain period of time, or the UE ignores the TCI carried in the DCI received during that period, such as... Figure 16 As shown, it illustrates the timing 1600 of time beam prediction.

[0229] In some implementations, if a beam indication for a future time instance is provided (i.e., network device 120 configures terminal device 110 to use beams in a future time instance), network device 120 may also provide an enable configuration / indication. Therefore, in some implementations, based on this configuration / indication, terminal device 110 may anticipate not receiving additional configuration information indicating at least one additional first beam set during the at least one first future duration. Alternatively or additionally, based on this configuration / indication, terminal device 110 may ignore at least one additional first beam set included in the additional configuration information during the at least one first future duration.

[0230] In some implementations, a first-in, first-out (FIFO) approach can be used to update beam indication. In this way, updating information only requires providing beam information, such as... Figure 17 As shown, it illustrates the timing 1700 of time beam prediction.

[0231] In some implementations, the update information only involves beam information (and future duration information; if the future duration is determined to be the default configuration, the future duration information can be omitted from the update information). Furthermore, the number of beams can be flexibly configured. In some implementations, the number of beams indicated in the update information is less than the number of beams indicated by the beam indication. In this way, signaling overhead is reduced.

[0232] In some implementations, the update information carries updated beam information and selection information to select which future beam needs to be updated, or which time information corresponding to a beam needs to be updated, such as... Figure 18As shown, it illustrates the timing of time beam prediction at 1800.

[0233] In other words, network device 120 can maintain / update the latest beam indication information via a first-in, first-out (FIFO) approach. In some implementations, network device 120 may periodically send beam indications to terminal device 110. Alternatively, in some implementations, network device 120 may send beam indications based on the maintained FIFO beam information after receiving beam feedback information (i.e., the first message) from terminal device 110. This simplifies the logic used to generate beam information at network device 120.

[0234] In some implementations, once prediction failure information is reported, the UE autonomously performs a beam indication update by discarding the beam with the prediction failure or replacing it with a recommended or default beam.

[0235] In some implementations, the default beam can be an indicated future beam for the last time instance or an indicated future beam for the next time instance.

[0236] In this way, network device 120 only needs to update the beams predicted to be associated with beam failure, thus reducing signaling overhead.

[0237] Example Method Figure 19 A flowchart illustrating a communication method 1900 implemented at a terminal device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1900 is described from the perspective of terminal device 110.

[0238] At box 1910, terminal device 110 determines at least one set of reference signals (RS) corresponding to at least one future duration. One of the at least one set of RSs includes one or more RSs for measurement. The at least one set of RSs is associated with at least one of the following: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM).

[0239] At box 1920, terminal device 110 performs RS measurements on the at least one RS set over at least one corresponding future duration.

[0240] In some example implementations, terminal device 110 receives configuration information from network device 120, which indicates the at least one set of RSs and at least one future duration corresponding to the at least one set of RSs. Furthermore, terminal device 110 performs RS measurements based on this configuration information.

[0241] In some example implementations, the at least one future duration is indicated by one of the following: at least one start time corresponding to the at least one future duration, at least one end time corresponding to the at least one future duration, at least one time length corresponding to the at least one future duration, a start time corresponding to the first future duration among the at least one future duration, or a common time length corresponding to each of the at least one future duration.

[0242] In some example implementations, one of the at least one RSs in the set is indicated by one of the following: the identifier of the RS, the identifier of the beam associated with the RS, the Transmission Configuration Indicator (TCI) associated with the RS, or the Quasi-Co-location (QCL) information associated with the RS.

[0243] In some example implementations, the configuration information also indicates at least one of the following: prediction quality information about the at least one RS set, or prediction failure information about the at least one RS set.

[0244] In some example implementations, if an RS is associated with prediction failure information, the terminal device 110 excludes the RS from the at least one set of RSs.

[0245] In some example implementations, the at least one RS set includes a first RS set corresponding to a first duration and a second RS set corresponding to a second duration following the first duration. The second RS set is at least partially different from the first RS set. Furthermore, the terminal device 110 can measure both the first RS set and the second RS set during a third duration prior to the end of the first duration.

[0246] In some example implementations, the third duration may be defined as a default value or determined by network device 120 or terminal device 110.

[0247] In some example implementations, terminal device 110 notifies its higher layers of beam failure at a period determined based on at least one of the following: the period of the RSs included in the at least one RS set, a predefined time length, a time length associated with a model, a scaling factor configured for discontinuous reception (DRX) mode, or the DRX cycle length.

[0248] In some example implementations, the model is used to predict beams, and the duration is correlated with the model's predictive power.

[0249] In some example implementations, the first value of the time length associated with the DRX mode is different from the second value of the time length associated with the non-DRX mode.

[0250] In some example implementations, the period is determined to be the maximum of at least one of the following: the minimum period of RS, a predefined time length, or a time length associated with the model.

[0251] In some example implementations, if the terminal device 110 is in DRX mode, the period is determined to be the maximum of at least one of the following: the minimum of the scaled period of RS, the scaled time length associated with the model, or the scaled DRX cycle length.

[0252] In some example implementations, terminal device 110 performs at least one of the following: resetting the beam failure counter at a first time point based on determining that a target beam will be applied at a second time point, wherein the first time point is earlier than the second time point; resetting the beam failure counter at a third time point based on determining that a different RS or RS set will be measured at a fourth time point, wherein the third time point is earlier than the fourth time point; resetting the beam failure counter when the measurement of an RS set is completed or when the measurement of a different RS set begins; or resetting the beam failure counter when the measurement of at least one RS set is completed.

[0253] In some example implementations, a fourth duration between the first and second time points is defined as a default value or determined by network device 120 or terminal device 110. A fifth duration between the third and fourth time points is defined as a default value or determined by network device 120 or terminal device 110.

[0254] In some example implementations, the at least one RS set includes a first RS set corresponding to a first duration and a second RS set corresponding to a second duration following the first duration. Furthermore, the terminal device 110 starts a beam failure counter at the beginning of the first duration. Based on the determination that the first RS set and the second RS set at least partially overlap, the terminal device 110 continues the beam failure counter during the second duration without resetting it.

[0255] In some example implementations, the maximum value of the beam failure counter is associated with at least one of the following: the number of future durations in the at least one future duration, or the number of RSs included in the RS set.

[0256] In some example implementations, if terminal device 110 or network device 120 predicts that at least one beam will be used in the at least one future duration, terminal device 110 stops performing the BFD process.

[0257] Figure 20 A flowchart illustrating a communication method 2000 implemented at network device 120 according to some embodiments of this disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 The method for describing the angle of network device 120 in 2000.

[0258] At box 2010, network device 120 generates configuration information indicating at least one set of reference signals (RS) corresponding to at least one future duration. One of the at least one set of RSs includes one or more RSs for measurement. The at least one set of RSs is associated with at least one of the following: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM).

[0259] At frame 2020, network device 120 sends configuration information to terminal device 110.

[0260] In some example implementations, the configuration information indicates the at least one future duration by one of the following: at least one start time corresponding to the at least one future duration, at least one end time corresponding to the at least one future duration, at least one time length corresponding to the at least one future duration, a start time corresponding to the first future duration among the at least one future duration, or a common time length corresponding to each of the at least one future duration.

[0261] In some example implementations, the configuration information indicates one of the at least one RS in the RS set by one of the following: the identifier of the RS, the identifier of the beam associated with the RS, the Transmission Configuration Indicator (TCI) associated with the RS, or the Quasi-Co-location (QCL) information associated with the RS.

[0262] In some example implementations, the configuration information also indicates at least one of the following: prediction quality information about the at least one RS set, or prediction failure information about the at least one RS set.

[0263] In some example implementations, if an RS is associated with prediction failure information, network device 120 excludes the RS from the at least one set of RSs.

[0264] Figure 21 A flowchart illustrating a communication method 2100 implemented at terminal device 110 according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 2100 is described from the perspective of terminal device 110.

[0265] At box 2110, terminal device 110 determines at least one first beam set that will be used for communication between terminal device 110 and network device 120 for at least one first future duration.

[0266] At block 2120, terminal device 110 sends a first message to network device 120 indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set; or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0267] In some example implementations, terminal device 110 receives configuration information from network device 120, which indicates: the at least one first beam set, and the at least one first future duration.

[0268] In some example implementations, after sending the first message, the terminal device 110 postpones the application timing or configuration information application timing for at least a second future duration.

[0269] In some example implementations, upon receiving configuration information, the terminal device 110 performs at least one of the following: anticipates not receiving additional configuration information indicating at least one additional first beam set during the at least one first future duration, or ignores at least one additional first beam set included in the additional configuration information during the at least one first future duration.

[0270] In some example implementations, terminal device 110 determines the at least one first beam set based on the output of a model used to predict beams and deployed at terminal device 110.

[0271] In some example implementations, the first message indicates at least one of the following: the at least one second beam set and the at least one second future duration, or at least one recommended beam set and the at least one third future duration.

[0272] In some example implementations, the at least one second future duration or the at least one third future duration is indicated by one of the following: at least one start time point corresponding to at least one corresponding future duration, at least one end time point corresponding to at least one corresponding future duration, at least one time length corresponding to at least one corresponding future duration, a start time point corresponding to the first future duration among at least one corresponding future duration, or a common time length corresponding to each of the at least one corresponding future duration.

[0273] In some example implementations, the beams in the at least one second beam set or recommended beam set are indicated by one of the following: beam identifier, identifier of the RS associated with the beam, transmission configuration indicator (TCI) associated with the beam, or quasi-co-address (QCL) information associated with the beam.

[0274] In some example implementations, the predicted beam failure information indicates at least one of the following: at least one first indication, each first indication indicating beam failure information corresponding to a beam set or future duration; and a plurality of second indications, each second indication indicating beam failure information corresponding to a RS.

[0275] In some example implementations, the predicted beam failure information includes at least one of the following: an indication of whether a predicted beam failure exists, a predicted beam failure probability, or predicted quality information.

[0276] In some example implementations, the second beam set includes at least one of the following: the beam with the highest failure probability, or at least one beam with a failure probability greater than or equal to a threshold probability.

[0277] In some example implementations, the threshold probability is defined as a default value or determined by network device 120 or terminal device 110.

[0278] In some example implementations, after sending the first message, terminal device 110 receives a second message from network device 120. The second message indicates at least one of the following: a beam indication indicating at least one beam to be used in the future, at least one fourth beam set for updating the at least one second beam set, confirmation information regarding the at least one recommended beam set, or at least one fifth beam set for updating at least one rejected recommended beam set.

[0279] Figure 22 A flowchart illustrating a communication method 2200 implemented at network device 120 according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1The angular description method of network device 120 in 2200.

[0280] At block 2210, network device 120 receives from terminal device 110 a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0281] In some example implementations, prior to receiving the first message, network device 120 receives configuration information indicating at least one first beam set for communication between terminal device 110 and network device 120, and at least one first future duration corresponding to the at least one first beam set.

[0282] In some example implementations, after receiving the first message, network device 120 postpones the application timing or configuration information application timing for at least a second future duration.

[0283] In some example implementations, the first message indicates at least one of the following: the at least one second beam set and the at least one second future duration, or at least one recommended beam set and the at least one third future duration.

[0284] In some example implementations, the at least one second future duration or the at least one third future duration is indicated by one of the following: at least one start time point corresponding to at least one corresponding future duration, at least one end time point corresponding to at least one corresponding future duration, at least one time length corresponding to at least one corresponding future duration, a start time point corresponding to the first future duration among at least one corresponding future duration, or a common time length corresponding to each of the at least one corresponding future duration.

[0285] In some example implementations, the beams in the at least one second beam set or recommended beam set are indicated by one of the following: beam identifier, identifier of the RS associated with the beam, transmission configuration indicator (TCI) associated with the beam, or quasi-co-address (QCL) information associated with the beam.

[0286] In some example implementations, the predicted beam failure information indicates at least one of the following: at least one first indication, each first indication indicating beam failure information corresponding to a beam set or future duration; and a plurality of second indications, each second indication indicating beam failure information corresponding to a RS.

[0287] In some example implementations, the predicted beam failure information includes at least one of the following: an indication of whether a predicted beam failure exists, a predicted beam failure probability, or predicted quality information.

[0288] In some example implementations, the second beam set includes at least one of the following: the beam with the highest failure probability, or at least one beam with a failure probability greater than or equal to a threshold probability.

[0289] In some example implementations, the threshold probability is defined as a default value or determined by network device 120 or terminal device 110.

[0290] In some example implementations, after receiving the first message, network device 120 sends a second message to terminal device 110. The second message indicates at least one of the following: a beam indication indicating at least one beam to be used in the future, at least one fourth beam set for updating the at least one second beam set, confirmation information regarding the at least one recommended beam set, or at least one fifth beam set for updating at least one rejected recommended beam set.

[0291] Example devices and apparatus Figure 23 This is a simplified block diagram of device 2300 suitable for implementing embodiments of this disclosure. Device 2300 can be considered as follows: Figure 1 Another example implementation of any of the devices shown. Therefore, device 2300 may be implemented at or be at least a part of terminal device 110 or network device 120.

[0292] As shown in the figure, device 2300 includes a processor 2310, a memory 2320 coupled to the processor 2310, a suitable transceiver 2340 coupled to the processor 2310, and a communication interface coupled to the transceiver 2340. The memory 2320 stores at least a portion of the program 2330. Depending on requirements, the transceiver 2340 can be used for bidirectional or unidirectional communication. The transceiver 2340 may include at least one of a transmitter 2342 and a receiver 2344. The transmitter 2342 and receiver 2344 may be functional modules or physical entities. The transceiver 2340 has at least one antenna to facilitate communication; however, in practice, the access node mentioned in this application may have several antennas. The communication interface can represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and relay nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal equipment.

[0293] Assume that program 2330 includes program instructions that, when executed by the associated processor 2310, enable device 2300 to operate according to embodiments of this disclosure, as referenced herein. Figures 1 to 23 The embodiments discussed herein may be implemented by computer software executable by processor 2310 of device 2300, or by hardware, or by a combination of software and hardware. Processor 2310 may be configured to implement various embodiments of this disclosure. Furthermore, a combination of processor 2310 and memory 2320 may form a processing unit 2350 suitable for implementing various embodiments of this disclosure.

[0294] Memory 2320 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 2320 is shown in device 2300, several physically different memory modules may exist in device 2300. Processor 2310 can be of any type suitable for a local technology network and may include one or more of the following: as non-limiting examples, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Device 2300 may have multiple processors, such as application-specific integrated circuit chips, which are time-dependent on a clock that synchronizes the main processor.

[0295] According to embodiments of this disclosure, a terminal device including circuitry is provided. The circuitry is configured to: determine at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one RS set including one or more RSs for measurement, the at least one RS set being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and perform RS measurements on the at least one RS set during at least one corresponding future duration. According to embodiments of this disclosure, the circuitry can be configured to perform any of the methods discussed above implemented by the terminal device.

[0296] According to embodiments of this disclosure, a network device including circuitry is provided. The circuitry is configured to: generate configuration information indicating at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one RS set including one or more RSs for measurement, the at least one RS set being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and transmit the configuration information to a terminal device. According to embodiments of this disclosure, the circuitry can be configured to perform any of the methods discussed above implemented by the network device.

[0297] According to embodiments of this disclosure, a terminal device including circuitry is provided. The circuitry is configured to: determine at least one first beam set to be used for communication between the terminal device and a network device over at least a first future duration; and send to the network device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set; or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure. According to embodiments of this disclosure, the circuitry can be configured to perform any of the methods implemented by the terminal device as discussed above.

[0298] According to embodiments of this disclosure, a network device including circuitry is provided. The circuitry is configured to receive from a terminal device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure. According to embodiments of this disclosure, the circuitry can be configured to perform any method implemented by the network device as discussed above.

[0299] As used herein, the term "circuit" can refer to hardware circuitry and / or a combination of hardware and software circuitry. For example, a circuit can be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit can be any part of a hardware processor with software, including digital signal processors, software, and memory, which work together to enable a device (such as a terminal device or network device) to perform various functions. In yet another example, a circuit can be hardware circuitry and / or a processor (such as a microprocessor or a portion thereof) that requires software / firmware to operate, but which may be absent when operation is not required. As used herein, the term "circuit" also encompasses a specific implementation of hardware circuitry or a processor alone, or a portion thereof, and its accompanying software and / or firmware.

[0300] According to embodiments of this disclosure, a terminal device is provided. The terminal device includes: components for determining at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RSs including one or more RSs for measurement, the at least one set of RSs being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and components for performing RS measurements on the at least one set of RSs during at least one corresponding future duration. In some embodiments, the first device may include components for performing a corresponding operation of method 1900. In some example embodiments, the first device may also include components for performing other operations of some example embodiments of method 1900. The components may be implemented in any suitable form. For example, the components may be implemented as circuitry or software modules.

[0301] According to embodiments of this disclosure, a network apparatus is provided. The network apparatus includes: components for generating configuration information indicating at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RSs including one or more RSs for measurement, the at least one set of RSs being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and components for transmitting the configuration information to a terminal device. In some embodiments, a second component may include components for performing corresponding operations of method 2000. In some example embodiments, the second component may also include components for performing other operations of some example embodiments of method 2000. The component may be implemented in any suitable form. For example, the component may be implemented as a circuit or a software module.

[0302] According to embodiments of this disclosure, a terminal device is provided. The terminal device includes: components for determining at least one first beam set to be used for communication between the terminal device and a network device over at least a first future duration; and components for sending a first message to the network device indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set; or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure. In some embodiments, a third component may include components for performing corresponding operations of method 2100. In some example embodiments, the third component may also include components for performing other operations of some example embodiments of method 2100. The component may be implemented in any suitable form. For example, the component may be implemented as a circuit or a software module.

[0303] According to embodiments of this disclosure, a network apparatus is provided. The network apparatus includes components for receiving from a terminal device a first message indicating at least one of: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure. In some embodiments, a fourth component may include components for performing corresponding operations of method 2200. In some example embodiments, the fourth component may also include components for performing other operations of some example embodiments of method 2200. This component may be implemented in any suitable form. For example, the component may be implemented as a circuit or a software module.

[0304] In summary, the implementation scheme disclosed herein provides the following aspects.

[0305] In one aspect, a terminal device is proposed, comprising: a processor configured to cause the terminal device to: determine at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RSs including one or more RSs for measurement, the at least one set of RSs being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and perform RS measurements on the at least one set of RSs during at least one corresponding future duration.

[0306] In some implementations, the processor is further configured to cause the terminal device to: receive configuration information from the network device, the configuration information indicating: the at least one RS set, and at least one future duration corresponding to the at least one RS set; and perform RS measurements based on the configuration information.

[0307] In some implementations, the at least one future duration is indicated by one of the following: at least one start time corresponding to the at least one future duration, at least one end time corresponding to the at least one future duration, at least one time length corresponding to the at least one future duration, a start time corresponding to the first future duration among the at least one future duration, or a common time length corresponding to each of the at least one future duration.

[0308] In some implementations, one of the at least one RSs in the set is indicated by one of the following: the identifier of the RS, the identifier of the beam associated with the RS, the transmission configuration indicator (TCI) associated with the RS, or the quasi-co-address (QCL) information associated with the RS.

[0309] In some implementations, the configuration information also indicates at least one of the following: prediction quality information about the at least one RS set, or prediction failure information about the at least one RS set.

[0310] In some implementations, the processor is further configured to cause the terminal device to exclude an RS from the at least one set of RSs if an RS is associated with prediction failure information.

[0311] In some embodiments, the at least one RS set includes a first RS set corresponding to a first duration and a second RS set corresponding to a second duration following the first duration, the second RS set being at least partially different from the first RS set, and wherein the processor is further configured to cause the terminal device to measure both the first RS set and the second RS set during a third duration prior to the end of the first duration.

[0312] In some implementations, the third duration is defined as a default value or determined by the network device or terminal device.

[0313] In some implementations, the processor is further configured to cause the terminal device to periodically notify higher layers of the terminal device of beam failure based on at least one of the following: the period of the RSs included in the at least one RS set, a predefined time length, a time length associated with the model, a scaling factor configured for discontinuous reception (DRX) mode, or the DRX cycle length.

[0314] In some implementations, the model is used to predict beams, and the duration is correlated with the model's predictive power.

[0315] In some implementations, the first value of the time length associated with the DRX mode is different from the second value of the time length associated with the non-DRX mode.

[0316] In some implementations, the period is determined to be the maximum of at least one of the following: the minimum period of RS, a predefined time length, or a time length associated with the model.

[0317] In some implementations, if the terminal device is in DRX mode, the period is determined to be the maximum of at least one of the following: the minimum scaled period of RS, the scaled time length associated with the model, or the scaled DRX cycle length.

[0318] In some implementations, the processor is further configured to cause the terminal device to perform at least one of the following: resetting the beam failure counter at a first time point based on determining that a target beam will be applied at a second time point, wherein the first time point is earlier than the second time point; resetting the beam failure counter at a third time point based on determining that a different RS or RS set will be measured at a fourth time point, wherein the third time point is earlier than the fourth time point; resetting the beam failure counter when the measurement of an RS set is completed or when the measurement of a different RS set begins; or resetting the beam failure counter when the measurement of at least one RS set is completed.

[0319] In some implementations, a fourth duration between the first and second time points is defined as a default value or determined by the network device or terminal device; a fifth duration between the third and fourth time points is defined as a default value or determined by the network device or terminal device.

[0320] In some embodiments, the at least one RS set includes a first RS set corresponding to a first duration and a second RS set corresponding to a second duration following the first duration, and wherein the processor is further configured to cause the terminal device to: start a beam failure counter at the beginning of the first duration; and, based on the determination that the first RS set and the second RS set at least partially overlap, continue the beam failure counter without resetting it during the second duration.

[0321] In some implementations, the maximum value of the beam failure counter is associated with at least one of the following: the number of future durations in the at least one future duration, or the number of RSs included in the RS set.

[0322] In some implementations, the processor is further configured to cause the terminal device to stop executing the BFD process if the terminal device or network device predicts that at least one beam will be used in the at least one future duration.

[0323] In one aspect, a network device is proposed, comprising: a processor configured to cause the network device to: generate configuration information indicating at least one set of reference signals (RS) corresponding to at least one future duration, one of the at least one set of RS including one or more RS for measurement, the at least one set of RS being associated with at least one of: beam failure detection (BFD), candidate beam measurement, or radio link monitoring (RLM); and transmit the configuration information to a terminal device.

[0324] In some implementations, the configuration information indicates the at least one future duration by one of the following: at least one start time corresponding to the at least one future duration, at least one end time corresponding to the at least one future duration, at least one time length corresponding to the at least one future duration, a start time corresponding to the first future duration among the at least one future duration, or a common time length corresponding to each of the at least one future duration.

[0325] In some implementations, the configuration information indicates one of the at least one RS in the RS set by one of the following: the identifier of the RS, the identifier of the beam associated with the RS, the Transmission Configuration Indicator (TCI) associated with the RS, or the Quasi-Co-location (QCL) information associated with the RS.

[0326] In some implementations, the configuration information also indicates at least one of the following: prediction quality information about the at least one RS set, or prediction failure information about the at least one RS set.

[0327] In some implementations, the processor is further configured to cause the network device to exclude an RS from the at least one set of RSs if an RS is associated with prediction failure information.

[0328] In one aspect, a terminal device is proposed, the terminal device comprising: a processor configured to cause the terminal device to: determine at least one first beam set to be used for communication between the terminal device and a network device for at least one first future duration; and send to the network device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set; or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0329] In some implementations, the processor is further configured to cause the terminal device to: receive configuration information from the network device, the configuration information indicating: the at least one first beam set, and the at least one first future duration.

[0330] In some implementations, the processor is further configured to cause the terminal device to: postpone the application timing of the at least one second future duration or the application timing of the configuration information after sending the first message.

[0331] In some embodiments, the processor is further configured to cause the terminal device, upon receiving configuration information, to perform at least one of the following: anticipating not to receive additional configuration information indicating at least one additional first beam set during the at least one first future duration, or ignoring at least one additional first beam set included in the additional configuration information during the at least one first future duration.

[0332] In some implementations, the processor is further configured to cause the terminal device to determine the at least one first beam set based on the output of a model used to predict beams and deployed at the terminal device.

[0333] In some implementations, the first message indicates at least one of the following: the at least one second beam set and the at least one second future duration, or at least one recommended beam set and the at least one third future duration.

[0334] In some embodiments, the at least one second future duration or the at least one third future duration is indicated by one of the following: at least one start time point corresponding to at least one corresponding future duration, at least one end time point corresponding to at least one corresponding future duration, at least one time length corresponding to at least one corresponding future duration, a start time point corresponding to the first future duration among at least one corresponding future duration, or a common time length corresponding to each of the at least one corresponding future duration.

[0335] In some implementations, the beams in the at least one second beam set or recommended beam set are indicated by one of the following: beam identifier, identifier of the RS associated with the beam, transmission configuration indicator (TCI) associated with the beam, or quasi-co-address (QCL) information associated with the beam.

[0336] In some implementations, the predicted beam failure information indicates at least one of the following: at least one first indication, each first indication indicating beam failure information corresponding to a beam set or future duration; and a plurality of second indications, each second indication indicating beam failure information corresponding to a RS.

[0337] In some implementations, the predicted beam failure information includes at least one of the following: an indication of whether a predicted beam failure exists, a predicted beam failure probability, or predicted quality information.

[0338] In some implementations, the second beam set includes at least one of the following: the beam with the highest failure probability, or at least one beam with a failure probability greater than or equal to a threshold probability.

[0339] In some implementations, this threshold probability is defined as a default value or determined by the network device or the terminal device.

[0340] In some implementations, the processor is further configured to cause the terminal device to: after sending the first message, receive a second message from the network device, the second message indicating at least one of the following: a beam indication indicating at least one beam to be used in the future duration, at least one fourth beam set for updating the at least one second beam set, confirmation information regarding the at least one recommended beam set, or at least one fifth beam set for updating at least one rejected recommended beam set.

[0341] In one aspect, a network device is proposed, the network device comprising: a processor configured such that the network device: receives from a terminal device a first message indicating at least one of the following: predicted beam failure information for at least one second beam set corresponding to at least one second future duration, or at least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

[0342] In some implementations, the processor is further configured to cause the network device to: receive configuration information from the network device before receiving the first message, the configuration information indicating: at least one first beam set for communication between the terminal device and the network device, and at least one first future duration corresponding to the at least one first beam set.

[0343] In some implementations, the processor is further configured to cause the network device to: postpone the application timing of the at least one second future duration or the application timing of the configuration information after receiving the first message.

[0344] In some implementations, the first message indicates at least one of the following: the at least one second beam set and the at least one second future duration, or at least one recommended beam set and the at least one third future duration.

[0345] In some embodiments, the at least one second future duration or the at least one third future duration is indicated by one of the following: at least one start time point corresponding to at least one corresponding future duration, at least one end time point corresponding to at least one corresponding future duration, at least one time length corresponding to at least one corresponding future duration, a start time point corresponding to the first future duration among at least one corresponding future duration, or a common time length corresponding to each of the at least one corresponding future duration.

[0346] In some implementations, the beams in the at least one second beam set or recommended beam set are indicated by one of the following: beam identifier, identifier of the RS associated with the beam, transmission configuration indicator (TCI) associated with the beam, or quasi-co-address (QCL) information associated with the beam.

[0347] In some implementations, the predicted beam failure information indicates at least one of the following: at least one first indication, each first indication indicating beam failure information corresponding to a beam set or future duration; and a plurality of second indications, each second indication indicating beam failure information corresponding to a RS.

[0348] In some implementations, the predicted beam failure information includes at least one of the following: an indication of whether a predicted beam failure exists, a predicted beam failure probability, or predicted quality information.

[0349] In some implementations, the second beam set includes at least one of the following: the beam with the highest failure probability, or at least one beam with a failure probability greater than or equal to a threshold probability.

[0350] In some implementations, this threshold probability is defined as a default value or determined by the network device or the terminal device.

[0351] In some implementations, the processor is further configured to cause the network device, after receiving the first message, to send a second message to the terminal device, the second message indicating at least one of the following: a beam indication indicating at least one beam to be used in the future duration, at least one fourth beam set for updating the at least one second beam set, confirmation information regarding the at least one recommended beam set, or at least one fifth beam set for updating at least one rejected recommended beam set.

[0352] In one aspect, a terminal device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the terminal device as discussed above.

[0353] In one aspect, a network device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the network device as discussed above.

[0354] In one aspect, a computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the terminal device discussed above.

[0355] In one aspect, a computer-readable medium stores instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0356] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods discussed above and implemented by the terminal device.

[0357] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0358] Generally, various embodiments of this disclosure can be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Although various aspects of embodiments of this disclosure are illustrated and described using block diagrams, flowcharts, or other illustrations, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0359] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (such as those included in program modules) that execute on a target real or virtual processor in a device to perform the functions described above. Figures 1 to 23 The described process or method. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. The functionality of a program module can be combined in various implementation schemes or split among program modules as needed. The machine-executable instructions used for a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0360] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0361] The aforementioned program code may be embodied on a machine-readable medium, which may be any tangible medium containing or storing a program used by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0362] Furthermore, although the operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all the illustrated operations to achieve the desired result. In some environments, multitasking and parallel processing can be advantageous. While several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in a single embodiment in combination. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0363] Although this disclosure has been described using language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.

Claims

1. A terminal device, the terminal device comprising: Processor, the processor being configured to cause the terminal device to: Determine at least one set of reference signals (RS) corresponding to at least one future duration, wherein one of the at least one set of RSs includes one or more RSs for measurement, and the at least one set of RSs is associated with at least one of the following: Beam failure detection (BFD) Candidate beam measurement, or Radio link monitoring (RLM); and RS measurements are performed on the at least one set of RSs during the at least one corresponding future duration.

2. The terminal device according to claim 1, wherein the processor is further configured to cause the terminal device to: Receive configuration information from the network device, the configuration information indicating: The at least one RS set, and The at least one future duration corresponding to the at least one set of RS; and The RS measurement is performed based on the configuration information.

3. The terminal device according to claim 2, wherein the at least one future duration is indicated by one of the following: At least one start time point corresponding to the at least one future duration. At least one end time point corresponding to the at least one future duration, At least one time length corresponding to the at least one future duration. The starting time point corresponding to the first future duration in the at least one future duration, or The common time length corresponding to each of the at least one future duration.

4. The terminal device according to claim 2, wherein the configuration information further indicates at least one of the following: Predicted quality information regarding the at least one RS set, or Information regarding prediction failures for at least one set of RS.

5. The terminal device according to claim 1, wherein the processor is further configured to cause the terminal device to: If an RS is associated with prediction failure information, the RS is excluded from the at least one set of RSs.

6. The terminal device of claim 1, wherein the at least one RS set includes a first RS set corresponding to a first duration and a second RS set corresponding to a second duration following the first duration, the second RS set being at least partially different from the first RS set. Furthermore, the processor is further configured to enable the terminal device to: Both the first RS set and the second RS set are measured during a third duration prior to the end of the first duration.

7. The terminal device according to claim 1, wherein the processor is further configured to cause the terminal device to: The terminal device shall notify its higher layers of beam failure at a period determined based on at least one of the following: The period of the RSs included in the at least one RS set, Predefined time length, The length of time associated with the model, The scaling factor configured for discontinuous reception (DRX) mode, or DRX loop length.

8. The terminal device of claim 7, wherein the first value of the time length associated with the DRX mode is different from the second value of the time length associated with the non-DRX mode.

9. The terminal device of claim 7, wherein the period is determined to be the maximum value of at least one of the following: The minimum value of the period of RS, The predefined time length, or The time length associated with the model.

10. The terminal device of claim 1, wherein the processor is further configured to cause the terminal device to perform at least one of the following: The beam failure counter is reset at a first time point, which is earlier than the second time point, based on the determination that the target beam will be applied at a second time point; The beam failure counter is reset at a third time point, which is earlier than the fourth time point, based on the determination that a different RS or RS set will be measured at a fourth time point. Reset the beam failure counter when the measurement of the RS set is completed or when the measurement of a different RS set begins; or The beam failure counter is reset upon completion of the measurement of at least one RS set.

11. A network device, the network device comprising: Processor, the processor being configured to cause the network device to: Generate configuration information indicating at least one set of reference signals (RS) corresponding to at least one future duration, wherein one of the at least one set of RSs includes one or more RSs for measurement, and the at least one set of RSs is associated with at least one of the following: Beam failure detection (BFD) Candidate beam measurement, or Radio Link Monitoring (RLM); and The configuration information is sent to the terminal device.

12. A terminal device, the terminal device comprising: Processor, the processor being configured to cause the terminal device to: Determine at least one first beam set to be used for communication between the terminal device and the network device during at least one first future duration; and A first message is sent to the network device, the first message indicating at least one of the following: Predicted beam failure information for at least one second beam set corresponding to the at least one second future duration, wherein the at least one second beam set is the same as or part of the at least one first beam set, or At least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

13. The terminal device of claim 12, wherein the processor is further configured to cause the terminal device to: Receive configuration information from the network device, the configuration information indicating: The at least one first beam set, and The at least one first future duration.

14. The terminal device of claim 13, wherein the processor is further configured to cause the terminal device to: After sending the first message, postpone the application timing of the at least one second future duration or the application timing of the configuration information.

15. The terminal device of claim 13, wherein the processor is further configured to cause the terminal device to: Upon receiving the configuration information, perform at least one of the following operations: During the at least one first future duration, it is anticipated that no further configuration information indicating at least one additional first beam set will be received, or At least one additional first beam set included in the additional configuration information is ignored during the at least one first future duration.

16. The terminal device of claim 12, wherein the first message indicates at least one of the following: The at least one second beam set and the at least one second future duration, or At least one recommended beam set, and at least one third future duration.

17. The terminal device of claim 12, wherein the predicted beam failure information includes at least one of the following: Indicates whether there is an indication of predicted beam failure. Predicted beam failure probability, or Predicted quality information.

18. The terminal device of claim 12, wherein the second beam set comprises at least one of the following: The beam with the highest failure probability, or At least one beam whose failure probability is higher than or equal to the threshold probability.

19. The terminal device of claim 12, wherein the processor is further configured to cause the terminal device to: After sending the first message, a second message is received from the network device, the second message indicating at least one of the following: A beam indicator that indicates at least one beam that will be used over a future duration. For updating at least one fourth beam set of the at least one second beam set, Confirmation information regarding the at least one recommended beam set, or Used to update at least one fifth beam set of at least one rejected recommended beam set.

20. A network device, the network device comprising: Processor, the processor being configured to cause the network device to: Receive a first message from the terminal device, the first message indicating at least one of the following: Predicted beam failure information for at least one second beam set corresponding to the at least one second future duration, or At least one recommended beam set corresponding to at least one third future duration, each recommended beam set corresponding to a beam set predicted to be associated with beam failure.

Images