WO2025013221A1 - Terminal, wireless communication method, and base station - Google Patents

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit that detects, through first performance monitoring, a variation in performance relating to an operation of at least one of a model, functionality, and fallback; and a transmission unit that transmits information for requesting second performance monitoring on the basis of the variation in performance. According to the one aspect of the present disclosure, preferred performance monitoring relating the model/the functionality/the fallback can be embodied.

Description

Terminal, wireless communication method and base station

This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

Successor systems to LTE (e.g., 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 under consideration.

3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Univers al　Terrestrial　Radio　Access　Network　(E-UTRAN);　Overall　description;　Stage 2　(Release　8)”, April 2010

In terms of future wireless communication technologies, the use of artificial intelligence (AI) technologies such as machine learning (ML) for network/device control and management is being considered.

Life Cycle Management (LCM) of AI models includes performance monitoring. Performance monitoring may be classified as NW transparent monitoring and NW non-transparent monitoring.

However, there has been no progress in considering how to differentiate between network-transparent and network-non-transparent monitoring, and how to perform related settings/controls. Unless these are clearly defined, appropriate monitoring will not be possible, and there is a risk that improvements in communication throughput/quality will be hindered in relation to processing based on models/functionality/fallbacks.

Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can perform suitable performance monitoring regarding models/functionality/fallbacks.

A terminal according to one aspect of the present disclosure has a control unit that detects performance fluctuations related to at least one of the operation of a model, functionality, and fallback through a first performance monitoring, and a transmission unit that transmits information for requesting a second performance monitoring based on the performance fluctuations.

According to one aspect of the present disclosure, suitable performance monitoring of models/functionality/fallbacks can be performed.

FIG. 1 is a diagram illustrating an example of a framework for managing AI models. FIG. 2 is a diagram illustrating an example of two-step performance monitoring according to the 0th embodiment. FIG. 3 is a diagram illustrating an example of control of the NW transparent monitoring according to the second embodiment. FIG. 4 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 5 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 6 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 7 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 8 is a diagram illustrating an example of a vehicle according to an embodiment.

(Application of Artificial Intelligence (AI)) Technology to Wireless Communications)
Regarding future wireless communication technologies, the use of AI technologies such as machine learning (ML) for network/device control and management is being considered.

For example, it is being considered that terminals (user equipment (UE))/base stations (BS)) will utilize AI technology to improve channel state information (CSI) feedback (e.g., reducing overhead, improving accuracy, prediction), improve beam management (e.g., improving accuracy, prediction in the time/space domain), and improve position measurement (e.g., improving position estimation/prediction).

The AI model may output at least one piece of information such as an estimate, a prediction, a selected action, a classification, etc. based on the input information. The UE/BS may input channel state information, reference signal measurements, etc. to the AI model, and output highly accurate channel state information/measurements/beam selection/position, future channel state information/radio link quality, etc.

In this disclosure, AI may be interpreted as an object (also called a target, object, data, function, program, etc.) having (implementing) at least one of the following characteristics:
- Estimation based on observed or collected information;
- making choices based on observed or collected information;
- Predictions based on observed or collected information.

In this disclosure, estimation, prediction, and inference may be interpreted as interchangeable. Also, in this disclosure, estimate, predict, and infer may be interpreted as interchangeable.

In the present disclosure, an object may be, for example, an apparatus such as a UE or a BS, or a device. Also, in the present disclosure, an object may correspond to a program/model/entity that operates in the apparatus.

In addition, in the present disclosure, an AI model may be interpreted as an object having (implementing) at least one of the following characteristics:
- Producing estimates by feeding information,
- Predicting estimates by providing information
- Discover features by providing information,
- Select an action by providing information.

In addition, in this disclosure, an AI model may refer to a data-driven algorithm that applies AI techniques to generate a set of outputs based on a set of inputs.

Furthermore, in this disclosure, AI model, model, ML model, predictive analytics, predictive analysis model, tool, autoencoder, encoder, decoder, neural network model, AI algorithm, scheme, etc. may be interchangeable. Furthermore, the AI model may be derived using at least one of regression analysis (e.g., linear regression analysis, multiple regression analysis, logistic regression analysis), support vector machine, random forest, neural network, deep learning, etc.

In this disclosure, the term "autoencoder" may be interchangeably referred to as any autoencoder, such as a stacked autoencoder or a convolutional autoencoder. The encoder/decoder of this disclosure may employ models such as Residual Network (ResNet), DenseNet, and RefineNet.

Furthermore, in this disclosure, encoder, encoding, encoding/encoded, modification/alteration/control by an encoder, compressing, compress/compressed, generating, generate/generated, etc. may be read as interchangeable terms.

Furthermore, in this disclosure, the terms decoder, decoding, decode/decoded, modification/alteration/control by a decoder, decompressing, decompress/decompressed, reconstructing, reconstruct/reconstructed, etc. may be interpreted as interchangeable.

In the present disclosure, a layer (of an AI model) may be interpreted as a layer (input layer, intermediate layer, etc.) used in an AI model. A layer in the present disclosure may correspond to at least one of an input layer, intermediate layer, output layer, batch normalization layer, convolution layer, activation layer, dense layer, normalization layer, pooling layer, attention layer, dropout layer, fully connected layer, etc.

In this disclosure, methods for training an AI model may include supervised learning, unsupervised learning, reinforcement learning, federated learning, and the like. Supervised learning may refer to the process of training a model from inputs and corresponding labels. Unsupervised learning may refer to the process of training a model without labeled data. Reinforcement learning may refer to the process of training a model from inputs (i.e., states) and feedback signals (i.e., rewards) resulting from the model's outputs (i.e., actions) in the environment with which the model interacts.

In this disclosure, terms such as generate, calculate, derive, etc. may be interchangeable. In this disclosure, terms such as implement, operate, operate, execute, etc. may be interchangeable. In this disclosure, terms such as train, learn, update, retrain, etc. may be interchangeable. In this disclosure, terms such as infer, after-training, production use, actual use, etc. may be interchangeable. In this disclosure, terms such as signal and signal/channel may be interchangeable.

Figure 1 shows an example of a framework for managing AI models. In this example, each stage related to an AI model is shown as a block. This example is also referred to as Life Cycle Management (LCM) of an AI model.

The data collection stage corresponds to the stage of collecting data for generating/updating an AI model. The data collection stage may include data organization (e.g., determining which data to transfer for model training/model inference), data transfer (e.g., transferring data to an entity (e.g., UE, gNB) that performs model training/model inference), etc.

In addition, data collection may refer to a process in which data is collected by a network node, management entity, or UE for the purpose of AI model training/data analysis/inference. In this disclosure, process and procedure may be interpreted as interchangeable. In this disclosure, collection may also refer to obtaining a data set (e.g., usable as input/output) for training/inference of an AI model based on measurements (channel measurements, beam measurements, radio link quality measurements, position estimation, etc.).

In the present disclosure, offline field data may be data collected from the field (real world) and used for offline training of an AI model. Also, in the present disclosure, online field data may be data collected from the field (real world) and used for online training of an AI model.

In the model training stage, model training is performed based on the data (training data) transferred from the collection stage. This stage may include data preparation (e.g., performing data preprocessing, cleaning, formatting, conversion, etc.), model training/validation, model testing (e.g., checking whether the trained model meets performance thresholds), model exchange (e.g., transferring the model for distributed learning), model deployment/update (deploying/updating the model to the entities that will perform model inference), etc.

In addition, AI model training may refer to a process for training an AI model in a data-driven manner and obtaining a trained AI model for inference.

Also, AI model validation may refer to a sub-process of training to evaluate the quality of an AI model using a dataset different from the dataset used to train the model. This sub-process helps select model parameters that generalize beyond the dataset used to train the model.

Also, AI model testing may refer to a sub-process of training to evaluate the performance of the final AI model using a dataset different from the dataset used for model training/validation. Note that testing, unlike validation, does not necessarily require subsequent model tuning.

In the model inference stage, model inference is performed based on the data (inference data) transferred from the collection stage. This stage may include data preparation (e.g., performing data preprocessing, cleaning, formatting, transformation, etc.), model inference, model monitoring (e.g., monitoring the performance of model inference), model performance feedback (feeding back model performance to the entity performing the model training), output (providing model output to the actor), etc.

In addition, AI model inference may refer to the process of using a trained AI model to produce a set of outputs from a set of inputs.

Also, a UE side model may refer to an AI model whose inference is performed entirely in the UE. A network side model may refer to an AI model whose inference is performed entirely in the network (e.g., gNB).

Also, a one-sided model may refer to a UE-side model or a network-side model. A two-sided model may refer to a pair of AI models where joint inference is performed. Here, joint inference may include AI inference where the inference is performed jointly across the UE and the network, e.g., a first part of the inference may be performed first by the UE and the remaining part by the gNB (or vice versa).

Also, AI model monitoring may refer to the process of monitoring the inference performance of an AI model, and may be interchangeably read as model performance monitoring, performance monitoring, etc.

Note that model registration may refer to making a model executable (registering) by assigning a version identifier to the model and compiling it into the specific hardware used in the inference phase. Model deployment may refer to distributing (or activating at) a fully developed and tested run-time image (or image of the execution environment) of the model to the target (e.g., UE/gNB) where inference will be performed.

Actor stages may include action triggers (e.g., deciding whether to trigger an action on another entity), feedback (e.g., feeding back information needed for training data/inference data/performance feedback), etc.

Note that, for example, training of a model for mobility optimization may be performed in, for example, Operation, Administration and Maintenance (Management) (OAM) in a network (NW)/gNodeB (gNB). In the former case, interoperability, large capacity storage, operator manageability, and model flexibility (feature engineering, etc.) are advantageous. In the latter case, the latency of model updates and the absence of data exchange for model deployment are advantageous. Inference of the above model may be performed in, for example, a gNB.

Depending on the use case (i.e., the function of the AI model), the entity performing the training/inference may be different. The function of the AI model may include beam management, beam prediction, autoencoder (or information compression), CSI feedback, positioning, etc.

For example, for AI-assisted beam management based on measurement reports, the OAM/gNB may perform model training and the gNB may perform model inference.

For AI-assisted UE-assisted positioning, a Location Management Function (LMF) may perform model training and the LMF may perform model inference.

For CSI feedback/channel estimation using autoencoders, the OAM/gNB/UE may perform model training and the gNB/UE may perform model inference (jointly).

For AI-assisted beam management or AI-assisted UE-based positioning based on beam measurements, the OAM/gNB/UE may perform model training and the UE may perform model inference.

Note that model activation may mean activating an AI model for a particular function. Model deactivation may mean disabling an AI model for a particular function. Model switching may mean deactivating a currently active AI model for a particular function and activating a different AI model.

Model transfer may also refer to distributing an AI model over the air interface. This may include distributing either or both of the parameters of the model structure already known at the receiving end, or a new model with the parameters. This may also include a complete model or a partial model. Model download may refer to model transfer from the network to the UE. Model upload may refer to model transfer from the UE to the network.

(Life Cycle Management (LCM))
In future wireless communication systems (e.g., Rel. 18 and later), the introduction of multiple LCMs is being considered.

The multiple LCMs may be a functionality-based LCM and a model-ID-based LCM. The functionality-based LCM may be referred to as a functionality-based LCM, and the model-ID-based LCM may be referred to as a model-ID-based LCM.

In functionality-based LCM, the network (e.g., a base station/network node) may instruct operations related to the functionality of the AI/ML (e.g., at least one of activation, deactivation, fallback operation, and switch).

The UE may perform model-level LCM (e.g., model switching and/or model selection) within the indicated functionality.

The functionality may be transparent as to which models are activated/deactivated.

UE Capability information reports may be used to indicate supported functionality.

In model-ID-based LCM, the network (e.g., a base station/network node) may instruct an operation related to an individual AI/ML model (e.g., at least one of activation, deactivation, fallback operation, and switch) by the model ID.

The UE may perform model-level LCM (e.g., at least one of model switching and model selection) based on instructions from the network.

A model may be defined in the network by a model identifier (ID).

(functionality identification)
As a procedure for identifying the functionality, for example, the UE may report certain conditions in the UE capabilities (capability information), in which case the NW may configure the corresponding functionality based on the reported conditions.

Here, functionality may represent features/feature groups (Feature Groups (FGs)) available in the AI/ML that are enabled by a certain setting, for example, a set of RRC parameters/LPP parameters. The setting may be supported based on conditions indicated by the UE capabilities. Furthermore, functionality may represent units that the NW can control on the UE side in the operation of LCM (monitoring (checking performance)/activation/deactivation/switching/fallback/update).

In this disclosure, functionality may refer to the use of the model or the physical meaning of the model's inputs/outputs. Multiple models may have the same functionality.

The operation of the LCM based on the functionality may be controlled based on the settings of features/feature groups available in the AI/ML described above. Here, signaling (signaling for activation/deactivation/switching) to support the operation of the LCM based on the functionality is considered.

The UE may also report applicable functionality updates. For example, a mechanism for updating the applicable models after identifying the models needs to be considered.

(model identification)
A model identified by a model ID may be associated with, for example, settings/conditions/additional conditions (specific scenarios, sites, data sets, etc.). A model may represent a unit that the NW can control on the UE side in the operation (activation/deactivation/switching) of the LCM.

A model ID may refer to an identifier for a model (or a set of models). Multiple models may be assigned the same model ID in an actual deployment. In this case, these models may be treated as the same model, even though they are actually different models (e.g., they may have different number of layers, etc.).

In addition, in this disclosure, the model ID may be interchangeably read as a meta information (or a set of meta information) ID. The meta information (or meta information ID) may be associated with information regarding the applicability of the model/functionality, the environment, the UE/gNB settings, etc.

The operation of the LCM based on the model ID may be controlled based on the identified model, where the model may be associated with specific settings/conditions regarding UE capabilities of features/feature groups available in the AI/ML and additional conditions determined/identified between the UE side and the NW side.

Furthermore, it is expected that the identification process and control unit will be different between the functionality-based LCM and the model ID-based LCM. Here, it is being considered to share the same activation/deactivation/switching procedures (or to use the same/similar procedures) between the functionality-based LCM and the model ID-based LCM.

In addition, the following types of model identification procedures are being considered:
Type A: Model information and model ID are associated without signaling. The UE reports the supported model IDs to the NW. That is, the mapping between the model ID and the model information is identified to the NW and the UE without signaling. The NW and the UE identify the corresponding model information based on the received model ID.
Type B1: Model information is reported from the UE to the NW via the air interface (signaling). Model identification is initiated by the UE and the NW assists (or takes responsibility for) the remaining steps of model identification. During model identification, a model ID may be assigned to the model.
Type B2: Model information is reported from the NW to the UE via the air interface (signaling). Model identification is initiated by the NW and the UE responds for the remaining steps of model identification. During model identification, a model ID may be assigned to the model.

(Transparency of performance monitoring to the network)
In order to enable flexible/efficient control, the present inventors consider classifying performance monitoring into NW transparent monitoring and NW non-transparent monitoring.

Network-transparent monitoring may mean that the UE evaluates the model/functionality based on criteria determined/defined by the UE. In network-transparent monitoring, the criteria determined/defined by the UE may or may not be transparent to the network (e.g., by notifying related information). In network-transparent monitoring, the result of the evaluation/judgment based on the criteria may not be transparent to the network.

NW non-transparent monitoring may mean at least one of the following:
The UE evaluates the model/functionality based on criteria defined in the standard or determined/configured/instructed by the NW;
- NW evaluates the model/functionality based on information reported from the UE (e.g., monitored metrics, inference results).

Network-transparent monitoring may also be called UE autonomous monitoring, network-independent monitoring, etc. Network-non-transparent monitoring may also be called UE non-autonomous monitoring, network-dependent monitoring, etc.

The advantages of NW transparent monitoring are, for example:
- Capabilities are not disclosed to other vendors. UE vendors do not report model/functionality capabilities to the NW, so they can hide performance details from NW vendors.
No need to define metrics: There is no need to define metrics in the standard. Some performance metrics are difficult to define (e.g., input data distribution), so not having to define them is an advantage.
Reduced reporting overhead: UE does not need to report performance metrics/events prior to evaluation.

In addition, in this disclosure, an event and the occurrence of an event may be interpreted as interchangeable. Also, in this disclosure, an event, an event before evaluation, an event during evaluation, an event after evaluation, etc. may be interpreted as interchangeable.

On the other hand, when using network-transparent monitoring, the network cannot know how good the model/functionality is, making it difficult to make decisions on activating (deactivating) the model/functionality.

Advantages of NW non-transparent monitoring include, for example:
The NW has some idea of how good the models/functionality are and can take appropriate decisions on (de)activation of the models/functionality.

On the other hand, when using non-transparent network monitoring, performance is disclosed to other vendors, metrics must be defined in standards, and reporting overhead is required.

Note that performance monitoring, for which specific procedures are prescribed in the standard, is considered to be network non-transparent monitoring, and the specific procedures for network transparent monitoring are considered to depend on the UE implementation.

Regarding the above-described network-transparent monitoring and network-non-transparent monitoring, how to use them differently and how to perform related settings/controls have not yet been considered. Unless these are clearly defined, appropriate monitoring cannot be performed, and there is a risk that improvements in communication throughput/communication quality will be hindered in relation to processing based on models/functionality/fallbacks.

The inventors therefore came up with a setting/control method suitable for network transparent monitoring, network non-transparent monitoring, etc.

Embodiments of the present disclosure will now be described in detail with reference to the drawings. The wireless communication methods according to the embodiments may be applied independently or in combination.

(Various changes in interpretation, etc.)
In the present disclosure, "A/B" and "at least one of A and B" may be interpreted as interchangeable. Also, in the present disclosure, "A/B/C" may mean "at least one of A, B, and C."

In this disclosure, terms such as notify, activate, deactivate, indicate, select, configure, update, and determine may be read as interchangeable terms. In this disclosure, terms such as support, control, capable of control, operate, and capable of operating may be read as interchangeable terms.

In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In this disclosure, Medium Access Control (MAC Control Element (CE)), update commands, activation/deactivation commands, etc. may be interchangeable.

In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocols (e.g., NR Positioning Protocol A (NRPPa)/LTE Positioning Protocol (LPP)) messages), or a combination of these.

In the present disclosure, the MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

In the present disclosure, the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.

In the present disclosure, monitoring, channel measurement/estimation, etc. may be performed using a reference signal (RS). The RS may include at least one of, for example, a channel state information reference signal (CSI-RS), a synchronization signal (SS), a synchronization signal/physical broadcast channel (SS/PBCH) block, a demodulation reference signal (DMRS), a sounding reference signal (SRS), etc.

In this disclosure, the measured/reported RS may refer to the RS measured/reported for a CSI report. In this disclosure, the RS index may be a CSI-RS Resource Indicator (CSI-RS Resource Indicator (CRI)), a SS/PBCH Block Resource Indicator (SSBRI), etc.

In this disclosure, functionality, function, functionality ID, model, and model ID may be interpreted interchangeably.

In this disclosure, model/functionality/fallback operation or operation of model/functionality/fallback may be read interchangeably as model/functionality/fallback.

In the present disclosure, the operation of the model/functionality may include, for example, at least one of model/functionality activation, deactivation, switching, fallback operation, update, etc. In the present disclosure, the fallback operation may include at least one of an operation based on information (e.g., input) used when applying the corresponding AI function, an operation based on information (e.g., input) used when applying the corresponding AI function and a non-AI function, etc.

In the present disclosure, monitoring and performance monitoring may be interchangeably read. NW transparent monitoring may be interchangeably read as first monitoring, first type monitoring, etc. NW non-transparent monitoring may be interchangeably read as second monitoring, second type monitoring, etc.

In this disclosure, fluctuation, change, transition, etc. may be interpreted interchangeably.

(Wireless communication method)
<Tenth embodiment>
The 0th embodiment relates to a two-step performance monitoring that combines NW transparent monitoring and NW non-transparent monitoring.

According to two-step performance monitoring, the UE normally performs network-transparent monitoring, and when it detects a performance fluctuation, it controls itself to perform network-non-transparent monitoring.

FIG. 2 is a diagram showing an example of two-step performance monitoring according to the 0th embodiment. In this example, the UE is configured to perform non-transparent network monitoring at a relatively long period.

The UE also performs NW transparent monitoring at a period shorter than the period of NW non-transparent monitoring. The UE performs the NW transparent monitoring based on the reception of a reference signal. The UE requests NW non-transparent monitoring based on the performance monitored by the NW transparent monitoring (for example, when the performance fluctuation is large, or when the performance fluctuation exceeds a threshold). This request will be described later in the first embodiment. Also, the setting/measurement method for NW transparent monitoring will be described later in the second embodiment.

The UE may determine the above threshold based on predefined rules, based on UE capabilities, or based on parameters instructed/set by the NW.

If there is no change in performance based on the NW non-transparent monitoring, the UE continues the NW transparent monitoring. The UE may perform NW non-transparent monitoring in the above-mentioned long period regardless of the result of the NW transparent monitoring. The UE may perform both NW non-transparent monitoring and NW transparent monitoring at the same time, or may perform (prioritize) one of them (for example, may prioritize NW non-transparent monitoring).

In Figure 2, when the UE detects a change in performance via network-transparent monitoring at time t, it requests network-non-transparent monitoring from the network and then performs network-non-transparent monitoring. This network-non-transparent monitoring can be performed at a timing different from the above-mentioned long period that is originally set.

The period of NW non-transparent monitoring and the period of NW transparent monitoring are not limited to the relationship shown in FIG. 2. They may be the same, or the former may be longer than the latter, or the latter may be longer than the former. In addition, NW non-transparent monitoring does not necessarily have to be configured to be performed periodically/semi-persistently (for example, it may be configured/instructed to be performed aperiodically). The UE may assume that there are constraints regarding the length relationship between the periods of NW non-transparent monitoring and NW transparent monitoring, their time domain behavior (for example, periodic, semi-persistent, aperiodic), etc. For example, the UE may determine the setting of NW transparent monitoring (e.g., period) from the setting of NW non-transparent monitoring (e.g., period) based on the constraint.

According to the 0th embodiment described above, for example, it is possible to reduce the overhead of reporting non-transparent network monitoring compared to when non-transparent network monitoring is performed frequently, while quickly responding to performance abnormalities.

First Embodiment
The first embodiment relates to a request for performance monitoring (NW non-transparent monitoring) based on NW transparent monitoring.

[Performance fluctuation possibility report]
The UE may report information on the possibility/probability of the performance of the model/functionality/fallback operation fluctuating (e.g., may be called performance fluctuation possibility information, performance fluctuation possibility report, etc.) to the NW. This information may be expressed, for example, as a hard value (which may be called a hard decision value) or a soft value (which may be called a soft decision value). The hard value may be expressed as a binary value (0 or 1). The soft value may be expressed as several candidate values (0, 0.1, 0,2, ..., 0.9, 1.0) or may be expressed as a real value.

The closer the value indicated by the information is to a first value (e.g., 0), the lower the possibility of performance fluctuation. The closer the value indicated by the information is to a second value (e.g., 1), the higher the possibility of performance fluctuation.

The UE may decide which value (e.g., a hard value or a soft value) to report as the performance variability information based on predefined rules, on the UE capabilities, or on the parameters that are instructed/set.

Performance variability information may include information to identify associated (or performance varying) model/functionality/fallback behavior.

The NW may trigger (perform) NW non-transparent monitoring for the UE based on the performance variation possibility information reported from the UE. For example, if the possibility indicated by the performance variation possibility information reported from the UE exceeds a threshold, the NW may trigger NW non-transparent monitoring for the UE. In other words, the report of the above-mentioned performance variation possibility information may correspond to a request for NW non-transparent monitoring.

[Performance measurement/report request]
The UE may request (or send information indicating the request (hereinafter also referred to as request information)) measurement/reporting of performance of the model/functionality/fallback operation.

The request information may include information for identifying the model/functionality/fallback behavior to be measured/reported (in other words, the measurement/report is requested). The requested model/functionality/fallback behavior may be the same as or different from the model/functionality/fallback behavior that caused the request (e.g., the model/functionality/fallback behavior whose performance is monitored by network transparent monitoring, or the model/functionality/fallback behavior indicated by performance variability information). If they are the same, the request information does not need to include information for identifying the requested model/functionality/fallback behavior.

The UE may transmit the above-mentioned performance variation possibility information and request information simultaneously or at different times.

[Related Timers]
When the UE transmits the performance variation possibility information/request information, the UE may start a specific timer.

The UE may allow the transmission of performance variation possibility information/request information only when the specific timer is not running. This makes it possible to prevent the performance variation possibility information/request information from being transmitted too frequently. The specific timer may be managed in the MAC layer (MAC entity).

The UE may stop (or suspend) the corresponding or all network transparent monitoring when the particular timer is running.

The UE may determine information about the particular timer (e.g., the length of the timer) based on predefined rules, based on UE capabilities, or based on instructed/set parameters.

Note that a different timer may be used for each model/functionality/fallback operation (or an individual timer may be used for a specific model/functionality/fallback operation), or the same timer may be used for multiple model/functionality/fallback operations.

According to the first embodiment described above, it is possible to transmit an appropriate request for NW non-transparent monitoring based on NW transparent monitoring.

Second Embodiment
The second embodiment relates to NW transmission type monitoring.

[Reference signal request]
In order to determine whether to transmit the performance variation possibility information/request information described in the first embodiment, the UE may request the configuration/measurement of a specific reference signal (RS) (may transmit information indicating the request (hereinafter, also referred to as RS request information)). Requesting the configuration/measurement of the RS may be interpreted as requesting the RS.

In addition, in this disclosure, "detecting performance fluctuations in model/functionality/fallback operation," "determining whether to send performance fluctuation possibility information/request information (described in the first embodiment)," "performing performance fluctuation monitoring," "performing network transparent monitoring," etc. may be read as interchangeable.

Hereinafter, the specific RS will also be referred to as an RS for monitoring performance fluctuations, an RS for determining whether to send request information, etc. The RS for monitoring performance fluctuations may be used only for monitoring performance fluctuations, or may be used for other purposes.

FIG. 3 is a diagram showing an example of the control of the network transparent monitoring according to the second embodiment. The control of the network transparent monitoring may be performed based on at least one of the steps shown in the figure. Note that some steps may be omitted.

In step S101, the UE may be notified of information regarding permission for the request of the performance variation monitoring RS from the NW. The information regarding the permission may be set in the UE using request setting information of the performance variation monitoring RS.

In addition, instead of/in addition to being notified by the NW, the UE may determine the information based on a predefined procedure.

The information regarding the authorization may include information regarding at least one of the following:
When/what RS request information can be sent,
What RS (e.g. CSI-RS/PRS/SSB) can be requested?
- What time periods (windows, gaps, etc.) can be requested?

The UE may be expected to measure the RS for monitoring performance variations within the above window/gap.

In step S102, the UE may transmit a request for a performance variation monitoring RS (RS request information) to the NW. The RS request information may include information on at least one of the following:
Information about the (desired) RS (e.g., ID of the RS configuration, ID of the RS resource);
Information about the (desired) time period (window, gap),
- ID related to RS request information,
Information regarding the number of measurements requested/maximum number of measurements,
- Information regarding the required measurement period.

In step S103, the UE may receive a confirmation from the NW regarding the configuration/reconfiguration/instruction/activation/request of the RS for monitoring performance fluctuations.

In step S104, the UE may receive/measure the performance variation monitoring RS corresponding to the notification in step S103, and perform performance variation monitoring based on this.

In step S105, the UE may end reception/measurement of the performance variation monitoring RS. The end of reception/measurement of the performance variation monitoring RS may be based on a notification from the NW, or may be determined by the UE.

[Detection techniques associated with network-transmitting monitoring]
The UE may be instructed/configured by the NW to use an approach for determining whether to transmit the performance variation possibility information/request information described in the first embodiment. The UE may detect the performance variation of the model/functionality/fallback operation based on the approach (detection method). The approach (detection method) may be at least one of the following:
Detection based on measurements (or input information) used in applying the model/functionality (may be called input distribution based detection);
Detection based on information derived (inferred) from models/functionality (may be called power distribution based detection);
Detection based on a model for detection (or a detection-specific model).

The detection-only model may be an additional model installed (configured/available) in the UE, whose sole purpose is to detect performance variations.

According to the second embodiment described above, the UE can appropriately perform control related to network transparent monitoring.

Third Embodiment
The third embodiment relates to the number of monitored models/functionality/fallbacks. Note that "monitored" may be read as "(UE) monitors" interchangeably.

The UE may report information regarding the maximum number of models/functionality/fallback operations it will monitor to the NW. This information may be included in the UE capability information. The UE may not be expected to monitor more than this maximum number of models/functionality/fallback operations.

In addition, in this disclosure, the maximum number may be interpreted interchangeably as the number supported, the number set, the number, etc.

The UE may report information regarding the maximum number of models/functionality/fallback operations to monitor to determine whether to transmit the performance variability information/request information described in the first embodiment to the NW. The information may be included in the UE capability information. The UE may not be expected to monitor a number of models/functionality/fallback operations that exceeds the maximum number to determine whether to transmit the performance variability information/request information described in the first embodiment.

The UE may report information to the NW regarding the maximum number of models/functionality/fallback operations that are configured/instructed (or supported) for the transmission of performance metrics/events. The information may be included in the UE capability information. For the transmission of performance metrics/events, the UE may not be expected to monitor more than the maximum number of models/functionality/fallback operations.

In addition, in this disclosure, "measure/report performance of model/functionality/fallback operation," "determine sending performance metrics/events," "measure performance metrics/events," "report performance metrics/events," "perform non-transparent network monitoring," etc. may be read as interchangeable.

Furthermore, in the present disclosure, reporting a performance metric/event may mean reporting that the performance of the corresponding model is greater than or less than a threshold. The threshold may be predefined in a standard, may be determined based on UE capabilities, or may be set/instructed to the UE by higher layer signaling/physical layer signaling. Also, the event to be reported may be determined by comparing the performance of the model with the threshold for a particular period of time.

In the third embodiment, when a UE reports information regarding any of the maximum numbers described above, the NW may control the UE to configure/instruct it to monitor the operation of models/functionality/fallbacks up to the maximum number.

Also, when configured/instructed to monitor a number of models/functionality/fallback operations exceeding the maximum number, this may mean that the UE selects and monitors the model/functionality/fallback operations up to the maximum number, and does not monitor the model/functionality/fallback operations that are not selected. The selection may be performed based on information (e.g., ID, priority) associated with the model/functionality/fallback operation. The associated information may be predetermined in a standard, may be determined based on UE capabilities, or may be set/instructed to the UE by higher layer signaling/physical layer signaling.

According to the third embodiment described above, the UE can appropriately report the number of models/functionalities/fallbacks to be monitored, and the NW can appropriately determine control for the UE based on the number.

Fourth Embodiment
A fourth embodiment relates to model/functionality/fallback activation restriction.

As mentioned above, when using network-transparent monitoring, it is difficult for the network to know how good the model/functionality is. Therefore, it is difficult for the network to make appropriate decisions such as activating, switching, and deactivating models/functionality without network-non-transparent monitoring.

In other words, it is preferable that network non-transparent monitoring is performed before model/functionality activation, switching, deactivation, etc.

The inventors have therefore devised a fourth embodiment. According to the fourth embodiment, it is ensured that the UE performs non-transparent network monitoring before instructing the operation of the model/functionality.

In a fourth embodiment, the UE may not be expected to receive or apply the model/functionality/fallback behavior indication unless certain conditions are met. The certain conditions may for example be at least one of the following:
The UE has reported performance metrics for the corresponding model/functionality/fallback operation,
The UE reports the occurrence of an event related to the corresponding model/functionality/fallback behavior.

Note that the above related events may be limited to events whose occurrence is determined by performance metrics of the model/functionality/fallback behavior.

The above phrase "if a particular condition is not met" may be interpreted interchangeably as "if a particular condition is not met within the most recent period X," "until a period Y has elapsed since a particular condition was not met within the most recent period X," "until a period Y has elapsed since a particular condition was not met within the most recent period X," etc.

The above phrase "reported the occurrence of a performance metric/event" may be read as "reported the occurrence of a performance metric/event N times within a (recent) period Z."

Here, the period X(Y,Z) may mean a period expressed by X(Y,Z) unit times. The unit times may be, for example, any one of a symbol, a slot, a subframe, a millisecond (ms), etc., or a combination of these.

The period X(Y,Z) may be managed based on a timer.

X/Y/Z/N may be any real number/integers equal to or greater than 0 (or 1), may be predefined in a standard, may be determined based on UE capabilities, or may be set/instructed to the UE by higher layer signaling/physical layer signaling.

According to the fourth embodiment described above, it is possible to ensure that the UE performs non-transparent network monitoring, for example, before model/functionality activation, switching, deactivation, etc.

<Additional Information>
[Notification of information to UE]
In the above-described embodiment, any information may be notified to the UE (from the NW) (in other words, any information received from the BS in the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

When the above notification is performed by a MAC CE, the MAC CE may be identified by including in the MAC subheader a new Logical Channel ID (LCID) that is not specified in existing standards.

When the notification is made by a DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

Furthermore, notification of any information to the UE in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically.

[Information notification from UE]
In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission/report 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), a specific signal/channel (e.g., PUCCH, PUSCH, reference signal), or a combination thereof.

If the notification is made by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.

If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

Furthermore, in the above-mentioned embodiments, notification of any information from the UE may be performed periodically, semi-persistently, or aperiodically.

[Application of each embodiment]
At least one of the above-mentioned embodiments may be applied when a specific condition is met, which may be specified in a standard or may be notified to a UE/BS using higher layer signaling/physical layer signaling.

At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

The specific UE capabilities may indicate at least one of the following:
Supporting specific processes/actions/controls/information for at least one of the above embodiments (e.g. performance variability reporting, requests for performance measurements/reports, maximum number of models/functionality/fallback actions to monitor for the third embodiment, limitations for the fourth embodiment);
Support two-step performance monitoring.

Furthermore, the above-mentioned specific UE capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities per Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

The above-mentioned specific UE capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

Furthermore, at least one of the above-mentioned embodiments may be applied when the UE configures/activates/triggers specific information related to the above-mentioned embodiments (or performs the operations of the above-mentioned embodiments) by higher layer signaling/physical layer signaling. For example, the specific information may be information indicating the activation of LCM based on a model/functionality ID, any RRC parameters for a specific release (e.g., Rel. 18/19), etc.

If the UE does not support at least one of the above specific UE capabilities or the above specific information is not configured, the UE may apply, for example, the behavior of Rel. 15/16/17.

(Additional Note)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix 1]
a control unit that detects, via a first performance monitoring, a performance variation related to the operation of at least one of the model, the functionality, and the fallback;
A terminal having a transmitting unit that transmits information for requesting second performance monitoring based on the fluctuation in performance.
[Appendix 2]
2. The terminal according to claim 1, wherein the transmission unit transmits information regarding a possibility that performance related to the at least one operation will fluctuate as information for requesting the second performance monitoring.
[Appendix 3]
3. The terminal according to claim 1 or 2, wherein the transmitting unit transmits information for requesting a reference signal for detecting a fluctuation in performance related to the at least one operation.
[Appendix 4]
4. The terminal according to claim 1, wherein the control unit detects a fluctuation in performance related to the at least one operation based on a set detection method.

(Additional Note)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix 1]
a transmitter for transmitting information regarding a maximum number of at least one of a model, a functionality, and a fallback to be monitored;
and a control unit that performs control not to monitor the at least one operation in a number exceeding the maximum number.
[Appendix 2]
2. The terminal of claim 1, wherein the transmission unit transmits the information regarding a maximum number of the at least one operation to monitor to detect a fluctuation in performance related to the at least one operation.
[Appendix 3]
3. The terminal according to claim 1 or 2, wherein the control unit does not receive or apply an instruction for the at least one operation if a certain condition is not met.
[Appendix 4]
4. The terminal of claim 3, wherein the particular condition is reporting a corresponding performance metric of the at least one operation or an occurrence of a related event.

(Wireless communication system)
A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination of these methods.

FIG. 4 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may simply be referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) specified by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), or the like.

The wireless communication system 1 may also 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)), etc.

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.

The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (e.g., dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged within the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

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).

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

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

The multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which corresponds to the upper station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which corresponds to a relay station, may be called an IAB node.

The base station 10 may be connected to the core network 30 via another base station 10 or directly. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), etc.

The core network 30 may include network functions (Network Functions (NF)) such as, for example, a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that multiple functions may be provided by one network node. In addition, communication with an external network (e.g., the Internet) may be performed via the DN.

The user terminal 20 may be a terminal that supports at least one of the communication methods such as LTE, LTE-A, and 5G.

In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), 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-FDMA), etc. may be used.

The radio access method may also be called a waveform. Note that in the wireless communication system 1, other radio access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL radio access methods.

In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

In addition, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted via PDSCH. User data, upper layer control information, etc. may also be transmitted via PUSCH. Furthermore, Master Information Block (MIB) may also be transmitted via PBCH.

Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.

Note that the DCI for scheduling the PDSCH may be called a DL assignment or DL DCI, and the DCI for scheduling the PUSCH may be called a UL grant or UL DCI. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

A control resource set (COntrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH. The CORESET corresponds to the resources to search for DCI. The search space corresponds to the search region and search method of PDCCH candidates. One CORESET may be associated with one or multiple search spaces. The UE may monitor the CORESET associated with a search space based on the search space configuration.

A search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in this disclosure may be read as interchangeable.

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

Note that in this disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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, as the DL-RS, 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. may be transmitted.

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 an SS (PSS, SSS) and a PBCH (and a DMRS for PBCH) may be called an SS/PBCH block, an SS Block (SSB), etc. In addition, the SS, SSB, etc. may also be called a reference signal.

In addition, in the wireless communication system 1, a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific Reference Signal).

(Base station)
5 is a diagram showing an example of a configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may each be provided in one or more units.

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the base station 10 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

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

The transceiver 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 transceiver unit 120 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.

The transceiver 120 may be configured as an integrated transceiver, or may be composed of a transmitter and a receiver. The transmitter may be composed of a transmission processing unit 1211 and an RF unit 122. The receiver may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

The transmitting/receiving antenna 130 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

The transceiver 120 may form at least one of the transmit beam and receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data and control information obtained from the control unit 110 to generate a bit string to be transmitted.

The transceiver 120 (transmission processor 1211) may perform transmission processing 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 on the bit string to be transmitted, and output a baseband signal.

The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

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

The transceiver 120 (reception 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 (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.

The transceiver 120 (measurement unit 123) may perform measurements on 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 measure received power (e.g., Reference Signal Received Power (RSRP)), received 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.

The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes providing 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.

Note that the transmitting section and receiving section of the base station 10 in this disclosure may be configured with at least one of the transmitting/receiving section 120, the transmitting/receiving antenna 130, and the transmission path interface 140.

The transmitting/receiving unit 120 may transmit a reference signal to cause the user terminal 20 to detect a performance fluctuation related to at least one of the operations of the model, the functionality, and the fallback. The transmitting/receiving unit 120 may receive information for requesting performance monitoring, which is transmitted from the user terminal 20 based on the performance fluctuation.

The transceiver 120 may also receive information regarding the maximum number of at least one of the models, functionality, and fallback behaviors to be monitored from the user terminal 20. The control unit 110 may control the user terminal 20 to set the at least one behavior to be monitored up to the maximum number.

(User terminal)
6 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the control unit 210, the transceiver unit 220, and the transceiver antenna 230 may each include one or more.

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the user terminal 20 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception using the transceiver unit 220 and the transceiver antenna 230, measurement, etc. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.

The transceiver 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 transceiver unit 220 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.

The transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222. The reception unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

The transmitting/receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

The transceiver unit 220 may form at least one of the transmit beam and receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

The transceiver 220 (transmission processor 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on the data and control information acquired from the controller 210, and generate a bit string to be transmitted.

The transceiver 220 (transmission processor 2211) may perform transmission processing 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 on the bit string to be transmitted, and output a baseband signal.

Whether or not to apply DFT processing may be based on the settings of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, it is not necessary to perform DFT processing as the above-mentioned transmission processing.

The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

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

The transceiver 220 (reception processor 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 to acquire user data, etc.

The transceiver 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), received 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.

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 (NZP) CSI-RS resources. 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 (IM) resources, etc. CSI-IM may be called CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be read as interchangeable.

In addition, the transmitting unit and receiving unit of the user terminal 20 in this disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.

The control unit 210 may detect a performance fluctuation related to at least one of the operation of the model, the functionality, and the fallback through the first performance monitoring (e.g., NW transparent monitoring). The transceiver unit 220 may transmit information for requesting a second performance monitoring (e.g., NW non-transparent monitoring) based on the performance fluctuation.

The transceiver unit 220 may transmit information regarding the possibility of fluctuation in performance related to the at least one operation (e.g., performance fluctuation possibility information) as information for requesting the second performance monitoring.

The transceiver unit 220 may transmit information (e.g., RS request information) to request a reference signal for detecting performance fluctuations related to the at least one operation.

The control unit 210 may detect performance fluctuations related to at least one of the operations based on a configured detection method (e.g., an approach instructed/configured by the base station 10).

The transceiver 220 may also transmit information (e.g., UE capability information) regarding the maximum number of at least one of the model, functionality, and fallback operations to be monitored. The control unit 210 may perform control not to monitor the at least one operation in a number that exceeds the maximum number.

The transceiver 220 may transmit the information regarding a maximum number of the at least one operation to monitor to detect performance variations related to the at least one operation.

The control unit 210 may not receive or apply an instruction for the at least one operation if a specific condition is not met. Here, the specific condition may be that the user terminal 20 reports a performance metric of the at least one corresponding operation or the occurrence of a related event.

(Hardware configuration)
The block diagrams used in the description of the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

Here, the functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function may be called a transmitting unit, a transmitter, and the like. In either case, as mentioned above, there are no particular limitations on the method of realization.

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

In addition, in this disclosure, terms such as apparatus, circuit, device, section, and unit may be interpreted as interchangeable. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figures, or may be configured to exclude some of the devices.

For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. Furthermore, the processor 1001 may be implemented by one or more chips.

The functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, etc. For example, at least a portion of the above-mentioned control unit 110 (210), transmission/reception unit 120 (220), etc. may be realized by the processor 1001.

The processor 1001 also reads out programs (program codes), 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 according to these. The programs used are those that cause a computer to execute at least some of the operations described in the above embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks.

Memory 1002 is a computer-readable recording medium and may be composed of at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.

Storage 1003 is a computer-readable recording medium and may be composed of at least one of a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

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 called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of, for example, 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 realized by the communication device 1004. The transmitting/receiving unit 120 (220) may be implemented as a transmitting unit 120a (220a) and a receiving unit 120b (220b) that are physically or logically separated.

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).

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 may be configured using different buses between each device.

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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

(Modification)
In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be read as mutually interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, or the like.

A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed 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.

Here, the numerology may be a communication parameter that is applied to at least one of the transmission and reception of a signal or channel. The numerology may indicate, 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, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

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

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

A radio frame, subframe, slot, minislot, and symbol all represent time units when transmitting a signal. A different name may be used for radio frame, subframe, slot, minislot, and symbol. Note that the time units such as frame, subframe, slot, minislot, and symbol in this disclosure may be read as interchangeable.

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

Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. In addition, the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, 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, minislot, subslot, slot, etc.

Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

Furthermore, an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource area of one subcarrier and one symbol.

A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP. Note that "cell," "carrier," etc. in this disclosure may be read as "BWP."

Note that the above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

The names used for parameters and the like in this disclosure are not limiting in any respect. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and the various names assigned to these various channels and information elements are not limiting in any respect.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. 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 voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

In addition, information, signals, etc. may be output from a higher layer to a lower layer and/or from a lower layer to a higher layer. Information, signals, etc. may be input/output via multiple network nodes.

Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

The notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information in this disclosure may be performed 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)), etc.), Medium Access Control (MAC) signaling), other signals, or a combination of these.

The physical layer signaling may be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, using a MAC Control Element (CE).

Furthermore, notification of specified information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).

The determination may be based on a value represented by a single bit (0 or 1), a Boolean value represented by true or false, or a comparison of numerical values (e.g., with a predetermined value).

Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

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

As used in this disclosure, the terms "system" and "network" may be used interchangeably. "Network" may refer to the devices included in the network (e.g., base stations).

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", "receiving entity", etc. may be used interchangeably.

In the present disclosure, the antenna port may be interchangeably read as an antenna port for any signal/channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the resource may be interchangeably read as a resource for any signal/channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time/frequency/code/space/power resources. The spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

The above groups may include, for example, at least one of 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, a panel group, etc.

Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable.

Furthermore, in this disclosure, the terms 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 as interchangeable.

Furthermore, in this disclosure, "QCL", "QCL assumptions", "QCL relationship", "QCL type information", "QCL property/properties", "specific QCL type (e.g., Type A, Type D) characteristics", "specific QCL type (e.g., Type A, Type D)", etc. may be read as interchangeable.

In this disclosure, the terms index, identifier (ID), indicator, indication, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information (TCI state)" may be interchangeable as "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. TCI state and TCI may be interchangeable. Spatial relationship information and spatial relationship may be interchangeable.

In this disclosure, terms such as "Base Station (BS)", "Radio 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", "Component carrier", etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.

In this disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control/operate based on the information.

In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

A mobile station may also be referred to as 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 suitable terminology.

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. In addition, at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

The moving body in question refers to an object that can move, and the moving speed is arbitrary, and of course includes the case where the moving body is stationary. The moving body in question includes, but is 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, artificial satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these. The moving body in question may also be a moving body that moves autonomously based on an operating command.

The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do 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.

FIG. 8 is a diagram showing an example of a vehicle according to an 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, an RPM sensor 51, an air 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.

The drive unit 41 is composed of at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handlebar), 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.

The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an Input/Output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

Signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the motor current, a rotation speed signal of the front wheels 46/rear wheels 47 acquired by a rotation speed sensor 51, an air pressure signal of the front wheels 46/rear wheels 47 acquired by an air pressure sensor 52, a vehicle speed signal acquired by a vehicle speed sensor 53, an acceleration signal acquired by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 acquired by a brake pedal sensor 56, an operation signal of the shift lever 45 acquired by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 58.

The information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via the communication module 60, etc., to provide various information/services (e.g., multimedia information/multimedia services) to the occupants of the vehicle 40.

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

The driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving load, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., a Global Navigation Satellite System (GNSS)), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Unit (IMU), an Inertial Navigation System (INS), etc.), an Artificial Intelligence (AI) chip, and an AI processor, and one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize a driving assistance function or an autonomous driving function.

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 transmits and receives data (information) via the communication port 63 between 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, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58 that are provided on the vehicle 40.

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 an external device. For example, it transmits and receives various information to and from the external device 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 above-mentioned base station 10 or user terminal 20. The communication module 60 may also be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (it may function as at least one of the base station 10 and user terminal 20).

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

The communication module 60 receives various information (traffic information, signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60).

The communication module 60 also stores various information received from external devices in memory 62 that can be used by the microprocessor 61. Based on the information stored in 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, axles 48, various sensors 50-58, and the like provided on the vehicle 40.

Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect/embodiment of the present 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), etc.). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, the uplink channel, downlink channel, etc. may be read as the sidelink channel.

Similarly, the user terminal in this disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

In this disclosure, operations that are described as being performed by a base station may in some cases be performed by its upper node. In a network that includes 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 (such as, but not limited to, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW)), or a combination of these.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency. For example, the methods described in this disclosure present elements of various steps in an exemplary order, and are not limited to the particular order presented.

Each aspect/embodiment described in this disclosure includes 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 (x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio The present invention may be applied to systems that use Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, as well as next-generation systems that are expanded, modified, created, or defined based on these. In addition, multiple systems may be combined (for example, a combination of LTE or LTE-A and 5G, etc.).

As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to an element using a designation such as "first," "second," etc., 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 method of distinguishing between two or more elements. Thus, a reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking in a table, database, or other data structure), ascertaining, etc.

"Determining" may also be considered to mean "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

Furthermore, "judgment (decision)" may be considered to mean "judging (deciding)" resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" may be considered to mean "judging (deciding)" some kind of action. In this disclosure, "judgment (decision)" may be read as interchangeably with the actions described above.

Furthermore, in this disclosure, "determine/determining" may be interpreted interchangeably as "assume/assuming," "expect/expecting," "consider/considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interpreted interchangeably as "assumes not to do...."

In the present disclosure, "expect" may be read as "be expected". For example, "expect(s)..." (where "..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be read as "be expected...", "does... (if "..." above is a to-infinitive, a verb with "to" in it)", etc. "does not expect..." may be read as "be not expected...", "does not... (if "..." above is a to-infinitive, a verb with "to" in it)", etc. Also, "An apparatus A is not expected..." may be read as "An apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B may be a base station).

In the third embodiment, "the UE may not be expected to monitor the operation of a number of models/functionality/fallbacks that exceeds the maximum number" may be read as "the UE will not monitor the operation of a number of models/functionality/fallbacks that exceeds the maximum number."

The "maximum transmit power" referred to in this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.

As used in this disclosure, the terms "connected" and "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

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 "combined" may also be interpreted in the same way as "different."

When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added through translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are plural.

In this disclosure, terms such as "less than", "less than", "greater than", "more than", "equal to", etc. may be read as interchangeable. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative, as expressions with "ith" (i is any integer) (for example, "best" may be read as "ith best").

In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

In the present disclosure, "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", "B until A" and the like may be read as interchangeable. Note that A, B, etc. here may be replaced with appropriate expressions such as nouns, gerunds, and normal sentences depending on the context. Note that the time difference between A and B may be almost 0 (immediately after or immediately before). Also, a time offset may be applied to the time when A occurs. For example, "A" may be read interchangeably as "before/after the time offset at which A occurs." The time offset (e.g., one or more symbols/slots) may be predefined or may be identified by the UE based on signaled information.

In this disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be interpreted as interchangeable.

The invention disclosed herein has been described in detail above, but it is clear to those skilled in the art that the invention disclosed herein is not limited to the embodiments described herein. The description of the present disclosure is intended for illustrative purposes only and does not imply any limitations on the invention disclosed herein.

Claims (6)

a control unit that detects, via a first performance monitoring, a performance variation related to the operation of at least one of the model, the functionality, and the fallback;
A terminal having a transmitting unit that transmits information for requesting second performance monitoring based on the fluctuation in performance. The terminal according to claim 1, wherein the transmission unit transmits information regarding the possibility of fluctuation in performance related to the at least one operation as information for requesting the second performance monitoring. The terminal according to claim 1, wherein the transmitting unit transmits information for requesting a reference signal for detecting a performance fluctuation related to the at least one operation. The terminal according to claim 1, wherein the control unit detects a performance fluctuation related to the at least one operation based on a detection method that is set. Detecting via a first performance monitoring a performance variation related to the operation of at least one of the model, the functionality, and the fallback;
and transmitting information for requesting second performance monitoring based on the fluctuation in performance. A transmitter for transmitting a reference signal for causing a terminal to detect a performance fluctuation related to at least one of the operation of a model, a functionality, and a fallback;
A base station comprising: a receiving unit that receives information for requesting performance monitoring, the information being transmitted from the terminal based on fluctuations in the performance.

Images