Network component and wireless communication method

Abstract

A network component according to one aspect disclosed herein comprises: a transmission unit that transmits a request related to at least one of collectable data or a transferable data set; and a control unit that controls the storage of the data and the data set transmitted on the basis of the request. According to one aspect disclosed herein, it is possible to achieve appropriate overhead reduction / channel estimation / resource utilization.

Description

Network element and wireless communication method

[0001] The present disclosure relates to network components and wireless communication methods in next generation mobile communication systems.

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

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

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

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

[0006] 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 of the objects of the present disclosure is to provide a network component and a wireless communication method that can achieve suitable overhead reduction / channel estimation / resource utilization.

[0008] A network element according to one aspect of the present disclosure includes a transmitter that transmits a request for collectable data and / or a transferable data set, and a controller that controls storage of the data and data set transmitted based on the request.

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

[0010] FIG. 1 is a diagram illustrating an example of a framework for managing AI models. FIG. 2 is a diagram illustrating an example of specifying an AI model. FIG. 3 is a diagram illustrating an example of an ORAN architecture. FIG. 4 is a diagram illustrating an example of a dataset. FIG. 5 is a diagram illustrating an example of dataset acquisition. FIG. 6 is a diagram illustrating an example of dataset transfer. FIG. 7 is a diagram illustrating an example of data collection according to the first embodiment. FIG. 8 is a diagram illustrating another example of data collection according to the first embodiment. FIG. 9 is a diagram illustrating another example of data collection according to the first embodiment. FIG. 10 is a diagram illustrating an example of a request for data collection / dataset transfer according to embodiment 1-2. FIG. 11 is a diagram illustrating an example of a request for data / dataset information according to embodiment 1-3. FIG. 12 is a diagram illustrating an example of a request for transferable data / dataset information according to embodiment 5-1. FIG. 13 is a diagram illustrating an example of notification of transferable dataset information according to embodiment 5-2. FIG. 14 is a diagram illustrating an example of data transfer according to embodiment 6. FIG. 15 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 16 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 17 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. Fig. 18 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. Fig. 19 is a diagram illustrating an example of a vehicle according to an embodiment.

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

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

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

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

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

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

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

[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] FIG. 1 is a diagram illustrating an example of a framework for managing AI models. In this example, each stage related to an AI model is shown as a block. This example is also referred to as AI model life cycle management (LCM).

[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 organization (e.g., determining which data to transfer for model training / model inference), data transfer (e.g., transferring data to an entity (e.g., UE, gNB) that performs model training / model inference), etc.

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

[0031] It should be noted that AI model training may refer to a process for training an AI model in a data-driven manner and obtaining a trained AI model for inference.

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

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

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

[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). In the former case, interoperability, large-capacity storage, operator manageability, and model flexibility (feature engineering, etc.) are advantageous. In the latter case, the latency of model updates and the need for data exchange for model deployment are advantageous. Inference of the above model may be performed in, for example, a gNB.

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

[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 disabling an AI model for a specific function, and model switching may mean deactivating a currently active AI model for a specific function and activating a different AI model.

[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, a UE and a NW (e.g., a base station (BS)) can recognize models #1 and #2 (although they do not need to fully understand the details of the models). The UE may report, for example, the capabilities of model #1 and model #2 to the NW, and the NW may instruct the UE on the AI ​​model to use.

[0050] (Open RAN (ORAN)) The ORAN architecture will be described below with reference to FIG.

[0051] In 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, in order to realize network operation utilizing the AI / ML model, a RIC (RAN Intelligent Controller) may be defined as a logical node that automates and optimizes the parameter design / configuration / operation of base stations.

[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 called 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 a functional unit that provides OAM services within the SMO and 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 a 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 (for example, Rel. 19 and later), use cases that require datasets when utilizing AI / ML models are expected.

[0061] Possible use cases include model training, model validation, model inference, and performance monitoring (performance verification 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] However, there has been insufficient consideration of how to manage data, including data collection, data set creation, transfer, and delivery.

[0064] If this consideration is insufficient, it may not be possible to properly utilize AI / ML models in future wireless communication systems, which could hinder improvements in communication throughput.

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

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

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

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

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

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

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

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

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

[0074] (Wireless Communication Method) The following describes terms / phrases used in this disclosure.

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

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

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

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

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

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

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

[0082] A DSM may include at least one of the following functions: - dataset manage function (DSMF) (e.g., a function for managing dataset identification / dataset distribution / data collection); - dataset storage function (DSSF) (e.g., a function for storing datasets / data); - dataset creating function (DSCF) (e.g., a function for creating a dataset based on data); - dataset registration function (DSRF) (e.g., a function for registering a dataset in the DSM (assigning a dataset ID to a dataset)); - dataset discovery function (DSDF) (e.g., a function for discovering a specific dataset in the DSM); - dataset generation function (DSGF) (e.g., a function for generating data / datasets based on samples / statistical models).

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

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

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

[0086] In the present disclosure, the NF may include, for example, at least one of the following: Application Function (AF) (e.g., a function that realizes an application server outside the 5G Core Network (5GC)); Access and Mobility management Function (AMF) (e.g., a function that manages UE registration, location, etc.); Data Network (DN) (e.g., a function that realizes a data network outside 5GC); Location Management Function (LMF) (e.g., a communication control function related to location-based services); Non-3GPP Inter-Working Function (N3IWF) (e.g., a function that connects 5GC with an untrusted non-3GPP access network); Network Exposure Function (NEF) (e.g., a function that provides an application interface for 5GC NF services to the outside); Network Slice Selection Function (NSSF) (e.g., a function that selects a network slice); Network Data Analytics Function (NWDAF) (e.g., a function that analyzes network data). Operation, Administration and Maintenance (Management) (OAM) (e.g., a function that provides means for operation, maintenance and management). Policy Control Function (PCF) (e.g., a function that controls the quality, policy, etc. of data transfer paths). Session Management Function (SMF) (e.g., a function that manages sessions). 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., a function that connects a trusted non-3GPP access network with 5GC for a non-5G-capable UE via a Wireless Local Area Network (LAN)). - (Radio) Access Network ((R)AN) (e.g., a function that provides a radio access network). - User Equipment (UE) (e.g., a function that provides user access to network services via the radio interface). - Unified Data Management (UDM) (e.g., a function that stores / manages subscriber information, UE authentication information, etc.). - Unified Data Repository (UDR) (e.g., a function that manages authentication / authorization based on subscriber information). - User Plane Function (UPF) (e.g., a function that transmits user data packets). - Over The Top (OTT) (e.g., content / services / functions provided by an independent provider bypassing the carrier's network). - Analytics Data Repository Function (ADRF) (e.g., a function that stores / manages analytical data in the communications network). Data Collection Analytics Function (DCAF) (e.g., a function that collects / analyzes data in a communications network) Data Collection Coordination Function (DCCF) (e.g., a function that collects / coordinates data in a communications network).

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

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

[0089] A "consumer" in this disclosure 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.

[0090] In this disclosure, a "requestor" may refer to an entity that requests a DSM to deliver a data set to a consumer. For example, a requestor 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.

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

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

[0093] In the present disclosure, the terms "data" and "dataset" may be read interchangeably.

[0094] In the present disclosure, a dataset may include at least one of the following values: - Dataset ID (e.g., an identifier for the dataset); - Feature / Label (e.g., a representation of a data value); - Data value (e.g., the value of a data sample); - Data / Dataset related information.

[0095] The feature may be at least one of those described in Supplementary Note 8 below.

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

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

[0098] <Dataset Acquisition> The following provides an overview of dataset acquisition using a DSM.

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

[0100] The DSM may acquire the data set.

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

[0102] Data collection will be described in detail in the first embodiment (step 1) below.

[0103] Data generation will be described in detail in the second embodiment (procedure 2) below.

[0104] The creation and registration of the data set will be described in detail in the third embodiment (procedure 3) below.

[0105] The DSM may also receive data sets from a provider entity.

[0106] Data set transfer / distribution will be described in detail in the first embodiment (procedure 1) below.

[0107] The data set registration will be described in detail in the third embodiment (step 3) below.

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

[0109] Data set identification will be described in detail in the fourth embodiment (step 4) below.

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

[0111] <Data Set Transfer / Distribution> The following provides an overview of data set transfer / distribution using DSM.

[0112] The DSM may transfer / deliver the data set to the consumer.

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

[0114] The DSM may be requested to transfer a data set by a requester.

[0115] The request for data set transfer will be described in detail in the fifth embodiment (procedure 5) below.

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

[0117] Data set transfer / distribution will be described in detail in the sixth embodiment (step 6) below.

[0118] Fig. 6 shows 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).

[0119] <First Embodiment (Procedure 1)> The first embodiment (Procedure 1) relates to data collection and data set transfer to the DSM.

[0120] In the data collection / dataset transfer, at least one of the following steps 1 to 4 in the first embodiment may be executed.

[0121] Step 1: The DSM may verify user consent for data collection / dataset.

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

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

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

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

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

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

[0128] Fig. 7 is a diagram illustrating an example of data collection according to the first embodiment. In the example illustrated in Fig. 7, a case where the provider is a UE is illustrated.

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

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

[0131] 9 is a diagram showing another example of data collection according to the first embodiment. 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, where the UE is replaced with the NF / OAM (S901-S905).

[0132] <<Embodiment 1-1>> In embodiment 1-1, step 1 in the first embodiment will be described in detail.

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

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

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

[0136] According to embodiment 1-1, user consent for data collection / data set can be properly confirmed.

[0137] <<Embodiment 1-2>> In embodiment 1-2, step 2 in the first embodiment will be described in detail.

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

[0139] The message / signaling / information may include, for example, the requested information. The message / signaling / information may include, for example, information on at least one of the following: - how many data samples can be collected; - data related information of the collectable data (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 defined as described in Supplementary Note 6 below)); - entity related information of the provider (entity related information may be defined as described in Supplementary Note 7 below).

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

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

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

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

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

[0145] According to the first and second embodiments, information relating to collectable data / transferable data sets can be appropriately transmitted and received.

[0146] <<Embodiment 1-3>> In embodiment 1-3, step 3 in the first embodiment will be described in detail.

[0147] The DSM may request that the provider provide data to the DSM.

[0148] 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 / dataset.

[0149] The message / signaling / information may include information regarding at least one of the following: - The requested dataset ID; - Which / how many data samples are requested; - Data / dataset related information regarding the requested data / dataset (Data / dataset related information may be defined as described in Supplementary Note 5 below); - Data collection / dataset transfer capabilities regarding the requested data / dataset (Data collection / dataset transfer related information may be defined as described in Supplementary Note 6 below); - Provider entity related information (Entity related information may be defined as described in Supplementary Note 7 below).

[0150] The provider may not expect / assume to receive any messages / signaling / information requesting data / datasets that were not reported as collectable / transferable in step 2 of the first embodiment above.

[0151] 11 is a diagram showing an example of a data / data set request according to embodiments 1 to 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).

[0152] According to the first to third embodiments, requests regarding data / data sets can be sent and received appropriately.

[0153] <<Embodiment 1-4>> In embodiment 1-4, step 4 in the first embodiment will be described in detail.

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

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

[0156] <<<Embodiment 1-4-1>>> A provider may initiate a data set transfer to a DSM.

[0157] The provider may provide the dataset ID of the dataset to be transferred.

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

[0159] 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 defined as described in Supplementary Note 5 below).

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

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

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

[0163] <<<Embodiment 1-4-2>>> A provider may terminate a data set transfer to a DSM in certain cases.

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

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

[0166] The termination indication may include information about at least one of the following: the reason why the dataset transfer is terminated, how many transferred datasets (samples for the dataset) will be sent after the termination indication is sent / received, how many messages / signaling for the dataset transfer will be sent after the termination indication is sent / received.

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

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

[0169] The termination indication may include information about at least one of the following: the reason why the dataset transfer is terminated, how many transferred datasets (samples for the dataset) will be sent after the termination indication is sent / received, how many messages / signaling for the dataset transfer will be sent after the termination indication is sent / received.

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

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

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

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

[0174] According to the first to fourth embodiments, data / data sets can be transferred appropriately.

[0175] According to the first embodiment, data collection and data set transfer can be performed appropriately.

[0176] <Second Embodiment (Procedure 2)> The second embodiment (Procedure 2) relates to data generation.

[0177] The DSM may perform data generation.

[0178] In the data generation, at least one of the following steps 1 to 4 in the second embodiment may be executed.

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

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

[0181] The request may include information on at least one of the following: - Dataset ID based on which data is generated; - Which / how many datasets to generate; - Dataset-related information of the dataset to generate (Dataset-related information may be specified as described in Supplementary 5 below); - Dataset transfer-related information available for dataset transfer (Dataset transfer-related information may be specified as described in Supplementary 6 below); - Entity-related information of the entity requesting generation of dataset information (Entity-related information, which may be specified as described in Supplementary 7 below); - Requirements for the generated data.

[0182] Step 2: The DSM may check 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.

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

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

[0185] Step 4: The DSM may generate the data.

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

[0187] According to the second embodiment described above, data can be generated appropriately using the DSM.

[0188] <Third Embodiment (Procedure 3)> The third embodiment (procedure 3) relates to the creation / registration of a dataset.

[0189] The DSM may create / register the dataset.

[0190] In creating / registering a dataset, at least one of the following steps 1 to 4 in the third embodiment may be executed.

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

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

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

[0194] In step 2, the DSM may create a dataset based on 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.

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

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

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

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

[0199] According to the third embodiment described above, a data set can be created / registered appropriately using a DSM.

[0200] <Fourth Embodiment (Procedure 4)> The fourth embodiment (Procedure 4) relates to data set identification.

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

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

[0203] For example, the DSM may notify the entity that provided the data set.

[0204] According to the fourth embodiment described above, data sets can be appropriately identified.

[0205] Fifth Embodiment (Procedure 5) The fifth embodiment (procedure 5) relates to a request for data set transfer.

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

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

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

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

[0210] Step 2: The DSM may notify the transferable data / data set information.

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

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

[0213] For example, in step 3, the requester may request the DSM to transfer a data set to the consumer.

[0214] <<Embodiment 5-1>> In embodiment 5-1, step 1 in the fifth embodiment will be described in detail.

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

[0216] 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 transferable data sets and how the data sets can be transferred.

[0217] The message / signaling related to the request may include information on at least one of the following: - Transferable dataset IDs; - Which / how many data samples are available for transfer; - Dataset related information about the transferable datasets (Dataset related information may be defined 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 transferable dataset information is requested (Entity related information may be defined as described in Supplementary Note 7 below).

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

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

[0220] 12 is a diagram showing an example of a request for transferable data / data set information according to embodiment 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) to the UE in response to the request (S1202).

[0221] According to the embodiment 5-1, it is possible to appropriately request information on transferable data / data set.

[0222] <<Embodiment 5-2>> In embodiment 5-2, step 2 in the fifth embodiment will be described in detail.

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

[0224] 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 that can be transferred and how the data sets can be transferred.

[0225] The informational message / signaling may include information on at least one of the following: - Transferable dataset IDs; - Which / how many data samples are transferable; - Dataset related information about the transferable datasets (Dataset related information may be defined 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 transferable dataset information is requested (Entity related information may be defined as described in Supplementary Note 7 below).

[0226] The informational message / signaling may for example include [only] some / subset of the information requested in step 1 of the fifth embodiment above.

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

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

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

[0230] According to the embodiment 5-2, it is possible to appropriately notify the transferable data set information.

[0231] <<Embodiment 5-3>> In embodiment 5-3, step 3 in the fifth embodiment will be described in detail.

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

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

[0234] The message / signaling related to the request may include information about at least one of the following: - The requested dataset ID; - Which / how many data samples are requested; - Dataset related information about the requested dataset (Dataset related information may be defined as described in Supplementary Note 5 below); - Dataset transfer related information about the requested dataset transfer (Dataset transfer related information may be defined as described in Supplementary Note 6 below); - Entity related information about the requester (Entity related information may be defined as described in Supplementary Note 7 below); - Usage of the dataset.

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

[0236] The response may include information regarding at least one of the following: Acknowledgment. Reject (which may include, for example, the reason for the rejection).

[0237] According to the embodiment 5-3, it is possible to appropriately request transferable data set information.

[0238] According to the fifth embodiment, a request for data set transfer can be made appropriately.

[0239] <Sixth Embodiment (Procedure 6)> The sixth embodiment (Procedure 6) relates to data set transfer / distribution.

[0240] The DSM may transfer / deliver the data set to the consumer.

[0241] In the data set transfer / distribution, at least one of the following steps 1 and 2 in the sixth embodiment may be executed.

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

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

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

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

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

[0247] <<Embodiment 6-1>> In embodiment 6-1, step 1 in the sixth embodiment will be described in detail.

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

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

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

[0251] For example, the DSM may transmit information indicating which / how many data samples are being transferred.

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

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

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

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

[0256] According to the embodiment 6-1, the data set transfer can be started appropriately.

[0257] <<Embodiment 6-2>> The DSM may terminate the data set transfer to the consumer in certain cases.

[0258] The particular case may be, for example, when the DSM receives an end instruction.

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

[0260] The termination indication may include information about at least one of the following: the reason why the dataset transfer is terminated, how many transferred datasets (samples for the dataset) will be sent after the termination indication is sent / received, how many messages / signaling for the dataset transfer will be sent after the termination indication is sent / received.

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

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

[0263] The termination indication may include information about at least one of the following: the reason why the dataset transfer is terminated, how many transferred datasets (samples for the dataset) will be sent after the termination indication is sent / received, how many messages / signaling for the dataset transfer will be sent after the termination indication is sent / received.

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

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

[0266] For example, the particular case may be when the amount of data samples notified in step 1 of the fifth and sixth embodiments above has been transferred.

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

[0268] According to embodiment 6-2, the data set can be transferred appropriately.

[0269] According to the sixth embodiment described above, data set transfer can be performed appropriately.

[0270] <Supplementary Notes> <<Notification of Information to UE (Supplementary Note 1)>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0284] In the present disclosure, the condition may be information indicated by UE capabilities.

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

[0286] <<Supplementary Note 5>> In the present disclosure, the data / dataset related information for a certain data set 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 related to the data / dataset (e.g., information about the vendor performing data collection). - Device (e.g., UE / base station) information related to the data / dataset. - Public Land Mobile Network (PLMN) / Mobile Network Operator (MNO) information related to the data / dataset. - Feature information related to the data / dataset. - Time information related to the data / dataset (e.g., time window). - Frequency information related to the data / dataset (e.g., band / frequency range). - Quality information of the data / dataset. - Quantization information related to the data / dataset. - Number of data samples in the data / dataset. - Information indicating how the data / dataset is generated (e.g., whether based on a statistical channel model or another dataset).

[0287] Regarding model information related to 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).

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

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

[0290] The device information associated with the data / dataset may include information of at least one of the following device collected data: Antenna settings (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 position of multi-TRP).

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

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

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

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

[0295] <<Supplementary Note 7>> Entity-related information in the present disclosure may include at least one of the following information: PLMN / MNO to which the entity belongs, Area / location in which the entity is located, Access tokens held by the entity.

[0296] <<Supplementary Note 8>> A feature 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 associated with the data sample; - Deployment information associated with the data sample; - Scenario information associated with the data sample; - Vendor information associated with the data sample (e.g., information about the vendor performing the data collection); - Device (e.g., UE / base station) information associated with the data sample; - 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 of the data sample; - Quantization information associated with the data sample; - Information indicating how the data sample is generated (e.g., whether based on a statistical channel model or another data set).

[0297] For model information associated with a 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).

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

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

[0300] The device information associated with the data sample may include information of at least one of the following device collected data: Antenna settings (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 position of multi-TRP).

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

[0302] In the present disclosure, the feature (for CSI compression) may be at least one of the following: - Nominal input of the generative model / precoding matrix / channel matrix. - Nominal input of the reconstruction model. - Nominal / target output of the generative model. - Nominal / target output of the reconstruction model / precoding matrix / channel matrix.

[0303] 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 for each antenna port / subband / DFT base / TRP / time instance (if the parameters are for each X (X may be a natural number), all parameters may be considered as N features).

[0304] The [nominal] inputs of the Generative Model / Precoding Matrix / Channel Matrix may be, for example, parameters representing the projection vector (DFT-based).

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

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

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

[0308] 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 for each antenna port / subband / DFT base / TRP / time instance (if the parameters are for each X (X may be a natural number), all parameters may be considered as N features).

[0309] The [nominal] inputs of the Generative Model / Precoding Matrix / Channel Matrix may be, for example, parameters representing the projection vector (DFT-based).

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

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

[0312] The nominal inputs of the generative model / precoding matrix / channel matrix may be, for example, parameters representing the antenna port / angle corresponding to the data sample.

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

[0314] For example, the features [for beam prediction in the temporal / frequency / spatial domain] 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 coefficient (amplitude / phase) per antenna port per time domain sample). - A parameter representing the time corresponding to the data sample. - A parameter representing the frequency corresponding to the data sample. - A parameter representing the angle corresponding to the data sample. - Top 1 beam (the one RS / beam index with the largest RSRP / SINR). - Top K beams (K RS / beam indices that achieve the largest RSRP / SINR from 1 to K). - Probability of the top 1 beam for each set A. - Top K probabilities for each set A. - Top K / 1 probabilities of the top K beams in set A.

[0315] 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 from the network without being reported by the UE, a value specified in a standard, a model used for beam prediction (associated model), etc.

[0316] The beam information may include information indicating a top-X probability. The top-X probability of a resource among one or more resources may refer to a 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%).

[0317] The beam information may include information indicating a 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 a confidence interval of any percentage (e.g., 95%). Note that, when 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.

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

[0319] The information indicating the L1-RSRP, the top X probability, the top X' / 1 probability, or the difference information therefor may be quantized information (quantization information). The quantization 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 any step (division)).

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

[0321] The information regarding the above X, X', specific range, specific quantization resolution, 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 (associated model), or may be determined based on other information within the same reporting instance.

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

[0323] For example, the features [for positioning] may include at least one of the following: CIR (e.g., CIR may be a parameter representing a coefficient (amplitude / phase) per antenna port / per path delay [per TRP]); Power delay profile (PDP, e.g., PDP may be a parameter representing a power intensity per antenna port / per path delay [per TRP]); Delay profile (DP, e.g., DP may be a parameter representing a power presence per antenna port / per path delay [per TRP]); A parameter representing a time corresponding to a data sample; A parameter representing a path delay corresponding to a data sample; Line-of-sight (LOS) / non-line-of-site (NLOS) discrimination [per TRP / per PRS] (soft / hard value of LOS / NLOS discrimination); 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).

[0324] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1-1] A network element having a transmitting unit that transmits a request for at least one of collectable data and a transferable dataset, and a control unit that controls storage of the data and the dataset transmitted based on the request. [Supplementary Note 1-2] The network element according to Supplementary Note 1-1, wherein the control unit confirms user consent for at least one of data collection and dataset transmission. [Supplementary Note 1-3] The network element according to Supplementary Note 1-1 or Supplementary Note 1-2, wherein the transmitting unit transmits the request based on information related to at least one of the collectable data and the transferable dataset. [Supplementary Note 1-4] The network element according to any of Supplements 1-1 to 1-3, wherein transmission of at least one of the data and the dataset is initiated based on a notification from an entity transmitting at least one of the data and the dataset. [Supplementary Note 1-5] The network element according to any of Supplements 1-1 to 1-4, wherein transmission of at least one of the data and the dataset is terminated in a specific case. [Supplementary Note 2-1] A network element having a receiving unit that receives a request for data generation, and a control unit that determines at least one of data generation and data collection based on the request. [Supplementary Note 2-2] The network element according to Supplementary Note 2-1, wherein the control unit determines to perform the data collection if the stored data does not satisfy requirements based on the request. [Supplementary Note 2-3] The network element according to Supplementary Note 2-1 or Supplementary Note 2-2, wherein the control unit creates a dataset based on the data to be generated. [Supplementary Note 2-4] The network element according to any of Supplements 2-1 to 2-3, wherein the control unit registers a dataset created based on the data to be generated. [Supplementary Note 2-5] The network element according to any of Supplements 2-1 to 2-4, wherein the control unit identifies a dataset created based on the data to be generated. [Supplementary Note 3-1] A network element having a receiving unit that receives a request for information related to a dataset, and a control unit that controls transmission of information related to a transferable dataset based on the request.[Supplementary Note 3-2] The network element according to Supplementary Note 3-1, wherein the receiving unit receives a request for dataset transfer that is transmitted based on information about the transferable dataset. [Supplementary Note 3-3] The network element according to Supplementary Note 3-1 or Supplementary Note 3-2, wherein the control unit controls transmission of a response to the request for dataset transfer that is transmitted based on information about the transferable dataset. [Supplementary Note 3-4] The network element according to any of Supplements 3-1 to 3-3, wherein the information about the transferable dataset is a response to a request for information about the dataset. [Supplementary Note 4-1] A network element having a receiving unit that receives a request for dataset transfer, and a control unit that controls start and end of dataset transfer based on the request. [Supplementary Note 4-2] The network element according to Supplementary Note 4-1, wherein the control unit controls start of dataset transfer using at least one of information indicating which dataset is to be transferred and information indicating how the dataset is to be transferred. [Supplementary Note 4-3] The network element according to Supplementary Note 4-1 or Supplementary Note 4-2, wherein the control unit controls end of dataset transfer based on reception of an instruction to end dataset transfer. [Supplementary Note 4-4] The network element according to any one of Supplementary Note 4-1 to Supplementary Note 4-3, wherein the control unit controls the end of the data set transfer based on transmission of an instruction to end the data set transfer. [Supplementary Note 4-5] The network element according to any one of Supplementary Note 4-1 to Supplementary Note 4-4, wherein the control unit controls the end of the data set transfer based on completion of the data set transfer.

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

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

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

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

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

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

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

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

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

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

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

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

[0337] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

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

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

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

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

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

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

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

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

[0347] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

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

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

[0351] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0372] The transceiver 120 may transmit a request for collectable data and / or transferable data sets, and the controller 110 may control the storage of the data and data sets transmitted based on the request (first embodiment).

[0373] The control unit 110 may confirm user consent for data collection and / or data set transfer (first embodiment).

[0374] The transceiver unit 120 may transmit the request based on information about at least one of collectable data and transferable data sets (first embodiment).

[0375] The transmission of the data and / or the data set may be initiated based on notification of an entity transmitting the data and / or the data set (first embodiment).

[0376] The transmission of the data and / or the data set may be terminated in certain cases (first embodiment).

[0377] The transmitting / receiving unit 120 may receive a request for data generation, and the control unit 110 may determine at least one of data generation and data collection based on the request (second embodiment).

[0378] The control unit 110 may determine to collect the data if the stored data does not satisfy the requirements based on the request (second embodiment).

[0379] The control unit 110 may create a data set based on the generated data (third embodiment).

[0380] The control unit 110 may also register a data set created based on the generated data (third embodiment).

[0381] The control unit 110 may identify a data set to be created based on the generated data (fourth embodiment).

[0382] The transceiver 120 may receive a request for information about a data set, and the controller 110 may control the transmission of information about a transferable data set based on the request (fifth embodiment).

[0383] The transmitting / receiving unit 120 may receive a request for data set transfer that is transmitted based on the information about the data sets that can be transferred (fifth embodiment).

[0384] The control unit 110 may control the transmission of a response to a request for data set transfer, which is transmitted based on the information on the data sets that can be transferred (fifth embodiment).

[0385] The information about the transferable dataset may be a response to a request for information about the dataset (fifth embodiment).

[0386] The transmitting / receiving unit 120 may receive a request for data set transfer, and the control unit 110 may control the start and end of data set transfer based on the request (sixth embodiment).

[0387] The control unit 110 may control the start of the dataset transfer using at least one of information indicating which dataset is to be transferred and information indicating how the dataset is to be transferred (sixth embodiment).

[0388] The control unit 110 may control the end of the data set transfer based on the reception of an instruction to end the data set transfer (sixth embodiment).

[0389] The control unit 110 may control the end of the data set transfer based on the transmission of an instruction to end the data set transfer (sixth embodiment).

[0390] The control unit 110 may control the end of the data set transfer based on the completion of the data set transfer (sixth embodiment).

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

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

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

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

[0395] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

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

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

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

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

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

[0402] 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, or if not, it may not be necessary to perform DFT processing as the transmission processing.

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

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

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

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

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

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

[0409] The transceiver 220 may transmit a request for collectable data and / or transferable data sets, and the controller 210 may control the storage of the data and data sets transmitted based on the request (first embodiment).

[0410] The control unit 210 may confirm user consent for data collection and / or data set transfer (first embodiment).

[0411] The transceiver unit 220 may transmit the request based on information regarding at least one of collectable data and transferable data set (first embodiment).

[0412] The transmission of the data and / or the data set may be initiated based on notification of an entity transmitting the data and / or the data set (first embodiment).

[0413] The transmission of the data and / or the data set may be terminated in certain cases (first embodiment).

[0414] The transmitting / receiving unit 220 may receive a request for data generation, and the control unit 210 may determine at least one of data generation and data collection based on the request (second embodiment).

[0415] The control unit 210 may determine to collect the data if the stored data does not satisfy the requirements based on the request (second embodiment).

[0416] The control unit 210 may create a data set based on the generated data (third embodiment).

[0417] The control unit 210 may also register a data set created based on the generated data (third embodiment).

[0418] The control unit 210 may identify a data set to be created based on the generated data (fourth embodiment).

[0419] The transceiver 220 may receive a request for information about a data set. The controller 210 may control the transmission of information about a transferable data set based on the request (fifth embodiment).

[0420] The transmitting / receiving unit 220 may receive a request for data set transfer that is transmitted based on the information about the data sets that can be transferred (fifth embodiment).

[0421] The control unit 210 may control the transmission of a response to a request for data set transfer, which is transmitted based on the information on the data sets that can be transferred (fifth embodiment).

[0422] The information about the transferable dataset may be a response to a request for information about the dataset (fifth embodiment).

[0423] The transceiver 220 may receive a request for data set transfer, and the controller 210 may control the start and end of data set transfer based on the request (sixth embodiment).

[0424] The control unit 210 may control the start of the dataset transfer using at least one of information indicating which dataset is to be transferred and information indicating how the dataset is to be transferred (sixth embodiment).

[0425] The control unit 210 may control the end of the data set transfer based on the reception of an instruction to end the data set transfer (sixth embodiment).

[0426] The control unit 210 may control the end of the data set transfer based on the transmission of an instruction to end the data set transfer (sixth embodiment).

[0427] The control unit 210 may control the end of the data set transfer based on the completion of the data set transfer (sixth embodiment).

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

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

[0430] 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. 18 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.

[0431] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

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

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

[0434] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0435] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

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

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

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

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

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

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

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

[0443] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

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

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

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

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

[0449] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

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

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

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

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

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

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

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

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

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

[0459] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0476] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0506] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

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

[0508] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0526] 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 network element having: a transmitter that transmits requests for collectable data and / or transferable data sets; and a controller that controls storage of the data and data sets transmitted based on the requests.

2. The network element of claim 1, wherein the controller verifies user consent for at least one of data collection and data set transfer.

3. The network element of claim 1, wherein the sender sends the request based on information regarding at least one of collectable data and transferable data sets.

4. The network element of claim 1, wherein transmission of said data and / or said data set is initiated upon notification of an entity transmitting said data and / or said data set.

5. The network element of claim 1, wherein transmission of said data and / or said data set is terminated in certain cases.

6. A method of wireless communication for a network element, comprising: transmitting a request for at least one of collectable data and transferable data sets; and controlling storage of the data and data sets transmitted based on said request.

Images