WO2025030281A1

WO2025030281A1 - Devices and methods for communication

Info

Publication number: WO2025030281A1
Application number: PCT/CN2023/111328
Authority: WO
Inventors: Zhen He; Peng Guan; Lin Liang; Rao SHI; Gang Wang
Original assignee: NEC Corp
Current assignee: NEC Corp
Priority date: 2023-08-04
Filing date: 2023-08-04
Publication date: 2025-02-13
Anticipated expiration: 2026-02-04

Abstract

Embodiments of the present disclosure provide a solution for communication. In a solution, a terminal device receives, from a network device, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type; receives a first message for triggering CSI report from the network device, the first message indicating the trigger state comprised in the list of trigger states; and transmits, to the network device, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.

Description

DEVICES AND METHODS FOR COMMUNICATION

FIELDS

Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for configuration and determination of CSI (Channel State Information) report.

BACKGROUND

As communication networks and services increase in size, complexity, and number of users, operations in the communication networks may become increasingly more complicated. In order to improve the communication performance, artificial intelligence (AI) /machine learning (ML) technology is proposed to be used in the wireless communication network.

As an example scenario, the AI/ML model can be deployed on terminal devices or network devices. It is desired that the terminal devices and the network devices may support ML/AI models and terminal devices may report AI/ML based CSI feedback.

SUMMARY

In general, embodiments of the present disclosure provide devices and methods for configuration and determination of CSI report.

In a first aspect, there is provided a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type; receive a first message for triggering CSI report from the network device, the first message indicating the trigger state comprised in the list of trigger states; and transmit, to the network device, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.

In a second aspect, there is provided a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, a second message for triggering channel state information (CSI) report; determine a target CSI type from a first CSI type and a second CSI type based on at least one of the following: a first timing required for CSI computation corresponding to the first CSI type, a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or an uplink timing of the uplink resource carrying the CSI report; and transmit, to the network device, a CSI report with the determined target CSI type.

In a third aspect, there is provided a network device comprising: a processor configured to cause the network device to: transmit, to a terminal device, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type; transmit a first message for triggering CSI report to the terminal device, the first message indicating the trigger state comprised in the list of trigger states; and receive, from the terminal device, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.

In a fourth aspect, there is provided a network device comprising: a processor configured to cause the network device to: transmit, to a terminal device, a second message for triggering channel state information (CSI) report; determine a target CSI type from a first CSI type and a second CSI type based on at least one of the following: a first timing required for CSI computation corresponding to the first CSI type, a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or an uplink timing of the uplink resource carrying the CSI report; and receive, from the terminal device, a CSI report with the determined target CSI type.

In a fifth aspect, there is provided a communication method performed by a terminal device. The method comprises: receiving, from a network device, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type; receiving a first message for triggering CSI report from the network device, the first message indicating the trigger state comprised in the list of trigger states; and transmitting, to the network device, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.

In a sixth aspect, there is provided a communication method performed by a terminal device. The method comprises: receiving, from a network device, a second message for triggering channel state information (CSI) report; determining a target CSI type from a first CSI type and a second CSI type based on at least one of the following: a first timing required for CSI computation corresponding to the first CSI type, a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or an uplink timing of the uplink resource carrying the CSI report; and transmitting, to the network device, a CSI report with the determined target CSI type.

In a seventh aspect, there is provided a communication method performed by a network device. The method comprises: transmitting, to a terminal device, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type; transmitting a first message for triggering CSI report to the terminal device, the first message indicating the trigger state comprised in the list of trigger states; and receiving, from the terminal device, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.

In an eighth aspect, there is provided a communication method performed by a network device. The method comprises: transmitting, to a terminal device, a second message for triggering channel state information (CSI) report; determining a target CSI type from a first CSI type and a second CSI type based on at least one of the following: a first timing required for CSI computation corresponding to the first CSI type, a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or an uplink timing of the uplink resource carrying the CSI report; and receiving, from the terminal device, a CSI report with the determined target CSI type.

In a ninth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the fifth, sixth, seventh, or eighth aspect.

Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:

FIG. 1 illustrates a trigger of aperiodic CSI report;

FIG. 2A illustrates that user equipment (UE) may provide a valid CSI report;

FIG. 2B illustrates that UE may ignore the scheduling PDCCH;

FIG. 2C illustrates that UE may provide a valid CSI report;

FIG. 3 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

FIG. 4A illustrates AI-CSI processing time;

FIG. 4B illustrates CSI processing time and AI-CSI processing time;

FIG. 5 illustrate examples of configuration and determination of CSI report in accordance with some embodiments of the present disclosure;

FIGS. 6A to 6D illustrate examples of trigger state associated with AI CSI report configuration and non-AI CSI report configuration in accordance with some embodiments of the present disclosure;

FIGS. 7A to 7C illustrate examples of an AI CSI report provided by UE in accordance with some embodiments of the present disclosure;

FIGS. 8A to 8C illustrate examples of a non-AI CSI report provided by UE in accordance with some embodiments of the present disclosure;

FIG. 8D illustrates an example of no CSI report provided by UE in accordance with some embodiments of the present disclosure;

FIG. 9 illustrates a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

FIG. 10 illustrates a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

FIG. 11 illustrates a flowchart of a method implemented at a network device according to some example embodiments of the present disclosure;

FIG. 12 illustrates a flowchart of a method implemented at a network device according to some example embodiments of the present disclosure; and

FIG. 13 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

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

As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.

The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.

The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.

The terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 52.6GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.

The embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator. In some embodiments, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In some embodiments, the first network device may be a first RAT device and the second network device may be a second RAT device. In some embodiments, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In some embodiments, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In some embodiments, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.

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 ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.

In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.

As used herein, the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

FIG. 1 illustrates a trigger of aperiodic CSI report. In FIG. 1, Radio resource control (RRC) signalling from a network device may include a multi-layer structure. In FIG. 1, the first layer structure includes a state list, such as CSI-AperiodicTriggerStateList. The second layer structure includes trigger state (s) , such as CSI-AperiodicTriggerState. The third layer structure includes configurations, such as CSI-ReportConfig. Downlink control information (DCI) from a network device is used to trigger an aperiodic CSI report, wherein a CSI request field indicates CSI-AperiodicTriggerState. The network device utilizes RRC to inform the terminal devices the trigger state list and utilizes DCI to activate the trigger state (s) desired.

Continue to refer to FIG. 1, when the CSI request field comprised in a DCI message triggers a CSI report (s) on physical uplink shared channel (PUSCH) , the UE may provide a valid CSI report for the n-th triggered report,

if the first uplink symbol to carry the corresponding CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref, and

if the first uplink symbol to carry the n-th CSI report including the effect of the timing advance, starts no earlier than at symbbl Z'_ref (n) .

Z_ref is defined as the next uplink symbol with its cyclic prefix (CP) starting T_proc, CSI= (Z) (2048+144) ·k2^-μ·T_c+T_switchafter the end of the last symbol of the physical downlink control channel (PDCCH) triggering the CSI report (s) , and where Z'_ref (n) , is defined as the next uplink symbol with its CP starting T`_proc, CSI= (Z`)(2048+144) ·k2^-μ·T_c after the end of the last symbol in time of the latest of: aperiodic CSI-reference signal (RS) resource for channel measurements, aperiodic CSI-interference measurement (IM) used for interference measurements, and aperiodic non-zero-power (NZP) CSI-RS for interference measurement, when aperiodic CSI-RS is used for channel measurement for the n-th triggered CSI report, and where T_swich is applied only if Z₁ is applied.

Further, T_switch is determined based the following and is applied only if Z₁ is applied. If uplink switching gap is triggered, T_switch equals to the switching gap duration and for the UE configured with higher layer parameter uplinkTxSwitchingOption set to 'dualUL' for uplink carrier aggregation μ_UL=min (μ_{UL, carrier1,} μ_{UL, carrier2}) , otherwise T_switch=0. T_c=1/ (Δf_max·N_f) where Δf_max=480·10³ Hz and N_f=4096, N=T_s/T_c=64.

If the PUSCH indicated by the DCI is overlapping with another physical uplink control channel (PUCCH) or PUSCH, then the CSI report (s) are multiplexed, otherwise the CSI report (s) are transmitted on the PUSCH indicated by the DCI.

When the CSI request field comprised in a DCI message triggers a CSI report (s) on PUSCH, if the first uplink symbol to carry the corresponding CSI report (s) including the effect of the timing advance, starts earlier than at symbol Z_ref,

the UE may ignore the scheduling DCI if no HARQ-ACK or transport block is multiplexed on the PUSCH.

When the CSI request field on a DCI triggers a CSI report (s) on PUSCH, if the first uplink symbol to carry the n-th CSI report including the effect of the timing advance, starts earlier than at symbol Z'_ref (n) ,

the UE may ignore the scheduling DCI if the number of triggered reports is one and no hybrid automatic repeat request-acknowledgement (HARQ-ACK) or transport block is multiplexed on the PUSCH;

otherwise, the UE is not required to update the CSI for the n-th triggered CSI report.

In FIG. 2A, UE may provide a valid CSI report if CSI processing time T_proc, CSI starts earlier than the time which the first uplink (UL) symbol of PUSCH arrives. In FIG. 2B, UE may ignore the scheduling PDCCH if CSI processing time T_proc, CSI starts no earlier than the time which the first UL symbol of PUSCH arrives.

In some embodiments, “earlier than” in this disclosure may be replaced by “no later than” , and “no earlier than” in this disclosure may be replaced by “later than” .

In FIG. 2C, when aperiodic CSI-RS is used as the measurement resource, UE may provide a valid CSI report both CSI processing time T_proc, CSI and aperiodic CSI-RS processing time are less than the time which the first UL symbol of PUSCH arrives. Otherwise, UE may ignore the scheduling PDCCH, or UE may not be required to update the CSI of the triggered CSI report. Otherwise, UE may ignore the scheduling PDCCH, or UE may not be required to update the CSI of the triggered CSI report.

In CSI compression using two-sided model use case, further study potential specification impact related to potential co-existence and fallback mechanisms between AI/ML-based CSI feedback mode and legacy non-AI/ML-based CSI feedback mode.

In CSI compression using two-sided model use case, for network (NW) -side monitoring, further study the necessity, feasibility and potential specification impact to enable performance monitoring using an existing CSI feedback scheme as the reference.

The association between AI/ML scheme and existing CSI feedback scheme for monitoring.

Note: The metric for monitoring and comparison includes intermediate key performance indicator (KPI) and eventual KPI.

Other aspects are not precluded.

The CSI computation time/delay requirement of generating a valid AI/ML-based CSI report is likely to be different from of generating a valid traditional or legacy CSI report. This is because generating an AI/ML-based CSI report involves additional model inference. Specifically,

In case of AI/ML-based CSI compression feedback, for generating a valid AI/ML-based CSI report, UE needs to first calculate the channel (response or eigenvectors) and then obtain the compressed bits through AI/ML model (inference) . For generating a valid legacy CSI report, UE needs to first calculate the channel and then obtain precoding information through traditional mathematical algorithm (s) . Generally speaking, the complexity corresponding to the AI/ML model is different from that corresponding to the traditional mathematical algorithm (s) . One possible reason is that, the AI/ML model (inference) may involve more parameters and more complex operations, occupy more memory, and require higher computational power or capability of UE. Therefore, the times required for them are most likely to be inconsistent.

In case of AI/ML based beam prediction, for generating a valid AI/ML-based beam report, UE needs to first calculate the beam qualities, e.g., layer 1 (L1) -reference signal receiving power (RSRP) , and then obtain the predicted beam and/or predicted beam qualities and/or other predicted information through AI/ML model (inference) . For generating a valid legacy beam report, UE only needs to calculate the beam qualities. Obviously, the times required for them are inconsistent.

Therefore, it is highly possible that a new CSI computation time/delay requirement would be introduced for the AI/ML-based CSI report.

For better descriptions, some terms used herein are listed as below:

AI/ML Model: refers to a data driven algorithm that applies AI/ML techniques to generate a set of outputs based on a set of inputs;

Model: refers to AI/ML, data-driven, data processing model, encoder, decoder, algorithm, functionality, procedure, process, entity, function, feature, feature group, model ID or functionality;

AI/ML-based CSI compression: refers to a process/method where AI/ML model is to compress CSI information into a specific format (e.g., binary bit) information and/or recover the CSI information from the specific format information;

AI/ML-based temporal CSI prediction: refers to a process/method where AL/ML model is to predict CSI information for future time based on historic measurement results of CSI information;

AI/ML-based spatial beam prediction: refers to a process/method where AI/ML model is to predict the information of beams in Set A based on the measurement results of beams in Set B;

AI/ML-based temporal beam prediction: refers to a process/method where AL/ML model is to predict the information of beams in Set A for future time based on historic measurement results of beams in Set B, wherein Set B may be the same as Set A, be a subset of Set A, or be different from Set A;

Predict: refers to prediction, inference, or infer;

CSI information: refers to at least one of CSI-RS resource indicator (CRI) , rank indicator (RI) , precoding matrix indicator (PMI) , layer indicator (LI) , i1, i2channel quality indicator (CQI) , raw channel matrix, or channel eigenvector;

Compressed bits: refers to encoded bits, quantization bits, (AI/ML) CSI, (AI/ML) CSI part 2, (AI/ML) PMI, output CSI, or latent space;

Beam: refers to RS, RS resource, CRI, or synchronization signal and physical broadcast channel (PBCH) block (SSB) resource indicator (SSBRI) ;

Beam ID: refers to CRI and/or SSBRI. Beam quality comprises L1-RSRP and/or L1-signal to interference plus noise ratio (SINR) ;

Parameter: refers to RRC information (element) or (RRC) configuration;

UE capability: refers to UE radio access capability, or UE assistance information (UAI) ;

Non-AI CSI report: refers to CSI report;

AI-CSI-ReportConfig or AI-CSI-ReportConfigId: refers to an example for explanation. It may be represented by CSI-ReportConfig or CSI-ReportConfigId that is configured for at least one of AI/ML, model or life-cycle management (LCM) procedure;

parameters Z_ref, Z’_ref, Z_ref-AI, Z’_ref-AI: refers to timing required for CSI computation for a triggered CSI report.

■ Z_ref: refers to the next uplink symbol with its CP starting after T_proc, CSI the end of the last symbol of the PDCCH triggering the CSI report (s) .

■ Z’_ref: refers to the next uplink symbol with its CP starting T’_proc, CSI after the end of the last symbol in time of the latest of: aperiodic CSI-RS resource for channel measurements, aperiodic CSI-IM used for interference measurements, and aperiodic NZP CSI-RS for interference measurement, when aperiodic CSI-RS is used for channel measurement for the n-th triggered CSI report.

■ Z_ref-AI: refers to the next uplink symbol with its CP starting after T_{proc, CSI-AI} the end of the last symbol of the PDCCH triggering the CSI report (s) .

■ Z’_ref-AI: refers to the next uplink symbol with its CP starting T’_{proc, CSI-AI} after the end of the last symbol in time of the latest of: aperiodic CSI-RS resource for channel measurements, aperiodic CSI-IM used for interference measurements, and aperiodic NZP CSI-RS for interference measurement, when aperiodic CSI-RS is used for channel measurement for the n-th triggered CSI report.

◆ T_{proc, CSI-AI} or T’_{proc, CSI-AI}: refers to an example for explanation, it can be represented by other parameter having the same meaning or function.

LCM procedure: refers to at least one of model inference, model training, model monitoring, model activation, model deactivation, model selection, model switching, or model update.

Model inference: refers to a process of using a trained AI/ML model to produce a set of outputs based on a set of inputs.

Model training: refers to a process to train an AI/ML Model (by learning the input/output relationship) in a data driven manner and obtain the trained AI/ML Model for inference.

Model monitoring: refers to a procedure that monitors the inference performance of the AI/ML model.

Model switching: refers to deactivate a currently active AI/ML model and activating a different AI/ML model for a specific AI/ML-enabled feature.

Model selection: refers to a process of selecting an AI/ML model for activation among multiple models for the same AI/ML-enabled feature.

Model update: refers to a process of updating the model parameters and/or model structure of a model.

Model activation/deactivation: refers to enable/disable an AI/ML model for a specific AI/ML-enabled feature.

In the present disclosure,

terms of “ML model” , “AI model” , “ML function” , “AI function” and “algorithm” may be used interchangeably;

terms of “ID” , “index” , “identification” and “identifier” may be used interchangeably; terms “select” , “switch” , “choose” , “choice” and “selection” may be used interchangeably;

terms “comprise” , “include” and “indicate” may be used interchangeably;

terms “corresponding to” , “associated with” , “mapping to/with” and “for” may be used interchangeably;

it is also possible or reasonable to replace “AI CSI report” with “non-AI CSI report” and replace “non-AI CSI report” with “AI CSI report” .

Principles and implementations of the present disclosure will be described in detail below with reference to the figures.

In the present disclosure, a beam may correspond to a CSI-RS, a synchronization signal and physical broadcast channel (PBCH) block (SSB) , a CSI-RS resource, or an SSB resource. Accordingly, a beam identity (ID) may be a CSI-RS resource indicator (CRI) , an SSB resource indicator (SSBRI) , or a RS ID. It also should be understood that in fact, a beam refers to a resource that enables a spatially directional communication, and thus may be identified by other suitable parameter in other embodiments. In present disclosure is not limited in this regard.

It is noted that when the term “aset of” is used, it may mean one or more elements/items, which may be replaced by terms of “at least one” , “agroup of” or “alist of” . For example, “aset of Xs” means “at least one X” or “one or more Xs” .

Example Environment

FIG. 3 illustrates a schematic diagram of an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 300, a plurality of communication devices, including a terminal device 310 and a network device 320, can communicate with each other.

Further, multiple input multiple output (MIMO) is supported in the communication environment 300, such that the network device 320 and the terminal device 310 may communicate with each other via different beams to enable a directional communication.

In the example of FIG. 3, in some embodiments, the terminal device 310 may include a terminal device and the network device 320 may include a network device serving the terminal device. In this specific example embodiment, a link from the terminal device 310 to the network device 320 is referred to as uplink, while a link from the network device 320 to the terminal device 310 is referred to as a downlink.

In downlink, the network device 320 is a transmitting (TX) device (or a transmitter) and the terminal device 310 is a receiving (RX) device (or a receiver) , and the network device 320 may transmit downlink transmission to the terminal device 310 via one or more beams. As illustrated in FIG. 3, the network device 320 transmits downlink transmission to the terminal device 310 via the one or more of beams 340-1, 340-2 and 340-3. For purpose of discussion, the beams 340-1 to 340-3 are collectively or individually referred to as beam 340.

Correspondingly, in uplink, the network device 320 is an RX device (or a receiver) and the terminal device 310 is a TX device (or a transmitter) , and the terminal device 310 may transmit uplink transmission to the network device 320 via one or more beams. As illustrated in FIG. 3, the terminal device 310 transmits uplink transmission to the network device 320 via the beams 330-1 to 330-3. For purpose of discussion, the beams 330-1 to 330-3 are collectively or individually referred to as beam 330.

In some embodiments, one or more models may be deployed at the terminal device 310 and/or the network device 320. As illustrated in FIG. 3, the model 315 may be deployed at the terminal device 310. Alternatively, or in addition, the model 325 may be deployed at the terminal device 310. In case that both model 315 and model 325 are deployed, the model 315 and model 325 may be operated collaboratively with each other.

Additionally, a hybrid model monitoring is supported in the communication environment 300. Specifically, the terminal device 310 monitors the performance metric (s) while the network device 320 makes decision (s) on model-related operations, such as, selections, activation, deactivation, switching, fallback and so on.

It is to be understood that the number of devices and their connections shown in FIG. 3 are only for the purpose of illustration without suggesting any limitation. The communication environment 300 may include any suitable number of devices configured to implementing example embodiments of the present disclosure.

In some embodiments, the terminal device 310 and the network device 320 may communicate with each other via a channel such as a wireless communication channel on an air interface (e.g., Uu interface) . The wireless communication channel may comprise 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 channels are also feasible.

The communications in the communication environment 300 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (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) and the like. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

As discussed above, if new CSI computation time/delay requirement for AI CSI report is considered, new Z_ref and/or Z’_ref for AI CSI report may be introduced, e.g., Z_ref-AI in Fig. 4A. When the UL timing (i.e., the first UL symbol to carry the triggered AI CSI report including the effect of the timing advance) starts no earlier than the new Z_ref and/or Z’_ref (e.g., Z_ref-AI) , UE shall provide a valid AI CSI report. However, when the UL timing starts earlier than the new Z_ref and/or Z’_ref (e.g., Z_ref-AI) , with reference to FIG. 4B, UE may omit the scheduling DCI or not update the CSI for the AI CSI report. This will result in wastage of signaling and CSI measurement resource.

In above case (i.e., when the UL timing starts earlier than the new Zref and/or Z’ref) , UE may provide a non-AI CSI report instead of the AI CSI report if the UL timing starts no earlier than the Z_ref and/or Z’_ref (corresponding to the non-AI CSI report) . In other words, a flexible CSI report based on CSI computation time/delay requirement (i.e., timing required for CSI computation) may be considered. In this way, unnecessary signaling and CSI measurement resource will be saved.

Based on the above, the first issue may be: after UE receives a DCI that is used to trigger CSI report, how does UE determine (configuration about) an AI CSI report and (configuration about) a non-AI CSI report based on the received DCI? Specifically, (the ‘CSI request’ field in) the DCI indicates a trigger state. Thus, this issue may also be, how does UE determine an AI CSI report and a non-AI CSI report based on the indicated trigger state?

The second issue may be: UE needs only to transmit/provide one CSI report to network, i.e., the target CSI report. Therefore, a target CSI report needs to be determined (or selected) from the determined AI CSI report and non-AI CSI report and then be generated and transmitted/provided to NW. Thus, the issue is that, how does UE determine a target CSI report (to be transmitted/provided to network) from the AI CSI report and non-AI CSI report?

Example Processes

It is to be understood that the operations at the terminal device 310 and the network device 320 should be coordinated. In other words, the network device 320 and the terminal device 310 should have common understanding about configurations, parameters and so on. Such common understanding may be implemented by any suitable interactions between the network device 320 and the terminal device 310 or both the network device 320 and the terminal device 310 applying the same rule/policy. In the following, although some operations are described from a perspective of the terminal device 310, it is to be understood that the corresponding operations should be performed by the network device 320. Similarly, although some operations are described from a perspective of the network device 320, it is to be understood that the corresponding operations should be performed by the terminal device 310. Merely for brevity, some of the same or similar contents are omitted here.

In addition, in the following description, some interactions are performed among the terminal device 310 and the network device 320 (such as, exchanging configuration (s) and so on) . It is to be understood that the interactions may be implemented either in one single signaling/message/configuration or multiple signaling/messages/configurations, including system information, RRC message, downlink control information (DCI) message, uplink control information (UCI) message, media access control information (MAC CE) and so on. The present disclosure is not limited in this regard.

Reference is made to FIG. 5, which illustrates a signaling flow 500 of configuration and determination of CSI report in accordance with some embodiments of the present disclosure. For the purposes of discussion, the signaling flow 500 will be discussed with reference to FIG. 3, for example, by using the terminal device 310 and the network device 320.

The signaling flow 500A includes a procedure 510, a procedure 520, a procedure 530 and a procedure 540.

It should be understood that although feature (s) /operation (s) in different procedures (i.e., procedures 510, 520, 530 and 540) are discussed in specific example embodiments separately, unless clearly indicated to the contrary, these feature (s) /operation (s) described in different example embodiments may be used in any suitable combination.

In some embodiments, the terminal device 310 receives configuration information from the network device 320, where the configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type. For example, in FIG. 5, UE receives a RRC 522 during procedure 520.

In some embodiments, the trigger state may be one of the following: an aperiodic trigger state, or a semi-persistent trigger state.

In some embodiments, the trigger state may be one of the following:

CSI-AperiodicTriggerState,

AI/ML-CSI-AperiodicTriggerState,

CSI-SemiPersistentOnPUSCH-TriggerState,

AI/ML-CSI-SemiPersistentOnPUSCH-TriggerState.

In some embodiments, the terminal device 310 may receive 532 a first message for triggering CSI report from the network device 320, the first message indicating the trigger state comprised in the list of trigger states.

In some embodiments, the first message may be MAC CE or DCI. For example, the UE may receive a MAC CE/DCI message during procedure 530.

In some embodiments, the terminal device 310 may transmit 542 a CSI report the network device 320, where the CSI report is determined based on the trigger state indicated by the first message. Further, the CSI report is associated with the first CSI type or the second CSI type.

In FIG. 5, during the procedure 540, UE determines 544 a target type of the CSI report and generates 545 the CSI report. Then, the UE may transmit 542 the CSI report to the network. Further embodiments will be described with reference to FIGS. 6A to 6D and FIGS. 7A to 7C.

In some embodiments, the CSI with the first CSI type may comprise non-AI CSI, and the CSI with the second CSI type may comprise AI-related CSI.

FIGS. 6A to 6C illustrate examples of trigger state associated with AI CSI report configuration and non-AI CSI report configuration in accordance with some embodiments of the present disclosure.

In some embodiments, the list of trigger states may comprise a first trigger state being associated with a first set of CSI report configurations and a second set of second CSI report configurations. Further, the first CSI report configuration may be associated with CSI with a first CSI type and the second CSI report configuration may be associated with CSI with a second CSI type. In FIG. 6A, the trigger state may be associated with AI CSI report config and non-AI CSI report config.

Further, if the first trigger state is indicated in the following MAC CE/DCI, it means that the terminal device 310 is triggered with an AI CSI report (s) and a non-AI CSI report (s) on PUSCH.

In some embodiments, UE may be provided by the network with at least one list of trigger states, where each trigger state may be associated with at least one AI CSI report config and at least one non-AI CSI report config, or at least one list of AI CSI report configs and at least one list of non-AI CSI report configs.

Further, in some embodiments, the non-AI CSI report may be indicated by such as CSI-ReportConfig and the AI CSI report is indicated by such as AI/ML-CSI-ReportConfig.

In some embodiments, the first number of first CSI report configurations comprised in the first set may be the same as the second number of second CSI report configurations comprised in the second set.

For example, for each trigger state, the number of associated AI CSI reports may be the same as the number of associated non-AI CSI reports. And the AI CSI report may be one-to-one associated with or corresponding to the non-AI CSI report.

In some embodiments, if a configuration parameter is absent in a first CSI report configuration, the terminal device 310 may determine the configuration parameter to be a corresponding configuration parameter comprised in a second CSI report configuration corresponding to the first CSI report configuration.

In some embodiments, if a configuration parameter is absent in a second CSI report configuration, the terminal device 310 may determine the configuration parameter to be a corresponding configuration parameter comprised in a first CSI report configuration corresponding to the second CSI report configuration.

As an example, the CSI-ResourceConfig (i.e., CSI resource) may be not configured in the CSI-ReportConfig or AI/ML-CSI-ReportConfig. If the CSI-ResourceConfig is configured in the CSI-ReportConfig (or AI/ML-CSI-ReportConfig) , i.e., if a non-AI CSI report config (or AI CSI report config) does not have a corresponding CSI resource, UE may determine the CSI resource corresponding to the non-AI CSI report config (or AI CSI report config) based on CSI resource corresponding to AI CSI report config (or non-AI CSI report config) associated with the non-AI CSI report config (or AI CSI report config) .

As another example, in addition to the CSI resource, any information (or parameter, configuration) corresponding to the non-AI CSI report config (or AI CSI report config) may be determined based on the associated AI CSI report config (or non-AI CSI report config) .

In some embodiments, for CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, CapabilityIndex, UE is configured by higher layers with N≥1 CSI-ReportConfig Reporting Settings, N1≥1 AI-CSI-ReportConfig Reporting Settings, M≥1 CSI-ResourceConfig Resource Settings, and one or two list (s) of trigger states (given by the higher layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList) . Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs indicating the Resource Set IDs for channel and optionally for interference, or a list of associated AI-CSI-ReportConfigs indicating the Resource Set IDs for channel and optionally for interference and a list of associated CSI-ReportConfigs (indicating the Resource Set IDs for channel and optionally for interference) .

An example IE is illustrated as below:

In some embodiments, the list of trigger states further comprises a second trigger state being associated with a third set of first CSI report configurations, wherein each first CSI report configuration comprised in the third set is associated with a second CSI report configuration. For example, in FIG. 6B, the AI CSI report config associated with the trigger state is associated with a non-AI CSI report config.

Further, if the second trigger state is indicated in the following MAC CE/DCI, it means that the terminal device 310 is triggered with a non-AI CSI report (s) on PUSCH.

In some embodiments, the list of trigger states further comprises a third trigger state being associated with a fourth set of second CSI report configurations, wherein each second CSI report configuration comprised in the fourth set is associated with a first CSI report configuration. For example, in FIG. 6C, the non-AI CSI report config associated with the trigger state is associated with an AI CSI report config.

Further, if the third trigger state is indicated in the following MAC CE/DCI, it means that the terminal device 310 is triggered with an AI CSI report (s) on PUSCH.

In some embodiments, UE is provided by the network with at least one list of trigger states, where each trigger state may be associated with at least one AI CSI report config (or non-AI CSI report config) . Each AI CSI report config (or non-AI CSI report config) may be associated with at least one non-AI CSI report config (or AI CSI report config) , or at least one list of non-AI CSI report configs (or AI CSI report configs) .

In some embodiments, any information (or parameter, configuration) corresponding to the non-AI CSI report (or AI CSI report) may be determined based on the associated AI CSI report (or non-AI CSI report) .

An example IE is illustrated as below :

In some embodiments, the list of trigger states further comprises a fourth trigger state being associated with a fifth set of third CSI report configurations, wherein each third CSI report configuration is associated with a first set of parameters and a second set of parameters, wherein the first set of parameters is associated with CSI with a first CSI type and the second set of parameters is associated with CSI with a second CSI type. For example, in FIG. 6D, the CSI report config associated with the trigger state is associated with a first configuration about non-AI CSI report config and a second configuration about AI CSI report.

Further, if the fourth trigger state is indicated in the following MAC CE/DCI, it means that the terminal device 310 is triggered with an AI CSI report (s) and a non-AI CSI report (s) on PUSCH.

In some embodiments, UE is provided by network with at least one list of trigger states, each trigger state is associated with at least one AI CSI report config (or non-AI CSI report config) . Each AI CSI report config (or non-AI CSI report config) may be associated with at least one first configuration and at least one second configuration, or at least one set of first configurations and at least one set of second configurations.

In some embodiments, the first configuration may be applied for (or associated with) the non-AI CSI report, and the second configuration may be applied for the AI CSI report.

In some embodiments, the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI. Alternatively, or in addition, the CSI with the first CSI type comprises information about the measured beam, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam. Alternatively, or in addition, the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits.

For example, the first configuration may indicate a first type of CSI (to be reported) , and the second configuration may indicate a second type of CSI (to be reported) . E. g., the first configuration or the second configuration may be reportQuantity. Specifically,

in case of AI/ML-based CSI compression, the first type of CSI may comprise ‘PMI’ , and the second type of CSI may comprise ‘compressed bits’ ;

in case of AI/ML-based temporal CSI prediction, the first type of CSI may comprise ‘measured CSI’ , and the second type of CSI may comprise at least one of ‘predicted CSI’ , ‘measured CSI’ or ‘other information (e.g., CSI application/dwelling time) ’ ;

in case of AI/ML-based temporal CSI prediction, the first type of CSI may comprise ‘measured CSI’ , and the second type of CSI may comprise at least one of ‘predicted CSI’ , ‘measured CSI’ or ‘other information (e.g., CSI application/dwelling time) ’ .

In some embodiments, the CSI with the first CSI type is determined from a first set of reference signal (RS) resources, and the CSI with the second CSI type is determined from a second set of RS resources.

In some embodiments, the second set of RS resources is the same as the first set of RS resources, a subset of the first set of RS resources, or different from the first set of RS resources.

In some embodiments, the second set of RS resources may be the same with the first set of RS resources or may be different with the first set of RS resources. Alternatively, or in addition, the second set of RS resources may be a subset of the first set of RS resources.

In some embodiments, the first set of RS resources may comprise at least one RS resource that is configured as beam measurement resource, and the second set of RS resources may comprise at least one RS resource that is configured as beam prediction resource.

For example, the first configuration may indicate that the reported beam (s) come from a first set of RS resources, the second configuration may indicate that the reported beam (s) come from a second set of RS resources.

In case of AI/ML-based spatial beam prediction, the first set of RS resources may comprise at least one RS resource that is configured as beam measurement resource (e.g., CMR, IMR) , and the second set of RS resources may comprise at least one RS resource that is configured as beam prediction resource. In other words, the first set of RS resource corresponds to the Set B, and the second set of RS resource corresponds to the Set A.

An example IE is illustrated as below:

In some embodiments, the terminal device 310 transmits, to the network device 320, capability information indicating at least one of the following: whether the terminal device supports a co-existence of a non- (artificial intelligence) AI (non-AI) CSI mode and an AI CSI mode; whether the terminal device supports a selection between a non-AI CSI mode and an AI CSI mode; whether the terminal device supports a co-existence of a non-AI CSI report and an AI CSI report; or whether the terminal device supports a selection between a non-AI CSI report and an AI CSI report.

Continue to refer to FIG. 5, in procedure 510, UE may provide one or multiple UE capabilities to the network, which are used to indicate at least one of the following:

Whether UE supports the co-existence of non-AI mode/state and AI mode/state;

Whether UE support the selection/choice between non-AI CSI mode/state and AI CSI mode/state;

Whether UE supports the co-existence of non-AI CSI report and AI CSI report;

Whether UE support the selection/choice between non-AI CSI report and AI CSI report.

In some embodiments, the terminal device 310 receives from the network device at least one of the following: a first indication used for enabling or disabling a co-existence of a non-AI CSI mode and an AI CSI mode, a second indication used for enabling or disabling a co-existence of a non-AI CSI report and an AI CSI report, a third indication used for enabling or disabling a selection between a non-AI CSI mode and an AI CSI mode, or a fourth indication used for enabling or disabling a selection between a non-AI CSI report and an AI CSI report.

For example, UE may be provided by network with one or multiple enable parameters, which are used to indicate at least one of the following:

Enable the selection/choice between non-AI CSI mode/state and AI CSI mode/state.

Enable the selection/choice between non-AI CSI report and AI CSI report.

In other words, the above UE capabilities and enable parameters may be precondition of the UE behaviors in the subsequent procedures.

In some embodiments, the terminal device 310 receives, from a network device 320, a second message for triggering channel state information (CSI) report. Then, the terminal device 310 determines a target CSI type from a first CSI type and a second CSI type based on at least one of the following: a first timing required for CSI computation corresponding to the first CSI type, a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or an uplink timing of the uplink resource carrying the CSI report.

In some embodiments, the second message indicates a trigger state associated with at least one of the following: a first CSI type, a second CSI type, or both a first CSI type and a second CSI type.

In some embodiments, the terminal device 310 transmits, to the network device 320, a CSI report with the determined target CSI type.

As an example, UE may determine a target CSI report (to be transmitted/provided to network) from the AI CSI report and the non-AI CSI report based on timing required for CSI computation corresponding to the AI CSI report and timing required for CSI computation corresponding to the non-AI CSI report and the other UE behaviors besides determination of the target CSI report.

In this way, UE may know how to determine a target CSI report (to be transmitted/provided to network) from the AI CSI report and the non-AI CSI report. Meanwhile, network may know whether the target CSI report transmitted/provided by UE is the AI CSI report or the non-AI CSI report.

In some embodiments, the first timing comprises at least one of the following: a first next uplink symbol after a first processing duration from an end of the last symbol of the second message, or a second next uplink symbol after a second processing duration from an end of the last symbol of the latest CSI reference signal (RS) resource for the CSI report, and wherein the second timing comprises at least one of the following: a third next uplink symbol after a third processing duration from an end of the last symbol of the second message, or a fourth next uplink symbol after a fourth processing duration from an end of the last symbol of the latest CSI RS resource for the CSI report.

For example, UE may determine a target CSI report (to be transmitted/provided to network) from the AI CSI report and the non-AI CSI report based on at least one of the following:

Timing required for CSI computation corresponding to the AI CSI report.

Timing required for CSI computation corresponding to the non-AI CSI report.

UL timing of the PUSCH resource carrying the target CSI report.

Predefined condition.

In some embodiments, the timing required for CSI computation corresponding to the non-AI CSI report comprises at least one of: Z_ref or Z’_ref, it may be referred to as ‘non-AI timing’ for short.

In some embodiments, the timing required for CSI computation corresponding to the AI CSI report comprises at least one of: Z_ref-AI or Z’_ref-AI, it may be referred to as ‘AI timing’ for short.

In some embodiments, the UL timing of the PUSCH resource carrying the target CSI report (referred to as ‘UL timing’ for short) means the first uplink symbol to carry the corresponding CSI report (s) (i.e., the target CSI report) including the effect of the timing advance.

In some embodiments, the terminal device 310 determines the target CSI type to be the second CSI type if at least one of the following: the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing, or the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing and the first timing.

In some embodiments, the terminal device 310 determines the target CSI type to be the first CSI type if: the uplink timing of the uplink resource carrying the CSI report starts no earlier than the first timing and earlier than the second timing.

For example, the predefined condition comprises at least one of the following:

Condition-1: The UL timing starts no earlier than the AI timing,

Condition-1*: The UL timing starts no earlier than the AI timing and the non-AI timing, or

Condition-2: The UL timing starts earlier than the AI timing and no earlier than the non-AI timing.

FIGS. 7A to 7C illustrates examples of an AI CSI report provided by UE in accordance with some embodiments of the present disclosure.

As an example, when UE is triggered with an AI CSI report (s) by network through a DCI message, if Condition-1 is fulfilled, i.e., the UL timing starts no earlier than the AI timing, UE determines the AI CSI report as the target CSI report, i.e., UE shall generate and provide a valid AI CSI report.

Alternatively, or in addition, when UE is triggered with an AI CSI report (s) by network through a DCI message, if the (n-th) AI CSI report (s) is associated with a non-AI CSI report (s) , and if Condition-1*is fulfilled, UE determines the AI CSI report as the target CSI report.

With reference to FIG. 7A, when the CSI request field on a DCI triggers an AI CSI report (s) on PUSCH, the UE shall provide a valid AI CSI report for the n-th triggered report,

if the first uplink symbol to carry the corresponding (AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref-AI, and

if the first uplink symbol to carry the n-th (AI) CSI report including the effect of the timing advance, starts no earlier than at symbol Z'_ref-AI (n) .

As another example, when UE is triggered with a non-AI CSI report (s) by network through a DCI message, if the (n-th) non-AI CSI report (s) is associated with an AI CSI report (s) , and if Condition-1 (or Condition-1*) is fulfilled, i.e., the UL timing starts no earlier than the AI timing, UE determines the associated AI CSI report as the target CSI report, i.e., UE shall generate and provide a valid (associated) AI CSI report.

With reference to FIG. 7B, when the CSI request field on a DCI triggers a non-AI CSI report (s) on PUSCH, the UE shall provide a valid (associated) AI CSI report for the n-th triggered report,

if the (n-th) non-AI CSI report (s) is associated with an AI CSI report (s) ,

if the first uplink symbol to carry the corresponding (non-AI or/and associated AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref-AI, and

if the first uplink symbol to carry the n-th (non-AI or/and associated AI) CSI report including the effect of the timing advance, starts no earlier than at symbol Z'_ref-AI (n) .

As another example, when UE is triggered with an AI CSI report (s) and a non-AI CSI report (s) by network through a DCI message, if Condition-1 (or Condition-1*) is fulfilled, i.e., the UL timing starts no earlier than the AI timing, UE determines the AI CSI report as the target CSI report, i.e., UE shall generate and provide a valid AI CSI report.

With reference to FIG. 7C, when the CSI request field on a DCI triggers an AI CSI report (s) and a non-AI CSI report (s) on PUSCH, the UE shall provide a valid AI CSI report for the n-th triggered report,

if the first uplink symbol to carry the corresponding (AI and/or non-AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref-AI, and

if the first uplink symbol to carry the n-th (AI and/or non-AI) CSI report including the effect of the timing advance, starts no earlier than at symbol Z'_ref-AI (n) .

FIGS. 8A to 8C illustrate examples of a non-AI CSI report provided by UE in accordance with some embodiments of the present disclosure.

As an example, when UE is triggered with an AI CSI report (s) by network through a DCI message, if the (n-th) AI CSI report (s) is associated with a non-AI CSI report (s) , if Condition-2 is fulfilled, i.e., the UL timing starts earlier than the AI timing and not earlier than the non-AI timing, UE determines the associated non-AI CSI report as the target CSI report, i.e., UE shall generate and provide a valid (associated) non-AI CSI report.

With reference to FIG. 8A, when the CSI request field on a DCI triggers an AI CSI report (s) on PUSCH, the UE shall provide a valid (associated) non-AI CSI report for the n-th triggered report,

if the (n-th) AI CSI report (s) is associated with a non-AI CSI report (s) ,

if the first uplink symbol to carry the corresponding (AI or/and associated non-AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref-AI, and/or if the first uplink symbol to carry the n-th (AI or/and associated non-AI) CSI report including the effect of the timing advance, starts earlier than at symbol Z'_ref-AI (n) , and

if the first uplink symbol to carry the corresponding (AI or/and associated non-AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref, and/or if the first uplink symbol to carry the n-th (AI or/and associated non-AI) CSI report including the effect of the timing advance, starts no earlier than at symbol Z'_ref (n) .

As another example, when UE is triggered with a non-AI CSI report (s) by network through a DCI message, if the (n-th) non-AI CSI report (s) is associated with an AI CSI report (s) , if Condition-2 is fulfilled, i.e., the UL timing starts earlier than the AI timing and not earlier than the non-AI timing, UE determines the non-AI CSI report as the target CSI report, i.e., UE shall generate and provide a valid non-AI CSI report.

With reference to FIG. 8B, when the CSI request field on a DCI message triggers a non-AI CSI report (s) on PUSCH, the UE shall provide a valid non-AI CSI report for the n-th triggered report,

if the (n-th) non-AI CSI report (s) is associated with an AI CSI report (s) ,

if the first uplink symbol to carry the corresponding (non-AI or/and associated AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref-AI, and/or if the first uplink symbol to carry the n-th (non-AI or/and associated AI) CSI report including the effect of the timing advance, starts earlier than at symbol Z'_ref-AI (n) , and

if the first uplink symbol to carry the corresponding (non-AI or/and associated AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref, and/or if the first uplink symbol to carry the n-th (non-AI or/and associated AI) CSI report including the effect of the timing advance, starts no earlier than at symbol Z'_ref (n) .

As another example, when UE is triggered with an AI CSI report (s) and a non-AI CSI report (s) by network through a DCI message, if Condition-2 is fulfilled, i.e., the UL timing starts earlier than the AI timing and not earlier than the non-AI timing, UE determines the non-AI CSI report as the target CSI report, i.e., UE shall generate and provide a valid non-AI CSI report.

With reference to FIG. 8C, when the CSI request field in a DCI message triggers an AI CSI report (s) and a non-AI CSI report (s) on PUSCH, the UE shall provide a valid non-AI CSI report for the n-th triggered report,

if the first uplink symbol to carry the corresponding (AI or/and non-AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref-AI, and/or if the first uplink symbol to carry the n-th (AI or/and non-AI) CSI report including the effect of the timing advance, starts earlier than at symbol Z'_ref-AI (n) , and

if the first uplink symbol to carry the corresponding (AI or/and non-AI) CSI report (s) including the effect of the timing advance, starts no earlier than at symbol Z_ref, and/or if the first uplink symbol to carry the n-th (AI or/and non-AI) CSI report including the effect of the timing advance, starts no earlier than at symbol Z'_ref (n) .

In some embodiments, if at least one of the following: the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing, or the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing and the second timing, the terminal device 310 performs at least one of the following: ignoring the second message; disabling to update CSI associated with at least one of the following: the first CSI type or the second CSI type; or disabling to provide a valid CSI report and updating CSI associated with at least one of the following: the first CSI type or the second CSI type.

As an example, in FIG. 8D, the predefined condition further comprises,

Condition-3: The UL timing starts earlier than the non-AI timing.

Condition-3*: The UL timing starts earlier than the non-AI timing and the AI timing.

Condition-4: The UL timing starts earlier than the AI timing.

In some embodiments, when Condition-3 (or Condition-3*) is fulfilled, UE may ignore the scheduling DCI.

In some embodiments, when Condition-4 is fulfilled, UE may transmit the non-AI CSI report.

Alternatively, or in addition, UE is not required to update the CSI for the triggered AI and/or non-AI CSI report, e.g., only not update AI-CSI, only not update CSI, not update both AI CSI and non-AI CSI.

Alternatively, or in addition, although UE does not provide a valid AI or non-AI CSI report, UE may update the CSI for the triggered AI and/or non-AI CSI report, e.g., only update AI-CSI, only update CSI, update both AI CSI and non-AI CSI.

In some embodiments, the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI. Alternatively, or in addition, the CSI with the first CSI type comprises information about the measured beam, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam. Alternatively, or in addition, the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits. Alternatively, or in addition, the CSI with the first CSI type comprises non- (artificial intelligence) AI (non-AI) CSI, and the CSI with the second CSI type comprises AI-related CSI.

As an example, when the CSI request field on a DCI triggers an AI CSI report (s) or/and a non-AI CSI report (s) on PUSCH, if the first uplink symbol to carry the corresponding AI CSI report (s) or/and non-AI CSI report (s) including the effect of the timing advance, starts earlier than at symbol Z_ref (and starts earlier than at symbol Z_ref-AI) , the UE may ignore the scheduling DCI if no HARQ-ACK or transport block is multiplexed on the PUSCH.

As another example, when the CSI request field on a DCI triggers an AI CSI report (s) or/and a non-AI CSI report (s) on PUSCH, if the first uplink symbol to carry the n-th AI CSI report and/or non-AI CSI report including the effect of the timing advance, starts earlier than at symbol Z'_ref (n) (and starts earlier than at symbol Z'ref-AI (n) ) , the UE may ignore the scheduling DCI if the number of triggered reports is one and no HARQ-ACK or transport block is multiplexed on the PUSCH. Otherwise, the UE is not required to update the CSI for the n-th triggered CSI report.

In some embodiments, the second timing is determined based on the first timing and an offset timing.

As an example, the Z_ref-AI or Z’_ref-AI may be determined based on at least one of the time required for CSI computation corresponding to the non-AI CSI report and/or an offset.

In this way, UE or network may know how to determine the Z_ref-AI or Z’_ref-AI.

In some embodiments, the Z_ref-AI or Z’_ref-AI is determined based on the time required for CSI computation corresponding to the AI CSI report, i.e., T_{proc, AI-CSI} and T’_{proc, AI-CSI}, which may be determined based on at least one of the time required for CSI computation corresponding to the non-AI CSI report (i.e., T_proc, CSI and T’_proc, CSI) or a offset, in other words, it may be determined based on the following formulas:
T_{proc, AI-CSI}= (Z) (2048+144) ·k2^-μ·T_C+T_switch+offset,
T′_{proc, AI-CSI}= (Z′) (2048+144) ·k2^-μ·T_C+offset.

Further, T_switch is determined based the following and is applied only if Z₁ is applied. If uplink switching gap is triggered, T_switch equals to the switching gap duration and for the UE configured with higher layer parameter uplinkTxSwitchingOption set to 'dualUL' for uplink carrier aggregation μ_UL=min (μ_{UL, carrier1,} μ_{UL, carrier2}) , otherwise T_switch=0. T_c=1/ (Δf_max·N_f) where Δf_max=480·10³ Hz and N_f=4096, N=T_s/T_c=64. In some embodiments, UE may be provided with the offset by network through an RRC signaling, MAC CE or DCI.

In some embodiments, the offset may serve as a UE capability, which may be reported by UE to NW.

In some embodiments, the offset timing is defined as a default value, determined by the network device, or reported by the terminal device.

In some scenarios, especially for the AI CSI report transmitted by UE, network first needs to recover CSI information from the transmitted CSI report, which is different from the non-AI CSI report. Thus, network needs to know how to determine if recovering CSI information is needed.

In some embodiments, network may determine whether to recover CSI information from the target CSI report based on timing required for CSI computation corresponding to the AI CSI report and timing required for CSI computation corresponding to the non-AI CSI report.

In this way, for the target CSI report transmitted/provided by UE, network may determine whether to perform the following procedure: recover CSI information based on the compressed bits included in the target CSI report based on AI/ML model.

As an example, network may whether to recover CSI information from the target CSI report based on at least one of the following:

Timing required for CSI computation corresponding to the AI CSI report.

Timing required for CSI computation corresponding to the non-AI CSI report.

UL timing of the PUSCH resource carrying the target CSI report.

Predefined condition.

In the examples of FIG. 7A to 7C, network needs to recover CSI information.

In the examples of FIG. 8A to 8C, network doesn’t need to recover CSI information.

Example Methods

FIG. 9 illustrates a flowchart of a communication method 900 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the terminal device 310 in FIG. 3.

At block 910, the terminal device 310 receives, from a network device 320, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type.

At block 920, the terminal device 310 receives a first message for triggering CSI report from the network device 320, the first message indicating the trigger state comprised in the list of trigger states.

At block 930, the terminal device 310 transmits, to the network device 320, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.

In some example embodiments, the list of trigger states comprising at least one of the following: a first trigger state being associated with a first set of first channel state information (CSI) report configurations and a second set of second CSI report configurations, wherein the first CSI report configuration is associated with CSI with a first CSI type and the second CSI report configuration is associated with CSI with a second CSI type, a second trigger state being associated with a third set of first CSI report configurations, wherein each first CSI report configuration comprised in the third set is associated with a second CSI report configuration, a third trigger state being associated with a fourth set of second CSI report configurations, wherein each second CSI report configuration comprised in the fourth set is associated with a first CSI report configuration, a fourth trigger state being associated with a fifth set of third CSI report configurations, wherein each third CSI report configuration is associated with a first set of parameters and a second set of parameters, wherein the first set of parameters is associated with CSI with a first CSI type and the second set of parameters is associated with CSI with a second CSI type.

In some example embodiments, the first number of first CSI report configurations comprised in the first set is the same as the second number of second CSI report configurations comprised in the second set.

In some example embodiments, the terminal device 310, if a configuration parameter is absent in a first CSI report configuration, determines the configuration parameter to be a corresponding configuration parameter comprised in a second CSI report configuration corresponding to the first CSI report configuration, and if a configuration parameter is absent in a second CSI report configuration, determine the configuration parameter to be a corresponding configuration parameter comprised in a first CSI report configuration corresponding to the second CSI report configuration.

In some example embodiments, the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI, the CSI with the first CSI type comprises information about the measured beam, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam, the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits, or the CSI with the first CSI type comprises non-(artificial intelligence) AI (non-AI) CSI, and the CSI with the second CSI type comprises AI-related CSI.

In some example embodiments, the CSI with the first CSI type is determined from a first set of reference signal (RS) resources, and the CSI with the second CSI type is determined from a second set of RS resources.

In some example embodiments, the first set of RS resources may comprise at least one RS resource that is configured as beam measurement resource, and the second set of RS resources may comprise at least one RS resource that is configured as beam prediction resource.

In some example embodiments, the trigger state is one of the following: an aperiodic trigger state, or a semi-persistent trigger state.

In some example embodiments, the terminal device 310 transmits, to the network device 320, capability information indicating at least one of the following: whether the terminal device 310 supports a co-existence of a non- (artificial intelligence) AI (non-AI) CSI mode and an AI CSI mode; whether the terminal device 310 supports a selection between a non-AI CSI mode and an AI CSI mode; whether the terminal device supports a co-existence of a non-AI CSI report and an AI CSI report; or whether the terminal device 310 supports a selection between a non-AI CSI report and an AI CSI report.

In some example embodiments, the terminal device 310 receives from the network device 320 at least one of the following: a first indication used for enabling or disabling a co-existence of a non-AI CSI mode and an AI CSI mode, a second indication used for enabling or disabling a co-existence of a non-AI CSI report and an AI CSI report, a third indication used for enabling or disabling a selection between a non-AI CSI mode and an AI CSI mode, or a fourth indication used for enabling or disabling a selection between a non-AI CSI report and an AI CSI report.

FIG. 10 illustrates a flowchart of a communication method 1000 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the terminal device 310 in FIG. 3.

At block 1010, the terminal device 310 receives, from a network device320, a second message for triggering channel state information (CSI) report.

At block 1020, the terminal device 310 determines a target CSI type from a first CSI type and a second CSI type based on at least one of the following: a first timing required for CSI computation corresponding to the first CSI type, a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or an uplink timing of the uplink resource carrying the CSI report.

At block 1030, the terminal device 310 transmits, to the network device 320, a CSI report with the determined target CSI type.

In some example embodiments, the first timing comprises at least one of the following: a first next uplink symbol after a first processing duration from an end of the last symbol of the second message, or a second next uplink symbol after a second processing duration from an end of the last symbol of the latest CSI reference signal (RS) resource for the CSI report, and wherein the second timing comprises at least one of the following: a third next uplink symbol after a third processing duration from an end of the last symbol of the second message, or a fourth next uplink symbol after a fourth processing duration from an end of the last symbol of the latest CSI RS resource for the CSI report.

In some example embodiments, the terminal device 310 determines the target CSI type to be the second CSI type if at least one of the following: the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing, or the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing and the first timing.

In some example embodiments, the terminal device 310 determines the target CSI type to be the first CSI type if: the uplink timing of the uplink resource carrying the CSI report starts no earlier than the first timing and earlier than the second timing.

In some example embodiments, the terminal device 310, if at least one of the following: the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing, or the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing and the second timing, performs at least one of the following: ignoring the second message; disabling to update CSI associated with at least one of the following: the first CSI type or the second CSI type; or disabling to provide a valid CSI report and updating CSI associated with at least one of the following: the first CSI type or the second CSI type.

In some example embodiments, the second message indicates a trigger state associated with at least one of the following: a first CSI type, a second CSI type, or both a first CSI type and a second CSI type.

In some example embodiments, the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI, the CSI with the first CSI type comprises information about the measured beam, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam, the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits, the CSI with the first CSI type comprises non-(artificial intelligence) AI (non-AI) CSI, and the CSI with the second CSI type comprises AI-related CSI.

In some example embodiments, the second timing is determined based on the first timing and an offset timing.

In some example embodiments, the offset timing is defined as a default value, determined by the network device 320, or reported by the terminal device 310.

FIG. 11 illustrates a flowchart of a communication method 1100 implemented at a network device 320 in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described from the perspective of the network device 320 in FIG. 3.

At block 1110, the network device 320 transmits, to a terminal device 310, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type.

At block 1120, the network device 320 transmits a first message for triggering CSI report to the terminal device 310, the first message indicating the trigger state comprised in the list of trigger states.

At block 1130, the network device 320 receives, from the terminal device 310, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.

In some example embodiments, the first number of first CSI report configurations comprised in the first set of first CSI report configurations is the same as the second number of second CSI report configurations comprised in the first set of second CSI report configurations.

In some example embodiments, the network device 320, if a configuration parameter is absent in a first CSI report configuration, determines the configuration parameter to be a corresponding configuration parameter comprised in a second CSI report configuration corresponding to the first CSI report configuration, and if a configuration parameter is absent in a second CSI report configuration, determine the configuration parameter to be a corresponding configuration parameter comprised in a first CSI report configuration corresponding to the second CSI report configuration.

In some example embodiments, the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI, the CSI with the first CSI type comprises information about the measured CSI, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam, the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits, or the CSI with the first CSI type comprises non- (artificial intelligence) AI (non-AI) CSI, and the CSI with the second CSI type comprises AI-related CSI.

In some example embodiments, the network device 320 receives, from the terminal device 310, capability information indicating at least one of the following: whether the terminal device 310 supports a co-existence of a non- (artificial intelligence) AI CSI mode and an AI CSI mode; whether the terminal device 310 supports a selection between a non-AI CSI mode and an AI CSI mode; whether the terminal device 310 supports a co-existence of a non-AI CSI report and an AI CSI report; or whether the terminal device 310 supports a selection between a non-AI CSI report and an AI CSI report.

In some example embodiments, the network device 320 transmits to the terminal device 310 at least one of the following: a first indication used for enabling or disabling a co-existence of a non-AI CSI mode and an AI CSI mode, a second indication used for enabling or disabling a co-existence of a non-AI CSI report and an AI CSI report, a third indication used for enabling or disabling a selection between a non-AI CSI mode and an AI CSI mode, or a fourth indication used for enabling or disabling a selection between a non-AI CSI report and an AI CSI report.

FIG. 12 illustrates a flowchart of a communication method 1200 implemented at a network device 320 in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the network device 320 in FIG. 3.

At block 1210, the network device 320 transmits, to a terminal device, a second message for triggering channel state information (CSI) report.

At block 1220, the network device 320 determines a target CSI type from a first CSI type and a second CSI type based on at least one of the following: a first timing required for CSI computation corresponding to the first CSI type, a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or an uplink timing of the uplink resource carrying the CSI report.

At block 1230, the network device 320 receives, from the terminal device 310, a CSI report with the determined target CSI type.

In some example embodiments, the network device 320 determines the target CSI type to be the second CSI type if at least one of the following: the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing, or the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing and the first timing.

In some example embodiments, the network device 320 determines the target CSI type to be the first CSI type if: the uplink timing of the uplink resource carrying the CSI report starts no earlier than the first timing and earlier than the second timing.

In some example embodiments, the network device 320, if at least one of the following: the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing, or the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing and the second timing, performs at least one of the following: ignoring the second message; disabling to update CSI associated with at least one of the following: the first CSI type or the second CSI type; or disabling to provide a valid CSI report and updating CSI associated with at least one of the following: the first CSI type or the second CSI type.

In some example embodiments, the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI, the CSI with the first CSI type comprises information about the measured beam, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam, the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits, the CSI with the first CSI type comprises non- (artificial intelligence) AI (non-AI) CSI, and the CSI with the second CSI type comprises AI-related CSI .

In some example embodiments, the network device 320, if the target CSI is determined to be the second CSI type, recovers CSI information from the CSI report by using an (artificial intelligence) AI model, and if the target CSI is determined to be the first CSI type, determine CSI information from the CSI report without using an AI model.

Example Devices

FIG. 13 is a simplified block diagram of a device 1300 that is suitable for implementing embodiments of the present disclosure. The device 1300 can be considered as a further example implementation of any of the devices as shown in FIG. 3. Accordingly, the device 1300 can be implemented at or as at least a part of the terminal device 310 or the network device 320.

As shown, the device 1300 includes a processor 1310, a memory 1320 coupled to the processor 1310, a suitable transceiver 1340 coupled to the processor 1310, and a communication interface coupled to the transceiver 1340. The memory 1320 stores at least a part of a program 1330. The transceiver 1340 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 1340 may include at least one of a transmitter 1342 and a receiver 1344. The transmitter 1342 and the receiver 1344 may be functional modules or physical entities. The transceiver 1340 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME)/Access and Mobility Management Function (AMF)/SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.

The program 1330 is assumed to include program instructions that, when executed by the associated processor 1310, enable the device 1300 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1 to 13. The embodiments herein may be implemented by computer software executable by the processor 1310 of the device 1300, or by hardware, or by a combination of software and hardware. The processor 1310 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1310 and memory 1320 may form processing means 1350 adapted to implement various embodiments of the present disclosure.

The memory 1320 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1320 is shown in the device 1300, there may be several physically distinct memory modules in the device 1300. The processor 1310 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1300 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

According to embodiments of the present disclosure, a terminal device comprising a circuitry is provided. The circuitry is configured to: determine, at least one reference signal (RS) set corresponding to at least one future duration, an RS set of the at least one RS set comprising one or more RSs for measurements, the at least one RS set being associated with at least one of the following: beam failure detection (BFD) , candidate beam measurement, or radio link monitoring (RLM) ; and perform RS measurements on the at least one RS set in the at least one respective future duration. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the terminal device as discussed above.

According to embodiments of the present disclosure, a network device comprising a circuitry is provided. The circuitry is configured to: generate, configuration information indicating at least one reference signal (RS) set corresponding to at least one future duration, an RS set of the at least one RS set comprising one or more RSs for measurements, the at least one RS set being associated with at least one of the following: 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 the present disclosure, the circuitry may be configured to perform any method implemented by the network device as discussed above.

According to embodiments of the present disclosure, a terminal device comprising a circuitry is provided. The circuitry is configured to: determine, at least one first beam set to be used for communications between the terminal device and a network device in at least one first future duration; and transmit, to the network device, a first message indicating at least one of the following: predicted beam failure information of 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 a 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 beam set which is predicted to be associated with a beam failure. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the terminal device as discussed above.

According to embodiments of the present disclosure, a network device comprising a 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 of 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 beam set which is predicted to be associated with a beam failure. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the network device as discussed above.

The term “circuitry” used herein may refer to hardware circuits and/or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.

According to embodiments of the present disclosure, a terminal apparatus is provided. The terminal apparatus comprises means for determining, at least one reference signal (RS) set corresponding to at least one future duration, an RS set of the at least one RS set comprising one or more RSs for measurements, the at least one RS set being associated with at least one of the following: beam failure detection (BFD) , candidate beam measurement, or radio link monitoring (RLM) ; and means for performing RS measurements on the at least one RS set in the at least one respective future duration. In some embodiments, the first apparatus may comprise means for performing the respective operations of the method 1900. In some example embodiments, the first apparatus may further comprise means for performing other operations in some example embodiments of the method 1900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

According to embodiments of the present disclosure, a network apparatus is provided. The network apparatus comprises means for generating, configuration information indicating at least one reference signal (RS) set corresponding to at least one future duration, an RS set of the at least one RS set comprising one or more RSs for measurements, the at least one RS set being associated with at least one of the following: beam failure detection (BFD) , candidate beam measurement, or radio link monitoring (RLM) ; and means for transmitting the configuration information to a terminal device. In some embodiments, the second apparatus may comprise means for performing the respective operations of the method 2000. In some example embodiments, the second apparatus may further comprise means for performing other operations in some example embodiments of the method 2000. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

According to embodiments of the present disclosure, a terminal apparatus is provided. The terminal apparatus comprises means for determining, at least one first beam set to be used for communications between the terminal device and a network device in at least one first future duration; and means for transmitting, to the network device, a first message indicating at least one of the following: predicted beam failure information of 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 a 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 beam set which is predicted to be associated with a beam failure. In some embodiments, the third apparatus may comprise means for performing the respective operations of the method 2100. In some example embodiments, the third apparatus may further comprise means for performing other operations in some example embodiments of the method 2100. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

According to embodiments of the present disclosure, a network apparatus is provided. The network apparatus comprises means for receiving, from a terminal device, a first message indicating at least one of the following: predicted beam failure information of 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 beam set which is predicted to be associated with a beam failure. In some embodiments, the fourth apparatus may comprise means for performing the respective operations of the method 2200. In some example embodiments, the fourth apparatus may further comprise means for performing other operations in some example embodiments of the method 2200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In summary, embodiments of the present disclosure provide the following aspects.

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

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

In some embodiments, the at least one future duration is indicated by one of the following: at least one starting time point corresponding to the at least one future duration, at least one ending time point corresponding to the at least one future duration, at least one time length corresponding to the at least one future duration, a starting time point corresponding to the first of the at least one future duration, or a common time length corresponding to each of the at least one future duration.

In some embodiments, an RS in the at least one RS set is indicated by one of the following: an identity of the RS, an identity of a beam associated with the RS, a transmission configuration indicator (TCI) associated with the RS, or quasi co-location (QCL) information associated with the RS.

In some embodiments, the configuration information further indicates at least one of the following: predicted quality information about the at least one RS set, or predicted failure information about the at least one RS set.

In some embodiments, the processor is further configured to cause the terminal device to: in case that an RS is associated with predicted failure information, exclude the RS from the at least one RS set.

In some embodiments, the at least one RS set comprises a first RS set corresponding to a first duration and a second RS set corresponding to a second duration which follows 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 and second RS sets during a third duration before an ending of the first duration.

In some embodiments, the third duration is defined as a default value, or determined by network device or the terminal device.

In some embodiments, the processor is further configured to cause the terminal device to: inform a beam failure to a higher layer of the terminal device with a periodicity determined based on at least one of the following: periodicities of RSs comprised in the at least one RS set, a pre-defined time length, a time length associated with a model, a scaling factor configured for a discontinuous reception (DRX) mode, or a DRX cycle length.

In some embodiments, the model is used for predicting beams and the time length is associated with a prediction capability of the model.

In some embodiments, a first value of the time length associated with the DRX mode is different from a second value of the time length associated with a non-DRX mode.

In some embodiments, the periodicity is determined to be the maximum value among at least one of the following: the minimum of the periodicities of RSs, the pre-defined time length, or the time length associated with the model.

In some embodiments, if the terminal device is in the DRX mode, the periodicity is determined to be the maximum value among at least one of the following: the minimum of scaled periodicities of RSs, a scaled time length associated with the model, or a scaled DRX cycle length.

In some embodiments, the processor is further configured to cause the terminal device to perform at least one of the following: resetting a beam failure counter at a first time point in accordance with a determination that a target beam is to be applied at a second time point, wherein the first time point starts earlier than the second time point; resetting a beam failure counter at a third time point in accordance with a determination that a different RS or RS set is to be measured at a fourth time point, wherein the third time point starts earlier than the fourth time point; resetting a beam failure counter upon a completion of measuring an RS set or a start of measuring a different RS set; or resetting a beam failure counter upon a completion of measuring the at least one RS set.

In some embodiments, a fourth duration between the first time point and the second time point is defined as a default value, or determined by network device or the terminal device, and wherein a fifth duration between the third time point and the fourth time point is defined as a default value, or determined by network device or the terminal device.

In some embodiments, the at least one RS set comprises a first RS set corresponding to a first duration and a second RS set corresponding to a second duration which follows the first duration, and wherein the processor is further configured to cause the terminal device to: start a beam failure counter at a start point of the first duration; and in accordance with a determination that the first RS set is at least partially overlapped with the second RS set, continue the beam failure counter without resetting in the second duration.

In some embodiments, a maximum value of a beam failure counter is associated with at least one of the following: the number of future durations of the at least one future duration, or the number of RSs comprised in an RS set.

In some embodiments, the processor is further configured to cause the terminal device to: stop performing a BFD procedure in case that at least one beam to be used in the at least one future duration is predicted by either the terminal device or the network device.

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

In some embodiments, the configuration information indicates the at least one future duration by one of the following: at least one starting time point corresponding to the at least one future duration, at least one ending time point corresponding to the at least one future duration, at least one time length corresponding to the at least one future duration, a starting time point corresponding to the first of the at least one future duration, or a common time length corresponding to each of the at least one future duration.

In some embodiments, the configuration information indicates an RS in the at least one RS set by one of the following: an identity of the RS, an identity of a beam associated with the RS, a transmission configuration indicator (TCI) associated with the RS, or quasi co-location (QCL) information associated with the RS.

In some embodiments, the processor is further configured to cause the network device to: in case that an RS is associated with predicted failure information, exclude the RS from the at least one RS set.

In an aspect, it is proposed a terminal device comprising: a processor configured to cause the terminal device to: determine, at least one first beam set to be used for communications between the terminal device and a network device in at least one first future duration; and transmit, to the network device, a first message indicating at least one of the following: predicted beam failure information of 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 a 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 beam set which is predicted to be associated with a beam failure.

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

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

In some embodiments, the processor is further configured to cause the terminal device to: upon a receipt of the configuration information, perform at least one of the following: expecting not to receive further configuration information indicating at least one further first beam set within the at least one first future duration, or ignoring at least one further first beam set comprised in further configuration information within the at least one first future duration.

In some embodiments, the processor is further configured to cause the terminal device to: determine the at least one first beam set based on an output of a model used for predicting beams and deployed at the terminal device.

In some embodiments, 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.

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 starting time point corresponding to the at least one respective future duration, at least one ending time point corresponding to the at least one respective future duration, at least one time length corresponding to the at least one respective future duration, a starting time point of corresponding to the first of the at least one respective future duration, or a common time length corresponding to each of the at least one respective future duration.

In some embodiments, a beam in the at least one second beam set or the recommended beam set is indicated by one of the following: a beam identity, an identity of the RS associated with the beam, a transmission configuration indicator (TCI) associated with the beam, or quasi co-location (QCL) information associated with the beam.

In some embodiments, the predicted beam failure information indicating at least one of the following: at least one first indication, each first indication indicating beam failure information corresponding to a beam set or a future duration, a plurality of second indication, each second indication indicating beam failure information corresponding to an RS.

In some embodiments, the predicted beam failure information comprises at least one of the following: an indication indicating whether there is a predicted beam failure, a predicted probability of beam failure, or predicted quality information.

In some embodiments, the second beam set comprises at least one of the following: a beam with the highest failure probability, or at least one beam with a failure probability higher than or equal to a threshold probability.

In some embodiments, the threshold probability is defined as a default value, or determined by network device or the terminal device.

In some embodiments, the processor is further configured to cause the terminal device to: after transmitting 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 future durations, at least one fourth beam set used to update the at least one second beam set, confirmation information on the at least one recommended beam set, or at least one fifth beam set used to update at least one rejected recommended beam set.

In an aspect, it is proposed a network device comprising: a processor configured to cause the network device to: receive, from a terminal device, a first message indicating at least one of the following: predicted beam failure information of 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 beam set which is predicted to be associated with a beam failure.

In some embodiments, the processor is further configured to cause the network device to: prior to receiving the first message, receive, from the network device, configuration information indicating: at least one first beam set to be used for communications between the terminal device and a network device, and at least one first future duration corresponding to the at least one first beam set.

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

In some embodiments, the processor is further configured to cause the network device to: after receiving the first message, transmit 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 future durations, at least one fourth beam set used to update the at least one second beam set, confirmation information on the at least one recommended beam set, or at least one fifth beam set used to update at least one rejected recommended beam set.

In an aspect, a terminal device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the terminal device discussed above.

In an aspect, a network device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the network device discussed above.

In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.

In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.

In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.

In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present 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, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 1 to 13. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A terminal device comprising:

a processor configured to cause the terminal device to:

receive, from a network device, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type;

receive a first message for triggering CSI report from the network device, the first message indicating the trigger state comprised in the list of trigger states; and

transmit, to the network device, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.
The terminal device of claim 1, wherein the list of trigger states comprising at least one of the following:

a first trigger state being associated with a first set of first channel state information (CSI) report configurations and a second set of second CSI report configurations, wherein the first CSI report configuration is associated with CSI with a first CSI type and the second CSI report configuration is associated with CSI with a second CSI type,

a second trigger state being associated with a third set of first CSI report configurations, wherein each first CSI report configuration comprised in the third set is associated with a second CSI report configuration,

a third trigger state being associated with a fourth set of second CSI report configurations, wherein each second CSI report configuration comprised in the fourth set is associated with a first CSI report configuration,

a fourth trigger state being associated with a fifth set of third CSI report configurations, wherein each third CSI report configuration is associated with a first set of parameters and a second set of parameters, wherein the first set of parameters is associated with CSI with a first CSI type and the second set of parameters is associated with CSI with a second CSI type.
The terminal device of claim 2, wherein the first number of first CSI report configurations comprised in the first set is the same as the second number of second CSI report configurations comprised in the second set.
The terminal device of claim 2, wherein the processor is further configured to cause the terminal device to:

if a configuration parameter is absent in a first CSI report configuration, determine the configuration parameter to be a corresponding configuration parameter comprised in a second CSI report configuration corresponding to the first CSI report configuration, and

if a configuration parameter is absent in a second CSI report configuration, determine the configuration parameter to be a corresponding configuration parameter comprised in a first CSI report configuration corresponding to the second CSI report configuration.
The terminal device of claim 1, wherein,

the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI,

the CSI with the first CSI type comprises information about the measured beam, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam,

the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits, or

the CSI with the first CSI type comprises non- (artificial intelligence) AI (non-AI) CSI, and the CSI with the second CSI type comprises AI-related CSI.
The terminal device of claim 1, wherein the CSI with the first CSI type is determined from a first set of reference signal (RS) resources, and the CSI with the second CSI type is determined from a second set of RS resources.
The terminal device of claim 6, wherein, the first set of RS resources may comprise at least one RS resource that is configured as beam measurement resource, and the second set of RS resources may comprise at least one RS resource that is configured as beam prediction resource.
The terminal device of claim 1, wherein the trigger state is one of the following: an aperiodic trigger state, or a semi-persistent trigger state.
The terminal device of claim 1, wherein the processor is further configured to cause the terminal device to:

transmit, to the network device, capability information indicating at least one of the following:

whether the terminal device supports a co-existence of a non- (artificial intelligence) AI (non-AI) CSI mode and an AI CSI mode;

whether the terminal device supports a selection between a non-AI CSI mode and an AI CSI mode;

whether the terminal device supports a co-existence of a non-AI CSI report and an AI CSI report; or

whether the terminal device supports a selection between a non-AI CSI report and an AI CSI report.
The terminal device of claim 1, wherein the processor is further configured to cause the terminal device to:

receive from the network device at least one of the following:

a first indication used for enabling or disabling a co-existence of a non-AI CSI mode and an AI CSI mode,

a second indication used for enabling or disabling a co-existence of a non-AI CSI report and an AI CSI report,

a third indication used for enabling or disabling a selection between a non-AI CSI mode and an AI CSI mode, or

a fourth indication used for enabling or disabling a selection between a non-AI CSI report and an AI CSI report.
A terminal device comprising:

a processor configured to cause the terminal device to:

receive, from a network device, a second message for triggering channel state information (CSI) report;

determine a target CSI type from a first CSI type and a second CSI type based on at least one of the following:

a first timing required for CSI computation corresponding to the first CSI type,

a second timing required for CSI computation corresponding to the second CSI type, wherein the second timing starts no earlier than the first timing, or

an uplink timing of the uplink resource carrying the CSI report; and

transmit, to the network device, a CSI report with the determined target CSI type.
The terminal device of claim 11, wherein the first timing comprises at least one of the following:

a first next uplink symbol after a first processing duration from an end of the last symbol of the second message, or

a second next uplink symbol after a second processing duration from an end of the last symbol of the latest CSI reference signal (RS) resource for the CSI report,

and wherein the second timing comprises at least one of the following:

a third next uplink symbol after a third processing duration from an end of the last symbol of the second message, or

a fourth next uplink symbol after a fourth processing duration from an end of the last symbol of the latest CSI RS resource for the CSI report.
The terminal device of claim 11, wherein the processor is further configured to cause the terminal device to:

determine the target CSI type to be the second CSI type if at least one of the following:

the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing, or

the uplink timing of the uplink resource carrying the CSI report starts no earlier than the second timing and the first timing.
The terminal device of claim 11, wherein the processor is further configured to cause the terminal device to:

determine the target CSI type to be the first CSI type if:

the uplink timing of the uplink resource carrying the CSI report starts no earlier than the first timing and earlier than the second timing.
The terminal device of claim 11, wherein the processor is further configured to cause the terminal device to:

if at least one of the following: the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing, or the uplink timing of the uplink resource carrying the CSI report starts earlier than the first timing and the second timing, perform at least one of the following:

ignoring the second message;

disabling to update CSI associated with at least one of the following: the first CSI type or the second CSI type; or

disabling to provide a valid CSI report and updating CSI associated with at least one of the following: the first CSI type or the second CSI type.
The terminal device of any of claims 13-15, wherein the second message indicates a trigger state associated with at least one of the following:

a first CSI type,

a second CSI type, or

both a first CSI type and a second CSI type.
The terminal device of claim 11, wherein,

the CSI with the first CSI type comprises the measured CSI, and the CSI with the second CSI type comprises at least one of the predicted CSI or the measured CSI,

the CSI with the first CSI type comprises information about the measured beam, and the CSI with the second CSI type comprises information about at least one of the predicted beam or the measured beam,

the CSI with the first CSI type comprises a precoding matrix indicator (PMI) codebook and the CSI with the second CSI type comprises compressed bits, or

the CSI with the first CSI type comprises non- (artificial intelligence) AI (non-AI) CSI, and the CSI with the second CSI type comprises AI-related CSI.
The terminal device of claim 11, wherein the second timing is determined based on the first timing and an offset timing,

and wherein the offset timing is defined as a default value, determined by the network device, or reported by the terminal device.
A network device comprising:

a processor configured to cause the network device to:

transmit, to a terminal device, configuration information indicating a list of trigger states, a trigger state comprised in the list of trigger states being associated with a first CSI type and a second CSI type;

transmit a first message for triggering CSI report to the terminal device, the first message indicating the trigger state comprised in the list of trigger states; and

receive, from the terminal device, a CSI report determined based on the trigger state indicated by the first message, the CSI report being associated with the first CSI type or the second CSI type.
The network device of claim 19, wherein the list of trigger states comprising at least one of the following:

a first trigger state being associated with a first set of first channel state information (CSI) report configurations and a second set of second CSI report configurations, wherein the first CSI report configuration is associated with CSI with a first CSI type and the second CSI report configuration is associated with CSI with a second CSI type,

a second trigger state being associated with a third set of first CSI report configurations, wherein each first CSI report configuration comprised in the third set is associated with a second CSI report configuration,

a third trigger state being associated with a fourth set of second CSI report configurations, wherein each second CSI report configuration comprised in the fourth set is associated with a first CSI report configuration,

a fourth trigger state being associated with a fifth set of third CSI report configurations, wherein each third CSI report configuration is associated with a first set of parameters and a second set of parameters, wherein the first set of parameters is associated with CSI with a first CSI type and the second set of parameters is associated with CSI with a second CSI type.