Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit that generates first information by applying compression processing, which uses a semantic base, to transmission data, generates reconstructed data by applying decompression processing, which uses the semantic base, to the first information, generates second information, which is the difference between the transmission data and the reconstructed data, generates a payload including the first information and the second information, and controls, on the basis of a condition, an operation of updating the semantic base and / or an operation of collecting third information for the updating; and a transmission unit that transmits the payload.

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 achieving higher data rates, lower latency, etc. (Non-Patent Document 1). Also, for the purpose of further increasing 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 (e.g., 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) 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] In future wireless communication systems (e.g., NR), it is being considered to apply a semantic base when a terminal (user terminal, User Equipment (UE)) encodes / decodes data (target signal).

[0006] However, the specific configuration and operating procedures for applying the semantic basis are not clearly defined. This may lead to a decrease in communication throughput because the payload size of transmitted / compressed data cannot be sufficiently suppressed.

[0007] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station to which a semantic basis can be appropriately applied.

[0008] A terminal according to one aspect of the present disclosure includes a control unit that generates first information by applying a compression process using a semantic basis to transmitted data, generates reconstructed data by applying a decompression process using the semantic basis to the first information, generates second information which is the difference between the transmitted data and the reconstructed data, generates a payload containing the first information and the second information, and controls at least one operation of updating the semantic basis and collecting third information for the update based on conditions, and a transmission unit that transmits the payload.

[0009] According to one aspect of this disclosure, a semantic basis can be appropriately applied.

[0010] Figure 1 shows an example of compressing a target signal transmitted by a transmitter (UE / NW). Figure 2 shows an example of reconstructing a received signal by a receiver (NW / UE). Figure 3 shows an example of a payload when using a semantic foundation. Figure 4 shows an example of updating an AI model when not using an adaptive semantic foundation. Figure 5 shows an example of updating an AI model when using an adaptive semantic foundation. Figure 6 shows an example of a UL case. Figure 7 shows an example of a DL case. Figure 8 shows an example of the timing and procedure of the semantic foundation. Figure 9 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 10 shows an example of a base station configuration according to one embodiment. Figure 11 shows an example of a user terminal configuration according to one embodiment. Figure 12 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 13 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. Furthermore, in this disclosure, estimate, predict, and infer may be interpreted interchangeably.

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

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

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

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

[0020] (Overview of the overall mechanism of the Adaptive semantic basis) Figure 1 shows an example of compressing a target signal transmitted by a transmitter (UE / NW). The following describes an example where the transmitter is a UE. The UE uses an encoder to encode the target signal (transmission data, e.g., image data, etc.) and generates tokens by applying post-processing using a semantic basis to the result.

[0021] The UE applies a proxy pre-processing (similar to the receiver's pre-processing) to the token, using a semantic basis, and then applies a proxy decoder (similar to the receiver's decoder) to the result to generate a target signal (proxy received data) reconstructed from the token. The UE generates an increment (information indicating the difference) by performing a difference operation (subtraction) between the proxy received data and the target signal (transmitted data). The UE combines the generated token and increment to generate a payload (UL signal / data), modulates that payload, and transmits it to the network.

[0022] For example, a Variational Quantize Variational Autoencoder (VQ-VAE) may be used to update / generate the semantic foundation for post-processing and [proxy] pre-processing.

[0023] The network (base station) decodes the transmitted payload as described below and reconstructs the target signal.

[0024] Figure 2 shows an example of how a receiver (NW / UE) restores / reconstructs a target signal. The following explanation describes an example where the receiver is the NW. When the UE is the transmitter, the NW demodulates the payload from the received signal and separates the payload into tokens and increments. The NW applies semantic-based preprocessing to the separated tokens and decodes the result using a decoder. The NW restores / reconstructs the target signal (the target signal reconstructed from the received data, received tokens, and increments) by adding the decoded result and the separated increments.

[0025] Furthermore, if UE corresponds to the transmitter in Figure 1, then NW (base station) corresponds to the receiver in Figure 2. If NW (base station) corresponds to the transmitter in Figure 1, then UE corresponds to the receiver in Figure 2.

[0026] Figure 3 shows an example of a payload when using a semantic foundation. A UE can reduce the signal payload by applying an appropriate semantic foundation. However, changes in the communication environment may render the semantic foundation inappropriate, potentially preventing sufficient payload reduction. In such cases, the UE can sufficiently reduce the payload by updating the semantic foundation.

[0027] For example, when inter-vendor collaboration is considered, the complexity of the frequency of encoder / decoder retraining increases. However, by using an adaptive semantic foundation (an updatable semantic foundation), the frequency of encoder / decoder retraining to adapt to new environments can be reduced.

[0028] Figure 4 shows an example of updating an AI model without using an adaptive semantic foundation. The network (base station) collects data for training the AI ​​model and updates the AI ​​model. The network transmits the updated AI model to the user interface (UE).

[0029] Figure 5 shows an example of updating an AI model using an adaptive semantic foundation. The UE / NW updates the adaptive semantic foundation / AI model based on the received data. In this case, the UE / NW does not need to collect data in advance. The UE does not need to receive the model / dataset.

[0030] (Quantization) A quantization scheme to support VQ-VAE is being considered. The learnable embedding vectors of the Autoencoder (AE) may be considered as an adaptive codebook. An adaptive semantic foundation for physical layer use cases may be an extension of VQ-VAE.

[0031] <Quantization Information> The following describes information relating to quantization and dequantization (which may be collectively referred to as quantization information or quantization-related information). In this disclosure, quantization and dequantization may be interpreted interchangeably.

[0032] The following may be assumed as quantization information: (1) Information on whether quantizer / dequantizer is supported in training (QAT / QNT support). Or information on whether quantizer / dequantizer is considered during training (QAT / QNT support). This information may include the index(s) of a model trained by QAT using the corresponding quantizer / dequantizer. (2) Information indicating whether quantizer / dequantizer is trainable (updatable during training). This information may include information on the types of trainable quantizer / dequantizer (e.g., ND layer, VQ VAE). (3) Information on how quantizer / dequantizer is constructed. This information may include constructing quantizer / dequantizer based on K-means of bit assignment, etc. (4) Information on whether quantizer / dequantizer is uniform or non-uniform. (5) Information regarding whether the number of bits after quantization is constant for all quantized bits. (6) Information regarding the resolution of uniform or non-uniform quantization. (7) Information regarding the number of units (m) before quantization or after dequantization. (8) Information regarding the number of bits (B) after quantization or before dequantization. (9) Information regarding whether the quantization / dequantization is a vector or a scalar. This information may include at least one of the following 9a-x, 9b-x. (9a-1) If the quantization / dequantization (quantization type) is a vector and the units are evenly divided across a subset, this information may include at least one of the following i to iii: (i) the number of units in the subset (m), (ii) the embedding vector (e), and (iii) the bit width (b). (9a-2) When the quantization / inverse quantization (quantization type) is a vector and the units are unevenly divided across subsets, the information may include at least one of the following i to iii: (i) the number of units in each subset (m1, m2, ..., m n(ii) Embedding vectors for each subset ({e1}, {e2}, ..., {e n}), (iii) bit width of each subset (b1, b2, ..., b n (9b-1) When quantization / inverse quantization (quantization type) is scalar uniform quantization, the bit width of each unit is (b). (9b-2) When quantization / inverse quantization (quantization type) is scalar non-uniform quantization, the sequence of bit widths of each unit is (b1, b2, ... b M ).

[0033] <Exchange of pre-processing / post-processing related information (quantization-related information) for model inference> The semantic basis may be quantization information (quantization-related information), or it may be updated based on quantization information (quantization-related information). The following describes the exchange of pre-processing / post-processing related information (quantization-related information) for model inference.

[0034] The UE may receive the quantization information described above when distributing / transferring the models of both sides. The UE may also receive the quantization information along with the AI ​​model-related information using higher-layer signaling / physical-layer signaling.

[0035] AI model-related information may include not only model-related information (model ID, model function, model input, model output, scope of application) but also quantization information (pre-processing / post-processing information).

[0036] The UE may set / reconfigure the quantization information after the model is delivered / transferred. The UE may further train / update the quantization information after the model is delivered / transferred. This allows the UE to utilize a properly quantized model.

[0037] <Exchange of pre-processing / post-processing information (quantization-related information) for model inference> This section explains the exchange of pre-processing / post-processing information (quantization-related information) for model updating.

[0038] The UE may receive the quantization information described above when the models on both sides are updated. The UE may receive the quantization information by using upper layer signaling / physical layer signaling together with the AI model related information.

[0039] In addition to the model related information described above, the AI model related information may include model parameter 1 (weight), model parameter 2 (quantization information), model structure, etc. The model related information may be called model update information.

[0040] Thereby, the exchange of preprocessing / postprocessing related information for model updates between the UE and the NW can be appropriately controlled.

[0041] (Analysis) As described above, in a future wireless communication system (e.g., NR), it has been considered to apply a semantic basis when a terminal (user terminal, User Equipment (UE)) encodes / decodes data (target signal).

[0042] However, the specific settings / operation procedures when applying the semantic basis are not clear. In this case, there is a risk that the communication throughput will decrease because the payload size of the transmitted / compressed data cannot be sufficiently suppressed.

[0043] Therefore, the inventors have conceived a method for appropriately applying the semantic basis.

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

[0045] (Various readings) In the present disclosure, the text surrounded by "()" in the text may indicate an explanation (e.g., a spelling explanation), a paraphrase, a specific example, a supplementary explanation, etc. for the immediately preceding text. Also, in the present disclosure, the text surrounded by "[]" in the text may be interpreted as the meaning of the entire text including this, or the meaning of the entire text may be interpreted without including this (ignoring this). Note that "()" and "[]" may be used for other purposes / meanings.

[0046] In the present disclosure, "A / B" and "at least one of A and B" may be read as each other. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0047] In the present disclosure, notify, activate, deactivate, instruct (or indicate), select, configure, update, determine, etc. may be read as each other. In the present disclosure, support, control, be able to control, operate, be able to operate, etc. may be read as each other.

[0048] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, upper layer parameters, fields, Information Elements (IEs), configurations, etc. may be read as each other. In the present disclosure, Medium Access Control control elements (MAC CE), update commands, activation / deactivation commands, etc. may be read as each other.

[0049] In the present disclosure, upper layer signaling may be any one of, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (such as messages from the core network, such as positioning protocol (for example, NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

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

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

[0052] In this disclosure, reconstruction, restoration, and recovery may be interpreted interchangeably. In this disclosure, semantic basis and adaptive semantic basis (updatable semantic basis) may be interpreted interchangeably.

[0053] (Wireless communication method) The semantic basis [set] may be a group / set / part of vectors / matrices / parameters / models used to represent the abstracted features of the target signal. Applying the semantic basis may mean, for example, compressing / abstracting / quantizing the target signal using vectors / matrices / models, etc.

[0054] The target signal may be a signal exchanged between nodes (NW / UE) or a signal generated by a node. The target signal may be, for example, a vector / matrix / parameter / model [group / set / part of]. The target signal may be included in PUSCH / PUCCH / PDSCH / PDCCH. The target signal may be a CSI report.

[0055] In this disclosure, the target signal to be compressed / encoded, the target signal / message / information / data to be compressed / encoded, the transmit (Tx) data, and the [UL / DL] data to be transmitted / compressed may be interpreted as each other.

[0056] In this disclosure, the target signal reconstructed [from the token, or from the token and increment] [at the transmitting / receiving side], the proxy received (Rx) data [from the token] at the transmitting side, and the received data (decoded data) [from the token and increment] at the receiving side may be interpreted as each other.

[0057] A token [payload] may represent an individual feature corresponding to a target signal / semantic basis. A token may be an index of a vector / matrix / parameter / model [group / set / part] corresponding to the semantic basis, or it may indicate the presence / validity of the semantic basis in the target signal. A token may include feature weights, including amplitude, phase, or both. Tokens may be generated by a model (AI model).

[0058] The increment [payload] may represent the difference information between the target signal [to be compressed / encoded] and the reconstructed target signal (reconstructed target signal). For example, the increment may represent the difference information between the target signal and the target signal reconstructed by the features indicated by a group of tokens (e.g., received tokens). The increment may also be a group of bits representing the difference information.

[0059] In this disclosure, payload, token and [normal transmission / additional] increment, transmitted / compressed data may be interpreted as mutually exclusive.

[0060] Collection may refer to UE behavior in logging / storing / recording / collecting information (data) about transmitted / received signals / messages / information. The UE may report this data or exchange this data with the server (e.g., non-OTA exchange) based on specifications or based on settings / instructions received [e.g., using over-the-air (OTA) signaling]. This data may be updated based on "Notification of Information to the UE" / "Notification of Information from the UE" in the "Supplement" below. On a semantic basis, the data to be collected may include at least the target signal, tokens and increments for reconstructing the target signal, and information about the tokens and increments. The data may include conditions / settings / instructions for collecting that data.

[0061] In this disclosure, the terms "transmit data," "target signal," and "data to be transmitted" may be interpreted interchangeably. In this disclosure, the terms "token," "first information," and "result obtained by applying compression (encoder and post-processing) to the transmit data" may be interpreted interchangeably. In this disclosure, the terms "reconstructed data" and "result obtained by applying decompression (pre-processing and decoder) to the token [in the transmitter / receiver]" may be interpreted interchangeably. In this disclosure, the terms "increment," "second information," "difference between the transmit data and the reconstructed data," and "result obtained by subtracting the reconstructed data from the transmit data" may be interpreted interchangeably. In this disclosure, the terms "payload," "token," and "result obtained by combining the payload" may be interpreted interchangeably. In this disclosure, the terms "received data," "result obtained by adding the reconstructed data [in the receiver] and the increment," and "reconstructed / reconstructed data / target signal" may be interpreted interchangeably.

[0062] In this disclosure, the terms [for updating the semantic basis] [collected] data / information, third information, token / [normal transmission / additional] increment / condition / setting / instruction may be interpreted as one another. In this disclosure, the terms [for updating the semantic basis] collection, logging, storage, recording, transmission, reporting, and reception may be interpreted as one another.

[0063] A metric may be an evaluation value / measurement / scale related to the quality / performance of the semantic foundation. For example, a metric may be the level / magnitude of the difference / error between the target signal and the reconstructed target signal, or a key performance indicator (KPI) between the target CSI / PMI and the reconstructed target CSI / PMI, or the Mean Square Error (MSE) / normalized mean square error (NMSE) / squared generalized cosine similarity (SGCS) / signal-to-noise ratio (SNR) / peak-signal-to-noise ratio (PSNR) of the reconstructed target signal. The reconstructed target signal may be a target signal (proxy received data) reconstructed at the transmitting side [only from the tokens to be transmitted], or a target signal (received data) reconstructed at the receiving side [from the received tokens and received increments]. The target signal reconstructed at the receiving side may include the effects of the channel state / quality between the transmitting and receiving sides.

[0064] In this disclosure, [specified / set / directed] [performance / quality] metrics, [semantic basis] quality / performance [metrics], KPI, indicator, difference, error, quantization error, MSE, NMSE, SGCS, SNR, PSNR may be interpreted as one another.

[0065] In this disclosure, the terms "target [performance] metric," "target [performance] requirement," "target value / threshold / requirement / condition / lower limit of a performance metric," and "metric being greater than or equal to the target value" may be interpreted as mutually exclusive.

[0066] In this disclosure, the terms [using a semantic basis] compression process / transmission process / first process, encoder / process including [semantic basis] post-processing may be interpreted as mutually interchangeable. In this disclosure, the terms [using a semantic basis] decompression process / reception process / second process, [semantic basis] [proxy] pre-processing / process including [proxy] decoder may be interpreted as mutually interchangeable.

[0067] In this disclosure, the terms transmitter, transmitting side, transmission process, compression process, UE, and NW / base station may be interpreted as interchangeable.

[0068] In this disclosure, receiver, receiving side, receiving process, decompression process, NW / base station, and UE may be interpreted as mutually interchangeable.

[0069] In this disclosure, NW, base station, core network (CN), and [outside / inside the CN] [over-the-top (OTT)] server may be interpreted as equivalent to each other.

[0070] <Embodiment A0> The operation when the UE acquires a semantic basis for transmission / reception will be described.

[0071] The UE may receive / generate a semantic basis (e.g., a vector / matrix / parameter / model [group / set / part of]) for transmitting / receiving the target signal.

[0072] The UE may receive vectors / matrices / parameters, each with an index assigned to it.

[0073] The UE may index each received / generated vector / matrix / parameter.

[0074] The UE may generate an index along with the received model / part of the model.

[0075] The UE may report the semantic basis and indexes used for transmission / reception (the above indexes corresponding to vectors / matrices / parameters / models [groups / sets / parts of]) using the method described below in <<Notification of Information from the UE>>.

[0076] The UE may receive a dataset that includes semantic basis.

[0077] Figure 6 shows an example of a UL case. This example corresponds to the example in Figure 1 and Embodiment A1 described later. The semantic basis may be a vector / matrix / parameter transferred / delivered to the UE, or a part of the AI / ML model for transmission (e.g., an embedded module). The UE uses the AI / ML model and the semantic basis to compress the target signal and generate the transmission signal.

[0078] Figure 7 shows an example of a DL case. This example corresponds to the example in Figure 2 and Embodiment A2 described later. The semantic basis may be a vector / matrix / parameter transferred / delivered to the UE, or a part of the receiving AI / ML model (e.g., an embedded module). The UE uses the AI / ML model and the semantic basis to reconstruct the received signal and generate a reconstructed target signal.

[0079] <Embodiment A1> In this embodiment, the transmitter shown in Figures 1 and 6 corresponds to the UL case where the UE is the UE. The UE encodes the generated or received target signal, generates tokens by applying semantic-based post-processing to the encoded signal, generates a reconstructed target signal by applying semantic-based pre-processing to the tokens and decoding them, and generates information (increment) indicating the difference between the target signal and the reconstructed target signal. The UE transmits the generated tokens and increment to the NW.

[0080] [First Embodiment] The UE may generate / transmit an index / token corresponding to the target signal based on the received / generated semantic basis (e.g., a vector / matrix / parameter / model [group / set / part of]).

[0081] The UE may reconstruct the target signal using the generated (transmitted) index / token (proxy received data). The UE may generate / transmit a signal / bit (i.e., an increment signal) representing the difference between the target signal and the target signal reconstructed by the UE.

[0082] The UE may determine the amount of tokens and the number of signals / bits used for increment transmission depending on one or a combination of the following: • The value / maximum specified / set / instructed by the method of <<Notification of Information to the UE>> described below. • The level / magnitude of the difference between the target signal and the reconstructed target signal. • Available transmission resources (resource range). • The performance of the target reconstruction specified / set / instructed by the method of <<Notification of Information to the UE>> described below. For example, if the reconstruction performance is below a threshold, the UE may increase the number of signals / bits used for increment transmission. • The type / data amount of the target signal. For example, the more data the target signal has, the more tokens and the number of signals / bits used for increment transmission may be increased.

[0083] The UE may specify / configure / instruct, using the <<Notification of Information to the UE>>, to send either a token or an increment, or both. The UE may decide, for example, whether to send a token or an increment, or both, depending on the type of target signal.

[0084] The UE may specify / configure / instruct a channel or data portion within a channel for transmitting tokens or increments, or both, using the method of <<Notification of Information to the UE>>. Tokens / increments may be transmitted together within the same channel or within the same data portion within the same channel. The UE may transmit tokens / increments in different channels or in different data portions within channels.

[0085] The UE may, for example, send the token / increment to the NW using the method of <<Notification of Information from the UE>> described below. The UE may, for example, send the token / increment in PUCCH / PUSCH.

[0086] [Second Embodiment] The case in which the target signal (transmitted signal) in Figures 1 and 6 is part or all of the CSI report will be described. This embodiment may be combined with at least a part of the first embodiment.

[0087] The UE may send indices / tokens based on (applying the semantic basis to) the received or generated semantic basis corresponding to the CSI / PMI report, if a specific CSI type / codebook type is configured or activated.

[0088] The UE may reconstruct the target CSI / PMI using the generated (transmitted) index / token (proxy received data). The UE may generate / transmit a signal / bit (i.e., an increment signal) representing the difference between the target signal (CSI / PMI) and the target signal (CSI / PMI) reconstructed by the UE. The UE may generate / quantize the difference (increment) based on a codebook (e.g., an NR extended type II codebook).

[0089] The UE may determine the amount of tokens and the number of signals / bits to use for increment transmission depending on one or a combination of the following: • The value / maximum specified / set / instructed by the method of <<Notification of Information to the UE>> described below. • The level / magnitude of the difference between the target signal and the reconstructed target signal. For example, if the KPI between the target CSI / PMI and the reconstructed target CSI / PMI (e.g., the UE may use more bits if the KPI is below a threshold, compared to if it is above a threshold.) • Available transmission resources. For example, the resources for the PUSCH / PUCCH CSI report or the remaining resources. • The performance of the target reconstruction specified / set / instructed by the method of <<Notification of Information to the UE>> described below. For example, an incremented target KPI (e.g., squared generalized cosine similarity (SGCS), Normalized Mean Square Error (NMSE)) added to the reconstruction target CSI / PMI. For example, if the reconstruction performance is below a threshold, the UE may increase the number of signals / bits used for increment transmission compared to when it is above the threshold.

[0090] For example, if the target signal is PMI, Spatial Domain (SD) / Frequency Domain (FD) / Time Domain (TD) basis (vectors / matrices) may be used as the semantic basis. The selected SD / FD / TD basis may be tokens. Increment may be considered an error caused by the unselected portion.

[0091] According to this embodiment, the UE can suppress signaling overhead by transmitting tokens and increments based on the target signal. Furthermore, by using an updatable semantic foundation (adaptive semantic foundation), the frequency of retraining the encoder / decoder to adapt to new environments can be reduced.

[0092] <Embodiment A2> The receiver shown in Figures 2 and 7 corresponds to the DL case where the UE is the UE.

[0093] The UE may reconstruct the target signal based on the received signal (token / increment) transmitted from the NW. Tokens and groups of tokens may be interchangeable. The received tokens and increments are described in detail below.

[0094] [Tokens] The UE may receive groups of tokens. The number of tokens to receive may be specified / set / notified by the method of <<Notification of Information to the UE>> described below. The UE may assume that the received tokens correspond to the received semantic basis (e.g., vectors / matrices / parameters / models [groups / sets / parts]) and apply the tokens to the semantic basis. Models / parts of models may be defined in the specification or specified / set / indicated by the method of <<Notification of Information to the UE>> described below.

[0095] [Increment] The UE may receive differential information (increment) corresponding to the received token [group]. The UE may assume that the number of bits indicating the increment is the value specified / set / instructed using <<Notification of Information to the UE>>. The UE may assume that the number of bits indicating the increment is the number of bits remaining after subtracting the bits used in the token from the total number of bits.

[0096] The UE may receive the amount of tokens and the number of signals / bits to be used for increment transmission, determined by the method of the first / second embodiment of Embodiment A1. Alternatively, the UE may determine the amount of tokens and the number of signals / bits to be used for increment transmission using the method of the first / second embodiment of Embodiment A1.

[0097] According to this embodiment, the UE can suppress signaling overhead by receiving and reconstructing tokens and increments based on the target signal.

[0098] <Embodiment B1> This embodiment relates to the initiation and termination of data collection / semantic infrastructure updates.

[0099] Figure 8 shows an example of the timing and procedure for semantic infrastructure updates. The semantic infrastructure during the period up to timing T1 may be an appropriate semantic infrastructure. The payload during that period may be a normal [transmit / receive] payload. A normal transmit / receive payload may include a token and an increment for normal transmit / receive (normal [transmit / receive] increment). At timing T1, a decrease in performance using the normal transmit / receive payload may be detected. The semantic infrastructure during the period from timing T1 to timing T2 may be an inappropriate semantic infrastructure. During that period, the payload may increase due to an increase in additional increments for target signal recovery / restoration. At timing T2, data acquisition / semantic infrastructure updates may be triggered / started. The semantic infrastructure may be updated during the period from timing T2 to timing T3. Compression performance may be lower (payload size may be larger) during the period from timing T2 to timing T3. By timing T3, data acquisition / semantic infrastructure updates may be stopped, additional increments may no longer be needed, and the payload size may be equal to the normal transmit / receive payload size. At timing T3, the updated semantic foundation may be deployed / applied. The semantic foundation for the period from timing T3 onward may be a new and appropriate semantic foundation. Compression performance may be improved (payload size may be reduced) during the period from timing T3 onward.

[0100] In this disclosure, the terms "normal [transmit / receive] payload size" and "normal / stable / high-compression / minimum payload size" may be interpreted interchangeably. In this disclosure, the terms "normal [transmit / receive] increment size" and "normal / stable / high-compression / minimum increment size" may be interpreted interchangeably.

[0101] When starting or stopping data collection / semantic infrastructure updates, the UE may operate based on at least one of the following multiple behaviors 1-x:

[0102] <<Behavior 1-1>> Start of Data Collection The UE may start data collection [for semantic foundation updating] based on specified / set / instructed conditions (it may determine the timing of the start of data collection, or determine timing T1). The conditions may be based on at least one of the following features:

[0103] ◆Features: The condition may be based on a specified / configured / instructed metric. The condition may include at least one of several examples below: —◆Example: The size / amount of the payload (or additional increment payload) required to fully recover / restore the target signal using the current semantic basis is greater than the threshold. —◆Example: [In the receiver / transmitter,] the MSE / SGCS / SNR / PSNR of the target signal reconstructed by a given (specific) size / amount payload is less than the threshold.

[0104] ◆Features: The conditions may be [specified / set / instructed] periodic (P) / semi-persistent (SP) / aperiodic (AP) [triggering / time-domain behavior] timings. The UE may start data collection at that timing.

[0105] <<Behavior 1-2>> Stopping Data Collection The UE may stop data collection [for semantic infrastructure updates] based on specified / configured / instructed conditions (it may determine the timing of stopping data collection, or determine timing T3). The conditions may be based on at least one of the following features:

[0106] ◆Features: The condition may be based on a specified / configured / instructed metric. The condition may include at least one of several examples below: —◆Example: The size / amount of the payload (or additional increment payload) required to fully recover / restore the target signal using the updated semantic basis is less than a threshold. —◆Example: [In the receiver / transmitter,] the MSE / SGCS / SNR / PSNR of the target signal reconstructed by a given (specific) size / amount payload is greater than a threshold.

[0107] <<Behavior 1-3>> Stopping Data Collection After data collection [for semantic infrastructure updates] has started, the UE may stop the data collection if a condition is met (it may determine the timing of stopping data collection, or it may determine timing T3). That condition may be that a specified / set / instructed period / time has elapsed since the start of data collection.

[0108] <<Behavior 1-4>> Initiation of semantic foundation update When the conditions are met, the UE may update the semantic foundation using the collected data (it may initiate a semantic foundation update or determine timing T2). The update may be based on at least one of the following methods:

[0109] ◆Method: The condition may be that the collected data has been reported. After the collected data has been reported, the UE may update the semantic basis using the collected data. The UE may update the semantic basis using only the reported data. It may be necessary for both the NW and the UE to update the semantic basis simultaneously. The UE may report the collected data [to the NW].

[0110] ◆Method: The condition may also be that a setting / instruction for semantic infrastructure update has been received. Based on the received setting / instruction, the UE may update the semantic infrastructure using the collected data.

[0111] ◆Method: The conditions may be P / SP / AP timing [triggering / time-domain behavior]. The UE may update the semantic basis [using the collected data] at [specified / configured / instructed] P / SP / AP timing [triggering / time-domain behavior].

[0112] <<Behavior 1-5>> Evaluation of Semantic Foundation The UE may evaluate specified / configured / instructed metrics relating to the quality of the semantic foundation when the conditions are met (and may determine the timing of the evaluation [start] of the semantic foundation). The conditions may be that the semantic foundation has been updated using [collected] data of specified / configured / instructed quantities / sizes. After the semantic foundation has been updated using [collected] data of specified / configured / instructed quantities / sizes, the UE may evaluate specified / configured / instructed metrics relating to the quality of the semantic foundation. Based on the evaluated metrics, the UE may determine the conditions for behaviors 1-1 / 1-2 / 1-6.

[0113] <<Behavior 1-6>> Stopping semantic base updates The UE may stop updating the semantic base (and may determine timing T3) if one or more of the following conditions (AND / OR) are met.

[0114] ◆Condition: Data collection has been stopped.

[0115] ◆Condition: Metrics related to the quality of the semantic foundation meet the specified / set / directed target requirements.

[0116] ◆Condition: The specified / set / instructed period / time has elapsed.

[0117] ◆Condition: The semantic basis has been updated using the [Collected] data of the specified / set / instructed quantity / size.

[0118] <<Behavior 1-7>> Synchronization of semantic foundation updates To synchronize updates on both the NW and UE, the UE may perform at least one of the following actions:

[0119] ◆Operation: The UE may report / transmit the start / stop [timing] [and the collected data used for the update] of semantic infrastructure updates via the signaling described in "Supplement <<Notification of Information from the UE>>" below.

[0120] ◆Operation: The UE may receive the start / stop of semantic infrastructure updates [the timing of these updates] [and instructions regarding which data will be used for the updates] via the signaling described in "Supplement <<Notification of Information to the UE>>" below.

[0121] According to Embodiment B1, the UE / NW can start / stop data collection / semantic infrastructure updates at appropriate times. By updating the semantic infrastructure at appropriate times, the increase in payload size can be suppressed.

[0122] <Embodiment B2> Regarding data / information (collected data) collected for updating the semantic basis.

[0123] To update the semantic foundation, the UE may operate based on at least one of the following multiple behaviors 2-x:

[0124] <<Behavior 2-1>> After data collection has started, the UE may collect / report at least one of the following pieces of information x.

[0125] ◆Information 1: Target signal / message / information.

[0126] ◆Information 2: Payload (sent token and sent increment). The sent increment may be a send / receive increment or an append increment.

[0127] ◆Information 3: An increment that can fully recover / restore the target signal [to the target metric] [used / sent with the transmitted token]. This increment may be an additional increment, a normal transmit / receive increment and an additional increment (when compression performance is low), a normal transmit / receive increment (when compression performance is high), or an additional increment / normal transmit / receive increment from the start to the end of data collection. This increment may be different from the increment transmitted [with the token]. The target metric may be a target value for the metric.

[0128] <<Behavior 2-2>> Reception of collected data The UE may receive at least one of the aforementioned information x for data collection. The data may be distributed / transmitted to the UE from the NW or an OTT server [on the NW side, or on the UE side, or outside the CN].

[0129] According to Embodiment B2, the UE / NW can collect appropriate data for updating the semantic foundation. By updating the semantic foundation with appropriate data, the increase in payload size can be suppressed.

[0130] <Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (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.

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

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

[0133] Furthermore, notification of any information to the UE in the above-described embodiment may be periodic, semi-persistent (triggered by instructions from the UE or gNB), or aperiodic (triggered by instructions from the UE or gNB).

[0134] In the embodiments described above, the UE may receive information from the NW as at least one of the following QCL rules: • QCL type A. • QCL type B. • QCL type C. • QCL type D.

[0135] In the embodiments described above, the QCL source RS for each QCL type may be at least one of the following RSs: • SSB; • CSI-RS with / without repetition; • TRS; • DMRS for PDCCH / PDSCH.

[0136] In the embodiments described above, information from the network may be set / instructed by the following methods: - Common to multiple UEs, or individual to a UE. - Cell-specific, or common to multiple cells. - Per UE / Per CC / Per BWP / Per band / Per cell / Per cell group (CG).

[0137] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (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.

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

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

[0140] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent (triggered by instructions from the UE or gNB), or aperiodic (triggered by instructions from the UE or gNB).

[0141] <<Regarding the application of each embodiment>> In UE / BS, a specific (one or more) process / operation / control / assumption / information / model 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 / model is set; - The specific process / operation / control / assumption / information / model is determined based on the relevant higher-layer parameter; - The specific process / operation / control / assumption / information / model 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 / model is reported or supported; - The application of the specific process / operation / control / assumption / information / model is determined based on specific conditions.

[0142] The above-mentioned specific UE capability may represent at least one of the following: supporting the above-mentioned specific processing / operation / control / assumption / information / model / embodiment / [UE]behavior; supporting a semantic foundation / adaptive semantic foundation; supporting the generation of tokens / increments using a semantic foundation; and supporting the reconstruction of a target signal based on tokens / increments generated using a semantic foundation.

[0143] In this disclosure, "to support" and "whether or not to support" may be interpreted interchangeably.

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

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

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

[0147] (Note) The following inventions are added with respect to one embodiment of the present disclosure (particularly embodiment Bx). <Note 1> A terminal having: a control unit that generates first information (e.g., tokens) by applying a compression process using a semantic basis (e.g., encoder and post-processing) to transmitted data; generates reconstructed data by applying a decompression process using the semantic basis to the first information; generates second information (e.g., increment) which is the difference between the transmitted data and the reconstructed data; generates a payload containing the first information and the second information; and controls at least one operation of updating the semantic basis and collecting third information (e.g., collected data) for the update based on conditions [in embodiment B1]; and a transmission unit that transmits the payload [modulated]. <Note 2> The terminal according to Note 1, wherein the operation is at least one of starting the collection, stopping the collection, starting the update, stopping the update, and evaluating the semantic basis. <Note 3> The terminal according to Note 1 or Note 2, wherein the control unit controls the reporting or reception of at least one of the timing of the operation (e.g., timing T1 / T2 / T3) and the third information. <Note 4> The terminal according to any one of Notes 1 to 3, wherein the third information is at least one of the transmission data, the payload, and the second information. <Supplement> The terminal in Notes 1 to 4 may be a user terminal 20. The receiving / transmitting unit in Notes 1 to 4 may be a transmitting / receiving unit 220. The control unit in Notes 1 to 4 may be a control unit 210. <Note A> A base station having a receiving unit that receives [and demodulates] a payload including the first information and the second information, and a control unit that generates reconstructed data by applying an extension process using a semantic basis to the first information, generates received data by adding the second information and the second reconstructed data, and controls at least one operation of updating the semantic basis and collecting the third information for the update based on conditions. <Supplement> The base station in Appendix A may be base station 10. The receiving / transmitting unit in Appendix A may be transmitting / receiving unit 120. The control unit in Appendix A may be control unit 110.

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

[0149] Figure 9 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0176] (Base Station) Figure 10 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0195] (User Terminal) Figure 11 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0213] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0214] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0215] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 12 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0216] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0217] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0249] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0250] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the 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.

[0251] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

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

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

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

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

[0256] 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 notifying the specified information or by notifying other information).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0302] 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.”

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

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

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

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

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

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

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

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

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

Claims

1. A terminal having a control unit that generates first information by applying a compression process using a semantic basis to transmitted data, generates reconstructed data by applying a decompression process using the semantic basis to the first information, generates second information which is the difference between the transmitted data and the reconstructed data, generates a payload containing the first information and the second information, and controls at least one operation of updating the semantic basis and collecting third information for the update based on conditions, and a transmission unit that transmits the payload.

2. The terminal according to claim 1, wherein the operation is at least one of: starting the collection, stopping the collection, starting the update, stopping the update, and evaluating the semantic basis.

3. The terminal according to claim 1, wherein the control unit controls the timing of the operation and the reporting or reception of at least one of the third information.

4. The terminal according to claim 1, wherein the third information is at least one of the transmission data, the payload, and the second information.

5. A wireless communication method for a terminal, comprising the steps of: generating first information by applying a first process using a semantic basis to transmitted data; generating reconstructed data by applying a second process using the semantic basis to the first information; generating second information which is the difference between the transmitted data and the reconstructed data; generating a payload containing the first information and the second information; and controlling at least one operation of updating the semantic basis and collecting third information for the update based on conditions; and transmitting the payload.

6. A base station having a receiving unit that receives a payload including first information and second information, and a control unit that generates reconstructed data by applying an extension process using a semantic basis to the first information, generates received data by adding the second information and the second reconstructed data, and controls at least one operation of updating the semantic basis and collecting third information for the update based on conditions.

Images