Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure comprises: a reception unit that receives information relating to an ID associated with a deployment or a scenario, or to the consistency of the deployment or the scenario; and a control unit that controls model identification on the basis of the information.

Description

Terminal, wireless communication method and base station

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

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] 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 or later, etc.) are also being considered.

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

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

[0006] Use cases for utilizing AI models include spatial domain downlink (DL) beam prediction, temporal DL beam prediction, positioning, etc. Such beam prediction methods may be referred to as AI-based beam prediction (beam reporting), AI-based positioning, AI-based beam management (BM), etc. Temporal DL beam prediction may be referred to as time-domain Channel State Information (CSI) prediction, for example.

[0007] In utilizing such AI, the introduction of multiple types of life cycle management (LCM) is being considered, but in some cases, this is not sufficiently considered. If this consideration is insufficient, it may be impossible to achieve optimal overhead reduction, channel estimation, and resource utilization, which may hinder improvements in communication throughput and communication quality.

[0008] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can achieve suitable overhead reduction / channel estimation / resource utilization.

[0009] A terminal according to one aspect of the present disclosure has a receiving unit that receives an ID associated with a deployment or scenario, or information regarding the consistency of the deployment or scenario, and a control unit that controls model identification based on the information.

[0010] According to one aspect of the present disclosure, it is possible to achieve favorable overhead reduction / channel estimation / resource utilization.

[0011] FIG. 1 is a diagram illustrating an example of a framework for managing AI models. FIG. 2 is a diagram illustrating an example of specifying an AI model. FIG. 3 is a conceptual diagram illustrating an example of an ID-based approach according to embodiment 0-1. FIG. 4 is a conceptual diagram illustrating an example of a non-ID-based approach according to embodiment 0-2. FIGS. 5A and 5B are diagrams illustrating an example of the timing (start point) of receiving an ID / consistency instruction according to the first embodiment. FIGS. 6A and 6B are diagrams illustrating an example of the timing (end point) of receiving an ID / consistency instruction according to the first embodiment. FIGS. 7A and 7B are diagrams illustrating an example of the timing (end point) of receiving an ID / consistency instruction according to the first embodiment. FIG. 8 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 9 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 10 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 11 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 12 is a diagram illustrating an example of a vehicle according to an embodiment.

[0012] (Application of Artificial Intelligence (AI) Technology to Wireless Communications) With regard to future wireless communications technologies, the use of AI technology such as machine learning (ML) for network / device control and management is being considered.

[0013] For example, it is being considered that terminals (user terminals, user equipment (UE)) / base stations (BSs) will utilize AI technology to improve Channel State Information (CSI) feedback (e.g., reduced overhead, improved accuracy, prediction), improve beam management (e.g., improved accuracy, prediction in the time / space domain), and improve position measurement (e.g., improved position estimation / prediction).

[0014] Based on the input information, the AI ​​model may output at least one information such as an estimate, a prediction, a selected action, a classification, etc. 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 / location, future channel state information / radio link quality, etc.

[0015] In the present disclosure, AI may be interpreted as an object (also called a subject, object, data, function, program, etc.) that has (performs) at least one of the following characteristics: - Estimation based on observed or collected information; - Selection based on observed or collected information; - Prediction based on observed or collected information.

[0016] In the present disclosure, estimation, prediction, and inference may be used interchangeably. Also, in the present disclosure, estimate, predict, and infer may be used interchangeably.

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

[0018] Also, in the present disclosure, an AI model may be interpreted as an object that has (performs) at least one of the following characteristics: - Generates an estimate by feeding information; - Predicts an estimate by feeding information; - Discovers features by feeding information; - Selects an action by feeding information.

[0019] Additionally, 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.

[0020] In addition, in the present disclosure, the terms AI model, model, ML model, predictive analytics, predictive analysis model, tool, autoencoder, encoder, decoder, neural network model, AI algorithm, scheme, etc. may be interchangeable. 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.

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

[0022] Furthermore, in the present disclosure, the terms encoder, encoding, encode / encoded, modification / alteration / control by an encoder, compressing, compress / compressed, generating, generate / generated, etc. may be read interchangeably.

[0023] In addition, in the present disclosure, decoder, decoding, decode / decoded, modification / alteration / control by decoder, decompressing, decompress / decompressed, reconstructing, reconstruct / reconstructed, etc. may be read interchangeably.

[0024] In the present disclosure, a layer (of an AI model) may be interchangeably read as a layer (such as an input layer or an intermediate layer) used in the AI ​​model. The layer in the present disclosure may correspond to at least one of an input layer, an intermediate layer, an output layer, a batch normalization layer, a convolutional layer, an activation layer, a dense layer, a normalization layer, a pooling layer, an attention layer, a dropout layer, a fully connected layer, etc.

[0025] In this disclosure, methods for training an AI model may include supervised learning, unsupervised learning, reinforcement learning, federated learning, etc. 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 an environment with which the model interacts.

[0026] In the present disclosure, terms such as generate, calculate, derive, etc. may be interchangeable. In the present disclosure, terms such as implement, operate, operate, execute, etc. may be interchangeable. In the present disclosure, terms such as train, learn, update, retrain, etc. may be interchangeable. In the present disclosure, terms such as infer, after-training, live use, actual use, etc. may be interchangeable. In the present disclosure, signal may be interchangeable with signal / channel.

[0027] FIG. 1 is a diagram illustrating 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 AI model life cycle management (LCM).

[0028] The data collection stage corresponds to a 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.

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

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

[0031] 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, transformation, etc.), model training / validation, model testing (e.g., verifying whether the trained model meets a performance threshold), model exchange (e.g., transferring the model for distributed learning), and model deployment / update (deploying / updating the model to the entity that will perform model inference).

[0032] It should be noted that 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.

[0033] AI model validation may also refer to a sub-process of training that evaluates the quality of an AI model using a dataset different from the dataset used to train the model, which helps select model parameters that generalize beyond the dataset used to train the model.

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

[0035] 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 training the model), and output (providing model output to the actor).

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

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

[0038] 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 in which joint inference is performed. Here, joint inference may include AI inference in which 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).

[0039] In addition, AI model monitoring may refer to a process for monitoring the inference performance of an AI model, and may be interchangeably read as model performance monitoring, performance monitoring, etc.

[0040] Note that model registration may refer to assigning a version identifier to a model and making the model executable (registering) the model by compiling it into the specific hardware used in the inference stage. Also, model deployment may refer to distributing (or activating in) a runtime image (or an image of an execution environment) of a fully developed and tested model to (or enabling in) a target (e.g., UE / gNB) where inference will be performed.

[0041] An actor stage 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.

[0042] For example, training of a model for mobility optimization may be performed in, for example, Operation, Administration and Maintenance (Management) (OAM) / gNodeB (gNB) in a network (NW). 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 need for data exchange for model deployment are advantageous. Inference of the above model may be performed in, for example, a gNB.

[0043] The entity that performs training / inference may vary depending on the use case (i.e., the function of the AI ​​model), which may include beam management, beam prediction, autoencoder (or information compression), CSI feedback, positioning, etc.

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

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

[0046] For CSI feedback / channel estimation using an autoencoder, the OAM / gNB / UE may perform model training and the gNB / UE may perform model inference (jointly).

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

[0048] Note that model activation may mean activating an AI model for a specific function, model deactivation may mean disabling an AI model for a specific function, and model switching may mean deactivating a currently active AI model for a specific function and activating a different AI model.

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

[0050] 2 is a diagram showing an example of specifying an AI model. In this example, a UE and a NW (e.g., a base station (BS)) can recognize models #1 and #2 (although they do not need to fully understand the details of the models). The UE may report, for example, the capabilities of model #1 and model #2 to the NW, and the NW may instruct the UE on the AI ​​model to use.

[0051] (Life Cycle Management (LCM)) In future wireless communication systems (for example, Rel. 18 and later), the introduction of multiple LCMs is being considered.

[0052] The plurality of LCMs may include 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.

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

[0054] The UE may perform model-level LCM (eg, model switching and / or model selection) among the indicated functionality.

[0055] Among other things, the functionality may be transparent as to which models are activated / deactivated.

[0056] UE Capability information reporting may be used to signal supported functionality.

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

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

[0059] A model may be defined in the NW by a model identifier (ID).

[0060] (Cases Related to Model Delivery / Transfer) Regarding model delivery / transfer, when a model is trained by a network, three cases are defined in existing scenarios.

[0061] [Case y] First, the NW trains a model and distributes the model to the UE outside the 3GPP network through offline engineering by multiple vendors.

[0062] The UE then reports its support for the delivered model (this step may be called model identification).

[0063] [Case z2] First, the NW trains a model through offline engineering of multiple vendors and saves it in a proprietary format, which may mean a format defined for each vendor.

[0064] The UE then reports the use of the stored model in the 3GPP network (this step may be called model identification).

[0065] A model transport is then carried out.

[0066] The UE then reports support for the transferred model (this step may be called model identification).

[0067] [Case z4] First, the UE reports the supported model structure (this step may be called model identification).

[0068] The NW then forwards the model parameters of the supported model structures.

[0069] The UE then reports support for the transferred model (this step may be called model identification).

[0070] (Functionality Identification) As a procedure for identifying functionality, for example, the UE may report a specific condition in the UE capability (capability information). In this case, the NW may configure the corresponding functionality based on the reported condition.

[0071] Here, functionality may represent features / feature groups (FGs) available in the AI / ML that are enabled by a certain configuration, such as a set of RRC parameters / LPP parameters. The configuration 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 (activation / deactivation / switching) of LCM.

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

[0073] The UE may also report applicable functionality updates, e.g., a mechanism for updating the applicable model after identifying the model needs to be considered.

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

[0075] The operation of the Model ID-based LCM 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.

[0076] In addition, it is assumed that the identification process and control unit are different between the functionality-based LCM and the model ID-based LCM. Here, it is being considered to share the activation / deactivation / switching procedures between the functionality-based LCM and the model ID-based LCM.

[0077] The following types of model identification procedures are also considered: Type A: Model information and model IDs are associated without signaling. The UE reports supported model IDs to the NW. That is, the mapping between model IDs and model information is identified to the NW and UE without signaling. The NW and 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 (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 to the remaining steps of model identification. During model identification, a model ID may be assigned to the model.

[0078] Type B1 can be further classified into Type B1-1 and Type B1-2.

[0079] <Type B1-1> Type B1-1 refers to a type of model identification in which an ID is assigned by the NW, and may include the following procedures: ・The UE (re)trains and deploys a new model. ・The UE reports the existence of the new model along with any associated additional conditions. ・The NW indicates the model ID assigned to the reported model.

[0080] <Type B1-2> Type B1-2 refers to a type of model identification where the ID is assigned by the UE, and may include the following steps: The UE (re)trains a new model. The UE assigns a model ID to the new model. The UE reports the existence of the new model with additional conditions and the associated model ID.

[0081] Type B2 can be further classified into Type B2-1 and Type B2-2.

[0082] <Type B2-1> Type B2-1 refers to a type of model identification corresponding to model transfer, and may include the following procedures: ・UE reports supportable model information. ・NW (re)trains a new model. ・NW transfers the new model (with the model ID assigned to the new model) together with the model ID to the UE.

[0083] <Type B2-2> Type B2-2 refers to a type of model identification corresponding to data collection initiation, and may include the following procedures: The NW initiates collection of a dataset for model training to the UE and assigns a model ID. The UE trains a model based on the collected dataset. The UE notifies that the model associated with the model ID has been deployed.

[0084] (Meta Information) The UE may receive at least one of the following as meta information.

[0085] Note that the term "meta information" in this disclosure is merely an example, and meta information may refer to at least one of specific setting information, scenario information, environmental information, support information, and model information. In this disclosure, meta information, setting information, scenario information, environmental information, support information, and model information may be read interchangeably.

[0086] The meta information used by the UE / NW may include at least one of information regarding NW configuration / deployment, information regarding the environment, information regarding the AL / ML model on the NW side, and information regarding the model required by the NW.

[0087] The information regarding network settings / deployment may include, for example, information regarding antenna settings.

[0088] The information regarding the antenna configuration may indicate, for example, at least one of the following: horizontal / vertical antenna element / panel number, port number, antenna spacing, antenna position, panel position, and transceiver unit (TxRU) mapping.

[0089] The information regarding network configuration / deployment may include, for example, information regarding beam configuration.

[0090] The information about the beam setting may include, for example, at least one of the beam width, the number of beams, and the beam direction.

[0091] The information regarding network configuration / deployment may include, for example, information regarding TRP.

[0092] The information regarding the beam setting may include, for example, at least one of the altitude of the TRP and the relative positions of the multi-TRP.

[0093] The information about the environment may include, for example, information about the deployment scenario.

[0094] The information about the deployment scenario may indicate, for example, at least one of Urban Macro (UMa), Urban Micro (Umi), and Indoor Hotspot (InH).

[0095] The information about the environment may include, for example, information about indoors or outdoors.

[0096] The information about indoor or outdoor may indicate, for example, an indoor / outdoor probability.

[0097] The information about the environment may for example be information about objects around the UE / base station.

[0098] The information about the objects around the UE / base station may, for example, indicate the location of the objects around the UE / base station.

[0099] The information about the environment may include, for example, the scenario setting format (meta information) described below.

[0100] Use cases using AI models may be associated with a scenario-setting format that consists of long-term features.

[0101] Note that the term "long-term features" may be interchangeably read as "short-term / mid-term / long-term features" or simply "features." Furthermore, the term "scenario setting format" may be interchangeably read as "meta information," "meta information format," "scenario and configuration format," "scenario configuration format," "scenario format," "setting format," "use case format," "environment format," "meta format," etc. Furthermore, the term "format" may be interchangeably read as "type," "mode," "data," "setting," etc.

[0102] The above features may include one or more combinations of the following elements: - Scenario / model (Urban Macro (UMa), Urban Micro (Umi), indoor, outdoor, indoor hotspot (InH), etc.); - Frequency / frequency range; - Numerology (or subcarrier spacing); - Distribution / set of general channel parameters (e.g., inter-site distances (ISD), gNB height, delay spread, angle spread, Doppler spread, etc.) in a single scenario / model; - UE distribution; - UE speed; - UE orbit; - Number of transmit beams / receive beams; - UE rotation pattern; - gNB / UE antenna configuration (e.g., transmit and receive antenna vectors); - Number of cells / sectors; - Bandwidth; - UE payload; - Channel quality (e.g., RSRP, SINR); - Beam configuration ID; - Physical Cell ID (PCI). Global Cell ID (GCI) Absolute Radio Frequency Channel Number (ARFCN) Line Of Site (LOS) / Non-Line Of Site (NLOS) probability.

[0103] A UE may be expected to be configured / registered with a model whose associated scenario configuration format matches the UE's configuration / status.

[0104] The UE may also be expected to activate a model whose associated scenario configuration format matches the UE's configuration / status.

[0105] The correspondence between a use case and a scenario configuration format may be specified in a standard, and information on the correspondence may be notified to the UE. Also, the features included in the scenario configuration format corresponding to the use case may be specified in a standard, and information on the features may be notified to the UE.

[0106] The information on the AL / ML model on the NW side may include, for example, information on paired models available on the NW side.

[0107] The information about the paired model available on the NW side may indicate, for example, a paired decoder for CSI compression.

[0108] The information about the AL / ML model on the NW side may include, for example, information about pre-processing / post-processing available on the NW side.

[0109] The information regarding pre-processing / post-processing available on the NW side may include, for example, at least one of quantization / dequantization processing, DFT transformation, IDFT transformation, FFT transformation, and IFFT transformation.

[0110] UE Assistance Information The UE may report assistance information / metadata (meta-information) for the AI / ML model.

[0111] The assistance information may include, for example, at least one of the following information (user status): overheating assistance information; DRX parameter preference; priority regarding maximum aggregate bandwidth; preference for maximum number of MIMO layers.

[0112] The AI / ML model may be an AI / ML model that is registered / configured / compiled / activated in the UE.

[0113] The aiding information / metadata for the AI / ML model may be transmitted together with or instead of the beam information, which may be, for example, information about the UE's antennas / beams.

[0114] The supporting information / metadata of the AI / ML model may be at least one of the information described below.

[0115] The supporting information / metadata for the AI / ML model may be the ID of the AI / ML model.

[0116] The ID of the AI / ML model may be a global / local AI / ML model ID.

[0117] The supporting information / metadata for the AI / ML model may be information regarding the applicable bandwidth corresponding to the AI / ML model ID.

[0118] The bandwidth may be indicated as the applicable minimum / maximum bandwidth.

[0119] The information about the bandwidth may include, for example, information indicating a band indicator (e.g., "freqBandIndicatorNR"). The information indicating the band indicator may be represented by a specific number of bits (e.g., 10 bits).

[0120] The information about the bandwidth may include, for example, information indicating the bandwidth of the RS associated with the corresponding AI / ML model (eg, "supportedBandwidth").

[0121] The information indicating the bandwidth of the RS associated with the corresponding AI / ML model may indicate the frequency for each frequency range (for example, FR1 / FR2 (FR2-1 / FR2-2) / FR3 / FR4 / FR5).

[0122] The supporting information / metadata of the AI / ML model may be information about the applicable area corresponding to the AI / ML model ID.

[0123] The information regarding the applicable area corresponding to the AI / ML model may include at least one of the following information (list of information): Area ID. Cell global ID (in NR). Physical cell ID (Identifier) ​​(in NR). ARFCN (Absolute Radio Frequency Channel Number). Evolved Cell Global ID (ECGI).

[0124] The area ID may include at least one of the global ID of the NR cell, the physical cell ID of the NR, and the ARFCN.

[0125] The support information / metadata for the AI / ML model may be antenna setting / beam information corresponding to the AI / ML model ID.

[0126] (KPI) Common Key Performance Indicators (KPIs) are being considered for monitoring the performance of AI models.

[0127] Below is an initial list of common KPIs for evaluating the performance impact of AI / ML models: Performance, Intermediate KPIs, Link-level and system-level performance, Generalization performance, Over-the-air overhead, Assistance information overhead, Data collection overhead, Model delivery / transfer overhead, Other AI / ML model related signaling overhead, Inference complexity, Model inference computational complexity: floating point operations (FLOPs) (note that the s is lowercase), Pre- and post-processing computational complexity, Model complexity (number of parameters / data size (e.g., Mbyte), etc.), Training complexity, LCM related complexity. complexity) and storage overhead, and latency (e.g., inference latency). Note that the above KPIs are merely examples, and other KPIs may be added to the list (e.g., KPIs related to model training, use-case-specific KPIs considered for a given use case, etc.).

[0128] Of the above-mentioned KPIs, KPIs related to performance may be called performance KPIs.

[0129] Functionality Related Information A UE may report the functionality it supports (or is supported).

[0130] A functionality may be associated with, include, or belong to a particular piece of information.

[0131] In this disclosure, "be associated with," "include," "belong to," and "correspond to" may be used interchangeably.

[0132] The specific information may be at least one of the following: The specific information and the functionality-related information may be interchangeable.

[0133] The particular information may be information regarding applicable conditions / settings.

[0134] The specific information may be, for example, applicable NW configurations. For example, the applicable parameters related to the NW configurations may be at least one of parameters of system information and parameters of assistance information.

[0135] The specific information may for example be applicable UE configuration, for example applicable parameters of the UE configuration may be higher layer (e.g. RRC) parameters.

[0136] The specific information may be, for example, information about an applicable scenario, such as information indicating at least one of NLOS / LOS, UE distribution, SINR, RSRP, bandwidth, frequency, indoor / outdoor, and deployment scenario (e.g., at least one of Urban Macro (UMa), Urban Micro (Umi), and Indoor Hotspot (InH)).

[0137] The specific information may be, for example, information about an applicable arrangement, which may be information indicating at least one of an applicable antenna configuration (e.g., at least one of the number of antenna elements / panels in the horizontal / vertical directions, the number of ports, the antenna spacing, the antenna position, the panel position, and the transceiver unit (TxRU) mapping), a beam configuration (e.g., at least one of the beam width, the number of beams, and the beam direction), and TRP information (e.g., at least one of the altitude of the TRP and the relative positions of multiple TRPs).

[0138] The specific information may be, for example, information about an applicable site, or may be information indicating at least one of an area ID, an NR cell global ID, an NR physical cell ID, a specific frequency (e.g., ARFCN), and an ECGI.

[0139] The specific information may be, for example, information about an applicable paired model. The paired model may be, for example, two (two or more) network-side models (combinations of models). The specific information may be, for example, information indicating a paired model for CSI compression.

[0140] The specific information may be, for example, information about an applicable time. The information may be, for example, information indicating an applicable period / interval / duration. The period may be, for example, indicated using a specific time unit (e.g., slot / symbol / subslot / millisecond / second).

[0141] The applicable conditions / settings may be predefined in the specification or may be determined / identified using a specific ID / token. For example, the applicable settings / scenarios / conditions may be defined as specific parameters (e.g., test parameters) or may be represented using a specific ID / token.

[0142] The performance of a functionality (e.g., prediction accuracy, location error) may be assumed to be better (e.g., higher) than a particular threshold under applicable conditions / settings, which may be, for example, the conditions / settings of a particular test.

[0143] The thresholds / performance requirements may be pre-specified or may be determined / identified using a specific ID / token.

[0144] If the threshold / performance requirements are based on a specific ID / token, each vendor / operator can define and utilize the desired thresholds / performance.

[0145] (Analysis) As described above, Type B1 / B2 are being considered as procedures for model identification. In Type B1, model identification is initiated by the UE, and in Type B2, model identification is initiated by the NW.

[0146] However, the specific steps for this have not been clarified.

[0147] Furthermore, models specialized for a certain deployment / scenario are believed to perform better than general models (general-purpose models). For example, a model trained on a dataset collected in a certain environment (environment ID = A) is likely to perform well in that environment, but it may not necessarily perform well in a different environment (environment ID = B).

[0148] On the other hand, if a different environment (say, environment ID = C) is similar to a certain environment (say, environment ID = A), it is likely that a model trained based on a dataset collected in the certain environment (say, environment ID = A) will also perform well in the different environment (say, environment ID = C).

[0149] That is, in model identification, it is necessary to associate a model with a deployment / scenario suitable for that model in order to maximize the performance of the model. On the other hand, gNB / UE vendors try to avoid disclosing implementation information for models (information regarding the specification of various input information for model training, such as beam mapping) as much as possible.

[0150] As mentioned above, if an ID is used to indicate a specific deployment / scenario, from the perspective of the gNB / UE vendor, there is a risk that information regarding a partial deployment / scenario may be identified based on the ID.

[0151] Therefore, the present inventors have conceived a method (procedure) for model identification that solves these problems.

[0152] (Various Replacements, etc.) Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0153] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0154] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0155] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0156] 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 protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0157] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. 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.

[0158] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0159] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0160] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0161] In the present disclosure, CSI-RS, non-zero power (NZP) CSI-RS, zero power (ZP) CSI-RS, and CSI interference measurement (CSI-IM) may be interchangeable. Furthermore, CSI-RS may include other reference signals.

[0162] In this disclosure, a measured / reported RS may refer to an RS that is measured / reported for a CSI report.

[0163] In the present disclosure, timing, time, duration, slot, subslot, symbol, subframe, etc. may be read interchangeably.

[0164] In the present disclosure, the terms direction, axis, dimension, domain, polarization, polarization component, etc. may be read interchangeably.

[0165] In the present disclosure, estimation, prediction, and inference may be used interchangeably. Also, in the present disclosure, estimate, predict, and infer may be used interchangeably.

[0166] In the present disclosure, the terms autoencoder, encoder, decoder, etc. may be replaced with at least one of a model, an ML model, a neural network model, an AI model, an AI algorithm, etc. Furthermore, the term autoencoder may be replaced with any autoencoder, such as a stacked autoencoder or a convolutional autoencoder. The encoder / decoder of the present disclosure may employ a model such as a Residual Network (ResNet), a DenseNet, or a RefineNet.

[0167] In the present disclosure, the terms bit, bit string, bit sequence, sequence, value, information, value obtained from a bit, information obtained from a bit, etc. may be read interchangeably.

[0168] In the present disclosure, a layer (for an encoder) may be interchangeably read as a layer (such as an input layer or an intermediate layer) used in an AI model. The layer in the present disclosure may correspond to at least one of an input layer, an intermediate layer, an output layer, a batch normalization layer, a convolutional layer, an activation layer, a dense layer, a normalization layer, a pooling layer, an attention layer, a dropout layer, a fully connected layer, etc.

[0169] In the present disclosure, RSRP may be interchangeably read as any parameter related to received power / received quality, etc. (e.g., RSRQ, SINR, CSI), etc.

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

[0171] In the present disclosure, channel measurement / estimation may be performed using 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), and the like.

[0172] In the present disclosure, the terms "receive beam assumption," "number of receive beams," "index of receive beam," "receive beam selection," "receive beam setting," and "receive beam instruction" may be interchangeable. In the present disclosure, the terms "receive beam," "transmit beam," "DL receive beam," "DL transmit beam," and "pair of transmit beam and receive beam" may be interchangeable. In the present disclosure, the terms "transmit / receive beam" may be interchangeable with the terms "transmit / receive beam for beam prediction" and "transmit / receive beam for CSI measurement / reporting for beam prediction."

[0173] In this disclosure, functionality may refer to the use of a model or the physical meaning of the model's input / output. Multiple models may have the same functionality. Monitoring (checking performance), activation, deactivation, switching, fallback, and updating may be instructed (controlled) based on the functionality (e.g., for each function).

[0174] In this disclosure, functionality may refer to features (requiring AI / ML capabilities) (e.g., CSI prediction / CSI compression / temporal beam prediction / reporting information based on spatial domain beam prediction).

[0175] A model ID may also 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 actually be different models (e.g., have different numbers of layers) but may be treated as the same model.

[0176] In the present 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 about the applicability of the model / functionality, the environment, the UE / gNB settings, etc.

[0177] In the present disclosure, functionality may be simply read as "function."

[0178] In the present disclosure, functionality, function, functionality ID, model, and model ID may be read interchangeably.

[0179] In the present disclosure, applicable update, updating applicable models / functionality, updating applicability of models / functionality, and applicable update may be read interchangeably.

[0180] In the present disclosure, update, report, and send may be read interchangeably.

[0181] In the present disclosure, applicability report and applicability report may be read interchangeably.

[0182] In the present disclosure, meta information, assistance information, sensing information, KPI, performance KPI, UE status, and status may be read interchangeably.

[0183] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.

[0184] In the present disclosure, consistency, coherence, and consistency may be read interchangeably.

[0185] In the present disclosure, consistent and matching may be read interchangeably.

[0186] In the present disclosure, an ID may represent an ID corresponding to (for identifying) at least one of a dataset, a model, and a property of a channel / RS. That is, in the present disclosure, an ID, a dataset ID, a model ID, and a property ID of a channel / RS may be read as interchangeable.

[0187] In the present disclosure, the terms "report initiation" and "report trigger" may be read interchangeably.

[0188] In the present disclosure, ID and consistency may be read as interchangeable.

[0189] In the present disclosure, receiving an ID, receiving information about an ID, and receiving (information about) a consistency instruction may be read interchangeably.

[0190] In the present disclosure, the predetermined duration for receiving an ID / consistency instruction, duration, received ID), duration, consistency duration, consistency instruction time, consistency application time, ID / consistency receivable time, and receivable time corresponding to the received ID may be read interchangeably.

[0191] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0192] (Wireless Communication Method) The embodiments of the present disclosure can be broadly categorized as follows: ・Embodiment 0: ID-based / non-ID-based approach to model identification. ・Embodiment 1: Receiving an ID / consistency indication. ・Embodiment 2: Reporting supported IDs. ・Embodiment 3: Reporting applicable / supported functionality. ・Embodiment 4: Constraints on applicable reporting. Each embodiment will be described below based on these.

[0193] <Tenth Embodiment> The tenth embodiment relates to an ID-based / non-ID-based approach to model identification.

[0194] The 0th embodiment can be further classified into embodiments 0-1 and 0-2.

[0195] <<Embodiment 0-1>> In embodiment 0-1, an ID-based approach to model identification will be described. Fig. 3 is a conceptual diagram showing an example of the ID-based approach according to embodiment 0-1.

[0196] In ID-based, the NW triggers data collection at the UE side and assigns an ID without informing the UE of the deployment / scenario information. Based on the assigned ID, the NW instructs the model to be used.

[0197] As shown in Figure 3, the UE may receive information about the ID from the gNB (NW). Here, the ID received by the UE may represent an ID corresponding to (for identifying) at least one of the following: a data set, a model, a period, a measurement setting, and a channel / RS property. Details of the UE's reception operation will be described in the first embodiment below.

[0198] The ID received by the UE may include information about the ID, information indicating the ID, etc. The ID may be associated with information related to data collection, model training, and performance monitoring.

[0199] If the UE receives the above ID, it may assume that the collected data set, model, or channel / RS characteristics are consistent during a certain duration.

[0200] As shown in Figure 3, the UE may report supported IDs for a certain functionality. For example, the UE may report supported model IDs for a certain functionality. The reported IDs may be used for model management among the supported IDs.

[0201] In this disclosure, functionality may refer to features (requiring AI / ML capabilities) (e.g., CSI prediction / CSI compression / temporal beam prediction / reporting information based on spatial domain beam prediction).

[0202] In embodiment 0-2, a non-ID-based approach to model identification will be described. Fig. 4 is a conceptual diagram showing an example of the non-ID-based approach according to embodiment 0-2.

[0203] The NW may only indicate consistency for a certain period in a deployment / scenario, in which case the UE cannot track a deployment / scenario that corresponds to a past deployment / scenario.

[0204] As shown in FIG. 4, the UE may receive information regarding a consistency indication from the gNB (NW). That is, in embodiment 0-2, the UE may receive information regarding the consistency indication instead of the ID of embodiment 0-1. Details of the UE's reception operation will be described in the first embodiment below.

[0205] The consistency received by the UE may include information about consistency, information indicating consistency (consistency indication information), etc. The consistency may be associated with information about data collection, model training, and performance monitoring.

[0206] If the UE receives information regarding the above-mentioned consistency indication, it may assume that the collected data set, model, or specific characteristics of the channel / RS are consistent during a certain duration.

[0207] The UE may monitor the performance of the functionality / model and report the supported / applicable functionality / model for a certain duration, which may be referred to as a consistency application time, consistency indication time, consistency duration, etc.

[0208] As shown in Figure 4, the UE may report the supported models / functionality, which may be used for model management among the supported models / functionality.

[0209] According to the 0th embodiment described above, model identification can be appropriately controlled by the ID-based / non-ID-based approach.

[0210] First Embodiment The first embodiment relates to receiving an ID / consistency instruction and is applicable to the above-described 0th embodiment (embodiment 0-1 / 0-2).

[0211] Embodiment 1-1 In embodiment 1-1, the timing of receiving an ID / consistency instruction will be described. Figures 5A and 5B are diagrams showing an example of the timing (start point) of receiving an ID / consistency instruction according to the first embodiment. Figures 6A and 6B are diagrams showing an example of the timing (end point) of receiving an ID / consistency instruction according to the first embodiment. Figures 7A and 7B are diagrams showing an example of the timing (end point) of receiving an ID / consistency instruction according to the first embodiment.

[0212] The timing (start and end points) at which the UE receives the information regarding the ID / consistency indication may be determined by the following method.

[0213] In the present disclosure, the time (period) during which an ID / consistency instruction can be received may be interpreted interchangeably as the time duration corresponding to the received ID (received ID), the consistency duration, the consistency instruction time, the consistency application time, the ID / consistency receivable time, the receivable time, etc.

[0214] In the present disclosure, the unit of time may be any one of a symbol, a slot, a subframe, and a radio frame, as well as a duration and a time offset X / Y / Z / x, which will be described later.

[0215] (Start Point of Reception) The start point may be a timing of a time offset X before / after the first / last reception of an ID / integrity indication. The time offset X may indicate an offset relative to the start point.

[0216] For example, as shown in FIG. 5A, the start of the duration corresponding to ID#1 may be a time offset X before the first / last time an ID / consistency indication is received.

[0217] Alternatively, as shown in FIG. 5B, the start of the duration corresponding to ID#1 may be a time offset X after the first / last time an ID / consistency indication is received.

[0218] In the present disclosure, the start point, start timing, and start time may be read interchangeably.

[0219] In the present disclosure, the time offset and the length of the duration (receivable time) may be read as interchangeable.

[0220] The value of X may be set / indicated by the NW through higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined based on UE capabilities. For example, X may be determined based on a parameter included in information on ID / consistency indication transmitted from the NW. Furthermore, the value of X may vary depending on numerology (e.g., subcarrier spacing (SCS)) and frequency range.

[0221] (End Point of Reception) The end point may be determined by at least one of the following options 1 to 6.

[0222] In the present disclosure, the terms end point, end timing, and end time may be interpreted interchangeably.

[0223] <Option 1> The end point may be a timing after (from) the start point of the duration, at a certain time point. For example, as shown in Figure 6A, the length of the duration may be the same as the time from the start point to the end point (receivable time).

[0224] Option 2: The end point may be a certain duration after the first / last ID / consistency indication is received, i.e., the duration (time from the ID / consistency indication reception to the end point) may be longer than the time from the start point to the end point (receiveable time), as shown in Figure 6B.

[0225] <Option 3> The end point may be a timing of a time offset Y before / after the first / last reception of information regarding an ID / consistency termination indication. The time offset Y may indicate an offset relative to the end point.

[0226] 7A, the end point of the receivable time may be a time offset Y after the ID / consistency instruction is received. That is, even after the ID / consistency instruction is received, the receivable time may continue for the time offset Y.

[0227] The value of Y may be set / indicated by the NW through higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined based on UE capabilities. For example, Y may be determined based on a parameter included in information on ID / consistency indication transmitted from the NW. Furthermore, the value of Y may vary depending on numerology (e.g., subcarrier spacing (SCS)) and frequency range.

[0228] Option 4: The end point may be a timing offset Y before / after the first / last reception of (information about) another ID / consistency indication (indicating a different ID / consistency).

[0229] <Option 5> The end point may be the start of a duration corresponding to another ID / consistency indication (indicating a different ID / consistency). For example, as shown in Figure 7B, the end point may be the point (start point #2) where the duration corresponding to ID #1 (first reception time) ends and the duration corresponding to ID #2 (second reception time) starts, time offset Y later. <Option 6> The end point may be a timing offset Y before / after a specific event (e.g., RRC reconfiguration, radio link failure, beam failure detection, handover command reception, handover execution).

[0230] <<Embodiment 1-1>> In embodiment 1-1, a method for receiving an ID / consistency instruction will be described.

[0231] The UE may receive the identity / consistency indication e.g. via the following signaling: - Signaling as described in Supplementary Note 2 below or UE capability request - System information (e.g. SIB) - Group-common signaling (e.g. multicast / broadcast).

[0232] All / certain RS resources / channels may be associated with an ID / consistency indication.

[0233] For example, the RS resource / channel associated with the ID / consistency indication may be at least one of the following: RS / channel in a particular band / bandwidth / BWP / serving cell; A particular RS setting; A particular RS resource set / RS resource; RS / channel in a particular CORESET / search space; A particular type of RS / channel (e.g., PRS, CSI-RS); A particular frequency layer.

[0234] The RS resource / channel associated with the ID / consistency indication may be determined based on configuration / indication / predefined parameters or parameters reported in the UE capabilities / associated functionality.

[0235] In addition to the identity / integrity indication, the UE may receive the following information associated with the identity: Vendor indication / ID (Type Allocation Code) International Mobile Equipment Identity (IMEI) Type allocation code Final assembly code Check digit (CD) / spare digit (SD).

[0236] For example, the IMEI may be represented by 15 bits as follows: IMEI (15 bits) = TAC (6 digits) + FAC (2 digits) + serial number (SNR) (6 digits) + check digit (1 digit).

[0237] A Type Allocation Code (TAC) is a code for identifying the manufacturer and device type, and is a code for identifying the vendor / device. In the present disclosure, the first 6 bits / 8 bits of the IMEI may represent the TAC.

[0238] A Final Assembly Code (FAC) is a code that identifies the country in which a device is manufactured. In the present disclosure, the FAC may or may not be part of the TAC (it may be separate from the TAC).

[0239] The CD / SD is one bit of information for checking the IMEI.

[0240] According to the first embodiment described above, the UE can properly receive (information relating to) the ID / consistency indication.

[0241] Second Embodiment The second embodiment relates to reporting of supported IDs.

[0242] The UE may report the IDs supported for a particular functionality.

[0243] <<Supported IDs>> Supported IDs preferably satisfy at least one of the following conditions.

[0244] <Condition 1> A specific indicator (metric) derived from a data set (measurement results) collected / measured within a duration corresponding to the ID is greater / less than a certain threshold. The specific indicator or threshold may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined based on UE capabilities.

[0245] <Condition 2> The model / functionality may be trained / derived based on a data set (measurement results) collected / measured within the duration corresponding to the ID. For example, the model / functionality may be trained / derived based on a certain number or more data samples (measurement results / measurements) collected / measured within the duration corresponding to the ID.

[0246] The predetermined number may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined based on UE capabilities.

[0247] According to condition 2, it is possible to utilize a dataset corresponding to a specific ID to train / fine-tune a model.

[0248] <Condition 3> The UE may determine / judge the supported IDs based on at least one of the conditions shown in options 1 to 4 below.

[0249] <Option 1> The UE may determine / judge supported IDs based on performance KPIs (which may also be called performance KPIs). More specifically, the UE may determine / judge supported IDs based on whether the performance KPIs are greater than or less than a certain requirement (threshold).

[0250] The threshold may be set / indicated by higher layer / physical layer signaling or may be predefined by a specification.

[0251] Performance KPIs may be set / indicated by higher layer signaling / physical layer signaling.

[0252] A performance KPI may be calculated over a certain duration, for example, an average value of performance over a certain duration may be used as the performance KPI.

[0253] If the performance KPI is greater than a certain threshold, the UE may determine / assess that it can support the corresponding ID, and if the KPI is less than a certain threshold, the UE may determine / assess that it cannot support the corresponding ID.

[0254] <Option 2> The UE may determine / judge the supported IDs based on the UE status (UE state) shown in Options 2-1 to 2-4: Overheating condition (Option 2-1), Computational resources (Option 2-2), Memory storage (Option 2-3), Power battery (Option 2-4).

[0255] For example, the UE may compare the status of the above-mentioned options 2-1 to 2-4 with a certain threshold and determine / judge the supported IDs based on the result.

[0256] <Option 3> The UE may determine / judge a supported ID based on the support information received from the NW. For example, the UE may determine / judge that the ID can be supported if the model / function status / condition matches the support information received from the NW.

[0257] <Option 4> The UE may determine / judge the supported IDs based on sensing information (detection information), which may be any information (measurement / detection value, etc.) detected by the UE, such as L1-RSRP / SINR or information about the surrounding environment.

[0258] For example, the UE may determine / assess that it can support the ID if the state / condition of the model / function matches the sensing information.

[0259] For each of the above options, the UE may be configured with higher layer parameters to determine whether to apply any of the options (whether to determine / judge supported IDs based on any of the options).

[0260] <<Reporting Supported IDs>> A UE may report supported IDs for a certain functionality via signaling as described in Supplementary Note 3 below (e.g., using the following messages): - UECapabilityInformation message (message containing UE capability information) - UEAssistanceInformation message (message containing UE assistance information) - RRCReconfigurationComplete message (message containing information about RRC configuration completion).

[0261] The NW may start (trigger) reporting of supported IDs based on at least one condition / rule shown in the following options 1-1 to 1-4. In this case, the UE may report supported IDs based on a trigger (such as an instruction to start reporting) from the NW.

[0262] <Option 1-1> The UE may report supported IDs based on a configuration from the NW. For example, the UE may periodically report supported IDs based on a configured / predefined period.

[0263] <Option 1-2> The UE may report supported IDs based on the configuration from the NW. For example, when the serving cell is switched, the UE may periodically report supported IDs.

[0264] <Option 1-3> The UE may report the supported IDs based on an inquiry / instruction from the NW. For example, the UE may report the supported IDs when it receives an inquiry / instruction from the NW to report the supported IDs.

[0265] <Option 1-4> The UE may report supported IDs if it receives at least one of the following assistance information: In addition to the above, the assistance information may be at least one of the following:

[0266] Dataset information (for example, a dataset ID may be defined that indicates the characteristics of the channel in which the UE is present / present in the vicinity, and the characteristics of the measurement values ​​that the UE can obtain) Network placement (location) information (for example, a network placement ID that indicates the placement of the gNB may be defined) Environment information (for example, an environment ID that indicates the environment in which the UE is present (LOS / NLOS environment, etc.) may be defined)

[0267] By utilizing this assistance information, the UE can determine / determine the appropriate supported IDs based on the received assistance information.

[0268] The UE may start transmitting (reporting) supported IDs if the configured / predefined rules are met. Specifically, the UE may start reporting supported IDs based on at least one of the conditions / rules shown in Options 1 to 6 below.

[0269] <Option 1> The UE may start reporting supported IDs if a specific higher layer parameter (RRC parameter) is configured, which may be a parameter related to reporting supported IDs.

[0270] <Option 2> If the UE has not reported (transmitted) the supported IDs and if at least one of the following options 2-1 to 2-3 is satisfied, the UE may start reporting the supported IDs.

[0271] [Option 2-1] The UE is configured with certain higher layer parameters for reporting supported IDs.

[0272] [Option 2-2] The UE reports (transmits) at least one of the conditions of the supported IDs.

[0273] [Option 2-3] The UE is configured with a model / functionality, i.e., the configured model / functionality has been determined / determined.

[0274] <Option 3> The UE may start reporting the supported ID if the supported ID is different from the ID reported / indicated in the last (latest) report (transmission). The cases where the IDs are different can be broadly categorized into the following options 3-1 to 3-3.

[0275] [Option 3-1] When the configurable supported ID is different from the indicated supported ID.

[0276] [Option 3-2] When the configured supported ID is different from the indicated supported ID.

[0277] [Option 3-3] When the activated / monitored supported ID is different from the indicated supported ID.

[0278] <Option 4> The UE may start reporting supported IDs if a predetermined timer for reporting supported IDs is not running. The timer length may be configured / indicated by higher layer signaling / physical layer signaling or may be predefined by a specification. For example, if the timer length is not configured / indicated, a default / initial value may be determined based on a predefined value.

[0279] <Option 5> If there is an unsupported ID, the UE may start reporting supported IDs. The cases where there is an unsupported ID can be broadly classified into the following options 5-1 to 5-3.

[0280] [Option 5-1] If at least one of the configurable models / functionalities is not applicable.

[0281] [Option 5-2] If at least one of the configured models / functionalities is not applicable.

[0282] [Option 5-3] If at least one of the activated / monitored models / functionalities is not applicable.

[0283] <Option 6> The UE may start reporting the supported IDs if there are any supported IDs. The types of cases where there are supported IDs can be broadly classified into the following options 6-1 to 6-3.

[0284] [Option 6-1] If at least one of the configurable models / functionalities is applicable.

[0285] [Option 6-2] If at least one of the configured models / functionalities is applicable.

[0286] [Option 6-3] If at least one of the activated / monitored models / functionalities is applicable.

[0287] The UE may report IDs that are supported only for certain functionality. The certain functionality may be configured / indicated by higher layer / physical layer signaling, may be predefined by a specification, or may be determined based on UE capabilities. The UE may receive a request for support.

[0288] In addition to the supported IDs, the UE may receive the following information with which the supported IDs are associated: Vendor indication / ID (Type Allocation Code); Mobile Network Code (MNC); Public Land Mobile Network-ID; Serving cell index.

[0289] A PLMN is a unique ID for identifying a mobile network operator (MNO) and consists of five digits. Specifically, the first three digits correspond to the Mobile Country Code (MCC), and the last two (or three) digits correspond to the Mobile Network Code. A UE can identify which operator (MNO) operates the access network based on the PLMN-ID in SIB1 (PLMN-IdentityInfoList in CellAccessRelatedInfo).

[0290] International mobile subscriber identity (IMSI) indicates a user's unique global ID and is usually registered in the SIM. IMSI may be represented by the following bits: MSIN may mean Mobile Subscriber Identification Number: IMSI = MCC (3 digits) + MNC (2 / 3 digits) + MSIN (10 digits)

[0291] The serving cell index may represent the index of the serving cell whose corresponding ID is signaled.

[0292] According to the second embodiment described above, the UE can appropriately control the reporting of supported IDs.

[0293] <Third embodiment> The third embodiment relates to reporting of applicable / supported functionality. In the second embodiment described above, "supported ID" can be read as "applicable / supported functionality" and applied to this embodiment. Also, "duration corresponding to ID" in the second embodiment can be read as "consistency duration" and applied to this embodiment.

[0294] The UE may report applicable / supported functionality within the consistency duration.

[0295] Applicable / Supported Functionality Applicable / supported functionality preferably satisfies at least one of the following conditions.

[0296] <Condition 1> A specific indicator (metric) derived from a data set (measurement results) collected / measured within the corresponding consistency duration is greater / less than a certain threshold. The specific indicator or threshold may be set / indicated by higher layer signaling / physical layer signaling, predefined by a specification, or determined based on UE capabilities.

[0297] Condition 2: The model / functionality may be trained / derived based on a data set (measurements) collected / measured within the corresponding consistency duration. For example, the model / functionality may be trained / derived based on a certain number or more data samples (measurements) collected / measured within the consistency duration.

[0298] The predetermined number may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined based on UE capabilities.

[0299] According to condition 2, it is possible to utilize a dataset corresponding to a specific ID to train / fine-tune a model.

[0300] <Condition 3> The UE may determine / judge applicable / supported functionality based on at least one of the conditions listed in options 1 to 4 below.

[0301] <Option 1> The UE may determine / judge applicable / supported functionality based on a performance-related KPI (which may be referred to as a performance KPI). More specifically, the UE may determine / judge applicable / supported functionality based on whether the performance KPI is greater than or less than a certain requirement (threshold).

[0302] The threshold may be set / indicated by higher layer / physical layer signaling or may be predefined by a specification.

[0303] Performance KPIs may be set / indicated by higher layer signaling / physical layer signaling.

[0304] A performance KPI may be calculated over a certain duration, for example, an average value of performance over a certain duration may be used as the performance KPI.

[0305] If the performance KPI is greater than a certain threshold, the UE may determine / judge that the corresponding ID can be supported, and if the KPI is less than a certain threshold, the UE may determine / judge that the corresponding functionality cannot be applied / supported.

[0306] <Option 2> The UE may determine / judge applicable / supported functionality based on the UE status (UE state) shown in Options 2-1 to 2-4: Overheating condition (Option 2-1), Computational resources (Option 2-2), Memory storage (Option 2-3), Power battery (Option 2-4).

[0307] For example, the UE may compare the status of the above-mentioned options 2-1 to 2-4 with a certain threshold and determine / judge applicable / supported functionality based on the result.

[0308] <Option 3> The UE may determine / judge applicable / supported functionality based on the assistance information received from the NW. For example, the UE may determine / judge that a corresponding functionality is applicable / supportable if the status / condition of the model / function matches the assistance information received from the NW.

[0309] <Option 4> The UE may determine / judge applicable / supported functionality based on sensing information (detection information), which may be any information (measurement / detection value, etc.) detected by the UE, such as L1-RSRP / SINR or information about the surrounding environment.

[0310] For example, the UE may determine / assess that the corresponding functionality is applicable / supportable if the state / condition of the model / function matches the sensing information.

[0311] For each of the above options, the UE may be configured with higher layer parameters to determine whether to apply any of the options (whether to determine / judge applicable / supported functionality based on any of the options).

[0312] <Reporting of Applicable / Supported Functionality> The UE may report applicable / supported functionality within the consistency duration via signaling as described in Supplementary Note 3 below (e.g. using the following messages): - UECapabilityInformation message (message containing UE capability information) - UEAssistanceInformation message (message containing UE assistance information) - RRCReconfigurationComplete message (message containing information about RRC configuration completion)

[0313] The NW may start (trigger) reporting of applicable / supported functionality based on at least one condition / rule shown in the following options 1-1 to 1-4. In this case, the UE may report applicable / supported functionality based on a trigger (such as an instruction to start reporting) from the NW.

[0314] <Option 1-1> The UE may report applicable / supported functionality based on a configuration from the NW. For example, the UE may periodically report applicable / supported functionality based on a configured / predefined period.

[0315] <Option 1-2> The UE may report applicable / supported functionality based on the configuration from the NW. For example, when the serving cell is switched, the UE may periodically report applicable / supported functionality.

[0316] <Options 1-3> The UE may report applicable / supported functionality based on an inquiry / instruction from the NW. For example, the UE may report applicable / supported functionality when it receives an inquiry / instruction from the NW to report applicable / supported functionality.

[0317] <Options 1-4> The UE may report applicable / supported functionality if it receives at least one of the following assistance information: In addition to the above, the assistance information may be at least one of the following:

[0318] Dataset information (for example, a dataset ID may be defined that indicates the characteristics of the channel in which the UE is present / present in the vicinity, and the characteristics of the measurement values ​​that the UE can obtain) Network placement (location) information (for example, a network placement ID that indicates the placement of the gNB may be defined) Environment information (for example, an environment ID that indicates the environment in which the UE is present (LOS / NLOS environment, etc.) may be defined)

[0319] By utilizing this assistance information, the UE can determine / determine the applicable / supported functionality appropriately based on the received assistance information.

[0320] The UE may start transmitting (reporting) applicable / supported functionality if the configured / predefined rules are met. Specifically, the UE may start reporting supported IDs based on at least one condition / rule shown in options 1 to 6 below.

[0321] <Option 1> The UE may start reporting applicable / supported functionality if certain higher layer parameters (RRC parameters) are configured, which may be parameters related to reporting applicable / supported functionality.

[0322] <Option 2> If the UE has not reported (sent) applicable / supported functionality and if at least one of the following options 2-1 to 2-3 is met, the UE may start reporting applicable / supported functionality.

[0323] [Option 2-1] The UE is configured with certain higher layer parameters for reporting applicable / supported functionality.

[0324] [Option 2-2] The UE reports (sends) at least one of the conditions of applicable / supported functionality.

[0325] [Option 2-3] The UE is configured with a model / functionality, i.e., the configured model / functionality has been determined / determined.

[0326] <Option 3> The UE may start reporting applicable / supported functionality if the applicable / supported functionality differs from the functionality reported / indicated in the last (latest) report (transmission). Types of cases where functionality differs can be broadly divided into the following options 3-1 to 3-3.

[0327] [Option 3-1] When the configurable functionality differs from the indicated functionality.

[0328] [Option 3-2] When the configured functionality differs from the indicated functionality.

[0329] [Option 3-3] When the activated / monitored functionality differs from the indicated functionality.

[0330] <Option 4> The UE may start reporting applicable / supported functionality if a predetermined timer for reporting applicable / supported functionality is not running. The timer length may be set / indicated by higher layer signaling / physical layer signaling or may be predefined by a specification. For example, if the timer length is not set / indicated, a default / initial value may be determined based on a predefined value.

[0331] <Option 5> The UE may start reporting applicable / supported functionality if there is applicable / unsupported functionality. Types of cases where applicable / unsupported functionality exists can be broadly divided into the following options 5-1 to 5-3.

[0332] [Option 5-1] If at least one of the configurable models / functionalities is not applicable.

[0333] [Option 5-2] If at least one of the configured models / functionalities is not applicable.

[0334] [Option 5-3] If at least one of the activated / monitored models / functionalities is not applicable.

[0335] <Option 6> The UE may start reporting applicable / supported functionality if there is applicable / supported functionality. Types when a supported ID exists can be broadly divided into the following options 6-1 to 6-3.

[0336] [Option 6-1] If at least one of the configurable models / functionalities is applicable.

[0337] [Option 6-2] If at least one of the configured models / functionalities is applicable.

[0338] [Option 6-3] If at least one of the activated / monitored models / functionalities is applicable.

[0339] The UE may report applicability only for certain functionality, which may be configured / indicated by higher layer / physical layer signaling, predefined by a specification, or determined based on UE capabilities. The UE may receive a request for support.

[0340] Initiation and Restrictions on Reporting of Applicable / Supported Functionality The UE may not initiate or drop reporting of applicable / supported functionality if any of the following options apply:

[0341] Option 1: The UE may not start reporting or may stop (drop) reporting of applicable / supported functionality if the corresponding consistency duration has ended (expired).

[0342] For example, the end timing of the consistency duration may be represented by a time offset Z. The time offset Z may be set / indicated from the NW by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined based on UE capabilities. For example, Z may be determined based on a parameter included in information about the ID / consistency indication transmitted from the NW.

[0343] <Option 2> If the UE receives an indication of the end of the consistency duration or if the UE receives another consistency indication, the UE may not start reporting or may stop (drop) reporting of applicable / supported functionality.

[0344] As mentioned above, the end timing of the consistency duration may be represented by a time offset Z.

[0345] According to the third embodiment described above, the UE can appropriately control the reporting of applicable / supported functionality.

[0346] Fourth Embodiment The fourth embodiment relates to constraints on applicable (applicability) reports.

[0347] Within a consistency duration, the UE may not (should not) expect at least one of the following models / functionalities to be configured / activated, i.e., the UE may be limited (constrained) in reporting the following models / functionalities: - Models / functionalities that are not reported as applicable within the corresponding consistency duration; - Models / functionalities that are reported as inapplicable within the corresponding consistency duration.

[0348] The above-mentioned constraints may be applied for a certain duration before or after the reception of the signaling related to the applicable report. The value of the certain duration x may be set / indicated by the NW via higher layer / physical layer signaling, may be predefined by a specification, or may be determined based on the UE capabilities. For example, x may be determined based on a parameter included in the information about the ID / consistency indication sent from the NW.

[0349] The signaling related to the applicability report may be at least one of the following: Signaling containing information about the applicability of the model / functionality (e.g. PUCCH / PUSCH transmission), PDCCH reception with a DCI format scheduling a PUSCH transmission with a toggled NDI field value on the same HARQ process number as the applicability report transmission.

[0350] According to the fourth embodiment described above, the UE can appropriately control operations related to applicability reporting based on predetermined constraints.

[0351] <Supplementary Notes> [Supplementary Note 1: AI Model Information] In the present disclosure, AI model information may refer to information including at least one of the following: - Input / output information of the AI ​​model. - Pre-processing / post-processing information for the input / output of the AI ​​model. - Parameter information of the AI ​​model. - Training information for the AI ​​model. - Inference information for the AI ​​model. - Performance information regarding the AI ​​model.

[0352] Here, the input / output information of the AI ​​model may include information on at least one of the following: - Contents of the input / output data (e.g., RSRP, SINR, amplitude / phase information in the channel matrix (or precoding matrix), information on the angle of arrival (Angle of Arrival (AoA)), information on the angle of departure (Angle of Departure (AoD)), location information); - Auxiliary information of the data (which may be called meta-information); - Type of the input / output data (e.g., immutable value, floating-point number); - Bit width of the input / output data (e.g., 64 bits for each input value); - Quantization interval (quantization step size) of the input / output data (e.g., 1 dBm for L1-RSRP); - Range that the input / output data can take (e.g., [0, 1]).

[0353] In the present disclosure, the information on AoA may include information on at least one of an azimuth angle of arrival and a zenith angle of arrival (ZoA). The information on AoD may include information on at least one of an azimuth angle of departure and a zenith angle of departure (ZoD).

[0354] In the present disclosure, location information may be location information related to a UE / NW. The location information may include at least one of information (e.g., latitude, longitude, altitude) obtained using a positioning system (e.g., a satellite positioning system (Global Navigation Satellite System (GNSS), Global Positioning System (GPS), etc.)), information about a BS neighboring (or serving) the UE (e.g., a BS / cell identifier (ID), a BS-UE distance, a direction / angle of the BS (UE) as seen from the UE (BS), coordinates of the BS (UE) as seen from the UE (BS) (e.g., X / Y / Z axis coordinates), etc.), a specific address of the UE (e.g., an Internet Protocol (IP) address), etc. The location information of the UE is not limited to information based on the position of the BS, and may be information based on a specific point.

[0355] The location information may include information about its implementation (e.g., location / position / orientation of antennas, location / orientation of antenna panels, number of antennas, number of antenna panels, etc.).

[0356] The location information may include mobility information, which may include information indicating at least one of information indicating a mobility type, a moving speed of the UE, an acceleration of the UE, and a moving direction of the UE.

[0357] Here, the mobility type may correspond to at least one of a fixed location UE, a movable / moving UE, a no mobility UE, a low mobility UE, a middle mobility UE, a high mobility UE, a cell-edge UE, a not-cell-edge UE, etc.

[0358] In the present disclosure, environmental information (for data) may be information about the environment in which the data is acquired / used, and may correspond to, for example, frequency information (such as a band ID), environmental type information (information indicating at least one of indoor, outdoor, Urban Macro (UMa), Urban Micro (Umi), etc.), information indicating Line Of Site (LOS) / Non-Line Of Site (NLOS), etc.

[0359] Here, LOS may mean that the UE and the BS are in an environment where they can see each other (or there is no obstruction), and NLOS may mean that the UE and the BS are not in an environment where they can see each other (or there is an obstruction). The information indicating LOS / NLOS may indicate a soft value (e.g., the probability of LOS / NLOS) or a hard value (e.g., either LOS or NLOS).

[0360] In the present disclosure, meta-information may mean, for example, information regarding input / output information suitable for an AI model, information regarding acquired / acquirable data, etc. Specifically, meta-information may include information regarding beams of RS (e.g., CSI-RS / SRS / SSB, etc.) (e.g., the pointing angle of each beam, the 3 dB beam width, the shape of the pointed beam, the number of beams), layout information of the gNB / UE antenna, frequency information, environmental information, meta-information ID, etc. Note that meta-information may be used as input / output of the AI ​​model.

[0361] The pre-processing / post-processing information for the input / output of the AI ​​model may include information on at least one of the following: Whether to apply normalization (e.g., Z-score normalization (standardization), min-max normalization); Parameters for normalization (e.g., mean / variance for Z-score normalization, min / max for min-max normalization); Whether to apply a specific numerical conversion method (e.g., one hot encoding, label encoding, etc.); Selection rules for whether to use as training data.

[0362] For example, Z-score normalization (x) is performed as a preprocessing step for input information x. ｎｅｗ = (x - μ) / σ, where μ is the mean of x and σ is the standard deviation) ｎｅｗ may be input to the AI ​​model, and the output y ｏｕｔ may be subjected to post-processing to obtain the final output y.

[0363] The information on the parameters of the AI ​​model may include information on at least one of the following: - Information on weights in the AI ​​model (e.g., neuron coefficients (connection coefficients)); - Structure of the AI ​​model; - Type of the AI ​​model as a model component (e.g., Residual Network (ResNet), DenseNet, RefineNet, Transformer model, CRBlock, Recurrent Neural Network (RNN), Long Short-Term Memory (LSTM), Gated Recurrent Unit (GRU)); - Function of the AI ​​model as a model component (e.g., decoder, encoder).

[0364] Note that the weight information in the AI ​​model may include information on at least one of the following: - Bit width (size) of the weight information; - Quantization interval of the weight information; - Granularity of the weight information; - Range that the weight information can take; - Weight parameters in the AI ​​model; - Information on the difference from the AI ​​model before update (if updating); - Weight initialization method (e.g., zero initialization, random initialization (based on normal distribution / uniform distribution / truncated normal distribution), Xavier initialization (for sigmoid function), He initialization (for rectified linear units (ReLU))).

[0365] The structure of the AI ​​model may also include information about at least one of the following: the number of layers, the type of layer (e.g., convolutional layer, activation layer, dense layer, normalization layer, pooling layer, attention layer), layer information, time series specific parameters (e.g., bidirectionality, time step), parameters for training (e.g., type of function (e.g., L2 regularization, dropout function, etc.), where (e.g., after which layer) to place this function).

[0366] The layer information may include information about at least one of the following: Number of neurons in each layer; Kernel size; Stride for pooling / convolutional layers; Pooling method (MaxPooling, AveragePooling, etc.); Residual block information; Number of heads; Normalization method (Batch normalization, instance normalization, layer normalization, etc.); Activation function (Sigmoid, tanh function, ReLU, leaky ReLU information, Maxout, Softmax).

[0367] An AI model may be included as a component of another AI model, for example, an AI model that includes model component #1, ResNet, model component #2, a Transformer model, a dense layer, and a normalization layer in that order.

[0368] The training information for the AI ​​model may include information about at least one of the following: - Information for the optimization algorithm (e.g., type of optimization (Stochastic Gradient Descent (SGD)), AdaGrad, Adam, etc.), parameters of the optimization (learning rate, momentum information, etc.); - Information on the loss function (e.g., information on metrics of the loss function (Mean Absolute Error (MAE)), Mean Square Error (MSE), Cross Entropy Loss, NLL Loss, Kullback-Leibler (KL) Divergence, etc.)); - Parameters to be frozen for training (e.g., layers, weights); - Parameters to be updated (e.g., layers, weights); - Parameters to be (used as) initial parameters for training (e.g., layers, weights); - Method of training / updating the AI ​​model (e.g., (recommended) number of epochs, batch size, number of data to use for training).

[0369] The inference information for the AI ​​model may include information regarding decision tree branch pruning, parameter quantization, and functions of the AI ​​model, etc. Here, the functions of the AI ​​model may correspond to at least one of, for example, time domain beam prediction, spatial domain beam prediction, an autoencoder for CSI feedback, and an autoencoder for beam management.

[0370] An autoencoder for CSI feedback may be used as follows: The UE inputs the CSI / channel matrix / precoding matrix into the AI ​​model of the encoder and transmits the encoded bits as CSI feedback (CSI report). The BS inputs the received encoded bits into the AI ​​model of the decoder to reconstruct the CSI / channel matrix / precoding matrix, which is the output.

[0371] In spatial domain beam prediction, the UE / BS may input measurement results (beam quality, e.g., RSRP) based on sparse (or thick) beams into an AI model and output dense (or thin) beam quality.

[0372] In time domain beam prediction, the UE / BS may input time series (past, present, etc.) measurement results (beam quality, e.g., RSRP) into an AI model and output future beam quality.

[0373] The performance information regarding the AI ​​model may include information regarding the expected value of a loss function defined for the AI ​​model.

[0374] The AI ​​model information in the present disclosure may include information regarding the application range (applicable range) of the AI ​​model. The application range may be indicated by a physical cell ID, a serving cell index, etc. The information regarding the application range may be included in the above-mentioned environment information.

[0375] AI model information regarding a specific AI model may be predetermined in a standard or may be notified to a UE from a network (NW). An AI model defined in a standard may be referred to as a reference AI model. AI model information regarding a reference AI model may be referred to as reference AI model information.

[0376] Note that the AI ​​model information in the present disclosure may include an index for identifying the AI ​​model (which may be referred to as, for example, an AI model index, an AI model ID, a model ID, etc.). The AI ​​model information in the present disclosure may include an AI model index in addition to / instead of the input / output information of the AI ​​model described above. The association between the AI ​​model index and the AI ​​model information (for example, input / output information of the AI ​​model) may be predetermined in a standard, or may be notified to the UE from the NW.

[0377] The AI ​​model information in the present disclosure may be associated with an AI model and may be referred to as AI model relevant information, simply relevant information, etc. The AI ​​model relevant information does not need to explicitly include information for identifying the AI ​​model. The AI ​​model relevant information may be information that includes only meta information, for example.

[0378] In the present disclosure, the model ID may be interchangeably read as an ID (model set ID) corresponding to a set of AI models. Furthermore, in the present disclosure, the model ID may be interchangeably read as a meta information ID. The meta information (or the meta information ID) may be associated with information about a beam (beam setting) as described above. For example, the meta information (or the meta information ID) may be used by the UE to select an AI model taking into account which beam the BS is using, or may be used to notify the BS of which beam to use to apply the AI ​​model deployed by the UE. Furthermore, in the present disclosure, the meta information ID may be interchangeably read as an ID (meta information set ID) corresponding to a set of meta information.

[0379] [Supplementary Note 2: Notification of Information to UE] In the above-described embodiments, any information may be notified (from the NW) to the UE (in other words, reception of any information from the BS by 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.

[0380] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0381] When the notification is made by 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.

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

[0383] [Supplementary Note 3: Notification of Information 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.

[0384] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

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

[0386] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0387] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0388] At least one of the above embodiments may be applied only to UEs that have reported or support certain UE capabilities, for example (by way of example only): Supporting functionality-based LCM; Supporting model ID-based LCM; Supporting model training within a certain duration; Time required to train / update a model; Number of data samples (number of measurements / measurement result samples) required to train / update a model.

[0389] The particular UE capability may indicate support for particular processes / operations / controls / information for at least one of the above embodiments / options / choices.

[0390] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC) (CSI prediction / CSI compression / time beam prediction / spatial domain beam prediction / AI-based positioning, etc.).

[0391] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

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

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

[0394] (Supplementary Notes) The following inventions are supplementary notes regarding an embodiment (0th to 4th embodiments) of the present disclosure. [Supplementary Note 1] A terminal having: a receiving unit that receives an ID associated with a deployment or a scenario, or information regarding the consistency of the deployment or scenario; and a control unit that controls model identification based on the information. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the control unit determines a time when the information can be received based on information of a certain time offset. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit controls reporting of supported IDs or functionality based on a predetermined condition. [Supplementary Note 4] The terminal according to any of Supplements 1 to 3, wherein the control unit controls reporting of applicability to a certain model or functionality based on a specific condition.

[0395] (Wireless Communication System) The 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 thereof.

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

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

[0398] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (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.

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

[0400] 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 located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 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.

[0401] 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 (CCs) and dual connectivity (DC).

[0402] 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)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 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.

[0403] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

[0405] The base station 10 may be connected to the core network 30 directly or via another base station 10. 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), and the like.

[0406] The core network 30 may include network functions (Network Functions (NF)) such as 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). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

[0408] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0409] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

[0411] Furthermore, 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)), or the like may be used as an uplink channel.

[0412] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

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

[0414] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0415] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0416] One 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 configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0417] 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 scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0418] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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

[0420] 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 the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0421] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like 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).

[0422] (Base Station) Fig. 9 is a diagram showing an example of the 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 base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

[0424] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0425] 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 (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0426] 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 configured with 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 common understanding in the technical field related to the present disclosure.

[0427] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0428] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

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

[0431] The transmitter / receiver unit 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, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0432] The transmitter / receiver unit 120 (transmission processing unit 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.

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

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

[0435] 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, thereby acquiring user data, etc.

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

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

[0438] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0439] The transceiver 120 may transmit an ID associated with a deployment or a scenario, or information regarding the consistency of the deployment or the scenario. The controller 110 may control generation of the information for model identification.

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

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

[0442] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

[0444] 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 configured with 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 common understanding in the technical field related to the present disclosure.

[0445] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0446] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

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

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

[0450] The transmitter / receiver unit 220 (transmission processing unit 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.

[0451] Whether or not to apply DFT processing may be based on the setting 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 transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

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

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

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

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

[0456] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0457] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0458] The transceiver 220 may receive an ID associated with a deployment or a scenario, or information regarding the consistency of the deployment or scenario. The controller 210 may control model identification based on the information. The controller 210 may determine a time when the information can be received based on information about a certain time offset. The controller 210 may control reporting of supported IDs or functionality based on a predetermined condition. The controller 210 may control reporting of applicability to a certain model or functionality based on a specific condition.

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

[0460] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

[0461] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described 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.

[0462] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. 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 drawings, or may be configured to exclude some of the devices.

[0463] 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, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

[0465] The processor 1001, for example, runs 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, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

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

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

[0468] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), 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.

[0469] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. 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 frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0470] 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 outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0471] Furthermore, each device, such as the processor 1001 and the 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.

[0472] 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 this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0473] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present 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 interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

[0475] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

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

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

[0478] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0479] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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.

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

[0481] The TTI may be a transmission time unit for a channel-encoded 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) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0482] 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 for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0483] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0484] In addition, 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 greater than or equal to 1 ms.

[0485] A resource block (RB) is a resource allocation unit in the time domain and the 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, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0486] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

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

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

[0489] 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 their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

[0491] 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 the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0492] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

[0494] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions 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 therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0495] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, 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.

[0496] Furthermore, 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.

[0497] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0498] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0499] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0500] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0501] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

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

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

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

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

[0506] In the present disclosure, the term "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 term "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. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0507] The group 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, and the like.

[0508] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0509] In addition, in the present 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 read interchangeably.

[0510] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0511] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0512] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0513] In the present 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.

[0514] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0515] In the present 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.

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

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

[0518] 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. Note that 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.

[0519] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0520] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile 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.

[0521] 12 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, axles 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.

[0522] The drive unit 41 is configured with 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 handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0523] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, 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).

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

[0525] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0526] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0527] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as 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 driving assistance functions or autonomous driving functions.

[0528] 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 to and from 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, which are provided in the vehicle 40.

[0529] 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 base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0530] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 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-mentioned input.

[0531] The communication module 60 receives various information (traffic information, traffic 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 received by the communication module 60 (or data / information decoded from the PDSCH)).

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

[0533] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments 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) or Vehicle-to-Everything (V2X)). 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, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0534] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0535] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal 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), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0536] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0537] Each aspect / embodiment described in the present disclosure may be a technology other than 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 number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

[0539] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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 a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0540] 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 up in a table, database, or another data structure), ascertaining, etc.

[0541] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0542] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

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

[0544] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...." "does not expect ..." may be interchangeably read as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (e.g., if apparatus A is a UE, apparatus B may be a base station).

[0545] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0546] As used in this disclosure, the terms "connected," "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 elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0547] 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, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0548] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0549] 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." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0550] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0551] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

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

[0553] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0554] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0555] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal having a receiving unit that receives an ID associated with a deployment or a scenario, or information regarding the consistency of the deployment or scenario, and a control unit that controls model identification based on the information.

2. The terminal according to claim 1, wherein the control unit determines the time when the information can be received based on information of a certain time offset.

3. The terminal according to claim 1 or 2, wherein the control unit controls the reporting of supported IDs or functionality based on predetermined conditions.

4. The terminal according to any one of claims 1 to 3, wherein the control unit controls reporting of applicability for a certain model or functionality based on certain conditions.

5. A wireless communication method for a terminal, comprising the steps of: receiving an ID associated with a deployment or scenario, or information regarding the consistency of the deployment or scenario; and controlling model identification based on the information.

6. A base station comprising: a transmitting unit for transmitting an ID associated with a deployment or scenario, or information regarding the consistency of the deployment or scenario; and a control unit for controlling generation of the information for model identification.

Images