Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a transmission unit that transmits information relating to consent for a data set to be transmitted or received; and a control unit that assumes collection of the data set within the scope of consent based on the information relating to the consent. According to the aspect of the present disclosure, it is possible to achieve suitable overhead reduction, channel estimation, resource utilization.

Description

Terminal, Wireless Communication Method, and Base Station

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

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also 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, it is being considered to utilize artificial intelligence (AI) technologies such as machine learning (ML) for network / device control, management, etc.

[0006] While dataset / model management is being considered when utilizing AI models, there are cases where this has not been adequately considered. If this consideration is insufficient, optimal overhead reduction, channel estimation, and resource utilization may not be possible, potentially hindering improvements in communication throughput and communication quality.

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

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

[0009] According to one aspect of this disclosure, suitable overhead reduction, channel estimation, and resource utilization can be achieved.

[0010] Figure 1 shows an example of an AI model management framework. Figure 2 shows an example of specifying an AI model. Figure 3 shows an example of an ORAN architecture. Figure 4 shows an example of a dataset. Figure 5 shows an example of dataset acquisition. Figure 6 shows an example of dataset transfer. Figure 7 shows an example of data collection related to step 1. Figure 8 shows another example of data collection related to step 1. Figure 9 shows another example of data collection related to step 1. Figure 10 shows an example of a data collection / dataset transfer request related to steps 1-2. Figure 11 shows an example of a data / dataset request related to steps 1-3. Figure 12 shows an example of a request for transferable data / dataset information related to step 5-1. Figure 13 shows an example of notification of transferable dataset information related to step 5-2. Figure 14 shows an example of data transfer related to step 6. Figure 15 shows an example of a UE consent report according to the first embodiment. Figure 16 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 17 shows an example of a base station configuration according to one embodiment. Figure 18 shows an example of a user terminal configuration according to one embodiment. Figure 19 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 20 shows an example of a vehicle according to one embodiment.

[0011] (Application of Artificial Intelligence (AI) Technology to Wireless Communication) Regarding future wireless communication technologies, the use of AI technologies such as Machine Learning (ML) for network / device control and management is being considered.

[0012] For example, terminals (user terminals, User Equipment (UE)) and base stations (BS) are being considered to utilize AI technology to improve Channel State Information (CSI) feedback (e.g., overhead reduction, improved accuracy, prediction), beam management (e.g., improved accuracy, prediction in the spatiotemporal domain), and position measurement (e.g., improved position estimation / prediction).

[0013] The AI ​​model may output at least one piece of information, such as an estimated value, a predicted value, a selected action, or a classification, based on the input information. The UE / BS may input channel status information, reference signal measurements, etc., to the AI ​​model and output highly accurate channel status information / measurements / beam selection / position, future channel status information / wireless link quality, etc.

[0014] In this disclosure, AI may be interpreted as an object (also called a subject, object, data, function, program, etc.) having 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 this disclosure, estimation, prediction, and inference may be interpreted interchangeably. Also, in this disclosure, estimate, predict, and infer may be interpreted interchangeably.

[0016] In this disclosure, an object may be, for example, a device or apparatus such as a UE or BS. In this disclosure, an object may also refer to a program / model / entity that operates on such apparatus.

[0017] Furthermore, in this disclosure, the AI ​​model may be reinterpreted as an object having (implementing) at least one of the following features: - generating estimates by feeding; - predicting estimates by feeding; - discovering features by feeding; - selecting actions by feeding.

[0018] Furthermore, in this disclosure, the term "AI model" may also mean a data-driven algorithm that applies AI technology to generate a set of outputs based on a set of inputs.

[0019] Furthermore, in this disclosure, AI models, models, ML models, predictive analytics, predictive analytics models, tools, autoencoders, encoders, decoders, neural network models, AI algorithms, schemes, etc., may be interpreted interchangeably. Also, AI models may be derived using at least one of the following: regression analysis (e.g., linear regression analysis, multiple regression analysis, logistic regression analysis), support vector machines, random forests, neural networks, deep learning, etc.

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

[0021] Furthermore, in this disclosure, terms such as encoder, encoding, encoding / encoded, modification / change / control by an encoder, compression, compression / compressed, generating, and generated / generated may be interpreted interchangeably.

[0022] Furthermore, in this disclosure, terms such as decoder, decoding, decoding / decoded, modification / change / control by a decoder, decompressing, decompressing / decompressed, reconstructing, and reconstructing / reconstructed may be interpreted interchangeably.

[0023] In this disclosure, the term "layer" (referring to an AI model) may be interpreted interchangeably with the terms "input layer," "hidden layer," etc., used in an AI model. The layers in this disclosure may correspond to at least one of the following: an input layer, a hidden 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 AI models may include supervised learning, unsupervised learning, reinforcement learning, and federated learning. Supervised learning may mean the process of training a model from inputs and corresponding labels. Unsupervised learning may mean the process of training a model without labeled data. Reinforcement learning may mean the process of training a model from inputs (in other words, states) and feedback signals (in other words, rewards) resulting from the model's outputs (in other words, actions) in an environment in which the model interacts.

[0025] In this disclosure, terms such as generation, calculation, and derivation may be interpreted interchangeably. In this disclosure, terms such as implementation, operation, function, and execution may be interpreted interchangeably. In this disclosure, terms such as training, learning, updating, and retraining may be interpreted interchangeably. In this disclosure, terms such as inference, after-training, production use, and actual use may be interpreted interchangeably. In this disclosure, "signal" may be interpreted interchangeably with "signal / channel".

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

[0027] The data collection stage is the phase in which data is collected for the generation / updating of an AI model. The data collection stage may also include data organization (e.g., deciding which data to transfer for model training / model inference) and data transfer (e.g., transferring data to entities (e.g., UE, gNB) that will be used for model training / model inference).

[0028] Data collection may also mean the process by which data is collected by a network node, management entity, or UE for the purpose of AI model training / data analysis / inference. In this disclosure, processing and procedures may be interpreted interchangeably. In this disclosure, collection may also mean obtaining a dataset (e.g., usable as input / output) for AI model training / inference based on measurements (e.g., channel measurements, beam measurements, radio link quality measurements, location estimation).

[0029] In this disclosure, offline field data may be data collected from the field (real world) and used for offline training of an AI model. In this 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, the model is trained based on the data (training data) transferred from the collection stage. This stage may include data preparation (e.g., data preprocessing, cleaning, formatting, transformation, etc.), model training / validation, model testing (e.g., checking whether the trained model meets performance thresholds), model exchange (e.g., transferring the model for distributed learning), and model deployment / update (deploying / updating the model to entities that perform model inference).

[0031] Furthermore, AI model training may also refer to the process of training an AI model in a data-driven manner and obtaining a trained AI model for inference.

[0032] Furthermore, AI model validation may refer to a sub-process of training that evaluates the quality of the AI ​​model using a different dataset than the one used for model training. This sub-process helps in selecting model parameters that generalize beyond the dataset used for model training.

[0033] Furthermore, AI model testing may refer to a sub-training process that evaluates the performance of the final AI model using a different dataset than the one used for model training / validation. 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., data preprocessing, cleaning, formatting, transformation, etc.), model inference, model monitoring (e.g., monitoring the performance of the model inference), model performance feedback (feeding back model performance to the entities being trained on the model), and output (providing the model output to the actors).

[0035] Furthermore, AI model inference may also refer to the process of using a trained AI model to produce a set of outputs from a set of inputs.

[0036] Furthermore, the UE-side model may refer to an AI model in which the inference is performed entirely within the UE. The network-side model may refer to an AI model in which the inference is performed entirely within the network (e.g., gNB).

[0037] Furthermore, a one-sided model may refer to either the UE-side model or the 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, for example, the first part of the inference may be performed first by the UE and the rest by the gNB (or vice versa).

[0038] Furthermore, AI model monitoring may also refer to the process of monitoring the inference performance of an AI model, and may be interchangeable with model performance monitoring, performance monitoring, etc.

[0039] Model registration may also mean making a model executable (registering it) by assigning a version identifier to the model and compiling it for specific hardware used during the inference phase. Model deployment may also mean delivering (or activating) a runtime image (or execution environment image) of a fully developed and tested model to a target (e.g., UE / gNB) where inference will be performed.

[0040] The actor stage may include an action trigger (e.g., a determination of whether to trigger an action against other entities), feedback (e.g., feedback of information necessary for training data / inference data / performance feedback), and the like.

[0041] For example, the training of a model for mobility optimization may be performed, for example, in the maintenance operation management (Operation, Administration and Maintenance (Management) (OAM)) in a network (Network (NW)) / gNodeB (gNB). In the former case, interoperability, large-capacity storage, operator manageability, and model flexibility (such as feature engineering) are advantageous. In the latter case, advantages include the latency of model updates and the lack of need for data exchange for model deployment. The inference of the above model may be performed, for example, in the gNB.

[0042] Depending on the use case (or, in other words, the function of the AI model), the entity that performs training / inference may be different. The function of the AI model may include beam management, beam prediction, autoencoder (or information compression), CSI feedback, positioning, and the like.

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

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

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

[0046] Regarding AI-assisted beam management or AI-assisted UE-based positioning based on beam measurement, OAM / gNB / UE may perform model training, and UE may perform model inference.

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

[0048] Also, model transfer may mean delivering an AI model over the air interface. This delivery may include delivering one or both of the parameters of a known model structure or a new model with parameters on the receiving side. Also, this delivery may include a complete model or a partial model. Model download may mean model transfer from the network to the UE. Model upload may mean model transfer from the UE to the network.

[0049] Figure 2 is a diagram showing an example of specifying an AI model. In this example, UE and NW (e.g., Base Station (BS)) can recognize models #1 and #2 (it is not necessary to fully understand the details of the models). UE may report, for example, the performance of model #1 and the performance of model #2 to NW, and NW may instruct UE about the AI model to be used.

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

[0051] In 5G NR, in order to reduce the burden of operator RAN construction / operation and to introduce automation using AI / ML models, the standardization of Open RAN (ORAN / ORAN Alliance) is being considered.

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

[0053] As shown in Figure 3, the RIC may include non-real-time RIC and near real-time RIC (which may simply be called real-time RIC).

[0054] Non-real-time RIC may be located within a Service Management and Orchestration (SMO) that performs RAN monitoring, maintenance, and orchestration.

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

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

[0057] The non-real-time RIC may work in conjunction with the function unit that provides OAM services within the SMO to collect data accumulated within the E2 node, such as Performance Management Counter, 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. The near real-time RIC may also control the E2 node according to the policy notified by the non-real-time RIC.

[0059] Note that the ORAN architecture shown in Figure 3 is merely one example and is not the only example.

[0060] (Analysis) In future wireless communication systems (e.g., Rel. 19 and beyond), use cases are anticipated where datasets will be required when utilizing AI / ML models.

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

[0062] Furthermore, the use of data collection in the Core Network (CN), Operation Administration and Maintenance (Management) (OAM), and Over The Top (OTT) is being considered in the UE's model training.

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

[0064] However, in such use cases, the sharing of data / datasets has not been adequately considered.

[0065] For example, it is preferable to avoid sharing data related to multiple different users without the user's consent, and when a network distributes a dataset to a consumer, it should avoid including data collected by users other than the consumer in the dataset. However, the specific methods for achieving this have not been sufficiently considered.

[0066] Furthermore, there has been insufficient consideration of what the UE will report regarding such consent, and how the UE's assumptions / expectations regarding such consent will be defined (Issue 1).

[0067] Furthermore, there has been insufficient consideration of what data / datasets the UE receives, and the relationship between the data / datasets the UE receives and the data / datasets the UE collects (Issue 2).

[0068] Furthermore, the operation of the NW data management entity has not been adequately considered (Issue 3).

[0069] If these considerations are insufficient, it may become impossible to properly utilize AI / ML models using datasets in future wireless communication systems, potentially hindering improvements in communication throughput.

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

[0071] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0072] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0073] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0074] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0075] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0076] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0077] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0078] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0079] (Wireless communication methods) The following explains the terms and phrases used in this disclosure.

[0080] In this disclosure, “dataset” may mean a set of data samples assigned to a dataset ID [and dataset-related information].

[0081] In this disclosure, “data sample” may mean a component of a dataset.

[0082] In this disclosure, “dataset delivery” may mean the delivery of a dataset (for example, from a DSM to a consumer / from a provider to a DSM).

[0083] In this disclosure, “data” is a generic term and may mean a data sample (a component of a dataset) or a dataset.

[0084] In this disclosure, “data collection” may mean the collection of data [including the transfer of data samples].

[0085] In this disclosure, “dataset identification” may also mean a procedure for obtaining a common understanding / recognition of a dataset (for example, an understanding of the mapping between a dataset ID and a dataset).

[0086] In this disclosure, "Dataset manage (management) entity (DSM)" may also refer to an entity that manages a dataset.

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

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

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

[0090] The DSM may be any core network (CN), network function (NF), CN NF, SMO, non-real-time RIC, or real-time RIC.

[0091] In this disclosure, the NF may include, for example, at least one of the following: • Application Function (AF) (e.g., a function that provides 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 provides a data network outside the 5GC). • Location Management Function (LMF) (e.g., a function that controls communication related to location information services). • Non-3GPP Inter-Working Function (N3IWF) (e.g., a function that connects an untrusted non-3GPP access network to the 5GC). • Network Exposure Function (NEF) (e.g., a function that provides an application interface for the 5GC's 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 maintenance and operation management). - Policy Control Function (PCF) (e.g., a function that controls the quality and policies 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 to 5GC).・Trusted WLAN Interworking Function (TWIF) (e.g., a function that connects a trusted non-3GPP access network to 5GC for non-5G UEs via a wireless local area network (LAN)). ・(Radio) Access Network ((R)AN) (e.g., a function that provides a wireless access network). ・User Equipment (UE) (e.g., a function that allows users to access network services via a wireless 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 that bypasses the telecommunications carrier's network). ・Analytics Data Repository Function (ADRF) (e.g., a function that stores / manages analytical data in a communication network). - Data Collection Analytics Function (DCAF) (e.g., a function to collect and analyze data in a communication network). - Data Collection Coordination Function (DCCF) (e.g., a function to collect and coordinate data in a communication network).

[0092] It should be noted that these are merely examples, and it is understood that other non-funding factors are also covered in this disclosure.

[0093] This disclosure primarily describes the operation of DSM, but DSM (the name of DSM) is merely an example and may be interpreted as any network component / function.

[0094] In this disclosure, “Consumer” may mean an entity that receives a dataset for a specific use. In this disclosure, a Consumer may be, for example, a UE, a RAN node (e.g., a base station), an OAM, a CN NF, an SMO, a non-real-time RIC, a real-time RIC, etc.

[0095] In this disclosure, "Requester" may mean an entity that requests the DSM to deliver a dataset to a consumer. For example, the Requester may be a consumer, such as a UE, RAN node, OAM, CN NF, SMO, non-real-time RIC, real-time RIC, etc.

[0096] In this disclosure, “Provider” may mean an entity that provides data / data samples / datasets to the DSM.

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

[0098] In this disclosure, "other users" may refer to at least one of the following: other UEs, other UE side servers, any AF, any NF, or third parties.

[0099] In this disclosure, “data,” “feedback,” “signal,” and “dataset” may be interpreted as mutually exclusive.

[0100] In this disclosure, a dataset may include at least one of the following values: a dataset ID (e.g., an identifier for the dataset); a feature / label (e.g., a representation of a data value); a data value (e.g., a value for a data sample); and data / dataset-related information.

[0101] Furthermore, the said feature may be at least one of those described in Supplementary Information 8 below.

[0102] Furthermore, the label may also be one of the features in this disclosure.

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

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

[0105] The DSM may be triggered to retrieve the dataset.

[0106] DSM may obtain the dataset.

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

[0108] The data collection process will be described in detail in step 1 below.

[0109] The data generation process will be described in detail in step 2 below.

[0110] The creation and registration of datasets will be described in detail in step 3 below.

[0111] Additionally, the DSM may receive a dataset from the provider entity.

[0112] Dataset transfer / distribution will be described in detail in step 1 below.

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

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

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

[0116] Figure 5 shows an example of dataset acquisition. In the example shown in Figure 5, first, the DSM collects data from the provider (S501). Next, the DSM constructs / creates the dataset (S502). Furthermore, the DSM identifies the dataset to the provider (S503).

[0117] <Dataset Transfer / Distribution> The following section provides an overview of dataset transfer / distribution using DSM.

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

[0119] In this disclosure, "transfer" and "delivery" may be interpreted interchangeably.

[0120] The DSM may be requested by the requester to transfer the dataset.

[0121] The request for dataset transfer will be described in detail in step 5 below.

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

[0123] Dataset transfer / distribution will be described in detail in step 6 below.

[0124] Figure 6 shows an example of dataset transfer. In the example shown in Figure 6, first, the DSM receives a request from the requester for the transfer of a dataset (S601). Next, the DSM transfers / distributes the dataset to the consumer (S602).

[0125] <Procedure 1> Procedure 1 concerns data collection and data set transfer to the DSM.

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

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

[0128] Step 2: The DSM may receive information about at least one of the data that can be collected and the data sets that can be transferred.

[0129] For example, in step 2, the source / provider (e.g., UE / base station / CN NF / OAM / AF / DSM) may transmit information about collectible data / transferable datasets that are deliverable to the DSM.

[0130] Step 3: The DSM may request the source / provider to collect / provide the data / dataset to the DSM.

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

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

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

[0134] Figure 7 shows an example of data collection related to Procedure 1. The example shown in Figure 7 illustrates the case where the provider is a User Application (UE).

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

[0136] Figure 8 shows another example of data collection related to step 1. In the example shown in Figure 8, the provider is a RAN node. The operations performed by the DSM may be the same as those in Figure 7, but with the UE replaced by a RAN node (S801-S805).

[0137] Figure 9 shows another example of data collection related to Procedure 1. The example shown in Figure 9 shows the case where the provider is NF / OAM. The actions performed by DSM may be the same as those in Figure 7 above, but with UE replaced by NF / OAM (S901-S905).

[0138] <<Procedure 1-1>> Procedure 1-1 will provide a detailed explanation of Step 1 in Procedure 1 above.

[0139] In Step 1, the DSM may contact a specific entity.

[0140] The specific entity in question may be, for example, an entity (e.g., a UDM) that manages subscriber information / subscriptions for a particular UE regarding the feasibility of data collection / dataset transfer for that UE.

[0141] The specific entity in question may be, for example, an entity that manages at least one of the data collection / dataset transfer access tokens and the data collection / dataset transfer services / functions for a particular UE.

[0142] According to Procedure 1-1, user consent for data collection / dataset use can be properly verified.

[0143] <<Procedure 1-2>> Procedure 1-2 will provide a detailed explanation of Step 2 in Procedure 1 above.

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

[0145] The message / signaling / information may include, for example, the requested information. The message / signaling / information may include, for example, information about at least one of the following: • How many data samples can be collected. • Data-related information about the collectible data (the data-related information may be defined as described in Supplement 5 below). • Data collection / dataset transfer capability (data collection / dataset transfer-related information available for data collection (the data collection / dataset transfer-related information may be defined as described in Supplement 6 below)). • Provider entity-related information (the entity-related information may be defined as described in Supplement 7 below).

[0146] A potential provider may, based on an incoming request, send messages / signaling / information relating to at least one of the collectible data, the transferable dataset, and the data collection / data transfer capability.

[0147] The messages / signals / information transmitted by the potential provider may include all or part (a subset) of the requested information.

[0148] Messages / signals / information sent by a potential provider may contain only information that is different (e.g., updated) from the information received previously.

[0149] Figure 10 shows an example of a data collection / dataset transfer request related to step 1-2. In the example shown in Figure 10, the potential provider is shown to be a UE.

[0150] In the example shown in Figure 10, the DSM sends a request to the UE for information on transferable datasets (S1001). The UE then sends a response to the request (information on transferable datasets) (S1002).

[0151] According to steps 1-2, information regarding collectible data / transferable datasets can be properly sent and received.

[0152] <<Procedure 1-3>> Procedure 1-3 will provide a detailed explanation of step 3 in Procedure 1 above.

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

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

[0155] The message / signaling / information may include information relating to at least one of the following: • The requested dataset ID. • Which / how many data samples are requested. • Data / dataset-related information relating to the requested data / dataset (the data / dataset-related information may be specified as described in Supplement 5 below). • Data collection / dataset transfer capabilities relating to the requested data / dataset (the data collection / dataset transfer information may be specified as described in Supplement 6 below). • Provider entity-related information (the entity-related information may be specified as described in Supplement 7 below).

[0156] The provider does not need to expect or anticipate receiving messages, signaling, or information requesting data / datasets that have not been reported as collectible / transferable in step 2 of procedure 1 above.

[0157] Figure 11 shows an example of a data / dataset request related to steps 1-3. In the example shown in Figure 11, the DSM sends a request to the provider regarding data collection / dataset transfer (S1101). The provider then performs data collection / dataset transfer to the DSM (S1102).

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

[0159] <<Procedure 1-4>> Procedure 1-4 will provide a detailed explanation of step 4 in Procedure 1 above.

[0160] The DSM may receive data / datasets from the provider.

[0161] Providers (e.g., UE / base station / CN NF / OAM / AF / DSM) may provide data / datasets to DSM.

[0162] <<<Procedure 1-4-1>>> The provider may initiate the transfer of the dataset to the DSM.

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

[0164] The provider may specify which information (e.g., the type of dataset) from the dataset to transfer.

[0165] For example, the provider provides data / dataset-related information about the data / dataset being transferred (e.g., information indicating which features will be transferred; however, data / dataset-related information may be defined as described in Supplement 5 below).

[0166] For example, the provider may provide information indicating which / how many data samples will be transferred (e.g., the number of samples or the index of the data samples).

[0167] The provider may notify how to transfer the dataset (or between datasets).

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

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

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

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

[0172] The termination instruction may include information regarding at least one of the following: • The reason for terminating the dataset transfer. • How many datasets (sample datasets) will be sent after the termination instruction is sent / received. • How many dataset transfer messages / signals will be sent after the termination instruction is sent / received.

[0173] Furthermore, the specific case may also be when the DSM sends / receives a termination command.

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

[0175] The termination instruction may include information regarding at least one of the following: • The reason for terminating the dataset transfer. • How many datasets (sample datasets) will be sent after the termination instruction is sent / received. • How many dataset transfer messages / signals will be sent after the termination instruction is sent / received.

[0176] Furthermore, this particular case may also occur when the provider has completed the transfer of multiple (e.g., all) datasets.

[0177] For example, the specific case may be when the amount of data sample required in step 3 above has been transferred.

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

[0179] For example, that particular case might be when all the data samples included in the transferred dataset have been transferred.

[0180] Following steps 1-4, data / dataset transfer can be performed properly.

[0181] By following the above procedure 1, data collection and dataset transfer can be performed appropriately.

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

[0183] DSM may perform data generation.

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

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

[0186] The request may include a method for generating data (e.g., data / data samples / datasets).

[0187] The request may include information relating to at least one of the following: • The dataset ID that serves as the basis for data generation. • Which / how many datasets to generate. • Dataset-related information for the datasets to be generated (the dataset-related information may be defined as described in Supplement 5 below). • Dataset transfer-related information available for dataset transfer (the dataset transfer-related information may be defined as described in Supplement 6 below). • Entity-related information for the entity requesting the generation of dataset information (the entity-related information may be defined as described in Supplement 7 below). • Requirements for the generated data.

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

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

[0190] Interruption of the data collection procedure may be performed based on, for example, an operator policy regarding the number / rate of data samples collected from the provider, an estimated time to collect the necessary samples considering the availability period of the dataset, and a termination signal from the provider.

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

[0192] In step 4, the DSM may generate data (e.g., data samples / datasets) based on at least one of the following: • Existing data stored in the DSM (e.g., data samples / datasets); • A statistical channel model; • The use of generative adversarial networks (GANs).

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

[0194] <Step 3> Step 3 concerns the creation / registration of a dataset.

[0195] DSM may create / register datasets.

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

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

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

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

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

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

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

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

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

[0205] By following the above procedure 3, the DSM can properly create and register datasets.

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

[0207] The DSM may provide at least one of the following: the dataset ID, the dataset, and the data / dataset-related information.

[0208] For example, the DSM may send such notification to the entity that requested the creation / registration of the dataset.

[0209] For example, the DSM may send such notification to the entity that provided the dataset.

[0210] By following the above procedure 4, it is possible to properly identify the dataset.

[0211] <Step 5> Step 5 concerns the request for dataset transfer.

[0212] The requester may request a dataset [transfer].

[0213] In a dataset transfer request, at least one of the following steps 1 to 3 in procedure 5 may be performed (see Figure 6 above).

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

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

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

[0217] For example, in step 2, the potential requester may receive information about data / datasets that can be transferred to the potential requester. This information may include, for example, a data / dataset ID and at least one of the data / dataset-related information.

[0218] Step 3: The DSM may receive a request from the requester to transfer data / datasets.

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

[0220] <<Procedure 5-1>> Procedure 5-1 will provide a detailed explanation of Step 1 in Procedure 5 above.

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

[0222] UE / RAN node / base station / NF / OAM / AF / SMO / non-real-time RIC / real-time RIC may request DSM to transmit information regarding at least one of the transferable datasets and how the datasets are transferable.

[0223] The message / signaling relating to the request may include information relating to at least one of the following: • The transferable dataset ID. • Which / how many data samples are transferable. • Dataset-related information relating to the transferable dataset (the dataset-related information may be defined as described in Supplement 5 below). • Dataset transfer-related information available for dataset transfer (the dataset transfer-related information may be defined as described in Supplement 6 below). • Entity-related information relating to the entity requesting transferable dataset information (the entity-related information may be defined as described in Supplement 7 below).

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

[0225] The response may include information relating to at least one of the following: • Acknowledgment (e.g., transferable data information, which will be detailed in step 5-2 below). • Reject (e.g., reasons for rejection).

[0226] Figure 12 shows an example of a request for transferable data / dataset information related to step 5-1. In the example shown in Figure 12, first, the UE sends a request for transferable dataset information to the DSM (S1201). Then, the DSM sends a response signal to the UE for the request (for example, transferable dataset information) (S1202).

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

[0228] <<Procedure 5-2>> Procedure 5-2 will provide a detailed explanation of Step 2 in Procedure 5 above.

[0229] The DSM may notify information about transferable datasets.

[0230] UE / RAN node / base station / NF / OAM / AF / SMO / non-real-time RIC / real-time RIC may receive information about at least one of the transferable datasets and how the datasets are transferable.

[0231] The message / signaling relating to the information may include information relating to at least one of the following: • The transferable dataset ID. • Which / how many data samples are transferable. • Dataset-related information relating to the transferable dataset (the dataset-related information may be defined as described in Supplement 5 below). • Dataset transfer-related information available for dataset transfer (the dataset transfer-related information may be defined as described in Supplement 6 below). • Entity-related information relating to the entity requesting the transferable dataset information (the entity-related information may be defined as described in Supplement 7 below).

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

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

[0234] Figure 13 shows an example of notification of transferable dataset information related to step 5-2. In the example shown in Figure 13, the DSM sends transferable dataset information (#1 and #2) to the UE (S1301 / S1302).

[0235] In the example shown in Figure 13, for example, the transferable dataset information #2 may contain only the information updated from the transferable dataset information #1.

[0236] According to step 5-2, it is possible to appropriately notify users of transferable dataset information.

[0237] <<Procedure 5-3>> Procedure 5-3 will provide a detailed explanation of step 3 in Procedure 5 above.

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

[0239] A requester (e.g., a 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 transferable datasets and how the datasets are transferable.

[0240] The message / signaling relating to the request may include information relating to at least one of the following: • The requested dataset ID. • Which / how many data samples are requested. • Dataset-related information relating to the requested dataset (the dataset-related information may be defined as described in Supplement 5 below). • Dataset transfer-related information relating to the requested dataset transfer (the dataset transfer-related information may be defined as described in Supplement 6 below). • Entity-related information relating to the requester (the entity-related information may be defined as described in Supplement 7 below). • The usage of the dataset.

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

[0242] The response may include information regarding at least one of the following: • Acknowledgment. • Rejection (for example, including reasons for rejection).

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

[0244] By following the above procedure 5, a request for dataset transfer can be made appropriately.

[0245] <Step 6> Step 6 concerns the transfer / delivery of the dataset.

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

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

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

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

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

[0251] For example, in step 2, the consumer may stop receiving the dataset from the DSM.

[0252] Figure 14 shows an example of data transfer related to step 6. In the example shown in Figure 14, the DSM transfers / distributes the dataset to the consumer.

[0253] <<Procedure 6-1>> Procedure 6-1 will provide a detailed explanation of Step 1 in Procedure 6 above.

[0254] The DSM may initiate the transfer of the dataset to the consumer.

[0255] The DSM may notify what information to transfer.

[0256] For example, the DSM may transmit dataset-related information about the dataset being transmitted (the dataset-related information may be defined as described in Supplement 5 below). This dataset-related information may, for example, indicate which / which features are being transmitted.

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

[0258] This information may, for example, indicate the number of samples to be notified. For example, if information indicating a sample size of 50 is notified, data samples corresponding to indices 0 through 49 (or 1 through 50) may be transferred.

[0259] Additionally, for example, the DSM may notify the index of the data sample being transferred.

[0260] The DSM may notify how the dataset transfer should be performed.

[0261] For example, the DSM may transmit 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 Supplement 6 below).

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

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

[0264] This particular case may be, for example, when the DSM receives a termination command.

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

[0266] The termination instruction may include information regarding at least one of the following: • The reason for terminating the dataset transfer. • How many datasets (sample datasets) will be sent after the termination instruction is sent / received. • How many dataset transfer messages / signals will be sent after the termination instruction is sent / received.

[0267] Furthermore, the specific case may also occur when the DSM sends a termination command.

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

[0269] The termination instruction may include information regarding at least one of the following: • The reason for terminating the dataset transfer. • How many datasets (sample datasets) will be sent after the termination instruction is sent / received. • How many dataset transfer messages / signals will be sent after the termination instruction is sent / received.

[0270] Furthermore, this particular case may also occur when the provider has completed the transfer of multiple (e.g., all) datasets.

[0271] For example, the specific case may be when the amount of data sample required in step 3 of procedure 5 above has been transferred.

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

[0273] For example, that particular case might be when all the data samples included in the transferred dataset have been transferred.

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

[0275] By following the above procedure 6, the dataset transfer can be performed properly.

[0276] <First Embodiment> The first embodiment relates to a method for resolving the above issue 1.

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

[0278] The UE may submit a report regarding user consent (which may simply be called consent or UE consent) (see Figure 15).

[0279] UE may report information regarding consent about the data / datasets being sent / received.

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

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

[0282] In this disclosure, such consent [to forward / receive] may be defined / determined on the basis of at least one of the following: each type of UE report, each ID of the UE report, each setting of the UE report, and each method of data processing.

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

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

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

[0286] The scope of such consent may, for example, be limited to specific (partial) UEs.

[0287] The specific (partial) UE in question may, for example, be a UE from the same vendor / type / chipset vendor.

[0288] The specific (partial) UE in question may be, for example, a UE that reports the same ID indicating the content of consent, or a UE that reports an ID indicating the content of consent from within a single list.

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

[0290] According to the first embodiment described above, the content of the report regarding UE consent can be appropriately defined, and this can contribute to resolving Issue 1 above.

[0291] <Second Embodiment> The second embodiment relates to a method for resolving issue 1 described above.

[0292] More specifically, in the second embodiment, we will describe the assumptions / expectations of the UE regarding consent.

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

[0294] In this case, the UE may assume / expect that the data / signals / datasets it transmits / receives will be collected (by other users / the UE) to the extent of the consent reported [for example, by using the first embodiment described above].

[0295] The UE may assume / expect that there are similar / common features between the data / signals / datasets it receives.

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

[0297] A UE may transmit / report one or more data / signals / datasets.

[0298] In this case, the UE does not need to assume or expect that the reported data / signals / datasets (or data / signals / datasets after specific processing) will be received by any entity / device outside the scope of consent.

[0299] According to the second embodiment described above, it is possible to appropriately define the assumptions / expectations of the UE regarding UE consent (i.e., the rules regarding UE consent), and contribute to resolving Issue 1 above.

[0300] <Third Embodiment> The third embodiment relates to a method for resolving issue 2 described above.

[0301] The UE may report information about the index of the data / dataset being collected.

[0302] A UE may perform actions related to receiving data / datasets based on the data / datasets to be collected and at least one of other users (e.g., other UEs / AFs / NFs / third parties).

[0303] The UE may receive data / signals / datasets associated with the same index as the data / datasets it reports.

[0304] In this case, the UE may assume / expect that the data / signals / datasets it receives will contain only the data / signals / datasets that will be processed based on the reported data / signals / datasets.

[0305] Furthermore, the (original) data / signals / dataset reported by the UE may be omitted in the received data / signals / dataset.

[0306] The UE may receive data / signals / datasets that are not associated with the same index as the data / datasets it reports.

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

[0308] In this disclosure, the processed data / signals / dataset may mean data / signals / dataset generated by (or based on) at least one of UE features and feature groups based on group settings.

[0309] According to the third embodiment described above, the data / datasets received by the UE, and the relationship between the data / datasets collected by the UE and the received data / datasets can be appropriately defined, thereby contributing to the resolution of issue 2 above.

[0310] <Fourth Embodiment> The fourth embodiment relates to a method for resolving issue 3 described above.

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

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

[0313] The one or more entities in question may be, for example, DSMs.

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

[0315] The NW / DSM may review information regarding UE consent for any data / signals / datasets reported by the UE / UE side server.

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

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

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

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

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

[0321] According to the fourth embodiment described above, the NW entity behavior related to UE consent can be appropriately defined, and this can contribute to resolving issue 3.

[0322] <Supplement> <<Notification of Information to UE (Supplement 1)>> Notification of any information from the Network (NW) (e.g., Base Station (BS))) to the UE in the above embodiments (in other words, reception of any information from the BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0323] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0324] If the above 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 the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0325] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0326] <<Notification of Information from UE (Supplement 2)>> Notification of any information from the UE to the NW in the above embodiments (in other words, transmission / reporting 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), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

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

[0328] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0329] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0330] <<Regarding the application of each embodiment (Supplement 3)>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / resource / channel / RS; - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0331] The above-mentioned specific UE capabilities may indicate that they support the above-mentioned specific processes / operations / controls / assumptions / information.

[0332] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0333] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

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

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

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

[0337] <<Supplement 4>> In this disclosure, functionality may be a set of parameters supported based on conditions indicated by UE capability (e.g., a set of parameters for CSI prediction / beam prediction / CSI compression).

[0338] In this disclosure, the conditions may be information indicated by UE capability.

[0339] In this disclosure, additional conditions do not have to be indicated by UE capability information, but may be assumed by training.

[0340] <<Supplement 5>> In this disclosure, data / dataset-related information for a given dataset may include at least one of the following: • Model information related to the data / dataset. • Deployment information related to the data / dataset. • Scenario information related to the data / dataset. • Area / site information related to the data / dataset (e.g., serving cell index / area ID). • Vendor information related to the data / dataset (e.g., information of the vendor that collects the data). • Device information related to the data / dataset (e.g., UE / base station). • 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., based on a statistical channel model or based on another dataset).

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

[0342] Regarding model information related to data / datasets, the dataset may be used to train the model.

[0343] Model information may include information regarding preprocessing / postprocessing / quantization methods / quantization resolution.

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

[0345] Feature information related to the data / dataset may indicate the features contained in the data / dataset.

[0346] Feature information associated with the data / dataset may indicate a combination of features included in the data / dataset (e.g., Channel Impulse Response (CIR) and associated UE location).

[0347] Regarding data / dataset quality information, for example, achieving a confidence level of X% may be considered a data quality requirement.

[0348] <<Supplement 6>> The data collection / dataset transfer-related information in this disclosure may include at least one of the following: • The periodic type of the data collection / dataset transfer signaling / message (e.g., periodic / semi-persistent / aperiodic). • The period of the data collection / dataset transfer signaling / message. • The number of samples in one signal / message in the data collection / dataset transfer. • The number of signals / messages in the data collection / dataset transfer.

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

[0350] <<Supplement 8>> The features in this disclosure may be at least one of the following: • Area / site related to the data sample (e.g., serving cell index / area ID). • Model information related to the data sample. • Deployment information related to the data sample. • Scenario information related to the data sample. • Vendor information related to the data sample (e.g., information of the vendor performing data collection). • Device information related to the data sample (e.g., UE / base station). • PLMN / MNO related to the data sample. • Time information related to the data sample. • Frequency information related to the data sample (e.g., band / frequency range). • Quality information of the data sample. • Quantization information related to the data sample. • Information indicating how the data sample is generated (e.g., based on a statistical channel model or based on other datasets).

[0351] Regarding model information related to data samples, the data samples may be generated based on the model (for example, the data samples may be data samples generated by a generative / reconstruction model in training of type 3).

[0352] Regarding model information related to the data samples, the data samples may be used to train the model.

[0353] Model information may include information regarding preprocessing / postprocessing / quantization methods / quantization resolution.

[0354] Device information associated with a data sample may include information from at least one of the following device acquisition data: • Antenna configuration (e.g., number of horizontal / vertical antenna elements / panels, number of ports, antenna spacing, antenna position, panel position, and at least one of the TxRU mappings). • Beam configuration (e.g., beam width / number of beams / beam direction). • TRP information (e.g., TRP altitude and relative position of multi-TRPs).

[0355] Regarding the quality information of data samples, for example, achieving a confidence level of X% may be considered a data quality requirement.

[0356] In this disclosure, the features 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 reconstructed model. - Nominal / target output of the generative model. - Nominal / target output of the reconstructed model / precoding matrix / channel matrix.

[0357] The nominal inputs to 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 X (where X may be a natural number), all parameters may be considered as N features).

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

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

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

[0361] In this disclosure, the features [for time-domain / frequency-domain / spatial-domain CSI prediction] may be the [nominal] inputs to the generative model / precoding matrix / channel matrix.

[0362] The nominal inputs to 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 X (where X may be a natural number), all parameters may be considered as N features).

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

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

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

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

[0367] In this disclosure, the features [for beam prediction in the time domain / frequency domain / spatial domain] may be the [nominal] inputs to the generative model / precoding matrix / channel matrix.

[0368] For example, a feature [for beam prediction in the time domain / frequency domain / 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 a 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 maximum RSRP / SINR). • Top K beams (the K RS / beam indices that achieve a large RSRP / SINR from 1 to K). • The probability of the top 1 beam for each set A. • The top K probability for each set A. • The top K / 1 probability of the top K beams in set A.

[0369] The UE may transmit beam information to the network. The beam information may include at least one of the following pieces of information. Which information to include in the beam information may be notified to the UE by the network, specified in the standard, or derived from the model used for beam prediction (associated model). The beam information may also be derived from at least one of the following: information notified to the UE by the network without the UE reporting it, values ​​specified in the standard, or the model used for beam prediction (associated model).

[0370] Beam information may include information indicating the top-X probability. The top-X probability for one of several resources may mean the probability / confidence level / confidence interval that the RSRP or SINR corresponding to that resource is greater than or equal to the Xth largest RSRP or SINR among the RSRP or SINR corresponding to the one or more resources. This confidence interval may be any percentage (e.g., 95%).

[0371] Beam information may include information indicating the top-X' / 1 probability. The top-X' / 1 probability for one or more resources may mean the probability / confidence level / confidence interval at which 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 any percentage (e.g., 95%). If different top-X' / 1 probabilities are obtained for the same value of X' depending on how the resources are selected, one of these values ​​(e.g., the maximum value) may be determined as the top-X' / 1 probability.

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

[0373] The information indicating L1-RSRP, top X probability, top X' / 1 probability, or the difference information relating thereto may be quantized information. The quantized information may be information represented by a specific number of bits that divide L1-RSRP, top X probability, top X' / 1 probability, or the difference thereto into a specific range that can be represented at a specific quantization resolution (e.g., dB step size) (the value indicated by the bit corresponds to one of the steps (divisions)).

[0374] It is preferable that the quantized information of differential information be represented with fewer bits than the quantized information of non-differential information (for example, with a lower quantization resolution or a narrower representable range than the quantized information of non-differential information), but it may also be represented with the same or more bits.

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

[0376] In this disclosure, the [positioning] feature may be the [nominal] input to the generative model / precoding matrix / channel matrix.

[0377] For example, a feature [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 power intensity per antenna port / per path delay [ / per TRP]). • Delay profile (DP, e.g., DP may be a parameter representing power presence per antenna port / per path delay [ / per TRP]). • A parameter representing the time corresponding to a data sample. • A parameter representing the path delay corresponding to a data sample. • LOS (line-of-sight) / NLOS (non-line-of-sight) identification [per TRP / per PRS] (soft / hard value of LOS / NLOS identification). • Timing of arrival [per TRP] (ToA). • Receive (Rx) - Transmit (Tx) time difference [per TRP]. • Angle of Arrival (AoA) [per TRP] (DL / UL AoA). • Angle of Departure (AoD) [per TRP] (DL / UL AoA). • Number of wavelengths between TRP and UE. • Rx-Tx phase difference between TRP and UE. • DL Receive Time Difference (Reference Signal Time Difference (RSTD)) / UL Arrival Time Difference (Time Difference of Arrival (TDoA)) (per path / per TRP). • RSRPs / RSRPPs (path-specific RSRPs, RSRPPs). • Likelihood of the above values ​​(e.g., probability of each ToA value for each TRP). UE position (e.g., UE position coordinates).

[0378] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having a transmitting unit that transmits information regarding consent for a dataset to be transmitted or received, and a control unit that assumes that the collection of the dataset will be carried out within the scope of the consent based on the consent information. [Note 2] The terminal according to Note 1, wherein the consent information includes at least one of the following: information indicating whether consent has been obtained for the transfer of a dataset reported by the terminal to other users, information indicating whether consent has been obtained for the terminal to receive a dataset reported by other users, information indicating the scope of the consent, and information indicating the validity period of the consent. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit assumes that the collection of the dataset will not be carried out by any entity outside the scope of the consent based on the consent information. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the transmitting unit transmits information regarding the index of the dataset to be collected.

[0379] (Wireless Communication System) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof.

[0380] Figure 16 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0381] Furthermore, the wireless communication system 1 may 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)), and the like.

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

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

[0384] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

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

[0386] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

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

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

[0390] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0391] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0392] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0393] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0394] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0395] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each user terminal 20.

[0396] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0397] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0399] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0400] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0401] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

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

[0403] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0404] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, the DL-RS may include 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.

[0405] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0406] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0407] (Base Station) Figure 17 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0408] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0409] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0411] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0412] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0413] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0414] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0415] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0416] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.

[0417] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

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

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

[0420] The transmitting / receiving unit 120 (receiving 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 (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0421] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0422] The transmission path interface 140 may send and receive signals (backhaul signaling) with 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.

[0423] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

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

[0425] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

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

[0427] (User Terminal) Figure 18 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0428] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0429] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0431] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0432] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0433] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0434] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0435] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0436] The transmitting / receiving 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 and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0437] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0438] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

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

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

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

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

[0443] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. 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 interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0444] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0445] The transmitting / receiving unit 220 may transmit information regarding consent for the dataset to be transmitted or received. The control unit 210 may assume that the collection of the dataset will be carried out within the scope of consent based on the consent information.

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

[0447] The control unit 210 may assume that the data set is not collected in any entity outside the scope of consent based on the information regarding the consent.

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

[0449] (Hardware Configuration) The block diagrams used in the description of the above embodiment show functional unit blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly (e.g., using wired, wireless, etc.) connected and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0450] Here, functions include, but are not limited to, judgment, decision-making, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), assigning, etc. For example, a functional block (component) that enables transmission may be referred to as a transmitting unit, a transmitter, etc. In any case, as described above, the implementation method is not particularly limited.

[0451] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs the processing of the wireless communication method of the present disclosure. FIG. 19 is a diagram showing 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 physically be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0452] In the present disclosure, the terms such as device, circuit, device, section, unit, etc. can be read interchangeably with each other. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without including some devices.

[0453] For example, although only one processor 1001 is shown, there may be a plurality of processors. Also, the processing may be executed by one processor, or the processing may be executed by two or more processors simultaneously, sequentially, or using other methods. Note that the processor 1001 may be implemented by one or more chips.

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

[0455] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0456] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.

[0457] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0458] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

[0459] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated transmitting unit 120a (220a) and receiving unit 120b (220b).

[0460] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0461] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

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

[0463] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0464] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0465] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0466] Here, the neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

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

[0469] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

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

[0471] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0472] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0473] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0474] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0475] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0476] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0477] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0478] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

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

[0480] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

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

[0482] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0483] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

[0485] The names used for parameters, etc. in the present disclosure are not limiting names in any way. Furthermore, mathematical formulas, etc. using these parameters may be different from those explicitly disclosed in the present disclosure. Since various channels (such as PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not limiting names in any way.

[0486] The information, signals, etc. described in the present disclosure may be represented using any of various 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0487] In addition, information, signals, etc. may be output from at least one of the upper layer to the lower layer and from the lower layer to the upper layer. Information, signals, etc. may be input and output via a plurality of network nodes.

[0488] The input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information, signals, etc. may be overwritten, updated, or appended. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

[0489] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0490] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0491] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0492] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not providing notification of the specified information or by providing notification of other information).

[0493] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0494] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0496] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0497] 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,” and “receiving entity” may be used interchangeably.

[0498] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0499] The above group may include, for example, at least one of the following: 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, or a panel group.

[0500] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0501] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0502] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

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

[0504] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0505] In this disclosure, terms such as “Base Station (BS),” “wireless 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,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0506] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services 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 ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0507] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0509] A mobile station may also be called 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 appropriate term.

[0510] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0511] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0512] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

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

[0516] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0517] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0519] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0520] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0521] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices 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. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

[0523] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

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

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

[0526] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0527] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0528] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0529] Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0530] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0531] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0532] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0533] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0534] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0535] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0536] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0537] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0538] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0539] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0540] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0541] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0542] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0543] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0544] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0545] In this disclosure, phrases 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. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0546] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0547] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0548] This application is based on Japanese Patent Application No. 2025-025791, filed on February 20, 2025. All of its contents are included herein.

Claims

A transmitting unit that transmits information regarding consent about a dataset to be transmitted or received, A terminal having a control unit which assumes that the collection of the dataset will be carried out within the scope of consent based on the information regarding the consent. 　 The terminal according to claim 1, wherein the information relating to consent includes at least one of the following: information indicating whether consent has been obtained to transfer a dataset reported by the terminal to other users; information indicating whether consent has been obtained to receive a dataset reported by other users; information indicating the scope of consent; and information indicating the validity period of consent. 　 The terminal according to claim 1, wherein the control unit assumes that the dataset will not be collected in any entity outside the scope of consent based on the consent information. 　 The terminal according to claim 1, wherein the transmitting unit transmits information regarding the index of the collected dataset. 　 The steps include: sending information regarding consent about the dataset to be sent or received, A wireless communication method for a terminal, comprising the step of assuming that the collection of the dataset is carried out within the scope of consent based on the information regarding the consent. 　 A receiving unit that receives information regarding consent about a dataset to be transmitted or received, A base station having a control unit that controls the transmission of the dataset for collection within the scope of consent based on the consent information.

Images