Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure comprises: a control unit that executes a first measurement for an inference result report and a second measurement for performance monitoring, and acquires a predicted result that corresponds to a predicted time instance from the first measurement; and a transmission unit that transmits the inference result report including the predicted result. The control unit calculates a metric instance on the basis of the predicted result and the second measurement.

Description

Terminal, wireless communication method, and base station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being considered.

[0004] 3GPP TS 36.300 V8.12.0, "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010

[0005] Regarding future wireless communication technologies, it is being considered to utilize artificial intelligence (AI) technologies such as machine learning (ML) for network / device control, management, etc.

[0006] As use cases for the utilization of AI models, spatial domain downlink (DL) beam prediction, temporal DL beam prediction, etc. are being considered. Such beam prediction methods may be referred to as AI-based beam prediction (beam reporting), AI-based beam management (BM), etc. Temporal DL beam prediction may be referred to as, for example, time domain channel state information (CSI) prediction.

[0007] In such utilization of AI, the introduction of life cycle management (LCM) is being considered, but there are cases where the consideration is not sufficient. If this consideration is not sufficient, suitable overhead reduction / channel estimation / resource utilization may not be achievable, and there is a risk that the improvement of communication throughput / communication quality may be suppressed.

[0008] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication throughput / communication quality.

[0009] A terminal according to one aspect of the present disclosure includes a control unit that executes a first measurement for inference result reporting and a second measurement for performance monitoring, and obtains a prediction result corresponding to a prediction time instance from the first measurement, and a transmission unit that transmits the inference result report including the prediction result. The control unit calculates a metric instance based on the prediction result and the second measurement.

[0010] According to one aspect of the present disclosure, communication throughput / communication quality can be improved.

[0011] Figure 1 is an example of an LCM framework for performance monitoring using a UE-side model. Figures 2A to 2C show an example of set B / set A / set P in beam prediction. Figure 3 shows an example of measurement timing for set B / set P in beam prediction. Figures 4A to 4C show an example of set B / set A / set P in CSI prediction. Figure 5 shows an example of measurement timing for set B / set P in CSI prediction. Figure 6 shows an example of performance monitoring according to this disclosure. Figure 7 shows an example of performance monitoring according to this disclosure. Figure 8 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 9 shows an example of a base station configuration according to one embodiment. Figure 10 shows an example of a user terminal configuration according to one embodiment. Figure 11 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 12 shows an example of a vehicle according to one embodiment.

[0012] (Use cases for prediction using AI / ML technology) The following are examples of various predictions using AI / ML models: ・Beam prediction. In beam prediction, beams / resources that achieve RSRP / SINR greater than a threshold are the targets of prediction. Examples include temporal beam prediction, spatial domain beam prediction, and frequency domain beam prediction. ・CSI prediction. Examples of CSI prediction include temporal CSI prediction and spatial domain CSI prediction. For example, in spatial domain CSI prediction, the CSI for a larger number of antenna ports is predicted based on a smaller number of antenna ports.

[0013] In this disclosure, beam prediction, CSI prediction, and specific predictions [using AI / ML models] may be interpreted interchangeably.

[0014] (Lifecycle Management (LCM) in UE-side models) UE-assisted performance monitoring may be supported for beam prediction. Therefore, for example, reporting methods, report content, and reporting trigger methods (whether to trigger reporting based on specific events, and details of those events) are being considered. For example, performance monitoring reports are being considered to follow the CSI framework.

[0015] The following specific points are being considered:

[0016] In beam management (BM) cases 1 and 2 using the AI / ML model on the UE side, the following options 1 and 2 of performance monitoring may be supported. Option 1 and 2 of performance monitoring may also be called type 1 performance monitoring.

[0017] BM Case 1 may also be called spatial domain DL beam prediction. BM Case 2 may also be called temporal DL beam prediction.

[0018] Here, spatial domain DL beam prediction may refer to predicting the quality of beamset #B, for example, a dense beam, in a spatial domain based on the measurement [results] of beamset #A, for example, a space beam, in the same spatial domain.

[0019] Temporal DL beam prediction may also refer to predicting the quality of a beam (future beam) at a time later than the measurement time, based on the measurement [results] of a historical beam.

[0020] Furthermore, a beamset may be a set containing one or more beams. Beamset #A / #B may be simply read as set #A / #B.

[0021] <Option 1: Network-side performance monitoring> The UE sends a report to the network (e.g., gNB) so that the network can calculate performance metrics. In other words, the network calculates the performance metrics.

[0022] The report may include the L1-RSRP / RS index as measurement results from the monitoring resource set. However, the report is not limited to this and may include other content.

[0023] The report can be configured / triggered by the network at least.

[0024] <Option 2: UE-Assisted Performance Monitoring> The UE calculates the performance metrics. In Option 2, there is room for further consideration regarding the reporting method / content.

[0025] Regarding whether to trigger reports based on specific events for options 1 and 2, option 2 requires further consideration regarding the reporting method and content.

[0026] Furthermore, performance monitoring of Type 2 is also being considered.

[0027] Figure 1 shows an example of an LCM framework for performance monitoring using a UE-side model. The LCM procedure may include the following six steps. Note that some of the steps shown in Figure 1 (performance reporting / model request) may be omitted. Also, the order of the steps is merely an example.

[0028] <RS Measurement> In this step, RS (CSI-RS / SSB) is measured for prediction (input to the AI ​​model) and performance monitoring.

[0029] <Performance Monitoring> In this step, the performance of the model and fallback scheme is monitored.

[0030] <UE Model Evaluation> In this step, the monitored / reported performance is compared.

[0031] <Performance Report> In this step, the monitored performance will be reported as needed.

[0032] <Model Requirements> In this step, the UE will request, as needed, which model to apply to the NW and which fallback scheme to apply.

[0033] <Model Activation / Deactivation> This step indicates which scheme is activated and whether to activate a specific model. After this step, you may return to the RS measurement step.

[0034] In this disclosure, lifecycle management and performance monitoring may be interpreted interchangeably.

[0035] (Performance Metrics) The UE may calculate and report performance metrics for performance monitoring. The following explains the various definitions depending on the type of forecast.

[0036] <Beam Prediction> (Definition of Terms) The terms related to beam prediction in this disclosure are listed below.

[0037] - Actual top-K beam. The actual top-K beam may refer to the top K resources / beams (where K is 1 or greater) in a set of resources / beams that achieve the highest RSRP / SINR based on measurements of the corresponding set of resources / beams.

[0038] - Predicted top-K beam. The predicted top-K beam may refer to the top K resources / beams (where K is 1 or greater) in a set of resources / beams that achieve the highest RSRP / SINR based on the UE-side prediction [for the corresponding set of resources / beams]. Note that the UE-side prediction may be performed together with the measurement.

[0039] • Current beam. The current beam may refer to the resource / beam corresponding to the QCL RS in the indicated TCI state, or the resource / beam corresponding to the RS (e.g., SSB) that is in a QCL relationship with the QCL RS in the indicated TCI state (QCLed).

[0040] Measured RSRP. Measured RSRP may refer to the RSRP / SINR value based on measurements of a particular beam / resource.

[0041] - Predicted RSRP. Predicted RSRP may refer to the RSRP / SINR value of a particular beam / resource derived based on predictions made by the UE. Note that predictions made by the UE may be performed together with (in conjunction with) the measurements.

[0042] (Definition of performance metrics) The performance metrics for beam prediction may represent at least one of the following options:

[0043] (Opt1) Percentage / probability of the predicted top K beam being the actual top-1 beam.

[0044] (Opt2) The proportion / probability that the predicted top K-beam will be equal to (or become equal to) the actual top K-beam.

[0045] (Opt3) The proportion / probability of the predicted top 1 beam being included in the actual top K beam.

[0046] (Opt4) The difference (difference value) between at least one measured RSRP of the predicted top K beam and the measured RSRP of the actual top 1 beam (may also be called the RSRP difference).

[0047] (Opt5) The difference between the predicted RSRP of the predicted top K-beam and the measured RSRP of the predicted top K-beam (this may also be called the predicted RSRP difference).

[0048] (Opt6) The difference between the predicted RSRP of the predicted top K beam and the measured RSRP of the current beam.

[0049] (Opt7) The hypothetical Block Error Rate (BLER) for PDSCH transmissions that have (or include) a predicted top K beam.

[0050] (Opt8) A virtual BLER for a PDSCH transmission having (including) a top K beam.

[0051] (Opt9) [Virtual] BLER for PDSCH transmissions having (including) the current beam.

[0052] (Opt10) The difference between Opt7 and Opt9. For example, the difference between Opt8 and Opt7 (the difference between the [virtual] BLER for a PDSCH transmission having (including) a measured top K beam and the [virtual] BLER for a PDSCH transmission having (including) a predicted top K beam).

[0053] For Opt7 to Opt10, assumptions used in BLE calculations (e.g., MCS, resource allocation) can be specified / configured / instructed / reported.

[0054] (Opt11) The range of the Y% confidence level for the predicted RSRP (e.g., the range around the predicted RSRP where the measured RSRP falls within Y%). Alternatively, the confidence level of the predicted RSRP with respect to range T (e.g., the proportion / probability that the measured RSRP falls within range T around the predicted RSRP).

[0055] (Opt12) The proportion / probability that the specific difference value shown in Opt4 / 5 / 6 / 10 is greater / less than the given value X [dB].

[0056] (Opt13) The range of Y% confidence levels for the specific value (BLER) shown in Opt7 to Opt9 (for example, the range in which the corresponding specific BLER falls within Y%). Alternatively, the confidence level for range T (for example, the proportion / probability that the corresponding specific BLER falls within range T).

[0057] (Opt14) The proportion / probability that the predicted ranking / ordering of the top K-beams is the same as the actual ranking / ordering of the top K-beams.

[0058] (Note) In this disclosure, proportions and probabilities may be interpreted as mutually exclusive.

[0059] In this disclosure, performance metrics and key performance indicators (KPIs) may be interpreted interchangeably.

[0060] In each of the options described above, the metric may be a hypothetical KPI or a measured KPI.

[0061] In the case of virtual KPIs, the KPIs may be calculated based on UE's estimates [and measurements]. For example, the percentage / probability of Opt1 may be based on UE's estimates.

[0062] In the case of measured KPIs, the KPI may be calculated based on measured and predicted values. For example, the percentage / probability of Opt1 may be based on measured values.

[0063] The specific parameters (K, X, Y, T) in each of the above options may be predefined by the specification, set / instructed by upper-layer signaling / physical layer signaling, or determined (or reported) according to UE capabilities.

[0064] Performance metrics for beam prediction may refer to specific parameters included in / associated with a given PDSCH [transmitter].

[0065] (Definitions of Set B / Set A / Set P in Beam Prediction) In this disclosure, Set B may mean RS resource / beam / time instance that is expected to be measured by the UE for inference result reporting (e.g., predicted beam result). Set B may also be interpreted as resource / beam / time instance relating to (potentially being input to) an AI model.

[0066] In this disclosure, Set A may mean RS resource / beam / time instances that are expected to be predicted / reported by the UE in the inference result report (e.g., predicted beam results). Set A may also be interpreted as resource / beam / time instances related to (potentially being outputs of) the output of the AI ​​model.

[0067] In this disclosure, set P may mean an RS resource / beam / time instance used by the UE for performance monitoring. Alternatively, set P may mean a resource / beam / time instance unrelated to the input / output of the AI ​​model.

[0068] <<Specific Example>> Figures 2A to 2C show an example of set B / set A / set P in beam prediction.

[0069] As shown in Figure 2A, set B may include one or more measurements [results (beams)] that constitute a plurality of predictions [results (beams)] (i.e., set A).

[0070] As shown in Figure 2B, set A may include multiple predictions [results (beams)] obtained (predicted) from set B.

[0071] As shown in Figure 2C, set P may include one or more measurements [results (beams)] that constitute a group of predictions [results (beams)] (i.e., set A). Alternatively, set P may include one or more other measurements [results (beams)] that are unrelated to set A.

[0072] Furthermore, Set B and Set P may or may not share / overlap at least some of their beams. Set B and Set P may also have beams that yield completely different measurement results.

[0073] Figure 3 shows an example of the measurement timing for set B / set P in beam prediction.

[0074] As shown in Figure 3, Set B and Set P may be measured alternately. In this case, Set B may be measured first, or Set P may be measured first. Also, Set B and Set P may be measured at the same time. Furthermore, Set P may be measured before or after the timing of Set A (i.e., the prediction).

[0075] The time interval between the measurement timing of set B and the measurement timing of set P may be predefined by the specifications, set / instructed by upper-layer signaling / physical layer signaling, or determined according to UE capabilities.

[0076] In this disclosure, performance monitoring is performed using prediction results based on set A and measurement results (i.e., actual values) based on set B / set P. Therefore, it is preferable that the prediction time instance of set A and the measurement timing (measurement time instance) of set B / set P are as close together as possible. By having the prediction and measurement timings closer together, more accurate performance monitoring can be achieved.

[0077] Furthermore, as shown in Figure 3, in set B, the same beam may be the target of measurement for each measurement. In set P, different beams may be the target of measurement for each measurement. For example, in set P, a subset of different beams may be the target of measurement for each measurement. This subset may include one or more beams.

[0078] Furthermore, Set B and Set P may both measure the same beam.

[0079] <CSI Forecast> (Definition of Terms) The terms related to the CSI forecast in this disclosure are listed below.

[0080] • Predicted CSI. Predicted CSI can refer to CSI based on predictions from the UE side. Examples of predicted CSI include the precoding matrix, channel matrix, channel quality, and rank of the precoding matrix.

[0081] The UE's predictions may be performed together with (in conjunction with) the measurements. Furthermore, the UE's predictions may be performed using a specific non-AI algorithm / AI algorithm (a prediction associated with a specific model).

[0082] • Reference CSI. The reference CSI may refer to a measurement-based CSI. For example, the reference CSI may include the precoding matrix, channel matrix, channel quality, and the rank of the precoding matrix. The reference CSI may also be used in the calculation of performance metrics using the predicted CSI.

[0083] The UE may determine the measurement opportunities to be used for the calculation of the reference CSI in accordance with rules predefined by the specification and parameters set / instructed / reported.

[0084] The reference CSI may also mean the quantized CSI (for example, a CSI represented by a specific codebook type, such as a Type 2 codebook).

[0085] (Definition of performance metrics) The performance metrics for CSI prediction may represent at least one of the following options:

[0086] (Opt1) The difference between the predicted CSI and the reference CSI (difference / similarity). Examples include various cosine similarities (squared generalized cosine similarity (SGCS) / generalized cosine similarity (GCS)), normalized mean square error (NMSE) / mean square error (MSE)), etc.

[0087] (Opt2) [Virtual] BLER for PDSCH transmissions that have / include / utilize predictive CSI.

[0088] (Opt3) A virtual BLER for PDSCH transmissions that have / include / use a reference CSI.

[0089] (Opt4) A [virtual] BLER for PDSCH transmissions that have / include / utilize a specific type (Type 1 / 2, or Extended Type 2) of CSI reporting.

[0090] (Opt5) Channel quality information (CQI) / rank indicator (RI) for PDSCH transmissions that have / include / utilize predicted CSI.

[0091] (Opt6) CQI / RI for PDSCH transmissions that have / include / utilize a reference CSI.

[0092] (Opt7) CQI / RI for PDSCH transmissions that have / include / utilize a specific type (Type 1 / 2, or Extended Type 2) CSI report.

[0093] (Opt8) The difference between Opt2 and Opt4. For example, the difference between identical options to which different derivation methods have been applied may be applied (the difference between the predictive CSI (Opt2) via / using the model ID and the predictive CSI (Opt2) via / using a specific non-AI algorithm).

[0094] (Opt9) The range of Y% confidence for the specific value (BLER) shown in Opt2 to Opt4 (for example, the range in which the corresponding specific BLER falls within Y%). Alternatively, the confidence level for range T (for example, the proportion / probability that the corresponding specific BLER falls within range T).

[0095] (Note) The specific parameters (Y, T) in each of the above options may be predefined by the specification, set / indicated by upper-layer signaling / physical layer signaling, or determined (reported) according to UE capabilities.

[0096] For Opt2 through Opt8, assumptions used in BLE calculations (e.g., MCS, resource allocation) can be specified / configured / instructed / reported.

[0097] Performance metrics for CSI prediction may refer to specific parameters included in / associated with a given PDSCH [transmission].

[0098] (Definitions of Set B / Set A / Set P in CSI Prediction) In this disclosure, Set B may mean RS resource / [antenna]port / time instance that is expected to be measured by the UE for inference result reporting (e.g., predictive CSI). Set B may also be interpreted as (potentially) resource / [antenna]port / time instance relating to the input of the AI ​​model.

[0099] In this disclosure, set A may mean RS resource / [antenna] port / time instance that is expected to be predicted / reported by the UE in the inference result report (e.g., predictive CSI). Set A may also be interpreted as a resource / [antenna] port / time instance relating to (potentially being an output of) the output of an AI model.

[0100] In this disclosure, set P may mean an RS resource / [antenna] port / time instance used by the UE for performance monitoring. Alternatively, set P may mean a resource / [antenna] port / time instance unrelated to the input / output of the AI ​​model.

[0101] <<Specific Example>> Figures 4A to 4C show an example of set B / set A / set P in CSI prediction.

[0102] As shown in Figure 4A, set B may include one or more measurements [results (CSI)] that constitute a group of predictions [results (CSI)] (i.e., set A).

[0103] As shown in Figure 4B, set A may include multiple predictions [results (CSI)] obtained (predicted) from set B.

[0104] As shown in Figure 4C, set P may include one or more measurements [results (CSI)] that constitute a group of predictions [results (CSI)] (i.e., set A). Alternatively, set P may include one or more other measurements [results (CSI)] that are unrelated to set A.

[0105] Furthermore, Set B and Set P may or may not share / overlap at least some ports. Set B and Set P may also have ports where all measurement results are different.

[0106] Figure 5 shows an example of the measurement timing for set B / set P in CSI prediction.

[0107] As shown in Figure 5, Set B and Set P may be measured alternately. In this case, Set B may be measured first, or Set P may be measured first. Also, Set B and Set P may be measured at the same time. Furthermore, Set P may be measured before or after the timing of Set A (i.e., the prediction).

[0108] The time interval between the measurement timing of set B and the measurement timing of set P may be predefined by the specifications, set / instructed by upper-layer signaling / physical layer signaling, or determined according to UE capabilities.

[0109] In this disclosure, performance monitoring is performed using prediction results based on set A and measurement results (i.e., actual values) based on set B / set P. Therefore, it is preferable that the prediction time instance of set A and the measurement timing (measurement time instance) of set B / set P are as close together as possible. By having the prediction and measurement timings closer together, more accurate performance monitoring can be achieved.

[0110] Furthermore, as shown in Figure 5, in set B, the same port may be measured for each measurement. In set P, different ports may be measured for each measurement. For example, in set P, a subset of different ports may be measured for each measurement. This subset may include one or more ports.

[0111] Furthermore, Set B and Set P may measure the same port.

[0112] (Calculation of processed performance metrics) The UE may process the previously calculated performance metrics, or calculate the processed performance metrics. That is, the UE may perform specific processing on the previously calculated performance metrics.

[0113] Specifically, the UE may calculate / process performance metrics based on the following options. Furthermore, the UE may report the processed performance metrics to the NW.

[0114] (Opt1) The UE may calculate a processed performance metric based on a performance metric at a particular occasion / timing. For example, the processed performance metric may be one of the performance metrics mentioned above. In other words, the UE may treat the previously calculated performance metric as the processed performance metric. To put it another way, the UE does not need to perform any processing on the previously calculated performance metric.

[0115] (Opt2) The UE may calculate the processed performance metrics based on performance metrics at multiple opportunities / timings.

[0116] Specifically, the UE may calculate the average value of the multiple performance metrics calculated in step #1 [at different timings] and treat this average value as the processed performance metric.

[0117] The precise performance metrics for averaging (the number of performance metrics to be averaged, the timer for determining the target, etc.) may be predefined by the specification, set / instructed by upper-layer signaling / physical-layer signaling, or reported.

[0118] (Opt3) The UE may calculate the processed performance metrics based on performance metrics at multiple opportunities / timings.

[0119] Specifically, the UE may calculate the processed performance metrics by applying a specific formula to multiple performance metrics [with different timings] calculated in step #1.

[0120] The specific formula may be predefined by the specification, and for example, a formula similar to that of existing L3 filtering (see below) may be applied. F ｎ = (1-a) * F ｎ－１ +a*M ｎ

[0121] Here, F ｎmay represent the processed performance metric (filtered updated version of the performance metric). F ｎ－１ may represent the past [filtered] performance metric. M ｎ may represent the latest [received] performance metric. a represents a specific coefficient (which may also be called a scaling factor) and may be predefined according to the specification or set / instructed by upper layer signaling / physical layer signaling.

[0122] For example, the processed performance metric (F ｎ ) may be determined based on the performance metric that was calculated / processed / reported previously (in the past), i.e., F ｎ－１ , or M ｎ .

[0123] Also, the processed performance metric (F ｎ ) may be determined based on the sum of the performance metric and the scaling factor (i.e., a) according to the measurement time used for calculating the performance metric or the calculation time of the performance metric (the time required for the calculation).

[0124] The method for determining the number of performance metrics required for calculating the processed performance metric (F ｎ ), i.e., the method for selecting a plurality of performance metrics, may follow at least one of the following.

[0125] - The number of samples indicated by parameters predefined / set / instructed / reported. - The time window (length / start timing / end timing) indicated by parameters predefined / set / instructed / reported.

[0126] Thus, by applying specific processing to the performance metric previously calculated by the UE, it is possible to apply a more accurate performance metric to LCM (performance monitoring).

[0127] (Analysis) As described above, for example, in beam prediction, it is being considered that the performance monitoring report follows the CSI framework. Also, as a performance metric, the prediction accuracy of the top 1 / K beams may be supported.

[0128] However, the precise performance metrics that can be reported as the prediction accuracy of the top 1 / K beam remain unclear.

[0129] In other words, the definition and calculation methods of metrics for performance monitoring are unclear. Without this clarity, it is anticipated that proper performance monitoring (LCM) cannot be achieved. As a result, optimal overhead reduction, channel estimation, and resource utilization may not be realized, potentially hindering improvements in communication throughput and communication quality.

[0130] Therefore, the inventors of this case conceived a way to solve these problems.

[0131] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0132] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0133] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0134] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0135] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0136] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0137] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0138] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.

[0139] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), Antenna port (e.g., Demodulation Reference Signal (DMRS) port), Antenna port group (e.g., DMRS port group), Group (e.g., Spatial relationship group, Code Division Multiplexing (CDM) group, Reference Signal group, CORESET group, Physical Uplink Control The following terms may be interchangeable: Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc.

[0140] In this disclosure, CSI-RS, Non Zero Power (NZP) CSI-RS, Zero Power (ZP) CSI-RS, and CSI Interference Measurement (CSI-IM) may be interpreted as interchangeable. Furthermore, CSI-RS may include other reference signals.

[0141] In this disclosure, the measured / reported RS may mean the RS measured / reported for CSI reporting.

[0142] In this disclosure, timing, time, duration, slot, sub-slot, symbol, subframe, etc., may be interpreted interchangeably.

[0143] In this disclosure, terms such as direction, axis, dimension, domain, polarization, and polarization component may be interpreted interchangeably.

[0144] In this disclosure, estimation, prediction, and inference may be interpreted interchangeably. Furthermore, in this disclosure, estimate, predict, and infer may be interpreted interchangeably.

[0145] In this disclosure, autoencoders, encoders, decoders, etc., may be interpreted as at least one of a model, ML model, neural network model, AI model, AI algorithm, etc. Furthermore, autoencoders may be interpreted as any autoencoder, such as a stacked autoencoder or a convolutional autoencoder. The encoders / decoders in this disclosure may employ models such as Residual Network (ResNet), DenseNet, and RefineNet.

[0146] In this disclosure, the terms bit, bit string, bit sequence, sequence, value, information, value obtained from a bit, and information obtained from a bit may be interpreted interchangeably.

[0147] In this disclosure, the term "layer" (referring to an encoder) may be interpreted interchangeably with the terms "input layer," "hidden layer," etc., used in an AI model. The layers in this disclosure may correspond to at least one of the following: an input layer, a hidden layer, an output layer, a batch normalization layer, a convolutional layer, an activation layer, a dense layer, a normalization layer, a pooling layer, an attention layer, a dropout layer, a fully connected layer, etc.

[0148] In this disclosure, RSRP may be interpreted as any parameter relating to received power / received quality, etc. (e.g., RSRQ, SINR, CSI).

[0149] In this disclosure, RS may be, for example, CSI-RS, SS / PBCH block (SS block (SSB)), etc. Also, the RS index may be a CSI-RS Resource Indicator (CRI), an SS / PBCH Block Resource Indicator (SSBRI), etc.

[0150] In this disclosure, channel measurement / estimation may be performed using, for example, at least one of the following: Channel State Information Reference Signal (CSI-RS), Synchronization Signal (SS), Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, DeModulation Reference Signal (DMRS), Sounding Reference Signal (SRS).

[0151] In this disclosure, the terms "received beam assumption," "number of received beams," "received beam index," "received beam selection," "received beam setting," and "received beam instruction" may be interpreted interchangeably. In this disclosure, the terms "received beam," "transmitted beam," "DL received beam," "DL transmitted beam," and "pair of transmitted and received beams" may be interpreted interchangeably. In this disclosure, "transmitted / received beams" may be interpreted interchangeably as "transmitted / received beams for beam prediction" and "transmitted / received beams for CSI measurement / reporting for beam prediction."

[0152] In this disclosure, functionality may mean the intended use of the model or the physical meaning of the model's inputs / outputs. Multiple models may have the same functionality. Based on functionality (for example, per functionality), monitoring (performance verification), activation, deactivation, switching, fallback, and updates may be instructed (controlled).

[0153] In this disclosure, "function" may mean a feature (reporting information based on CSI prediction / CSI compression / temporal beam prediction / spatial domain beam prediction) that requires AI / ML capabilities.

[0154] Furthermore, the model ID may mean an identifier for a model (or set of models). Multiple models may be assigned the same model ID in an actual deployment. In this case, these models may actually be different models (e.g., different number of layers), but may be treated as the same model.

[0155] In this disclosure, the model ID may be interpreted interchangeably with the metadata (or metadata set) ID. The metadata (or metadata ID) may be associated with information such as the applicability of the model / function, the environment, and the settings of the UE / gNB.

[0156] In this disclosure, functionality, functionality ID, model, and model ID may be interpreted interchangeably.

[0157] In this disclosure, ID may represent an ID that corresponds to (or identifies) at least one of the dataset, model, or channel / RS property. That is, in this disclosure, ID, dataset ID, model ID, and channel / RS property ID may be interchangeable.

[0158] In this disclosure, the terms "initiation of reporting" and "trigger for reporting" may be interpreted interchangeably.

[0159] In this disclosure, the prediction results and monitoring outputs may be interpreted interchangeably.

[0160] In this disclosure, measurement, measurement, and measurement may be interpreted interchangeably.

[0161] In this disclosure, "Top X" may be interpreted interchangeably with "Top X items".

[0162] (Wireless Communication Method) This disclosure can be broadly divided into the following embodiments: • First embodiment: Calculation of performance indicators on the UE side. • Second embodiment: Calculation of performance indicators on the NW side. • Third embodiment: Reporting of performance indicators.

[0163] The following describes each embodiment based on these. Each embodiment / option may be applied individually or in combination with others.

[0164] This disclosure primarily illustrates beam prediction and CSI prediction as use cases for utilizing AI models. However, the content of this disclosure is not limited to these and can be applied to other use cases (e.g., cell prediction). In this case, "beam" may be replaced with "cell."

[0165] In this disclosure, the term "RS resource" may be interpreted as simply "resource" or "measurement resource." Furthermore, in the following embodiments, the term "RS resource" exemplified a CSI-RS resource, but is not limited to it. "RS resource" may also mean a resource of another RS.

[0166] In this disclosure, a subset of RS resources may include some (or more / several) RS [resources] within a resource set. A subset of RS resources may include one or more (at least one) RS [resources].

[0167] In this disclosure, the beam / RS associated with the output (prediction result) of the AI ​​model may be referred to as Set A. The beam / RS associated with the input of the AI ​​model may be referred to as Set B.

[0168] More specifically, in the case of beam prediction / CSI prediction, Set A / Set B may be interpreted as Resource A / Resource B, respectively. Resource A may mean the resources related to the predicted value. Resource B may mean the resources measured to derive the predicted value (i.e., resources related to the measurement values).

[0169] Furthermore, in the case of CSI prediction, Set A / Set B may be interpreted as Antenna Port A / Antenna Port B, respectively. Antenna Port A may refer to the antenna port associated with the predicted value (predicted CSI). Antenna Port B may refer to the antenna port measured in order to derive the predicted value.

[0170] In the case of CSI prediction, resource A and antenna port A may be combined to form set A, and resource B and antenna port B may be combined to form set B.

[0171] In this disclosure, Set A, Resource A, Antenna Port A, and Predicted Value may be interpreted as interchangeable. Similarly, Set B, Resource B, Antenna Port B, and Measured Value may be interpreted as interchangeable. A and B may be interpreted as #A and #B, respectively.

[0172] In this disclosure, "antenna port" and "port" may be interpreted interchangeably.

[0173] The UE / NW (gNB) may perform LCM procedures (e.g., various operations related to beam prediction / CSI prediction) by applying the embodiments shown below.

[0174] The UE may receive various settings for beam prediction / CSI prediction. Furthermore, the UE may report / transmit the corresponding prediction results to the NW.

[0175] The network (NW) may transmit various settings for beam prediction / CSI prediction to the user (UE). Furthermore, the network may receive the corresponding prediction results (reports) from the UE.

[0176] In this disclosure, beam prediction and predicted beam may be interpreted interchangeably. Similarly, CSI prediction and predicted CSI may be interpreted interchangeably.

[0177] The wireless communication method described herein clarifies the provisions for calculating and reporting performance metrics. As a result, appropriate performance monitoring (LCM) is achieved. Furthermore, optimal overhead reduction, channel estimation, and resource utilization are realized, improving communication throughput and communication quality.

[0178] This disclosure provides an example of using a UE-side model as the AI ​​model, but is not limited to this. The AI ​​model may also be a NW-side model (e.g., a gNB-side model).

[0179] In this disclosure, subsets, beam / RS / [RS] resource subsets, measured subsets, and configured subsets may be interpreted interchangeably. Furthermore, measured subsets may mean subsets determined by the methods of this disclosure.

[0180] <First Embodiment> The first embodiment relates to the calculation of performance indicators on the UE side.

[0181] The performance indicators of this disclosure may include, in addition to those described below, at least one of the performance indicators mentioned above.

[0182] <<Metric Instances in Performance Metric Calculation>> The definition of metric instances in this disclosure is described below.

[0183] In this disclosure, a metric instance may mean a metric calculated based on one inference report instance / prediction and one or more measurements for performance monitoring.

[0184] In this disclosure, a valid metric instance may mean a computable metric instance, or a valid trick instance may mean a metric instance that satisfies certain conditions.

[0185] In this disclosure, an invalid metric instance may mean a metric instance that cannot be computed. Alternatively, an invalid trick instance may mean a metric instance that does not satisfy certain conditions.

[0186] In this disclosure, an accurate metric instance may mean a metric instance that satisfies certain conditions, which may mean satisfying an accurate condition (a condition indicating accuracy) or failing to satisfy an inaccurate condition (a condition indicating inaccuracy).

[0187] In this disclosure, an inaccurate metric instance may mean a metric instance that does not satisfy certain conditions, which may mean that it does not satisfy an accurate condition (a condition indicating accuracy) or that it satisfies an inaccurate condition (a condition indicating inaccuracy).

[0188] In this disclosure, a metric instance may include (or be composed of) valid metric instances and invalid metric instances. A valid metric instance may include at least a portion of accurate metric instances and inaccurate metric instances.

[0189] In this disclosure, metric instances and performance indicators may be interpreted as interchangeable.

[0190] <<Calculation of Percentages / Probabilities by the UE>> The UE may calculate performance metrics based on this disclosure. For example, the UE may calculate percentages / probabilities for a specific measurement as performance metrics depending on the type of forecast described above.

[0191] In this case, the ratio / probability may mean the ratio of at least one of the following options.

[0192] (Opt1) The ratio of the number of exact metric instances to the total number of all metric instances. That is, (number of exact metric instances) ÷ (total number of metric instances).

[0193] (Opt2) The ratio of the number of inaccurate metric instances to the total number of all metric instances. That is, (number of inaccurate metric instances) ÷ (total number of metric instances).

[0194] (Opt3) The ratio of the number of accurate metric instances to the number of valid metric instances. That is, (number of accurate metric instances) ÷ (number of valid metric instances).

[0195] (Opt4) The ratio of the number of inaccurate metric instances to the number of valid metric instances. That is, (number of inaccurate metric instances) ÷ (number of valid metric instances).

[0196] In each of the above options, the total number of metric instances (N, as described later) ａｌｌ ) is the number of valid metric instances (N, as described later). ｖａｌｉｄ ) + Number of invalid metric instances (N, as described later) ｉｎｖａｌｉｄ ) may be the number of valid metric instances (N ｖａｌｉｄ ) is the total number of metric instances (N ａｌｌ ) - Number of invalid metric instances (N) ｉｎｖａｌｉｄ ) is acceptable.

[0197] Also, the number of valid metric instances (N ｖａｌｉｄ) may be the number of accurate metric instances plus the number of inaccurate metric instances.

[0198] (Conditions for accurate metric instances) In the options described above, the conditions for accurate metric instances may include the following: The UE may determine the accuracy (accuracy / inaccuracy) of a metric instance based on at least one of the following conditions:

[0199] ((Alt1)) At least N#3 beams from the actual top N#1 beams are included in the predicted top N#2 beams, where N#1 to N#3 can be any integers.

[0200] For example, if N#1=1, N#2=K, and N#3=1, the condition for Alt1 may be "the actual top 1 beam is included in the predicted top K beam."

[0201] ((Alt2)) At least N#4 of the predicted top N#2 beams are included in the actual top N#1 beam, where N#1, N#2, and N#4 can be any integers.

[0202] For example, if N#1=K, N#2=1, and N#4=1, the condition for Alt2 may be "the predicted top 1 beam is included in the actual top K beam."

[0203] ((Alt3)) The RSRP / SINR of the predicted top K beam [of set P] is greater than / less than a predetermined value (e.g., X#1) than the actual top 1 beam [of set P].

[0204] ((Alt4)) The performance indicators mentioned above are greater than / less than a certain threshold #1.

[0205] (Conditions for Inaccurate Metric Instances) The conditions for accurate metric instances described above may be interchangeable with the conditions for inaccurate metric instances. In this case, the conditions for an inaccurate metric instance may be that it does not satisfy at least one of Alt1 to Alt4 described above.

[0206] Thus, the UE may determine / recognize the accuracy of the metric instance based on at least one of the predicted beam / actual beam.

[0207] (Conditions for a valid metric instance) In the options described above, the conditions for a valid metric instance may include the following: The UE may determine the validity / appropriateness (whether or not it is valid) of a metric instance based on at least one of the following conditions.

[0208] ((Alt1)) At least N#5 beams out of the predicted top N#2 beams are included in set P, where N#2 and N#5 can be any integers.

[0209] ((Alt2)) The time length (duration) between the measurement opportunity and the predicted time instance is less than a certain threshold #2.

[0210] (Conditions for an Invalid Metric Instance) The conditions for a valid metric instance described above may be interpreted interchangeably with the conditions for an invalid metric instance. In this case, the conditions for an invalid metric instance may be that it does not satisfy at least one of Alt1 to Alt2 described above.

[0211] Thus, the UE may determine / recognize the effectiveness / validity of a metric instance based on the number of beams included in set P, or the time length between the measurement opportunity and the predicted time instance.

[0212] For example, a UE may determine whether a metric instance is computable (effective / valid) based on whether it can secure a sufficient number of metric instances to compute the performance indicator.

[0213] Alternatively, the UE may determine that a [valid] metric instance is computable if the time length between the measurement opportunity and the predicted time instance is less than a certain threshold #2. Otherwise (if the time length between the measurement opportunity and the predicted time instance is greater than or equal to a certain threshold #2), the UE may determine that a [valid] metric instance is not computable. This is because if the time length is too long, it may not be possible to compose a valid (with sufficient accuracy for monitoring) metric instance.

[0214] (Note) The above-mentioned N#1 to N#5, X#1, threshold #1, and #2 may be predefined by the specification, set / instructed by upper layer signaling / physical layer signaling, or determined according to UE capabilities.

[0215] (Specific Example) Figure 6 shows an example of performance monitoring according to this disclosure. Figure 6 shows an example in which two inference results (corresponding to two predicted time instances) are obtained for one inference measurement.

[0216] The UE may send an inference result report (CSI report) for each inference measurement (Inference #1 to #4). Alternatively, the UE may send one monitoring report (CSI report) for two (two) monitoring measurements (Monitoring #1 and #3).

[0217] Furthermore, the UE may perform one monitoring measurement for every two transition measurements. That is, the period of the monitoring measurement may be twice that of the inference measurement.

[0218] Alternatively, the UE may compute a metric instance for each predicted time instance. In this case, the UE may compute two metric instances for each inference measurement.

[0219] Alternatively, the UE may calculate a metric instance for each monitoring measurement. In this case, the UE may calculate one metric instance for each monitoring measurement.

[0220] Alternatively, the UE may calculate a metric instance for each inference measurement / inference result report. In this case, the UE may calculate one metric instance for each inference measurement / inference result report.

[0221] Note that the content shown in Figure 6 is merely an example, and the number / period of measurements performed by the UE, the number / period of metric instances calculated by the UE, etc., are not limited to these and can be changed as appropriate.

[0222] <<Bit Size of Percentages / Probabilities>> When a UE calculates / reports the above percentages / probabilities, the bit size (length of the bit field) of the percentages / probabilities may be determined according to at least one of the following options:

[0223] In this disclosure, floor(A) may mean multiplying A by a floor function. Similarly, ceiling(A) may mean multiplying A by a ceiling function. floor(A) and ceiling(A) may be transformed / interpreted as one another.

[0224] (Opt1) The bit size of the ratio / probability is the total number of metric instances (N ａｌｌ ) may be decided based on the following.

[0225] For example, the bit size of the ratio / probability is floor{log ２ (N ａｌｌ It can be expressed as )}.

[0226] Total number of metric instances (N ａｌｌ The periodicity / interval of inference reports, the periodicity / interval of measurement opportunities for performance monitoring, the periodicity / interval of performance monitoring reports, etc., may be used to calculate this.

[0227] More specifically, for example, N ａｌｌ This is the ratio of the period / interval of performance monitoring reports to the period / interval of inference reports. That is, N ａｌｌ This can be expressed as (Performance monitoring report cycle / interval) ÷ ​​(Inference report cycle / interval).

[0228] Or, N ａｌｌ This is the ratio of the period / interval of performance monitoring reports to the period / interval of measurement opportunities for performance monitoring. That is, N ａｌｌ This can be expressed as (Performance monitoring report cycle / interval) ÷ ​​(Performance monitoring measurement opportunity cycle / interval).

[0229] (Opt2) The bit size of the ratio / probability may be determined based on the reported information (e.g., the number of valid metric instances).

[0230] For example, the number of metric instances (N) for which UE is enabled. ｖａｌｉｄ When reporting the ratio / probability, the bit size of the ratio / probability is floor{log ２ (N ｖａｌｉｄ It can be expressed as )}.

[0231] (Opt3) The bit size of the ratio / probability may be determined based on the number of predicted time instances per inference report (the number of predicted time instances within a single inference report). The number of predicted time instances per inference report may be, for example, N. ｐ＿ｐｅｒ＿ｉｒ It may be expressed as follows.

[0232] (Opt4) The bit size of the ratio / probability may be predefined by the specification, set / instructed by upper layer signaling / physical layer signaling, or determined according to UE capabilities.

[0233] (Opt5) The bit size of the ratio / probability may be determined based on the combination of Opt1 to Opt4 described above.

[0234] For example, the bit size of the ratio / probability is floor{log ２ (N ａｌｌ ) * (N ｐ＿ｐｅｒ＿ｉｒ It can be expressed as )}.

[0235] Alternatively, the bit size of the ratio / probability is floor{log ２ (N ｖａｌｉｄ ) * (N ｐ＿ｐｅｒ＿ｉｒ It can be expressed as )}.

[0236] (Note) As mentioned above, in each option, N ａｌｌ = N ｖａｌｉｄ +N ｉｎｖａｌｉｄ The following relationship may hold. Here, N ｉｎｖａｌｉｄ This can mean the number of invalid (not valid) metric instances.

[0237] According to this embodiment, the definition of the metric instance required for calculating performance metrics and the method for determining the bit size of the performance metrics become clear. The UE can then appropriately calculate the performance metrics based on this information. As a result, appropriate performance monitoring (LCM) is achieved.

[0238] <Second Embodiment> The second embodiment relates to the calculation of performance indicators on the network side.

[0239] <<Calculation of Percentage / Probability on the Network Side>> In the first embodiment, the calculation of performance indicators (percentage / probability) on the UE side was described. On the other hand, the network can calculate the percentage / probability as long as it knows the exact number of metric instances and the number of valid metric instances / total number of metric instances.

[0240] Here, the following three points may need to be considered on the network side.

[0241] (1) The exact number of metric instances (e.g., N) ｖａｌｉｄ This value (the exact number of metric instances) can be recognized by the UE based on measurement and inference results for performance monitoring. In this case, the NW cannot recognize (does not know) the value.

[0242] (2) The total number of valid metric instances (e.g., N) ｖａｌｉｄ This value can be determined based on settings / instructions via upper layer signaling (RRC / MAC CE) / physical layer signaling (DCI) and inference results. In this case, the network can recognize (know) the value (the number of all exact metric instances) if it can decode the inference result report, because the network is the entity responsible for the settings / instructions.

[0243] (3) The total number of metric instances (N) ａｌｌ This value can be determined based on settings / instructions via upper layer signaling (RRC / MAC CE) / physical layer signaling (DCI). In this case, the network can know the value (the total number of metric instances) because the network is the entity responsible for the settings / instructions.

[0244] In particular, considering (1) and (2) above, in order for NW to calculate the above-mentioned ratio / probability, it is necessary to obtain (be provided with) the information required for the calculation from UE.

[0245] Therefore, in order to realize the calculation of proportions / probabilities on the network side, we propose the following. This makes it possible to calculate proportions / probabilities appropriately on the network side as well. In particular, since only information that the network cannot know is obtained from the user, it is possible to reduce the communication overhead when the user reports.

[0246] <<Number of metric instances that satisfy the conditions>> The UE may calculate the processed performance metrics and report / send them to the NW. The processing method (how to calculate the processed performance metrics) may follow the method described above.

[0247] The processed performance metric may be at least one of the following options:

[0248] (Opt1) The exact number of metric instances.

[0249] (Opt2) The number of inaccurate metric instances.

[0250] (Opt3) The number of valid metric instances.

[0251] (Opt4) The number of invalid (not valid) metric instances.

[0252] (Specific Example) Figure 7 shows an example of performance monitoring according to this disclosure. Figure 7 shows an example in which two inference results (corresponding to two predicted time instances) are obtained for one inference measurement.

[0253] In Figure 7, the UE performs a monitoring measurement for each inference measurement. That is, the periods for the inference measurement and the monitoring measurement are the same.

[0254] Furthermore, the UE calculates a metric instance for each predicted time instance. In other words, the UE calculates two metric instances for each measurement used for inference.

[0255] As shown in Figure 7, the metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #1 is valid and accurate. The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #1 is valid and accurate.

[0256] The metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #2 is invalid. The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #2 is valid and inaccurate.

[0257] The metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #3 is valid and accurate. The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #1 is invalid.

[0258] The metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #4 is valid and accurate. The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #4 is valid and inaccurate.

[0259] Thus, in Figure 7, the total number of metric instances (N ａｌｌ ) is 8, and the number of valid metric instances (N ｖａｌｉｄ ) is 6, and the number of invalid metric instances (N ｉｎｖａｌｉｄThe number of accurate metric instances is 2. Furthermore, the number of accurate metric instances is 4, and the number of inaccurate metric instances is 2.

[0260] <<Number of metric instances that satisfy the conditions>> The conditions for determining / judging the metric instances described above may also follow those of the first embodiment. In this case, "performance indicator" in the first embodiment may be read interchangeably with "processed performance indicator". Specifically, the following can be given as examples.

[0261] (Conditions for accurate metric instances) In the options described above, the conditions for accurate metric instances may include the following: The UE may determine the accuracy (accuracy / inaccuracy) of a metric instance based on at least one of the following conditions:

[0262] ((Alt1)) At least N#3 beams from the actual top N#1 beams are included in the predicted top N#2 beams, where N#1 to N#3 can be any integers.

[0263] For example, if N#1=1, N#2=K, and N#3=1, the condition for Alt1 may be "the actual top 1 beam is included in the predicted top K beam."

[0264] ((Alt2)) At least N#4 of the predicted top N#2 beams are included in the actual top N#1 beam, where N#1, N#2, and N#4 can be any integers.

[0265] For example, if N#1=K, N#2=1, and N#4=1, the condition for Alt2 may be "the predicted top 1 beam is included in the actual top K beam."

[0266] ((Alt3)) The RSRP / SINR of the predicted top K beam [of set P] is greater than / less than a predetermined value (e.g., X#1) than the actual top 1 beam [of set P].

[0267] ((Alt4)) The processed performance metric described above is greater than / less than a certain threshold #1.

[0268] (Conditions for Inaccurate Metric Instances) The conditions for accurate metric instances described above may be interchangeable with the conditions for inaccurate metric instances. In this case, the conditions for an inaccurate metric instance may be that it does not satisfy at least one of Alt1 to Alt4 described above.

[0269] Thus, the UE may determine / recognize the accuracy of the metric instance based on at least one of the predicted beam / actual beam.

[0270] (Conditions for a valid metric instance) In the options described above, the conditions for a valid metric instance may include the following: The UE may determine the validity / appropriateness (whether or not it is valid) of a metric instance based on at least one of the following conditions.

[0271] ((Alt1)) At least N#5 beams out of the predicted top N#2 beams are included in set P, where N#2 and N#5 can be any integers.

[0272] ((Alt2)) The time length (duration) between the measurement opportunity and the predicted time instance is less than a certain threshold #2.

[0273] (Conditions for an Invalid Metric Instance) The conditions for a valid metric instance described above may be interpreted interchangeably with the conditions for an invalid metric instance. In this case, the conditions for an invalid metric instance may be that it does not satisfy at least one of Alt1 to Alt2 described above.

[0274] Thus, the UE may determine / recognize the effectiveness / validity of a metric instance based on the number of beams included in set P, or the time length between the measurement opportunity and the predicted time instance.

[0275] (Note) The above-mentioned N#1 to N#5, X#1, threshold #1, and #2 may be predefined by the specification, set / instructed by upper layer signaling / physical layer signaling, or determined according to UE capabilities.

[0276] <<Bit size of processed performance metrics (number of metric instances)>> When the UE calculates / reports the processed performance metrics described above, the bit size (length of the bit field) of the processed performance metrics may also be determined according to the first embodiment described above. In this case, "percentage / probability" in the first embodiment may be read as "number of processed performance metrics / metric instances". Specifically, the bit size of the processed performance metrics may be determined according to at least one of the following options.

[0277] (Opt1) The bit size of the ratio / probability is the total number of metric instances (N ａｌｌ ) may be decided based on the following.

[0278] For example, the bit size of the ratio / probability is floor{log ２ (N ａｌｌ It can be expressed as )}.

[0279] Total number of metric instances (N ａｌｌ The periodicity / interval of inference reports, the periodicity / interval of measurement opportunities for performance monitoring, the periodicity / interval of performance monitoring reports, etc., may be used to calculate this.

[0280] More specifically, for example, N ａｌｌ This is the ratio of the period / interval of performance monitoring reports to the period / interval of inference reports. That is, N ａｌｌ This can be expressed as (Performance monitoring report cycle / interval) ÷ ​​(Inference report cycle / interval).

[0281] Or, N ａｌｌ This is the ratio of the period / interval of performance monitoring reports to the period / interval of measurement opportunities for performance monitoring. That is, N ａｌｌThis can be expressed as (Performance monitoring report cycle / interval) ÷ ​​(Performance monitoring measurement opportunity cycle / interval).

[0282] (Opt2) The bit size of the ratio / probability may be determined based on the reported information (e.g., the number of valid metric instances).

[0283] For example, the number of metric instances (N) for which UE is enabled. ｖａｌｉｄ When reporting the ratio / probability, the bit size of the ratio / probability is floor{log ２ (N ｖａｌｉｄ It can be expressed as )}.

[0284] (Opt3) The bit size of the ratio / probability may be determined based on the number of predicted time instances per inference report (the number of predicted time instances within a single inference report). The number of predicted time instances per inference report may be, for example, N. ｐ＿ｐｅｒ＿ｉｒ It may be expressed as follows.

[0285] (Opt4) The bit size of the ratio / probability may be predefined by the specification, set / instructed by upper layer signaling / physical layer signaling, or determined according to UE capabilities.

[0286] (Opt5) The bit size of the ratio / probability may be determined based on the combination of Opt1 to Opt4 described above.

[0287] For example, the bit size of the ratio / probability is floor{log ２ (N ａｌｌ ) * (N ｐ＿ｐｅｒ＿ｉｒ It can be expressed as )}.

[0288] Alternatively, the bit size of the ratio / probability is floor{log ２ (N ｖａｌｉｄ ) * (N ｐ＿ｐｅｒ＿ｉｒ It can be expressed as )}.

[0289] According to this embodiment, the content of the processed performance indicator report and the method for determining the bit size of the processed performance indicator become clear.

[0290] For example, the UE may report only information that the NW cannot know (the numerator for calculating the ratio / probability) to the NW. Since the UE does not need to calculate the ratio / probability as in the first embodiment, it is possible to reduce the communication overhead when the UE reports [compared to when the UE calculates / reports the ratio / probability].

[0291] The network (NW) can appropriately calculate percentages / probabilities based on the processed performance metrics received from the user audience (UE) and the information it recognizes (the denominator for calculating percentages / probabilities).

[0292] <Third Embodiment> The third embodiment relates to the reporting of performance metrics (metric instances).

[0293] The UE may report to the NW a bit sequence corresponding to whether each metric instance satisfies the following conditions (for example, whether the metric instance is accurate / inaccurate / valid / invalid).

[0294] Based on the received bit sequence, the network can determine whether a metric instance satisfies the conditions (whether the metric instance is accurate / inaccurate / valid / invalid).

[0295] <<Conditions for Determining / Judging the Bit Sequence>> The UE may report the bit sequence corresponding to the metric instance being reported to the NW. The bit sequence (each bit value) corresponding to the metric instance being reported may be determined based on whether it satisfies at least one of the following options. That is, whether the metric instance is accurate / inaccurate / valid / invalid may be determined according to the following options.

[0296] (Opt1) Metric instances are accurate / inaccurate metric instances.

[0297] The following are examples of conditions under which a metric instance is an accurate metric instance. The following are conditions under which a metric instance is an inaccurate metric instance, provided that it does not satisfy any of the following conditions. In other words, the UE may determine the accuracy (accuracy / inaccuracy) of a metric instance based on at least one of the following conditions.

[0298] (Condition 1-1) At least N#3 beams from the actual top N#1 beams are included in the predicted top N#2 beams. Here, N#1 to N#3 can be any integers.

[0299] For example, if N#1=1, N#2=K, and N#3=1, then condition 1-1 may be "the actual top 1 beam is included in the predicted top K beam."

[0300] (Condition 1-2) At least N#4 of the predicted top N#2 beams are included in the actual top N#1 beam. Here, N#1, N#2, and N#4 can be any integers.

[0301] For example, if N#1=K, N#2=1, and N#4=1, then condition 1-2 may simply be that "the predicted top 1 beam is included in the actual top K beam."

[0302] (Conditions 1-3) The RSRP / SINR of the predicted top K beam [of set P] is greater than / less than a predetermined value (e.g., X#1) than the actual top 1 beam [of set P].

[0303] (Condition 1-4) The performance indicator described above is greater than / less than a certain threshold #1.

[0304] (Opt2) A metric instance is either an enabled or disabled metric instance.

[0305] The following are examples of conditions under which a metric instance is a valid metric instance. The following conditions may indicate that a metric instance is an invalid metric instance: it may not satisfy any of the following conditions. In other words, the UE may determine the validity / appropriateness (whether it is valid or not) of a metric instance based on at least one of the following conditions.

[0306] (Condition 2-1) At least N#5 beams out of the predicted top N#2 beams are included in set P. Here, N#2 and N#5 can be any integers.

[0307] (Condition 2-2) The time length (duration) between the measurement opportunity and the predicted time instance is less than a certain threshold #2.

[0308] (Note) The above-mentioned N#1 to N#5, X#1, threshold #1, and #2 may be predefined by the specification, set / instructed by upper layer signaling / physical layer signaling, or determined according to UE capabilities.

[0309] (Specific Example) The bit values ​​(bit sequences) corresponding to each metric instance can be exemplified as follows. This correspondence is just one example, and "0" and "1" may be reversed. • Valid metric instance: Bit value = "1". • Invalid metric instance: Bit value = "0". • Accurate metric instance: Bit value = "1". • Inaccurate metric instance: Bit value = "0".

[0310] More specifically, as shown in Figure 7, the metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #1 is valid and accurate (1 / 1). The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #1 is valid and accurate (1 / 1).

[0311] The metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #2 is invalid (0). The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #2 is valid and inaccurate (1 / 0).

[0312] The metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #3 is valid and accurate (1 / 1). The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #1 is invalid (0).

[0313] The metric instance corresponding to the first (earlier) predicted time instance for the measurement for inference #4 is valid and accurate (1 / 1). The metric instance corresponding to the second (later) predicted time instance for the measurement for inference #4 is valid and inaccurate (1 / 0).

[0314] <<Size of Bit Sequence>> When the UE calculates / reports the above-mentioned performance metrics (metric instances), the size of the bit sequence (length of the bit field) corresponding to the performance metric (metric instance) may be determined according to at least one of the following options:

[0315] (Opt1) The size of the bit sequence is the total number of metric instances (N ａｌｌ ) may be decided based on the following.

[0316] For example, the size of the bit sequence is N ａｌｌ It can be expressed as follows.

[0317] Total number of metric instances (N ａｌｌ The periodicity / interval of inference reports, the periodicity / interval of measurement opportunities for performance monitoring, the periodicity / interval of performance monitoring reports, etc., may be used to calculate this.

[0318] More specifically, for example, N ａｌｌ This is the ratio of the period / interval of performance monitoring reports to the period / interval of inference reports. That is, Nａｌｌ This can be expressed as (Performance monitoring report cycle / interval) ÷ ​​(Inference report cycle / interval).

[0319] Or, N ａｌｌ This is the ratio of the period / interval of performance monitoring reports to the period / interval of measurement opportunities for performance monitoring. That is, N ａｌｌ This can be expressed as (Performance monitoring report cycle / interval) ÷ ​​(Performance monitoring measurement opportunity cycle / interval).

[0320] (Opt2) The size of the bit sequence may be determined based on the reported information (e.g., the number of valid metric instances).

[0321] For example, the number of metric instances (N) for which UE is enabled. ｖａｌｉｄ When reporting ), the size of the bit sequence is N ｖａｌｉｄ It can be expressed as follows.

[0322] (Opt3) The size of the bit sequence may be determined based on the number of predicted time instances per inference report (the number of predicted time instances within a single inference report). The number of predicted time instances per inference report is, for example, N ｐ＿ｐｅｒ＿ｉｒ It may be expressed as follows.

[0323] (Opt4) The size of the bit sequence may be predefined by the specification, set / indicated by upper layer signaling / physical layer signaling, or determined according to UE capabilities.

[0324] (Opt5) The bit size of the ratio / probability may be determined based on the combination of Opt1 to Opt4 described above.

[0325] For example, the size of the bit sequence is N ａｌｌ *N ｐ＿ｐｅｒ＿ｉｒ It can be expressed as follows.

[0326] Alternatively, the size of the bit sequence is N ｖａｌｉｄ *N ｐ＿ｐｅｒ＿ｉｒ It can be expressed as follows.

[0327] <<Variations>> The above example shows how bit values ​​are assigned / assigned / associated for each metric instance [type], but is not limited to this. For example, a set of bits that has at least one meaning of validity / accuracy may be defined (associated / associated) for a single metric instance. The UE may report such set of bits [for each metric instance].

[0328] For example, if the set of bits is "XXX" (for example, a bit value of "11" may indicate invalidity), it may mean that the metric instance is valid / invalid.

[0329] For example, if the set of bits is "XXX" (e.g., bit value = "00" or "01"), it may mean that the metric instance is accurate. In this case, two conditions may be defined to determine which bit value is accurate. The UE may report to the NW whether either of the two upper limits for determining / identifying an accurate metric instance has been met.

[0330] In other words, by combining bit values ​​and conditions, it is possible to represent (identify) more multi-level metric instances. This allows the network to implement a more detailed LCM.

[0331] For example, if the set of bits is "XXX" (e.g., bit value = "10"), it may mean that the metric instance is inaccurate.

[0332] In this way, it is possible to determine / formulate any [type] of metric instance based on the set of bits.

[0333] According to this embodiment, the content of the bit sequence corresponding to the metric instance being reported becomes clear. Based on the bit sequence reported by the UE, the NW can appropriately recognize and determine which metric instances satisfy the conditions (whether the metric instance is accurate / inaccurate / valid / invalid).

[0334] <Supplement> <<Notification of Information from UE>> Notification of any information from the UE to the NW in the above embodiments (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0335] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0336] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0337] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0338] <<Regarding the application of each embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS; - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0339] The above-mentioned specific UE capabilities may indicate at least one of the following: • Support for the above-mentioned specific processing / operation / control / assumment / information; • Support for LCM in the UE-side model; • Support for UE-assisted performance monitoring; • Support for beam prediction / CSI prediction / cell prediction using AI / ML [UE-side] models; • Support for Set B / Set A / Set P; • Number of supported metric instances; • Supported specific parameters (parameters for calculating performance metrics).

[0340] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0341] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0342] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.

[0343] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal comprising: a control unit that performs a first measurement for reporting inference results and a second measurement for performance monitoring and obtains a prediction result corresponding to a predicted time instance from the first measurement; and a transmission unit that transmits the inference result report including the prediction result, wherein the control unit calculates a metric instance based on the prediction result and the second measurement. [Note 2] The terminal according to Note 1, wherein the control unit determines at least one of the validity and accuracy of the metric instance based on certain conditions. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit is controlled to report a ratio of the number of valid / accurate metric instances to the number of certain metric instances, or the number of valid / accurate metric instances. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit is controlled to report a bit sequence corresponding to whether a metric instance satisfies certain conditions.

[0344] (Wireless Communication System) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof.

[0345] Figure 8 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0346] Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0347] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0348] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0349] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0350] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[0351] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

[0352] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

[0353] Furthermore, the user terminal 20 may communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0354] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0355] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0356] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0357] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0358] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0359] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0360] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each user terminal 20.

[0361] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0362] The base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0363] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0364] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0365] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0366] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0367] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0368] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0369] PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0370] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0371] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, the DL-RS may include a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc.

[0372] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0373] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0374] (Base Station) Figure 9 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0375] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0376] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0377] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 120, transmitting / receiving antenna 130, and transmission path interface 140. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 120. The control unit 110 may also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of wireless resources, etc.

[0378] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0379] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0380] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0381] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0382] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0383] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.

[0384] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0385] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

[0386] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.

[0387] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0388] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0389] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0390] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0391] The base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0392] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0393] The transmitting / receiving unit 120 may transmit signals for a first measurement for reporting inference results and a second measurement for performance monitoring. The transmitting / receiving unit 120 may receive a metric instance calculated by the terminal based on the prediction result corresponding to the predicted time instance obtained from the first measurement and the second measurement.

[0394] (User Terminal) Figure 10 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0395] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0396] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0397] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

[0398] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0399] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0400] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0401] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0402] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0403] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0404] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0405] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0406] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

[0407] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation into a baseband signal, etc. on the signal in the radio frequency band received by the transceiver antenna 230.

[0408] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0409] The transceiver unit 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), reception quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0410] Note that the measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. The channel measurement resources may be, for example, non-zero power (Non Zero Power (NZP)) CSI-RS resources. Also, the measurement unit 223 may derive interference measurements for CSI calculation based on interference measurement resources. The interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-interference measurement (Interference Measurement (IM)) resources, etc. Note that CSI-IM may also be called CSI-interference management (Interference Management (IM)), or may be mutually read as zero power (Zero Power (ZP)) CSI-RS. In the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be mutually read.

[0411] Note that the transmission unit and reception unit of the user terminal 20 in the present disclosure may be constituted by at least one of the transmission / reception unit 220 and the transmission / reception antenna 230.

[0412] The control unit 210 may perform at least a part of the processing of the control unit in the above supplementary note.

[0413] The transmission / reception unit 220 may perform at least a part of the processing of the transmission unit / reception unit in the above supplementary note.

[0414] (Hardware Configuration) Note that the block diagrams used in the description of the above embodiment show functional unit blocks. These functional blocks (components) are realized by an arbitrary combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly connected (for example, using wired, wireless, etc.), and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices. [[ID=##]] [[ID=##]]

[0415] Here, functions include, but are not limited to, judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, notification (broadcasting), notification (notifying), communication (communicating), forwarding, configuration (configuring), reconfiguration (reconfiguring), allocation (allocating, mapping), assignment (assigning), etc. For example, a functional block (component) that functions as transmission may be referred to as a transmission unit (transmitting unit), a transmitter, etc. In any case, as described above, the realization method is not particularly limited.

[0416] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 11 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0417] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0418] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.

[0419] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or control at least one of reading and writing data in the memory 1002 and storage 1003.

[0420] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0421] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0422] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0423] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

[0424] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated transmitting unit 120a (220a) and receiving unit 120b (220b).

[0425] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0426] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0427] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0428] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0429] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0430] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0431] Here, the neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0432] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

[0433] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using minislots may be called a PDSCH (PUSCH) mapping type B.

[0434] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0435] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0436] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0437] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0438] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0439] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0440] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0441] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0442] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0443] Note that one or more RBs may be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.

[0444] Also, a resource block may be composed of one or more resource elements (Resource Element (RE)). For example, 1 RE may be a radio resource region of 1 sub-carrier and 1 symbol.

[0445] A bandwidth part (Bandwidth Part (BWP)) (which may also be referred to as a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (common resource blocks) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. The PRB is defined in a certain BWP and may be numbered within the BWP.

[0446] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be set within one carrier for the UE.

[0447] At least one of the set BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0448] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

[0449] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.

[0450] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0451] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0452] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0453] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0454] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0455] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0456] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0457] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not providing notification of the specified information or by providing notification of other information).

[0458] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0459] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0460] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0461] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0462] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0463] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0464] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0465] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0466] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0467] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0468] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset may be interpreted interchangeably.

[0469] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0470] In this disclosure, terms such as “Base Station (BS),” “wireless base station,” “fixed station,” “NodeB,” “eNB (eNodeB),” “gNB (gNodeB),” “access point,” “Transmission Point (TP),” “Reception Point (RP),” “Transmission / Reception Point (TRP),” “panel,” “cell,” “sector,” “cell group,” “carrier,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0471] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0472] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

[0473] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0474] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0475] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0476] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0477] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0478] Figure 12 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0479] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0480] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0481] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0482] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0483] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0484] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0485] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0486] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

[0487] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include the information based on the above input.

[0488] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0489] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0490] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.

[0491] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0492] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0493] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0494] Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0495] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0496] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0497] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0498] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0499] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0500] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0501] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0502] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0503] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0504] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0505] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0506] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0507] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0508] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0509] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0510] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0511] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0512] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0513] This application is based on Japanese Patent Application No. 2025-019504, filed on February 7, 2025. All of its contents are included herein.

Claims

1. A terminal comprising: a control unit that performs a first measurement for reporting inference results and a second measurement for performance monitoring, and obtains a prediction result corresponding to a predicted time instance from the first measurement; and a transmission unit that transmits the inference result report including the prediction result, wherein the control unit calculates a metric instance based on the prediction result and the second measurement.

2. The terminal according to claim 1, wherein the control unit determines at least one of the validity and accuracy of the metric instance based on certain conditions.

3. The terminal according to claim 1, wherein the control unit is controlled to report the ratio of the number of valid / accurate metric instances to the number of a certain metric instance, or the number of valid / accurate metric instances.

4. The terminal according to claim 1, wherein the control unit controls the terminal to report a bit sequence corresponding to whether a metric instance satisfies a certain condition.

5. A wireless communication method for a terminal, comprising the steps of: performing a first measurement for reporting inference results and a second measurement for performance monitoring, obtaining a prediction result corresponding to a predicted time instance from the first measurement; and transmitting the inference result report including the prediction result, wherein the terminal calculates a metric instance based on the prediction result and the second measurement.

6. A base station comprising: a transmitting unit that transmits signals for a first measurement for reporting inference results and a second measurement for performance monitoring; and a receiving unit that receives a metric instance calculated by a terminal based on the prediction result corresponding to the prediction time instance obtained from the first measurement and the second measurement.

Images