Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure comprises: a reception unit that receives, from a Location Management Function (LMF), information relating to consistency in artificial intelligence (AI)-based positioning; and a control unit that applies a specific assumption relating to consistency on the basis of whether a specific parameter is included in the information. In cases where the specific parameter is set or validated, the control unit assumes that the characteristics of a positioning reference signal (PRS) corresponding to the specific parameter are consistent.

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 information regarding consistency in artificial intelligence (AI)-based positioning from a Location Management Function (LMF), and a control unit that applies a specific assumption regarding consistency based on the presence or absence of a specific parameter included in the information, and if the specific parameter is set or enabled, the control unit assumes that the characteristics of a positioning reference signal (PRS) corresponding to the specific parameter are consistent.

[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 diagram illustrating an example of a UE positioning method. FIG. 4 is a diagram illustrating an example of a UE positioning method. FIG. 5 is a diagram illustrating an example of a UE positioning method. FIG. 6 is a diagram illustrating an example of a UE positioning method. FIG. 7 is a conceptual diagram illustrating an example of an ID-based approach to model identification. FIG. 8 is a conceptual diagram illustrating an example of a non-ID-based approach to model identification. FIGS. 9A and 9B are diagrams illustrating an example of timing (start point) for receiving an ID / consistency indication regarding consistency. FIGS. 10A and 10B are diagrams illustrating an example of timing (end point) for receiving an ID / consistency indication regarding consistency. FIGS. 11A and 11B are diagrams illustrating an example of timing (end point) for receiving an ID / consistency indication regarding consistency. FIG. 12 is a diagram illustrating an example of RRC parameters related to CSI reporting configuration. FIG. 13 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 14 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 15 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. Fig. 16 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment. Fig. 17 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] (UE positioning using AI technology) Fingerprinting localization, which estimates the location of wireless devices using the propagation characteristics of wireless signals, is widely used in both Line Of Site (LOS) and Non-Line Of Site (NLOS) scenarios.

[0052] In this disclosure, LOS may mean that the UE and base station are in an environment where they can see each other (or there are no obstructions), and NLOS may mean that the UE and base station are not in an environment where they can see each other (or there are obstructions).

[0053] Fingerprinting location estimates the UE's location based on a database / AI model from the fingerprints of the UE's multiple transmission paths (multipath).

[0054] The multipath information may be, for example, information regarding the Angle of Arrival (AoA) / Angle of Departure (AoD) of the signal for optimal / candidate transmission paths.

[0055] In the present disclosure, the information on AoA may include, for example, information on at least one of azimuth angles of arrival and zenith angles of arrival, and the information on AoD may include, for example, information on at least one of azimuth angles of departure and zenith angles of departure.

[0056] 3GPP Rel. 16 NR supports the following positioning technologies: DL / UL Time Difference Of Arrival (TDOA) based positioning, Angle (DL AoD / UL AoA) based positioning, Multi-Round Trip Time (RTT) based positioning, and Enhanced Cell ID (E-CID) based positioning.

[0057] FIG. 3 is a diagram showing an example of positioning based on DL / UL TDOA. For example, assume that multiple base stations (TRP#0-#2) are arranged around a UE. In this positioning method, the location of the UE is estimated (measured) using a measurement value of the Reference Signal Time Difference (RSTD). For example, the RSTD (T ｉ -T ｊ ) is a certain value (k ｉ，ｊ ) to draw a hyperbola Hｉ，ｊ The intersection of multiple such hyperbolas (H ０，１、 H １，２、 H ２，０ The location of the UE may be estimated by using the RSRP of the reference signal.

[0058] 4 shows an example of DL AoD / UL AoA-based positioning. In this positioning method, the UE's location is estimated using DL AoD measurements (e.g., θ or φ) or UL AoA measurements (e.g., θ or φ). The UE's location may also be estimated using RSRP.

[0059] 5 is a diagram showing an example of multi-RTT-based positioning. In this positioning method, the location of a UE is estimated using multiple RTTs calculated from the Tx / Rx time difference of reference signals (and additionally RSRP, RSRQ, etc.). For example, geometric circles based on the RTTs can be drawn with each base station at its center. The intersection of these multiple circles may be estimated as the location of the UE.

[0060] Figure 6 shows an example of E-CID based positioning, in which the UE location is estimated based on the geometrical location of the serving cell / neighbor cells and additional measurements (Tx-Rx time difference, RSRP, RSRQ, etc.).

[0061] The positioning in the above-mentioned DL (DL TDOA, DL AoD) may be performed on the UE side or the LMF side. For example, in UE-based positioning, the UE may calculate the UE position based on various measurement results of the UE and assistance information from the LMF. Also, in UE-assisted positioning, the UE may report various measurement results to the LMF, and the LMF may calculate the UE position. The assistance information may be information for assisting in estimating the UE's position.

[0062] The above-mentioned UL (UL TDOA, UL AoA) positioning may be performed by the LMF side. In this case, the base station may report various measurement results to the LMF, and the LMF may calculate the UE's position.

[0063] The above-mentioned positioning in DL and UL (multi-RTT, E-CID) may be performed on the LMF side. In this case, the UE / base station may report various measurement results to the LMF, and the LMF may calculate the UE's position.

[0064] Furthermore, in 3GPP Rel. 17, a positioning method using assistance information is proposed for the purpose of further improving positioning accuracy. The assistance information may be transmitted between the UE, the base station, and the LMF as measurement information for the above-mentioned DL / UL-TDOA, DL-AoD / UL-AoA, multi-RTT, and E-CID.

[0065] The assistance information may include information regarding at least one of the following: Timing Error Group (TEG); RSRPP (path-specific RSRP); Expected angle; Adjacent beam information; TRP antenna / beam information; LOS / NLOS indicator; Additional path reports.

[0066] The TEG may indicate one or more Positioning Reference Signal (PRS) resources whose Rx / Tx timing errors are within a certain margin.

[0067] RSRPP may indicate the measurement result of RSRP on the first pass.

[0068] In UL positioning, the assistance information regarding the expected angle may indicate an expected UL-AoA / ZoA. The assistance information may be transmitted to the base station from an LMF. The assistance information may support at least one of UL TDOA, UL AoA, and multi-RTT positioning.

[0069] In DL positioning, assistance information regarding expected angles may include information regarding expected DL-AoA / ZoA or DL-AoD / ZoD. The assistance information may be transmitted from an LMF to a UE. The assistance information may also support at least one of DL TDOA, DL AoA, and multi-RTT positioning. This improves the accuracy of angle-based UE positioning and enables optimization of Rx beamforming of the UE or base station.

[0070] The assistance information regarding the predicted angles may include, in addition to the information on the values ​​of the AoA / ZoA / AoD / ZoD themselves as described above, information indicating the uncertainty range of these values.

[0071] As additional beam information, the neighboring beam information may include information about a subset of DL-PRS resources for the purpose of prioritizing DL-AoD reports (Option 1) or the boresight direction of each DL-PRS resource (Option 2), allowing for optimization of UE Rx beam sweeping and DL-AoD measurements.

[0072] As additional beam information, the assistance information may also include PRS beam pattern information, which may include information regarding the relative power between DL-PRS resources for each angle for each TRP.

[0073] The LOS / NLOS indicator may indicate information regarding Line Of Site (LOS) / Non-Line Of Site (NLOS).

[0074] In addition, in order to improve the positioning delay of the UE, pre-configured measurement gaps (MG), activation of the MG via lower layers, MG-less location, PRS Rx / Tx in RRC_INACTIVE state, or on-demand PRS may be configured for the UE (or may be used by the UE).

[0075] In 3GPP Rel. 17 NR, it is agreed that the UE measures / reports the RSRP of neighboring beams to improve the accuracy of UE location estimation. For example, in a UE-assisted DL-AoD positioning method, the LMF can indicate at least one of the following options 1 and 2 in the assistance information:

[0076] Option 1: A subset of PRS resources for DL-AoD reporting prioritization. The subset may be configured for each PRS resource depending on UE capabilities. The UE may include PRS measurements requested for a subset of PRSs in the DL-AoD additional measurements if required PRS measurements for the associated PRS are reported. The required PRS measurements may be DL PRS RSRP / path PRS RSRP. The UE may report PRS measurements only for a subset of PRS resources. Note that the subset associated with a PRS resource may be in the same / different PRS resource set as the PRS resource. Option 2: Information about the boresight direction configured for each PRS resource depending on UE capabilities.

[0077] In 3GPP Rel. 16 NR, it is agreed that the expected RSTD and its uncertainty range will be indicated from the LMF to the UE. Furthermore, in Rel. 17, it is agreed that the expected angle and its uncertainty range will be indicated from the LMF to the UE in order to reduce errors and complexity in AoA / AoD measurements.

[0078] 3GPP Rel. 17 NR is considering the introduction of a Positioning Reference Unit (PRU) for positioning. The PRU is being discussed as a reference (reference) device with a known location to mitigate transmission and reception timing errors of UEs / gNBs. The PRU may also be read as UE / gNB / TRP (transmission reception point) / TP (transmission point).

[0079] For example, the PRU may support at least one of the following: - Measuring DL PRS and reporting related measurements (e.g., RSTD / transmission time difference / RSRP) to the LMF; - Transmitting SRS and enabling the TRP to measure and report measurements related to the reference device (e.g., Relative Time of Arrival (RTOA) / transmission time difference, AOA) to the LMF; - Operation, measurements, various parameters (parameters related to transmission and reception timing delay, AoD and AOA enhancement, and measurement calibration); - Reporting location coordinate information of the reference device to the LMF if the LMF does not have the location coordinate information; - A reference device with a known location is a UE / gNB; - The accuracy with which the location of the reference device can be known.

[0080] Positioning using AI models has two use cases, for example: Direct AI / ML positioning, and AI / ML assisted positioning.

[0081] Direct AI / ML positioning outputs, for example, UE positioning, while AI / ML-assisted positioning outputs, for example, intermediate features, which may be input back into the AI / ML model.

[0082] Examples of outputs of the AI / ML assisted positioning described above may include at least one of the following: - LOS / NLOS identification (probability of LOS / NLOS), - ToA (time of arrival of PRS / SRS), - Rx-Tx (transmit / receive) time difference, - AoA / AoD, - Number of waves, Rx-Tx (transmit / receive) phase difference (Rel. 18 phase measurement), - DL RSTD / UL TDOA, - DL-PRS / UL-SRS, RSRPs / RSRPPs, - Likelihood of the above values ​​(e.g., ToA probability).

[0083] (Beam Information for UE Positioning) As mentioned above, antenna (configuration) configuration / beam information is considered useful for the AI / M1 model.

[0084] The following scenarios A and B are possible scenarios in which antenna (arrangement) setting / beam information is used.

[0085] [Scenario A] A more appropriate AI model is selected based on antenna settings / frequency / area.

[0086] [Scenario B] The AI ​​model requires metadata (antenna configuration information / beam information) as input to provide better performance.

[0087] Existing specifications support the use of assistance information from the base station (gNB) beam information from the network (NW) to the UE only for positioning purposes.

[0088] The following are being considered for future wireless communication methods: - Using beam information for beam management. - Using beam information in interfaces other than positioning protocols (e.g., LTE Positioning Protocol (LPP)). - Using beam information of RSs other than positioning reference signals (PRSs) for positioning. - Using beam information in the UE.

[0089] In Rel. 17, beam information indicating the direction of a beam (boresight direction) for each PRS is supported as beam information from the LMF to the UE (beam information for UE-based positioning, information on a transmission beam from a base station). The beam information may be information indicating the boresight direction for each PRS.

[0090] The beam information indicating the direction of the beam for each PRS is "DL-PRS-BeamInfoElement" included in the common NR positioning information element "NR-DL-PRS-BeamInfo".

[0091] "DL-PRS-BeamInfoElement" includes information about the azimuth angle and elevation angle of the beam transmitted from the base station (TRP).

[0092] Information about the azimuth angle is "dl-PRS-Azimuth" and "dl-PRS-Azimuth-fine." "dl-PRS-Azimuth" is information expressed in units of 1 degree, with values ​​ranging from 0 to 359 degrees, and "dl-PRS-Azimuth-fine" is information expressed in units of 0.1 degrees, with values ​​ranging from 0 to 0.9 degrees.

[0093] Information about the elevation angle is "dl-PRS-Elevation" and "dl-PRS-Elevation-fine." "dl-PRS-Elevation" is information expressed in 1-degree increments and values ​​from 0 to 180 degrees, while "dl-PRS-Elevation-fine" is information expressed in 0.1-degree increments and values ​​from 0 to 0.9 degrees.

[0094] Furthermore, in Rel. 17, beam information indicating the relative power of DL PRS at each angle (azimuth angle / elevation angle) is supported as beam information from the LMF to the UE (beam information for UE-based positioning, information on the transmission beam of the base station).

[0095] The beam information indicating the relative power is included in the beam antenna information of the TRP in the common NR positioning information element ("NR-TRP-BeamAntennaInfo").

[0096] "NR-TRP-BeamAntennaInfo" includes information "NR-TRP-BeamAntennaInfoAzimuthElevation" regarding the beam antenna information of the TRP for azimuth and elevation angles.

[0097] "NR-TRP-BeamAntennaInfoAzimuthElevation" includes "azimuth" indicating the azimuth angle in 1° granularity, "azimuth-fine" indicating the azimuth angle in 0.1° granularity, and "elevationList" a list of elevation angles.

[0098] The elevation angle list "elevationList" includes "elevation" indicating the elevation angle in 1° granularity, "elevation-fine" indicating the elevation angle in 0.1° granularity, and a beam power list "beamPowerList".

[0099] The beam power list "beamPowerList" includes "nr-dl-prs-ResourceSetID" indicating the resource set ID of the DL PRS, "nr-dl-prs-ResourceID" indicating the resource ID of the DL PRS, "nr-dl-prs-RelativePower" indicating the relative power of the resource given by "nr-dl-prs-ResourceID" in 1 dB granularity, and "nr-dl-prs-RelativePowerFine" indicating the relative power of the resource given by "nr-dl-prs-ResourceID" in 0.1 dB granularity.

[0100] Furthermore, in Rel. 17, information indicating an antenna reference point (ARP) is supported as beam (antenna) information (information on the transmission beam of the base station) from the LMF to the UE.

[0101] This information is indicated by the "referencePoint" in "NR-TRP-LocationInfo", which is the location information of the TRP in the common NR positioning information element.

[0102] The TRP location information "NR-TRP-LocationInfo" is expressed by the relative positions between reference points.

[0103] The ARP location of a PRS resource is expressed as a relative location associated with the ARP location of the PRS resource set.

[0104] The antenna reference point is designated by altitude, latitude and longitude.

[0105] In addition, in Rel. 17, information regarding the spatial direction of DL PRS is supported as information from a base station (e.g., a gNB, a Next Generation Radio Access Network (NG-RAN) node) to an LMF (information regarding the transmission beam of the base station).

[0106] The information includes information indicating the azimuth and elevation boresight directions of the PRS resource.

[0107] The information also includes transition information from a local coordinate system (LCS) to a global coordinate system (GCS).

[0108] A GCS may be defined for a system including multiple base stations and multiple UEs, and an LCS may define an array antenna for one base station or one UE.

[0109] The LCS is used as a reference to define the vector far-field of each antenna element in the array. The vector far-field is a pattern and polarization. The placement of the array within the GCS may be defined by a transformation between the GCS and the LCS. The GCS / LCS may be derived, for example, based on definitions and transformation formulas (defined in the specification) that would be recognized by one skilled in the art.

[0110] In addition, Rel. 17 supports information indicating the beam / antenna of the TRP as information from a base station (e.g., a gNB) to an LMF (information regarding the transmission beam of the base station).

[0111] The information includes information indicating the relative power of the DL PRS at each angle (azimuth / elevation).

[0112] In addition, Rel. 17 supports information about the receiving beam when measuring a UL signal as information from a base station (e.g., a gNB) to an LMF (information about the receiving beam of the base station).

[0113] The information includes at least one of a PRS resource ID, a PRS resource set ID, and an SSB index.

[0114] Furthermore, Rel. 17 supports information about spatial relationships as information transmitted from a UE to a NW (information about a transmission beam of the UE).

[0115] The information indicates the ID / index of a particular RS (e.g., SSB / CSI-RS / SRS / DL PRS).

[0116] In addition, Rel. 17 defines the number of receiving beams for a UE in beam sweeping for positioning. A UE may report the support of its UE capabilities to the LMF.

[0117] For example, in FR1, the UE uses one receive beam.

[0118] In FR2, if the UE supports a specific UE capability, the number of beams indicated by the information "numberOfRxBeamSweepingFactor" indicating the number of Rx beam sweeping factors for FR2 is used. Otherwise, the UE uses eight receiving beams.

[0119] In addition, information regarding the receiving beam that the UE uses for measurements (e.g., "nr-DL-PRS-RxBeamIndex") is supported.

[0120] For this information, if different beams are used within a DL PRS resource set, the UE may report measurements received on the same receiving beam.

[0121] In other words, the beam information transmitted by the UE is information indicating whether the same beam is used between resource sets.

[0122] (UE-based DL positioning) This section describes a case where the UE performs positioning using the UE-side AI model. The UE may use the AI ​​model to infer UE positioning (UE positioning, location). The UE may report the inferred positioning result to the LMF.

[0123] The inference of the AI ​​model in the UE may be performed based on a data set that the UE has. The input information for the AI ​​model (input information) may include raw data (information about characteristics) measured by the UE / assistance information. The UE may receive the assistance information from a base station or an LMF.

[0124] The raw measurement results (which may also be referred to as measured features) measured by the UE may include data (information) related to at least one of the following (note that information listed with a comma does not necessarily have to be included in its entirety; the same applies hereinafter in this disclosure): UE DL-PRS-RSRP (or DL-PRS-RSSI / RSRQ) measurement results of multiple reference TRPs, DL-RSTD measurement results of multiple reference TRPs, Time of Arrival (ToA) measurement results of the reference TRPs, AoD measurement results of the reference TRPs, quality of various measurements, timestamps (times) of the measurement results, Physical Cell ID (PCI), Global Cell ID (GCI), Absolute Radio Frequency Channel Number (ARFCN), PRS resource ID, PRS resource set ID, and PRS ID for each measurement, UE Rx TEG for DL ​​RSTD measurement. ID, TRP Tx TEG ID, UE Tx TEG ID, UE RxTx TEG ID, TRP Rx TEG ID, TRP RxTx TEG ID, DL-PRS receive beam index, First path DL-PRS-RSRP measurement results, Channel impulse response / Channel frequency response, Coded channel impulse response / Coded channel frequency response, Phase difference at different antennas in the antenna array, Received multipath characteristics of the reference TRP (e.g., each path DL-PRS-RSRP measurement results, amplitude / mean / Cumulative Distribution Function (CDF) of estimated multipath amplitude, path loss, root-mean-square (rms) delay spread, kurtosis of channel impulse response).

[0125] Note that GCI may be interchangeably read as NR Cell Global Identity (NCGI).

[0126] The assistance information notified by the base station / LMF may include information on at least one of the following: - Noise of the ground truth dataset (such as the expected variance of noise); - Physical cell ID (PCI), global cell ID (GCI), ARFCN, and PRS ID of the NR TRP candidate to be measured; - Timing relative to the serving (reference) TRP of the NR TRP candidate; - SSB information of the TRP (time / frequency occupancy of the SSB); - DL-PRS configuration of the candidate NR TRP; - Spatial direction information of the DL-PRS resource of the TRP provided by the base station (azimuth angle, elevation angle, etc.); - Geographical coordinates of the TRP provided by the base station (including the transmission reference position for each DL-PRS resource ID, the reference position of the transmitting antenna of the reference TRP, and the reference positions of the transmitting antennas of other TRPs); - Candidate NR Fine timing relative to the serving (reference) TRP; PRS-specific transmission point indication (TP indication); Association information between TRP Tx TEG ID and DL-PRS resources; Information on LOS / NLOS for each DL-PRS-RSRP / DL-PRS-RSSI / DL-RSTD / ToA / AoD / phase difference measurement; On-demand DL-PRS configuration; TRP beam / antenna information (including azimuth angle, zenith angle, and relative power between PRS resources for each angle in each TRP); Expected angle assistance information; PRS priority list.

[0127] The above-mentioned ground truth dataset may be interpreted as a dataset representing location information used for AI training / validation / testing.

[0128] The UE may output the UE location from the AI ​​model. The above AI model on the UE side having the UE location as an output can also be applied to UL-based positioning, DL UL-based positioning, etc. These inputs may include, for example, UE / gNB measurement results, extracted features, etc., or may include features extracted on the gNB side, or may include features extracted on the LMF side, etc.

[0129] (Positioning Classification) Positioning using AI models may be classified as follows: (1) UE-based positioning; (2) AI / ML-assisted positioning; and (3) NG-RAN (Next Generation-Radio Access Network) node-assisted positioning.

[0130] (1) UE-based positioning can be further classified as follows: (1-1) Direct AI / ML positioning in the UE-side model, (1-2) AI / ML-assisted positioning in the UE-side model, and non-AI-based positioning in the UE-side algorithm.

[0131] (2) AI / ML assisted positioning can be further classified as follows: (2-1) AI / ML assisted positioning in the UE side model and non-AI based positioning in the LMF side algorithm, (2-2) direct AI / ML positioning in the LMF side model.

[0132] (3) NG-RAN node assisted positioning can be further classified as follows: (3-1) AI / ML assisted positioning in the gNB side model and non-AI based positioning in the LMF side algorithm, (3-2) direct AI / ML positioning in the LMF side model.

[0133] For each of the above-mentioned positioning methods, the following are being considered: - Type of measurement as model inference input (new measurement / existing measurement); - For positioning methods (1) and (2) above, it is assumed that the UE will measure as model inference input; - For positioning method (3) above, it is assumed that the TRP (gNB / LMF) will measure as model inference input; - Reporting measurement results as model inference input to the LMF for the LMF-side models (2-2, 3-2); - For AI / ML-assisted positioning, new measurement reports / existing measurement reports may be extended as model outputs to the LMF for UE-assisted (2-1) and NG-RAN node-assisted positioning (3-1); - Extension of assistance signaling / procedures to facilitate model inference for both the UE-side model and the NW-side model.

[0134] The positioning methods (1) to (3) above may be collectively referred to as AI / ML-based positioning. That is, positioning using an AI model, the above-mentioned positioning methods, and AI / ML-based positioning (AI-based positioning) may be interchangeable.

[0135] (Performance metrics for positioning) Rel. 17 positioning specifies that the following metrics be applied for performance evaluation (TR 38.857). Note that the percentiles of positioning error may be 50%, 67%, 80%, and 90%.

[0136] Horizontal accuracy: Horizontal accuracy may indicate the difference between the calculated horizontal position of the UE and the actual horizontal position of the UE. For example, the horizontal accuracy may be less than 0.2 meters for 90% of the UEs.

[0137] Vertical accuracy: Vertical accuracy may indicate the difference between the calculated vertical position of the UE and the actual vertical position of the UE. For example, the vertical accuracy may be less than 1 meter for 90% of the UEs.

[0138] Latency The latency may be, for example, the end-to-end latency for UE location estimation. The latency may be less than 100 milliseconds (more preferably, on the order of 10 milliseconds). The latency may include processing delays of the various nodes involved (UE, gNB, AMF, LMF, etc.) and signaling delays between the nodes. Another latency may include the physical layer latency for UE location estimation. The latency may be, for example, less than 10 milliseconds.

[0139] Performance metrics for model monitoring can be at least one of the following: Performance, Latency, Complexity.

[0140] Performance may include at least one of the following: Horizontal accuracy (meters) of AI / ML based positioning; Vertical accuracy (meters) of AI / ML based positioning; Accuracy of intermediate feature (meters) of AI / ML based positioning.

[0141] The horizontal accuracy may indicate the difference between the calculated horizontal position of the UE and the actual horizontal position of the UE. For example, the horizontal accuracy may be less than 0.2 m for 90% of the UEs.

[0142] The vertical accuracy may indicate the difference between the calculated vertical position of the UE and the actual vertical position of the UE. For example, the vertical accuracy may be less than 1 m for 90% of the UEs.

[0143] The intermediate feature accuracy may indicate the difference between the inferred intermediate value and the intermediate value derived based on the actual UE location, and may be indicated by at least one of the following: accuracy of the LOS / NLOS indicator (error rate %), ToA (milliseconds), AoA (degrees), RSTD (milliseconds), RSRP (dBm), etc.

[0144] Latency may include at least one of the following: Physical layer latency (ms); End-to-end latency (ms).

[0145] The latency in the positioning procedure may be defined according to a predetermined rule, and the latency (start time / end time) of the physical layer may be defined individually depending on the positioning method.

[0146] For example, in the case of UE-based positioning, the start time may be the timing when the UE transmits a PUSCH including an MG request (Alt1), the timing when the gNB transmits an LPP message including assistance data using a PDSCH (Alt2), or the timing when the UE starts receiving DL PRS (Alt3). In addition, the end time in this case may be the timing when the gNB successfully decodes a PUSCH including an LPP Provide Location Information message, or if not successful, the timing when the UE performs a location estimation calculation.

[0147] In the case of UE-assisted positioning / LMF-based positioning, the start time may be the timing when the gNB transmits a PDSCH including an LPP Request Location Information message. In addition, the end time in this case may be the timing when the gNB successfully decodes a PUSCH including an LPP Provide Location Information message.

[0148] In the case of NG-RAN node-assisted positioning, the start time may be the timing when the gNB receives the NRPPa measurement request message, and the end time in this case may be the timing when the gNB transmits the NRPPa measurement response message.

[0149] In addition, in terms of the latency of an AI model, the start time may be the time when the UE / NW receives the input of the model inference, and the end time may be the time when the NW / UE receives the output of the AI ​​model.

[0150] The end-to-end latency may be the latency for the UE's location estimation.

[0151] The latency may also include higher layer latency as another latency. The latency may include processing delays of various related nodes (UE, gNB, AMF, LMF, etc.) and signaling delays between nodes. The definitions of each latency described above may follow the definitions in Rel. 17.

[0152] Complexity may be defined by the computational complexity (floating point operations (FLOPs)) of model inference. The complexity of an AI model may also be defined by, for example, the data size (Mbytes) of the model or the number of parameters associated with the AI ​​model.

[0153] (Performance Monitoring (Model Monitoring) for Positioning) Performance metrics calculation In UE-based positioning, model monitoring for direct AI / ML positioning using a UE-side model may be performed by at least one of the following: <1> Performance metrics calculation in the UE, <2> Performance metrics calculation in the LMF.

[0154] In UE-based positioning, model monitoring for AI / ML-assisted positioning using a UE-side model may be performed by at least one of the following: <3> Performance metric calculation in the UE; <4> Performance metric calculation in the LMF.

[0155] In UE-assisted positioning, model monitoring for AI / ML-assisted positioning by a UE-side model may be performed by: <5> Performance metrics calculation in the LMF.

[0156] In NG-RAN node assisted positioning, model monitoring for AI / ML assisted positioning using a gNB-side model may be performed by at least one of the following: <6> Performance metric calculation at the gNB, <7> Performance metric calculation at the LMF.

[0157] <<Performance Indicator Calculation in Direct AI / ML Positioning Using UE-Side Model>> The performance metrics calculation (model monitoring) in <1> above may be performed according to the following steps: Step 1: The UE obtains a noisy ground truth UE position (a true value related to the UE location). Step 1': The UE obtains an estimated UE position from model inference. Step 2: The UE calculates performance metrics for model monitoring. Step 3: The UE reports the performance metrics for model monitoring. Step 3': The UE requests model activation / deactivation / switching from the LMF. Step 4: The UE receives an instruction for model activation / deactivation / switching from the LMF. Step 5: The UE performs model activation / deactivation / switching.

[0158] The performance metrics calculation (model monitoring) of <2> above may be performed according to the following steps: Step 1: The UE obtains and reports the UE position from model inference. Step 1': The LMF obtains a noisy ground truth UE position (a true value related to the UE location). Step 2: The LMF calculates the performance metrics for model monitoring. Step 3: The UE receives an instruction for model activation / deactivation / switching from the LMF. Step 4: The UE performs model activation / deactivation / switching.

[0159] <<Performance Indicator Calculation in AI / ML Assisted Positioning Using UE-Side Models>> The performance metrics calculation (model monitoring) in <3> above may be performed according to the following steps: Step 1: The UE obtains noisy ground truth data (the true value for certain data (e.g., the UE position)). Step 1': The UE obtains estimated data from model inference. Step 2: The UE calculates performance metrics for model monitoring. Step 3: The UE reports the performance metrics for model monitoring. Step 3': The UE requests model activation / deactivation / switching from the LMF. Step 4: The UE receives a model activation / deactivation / switching instruction from the LMF. Step 5: The UE performs model activation / deactivation / switching.

[0160] The performance metrics calculation (model monitoring) of <4> and <5> above may be performed according to the following steps: Step 1: The UE obtains and reports estimated data from model inference. Step 2: The LMF obtains ground truth data (the true value for certain data (e.g., the UE position)). Step 3: The LMF calculates performance metrics for model monitoring. Step 4: The UE receives an instruction for model activation / deactivation / switching from the LMF. Step 5: The UE performs model activation / deactivation / switching.

[0161] <<Performance Indicator Calculation in AI / ML Assisted Positioning Using a gNB-Side Model>> The performance metrics calculation (model monitoring) in <6> above may be performed according to the following steps. Step 1: The gNB obtains and reports estimated data from model inference. Step 1': The gNB obtains ground truth data (the true value for certain data (e.g., UE position)). Step 2: The gNB calculates performance metrics for model monitoring. Step 3: The gNB reports the performance metrics for model monitoring. Step 3': The gNB requests model activation / deactivation / switching from the LMF. Step 4: The gNB receives an instruction for model activation / deactivation / switching from the LMF. Step 5: The gNB performs model activation / deactivation / switching.

[0162] The performance metric calculation (model monitoring) of <7> above may be performed according to the following steps: Step 1: The gNB obtains and reports estimated data from model inference. Step 2: The LMF obtains ground truth data (the true value for certain data (e.g., UE position)). Step 3: The LMF calculates performance metrics for model monitoring. Step 4: The gNB receives an instruction for model activation / deactivation / switching from the LMF. Step 5: The gNB performs model activation / deactivation / switching.

[0163] <<Application of Performance Metrics on the UE Side>> When model inference is performed on the NW / UE side, the UE may determine whether the requirements of the performance metrics are met.

[0164] The UE may report at least one of the following monitoring information to the NW via higher layer signaling / physical layer signaling such as LPP / MAC CE / DCI / RRC / NRPPa: - Accuracy of the output information of the monitored AI model; - Difference between the inferred horizontal position / vertical position and the actual horizontal position / vertical position; - Difference between the inferred output (ToA, AoA, RSTD, RSRP, etc.) and the output obtained from the actual position (ToA, AoA, RSTD, RSRP, etc.); - Latency difference; - Complexity of the AI ​​model and latency, required complexity; - Binary indicator indicating whether the performance metric requirements are met; - Calculated estimation accuracy (horizontal accuracy / vertical accuracy / intermediate feature accuracy); - Information on the reliability (value) of the estimation accuracy.

[0165] Furthermore, the above-mentioned monitoring information may be reported based on at least one of the following options: <Option 1> - When some of multiple conditions are met (e.g., when performance metrics do not meet certain requirements); <Option 2> - Always report after monitoring (report unconditionally); <Option 3> - Report based on configuration / NW instructions (e.g., periodically, semi-permanently, aperiodically).

[0166] <<Application of performance metrics on the gNB side>> When model inference is performed on the UE / gNB / LMF side, the gNB may determine whether the performance metric requirements are met.

[0167] The UE / LMF may report at least one of the following output information of the AI ​​model to the gNB / LMF via higher layer signaling / physical layer signaling such as LPP / MAC CE / DCI / RRC / NRPPa. In this case, the UE may report to the gNB via the LMF: Inferred UE coordinates, Inferred ToA, Inferred LOS / NLOS indicator, Inferred AoA, RSTD, RSRP, Complexity of the AI ​​model, Latency.

[0168] After comparing the information reported by the UE / information instructed by the LMF with the actual information, the gNB may instruct the UE / LMF of at least one of the above-mentioned monitoring information (UE-side information) via higher layer signaling / physical layer signaling such as LPP / MAC CE / DCI / RRC / NRPPa.

[0169] <<Application of performance metrics on the LMF side>> When model inference is performed on the UE / gNB / LMF side, the LMF may determine whether the performance metric requirements are met.

[0170] The UE / gNB may report at least one of the following output information of the AI ​​model to the NW via higher layer signaling / physical layer signaling such as LPP / MAC CE / DCI / RRC / NRPPa: - Inferred UE coordinates, - Inferred ToA, - Inferred LOS / NLOS indicator, - Inferred AoA, RSTD, RSRP, - Complexity of the AI ​​model, - Latency.

[0171] After comparing the information reported from the UE / gNB with the actual information, the LMF may instruct the UE / gNB of at least one of the above-mentioned monitoring information (UE-side information) via higher layer signaling / physical layer signaling such as LPP / MAC CE / DCI / RRC / NRPPa.

[0172] With regard to the application of performance metrics on the UE / gNB / LMF side as described above, it is preferable that model monitoring and model inference are performed in the same entity (UE / gNB / LMF).

[0173] <Issues in Model Monitoring> With regard to model monitoring of AI / ML-based positioning, consideration is being given to determining for which entities the calculation / application of the above-mentioned performance metrics should be specified.

[0174] For monitoring of AI / ML models in lifecycle management, at least the following metrics / methods are being considered for each use case: - Monitoring based on inference accuracy (including metrics related to intermediate KPIs), - Monitoring based on system performance (including metrics related to system performance KPIs), - Other monitoring, <Option 1> - Monitoring based on data distribution, (a) Input-based: For example, monitoring the validity of AI / ML input (out-of-distribution detection, input data drift detection, SNR, delay spread, etc.), (b) Output-based: For example, output data drift detection, <Option 2> - Monitoring based on application conditions

[0175] Metric calculation for model monitoring may be performed by the UE / NW.

[0176] As mentioned above, when it comes to monitoring AI / ML models for positioning, consideration is being given to who will calculate various metrics, how they will be calculated, and how they will be reported.

[0177] <<Entity that derives performance indicators (monitoring metrics)>> In addition to the above, for performance monitoring of AI / ML-based positioning, the following entities can be used to derive monitoring indicators: UE for Case 1 / Case 2a with (using) the UE-side model; gNB for Case 3a with (using) the gNB-side model; LMF for Case 2b / Case 3b with (using) the LMF-side model.

[0178] Additionally, the following entities are also considered: LMF for case 2a (using UE-side model) and case 3a (using gNB-side model), where monitoring is performed based at least on the provided ground truth labels (or an approximation thereof).

[0179] For example, in cases 2a and 3a, the UE side / gNB side model can be monitored by the UE / gNB or LMF.

[0180] The present disclosure is not limited to the above-described cases, but can also be applied to cases where the model in Case 1 can be monitored by the LMF-side model.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0195] A model transport is then carried out.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0275] (Consistency) Type B1 / B2 are 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.

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

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

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

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

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

[0281] Therefore, the following model identification method (procedure) may be envisaged.

[0282] <Approaches to Model Identification> <ID-Based Approach> FIG. 7 is a conceptual diagram showing an example of an ID-based approach to model identification.

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

[0284] As shown in Figure 7, the UE may receive information about the ID from the gNB (NW), where the ID received by the UE may represent an ID corresponding to (for identifying) at least one of a data set, a model, a period, a measurement setting, and a channel / RS property.

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

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

[0287] As shown in Figure 7, 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.

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

[0289] Non-ID-Based Approach FIG. 8 is a conceptual diagram illustrating an example of a non-ID-based approach to model identification.

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

[0291] As shown in Figure 8, 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 above-mentioned (ID-based) ID.

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

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

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

[0295] The UE may report supported models / functionality as shown in Figure 8. The reported models / functionality may be used for model management among the supported models / functionality.

[0296] In this way, the ID-based / non-ID-based approach allows for good control over model discrimination.

[0297] <Reception of ID / Consistency Instruction> <Reception Timing> Figures 9A and 9B are diagrams showing an example of the reception timing (start point) of an ID / consistency instruction. Figures 10A and 10B are diagrams showing an example of the reception timing (end point) of an ID / consistency instruction. Figures 11A and 11B are diagrams showing an example of the reception timing (end point) of an ID / consistency instruction.

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

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

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

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

[0302] For example, as shown in FIG. 9A, 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.

[0303] Alternatively, as shown in FIG. 9B, 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.

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

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

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

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

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

[0309] <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 10A, the length of the duration may be the same as the time from the start point to the end point (receivable time).

[0310] 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 10B.

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

[0312] 11A, 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.

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

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

[0315] 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 11B, the end point may be the point (start point #2) where the duration corresponding to ID #1 (first receivable time) ends and the duration corresponding to ID #2 (second receivable time) begins, time offset Y.

[0316] Option 6: The end point may be a time offset Y before / after a specific event (e.g., RRC reconfiguration, radio link failure, beam failure detection, handover command reception, handover execution).

[0317] Reception Methods The UE may receive the identity / consistency indication e.g. via the following signaling: - Specific signaling or UE capability request - System information (e.g. SIB) - Group-common signaling (e.g. multicast / broadcast).

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

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

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

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

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

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

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

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

[0326] <IDs Supported in a Consistency Instruction> It is preferable that IDs that can be supported in a consistency instruction satisfy at least one of the following conditions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0343] (Mapping Between Measurement and Reporting) <CSI Report or Reporting> In Rel. 15 / 16 NR, a terminal (also referred to as a user terminal, User Equipment (UE), etc.) generates (also referred to as determining, calculating, estimating, measuring, etc.) channel state information (CSI) based on a reference signal (RS) (or a resource for the RS), and transmits (also referred to as reporting, feedback, etc.) the generated CSI to a network (e.g., a base station). The CSI may be transmitted to the base station using, for example, an uplink control channel (e.g., a Physical Uplink Control Channel (PUCCH)) or an uplink shared channel (e.g., a Physical Uplink Shared Channel (PUSCH)).

[0344] The RS used to generate the CSI may be, for example, at least one of a Channel State Information Reference Signal (CSI-RS), a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Synchronization Signal (SS), a Demodulation Reference Signal (DMRS), etc.

[0345] The CSI-RS may include at least one of a non-zero power (NZP) CSI-RS and a CSI-Interference Management (CSI-IM). The SS / PBCH block is a block including an SS and a PBCH (and corresponding DMRS), and may be referred to as an SS block (SSB). The SS may include at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).

[0346] The CSI may include at least one of a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a CSI-RS Resource Indicator (CRI), a SS / PBCH Block Resource Indicator (SSBRI), a Layer Indicator (LI), a Rank Indicator (RI), L1-RSRP (Layer 1 Reference Signal Received Power), L1-RSRQ (Reference Signal Received Quality), L1-SINR (Signal to Interference plus Noise Ratio), L1-SNR (Signal to Noise Ratio), and the like.

[0347] The UE may receive information related to CSI reporting (report configuration information) and control CSI reporting based on the report configuration information. The report configuration information may be, for example, "CSI-ReportConfig" of an information element (IE) of Radio Resource Control (RRC). Note that in the present disclosure, the RRC IE may be interchangeably read as an RRC parameter, an upper layer parameter, or the like.

[0348] The reporting configuration information (e.g., "CSI-ReportConfig" of the RRC IE) may include, for example, at least one of the following: - Information on the type of CSI report (report type information, e.g., "reportConfigType" of the RRC IE) - Information on one or more quantities of CSI to be reported (one or more CSI parameters) (report quantity information, e.g., "reportQuantity" of the RRC IE) - Information on RS resources used to generate the quantities (the CSI parameters) (resource information, e.g., "CSI-ResourceConfigId" of the RRC IE) - Information on the frequency domain targeted for CSI reporting (frequency domain information, e.g., "reportFreqConfiguration" of the RRC IE)

[0349] For example, the report type information may indicate a periodic CSI (P-CSI) report, an aperiodic CSI (A-CSI) report, or a semi-persistent CSI (SP-CSI) report.

[0350] Furthermore, the reporting amount information may specify a combination of at least one of the above CSI parameters (for example, CRI, RI, PMI, CQI, LI, L1-RSRP, etc.).

[0351] In Rel. 15 / 16, the CRI / SSBRI fields are determined based on the number of CSI-RS resources or the number of SS / PBCH blocks in a resource set, respectively.

[0352] Correspondence / Mapping Between Measured RS / Beams and Reported RS / Beams The UE may separately determine the RS to measure (e.g., CSI-RS / SSB) and the RS to report.

[0353] The UE may report the L1-RSRP of an RS other than the RS being measured. The UE may support reporting the L1-RSRP of an RS other than the RS being measured.

[0354] The UE may determine which RSs to measure and report according to at least one of options 1 to 5 below.

[0355] <<Option 1>> The UE may make the RS decision using specific RRC parameters.

[0356] For example, the UE may make RS decisions using existing RRC parameters (defined up to Rel. 16 / 17).

[0357] The RRC parameters may be included in, for example, parameters for configuring resources for channel measurement / interference measurement, or may be RRC parameters included in a CSI report configuration (e.g., CSI-ReportConfig).

[0358] The UE may be configured with a CSI resource configuration (e.g., CSI-ResourceConfig) that includes the resources of the CSI to be reported in the beam prediction.

[0359] The UE may refer to / determine resources corresponding to existing RRC parameters (e.g., at least one of parameters for resources for channel measurement (e.g., resourceForChannelMeasurement) and parameters for resources for interference measurement (e.g., csi-IM-ResourcesForInterference)) for beam prediction calculation (e.g., input for an AI model).

[0360] Fig. 12 is a diagram illustrating an example of RRC parameters related to a CSI reporting configuration. In the example illustrated in Fig. 12, a parameter (resourcesForReporting) indicating resources for reporting is included in the CSI reporting configuration (CSI-ReportConfig). The parameter (resourcesForReporting) indicating resources for reporting refers to an ID (CSI-ResourceConfigId) of the CSI resource configuration.

[0361] The UE determines the resources to report based on the referenced CSI-ResourceConfigId.

[0362] <<Option 2>> The UE may make the RS decision using specific RRC parameters.

[0363] For example, the UE may determine the RS using new RRC parameters (defined in Rel. 18 / 19 and later).

[0364] The RRC parameters may be, for example, RRC parameters included in a CSI report configuration (for example, CSI-ReportConfig).

[0365] The RRC parameters may be configured for the UE using a CSI resource configuration that includes resources for channel measurements used for beam prediction.

[0366] The RRC parameters may be configured for the UE using a CSI resource configuration that includes resources for interference measurements / interference beam measurements used for beam prediction.

[0367] The RRC parameters may be configured for the UE using a CSI resource configuration that includes the CSI resources reported in the beam prediction.

[0368] <<Option 3>> The UE may determine the RS (resource set of RS) using specific RRC parameters.

[0369] The parameters of the CSI resource configuration (e.g., CSI-ResourceConfig) may be extended.

[0370] The UE may be configured with a resource set for the CSI reported after beam prediction.

[0371] A single CSI resource configuration parameter (e.g., CSI-ResourceConfig) may include both information about the resource set to be reported and information about the resource set to be measured for beam prediction (option 2-1-3-1).

[0372] One CSI resource configuration parameter (e.g., CSI-ResourceConfig) may include either information on a resource set to be reported or information on a resource set to be measured for beam prediction (option 2-1-3-2). In this case, two or more CSI resource configuration parameters (e.g., CSI-ResourceConfig) may be configured for a UE.

[0373] <<Option 4>> The UE may use specific RRC parameters to determine the RS (RS resource).

[0374] The parameters for the resource set may be expanded.

[0375] For example, the UE may be configured with a parameter (e.g., NZP-CSI-RS-ResourceSet) regarding a resource set that includes the resources to be reported and the resources to be measured for beam prediction.

[0376] <<Option 5>> A list may be defined that includes at least one of the resources of the RS to be reported and the resources of the RS to be measured for beam prediction.

[0377] The UE may determine the resources of the RSs to be reported and / or measured based on the list.

[0378] For example, the UE may be configured with a list containing the resource IDs / resource set IDs / CSI resource configurations of the resources to be reported.

[0379] For example, the UE may be configured with a list including resource IDs / resource set IDs / CSI resource configurations of resources to be measured for beam prediction.

[0380] One list may include both information about the resources of the RS to be reported and information about the resources of the RS to be measured for beam prediction.

[0381] One list may include either information about the resources of the RS to be reported or information about the resources of the RS to be measured for beam prediction.

[0382] At least two of the above options 1 to 5 may be applied in combination.

[0383] In the present disclosure, the CSI-RS resource set, the configuration parameters of the CSI-RS resource set, the NZP CSI-RS resource set, the configuration parameters of the NZP CSI-RS resource set (NZP-CSI-RS-ResourceSet), the configuration parameters of the resource set of the SSB for CSI measurement (CSI-SSB-ResourceSet), and the configuration parameters of the resource set of the CSI-IM (CSI-IM-ResourceSet) may be read as interchangeable.

[0384] Furthermore, in the present disclosure, the CSI-RS resource, the CSI-RS resource configuration parameter, the NZP CSI-RS resource, and the NZP CSI-RS resource configuration parameter (NZP-CSI-RS-Resource) may be read as interchangeable.

[0385] Validity Area: A validity area is defined for measurement reporting in RRC_idle and RRC_inactive (i.e., RRC idle and RRC inactive states). A UE may perform measurements within the validity area.

[0386] The parameters related to the validity area (validityAreaList) may include, for example, at least one of the following: Absolute radio-frequency channel number (ARFCN-ValueNR). Valid cell list (ValidityCellList).

[0387] validityAreaList indicates a list of frequencies and, optionally, for each frequency, a list of cells in the UE for which the UE needs to perform measurements during RRC_idle and RRC_inactive.

[0388] ARFCN-ValueNR may be read interchangeably with carrier frequency (carrierFreq).

[0389] ValidityCellList may refer to a list of physical cell ID ranges (PCI-Range).

[0390] The upper layer parameter (PCI-Range) may refer to a set of physical cell IDs (PCIs) represented by a starting index and a range.

[0391] PCI-Range is used to encode one or more (set) PCIs, where the range is encoded by using a start value and indicating the number of consecutive PCIs in the range (including the start value).

[0392] If the field contains multiple PCI-Ranges, the network may configure overlapping ranges of PCIs.

[0393] As mentioned above, the range may indicate the number of PCIs in the range (including the start value). If the range field is not present, the UE shall apply the value 1, in which case only the PCI value indicated by start (start value) shall be applied. Note that start may indicate the lowest PCI in the range.

[0394] (Measurement Settings for Positioning) The following can be exemplified as [information relating to] measurement settings for positioning.

[0395] The information related to the frequency layer may include at least one of the following: dl-PRS-SubcarrierSpacing, dl-PRS-CyclicPrefix, dl-PRS-PointA (lowest subcarrier), dl-PRS-StartPRB (start PRB index from reference point A), and dl-PRS-ResourceBandwidth (24 PRBs to 272 PRBs, 4 PRBs step).

[0396] The information about the resource set may include at least one of the following: nr-DL-PRS-ResourceSetID dl-PRS-Periodicity-and-ResourceSetSlotOffset dl-PRS-ResourceRepetitionFactor dl-PRS-ResourceTimeGap dl-PRS-MutingOption1 and dl-PRS-MutingOption2 NR-DL-PRS-SFN0-Offset: offset of SFN0 slot0 of cell with respect to SFN0 slot0 of reference cell dl-PRS-CombSizeN dl-PRS-NumSymbol: size of the downlink PRS resource in the time domain {2,4,6,12}

[0397] The information about the resource may include at least one of the following: nr-DL-PRS-ResourceID, dl-PRS-SequenceID, starting RE offset, starting slot offset, starting symbol offset, and QCL info.

[0398] (Analysis) As mentioned above, the procedure for model identification is not sufficiently clear. For example, it is necessary to clarify how to guarantee consistency regarding DL / UL positioning among the use cases of AI models.

[0399] More specifically, an example of a DL issue is a method for ensuring consistency for a positioning reference signal (PRS) (Problem 1), and an example of a UL issue is a method for ensuring consistency for a sounding reference signal (SRS) (Problem 2).

[0400] If these are not clear, it may be impossible to reduce overhead, estimate channels, or utilize resources appropriately, which may hinder improvements in communication throughput and communication quality.

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

[0402] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0438] In the present disclosure, ID, consistency, consistency ID, and consistency indication may be read interchangeably.

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

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

[0441] In the present disclosure, the terms entity, specific entity, UE, NW, gNB, and LMF may be read interchangeably.

[0442] In the present disclosure, NW, LMF, gNB, BS, and NG-RAN may be read interchangeably.

[0443] In the present disclosure, the terms performance index and monitoring index may be read interchangeably.

[0444] In the following embodiments, to explain the AI ​​model for communication between UE / gNB (NG-RAN) / LMF, the relevant entities are UE / gNB / LMF, but the application of each embodiment of the present disclosure is not limited to this. For example, for communication between different entities (e.g., communication between UEs), the UE / gNB / LMF in the following embodiments may be replaced with a first UE, a second UE, a third UE, etc. In other words, the UE / gNB / LMF in the present disclosure may be replaced with any UE / gNB / LMF. Furthermore, the NW / BS / gNB / LMF may be replaced with each other.

[0445] (Wireless Communication Method) The embodiments of the present disclosure can be broadly categorized as follows: First embodiment: Consistency ID / Consistency indication in PRS (for UE). Second embodiment: Consistency ID / Consistency indication in SRS (for UE). Third embodiment: Consistency ID / Consistency indication in PRS (for NG-RAN). Fourth embodiment: Consistency ID / Consistency indication in SRS (for NG-RAN).

[0446] Each embodiment will be described below based on these. Each embodiment / option may be applied alone or in combination.

[0447] In this disclosure, positioning is mainly exemplified as a use case of an AI model, but the contents of this disclosure are not limited to this and can be applied to other use cases.

[0448] In the present disclosure, a consistency indication may be read interchangeably with a consistency flag.

[0449] In this disclosure, "consistent" may mean "same" or "similar," i.e., the collected measurements (predicted values) show the same (similar) data distribution characteristics (trends).

[0450] In the present disclosure, gNB and NG-RAN may be read interchangeably.

[0451] The UE / NW (gNB / LMF) may perform model identification / positioning by applying the following embodiments.

[0452] The UE may receive various settings for model identification / positioning / reporting, and may further report / send the corresponding prediction (positioning) results to the NW.

[0453] The NW may send various settings for model identification / positioning / reporting to the UE, and may also receive corresponding prediction results (reports) from the UE.

[0454] First Embodiment The first embodiment addresses the above-described problem 1 and relates to a consistency ID / consistency indication (for UE) in a PRS, that is, a method of notifying / commanding a UE of consistency for a PRS.

[0455] In a first embodiment, the RS / channel of interest may be a PRS.

[0456] <<Aspect 1-1>> Aspect 1-1 relates to the assumption of the gNB side (transmitting side). That is, in this aspect, when the UE receives an RS / channel transmitted from the gNB, the NW (LMF / gNB) sets / instructs the UE to be consistent so that the UE can determine / understand / assume that the RS / channel is consistent. An example will be described.

[0457] The UE may apply specific assumptions regarding consistency based on the presence or absence of specific configuration regarding consistency (setting of parameters indicating consistency).

[0458] Specifically, when a parameter indicating consistency (Consistency ID / Consistency Indication) is set (enabled) in a particular configuration (configX) and / or when a particular configuration ID (configID) is set / indicated by higher layer signaling / physical layer signaling, the UE may assume at least one of the following for the RS / channel associated with that configuration:

[0459] For example, the UE may assume that the characteristics of the RS / channel are consistent, such as the following:

[0460] (gNB beam-related assumptions) For RS / channels associated with each resource / resource set, the UE may assume that at least one of the following characteristics is consistent: - Spatial transmit filter applied. - Boresight (pointing) direction (horizontal axis / vertical axis). - Relative pointing direction / relationship in pointing direction between resources (e.g., angle of resource #1 < angle of resource #2 < angle of resource #3). - Beam shape (e.g., beam width). - Relative power. Relative power may be a value per angle / per beam / per TRP. - QCL.

[0461] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0462] (Transmission-related assumptions from the gNB) For the RS / channel associated with each resource / resource set, the UE may assume that at least one of the following characteristics is consistent: Doppler shift / Doppler spread / average delay / delay spread; TRP / antenna / antenna panel / RF chain (e.g., the UE may assume that the RS / channel is transmitted by the same TRP / antenna / antenna panel / RF chain); Relative position / relative distance between multiple panels; Carrier / baseband frequency; Frame / subframe / signaling timing; TRP Tx TEG; gNB antenna spacing / transmitter layout.

[0463] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0464] (Specific Configuration (configX)) The specific configuration (configX) may be at least one of the following: - Reporting configuration - Resource configuration - Resource set configuration Specifically, examples include NR-DL-PRS-AssistanceData, NR-DL-PRS-AssistanceDataPerFreq, NR-DL-PRS-PositioningFrequencyLayer, NR-DL-PRS-AssistanceDataPerTRP, DL-PRS-Info, NR-DL-PRS-ResourceSet, and NR-DL-PRS-Resource.

[0465] (Consistency ID) The consistency ID may be at least one of the following: Data set ID Model ID Data collection setting ID Reporting setting ID Resource setting ID Resource set setting ID Specifically, examples include dl-PRS-ID, nr-DL-PRS-ResourceSetID, and nr-DL-PRS-ResourceID.

[0466] (Specific Configuration ID (configID)) The specific configuration ID (configID) may be at least one of the following: Reporting configuration ID. Resource configuration ID. Resource set configuration ID. Specifically, examples include dl-PRS-ID, nr-DL-PRS-ResourceSetID, and nr-DL-PRS-ResourceID.

[0467] In addition, the specific setting (configX) / consistency ID / specific setting ID (configID) is not limited to the contents listed above (e.g., existing parameters), and specific values ​​(parameters) related to consistency may be specified separately by specifications.

[0468] (Area / time / frequency where the assumption is valid) Examples of the area (validity area) where the above-mentioned assumption is valid include the following. The area may simply be called the validity region, etc. - All areas. - A certain area. For example, an area ID / NR cell global ID / NR physical cell ID / Evolved Cell Global Identifier (ECGI), or a set of these IDs.

[0469] The parameters related to the validity area (e.g., the above-mentioned validityAreaList) may include an ARFCN-ValueNR or a list of physical cells (e.g., ValidityCellList). The list of cells may be configured by, for example, a PCI-Range or PCI. Here, a PCI-Range may be a set of physical cells (one or more) represented by a start index (start value) and a range (range).

[0470] The parameters regarding the effective area may be predefined by a specification or may be set / indicated by higher layer / physical layer signaling.

[0471] The validity time for which the above assumption is valid can be exemplified as follows. This time may be simply called the validity time. - All time durations - A certain time duration This duration may be the above-mentioned duration (for example, the consistency application time).

[0472] The frequencies at which the above assumptions are valid (validity frequencies) can be exemplified as follows. The frequencies may be simply called valid frequencies. All frequencies. A specific frequency. For example, a specific band / bandwidth / BWP ID / ARFCN (Absolute radio-frequency channel number), or a set of these.

[0473] According to this aspect, the assumption of consistency on the transmitting side (gNB side) can be clarified.

[0474] <<Aspect 1-2>> Aspect 1-2 relates to the assumption / manner of the UE side (receiving side). That is, in this aspect, an example is described in which the NW (LMF / gNB) sets / instructs the UE to consistently receive the RS / channel transmitted from the gNB.

[0475] Depending on whether or not there is a specific configuration regarding consistency (a setting of a parameter indicating consistency), the UE may apply a specific assumption / manner regarding consistency to control reception of RSs / channels.

[0476] Specifically, when a parameter (consistency ID / consistency indication) indicating consistency is set (enabled) in a specific configuration (configX), and / or when a specific configuration ID (configID) is set / indicated by higher layer signaling / physical layer signaling, the UE may control reception for RS / channels related to that configuration by assuming (applying the method of) at least one of the following:

[0477] The method described below may be called a consistent reception method.

[0478] For example, the UE may control reception of the RS / channel assuming that the characteristics of the RS / channel are consistent.

[0479] (UE Beam Related [Assumption]) For the RS / channel associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: - Spatial receive filter applied. - Boresight direction. - Relative pointing direction / relationship in terms of pointing direction between resources (e.g., angle of resource #1 < angle of resource #2 < angle of resource #3). - Beam shape (e.g., beam width). - Relative power. Relative power may be a value per angle / beam / TRP. - Method / mechanism for determining the receive beam (e.g., random selection of receive beam or selection of best receive beam based on past measurements).

[0480] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0481] (UE Reception-Related [Assumptions]) For RSs / channels associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: - TRP / antenna / antenna panel / RF chain (e.g., the UE may use the same TRP / antenna / antenna panel / RF chain to receive the RSs / channels); - Relative position / distance between multiple panels; - Carrier / baseband frequency; - Frame / subframe / signaling timing; - UE reception TEG (UE Rx TEG); - UE antenna spacing / receiver layout.

[0482] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0483] (Area / time / frequency to which the reception method is applied) Examples of the area (validity area) to which the above-mentioned reception method is applied include the following: The area may simply be called the validity area, etc. - All areas. - A certain area. For example, an area ID / NR cell global ID / NR physical cell ID / Evolved Cell Global Identifier (ECGI), or a set of these IDs.

[0484] The parameters related to the validity area (e.g., the above-mentioned validityAreaList) may include an ARFCN-ValueNR or a list of physical cells (e.g., ValidityCellList). The list of cells may be configured by, for example, a PCI-Range or PCI. Here, a PCI-Range may be a set of physical cells (one or more) represented by a start index (start value) and a range (range).

[0485] The parameters regarding the effective area may be predefined by a specification or may be set / indicated by higher layer / physical layer signaling.

[0486] The validity time for which the above-described receiving method is applied can be exemplified as follows. This time may be simply called the validity time, etc. All time durations A certain time duration The duration may be the above-described duration (for example, the consistency application time).

[0487] The frequencies to which the above-described receiving method is applied (validity frequencies) can be exemplified as follows. The frequencies may be simply called valid frequencies, etc. All frequencies. A specific frequency. For example, a specific band / bandwidth / BWP ID / ARFCN (Absolute radio-frequency channel number), or a set of these.

[0488] According to this aspect, it is possible to clarify the (assumed) consistency on the receiving side (UE side).

[0489] According to this embodiment, the UE can control DL (PRS) reception taking into account the consistency with PRS in positioning.

[0490] Second Embodiment The second embodiment addresses the above-described problem 2 and relates to a consistency ID / consistency indication (for UE) in SRS, that is, a method of notifying / commanding a UE of consistency for SRS.

[0491] In a second embodiment, the RS / channel of interest may be an SRS.

[0492] This embodiment relates to the assumption / manner of the UE side (transmitting side). That is, in this aspect, an example will be described in which the NW (LMF / gNB) sets / instructs consistency to the UE so that the UE transmits RS / channels consistently.

[0493] The UE may apply specific assumptions / manners regarding consistency to control the transmission of RSs / channels based on the presence or absence of specific configuration regarding consistency (setting of parameters indicating consistency).

[0494] Specifically, when a parameter (consistency ID / consistency indication) indicating consistency is set (enabled) in a specific configuration (configX), and / or when a specific configuration ID (configID) is set / indicated by higher layer signaling / physical layer signaling, the UE may control transmission for the RS / channel associated with that configuration by assuming (applying the method of) at least one of the following:

[0495] The method described below may be called a consistent transmission method.

[0496] For example, the UE may control the transmission of the RS / channel assuming that the characteristics of the RS / channel are consistent. Examples of the characteristics are listed below.

[0497] (UE Beam-Related [Assumptions]) For RSs / channels associated with each resource / resource set, the UE may assume that at least one of the following characteristics is consistent: - Spatial transmit filter applied; - Boresight direction; - Relative pointing direction / relationship between resources in terms of pointing direction (e.g., angle of resource #1 < angle of resource #2 < angle of resource #3); - Beam shape (e.g., beam width); - Relative power. Relative power may be a value per angle / per beam / per TRP.

[0498] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0499] (UE Transmission-Related Assumptions) For RSs / channels associated with each resource / resource set, the UE may assume that at least one of the following characteristics is consistent: Doppler shift / Doppler spread / average delay / delay spread; Antenna / antenna panel / RF chain (e.g., the UE may transmit RSs / channels using the same antenna / antenna panel / RF chain); Relative position / distance between multiple panels; Carrier / baseband frequency; Frame / subframe / signaling timing; UE Tx TEG; UE antenna spacing / transmitter layout.

[0500] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0501] (Specific Configuration (configX)) The specific configuration (configX) may be at least one of the following: - Reporting configuration - Resource configuration - Resource set configuration Specifically, examples include SRS-Config, SRS-ResourceSet, SRS-Resource, SRS-PosResourceSet, and SRS-PosResource.

[0502] (Consistency ID) The consistency ID may be at least one of the following: Data set ID Model ID Data collection setting ID Report setting ID Resource setting ID Resource set setting ID Specifically, examples include srs-ResourceSetId, srs-ResourceId, srs-PosResourceSetId, and srs-PosResourceId.

[0503] (Specific Configuration ID (configID)) The specific configuration ID (configID) may be at least one of the following: Reporting configuration ID. Resource configuration ID. Resource set configuration ID. Specifically, examples include srs-ResourceSetId, srs-ResourceId, srs-PosResourceSetId, and srs-PosResourceId.

[0504] In addition, the specific setting (configX) / consistency ID / specific setting ID (configID) is not limited to the contents listed above (e.g., existing parameters), and specific values ​​(parameters) related to consistency may be specified separately by specifications.

[0505] (Area / time / frequency to which the transmission method is applied) Examples of the area (validity area) to which the above-mentioned transmission method is applied include the following: The area may simply be called the validity area, etc. - All areas. - A certain area. For example, an area ID / NR cell global ID / NR physical cell ID / Evolved Cell Global Identifier (ECGI), or a set of these IDs.

[0506] The parameters related to the validity area (e.g., the above-mentioned validityAreaList) may include an ARFCN-ValueNR or a list of physical cells (e.g., ValidityCellList). The list of cells may be configured by, for example, a PCI-Range or PCI. Here, a PCI-Range may be a set of physical cells (one or more) represented by a start index (start value) and a range (range).

[0507] The parameters regarding the effective area may be predefined by a specification or may be set / indicated by higher layer / physical layer signaling.

[0508] The validity time for which the above-described transmission method is applied can be exemplified as follows. This time may be simply called the validity time, etc. All time durations A certain time duration The duration may be the above-described duration (for example, the consistency application time).

[0509] The frequencies to which the above-described transmission method is applied (validity frequencies) can be exemplified as follows. The frequencies may be simply called valid frequencies, etc. All frequencies. A specific frequency. For example, a specific band / bandwidth / BWP ID / ARFCN (Absolute radio-frequency channel number), or a set of these.

[0510] According to this embodiment, the UE can control UL (SRS) transmission taking into account the consistency with SRS in positioning.

[0511] Third Embodiment The third embodiment addresses the above-described problem 1 and relates to a consistency ID / consistency instruction (for NG-RAN) in a PRS, that is, a method of notifying / commanding the NG-RAN of the consistency for the PRS.

[0512] In the third embodiment, the target RS / channel may be a PRS. Also, NG-RAN and gNB may be interchangeable.

[0513] This embodiment relates to the assumption / manner of the gNB side (transmitting side). That is, this aspect describes an example in which the LMF sets / instructs the gNB to transmit the RS / channel consistently (transmits a message including a consistency instruction).

[0514] The LMF may send a message instructing the gNB to perform a predetermined operation, which may be, for example, the gNB transmitting to the UE RS / channels (i.e., PRS) associated with a specific configuration (configX) by applying at least one of the following methods:

[0515] That is, the LMF transmits / instructs the conditions (consistency) under which the gNB transmits RS / channels (i.e., PRS) associated with a particular configuration (configX).

[0516] The gNB may apply (assume / consider) at least one of the following methods to transmit RS / channels (i.e., PRS) associated with a specific configuration (configX) to the UE: The UE may apply (assume / consider) at least one of the following methods to receive the RS / channels transmitted from the gNB:

[0517] The UE may receive the RS / channel from the gNB assuming at least one of the following:

[0518] For example, the gNB may control the transmission of the RS / channel assuming that the characteristic of the RS / channel is consistent. Also, the UE may control the reception of the RS / channel assuming that the characteristic of the RS / channel is consistent. Examples of characteristics are listed below.

[0519] (gNB beam-related assumptions) For the RS / channel associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: - Spatial transmit filter applied. - Boresight (pointing) direction (horizontal axis / vertical axis). - Relative pointing direction / relationship in pointing direction between resources (e.g., angle of resource #1 < angle of resource #2 < angle of resource #3). - Beam shape (e.g., beam width). - Relative power. Relative power may be a value per angle / per beam / per TRP.

[0520] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0521] (Transmission-related assumptions from the gNB) For the RSs / channels associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: - Doppler shift / Doppler spread / average delay / delay spread. - TRP / antenna / antenna panel / RF chain (e.g., the UE may assume that the RSs / channels are transmitted by the same TRP / antenna / antenna panel / RF chain). - Relative position / relative distance between multiple panels. - Carrier / baseband frequency. - Frame / subframe / signaling timing. - TRP Tx TEG. - gNB antenna spacing / transmitter layout.

[0522] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0523] (Specific Configuration (configX)) The specific configuration (configX) may be at least one of the following: Reporting configuration Resource configuration Resource set configuration Specifically, PRSInformationPos, PRSConfiguration, PRSResourceSet-Item, and PRSResource-Item can be exemplified.

[0524] In addition, the message sent by the LMF may include at least one of the following information (e.g., consistency indication / consistency ID / config ID representing configX):

[0525] (Consistency ID) The consistency ID may be at least one of the following: Data set ID Model ID Data collection setting ID Reporting setting ID Resource setting ID Resource set setting ID Specifically, examples include dl-PRS-ID, nr-DL-PRS-ResourceSetID, and nr-DL-PRS-ResourceID.

[0526] (Specific Configuration ID (configID)) The specific configuration ID (configID) may be at least one of the following: Reporting configuration ID. Resource configuration ID. Resource set configuration ID. Specifically, examples include dl-PRS-ID, nr-DL-PRS-ResourceSetID, and nr-DL-PRS-ResourceID.

[0527] In addition, the specific setting (configX) / consistency ID / specific setting ID (configID) is not limited to the contents listed above (e.g., existing parameters), and specific values ​​(parameters) related to consistency may be specified separately by specifications.

[0528] (Time / frequency when the transmission method is valid) Examples of the area (validity area) to which the above-mentioned gNB transmission method (consistency instruction) is applied include the following: The area may simply be called the validity area. - All areas. - A certain area. For example, an area ID / NR cell global ID / NR physical cell ID / Evolved Cell Global Identifier (ECGI), or a set of these IDs.

[0529] The parameters related to the validity area (e.g., the above-mentioned validityAreaList) may include an ARFCN-ValueNR or a list of physical cells (e.g., ValidityCellList). The list of cells may be configured by, for example, a PCI-Range or PCI. Here, a PCI-Range may be a set of physical cells (one or more) represented by a start index (start value) and a range (range).

[0530] The parameters regarding the effective area may be predefined by a specification or may be set / indicated by higher layer / physical layer signaling.

[0531] The validity time for which the above-mentioned gNB transmission method (consistency indication) is valid can be exemplified as follows. This time may be simply referred to as a validity time. - All durations. - A certain duration. This duration may be the above-mentioned duration (for example, the consistency application time).

[0532] The frequencies (validity frequencies) at which the above-mentioned gNB transmission method (consistency indication) is valid can be exemplified as follows. The frequencies may be simply referred to as valid frequencies, etc.: - All frequencies. - A specific frequency. For example, a specific band / bandwidth / BWP ID / ARFCN (Absolute radio-frequency channel number), or a set of these.

[0533] According to this embodiment, the consistency indication from the LMF to the NG-RAN (gNB) can be appropriately controlled. The gNB can control DL (PRS) transmission to the UE taking into account the consistency for the PRS in positioning. The UE can control DL (PRS) reception from the gNB taking into account the consistency for the PRS in positioning.

[0534] Fourth Embodiment The fourth embodiment addresses the above-described problem 2 and relates to a consistency ID / consistency instruction (for NG-RAN) in SRS, that is, a method of notifying / commanding the NG-RAN of the consistency for SRS.

[0535] In the fourth embodiment, the target RS / channel may be an SRS. Also, NG-RAN and gNB may be interchangeable.

[0536] <<Aspect 4-1>> Aspect 4-1 relates to the assumption / manner of the gNB side (receiving side). That is, in this aspect, an example is described in which the LMF sets / instructs the gNB to consistently receive the RS / channel transmitted from the UE (transmits a message including a consistency instruction).

[0537] The LMF may send a message instructing the gNB to perform a predetermined operation, which may be, for example, the gNB receiving from the UE an RS / channel (i.e., SRS) associated with a specific configuration (configX) by applying at least one of the following methods:

[0538] That is, the LMF transmits / instructs the conditions (consistency) under which the gNB receives RS / channels (i.e., PRS) associated with a particular configuration (configX).

[0539] The gNB may apply (assume / consider) at least one of the following methods to receive from the UE the RS / channel (i.e., PRS) associated with a specific configuration (configX): The UE may apply (assume / consider) at least one of the following methods to transmit the RS / channel to the gNB:

[0540] The gNB may receive the RS / channel from the UE assuming (taking into account) at least one of the following:

[0541] For example, the gNB may control reception of the RS / channel assuming that the characteristic of the RS / channel is consistent. Also, the UE may control transmission of the RS / channel assuming that the characteristic of the RS / channel is consistent. Examples of characteristics are listed below.

[0542] (gNB beam-related [assumptions]) For the RS / channels associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: - Spatial receive filter applied. - Boresight (pointing) direction (horizontal axis / vertical axis). - Relative pointing direction / relationship in pointing direction between resources (e.g., angle of resource #1 < angle of resource #2 < angle of resource #3). - Beam shape (e.g., beam width). - Relative power. Relative power may be a value per angle / beam / TRP. - Method / mechanism for determining the receive beam (e.g., random selection of receive beam or selection of best receive beam based on past measurements).

[0543] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0544] (gNB Reception-related [Assumptions]) For the RS / channel associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: - Doppler shift / Doppler spread / average delay / delay spread. - TRP / antenna / antenna panel / RF chain (e.g., the UE may assume that the RS / channel is transmitted by the same TRP / antenna / antenna panel / RF chain). - Relative position / relative distance between multiple panels. - Carrier / baseband frequency. - Frame / subframe / signaling timing. - TRP reception TEG (TRP Rx TEG). - gNB antenna spacing / receiver layout.

[0545] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0546] (Specific Configuration (configX)) The specific configuration (configX) may be at least one of the following: - Reporting configuration - Resource configuration - Resource set configuration Specifically, examples include SRS-Config, SRS-ResourceSet, SRS-Resource, SRS-PosResourceSet, and SRS-PosResource.

[0547] In addition, the message sent by the LMF may include at least one of the following information (e.g., consistency indication / consistency ID / config ID representing configX):

[0548] (Consistency ID) The consistency ID may be at least one of the following: Data set ID Model ID Data collection setting ID Report setting ID Resource setting ID Resource set setting ID Specifically, examples include srs-ResourceSetId, srs-ResourceId, srs-PosResourceSetId, and srs-PosResourceId.

[0549] (Specific Configuration ID (configID)) The specific configuration ID (configID) may be at least one of the following: Reporting configuration ID. Resource configuration ID. Resource set configuration ID. Specifically, examples include srs-ResourceSetId, srs-ResourceId, srs-PosResourceSetId, and srs-PosResourceId.

[0550] In addition, the specific setting (configX) / consistency ID / specific setting ID (configID) is not limited to the contents listed above (e.g., existing parameters), and specific values ​​(parameters) related to consistency may be specified separately by specifications.

[0551] (Area / time / frequency where the reception method is valid) Examples of the area (validity area) to which the above-mentioned gNB reception method (consistency instruction) is applied include the following: The area may simply be referred to as the validity area. - All areas. - A certain area. For example, an area ID / NR cell global ID / NR physical cell ID / Evolved Cell Global Identifier (ECGI), or a set of these IDs.

[0552] The parameters related to the validity area (e.g., the above-mentioned validityAreaList) may include an ARFCN-ValueNR or a list of physical cells (e.g., ValidityCellList). The list of cells may be configured by, for example, a PCI-Range or PCI. Here, a PCI-Range may be a set of physical cells (one or more) represented by a start index (start value) and a range (range).

[0553] The parameters regarding the effective area may be predefined by a specification or may be set / indicated by higher layer / physical layer signaling.

[0554] The validity time for which the above-mentioned gNB reception method (consistency indication) is valid can be exemplified as follows. This time may be simply referred to as the validity time. - All durations. - A certain duration. This duration may be the above-mentioned duration (e.g., the consistency application time).

[0555] The frequencies (validity frequencies) at which the above-mentioned gNB reception method (consistency indication) is valid can be exemplified as follows. The frequencies may be simply referred to as valid frequencies. - All frequencies. - A specific frequency. For example, a specific band / bandwidth / BWP ID / ARFCN (Absolute radio-frequency channel number), or a set of these.

[0556] <<Aspect 4-2>> Aspect 4-2 relates to the assumption / manner of the UE side (transmitting side). That is, in this aspect, when the gNB receives an RS / channel transmitted from the UE, the LMF sets / instructs the gNB to be consistent so that the gNB can determine / understand / assume that the RS / channel is consistent. An example will be described (sending a message including a consistency instruction).

[0557] The LMF may send a message instructing the gNB to perform a predetermined operation, which may be, for example, the gNB receiving from the UE an RS / channel (i.e., SRS) associated with a specific configuration (configX) by applying at least one of the following methods:

[0558] That is, the LMF transmits / instructs the conditions (consistency) under which the gNB receives RS / channels (i.e., PRS) associated with a particular configuration (configX).

[0559] The gNB may apply (assume / consider) at least one of the following methods to receive from the UE the RS / channel (i.e., PRS) associated with a specific configuration (configX): The UE may apply (assume / consider) at least one of the following methods to transmit the RS / channel to the gNB:

[0560] The gNB may receive the RS / channel from the UE assuming (taking into account) at least one of the following:

[0561] For example, the gNB may control reception of the RS / channel assuming that the characteristic of the RS / channel is consistent. Also, the UE may control transmission of the RS / channel assuming that the characteristic of the RS / channel is consistent. Examples of characteristics are listed below.

[0562] (UE Beam-Related [Assumption]) For the RS / channel associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: - Spatial transmit filter applied. - Boresight direction. - Relative pointing direction / relationship in terms of pointing direction between resources (e.g., angle of resource #1 < angle of resource #2 < angle of resource #3). - Beam shape (e.g., beam width). - Relative power. Relative power may be a value per angle / per beam / per TRP.

[0563] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0564] (UE Transmission-Related Assumptions) For the RSs / channels associated with each resource / resource set, the UE / gNB may assume that at least one of the following characteristics is consistent: Doppler shift / Doppler spread / average delay / delay spread; Antenna / antenna panel / RF chain (e.g., the UE may transmit RSs / channels using the same antenna / antenna panel / RF chain); Relative position / relative distance between multiple panels; Carrier / baseband frequency; Frame / subframe / signaling timing; UE Tx TEG; UE antenna spacing / transmitter layout.

[0565] Each of the above mentioned properties may be associated with a particular ID (Consistency ID).

[0566] (Area / time / frequency to which the transmission method is applied) Examples of the area (validity area) to which the above-mentioned transmission method is applied include the following: The area may simply be called the validity area, etc. - All areas. - A certain area. For example, an area ID / NR cell global ID / NR physical cell ID / Evolved Cell Global Identifier (ECGI), or a set of these IDs.

[0567] The parameters related to the validity area (e.g., the above-mentioned validityAreaList) may include an ARFCN-ValueNR or a list of physical cells (e.g., ValidityCellList). The list of cells may be configured by, for example, a PCI-Range or PCI. Here, a PCI-Range may be a set of physical cells (one or more) represented by a start index (start value) and a range (range).

[0568] The parameters regarding the effective area may be predefined by a specification or may be set / indicated by higher layer / physical layer signaling.

[0569] The validity time for which the above-described transmission method is applied can be exemplified as follows. This time may be simply called the validity time, etc. All time durations A certain time duration The duration may be the above-described duration (for example, the consistency application time).

[0570] The frequencies to which the above-described transmission method is applied (validity frequencies) can be exemplified as follows. The frequencies may be simply called valid frequencies, etc. All frequencies. A specific frequency. For example, a specific band / bandwidth / BWP ID / ARFCN (Absolute radio-frequency channel number), or a set of these.

[0571] According to this embodiment, the consistency indication from the LMF to the NG-RAN (gNB) can be appropriately controlled. The UE can control UL (SRS) transmission to the gNB in ​​consideration of the consistency for SRS in positioning. The gNB can control UL (SRS) reception from the UE in consideration of the consistency for SRS in positioning.

[0572] <Supplementary Information> <<AI Model Information>> In the present disclosure, AI model information may mean 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0600] In this disclosure, functionality may refer to a set of parameters (e.g., a set of parameters for CSI prediction / beam prediction / CSI compression) that can be supported based on conditions dictated by UE capabilities.

[0601] The UE may report parameter values ​​related to the functionality / model as conditions to the NW via higher layer signaling (e.g., RRC, MAC CE) / physical layer signaling (e.g., DCI). For example, the UE may report the conditions using UE capability / feature / feature group reporting.

[0602] The UE may report or instruct the parameter values ​​related to the functionality / model as additional conditions to the NW using higher layer signaling / physical layer signaling or methods other than signaling via the air interface of the NW (e.g., operator's configurations, pre-configured messages, etc.).

[0603] The UE may report or be instructed on information / instructions about the parameters corresponding to these additional conditions (e.g., parameter names) as information / instructions about the additional conditions using higher layer signaling / physical layer signaling or methods other than signaling via the air interface of the network (e.g., operator's configurations, pre-configured messages, etc.).

[0604] For example, the UE may report a device ID, a vendor ID, etc. as additional information. The UE may also be notified of a cell ID as an additional condition. The UE may also report or be instructed to report information such as a cell ID / UE ID instead of a parameter name.

[0605] Methods other than signaling via the air interface of the network may be methods related to pre-configuration of the UE (for example, configuration by the UE vendor) or operator configuration provided by the network operator.

[0606] Time Related Information In the present disclosure, time related information may include at least one of the following:

[0607] A time offset between each timing associated with the predicted value and the reference timing, which may mean the CSI reference resource, CSI reporting slot, or measurement occasion used to derive the predicted value.

[0608] A reporting window associated with the predicted value. The start of the reporting window may be represented by a time offset and a reference timing. The reference timing may refer to a CSI reference resource, a CSI reporting slot, or a measurement occasion used to derive the predicted value. The reporting window may be determined by the interval between the timings associated with the predicted value.

[0609] <<Notification of Information to UE>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed 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.

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

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

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

[0613] <<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, PRACH, reference signal), or a combination thereof.

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

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

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

[0617] <<Regarding Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-mentioned embodiments may be applied (used) when one or more of the following conditions are met: - a higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured; - the specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters; - the specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS; - a specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported; - the application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.

[0618] The specific UE capability may indicate at least one of the following: - Supporting the specific process / operation / control / assumption / information. - Supporting functionality-based LCM. - Supporting model ID-based LCM. - Supporting AI / ML-based positioning. - Supporting AI models for obtaining UE location. - Supporting model inference / model monitoring (performance monitoring). - Supporting UE-side monitoring (first monitoring). - Supporting NW (LMF / gNB)-side monitoring. - Supporting two-stage monitoring. - Supporting consistency indication in use cases utilizing AI models (e.g., positioning).

[0619] 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, a band, a band combination, a BWP, a 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).

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

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

[0622] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (first / third embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives information regarding consistency in artificial intelligence (AI)-based positioning from a Location Management Function (LMF); and a controller that applies a specific assumption regarding consistency based on the presence or absence of a specific parameter included in the information, wherein, if the specific parameter is set or enabled, the controller assumes that characteristics of a positioning reference signal (PRS) corresponding to the specific parameter are consistent. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the controller controls reception of the PRS transmitted from a base station by assuming that at least one of a spatial filter, a boresight direction, a relative pointing direction, a beam shape, and a relative power is consistent. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the controller controls consistent reception of the PRS transmitted from a base station by taking into account at least one of a Doppler shift, a transmit timing error group (TEG) of a transmitting / receiving point (TRP), a relative position between multiple panels, a carrier, a frame, and a transceiver layout. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the specific parameters for the consistency instruction transmitted from the LMF to the terminal or the base station include at least one of a data set ID, a model ID, a data collection ID, a reporting configuration ID, a resource configuration ID, and a resource set configuration ID, and the controller controls DL reception based on the specific parameters.

[0623] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (first / third embodiment) of the present disclosure. [Supplementary Note 1] A terminal including: a receiver that receives information regarding consistency in artificial intelligence (AI)-based positioning from a location management function (LMF); and a controller that applies a specific assumption regarding consistency based on the presence or absence of a specific parameter included in the information, wherein, if the specific parameter is set or enabled, the controller assumes that characteristics of a sounding reference signal (SRS) corresponding to the specific parameter are consistent. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the controller controls transmission of the SRS assuming that at least one of a spatial filter, a boresight direction, a relative pointing direction, a beam shape, and a relative power is consistent. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the controller controls consistent transmission of the SRS by taking into account at least one of a Doppler shift, a relative position between multiple panels, a carrier, a frame, a transmit timing error group (TEG), and a transmitter layout. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the specific parameters for the consistency indication transmitted from the LMF to the terminal or the base station include at least one of a data set ID, a model ID, a data collection ID, a reporting configuration ID, a resource configuration ID, and a resource set configuration ID, and the controller controls UL transmission based on the specific parameters.

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

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

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

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

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

[0629] 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 location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as the base station 10.

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

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

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

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

[0634] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn 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.

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

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

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

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

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

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

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

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

[0643] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

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

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

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

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

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

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

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

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

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

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

[0654] (Base Station) Fig. 14 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0672] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0673] The transceiver 120 may receive a message regarding consistency instructions in AI-based positioning from a Location Management Function (LMF). The controller 110 may control consistent transmission of a positioning reference signal (PRS) based on a specific parameter included in the message, taking into account characteristics of the PRS corresponding to the specific parameter.

[0674] The control unit 110 may control consistent reception of a sounding reference signal (SRS) based on a specific parameter included in the message, taking into consideration the characteristics of the SRS corresponding to the specific parameter.

[0675] (User Terminal) Fig. 15 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0693] The transceiver unit 220 may receive information regarding consistency in artificial intelligence (AI)-based positioning from a location management function (LMF). The control unit 210 may apply a specific assumption regarding consistency based on the presence or absence of a specific parameter included in the information. If the specific parameter is set or enabled, the control unit 210 may assume that the characteristics of a positioning reference signal (PRS) corresponding to the specific parameter are consistent. The control unit 210 may control reception of the PRS transmitted from a base station by assuming that at least one of a spatial filter, a boresight direction, a relative pointing direction, a beam shape, and a relative power is consistent. The control unit 210 may control consistent reception of the PRS transmitted from a base station by taking into account at least one of a Doppler shift, a transmit timing error group (TEG) of a transmitting / receiving point (TRP), relative positions between multiple panels, a carrier, a frame, and a transceiver layout. The specific parameters for the consistency indication transmitted from the LMF to the terminal or the base station may include at least one of a data set ID, a model ID, a data collection ID, a reporting configuration ID, a resource configuration ID, and a resource set configuration ID. The control unit 210 may control DL reception based on the specific parameters.

[0694] When the specific parameter is set or enabled, the control unit 210 may assume that the characteristics of the sounding reference signal (SRS) corresponding to the specific parameter are consistent. The control unit 210 may control the transmission of the SRS assuming that at least one of a spatial filter, a boresight direction, a relative pointing direction, a beam shape, and a relative power is consistent. The control unit 210 may control the consistent transmission of the SRS by taking into account at least one of a Doppler shift, a relative position between multiple panels, a carrier, a frame, a transmit timing error group (TEG), and a transmitter layout. The specific parameter for the consistency indication transmitted from the LMF to the terminal or the base station may include at least one of a data set ID, a model ID, a data collection ID, a reporting configuration ID, a resource configuration ID, and a resource set configuration ID. The control unit 210 may control the UL transmission based on the specific parameter.

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

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

[0697] 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. 16 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.

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

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

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

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

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

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

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

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

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

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

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

[0709] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0735] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0759] 17 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0782] 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 ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. 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" (for example, if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

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

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

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

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

[0793] 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 comprising: a receiving unit that receives information regarding consistency in artificial intelligence (AI)-based positioning from a Location Management Function (LMF); and a control unit that applies specific assumptions regarding consistency based on the presence or absence of specific parameters included in the information, wherein if the specific parameters are set or enabled, the control unit assumes that the characteristics of a positioning reference signal (PRS) corresponding to the specific parameters are consistent.

2. The terminal according to claim 1, wherein the control unit controls reception of the PRS transmitted from a base station by assuming that at least one of a spatial filter, a boresight direction, a relative pointing direction, a beam shape, and a relative power is consistent.

3. The terminal according to claim 1, wherein the control unit controls consistent reception of the PRS transmitted from a base station by taking into account at least one of Doppler shift, transmission timing error group (TEG) of a transmission / reception point (TRP), relative positions between multiple panels, carrier, frame, and layout of a transceiver.

4. The terminal according to claim 1, wherein the specific parameters for the consistency instruction transmitted from the LMF to the terminal or base station include at least one of a data set ID, a model ID, a data collection ID, a reporting configuration ID, a resource configuration ID, and a resource set configuration ID, and the control unit controls DL reception based on the specific parameters.

5. A wireless communication method for a terminal, comprising: receiving information regarding consistency in artificial intelligence (AI)-based positioning from a Location Management Function (LMF); and applying a specific assumption regarding consistency based on the presence or absence of a specific parameter included in the information, wherein if the specific parameter is set or enabled, the terminal assumes that the characteristics of a positioning reference signal (PRS) corresponding to the specific parameter are consistent.

6. A base station having: a receiving unit that receives a message regarding a consistency instruction in artificial intelligence (AI)-based positioning from a Location Management Function (LMF); and a control unit that controls consistent transmission of a positioning reference signal (PRS) corresponding to a specific parameter based on the specific parameter and taking into account the characteristics of the PRS.

Images