Terminal, radio communication method, and base station

Abstract

To achieve suitable use of overhead reduction / channel estimation / resources.SOLUTION: A terminal according to an aspect of the present disclosure has: a transmission section that transmits information related to consent to a dataset to be transmitted or received; and a control section that assumes that collection of the dataset is performed within a range of consent based on the information related to the consent.SELECTED DRAWING: Figure 15

Description

[Technical Field]

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) has been specified 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) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 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 Summary of the Invention [Problem to be solved by the invention]

[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] When utilizing AI models, data set / model management is being considered, but in some cases, this is not sufficiently considered. If this consideration is insufficient, optimal overhead reduction, channel estimation, and resource utilization cannot be achieved, which may hinder improvements in communication throughput and communication quality.

[0007] Therefore, one object 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. [Means for solving the problem]

[0008] A terminal according to one aspect of the present disclosure includes a transmitting unit that transmits information regarding consent for a dataset to be transmitted or received, and a control unit that assumes that collection of the dataset will be performed within the scope of consent based on the information regarding consent. [Effects of the Invention]

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

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of a framework for managing AI models. [Figure 2] FIG. 2 is a diagram illustrating an example of specifying an AI model. [Figure 3] FIG. 3 is a diagram illustrating an example of an ORAN architecture. [Figure 4] FIG. 4 is a diagram illustrating an example of a data set. [Figure 5] FIG. 5 is a diagram illustrating an example of acquiring a data set. [Figure 6] FIG. 6 is a diagram illustrating an example of data set transfer. [Figure 7] FIG. 7 is a diagram showing an example of data collection according to procedure 1. In FIG. [Figure 8] FIG. 8 is a diagram showing another example of data collection according to procedure 1. In FIG. [Figure 9] FIG. 9 is a diagram showing another example of data collection according to procedure 1. In FIG. [Figure 10] FIG. 10 is a diagram showing an example of a data collection / data set transfer request according to step 1-2. [Figure 11] FIG. 11 is a diagram showing an example of a request for data / data set according to procedure 1-3. [Figure 12] FIG. 12 is a diagram showing an example of a request for transferable data / data set information according to step 5-1. [Figure 13] FIG. 13 is a diagram showing an example of notification of transferable data set information according to step 5-2. [Figure 14] FIG. 14 is a diagram showing an example of data transfer according to procedure 6. In FIG. [Figure 15] FIG. 15 is a diagram illustrating an example of a report of UE consent according to the first embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] For example, there are plans for terminals (user terminals, user equipment (UE)) / base stations (BSs) to utilize AI technology to improve Channel State Information (CSI) feedback (e.g., reducing overhead, improving accuracy, prediction), improve beam management (e.g., improving accuracy, prediction in the time / space domain), and improve position measurement (e.g., improving position estimation / prediction).

[0013] Based on the input information, the AI ​​model may output at least one piece of information such as an estimated value, a predicted value, 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 / position, future channel state information / radio link quality, etc.

[0014] In this disclosure, AI may be interpreted as an object (also referred to as a subject, object, data, function, program, etc.) that has (performs) at least one of the following characteristics: · inferences based on observed or collected information; · making choices based on information observed or collected; · Predictions based on observed or collected information.

[0015] In this disclosure, estimation, prediction, and inference may be used interchangeably. Also, in this disclosure, estimate, predict, and infer may be used interchangeably.

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

[0017] In addition, in this disclosure, an AI model may be interpreted as an object that has (implements) at least one of the following characteristics: - Producing estimates by feeding information, · Predicting estimates by giving information, · Discover features by providing information, · Selecting behavior by providing information.

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

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

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

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

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

[0023] 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 convolution layer, an activation layer, a dense layer, a normalization layer, a pooling layer, an attention layer, a dropout layer, a fully connected layer, etc.

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

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

[0026] Figure 1 shows an example of a framework for managing AI models. In this example, each stage related to an AI model is shown as a block. This example is also referred to as life cycle management (LCM) of AI models.

[0027] The data collection stage corresponds to a stage of collecting data for generating / updating an AI model. The data collection stage may include data reduction (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.

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

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

[0030] In the model training stage, model training is performed based on the data (training data) transferred from the collection stage. This stage may include data preparation (e.g., performing data preprocessing, cleaning, formatting, conversion, etc.), model training / validation, model testing (e.g., 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).

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

[0032] AI model validation may also refer to the subprocess 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.

[0033] AI model testing may also refer to a sub-process of training to evaluate 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.

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

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

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

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

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

[0039] 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, and model deployment may refer to distributing a fully developed and tested model runtime image (or an image of an execution environment) to (or enabling on) a target (e.g., UE / gNB) where inference will be performed.

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

[0041] 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). The former has advantages in interoperability, large-capacity storage, operator manageability, and model flexibility (feature engineering, etc.). The latter has advantages in that it does not require latency for model updates or data exchange for model deployment. Inference of the model may be performed in, for example, a gNB.

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

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

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

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

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

[0047] Note that model activation may mean activating an AI model for a specific function, model deactivation may mean deactivating 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.

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

[0049] 2 is a diagram showing an example of specifying an AI model. In this example, the UE and the 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.

[0050] (Open RAN (ORAN)) The ORAN architecture will be explained below using Figure 3.

[0051] For 5G NR, standardization of open RAN (ORAN / ORAN Alliance) is being considered to reduce the burden on operators in building and operating RAN and to introduce automation using AI / ML models.

[0052] In the ORAN Alliance architecture, a RAN Intelligent Controller (RIC) may be defined as a logical node that automates and optimizes base station parameter design / configuration / operation in order to realize network operations utilizing AI / ML models.

[0053] As shown in FIG. 3, the RIC may include a non-real-time RIC and a near real-time RIC (which may simply be referred to as a real-time RIC).

[0054] The non-real-time RIC may be located within Service Management and Orchestration (SMO), which monitors, maintains, and orchestrates the RAN.

[0055] The non-real-time RIC may be connected to the near real-time RIC via an A1 interface.

[0056] The near real-time RIC may be connected to E2 nodes such as an O-eNB (ORAN base station), an O-CU (ORAN central unit), and an O-DU (ORAN distributed unit) via an E2 interface. The SMO may be connected to the O-eNB, the O-CU, and the O-DU (ORAN distributed unit) via an O1 interface.

[0057] The non-real-time RIC may cooperate with the functional unit that provides the OAM service within the SMO to collect data accumulated within the E2 node, such as Performance Management Counters, Fault Management Data, and Trace Management Data.

[0058] The near real-time RIC may collect information about the E2 node from the E2 node using the E2 interface, and may control the E2 node according to the policy notified by the non real-time RIC.

[0059] The ORAN architecture shown in FIG. 3 is merely an example and is not limited to this example.

[0060] (analysis) In future wireless communication systems (e.g., Rel. 19 and later), use cases that utilize AI / ML models are expected to require datasets.

[0061] Possible use cases include model training, model validation, model inference, and performance monitoring (verifying performance in the actual field).

[0062] In addition, it is being considered to utilize data collection in the core network (CN), Operation Administration and Maintenance (Management) (OAM), and Over The Top (OTT) for model training on the UE side.

[0063] For example, in the case of training a two-sided model, the following procedure may be considered: Step 1: The network trains the encoder / decoder. Step 2: The network generates input / output datasets for the encoder / decoder based on the encoder / decoder to be trained. In step 2, the NW generates output data from the input. In step 2, the input data is associated with one or more UEs. Step 3: The NW delivers the input / output data sets generated by the encoder / decoder to the UE side (e.g., UE (device) / chip vendor server). Step 4: The UE side trains the encoder / decoder based on the delivered input / output dataset.

[0064] However, in such use cases, there is insufficient consideration given to sharing of data / data sets.

[0065] For example, it is desirable to avoid sharing data related to multiple different users without the users' consent, and when a network distributes a data set to a consumer, the data set should not include data collected by a user other than the consumer. However, there has been insufficient consideration of specific ways to achieve this.

[0066] Furthermore, there has been insufficient consideration given to what the UE should report regarding the consent and how to define the UE's assumptions / expectations regarding the consent (Issue 1).

[0067] In addition, there is insufficient consideration given to what data / data sets the UE receives and the relationship between the data / data sets the UE receives and the data / data sets the UE collects (Issue 2).

[0068] In addition, there is insufficient consideration of the behavior of the data management entity in the network (Issue 3).

[0069] If these considerations are not sufficient, it may not be possible to properly utilize AI / ML models that use datasets in future wireless communication systems, which could hinder improvements in communication throughput.

[0070] Therefore, the present inventors came up with a solution to this problem.

[0071] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0072] (Various reading changes) In this disclosure, words enclosed in "()" in a sentence may indicate an explanation of the immediately preceding wording (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in this disclosure, words enclosed in "[ ]" in a sentence may be interpreted including the meaning of the entire sentence, or may be interpreted excluding the meaning of the entire sentence (ignoring the meaning of the entire sentence). Note that "()" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

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

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

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

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

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

[0079] (Wireless communication method) The following explains terms / phrases in this disclosure.

[0080] In this disclosure, a "dataset" may refer to a set of data samples that are assigned a dataset ID [and dataset-related information].

[0081] In this disclosure, a "data sample" may refer to a component of a data set.

[0082] "Dataset delivery" in this disclosure may refer to the distribution of a dataset (e.g., from a DSM to a consumer / from a provider to a DSM).

[0083] "Data" in this disclosure is a generic term and may refer to a data sample (a component of a dataset) or a dataset.

[0084] "Data collection" in this disclosure may refer to the collection of data (including the distribution / transfer of data samples).

[0085] "Dataset identification" in this disclosure may refer to a procedure for achieving a common understanding / knowledge of a dataset (e.g., understanding the mapping between dataset IDs and datasets).

[0086] In the present disclosure, a "Dataset manage (management) entity (DSM)" may be an entity that manages a dataset.

[0087] The DSM may include at least one of the following functions: · DSMF (dataset manage function) (e.g., dataset identification / dataset distribution / data collection administration). · DSSF (dataset storage function) (e.g., function for saving datasets / data). · DSCF (dataset creating function) (e.g., a function that creates a dataset based on data). DSRF (dataset registration function) (for example, a function to register a dataset in DSM (assign a dataset ID to a dataset)). · DSDF (dataset discovery function) (e.g., the function to discover a specific dataset in a DSM). · DSGF (dataset generation function) (e.g., a function that generates data / datasets based on a sample / statistical model).

[0088] A DSM may be composed of multiple entities, for example, a DSM may include a DSSF entity and a DSCF entity.

[0089] Multiple types of DSMs may be defined. For example, DSM#1 may have DSMF, and DSM#2 may have DSSF / DSCF / DSRF / DSDF.

[0090] The DSM may be any Core Network (CN) / Network Function (NF) / CN NF / SMO / non real-time RIC / real-time RIC.

[0091] In the present disclosure, the NF may, for example, include at least one of the following: Application Function (AF) (for example, a function that realizes an application server outside the 5G Core Network (5GC)). Access and Mobility management Function (AMF) (e.g., function to manage UE registration, location, etc.). Data Network (DN) (e.g., the function to realize a data network outside of 5GC). Location Management Function (LMF) (e.g., communication control function related to location-based services). Non-3GPP Inter-Working Function (N3IWF) (e.g., function connecting untrusted non-3GPP access networks with 5GC). Network Exposure Function (NEF) (e.g., a function that provides an application interface for 5GC NF services to the outside world). Network Slice Selection Function (NSSF) (e.g., the function that selects the network slice). ·Network Data Analytics Function (NWDAF) (e.g., a function that analyzes network data). Operation, Administration and Maintenance (Management) (OAM) (e.g., functions that provide the means for operation, maintenance and management). ·Policy Control Function (PCF) (e.g., function that controls the quality, policy, etc. of the data transfer path). · Session Management Function (SMF) (e.g., a function that manages a session). ·Trusted Non-3GPP Gateway Function (TNGF) (e.g., a function that connects trusted non-3GPP access networks with 5GC). Trusted WLAN Interworking Function (TWIF) (e.g., for non-5G UEs, connecting trusted non-3GPP access networks with 5GC via a Wireless Local Area Network (LAN)). (Radio) Access Network ((R)AN) (e.g., the function that provides the radio access network). User Equipment (UE) (e.g., user access to network services over the radio interface). Unified Data Management (UDM) (e.g., the ability to store and manage subscriber information, UE authentication information, etc.). Unified Data Repository (UDR) (e.g., the ability to manage authentication / authorization based on subscriber information). User Plane Function (UPF) (e.g., the function that carries packets of user data). Over the Top (OTT) (e.g. content / services / features provided by independent providers, bypassing the carrier network). Analytics Data Repository Function (ADRF) (e.g., a function for storing and managing analytical data in a communications network). ·Data Collection Analytics Function (DCAF) (e.g., a function that collects and analyzes data in a communications network). ·Data Collection Coordination Function (DCCF) (e.g., a function that collects and coordinates data in a communications network).

[0092] It should be understood that these are merely examples and that other NFs are also covered by the present disclosure.

[0093] In this disclosure, the operation of the DSM will be mainly described, but the DSM (the name of the DSM) is merely an example and may be interpreted as any network component / function.

[0094] In this disclosure, a "consumer" may refer to an entity that receives a data set for a particular usage. In this disclosure, a consumer may be, for example, a UE, a RAN node (e.g., a base station), an OAM, a CN NF, an SMO, a non-real-time RIC, a real-time RIC, etc.

[0095] In this disclosure, a "requester" may refer to an entity that requests a DSM to deliver a data set to a consumer. For example, a requester may be a consumer, a UE, a RAN node, an OAM, a CN NF, an SMO, a non-real-time RIC, a real-time RIC, etc.

[0096] "Provider" in this disclosure may refer to an entity that provides data / data samples / data sets to a DSM.

[0097] In this disclosure, a "source" may refer to an entity from which a DSM can collect data.

[0098] In the present disclosure, other users may refer to at least one of other UEs, other UE-side servers, any AF, any NF, and a third party.

[0099] In the present disclosure, the terms "data," "feedback," "signal," and "data set" may be used interchangeably.

[0100] In the present disclosure, the data set may include at least one of the following values: · Dataset ID (e.g., the identifier of the dataset). Features / labels (e.g., representations of data values). Data values ​​(e.g., the value of a data sample). · Data / dataset related information.

[0101] In addition, the feature may be at least one of those described in Supplementary Note 8 below.

[0102] Labels may also be a feature in this disclosure.

[0103] Fig. 4 is a diagram showing an example of a dataset. In the example shown in Fig. 4, a dataset corresponding to dataset ID = 1 and a dataset corresponding to dataset ID = 2 are shown. Each dataset is composed of multiple data samples, and each data sample corresponds to a data sample ID / feature / label.

[0104] <Dataset acquisition> Below we provide an overview of dataset acquisition using DSM.

[0105] The DSM may be triggered to acquire the data set.

[0106] The DSM may acquire a data set.

[0107] The DSM may collect / generate data, which may then create / register a dataset.

[0108] Data collection is detailed in step 1 below.

[0109] Data generation is described in detail in step 2 below.

[0110] Dataset creation / registration is described in detail in step 3 below.

[0111] The DSM may also receive a data set from a provider entity.

[0112] Dataset transfer / delivery is detailed in step 1 below.

[0113] Dataset registration is described in detail in step 3 below.

[0114] The DSM may notify about received / created / registered datasets.

[0115] Dataset identification is described in detail in step 4 below.

[0116] Fig. 5 is a diagram showing an example of data set acquisition. In the example shown in Fig. 5, first, the DSM collects data from the provider (S501). Next, the DSM configures / creates a data set (S502). Furthermore, the DSM identifies the data set to the provider (S503).

[0117] <Dataset Transfer / Distribution> Below, we will provide an overview of dataset transfer / distribution using DSM.

[0118] The DSM may transfer / deliver the dataset to the consumer.

[0119] In the present disclosure, the terms "transfer" and "delivery" may be interpreted interchangeably.

[0120] A DSM may be requested to transfer a dataset by a requestor.

[0121] Requesting a dataset transfer is described in detail in step 5 below.

[0122] The DSM may transfer the dataset to the consumer.

[0123] Dataset transfer / delivery is described in detail in step 6 below.

[0124] Fig. 6 is a diagram showing an example of data set transfer. In the example shown in Fig. 6, first, the DSM receives a request for data set transfer from a requester (S601). Next, the DSM transfers / distributes the data set to a consumer (S602).

[0125] <Step 1> Step 1 involves data collection and data set transfer to the DSM.

[0126] In data collection / dataset transfer, at least one of the following steps 1 to 4 in procedure 1 may be performed.

[0127] Step 1: The DSM may verify the user's consent for the data collection / dataset.

[0128] Step 2: The DSM may receive information regarding data that may be collected (collectible) and / or data sets that may be transferred (transferable).

[0129] For example, in step 2, the source / provider (e.g., UE / base station / CN NF / OAM / AF / DSM) may send information about collectable data / transferable data sets that can be distributed to the DSM.

[0130] Step 3: The DSM may request sources / providers to collect / provide data / datasets to the DSM.

[0131] For example, in step 3, a provider (e.g., UE / base station / CN NF / OAM / AF / DSM / SMO / non real-time RIC / real-time RIC) may receive a request indicating that it will collect / provide data / data sets to the DSM.

[0132] Step 4: The DSM may receive the data / dataset from the provider.

[0133] For example, in step 4, a provider (e.g., UE / base station / CN NF / OAM / AF / DSM / SMO / non real-time RIC / real-time RIC) may provide data / data sets to the DSM.

[0134] Fig. 7 is a diagram showing an example of data collection according to procedure 1. In the example shown in Fig. 7, a case where the provider is the UE is shown.

[0135] In the example shown in Figure 7, first, the DSM requests subscriber information / subscription information from the UDM (S701), and the UDM notifies the DSM of the subscriber information / subscription information (S702) (corresponding to step 1 above). Next, the DSM receives information about collectable data from the UE (S703, corresponding to step 2 above). Furthermore, the DSM requests data from the UE (S704, corresponding to step 3 above) and collects data from the UE (S705, corresponding to step 4 above).

[0136] Fig. 8 is a diagram showing another example of data collection according to procedure 1. In the example shown in Fig. 8, a case is shown in which the provider is a RAN node. The operations performed by the DSM may be the same as those in Fig. 7 above, where the UE is replaced with a RAN node (S801-S805).

[0137] Fig. 9 is a diagram showing another example of data collection according to procedure 1. In the example shown in Fig. 9, the provider is an NF / OAM. The operations performed by the DSM may be the same as those in Fig. 7 above, where the UE is replaced with an NF / OAM (S901-S905).

[0138] <<Step 1-1>> Procedure 1-1 details step 1 in procedure 1 above.

[0139] In step 1, the DSM may contact a particular entity.

[0140] The particular entity may be, for example, an entity (eg, UDM) that manages the UE's subscriber information / subscriptions for the feasibility of data collection / dataset transfer for the particular UE.

[0141] The particular entity may be, for example, an entity that manages the data collection / data set transfer access tokens and / or the data collection / data set transfer services / functions (for the particular UE).

[0142] Step 1-1 ensures proper verification of user consent for data collection / dataset.

[0143] <<Step 1-2>> Procedure 1-2 details step 2 in procedure 1 above.

[0144] The DSM may request entities that may become providers (which may also be called potential providers, e.g., UE / base station / NF / OAM / AF / SMO / non real-time RIC / real-time RIC) to send messages / signaling / information regarding collectable data, transferable data sets, and at least one of data collection / data transfer capabilities.

[0145] The message / signaling / information may include, for example, the requested information. The message / signaling / information may include, for example, information regarding at least one of the following: How many data samples can be collected? · Data-related information for the data that can be collected (Data-related information may be defined as described in Supplementary Note 5 below). Data Collection / Dataset Transfer Capabilities (Data collection / dataset transfer related information available for data collection (Data collection / dataset transfer related information may be specified as described in Supplementary Note 6 below)). · Provider entity-related information (entity-related information may be defined as described in Addendum 7 below).

[0146] Based on the request received, the potential provider may send messages / signaling / information regarding collectable data, transferable data sets, and / or data collection / transfer capabilities.

[0147] The message / signaling / information sent by the potential provider may contain all or a subset of the requested information.

[0148] The message / signaling / information sent by the potential provider may contain [only] information that is different (eg, updated) from the previous message / signaling / information received.

[0149] Fig. 10 is a diagram showing an example of a request for data collection / data set transfer according to procedure 1-2. In the example shown in Fig. 10, the potential provider is the UE.

[0150] 10, the DSM transmits a request for information on transferable data sets to the UE (S1001). Then, the UE transmits a response to the request (information on the transferable data sets) (S1002).

[0151] According to step 1-2, information regarding collectable data / transferable data sets can be sent and received appropriately.

[0152] <<Steps 1-3>> Procedures 1-3 will provide detailed information on step 3 in procedure 1 above.

[0153] The DSM may request that providers provide data to the DSM.

[0154] A provider (e.g., UE / base station / NF / OAM / AF / SMO / non real-time RIC / real-time RIC) may receive a message / signaling / information requesting the DSM to provide data / datasets.

[0155] The message / signaling / information may include information regarding at least one of the following: The requested dataset ID. · What / how many data samples are required? Data / Dataset related information regarding the requested data / dataset (Data / Dataset related information may be specified as described in Supplementary Note 5 below). ·Data collection / dataset transfer capabilities for the required data / datasets (data collection / dataset transfer related information may be specified as described in Supplementary Note 6 below). · Provider entity-related information (entity-related information may be defined as described in Addendum 7 below).

[0156] Providers may not expect / assume to receive any messages / signaling / information requesting data / datasets that have not been reported as collectable / transferable in step 2 of procedure 1 above.

[0157] Fig. 11 is a diagram showing an example of a data / data set request related to steps 1-3. In the example shown in Fig. 11, the DSM sends a request for data collection / data set transfer to the provider (S1101). Next, the provider collects the data / transfers the data set to the DSM (S1102).

[0158] According to steps 1-3, requests regarding data / data sets can be sent and received appropriately.

[0159] <<Steps 1-4>> Procedures 1-4 will detail step 4 in procedure 1 above.

[0160] The DSM may receive data / data sets from a provider.

[0161] A provider (e.g., UE / base station / CN NF / OAM / AF / DSM) may provide data / data sets to the DSM.

[0162] <<<Step 1-4-1>>> A provider may initiate a dataset transfer to a DSM.

[0163] The provider may provide the dataset ID of the dataset being transferred.

[0164] The provider may indicate what / what information of the dataset (e.g., the type of dataset) is to be transferred.

[0165] For example, the provider may provide data / dataset-related information about the data / dataset being transferred (e.g., information indicating which features are being transferred; note that data / dataset-related information may be specified as described in Supplementary Note 5 below).

[0166] For example, the provider may communicate information indicating which / how many data samples are to be transferred (eg, the number of samples or the index of the data sample).

[0167] Providers may also communicate how transfers of datasets (or between datasets) may be performed.

[0168] For example, the provider may notify data collection / dataset transfer related information regarding the data collection / dataset transfer to be performed (the data collection / dataset transfer related information may be defined as described in Supplementary Note 6 below).

[0169] <<<Step 1-4-2>>> The provider may terminate the dataset transfer to the DSM in certain cases.

[0170] Such a particular case may be, for example, when the provider receives a termination instruction.

[0171] The provider may receive the termination instruction from the DSM.

[0172] The termination instruction may include information regarding at least one of the following: The reason why the dataset transfer is being terminated. How many transferred datasets (samples for datasets) will be sent after the end indication is sent / received. How many data set transfer messages / signaling are sent after the end indication is sent / received.

[0173] The particular case may also be when the DSM sends / receives an end instruction.

[0174] For example, the DSM may receive a termination instruction from the provider.

[0175] The termination instruction may include information regarding at least one of the following: The reason why the dataset transfer is being terminated. How many transferred datasets (samples for datasets) will be sent after the end indication is sent / received. How many data set transfer messages / signaling are sent after the end indication is sent / received.

[0176] The particular case may also be when the provider has completed the transfer of multiple (eg, all) data sets.

[0177] For example, this particular case may be when the amount of data samples requested in step 3 above has been transferred.

[0178] For example, the particular case may be when the amount of data samples notified in step 2 above has been transferred.

[0179] For example, the particular case may be when all data samples contained in the transferred data set have been transferred.

[0180] According to steps 1-4, the data / data set transfer can be performed properly.

[0181] According to the above procedure 1, data collection / data set transfer can be performed appropriately.

[0182] <Step 2> Step 2 concerns data generation.

[0183] The DSM may perform data generation.

[0184] In the data generation, at least one of the following steps 1 to 4 in procedure 2 may be performed.

[0185] Step 1: The DSM may receive a data generation request.

[0186] The request may include a method for generating the data (eg, data / data sample / data set).

[0187] The request may include information regarding at least one of the following: The dataset ID that is the basis for generating the data. · Which / how many datasets to generate. Dataset-related information for the dataset to be generated (dataset-related information may be specified as described in Supplementary Note 5 below). · Dataset transfer related information available for dataset transfer (Dataset transfer related information may be defined as described in Supplementary Note 6 below). Entity-related information for the entity requesting the generation of dataset information (Entity-related information, which may be specified as described in Supplementary Note 7 below). · Generation data requirements.

[0188] Step 2: The DSM may review the available stored data samples against the requirements set forth in the request. If the requirements are met, the DSM may use the stored data to create the dataset. Otherwise, it may perform steps 3 / 4 below.

[0189] Step 3: The DSM may start the data collection procedure. The DSM may interrupt the data collection procedure and perform step 4 below.

[0190] The interruption of the data collection procedure may be performed based on, for example, at least one of operator policy regarding the number / rate of collection of data samples from the provider, the estimated time to collect the required samples taking into account deadlines for providing the data set, and a termination signal from the provider.

[0191] Step 4: The DSM may generate data.

[0192] In step 4, the DSM may generate data (e.g., data samples / data sets) based on at least one of the following: · Existing data stored in the DSM (e.g. data samples / datasets). · Statistical channel model. Use of generative adversarial networks (GAN).

[0193] According to the above procedure 2, data can be generated appropriately using DSM.

[0194] <Step 3> Step 3 involves creating / registering a dataset.

[0195] The DSM may also create / register datasets.

[0196] In creating / registering a dataset, at least one of the following steps 1 to 4 in procedure 3 may be performed.

[0197] Step 1: The DSM may receive a request to create / register a dataset.

[0198] The request may include, for example, a method for creating the dataset.

[0199] Step 2: The DSM may create a dataset.

[0200] In step 2, the DSM may create a dataset based on the stored / received / generated data (e.g., data samples / datasets). The DSM may assign a dataset ID and / or data / dataset related information to the dataset.

[0201] In step 2, the DSM may assign a dataset ID to the received dataset.

[0202] Step 3: The DSM may register the dataset.

[0203] In step 3, the UE may store at least one of the dataset ID, the associated information, and the dataset / dataset location in a repository.

[0204] Step 4: The DSM may provide discovery / selection services for the repository. Consumers may use the provided services to query for datasets registered in the DSM.

[0205] By following step 3 above, the dataset can be created / registered appropriately using DSM.

[0206] <Step 4> Step 4 concerns dataset identification.

[0207] The DSM may notify at least one of a dataset ID, a dataset, and data / dataset related information.

[0208] For example, the DSM may notify the entity that requested the creation / registration of the dataset.

[0209] For example, the DSM may provide such notification to the entity that provided the data set.

[0210] According to the above step 4, the data set can be appropriately identified.

[0211] <Step 5> Step 5 concerns requesting a data set transfer.

[0212] A requester may request a data set [transfer].

[0213] In the data set transfer request, at least one of the following steps 1 to 3 in procedure 5 may be executed (see FIG. 6 above).

[0214] Step 1: A DSM may receive a request for transferable data / dataset information.

[0215] For example, in step 1, an entity that can become a requester (which may also be called a potential requester) may request the DSM to send information about data / data sets that can be distributed to consumers.

[0216] Step 2: The DSM may notify the transferable data / dataset information.

[0217] For example, in step 2, the potential requestor may receive information about the data / datasets available for transfer, which may include, for example, a data / dataset ID and / or data / dataset related information.

[0218] Step 3: The DSM may receive a request for transfer of data / dataset from a requestor.

[0219] For example, in step 3, the requester may request the DSM to transfer a dataset to the consumer.

[0220] <<Step 5-1>> Procedure 5-1 details step 1 in procedure 5 above.

[0221] The DSM may receive a request for transferable data set information.

[0222] The UE / RAN node / base station / NF / OAM / AF / SMO / non real-time RIC / real-time RIC may request the DSM to send information regarding at least one of the data sets that can be transferred and how the data sets can be transferred.

[0223] The message / signaling relating to the request may include information regarding at least one of the following: · Transferable dataset ID. · Which / how many data samples can be transferred? · Dataset-related information about the transferable dataset (Dataset-related information may be specified as described in Supplementary Note 5 below). · Dataset transfer related information available for dataset transfer (Dataset transfer related information may be defined as described in Supplementary Note 6 below). Entity-related information about the entity for which the transferable dataset information is requested (the entity-related information may be specified as described in Supplementary Note 7 below).

[0224] After sending / receiving the request, the UE / base station / NF / OAM / AF / SMO / non real-time RIC / real-time RIC may receive a response to the request.

[0225] The response may include information regarding at least one of the following: Acknowledgment (for example, it may be transferable data information. Transferable data information will be described in detail in step 5-2 below). · Reject (e.g., may include reason for rejection).

[0226] Fig. 12 is a diagram showing an example of a request for transferable data / data set information according to procedure 5-1. In the example shown in Fig. 12, first, the UE transmits a request for transferable data set information to the DSM (S1201). Next, the DSM transmits a response signal (e.g., transferable data set information) in response to the request to the UE (S1202).

[0227] According to step 5-1, a request for transferable data / data set information can be made appropriately.

[0228] <<Step 5-2>> Procedure 5-2 provides a detailed explanation of step 2 in procedure 5 above.

[0229] The DSM may notify transferable data set information.

[0230] The UE / RAN node / base station / NF / OAM / AF / SMO / non real-time RIC / real-time RIC may receive information regarding at least one of the data sets available for transfer and how the data sets can be transferred.

[0231] The informational message / signaling may include information regarding at least one of the following: · Transferable dataset ID. · Which / how many data samples can be transferred? · Dataset-related information about the transferable dataset (Dataset-related information may be specified as described in Supplementary Note 5 below). · Dataset transfer related information available for dataset transfer (Dataset transfer related information may be defined as described in Supplementary Note 6 below). Entity-related information about the entity for which the transferable dataset information is requested (the entity-related information may be specified as described in Supplementary Note 7 below).

[0232] The message / signaling relating to the information may, for example, include [only] some / subset of the information requested in step 1 of procedure 5 above.

[0233] The message / signaling relating to the information may, for example, contain [only] information that is different (eg, updated) from when the previous message / signaling was received.

[0234] 13 is a diagram showing an example of notification of transferable data set information according to procedure 5-2. In the example shown in FIG. 13, the DSM transmits transferable data set information (#1 and #2) to the UE (S1301 / S1302).

[0235] In the example shown in FIG. 13, for example, transferable data set information #2 may include [only] information that has been updated from transferable data set information #1.

[0236] According to step 5-2, the transferable data set information can be properly notified.

[0237] <<Step 5-3>> Procedure 5-3 details step 3 in procedure 5 above.

[0238] The DSM may receive a request for transferable data set information.

[0239] A requester (e.g., UE / ARN node / base station / NF / OAM / AF / SMO / non real-time RIC / real-time RIC) may request the DSM to send information regarding at least one of the data sets that can be transferred and how the data sets can be transferred.

[0240] The message / signaling relating to the request may include information regarding at least one of the following: The requested dataset ID. · What / how many data samples are required? · Dataset-related information about the requested dataset (Dataset-related information may be specified as described in Supplementary Note 5 below). · Dataset transfer related information regarding the requested dataset transfer (Dataset transfer related information may be specified as described in Supplementary Note 6 below). Entity-related information about the requester (Entity-related information may be defined as described in Addendum 7 below). The usage of the dataset.

[0241] After the DSM receives the request, the requester may receive a response to the request from the DSM.

[0242] The response may include information regarding at least one of the following: Acknowledgment. · Reject (e.g., may include reason for rejection).

[0243] According to step 5-3, a request for transferable data set information can be made appropriately.

[0244] According to the above procedure 5, a request for data set transfer can be made appropriately.

[0245] <Step 6> Step 6 concerns dataset transfer / distribution.

[0246] The DSM may transfer / deliver the dataset to the consumer.

[0247] In the data set transfer / distribution, at least one of the following steps 1 and 2 in procedure 6 may be performed.

[0248] Step 1: The DSM may initiate a dataset transfer to the consumer.

[0249] For example, in step 1, the consumer may begin receiving a data set from the DSM.

[0250] Step 2: The DSM may terminate the dataset transfer to the consumer.

[0251] For example, in step 2, the consumer may finish receiving the data set from the DSM.

[0252] Fig. 14 is a diagram showing an example of data transfer according to step 6. In the example shown in Fig. 14, the DSM transfers / distributes a data set to the consumer.

[0253] <<Step 6-1>> Procedure 6-1 details step 1 in procedure 6 above.

[0254] The DSM may initiate the data set transfer to the consumer.

[0255] The DSM may indicate what / which information to transfer.

[0256] For example, the DSM may send dataset-related information about the dataset being transferred (which may be defined as described in Supplementary Note 5 below), which may be, for example, information indicating what / which features are being transmitted.

[0257] For example, the DSM may send information indicating which / how many data samples are to be transferred.

[0258] The information may indicate, for example, the number of samples to be notified. For example, if information indicating the number of samples=50 is notified, data samples corresponding to indexes 0 to 49 (or 1 to 50) may be transferred.

[0259] Also, for example, the DSM may signal the index of the data sample to be transferred.

[0260] The DSM may also advise how the data set transfer should be performed.

[0261] For example, the DSM may send data collection / dataset transfer related information regarding the requested data collection / dataset transfer (the data collection / dataset transfer related information may be defined as described in Supplementary Note 6 below).

[0262] According to step 6-1, the data set transfer can be started properly.

[0263] <<Step 6-2>> The DSM may terminate the dataset transfer to the consumer in certain cases.

[0264] The particular case may be, for example, when the DSM receives an instruction to terminate.

[0265] The DSM may receive the termination indication from the consumer / requester.

[0266] The termination instruction may include information regarding at least one of the following: The reason why the dataset transfer is being terminated. How many transferred datasets (samples for datasets) will be sent after the end indication is sent / received. How many data set transfer messages / signaling are sent after the end indication is sent / received.

[0267] The particular case may also be when the DSM sends an end instruction.

[0268] For example, the consumer / requester may receive a termination indication from the DSM.

[0269] The termination instruction may include information regarding at least one of the following: The reason why the dataset transfer is being terminated. How many transferred datasets (samples for datasets) will be sent after the end indication is sent / received. How many data set transfer messages / signaling are sent after the end indication is sent / received.

[0270] The particular case may also be when the provider has completed the transfer of multiple (eg, all) data sets.

[0271] For example, this particular case may be when the requested amount of data samples has been transferred in step 3 of procedure 5 above.

[0272] For example, the particular case may be when the amount of data samples notified in step 1 of procedure 5 / procedure 6 above has been transferred.

[0273] For example, the particular case may be when all data samples contained in the transferred data set have been transferred.

[0274] According to step 6-2, the data set can be transferred properly.

[0275] According to the above step 6, the data set transfer can be performed appropriately.

[0276] First Embodiment The first embodiment relates to a method for solving the above-mentioned issue 1.

[0277] More specifically, in the first embodiment, the reporting of consent by the UE will be described.

[0278] The UE may send a report regarding the user consent (which may simply be referred to as consent or may be referred to as UE consent) (see FIG. 15).

[0279] The UE may report information regarding consent for the data / data sets to be transmitted / received.

[0280] For example, the information regarding the consent may include information indicating whether the UE has consented to forwarding signals / feedback / data reported by the UE to other users (e.g., other UEs / AFs / NFs / third parties) [after specified / configured / instructed data processing].

[0281] For example, the information regarding the consent may include information indicating whether the UE has consent to receive signals / feedback / data reported from other users (e.g., other UEs / AFs / NFs / third parties) [after specified / configured / instructed data processing].

[0282] In the present disclosure, the consent [to forward / receive] may be defined / determined based on at least one of a UE report type, a UE report ID, a UE report setting, and a data processing method.

[0283] For example, the information regarding the consent may include an ID indicating the content of the consent.

[0284] The ID may be, for example, an ID unique to each PLMN / MNO, or may be a global ID.

[0285] For example, the information regarding the consent may include information indicating the scope of the consent.

[0286] The scope of the consent may be limited to, for example, a specific (part of) UE.

[0287] The particular (subset) of UEs may be, for example, UEs from the same vendor / type / chipset vendor.

[0288] The specific (part of) UEs may be, for example, UEs that report the same ID indicating the content of the agreement, or UEs that report IDs indicating the content of the agreement from one list.

[0289] For example, the information regarding the consent may include information indicating the validity period / expiration timing (e.g., expiration date) of the UE consent.

[0290] According to the first embodiment described above, the contents of the report regarding UE consent can be appropriately defined, which can contribute to solving the above-mentioned issue 1.

[0291] <Second embodiment> The second embodiment relates to a method for solving the above issue 1.

[0292] More specifically, in the second embodiment, the assumptions / expectations of the UE regarding consent are described.

[0293] The UE may receive one or more data / signals / data sets.

[0294] At this time, the UE may assume / expect that the data / signals / data sets it sends / receives will be collected (by other users / the UE) within the scope of the reported consent (e.g., using the first embodiment above).

[0295] The UE may assume / expect similar / common characteristics to exist between the data / signals / data sets it receives.

[0296] The similar / common features may be, for example, specific features or UE implementation-dependent features, such as features related to at least one of pre-processing / post-processing methods / algorithms and phase normalization.

[0297] The UE may transmit / report one or more data / signals / data sets.

[0298] In this case, the UE may not assume / expect that the reported data / signal / dataset (or the data / signal / dataset after a particular process) will be received by any entity / device outside the scope of the agreement.

[0299] According to the second embodiment described above, it is possible to appropriately define the assumptions / expectations of the UE regarding UE consent (that is, rules regarding UE consent), which can contribute to solving the above-mentioned issue 1.

[0300] <Third embodiment> The third embodiment relates to a method for solving the above issue 2.

[0301] The UE may report information regarding the index of the data / data set that is collected.

[0302] The UE may perform an action related to receiving the data / data set based on the collected data / data set and / or other users (e.g., other UEs / AFs / NFs / third parties).

[0303] The UE may receive data / signals / data sets associated with the same index as the index of the data / data set being reported.

[0304] The UE may then assume / expect that the data / signals / datasets it receives will contain [only] data / signals / datasets that are processed based on the reported data / signals / datasets.

[0305] Also, at this time, the (original) data / signal / data set reported by the UE may be omitted in the received data / signal / data set.

[0306] The UE may receive data / signals / data sets that are not associated with the same index as the index of the data / data set that it is reporting.

[0307] In this case, the UE may assume / expect that the data / signals / datasets it receives will include both data / signals / datasets collected from other users (e.g., other UEs / AFs / NFs / third parties) and data / signals / datasets processed based on the data / signals / datasets collected from the other users.

[0308] In addition, in the present disclosure, the processed data / signal / data set may refer to data / signal / data set generated by (based on) at least one of a UE feature and a feature group based on a group setting.

[0309] According to the third embodiment described above, it is possible to appropriately define the data / data sets received by the UE and the relationship between the data / data sets collected by the UE and the received data / data sets, thereby contributing to solving the above-mentioned Issue 2.

[0310] <Fourth embodiment> The fourth embodiment relates to a method for solving the above issue 3.

[0311] The UE may assume the NW operation according to this embodiment.

[0312] The NW may have one or more entities that receive data / data sets from the UE / UE side server.

[0313] The one or more entities may be, for example, a DSM.

[0314] The NW / DSM may receive information regarding the UE consent.

[0315] The NW / DSM may check information regarding UE consent for any data / signal / data set reported by the UE / UE side server.

[0316] For example, the information regarding the UE consent may be the information described in the first embodiment above, and may include at least one of information indicating the scope of the consent and information indicating the validity period / expiration timing (e.g., expiration date) of the UE consent.

[0317] If the UE consent is valid, the NW / DSM may process the data / signal / dataset and forward / distribute / send the processed data / signal / dataset to other users (e.g., other UEs / UE-side servers / AFs / NFs / third parties) within the scope of the UE consent.

[0318] The processing may include, for example, at least one of grouping the data, transforming the data, using the data as input to a module / model / algorithm, generating output data, and removing certain information within the data.

[0319] NW / DSM may not transfer / deliver / transmit pre - processed / post - processed data / signals / data sets to other users (e.g., other UEs / UE - side servers / AFs / NFs / third parties) without valid UE consent for at least one of the received data / signals / data sets and the processed data / signals / data sets.

[0320] NW / DSM may be prohibited from transferring / delivering / transmitting pre - processed / post - processed data / signals / data sets to other users (e.g., other UEs / UE - side servers / AFs / NFs / third parties) without valid UE consent for at least one of the received data / signals / data sets and the processed data / signals / data sets.

[0321] According to the above - mentioned fourth embodiment, the NW entity operations related to UE consent can be appropriately defined, which can contribute to the solution of the above - mentioned issue 3.

[0322] <Supplementary Note> <<Notification of Information to UE (Supplementary Note 1)>> In the above - mentioned embodiments, the notification of any information from [a network (NW) (e.g., a base station (BS))] to a UE (or, equivalently, the reception of any information from a BS by a UE) may be performed using physical - layer signaling (e.g., DCI), higher - layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.

[0323] When the above - mentioned notification is performed by MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) that is not defined in the existing standards in the MAC sub - header.

[0324] When the above notification is performed by DCI, the above notification may be performed based on a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used for scrambling Cyclic Redundancy Check (CRC) bits assigned to the DCI, a format of the DCI, and the like.

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

[0326] <<Notification of Information from UE (Supplementary Note 2)>> The notification of any information from the UE to [NW] (in other words, the transmission / reporting of any information from the UE to the BS) in the above-described embodiments may be performed using physical layer signaling (e.g., UCI), upper layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0327] When the above notification is performed by MAC CE, the MAC CE may be identified by including a new LCID not defined in the existing standard in the MAC sub-header.

[0328] When the above notification is performed by UCI, the above notification may be transmitted using PUCCH or PUSCH.

[0329] Also, the notification of any information from the UE in the above-described embodiments may be performed periodically, semi-persistently, or aperiodically.

[0330] <<Regarding Application of Each Embodiment (Supplementary Note 3)>> In a UE / BS, the specific process / operation / control / assumption / information(s) of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: Upper layer parameters indicating the above specific processing / operation / control / assumment / information are set. The specific processing / action / control / assumption / information is determined based on relevant upper layer parameters; The above specific processes / actions / controls / assumptions / information are specified / activated / triggered by MAC CE / DCI / UCI / resources / channels / RS, Reporting or supporting specific UE capabilities indicating (or relating to) the above specific processes / actions / controls / assumptions / information; · The application of the above specific processing / action / control / assumption / information is judged based on specific conditions.

[0331] The particular UE capability may indicate that the particular process / action / control / assumption / information is supported.

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

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

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

[0335] Information on whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: The information is configured by one or more higher layer parameters / RRC IEs. The information is determined by one or more relevant higher layer parameters / RRC IEs. The information is directed by the MAC CE / DCI. The information is based on one or more UE capabilities. The information is described / defined in the specification. The information is based on the conditions described / defined in the specification. The information is determined by a combination of several pieces of information above. For example, the information is determined by higher layer parameters / MAC CE / DCI settings / indications and reported by UE capabilities.

[0336] The above embodiments / options / choices may be combined into one embodiment / option / choice.

[0337] <<Supplementary Note 4>> In the present disclosure, functionality may be a set of parameters (e.g., a set of parameters for CSI prediction / beam prediction / CSI compression) that are supported based on the conditions indicated by the UE capabilities.

[0338] In the present disclosure, the conditions may be information indicated by UE capabilities.

[0339] In the present disclosure, additional conditions may not be indicated by the UE capability information and may be assumed by training.

[0340] <<Supplementary Note 5>> In the present disclosure, the data / dataset related information of a dataset may include at least one of the following: · Model information related to the data / dataset. Deployment information related to the data / dataset. · Scenario information related to the data / dataset. Area / site information related to the data / dataset (e.g., serving cell index / area ID). Vendor information associated with the data / dataset (e.g., information about the vendor collecting the data). Device (e.g. UE / base station) information related to the data / dataset. · PLMN (Public Land Mobile Network) / MNO (Mobile Network Operator) information related to the data / dataset. Feature information related to the data / dataset. · Temporal information associated with the data / dataset (e.g., time window). Frequency information associated with the data / dataset (e.g. band / frequency range). · Data / dataset quality information. · Quantization information associated with the data / dataset. · Number of data samples in the data / dataset. Information indicating how the data / dataset is generated (e.g., based on a statistical channel model or other dataset).

[0341] Regarding model information related to the data / dataset, the dataset may be generated based on a model (e.g., the dataset may be a dataset generated by a generative model / reconstruction model in Type 3 training).

[0342] For model information associated with data / dataset, the dataset may be used to train a model.

[0343] The model information may include information regarding pre-processing, post-processing, quantization method, and quantization resolution.

[0344] The device information associated with the data / dataset may include at least one of the following device-collected data information: Antenna configuration (e.g., number of horizontal / vertical antenna elements / panels, number of ports, antenna spacing, antenna position, panel position, and / or TxRU mapping). Beam settings (e.g. beam width / number of beams / beam direction). TRP information (e.g., TRP altitude and relative positions of multiple TRPs).

[0345] Feature information associated with the data / dataset may indicate features contained in the data / dataset.

[0346] Feature information associated with the data / dataset may refer to a combination of features included in the data / dataset (eg, Channel impulse response (CIR) and associated UE location).

[0347] Regarding quality information of data / dataset, for example, the quality requirement of data may be that a confidence level of X% has been achieved.

[0348] <<Supplementary Note 6>> Data collection / dataset transfer related information in this disclosure may include at least one of the following information: · Periodicity type of data collection / dataset transfer signaling / messages (e.g., periodic / semi-persistent / aperiodic). · Data collection / dataset transfer signaling / message periodicity. · Number of samples in one signal / message in data collection / dataset transfer. Number of signals / messages for data collection / dataset transfer.

[0349] <<Supplementary Note 7>> Entity-related information in this disclosure may include at least one of the following information: The PLMN / MNO to which the entity belongs. The area / location where the entity is located. The access token held by the entity.

[0350] <<Supplementary Note 8>> Features of the present disclosure may be at least one of the following: Area / site associated with the data sample (e.g., serving cell index / area ID). Model information related to the data sample. Deployment information related to the data sample. Scenario information related to the data sample. Vendor information associated with the data sample (e.g., information about the vendor conducting the data collection). Device (e.g. UE / base station) information related to the data sample. The PLMN / MNO associated with the data sample. · Time information associated with the data sample. Frequency information associated with the data sample (e.g., band / frequency range). · Quality information for data samples. Quantization information associated with the data sample. Information indicating how the data samples are generated (e.g., based on a statistical channel model or other data set).

[0351] Regarding the model information associated with the data sample, the data sample may be generated based on a model (e.g., the data sample may be a data sample generated by a generative model / reconstruction model in Type 3 training).

[0352] For model information associated with a data sample, the data sample may be used to train a model.

[0353] The model information may include information regarding pre-processing, post-processing, quantization method, and quantization resolution.

[0354] The device information associated with the data sample may include at least one of the following device-collected data information: Antenna configuration (e.g., number of horizontal / vertical antenna elements / panels, number of ports, antenna spacing, antenna position, panel position, and / or TxRU mapping). Beam settings (e.g. beam width / number of beams / beam direction). TRP information (e.g., TRP altitude and relative positions of multiple TRPs).

[0355] Regarding the quality information of the data sample, for example, achieving X% confidence may be set as a data quality requirement.

[0356] In the present disclosure, the features [for CSI compression] may be at least one of the following: Nominal inputs for generative model / precoding matrix / channel matrix. · Nominal input for the reconstruction model. The nominal / target output of the generative model. · [Nominal / Target] output of reconstruction model / precoding matrix / channel matrix.

[0357] The nominal inputs of the generative model / precoding matrix / channel matrix are, for example, parameters representing the coefficients (amplitude / phase) of the channel matrix / precoding matrix per antenna port / subband / DFT base / TRP / time instance (if the parameters are per X (X can be a natural number), all parameters can be considered as N features).

[0358] The nominal inputs of the generative model / precoding matrix / channel matrix may be, for example, parameters representing the projection vector (DFT-based).

[0359] The [nominal / target] output of the reconstruction model / precoding matrix / channel matrix is, for example, parameters representing the coefficients (amplitude / phase) of the channel matrix / precoding matrix per antenna port / subband / DFT-based / TRP / time instance (if the parameters are per X (X can be a natural number), all parameters can be considered as N features).

[0360] The [nominal / target] output of the reconstruction model / precoding matrix / channel matrix may be, for example, parameters representing the projection vector (DFT-based).

[0361] In this disclosure, features [for temporal / frequency / spatial domain CSI prediction] may be [nominal] inputs of generative models / precoding matrices / channel matrices.

[0362] The nominal inputs of the generative model / precoding matrix / channel matrix are, for example, parameters representing the coefficients (amplitude / phase) of the channel matrix / precoding matrix per antenna port / subband / DFT base / TRP / time instance (if the parameters are per X (X can be a natural number), all parameters can be considered as N features).

[0363] The nominal inputs of the generative model / precoding matrix / channel matrix may be, for example, parameters representing the projection vector (DFT-based).

[0364] The "nominal" inputs of the generative model / precoding matrix / channel matrix may be, for example, parameters representing the time corresponding to the data sample.

[0365] The "nominal" inputs of the generative model / precoding matrix / channel matrix may be, for example, parameters representing the frequencies corresponding to the data samples.

[0366] The nominal inputs of the generative model / precoding matrix / channel matrix may be, for example, parameters representing the antenna ports / angles corresponding to the data samples.

[0367] In this disclosure, features [for temporal / frequency / spatial domain beam prediction] may be [nominal] inputs of generative models / precoding matrices / channel matrices.

[0368] For example, the features [for temporal / frequency / spatial domain beam prediction] may include at least one of the following: [L1 / L3-]RSRP / SINR / CIR for each RS / beam [per time instance] (CIR may be a parameter representing the coefficients (amplitude / phase) per antenna port per time domain sample). A parameter that represents the time corresponding to a data sample. A parameter that represents the frequency corresponding to a data sample. A parameter that represents the angle corresponding to a data sample. Top 1 beam (the single RS / beam index with the highest RSRP / SINR). Top K beams (K RS / beam indices that achieved the largest RSRP / SINR from 1 to K). Probability of the top 1 beam for each set A. -Top K probability for each set A. ·Top K / 1 probability of top K beams in set A.

[0369] The UE may transmit beam information to the network. The beam information may include at least one of the pieces of information described below. The information to be included in the beam information may be notified to the UE by the network, may be specified in a standard, or may be derived from a model used for beam prediction (associated model). Furthermore, the beam information may be derived from at least one of information notified to the UE by the network without being reported by the UE, a value specified in a standard, a model used for beam prediction (associated model), etc.

[0370] The beam information may include information indicating the top-X probability. The top-X probability of a resource among one or more resources may refer to the probability / confidence / confidence interval that the RSRP or SINR corresponding to the resource is equal to or greater than the Xth largest RSRP or SINR among the RSRPs or SINRs corresponding to the one or more resources. This confidence interval may be an arbitrary percentage (e.g., 95%).

[0371] The beam information may include information indicating the top-X' / 1 probability. The top-X' / 1 probability for one or more resources may refer to the probability / confidence / confidence interval that at least one of the RSRPs corresponding to X' resources is the maximum among the RSRPs or SINRs corresponding to the one or more resources. This confidence interval may be an arbitrary percentage (e.g., 95%). Note that, if different top-X' / 1 probabilities are obtained for the same value of X' depending on how the resources are selected, one of these values ​​(e.g., the maximum value) may be determined as the top-X' / 1 probability.

[0372] The information indicating the L1-RSRP, the top X probability, or the top X' / 1 probability may include information (difference information) indicating a difference from another L1-RSRP, the top X probability, or the top X' / 1 probability.

[0373] The information indicating the L1-RSRP, the top X probability, the top X' / 1 probability, or the difference information therefor may be quantized information (quantized information). The quantized information may correspond to information in which the L1-RSRP, the top X probability, the top X' / 1 probability, or the difference therefor is represented by a specific number of bits divided into a specific representable range by a specific quantization resolution (for example, dB step size) (the value indicated by the bit corresponds to one of the steps (divisions)).

[0374] It is preferable that the quantized information of the difference information be expressed with fewer bits than the quantized information of the non-difference information (for example, the quantized resolution is lower or the expressible range is narrower than the quantized information of the non-difference information), but it may be expressed with the same or more bits.

[0375] The information regarding X, X', the specific range, the specific quantization resolution, the specific number, etc. may be notified to the UE by the network, may be specified in the standard, may be derived from the model used for beam prediction (the associated model), or may be determined based on other information within the same reporting instance.

[0376] In this disclosure, the features (for positioning) may be the nominal inputs of the generative model / precoding matrix / channel matrix.

[0377] For example, the positioning features may include at least one of the following: CIR (for example, CIR may be a parameter representing the coefficient (amplitude / phase) per antenna port / per path delay [ / per TRP]). Power delay profile (PDP, for example, PDP may be a parameter representing power intensity per antenna port / per path delay [ / per TRP]). Delay profile (e.g., DP may be a parameter representing power presence per antenna port / per path delay [ / per TRP]). A parameter that represents the time corresponding to a data sample. A parameter that represents the path delay corresponding to a data sample. Line-of-sight (LOS) / non-line-of-sight (NLOS) discrimination (soft / hard values ​​for LOS / NLOS discrimination) [per TRP / per PRS]. Timing of arrival (ToA) [per TRP]. Receive (Rx) - Transmit (Tx) time difference [per TRP]. · Angle of Arrival (AoA) (DL / UL AoA) [per TRP]. · Angle of Departure (AoD) (DL / UL AoA) [per TRP]. Number of wavelengths between TRP and UE. Rx-Tx phase difference between TRP and UE. DL Reference Signal Time Difference (RSTD) / UL Time Difference of Arrival (TDoA) (per path / per TRP). ·RSRP(RSRPs) / RSRPP(Path-specific RSRP, RSRPPs). Likelihood of the above values ​​(e.g., probability of each ToA value per TRP). UE location (e.g., UE location coordinates).

[0378] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. [Appendix 1] A terminal having a transmitting unit that transmits information regarding consent for a dataset to be transmitted or received, and a control unit that assumes that collection of the dataset is performed within the scope of consent based on the information regarding consent. [Appendix 2] 2. The terminal of claim 1, wherein the information regarding consent includes at least one of information indicating whether consent has been obtained to transfer a dataset reported by the terminal to other users, information indicating whether consent has been obtained to receive a dataset reported by other users, information indicating the scope of consent, and information indicating a validity period of consent. [Appendix 3] 3. The terminal of claim 1 or 2, wherein the control unit assumes that collection of the data set does not occur at any entity outside the scope of consent based on information regarding the consent. [Appendix 4] 4. The terminal of claim 1, wherein the transmitter transmits information about an index of a data set to be collected.

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

[0380] 16 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), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

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

[0382] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0383] 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 the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0384] 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 base station 10.

[0385] 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 super cell) may be composed of multiple [virtual] cells (which may be called, for example, sub-cells). A super cell may correspond to a cell whose physical range is fixed, and a sub-cell may correspond to a cell whose physical range varies semi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[0386] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0387] 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 above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.

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

[0389] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (for example, 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.

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

[0391] The core network 30 may include network functions (NFs) 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 an Operation, Administration and Maintenance (Management) (OAM). Note that a single network node may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.

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

[0393] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio 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).

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

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

[0396] 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)), etc. may be used as an uplink channel.

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

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

[0399] 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 an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0400] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search 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 a CORESET associated with a certain search space based on the search space configuration.

[0401] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

[0402] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement 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.

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

[0404] 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, 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 as DL-RS.

[0405] 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 the SS (PSS, SSS) and the PBCH (and 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 reference signals.

[0406] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0407] (base station) 17 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.

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

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

[0410] 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 to be transmitted as signals, control information, sequences, etc., 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.

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

[0412] The transmitting / receiving unit 120 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 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0413] 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 pertains, such as an array antenna.

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

[0415] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

[0417] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

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

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

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

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

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

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

[0424] 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 perform 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 perform higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may perform PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0425] In the present disclosure, the base station 10 may include a single device that implements all of the functions of the RU, DU, and CU, or may include multiple devices that each implement 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.

[0426] The transceiver unit 120 may receive information regarding consent for a dataset to be transmitted or received. The control unit 110 may control transmission for collection of the dataset within the scope of consent based on the information regarding consent.

[0427] (user terminal) 18 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.

[0428] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, 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.

[0429] 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, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0430] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also 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.

[0431] 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 from 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.

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

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

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

[0435] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

[0438] 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 when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

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

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

[0441] The transceiver 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 to acquire user data, etc.

[0442] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, 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.

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

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

[0445] The transceiver 220 may transmit information regarding consent for the data set to be transmitted or received. The control unit 210 may assume that the collection of the data set is performed within the scope of consent based on the information regarding consent.

[0446] The information regarding consent may include at least one of information indicating whether consent has been obtained for the transfer of a dataset reported by the terminal to other users, information indicating whether consent has been obtained for the terminal to receive a dataset reported by other users, information indicating the scope of consent, and information indicating the validity period of consent.

[0447] The control unit 210 may assume that the collection of the data set will not occur for any entity outside the scope of consent based on the consent information.

[0448] The transceiver 220 may transmit information regarding the index of the data set to be collected.

[0449] (Hardware configuration) 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 also be realized by combining the single device or multiple devices with software.

[0450] 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 mentioned above, the implementation method of each is not particularly limited.

[0451] 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. 19 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.

[0452] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read 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.

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

[0454] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as 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.

[0455] 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), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0456] 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 realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0457] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0458] Storage 1003 is a computer-readable recording medium and may be constituted by 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, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

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

[0460] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

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

[0463] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.

[0464] (Variation) Note that terms explained 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.

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

[0466] 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, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

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

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

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

[0470] 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 a subframe and a 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.

[0471] 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. However, the definition of TTI is not limited to this.

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

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

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

[0475] 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 equal to or greater than 1 ms.

[0476] 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 also be determined based on numerology.

[0477] 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. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0478] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0480] A Bandwidth Part (BWP), which may also be referred to as a fractional 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 given BWP and numbered within that BWP.

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

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

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

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

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

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

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

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

[0489] 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 / identifying (or relating to) the value of the any information.

[0490] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, 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.

[0491] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called 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).

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

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

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

[0495] 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), then these wired and / or wireless technologies are included within the definition of transmission media.

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

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

[0498] 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. The spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

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

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

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

[0502] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

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

[0504] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interchangeable. "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 TCI may be interchangeable. The spatial relationship information and spatial relationship may be interchangeable.

[0505] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0506] 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 divided 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 term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

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

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

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

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

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

[0513] 20 is a diagram showing an example of a vehicle according to an embodiment. A 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.

[0514] 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 the user.

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

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

[0517] 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 (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0519] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing 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.

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

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

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

[0523] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices 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)).

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

[0525] 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 uplink channel and downlink channel may be read as sidelink channel.

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

[0527] 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) and a Serving-Gateway (S-GW)), or a combination thereof.

[0528] 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 specific order presented.

[0529] 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 The present invention may be applied to systems that use 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

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

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

[0534] 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 action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

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

[0536] 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 ...," "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ...," "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).

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

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

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

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

[0541] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

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

[0543] 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 the prefix "i-th" (i is any integer) (for example, "highest" may be interchangeable as "i-th highest").

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

[0545] 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 nearly zero (immediately after or immediately before). A time offset may be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after the 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.

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

[0547] 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 sending unit that sends information regarding consent for a data set to be sent or received; A terminal having a control unit that assumes that the collection of the data set is performed within the scope of consent based on information regarding the consent.

2. 2. The terminal according to claim 1, wherein the information regarding consent includes at least one of information indicating whether consent has been obtained to transfer a dataset reported by the terminal to other users, information indicating whether consent has been obtained to receive a dataset reported by the terminal from other users, information indicating the scope of consent, and information indicating a validity period of consent.

3. The terminal of claim 1 , wherein the control unit assumes that collection of the data set will not occur at any entity outside the scope of consent based on the consent information.

4. The terminal according to claim 1 , wherein the transmitter transmits information regarding an index of a collected data set.

5. sending information regarding consent for the dataset to be sent or received; and assuming that the collection of the data set is within the scope of consent based on information relating to the consent.

6. a receiving unit for receiving information regarding consent for a data set to be transmitted or received; A base station having a control unit that controls transmission for collection of the data set within the scope of the agreement based on information regarding the agreement.

Images