Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives physical layer signaling for scheduling transmission or reception of data to which an encoding process based on an artificial intelligence model is applied; and a control unit that performs control to implement transmission or reception of the data on the basis of the physical layer signaling. According to an aspect of the present disclosure, a suitable multiple access scheme can be implemented.

Description

Terminal, Wireless Communication Method, and Base Station

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

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

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

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

[0005] In NR, devices such as a terminal (terminal, user terminal, User Equipment (UE)), a base station, etc. perform physical layer processing to transmit signals.

[0006] Meanwhile, regarding future wireless communication technologies, the use of artificial intelligence (AI) technologies such as machine learning (ML) for network / device control and management is being considered. For example, multiple access methods for multiple data / UEs using AI technology are being explored.

[0007] However, how to implement the above-mentioned multiple access method has not yet been thoroughly considered. Without clearly defining these aspects, it may be impossible to implement suitable signal multiplexing, potentially hindering improvements in resource utilization efficiency, communication throughput, and communication quality.

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station capable of implementing a suitable multiple access scheme.

[0009] A terminal according to one aspect of this disclosure includes a receiving unit that receives physical layer signaling for scheduling the transmission or reception of data to which encoding processing based on an artificial intelligence model is applied, and a control unit that performs control to carry out the transmission or reception of the data based on the physical layer signaling.

[0010] According to one aspect of this disclosure, a suitable multiple access scheme can be implemented.

[0011] Figure 1 shows an example of the physical layer processing procedure for downlink transmission in the existing 3GPP NR standard. Figure 2 shows an example of MDMA. Figure 3 shows an example of eMDMA configuration 1 according to Embodiment 1.1. Figure 4 shows an example of eMDMA configuration 2 according to Embodiment 1.1. Figure 5 shows an example of separate L1 signaling for different UE / data schedules according to the third embodiment. Figure 6 shows an example of common L1 signaling and dedicated L1 signaling for different UE / data schedules according to the fourth embodiment. Figure 7 shows an example of operation 1 according to the fourth embodiment. Figure 8 shows an example of operation 2 according to the fourth embodiment. Figure 9 shows an example of common L1 signaling for different UE / data schedules according to the fifth embodiment. Figure 10 shows an example of the first format of hybrid DCI according to the fifth embodiment. Figure 11 shows an example of the second format of hybrid DCI according to the fifth embodiment. Figures 12A and 12B show an example of a third format of hybrid DCI according to a fifth embodiment. Figure 13 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 14 shows an example of a base station configuration according to one embodiment. Figure 15 shows an example of a user terminal configuration according to one embodiment. Figure 16 shows an example of a hardware configuration of a base station and user terminal according to one embodiment. Figure 17 shows an example of a vehicle according to one embodiment.

[0012] (Signal processing of the physical layer in the existing 3GPP NR standard) First, we will outline the signal processing of the physical layer in the existing 3GPP NR standard. In the following explanation of the signal processing order, the words enclosed in "()" indicate the content of the signal processing, the words before the "=" indicate the input, and the words after the "=>" indicate the output.

[0013] In this disclosure, bits, symbols, etc. may be interpreted as equivalent to blocks of bits, symbols, etc. In this disclosure, streams, sequences, blocks, sets, signals, etc. may be interpreted as equivalent to equivalent to each other.

[0014] Figure 1 shows an example of the physical layer processing procedure for downlink transmission in the existing 3GPP NR standard. As shown in Figure 1, when transmitting user data downlink (DL), the transmitting side (e.g., base station) proceeds with the following processing in order: Data = (channel coding) => channel-coded bit sequence = (interleaving) => bits = (scrambling) => scrambled bits = (modulation) => complex value modulation symbol = (layer mapping) => complex value symbol per layer = (precoding) => = complex value symbol per port = (resource mapping) => complex value per port and resource element = (orthogonal frequency division multiplexing (OFDM) signal generation) => time-continuous signal per port.

[0015] The transmitting side transmits a time-continuous signal for each port. The receiving side obtains the transmitted user data by sequentially performing the reverse processing of the corresponding processing performed by the transmitting side on the received signal. Here, the processes of channel decoding, deinterleaving, descrambling, demodulation, layer demapping, detection, resource demapping, and OFDM signal reception may correspond to the reverse processing of channel coding, interleaving, scrambling, modulation, layer mapping, precoding, resource mapping, and OFDM signal generation, respectively.

[0016] In this disclosure, bits, symbols, and the like may be interpreted as equivalent to blocks of bits, symbols, and the like.

[0017] In this disclosure, layer mapping may be interpreted as mapping from a codeword (CW) to a layer. Also, in this disclosure, layer demapping may be interpreted as demapping from a layer to a CW.

[0018] In this disclosure, precoding may be interpreted as antenna port mapping, and detection may be interpreted as antenna port demapping.

[0019] The data input to channel coding is also called the input bit sequence. This data may correspond to a transport block transmitted from a higher layer (for example, the Medium Access Control (MAC) layer). Before channel coding, the input bit sequence may be subjected to cyclic redundancy check (CRC) bits (also called parity bits) and code block segmentation.

[0020] Interleaving may be included in rate matching. Rate matching may include bit selection, rate matching, etc. In this disclosure, interleaving (deinterleaving) may be read interchangeably with rate matching (derate matching). Code block concatenation may be applied to interleaved bits.

[0021] A complex-valued modulation symbol is generated by a modulation mapper based on the bits contained in a block of bits. For example, in Quadrature Phase-Shift Keying (QPSK), the bit pairs b(2i) and b(2i+1) are mapped to the complex-valued modulation symbol d(i) according to d(i) = 1 / √2 * {(1 - 2b(2i)) + j(1 - 2b(2i+1))}.

[0022] A complex-valued symbol may be output after one or more signal processing operations are performed on a complex-valued modulated symbol, or it may correspond to a complex-valued modulated symbol. For example, in the case of the Physical Downlink Control Channel (PDCCH) / Physical Broadcast Channel (PBCH) described later, the above complex-valued modulated symbol is mapped to a physical resource as a complex-valued symbol.

[0023] In this disclosure, complex-valued symbols may be interpreted as complex-valued symbols for each port / layer, complex-valued symbols for a specific port / layer, etc. Also, in this disclosure, complex-valued symbols, complex-valued modulated symbols, complex values, etc. may be interpreted as interchangeable.

[0024] Regarding the physical layer processing related to the Physical Downlink Shared Channel (PDSCH) shown in Figure 1, the UE assumes the following: - Blocks of bits in the codeword q transmitted on the physical channel are scrambled before modulation to become scrambled bits; - For each codeword q, the blocks of scrambled bits are modulated using one of the modulation schemes to become blocks of complex-valued modulation symbols; - The complex-valued modulation symbols for each transmitted codeword are mapped to one or more layers; - Blocks of vectors of complex-valued symbols for each layer are mapped to the antenna ports corresponding to each layer to become blocks of vectors of complex-valued symbols for each antenna port; - For each antenna port used for transmission on the physical channel, the blocks of complex-valued symbols are sequentially mapped to resource elements in the virtual resource block assigned for transmission; - The virtual resource block is mapped to the physical resource block according to the specified mapping scheme (non-interleaved mapping or interleaved mapping).

[0025] The physical layer processing procedure for uplink (UL) transmission in the existing 3GPP NR standard is almost the same as that shown in Figure 1. For example, the difference from Figure 1 for Physical Uplink Shared Channel (PUSCH) transmission is that transform precoding may be performed before precoding.

[0026] In the case of a Physical Uplink Control Channel (PUCCH), signal processing for the PUCCH format, including modulation, basically proceeds in the following order: Block of bits = (scrambled) => Scrambled bits = (modulation) => Complex-valued modulation symbol = [(block-wise spread)] => Complex-valued symbol = (transform precoding) => Complex-valued symbol.

[0027] In the case of PUCCH format 1, the process ends with modulation, and the complex-valued modulation symbols are mapped to physical resources. Also, block-wise spreading is not applied in PUCCH format 3, but it is applied in PUCCH format 4. Block-wise spreading may also be interpreted as Frequency Domain Orthogonal Cover Code (FD-OCC).

[0028] In the case of PDCCH / PBCH, signal processing basically proceeds in the following order: bit block = (scrambled) => scrambled bits = (modulation) => complex value modulated symbol.

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

[0030] For example, UEs / 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).

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

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

[0033] In this disclosure, estimation, prediction, and inference may be interpreted interchangeably. Furthermore, in this disclosure, estimate, predict, and infer may be interpreted interchangeably.

[0034] In this disclosure, an object may be, for example, a device or apparatus such as a UE or BS. Furthermore, in this disclosure, an object may refer to a program / model / entity operating on such apparatus.

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

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

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

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

[0039] Furthermore, a one-sided model may refer to either the UE-side model or the network-side model. A two-sided model may refer to a pair of AI models in which joint inference is performed. Here, joint inference may include AI inference in which the inference is performed jointly across the UE and the network, for example, the first part of the inference may be performed first by the UE and the rest by the gNB (or vice versa).

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

[0041] (Model Division Multiple Access (MDMA)) For future wireless communication technologies (e.g., 3GPP Rels 19, 20, 21), AI technology is being explored to effectively multiplex signals. When multiple UEs / base stations transmit and receive signals using AI-based multiplexing, this may be called Model Division Multiple Access (MDMA).

[0042] Figure 2 shows an example of MDMA. In Figure 2, the transmitter encodes two signals (signal 1 and signal 2) using model encoders (model 1 encoder and model 2 encoder), multiplexes them (or superimposes them), and transmits them. Superimposed transmission may also mean simultaneous transmission over the same or partially overlapping resources.

[0043] The receiving side decodes (or demultiplexes) the received signal using model decoders (Model 1 decoder, Model 2 decoder) corresponding to the model encoder described above, and obtains the original signals (Signal 1, Signal 2) respectively.

[0044] The model encoder may correspond to a module that extracts and outputs, from an input signal, for example, important features (which may also be referred to as hidden layer parameters, feature quantities, latent variables, etc.). The model decoder may apply the reverse process of the model encoder (for example, detect the above important features from the input and reproduce the original signal). The model encoder / decoder may be realized by, for example, an autoencoder based on a convolutional neural network (CNN), or may be a deep learning-based model, or may be realized by any other encoder / decoder.

[0045] Note that the model 1 encoder and the model 2 encoder may be the same encoder (for example, the same model using different parameters), or may be different encoders. Also, the model 1 decoder and the model 2 decoder may be the same decoder (for example, the same model using different parameters), or may be different decoders.

[0046] The inventors are considering a method that extends MDMA (which may also be referred to as Enhanced MDMA (eMDMA)). MDMA / eMDMA may be called a multiple access method that uses a model (a two-sided model) for both the transmission side and the reception side. By adopting MDMA / eMDMA, improvement in the utilization efficiency of radio resources / communication throughput, improvement in communication quality, etc. are expected.

[0047] However, there has not yet been an in-depth study on how to implement eMDMA. If these are not clearly defined, a suitable multiplexing cannot be carried out, and there is a risk that improvements in resource utilization efficiency, communication throughput, communication quality, etc. will be suppressed.

[0048] Therefore, the inventors have conceived a suitable implementation method of eMDMA in the physical layer. In one aspect of the present disclosure, eMDMA does not necessarily have to use an AI model (it may be based on calculations, functions, databases, etc. other than the AI model).

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

[0050] In the following embodiments, the processing of the transmitting [e]MDMA module may be called [model] multiplexing. The processing of the receiving [e]MDMA module may be called [model] inverse multiplexing. These processes may be called eMDMA processing. The processing of the receiving [e]MDMA module may be called the inverse processing of the processing of the transmitting [e]MDMA module.

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

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

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

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

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

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

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

[0058] In this disclosure, “functionality” may mean a set of parameters / features supported based on conditions specified by UE capability (e.g., a set of parameters for eMDMA, CSI prediction, beam prediction, CSI compression, etc.).

[0059] In this disclosure, "model identifier (ID)" may mean an ID associated with a functionality / additional condition (or the model corresponding to that ID). Note that the model ID may be interpreted as an AI ID, dataset ID, pairing ID, etc.

[0060] In this disclosure, the terms "feature" and "functionality" may be interpreted as "feature," "function," or "functionality."

[0061] In this disclosure, the terms model, function, functionality, model ID, function ID, functionality ID, etc., may be interpreted interchangeably.

[0062] In the following embodiments, modules may be interpreted interchangeably with processes, processing units, models, etc. Also, in the following embodiments, eMDMA may be interpreted interchangeably with eMDMA modules and MDMA[module].

[0063] In this disclosure, the terms "transmitting side," "transmitter side," and "transmitter" may be interpreted interchangeably. In this disclosure, the terms "receiving side," "receiver side," and "receiver" may be interpreted interchangeably.

[0064] In this disclosure, terms such as process, procedure, and operation may be interpreted interchangeably.

[0065] In this disclosure, “multiplex” may mean multiplexing on a specific channel.

[0066] In this disclosure, terms such as signal, data, data layer, data portion (data part), value, bit [stream], etc., may be interpreted interchangeably. Also, in this disclosure, terms such as signal, signal stream, signal source, etc., may be interpreted interchangeably.

[0067] In this disclosure, eMDMA-based transmission, eMDMA-based data transmission, transmission or reception of data to which encoding processing based on an artificial intelligence model is applied, etc., may be interpreted interchangeably.

[0068] (Wireless communication method) <First embodiment> The first embodiment relates to the configuration of eMDMA.

[0069] The various pieces of information regarding the eMDMA configuration / model shown below (e.g., which configuration to use, input parameters for the data model encoder, etc.) may be associated with the eMDMA model, determined based on UE capabilities, or set for the UE [by System Information / DCI / MAC CE / RRC].

[0070] <<Embodiment 1.1>> Embodiment 1.1 relates to the components of eMDMA.

[0071] eMDMA may consist of one or more component models. Component models may also be called components, elements, etc. For example, eMDMA may include one or more of the following component models: (1) a model for signal / data processing (may be called a data model), (2) a model for scrambled code processing (may be called a code model), and (3) a model for signal / data processing and scrambled code processing (may be called a combined [component] model).

[0072] A data model may also be a model for encoding or decoding data.

[0073] The code model may be a model for scrambling or descrambling, or a model for outputting scrambled codes. The scrambled codes may be codes that facilitate easier separation of each UE / BS signal at the receiving end. In this disclosure, codes may be randomly generated codes, orthogonal codes, pseudo-orthogonal codes, non-orthogonal codes, network-learned codes, or any other codes.

[0074] A combined model may also refer to a model for encoding (decoding) and scrambling (descrambling) operations on data.

[0075] When eMDMA is applied to DL transmission, the transmitting side may be BS and the receiving side may be UE. When eMDMA is applied to UL transmission, the transmitting side may be UE and the receiving side may be BS.

[0076] The data model included in the transmitting eMDMA may be called a data model encoder, and the data model included in the receiving eMDMA may be called a data model decoder.

[0077] The code model included in the transmitting eMDMA may be called a code model encoder, and the code model included in the receiving eMDMA may be called a code model decoder. Furthermore, the same code model may be included in both the transmitting and receiving eMDMAs, or different code models may be included in each. The input / output elements of the code model encoder and code model decoder may differ. For example, the input of the code model encoder may include SINR, while the input of the code model decoder may not.

[0078] The processing of a code model encoder may be called code [model] encoding, and the processing of a code model decoder may be called code [model] decoding. The output of a code model encoder may include scrambled code, which may be called [code model] encoded scrambled code. The output of a code model decoder may include [de]scrambled code, which may be called [code model] decoded [de]scrambled code. In this disclosure, [code model] encoded [de]scrambled code, [code model] decoded scrambled code, [code model] processed [de]scrambled code, [de]scrambled code output from a code model, etc., may be read interchangeably.

[0079] A model for signal / data processing and scrambling code processing may be a model that combines (or integrates) a model for signal / data processing and a model for scrambling code processing. A combined model for signal / data processing and scrambling code processing included in the transmitting eMDMA may be called a model encoder, and a combined model for signal / data processing and scrambling code processing included in the receiving eMDMA may be called a model decoder.

[0080] Each model (e.g., a data model and a code model) may be associated with one another. Examples of associations between models include: • A data model encoder and a data model decoder are associated; • A code model and a data model encoder are associated (in this case, both may be used on one side, e.g., the transmitter); • A code model and a data model decoder are associated (in this case, both may be used on one side, e.g., the receiver); • A code model, a data model encoder, and a data model decoder are associated (in this case, all of these may be used for encoding and decoding the same signal / data; the code model and data model encoder may be used on one side, e.g., the transmitter, and the code model and data model decoder may be used on the other side, e.g., the receiver); • A model encoder and a model decoder are associated (in this case, all of these may be used for encoding and decoding the same signal / data; the model encoder may be used on one side, e.g., the transmitter, and the model decoder may be used on the other side, e.g., the receiver).

[0081] The eMDMA based on (1) and (2) above may be called configuration 1. The eMDMA based on (3) above may be called configuration 2.

[0082] Figure 3 shows an example of configuration 1 of eMDMA according to Embodiment 1.1. The left side of the figure corresponds to the transmitter's eMDMA, and the right side corresponds to the receiver's eMDMA. In this example, the transmitter applies eMDMA-based multiplexing to two data (data #1 and #2) and transmits them, and the receiver applies eMDMA-based demultiplexing to the received signal to reconstruct the two data. The two data may be processed in the same device or in different devices.

[0083] In the transmitter, the data model encoder may perform preferred encoding processing on the input data for eMDMA-based multiplexing. The code model encoder may output a scrambled code based on input parameters. These input parameters may include values ​​related to code generation (index), the code (e.g., the base scrambled code), parameters for the model encoder / decoder / code model [or AI model of the code] (e.g., information for input preprocessing, information for output postprocessing, functionality labels, model ID, etc.), and information regarding the communication status (e.g., Signal to Interference plus Noise Ratio (SINR) for the signal from the transmitter to the receiver).

[0084] In the transmitter, a combination operation may be applied to the output of the data model encoder and the output of the code model encoder. A multiplexing procedure (Σ in the figure) may be applied to the outputs of multiple combination operations. In this disclosure, terms such as combination, synthesis, and combination may be interpreted interchangeably.

[0085] In the receiver, a demultiplexing procedure (Σ in the diagram) may be applied to the received signal to separate it into individual streams. The separated streams may be combined with the output of a code model decoder by a coupling operation and input to a data model decoder. The data model decoder may then reconstruct (decode) the transmitted data.

[0086] Figure 4 shows an example of configuration 2 of the eMDMA according to Embodiment 1.1. Figure 4 differs from Figure 3 in that the code model encoder, data model encoder, and coupling operation in the transmitter are replaced with a model encoder, and the code model decoder, data model decoder, and coupling operation in the receiver are replaced with a model decoder.

[0087] In the transmitter, a multiplexing procedure (Σ in the diagram) may be applied to the outputs of multiple model encoders. In the receiver, a demultiplexing procedure (Σ in the diagram) may be applied to the received signal to separate it into individual streams. The separated streams may be input to a model decoder. The model decoder may reconstruct (decode) the transmitted data.

[0088] In Embodiment 1.1, each component model may be located before or after a certain process in the physical layer signal / bitstream processing procedure (for example, between one process and another). Here, "process" may be any process corresponding to each physical layer process used in existing 3GPP NR standards, as shown in Figure 1, and may also include processes in future wireless communication standards (the process names may differ from those in Figure 1).

[0089] Each component model may occupy a different position in the processing steps of the physical layer. In other words, an eMDMA module may be a separate eMDMA module.

[0090] Furthermore, each component model in Embodiment 1.1 may additionally include one or more (e.g., all) processes in the physical layer signal / bitstream processing procedure.

[0091] For example, the component model [in the transmitter] may include channel coding / interleaving / scrambling / modulation / layer mapping / precoding / resource mapping / OFDM signal generation functions [in addition to the eMDMA functions].

[0092] The component model [in the receiver] may include the functions of channel decoding / deinterleaving / descrambling / demodulation / layer demapping / detection / resource demapping / OFDM signal reception [in addition to the eMDMA functions].

[0093] According to Embodiment 1.1 described above, the components of eMDMA can be appropriately determined.

[0094] <<Embodiment 1.2>> Embodiment 1.2 relates to a procedure for processing eMDMA.

[0095] eMDMA may include one or more of the following processing steps: - A coupling operation at the transmitting end of the outputs from a data model encoder and a code model encoder [of one UE]; - A coupling operation at the receiving end of the demultiplexed data and the output from the code model decoder; - A multiplexing procedure at the transmitting end or in the air to multiplex the outputs of multiple coupling operations or multiple model encoders; - A demultiplexing procedure at the receiving end to demultiplex the received multiplexed data into multiple data streams.

[0096] The concatenation operation at the transmitting end may correspond to scrambling the encoded data. The concatenation operation at the receiving end may correspond to descrambling the demultiplexed data.

[0097] Furthermore, the above multiplexing procedure may be performed by the transmitting side (gNB side) for DL. Also, the above multiplexing procedure may be performed in the air for UL. For example, in UL, multiple UEs may individually transmit [unmultiplexed] eMDMA processed signals, and the network (gNB) may simultaneously receive a mixed signal from the multiple UEs. In this case, the mixed signal corresponds to a signal obtained by [one device] processing and multiplexing each data from the multiple UEs using eMDMA. In other words, the outputs of each eMDMA module of the multiple UEs are [pseudo] superimposed on the radio channel.

[0098] According to Embodiment 1.2 described above, the processing procedure for eMDMA can be appropriately determined.

[0099] <<Embodiment 1.3>> Embodiment 1.3 relates to a model of eMDMA (for example, each [component] model described in the first embodiment).

[0100] The eMDMA model may have one of the following features that take into account the operation of a single or multiple UEs: • Each UE has a UE-specific model; • Multiple UEs have a UE-common model.

[0101] For example, a UE may have its own data model encoder / data model decoder / code model. A UE may also have its own model encoder / model decoder.

[0102] A UE-common model may be used, for example, in the following ways: • The transmitter has a UE-specific data model encoder, and the receiver has a UE-common data model decoder; • The transmitter has a UE-common data model encoder, and the receiver has a UE-specific data model decoder; • The transmitter has a UE-common data model encoder, and the receiver has a UE-common data model decoder; • The transmitter and receiver have a UE-common code model; • The transmitter has a UE-common model encoder, and the receiver has a UE-common model decoder.

[0103] For UE-specific / UE-common models, a single UE may be configured with one or more models, including data model encoders, data model decoders, code models, model encoders, and model decoders. For example, a UE may be configured with A (A is an integer, e.g., 2) data model encoders, B (B is an integer, e.g., 3) data model decoders, and C (C is an integer, e.g., 4) code models. A UE may also be configured with D (D is an integer, e.g., 2) model encoders and E (E is an integer, e.g., 3) model decoders.

[0104] eMDMA may multiplex data from / to multiple UEs, or it may multiplex different data from / to the same / different UEs.

[0105] For example, the eMDMA shown in Figures 3 and 4 may multiplex data from / to different UEs (e.g., data #1 from UE #1, data #2 from UE #2). Alternatively, the eMDMA shown in Figures 3 and 4 may multiplex different data from / to the same UE (e.g., data #1 is data part #1 from UE #1, data #2 is data part #2 from UE #1).

[0106] Furthermore, eMDMA may multiplex data from / to different UEs and data from / to the same UE. For example, in the case of the eMDMA shown in Figures 3 and 4, where data #3 (not shown) is also multiplexed with data #1 and #2, data #1 may be data from UE #1, data #2 may be data part #1 from UE #2, and data #3 may be data part #3 from UE #2.

[0107] According to Embodiment 1.3 described above, it is possible to appropriately determine whether eMDMA uses UE-specific / common models, what kind of multiplexing is used for one or more UEs, and so on.

[0108] <<Embodiment 1.4>> Embodiment 1.4 relates to the input / output of eMDMA models / processing procedures.

[0109] The inputs / outputs of the eMDMA model (for example, each component model described in Embodiments 1.1 / 1.3), the eMDMA processing procedure (for example, see Embodiment 1.2), etc., may include (or conform to) a specific data format.

[0110] The particular format may include at least one of the following: • Input / output data size (e.g., size for pre-processing / post-processing), • Value type (e.g., immutable value, floating-point number, integer value, bit value, complex number), • Bit width of each value (e.g., 1 bit, 16 bits, 64 bits for each input value), • Quantization interval (e.g., 64 levels of quantization for each value on the image), • Range of possible values ​​for each value (e.g., [0, 255], [0, 1.0]).

[0111] Regarding the eMDMA model, eMDMA processing procedure, etc., the input / output may include pre-processing / post-processing. Such pre-processing / post-processing may include at least one of specific processes (e.g., normalization (z-score normalization, min-max normalization, etc.), one-hot encoding).

[0112] The preprocessing / postprocessing [input / output] may include at least one of the following parameters: whether to apply a specific process (e.g., normalization / one-hot encoding), which process (e.g., which normalization) to apply, parameters for the specific process (e.g., mean and variance for z-score normalization, minimum and maximum for min-max normalization), a rule for selecting whether to use it as training data, a rule for selecting whether to use it [as training data / as input / as output / during execution].

[0113] Here, the selection rules may include rules for excluding (ignoring, discarding, or not using as input / output) values ​​that meet or do not meet specific conditions (e.g., values ​​below a threshold, outliers, etc.).

[0114] The information regarding the specific data format [contents] and pre-processing / post-processing [contents, parameters, etc.] used in the eMDMA model / processing procedure may be associated with the eMDMA model, determined based on UE capabilities, or set for the UE.

[0115] According to Embodiment 1.4 described above, the input and output of the eMDMA model / processing procedure can be appropriately determined.

[0116] <<Embodiment 1.5>> Embodiment 1.5 relates to the use of eMDMA for multi-hop communication.

[0117] The eMDMA in this disclosure may be used for single-hop communication or for multi-hop communication. Single-hop communication may include, for example, direct communication such as UE-BS or UE-UE. Multi-hop communication may include communication via multiple devices, for example, UE-BS (or UE) communication via repeaters, relay nodes, Integrated Access Backhaul (IAB) nodes, other UEs, etc.

[0118] For example, with respect to UL's eMDMA, an intermediate node (e.g., a relay node) may receive signals from multiple UEs that are [not multiplexed] eMDMA processed signals, and the intermediate node may perform eMDMA processing on the signals received from the multiple UEs and then transmit them.

[0119] Regarding DL / UL eMDMA, the code model at the intermediate node and the code model at the final receiving node may be the same or different. For example, the transmitter may use one or more code models to output a first scramble code and a second scramble code, and use these scramble codes in the concatenation operation. The intermediate node may receive the signal transmitted from the transmitter using eMDMA and transmit a signal that has been de-scrambled by one stage using one of the first and second scramble codes. The final receiving node may receive the signal that has been de-scrambled by one stage and decode the data from the signal that has been completely de-scrambled using the other of the first and second scramble codes.

[0120] According to Embodiment 1.5 described above, eMDMA can be appropriately used for multi-hop communication.

[0121] According to the first embodiment described above, the configuration of eMDMA can be appropriately determined, and communication based on eMDMA can be suitably utilized.

[0122] <Second Embodiment> The second embodiment relates to physical layer (which may also be called Layer 1 (L1), PHY layer, etc.) signaling for eMDMA-based transmission. In the second embodiment, the UE may be the sender or receiver of the eMDMA-based data transmission.

[0123] The second embodiment serves as an introduction to the subsequent descriptions of the third to fifth embodiments. Any L1 signaling for eMDMA-based transmission in the subsequent embodiments may be, for example, DCI, and may include at least one of the following: a field indicating at least one eMDMA parameter, and a field indicating at least one parameter other than an eMDMA parameter (e.g., a data transmission-related parameter).

[0124] Any parameters included in the L1 signaling for eMDMA-based transmission may be called L1 scheduling parameters.

[0125] In this disclosure, eMDMA parameters may include at least one of the following: information indicating a model for eMDMA (for example, which may be called model specification information, model indicator, etc.); a scramble code [set] associated with the specified model; information indicating a join operation (for example, which may be called join operation specification information, join operation indicator, etc.) / parameters for a join operation; information indicating a multiplexing operation (for example, which may be called multiplexing operation specification information, multiplexing operation indicator, etc.) / parameters for a multiplexing operation; and other information / parameters relating to an eMDMA operation.

[0126] The join operation indicator may indicate which join operation to use, or it may indicate the parameters for the join operation. The join operation may be selected from one-to-one multiplication (each output value is derived from the multiplication of one first input value and one second input value), one-to-one weighting (each output value is derived from a weight function that considers one first input value and one second input value), many-to-one weighting (each output value is derived from a weight function that considers multiple first input values ​​and multiple second input values), etc.

[0127] For example, a join operation indicator may indicate one or more of the following: • How the output is generated (e.g., one-to-one multiplication, one-to-one weighting, many-to-one weighting); • An approach to considering the order of corresponding outputs (in other words, the order of inputs to the join operation) (e.g., which input values ​​to use when there are no corresponding values ​​in the inputs, such as when the input data sizes are different, or whether to use a specific value (e.g., 0)); • Whether or not pre-processing is performed using an AI model; • Which AI model is used as the pre-processing or AI model for the join operation; • The data size of each input; • The data size of the output.

[0128] The multiplexing operation indicator may indicate which multiplexing operation to use, or it may indicate the parameters for the multiplexing operation. Note that if the UE is the receiving side, multiplexing in this embodiment may be interpreted interchangeably with demultiplexing. Multiplexing operations may be performed using parameters such as the start position / end position / length of each input, or they may be performed using multiplexing groups (multiplexing group(s)). Each multiplexing group may occupy the same or different lengths of the output of the multiplexing operation (input in the case of demultiplexing), and may correspond to a set of data to which several inputs (outputs in the case of demultiplexing) are distributed.

[0129] For example, a multiplexing operation indicator may indicate one or more of the following: • How the output is generated (e.g., whether to use the input start position / end position / length for multiplexing, or whether to use multiplexing groups), • Whether or not pre-processing is performed [using an AI model], • Which AI model is used as the AI ​​model for pre-processing or the join operation, • The data size of each input, • The data size of the output, • The start position / end position / length mentioned above, the total number of [UEs / data / joining operations / model encoders / model decoders] within a single multiplexing group, etc.

[0130] Other information / parameters relating to the eMDMA operation may include, for example, information regarding the location of the eMDMA operation, information indicating that the eMDMA operation is a submodule of another operation (module), or information indicating that the eMDMA operation includes some or all of the existing modules of a protocol (e.g., a physical layer protocol).

[0131] In this disclosure, data transmission-related parameters may include, for example, at least one of the following: information on the modulation and coding scheme (MCS); information on the antenna port (e.g., whether eMDMA multiplexing is performed in its MIMO layer); and information on resource allocation (e.g., information on time / frequency resources for eMDMA transmission).

[0132] According to the second embodiment described above, the settings / instructions regarding the L1 scheduling parameter for eMDMA-based data transmission can be suitably utilized.

[0133] <Third Embodiment> The third embodiment relates to L1 signaling for eMDMA-based transmission. In the third embodiment, the UE may be the sender or receiver of the eMDMA-based data transmission.

[0134] In a third embodiment, different (dedicated) L1 signaling may be used for different UE / data schedules. In this disclosure, dedicated, individual, separate, etc., may be interpreted interchangeably.

[0135] The L1 signaling in the third embodiment may be a DCI that schedules eMDMA-based transmissions. The format of the DCI may be the same as or different from the format of the DCI that schedules non-eMDMA-based transmissions.

[0136] Figure 5 shows an example of separate L1 signaling for different UE / data schedules according to the third embodiment. In this example, DCI #1 for UE / data #1, DCI #2 for UE / data #2, and DCI #3 for UE / data #3 are shown. UE / data #1-#3 may correspond to sets of UE / data that are multiplexed by eMDMA. The format of each DCI may be the same or different.

[0137] Note that this example merely illustrates the configuration of the DCI and does not necessarily show the spatial relationships of the DCI resources. In other words, although the DCIs are aligned in Figure 5, this does not mean that their resources (e.g., time / frequency resources) are the same (although they may be the same). Please note that the same applies to subsequent figures.

[0138] The hatched areas in Figure 5 indicate information common to (the same as) DCI #1, #2, and #3. Thus, DCI #1, #2, and #3 may contain common (the same) information; for example, the fields indicating eMDMA parameters included in these DCIs may have the same value. Alternatively, DCI #1, #2, and #3 may contain individual (different) information. Note that one or more (for example, all) of DCI #1, #2, and #3 do not necessarily contain common information.

[0139] The DCI that schedules the above eMDMA-based transmission may be transmitted in the UE-specific search space or in the [UE / Cell] common search space.

[0140] The UE may set a Radio Network Temporary Identifier (RNTI) for detecting DCIs that schedule the eMDMA-based transmissions. The RNTI may be used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCIs. The RNTI may be the same as or different from the RNTI for DCIs that schedule non-eMDMA-based transmissions. The RNTI may be a cell RNTI (C-RNTI) or an RNTI for eMDMA (e.g., eMDMA-RNTI).

[0141] To schedule eMDMA-based transmissions of different data from the same UE, multiple RNTIs for eMDMA-based transmissions may be assigned to a single UE (hereinafter referred to as Assignment 1). For Assignment 1, the UE may assume at least one of the following: - There may be one or more DCIs for scheduling eMDMA-based transmissions, each having a CRC scrambled by the assigned RNTI, in one monitoring opportunity for scheduling eMDMA-based data transmissions; - The multiple DCIs in one monitoring opportunity have CRCs scrambled by the same / different RNTIs.

[0142] To schedule eMDMA-based transmissions of different data from the same UE, one RNTI for eMDMA-based transmissions may be assigned to a single UE (hereinafter referred to as Assignment 2). For Assignment 2, the UE may assume the following: There may be more than one DCI for scheduling eMDMA-based transmissions, each having a CRC scrambled by the same RNTI, in one monitoring opportunity for scheduling eMDMA-based data transmissions.

[0143] The UE may assume allocation 1, allocation 2, or both. Information regarding allocations 1 and 2 being used may be notified to the UE.

[0144] With respect to allocation 1 / 2, one or more of the above RNTIs may be set for the UE [by System Information / DCI / MAC CE / RRC]. One or more of the above RNTIs may be set / determined in the initial access procedure.

[0145] Furthermore, the number of DCIs [having CRCs scrambled by the same or different RNTIs] for scheduling eMDMA-based transmissions to be monitored by the UE in a single monitoring opportunity may be set for the UE [by System Information / DCI / MAC CE / RRC].

[0146] According to the third embodiment described above, different UE / data schedules for eMDMA can be suitably controlled using separate L1 signaling.

[0147] <Fourth Embodiment> The fourth embodiment relates to L1 signaling for eMDMA-based transmission. In the fourth embodiment, the UE may be the sender or receiver of the eMDMA-based data transmission.

[0148] In the fourth embodiment, multiple L1 signalings may be used for different UE / data schedules. These multiple L1 signalings may include a first L1 signaling common to multiple UE / data and a second L1 signaling specific to each UE / data. Hereinafter, "multiple" in this embodiment may be read as "all".

[0149] In the fourth embodiment, the first / second L1 signaling may be a DCI that schedules eMDMA-based transmission. Hereinafter, the first L1 signaling, which is a DCI, will also be referred to as the common DCI, and the second L1 signaling, which is a DCI, will also be referred to as the dedicated DCI.

[0150] The format of a common DCI may be the same as or different from the format of a dedicated DCI. Furthermore, the format of a common DCI / dedicated DCI may be the same as or different from the format of a DCI that schedules non-eMDMA-based transmissions.

[0151] A common DCI may transmit common parameters across different UEs / data for eMDMA-based transmission. A dedicated DCI may transmit dedicated parameters for a single UE / data for eMDMA-based transmission.

[0152] The parameters transmitted by the common DCI / dedicated DCI may include at least one of the following: eMDMA parameters, data transmission-related parameters, and common DCI / dedicated DCI configuration-related parameters.

[0153] Common DCI / dedicated DCI configuration-related parameters may include parameters for receiving current / past (e.g., recent) / future (e.g., next) common / dedicated DCI / DCI (e.g., time / frequency resources, aggregation level, etc.).

[0154] Figure 6 shows an example of common and dedicated L1 signaling for different UE / data schedules according to the fourth embodiment. In this example, a common DCI #0 for all UE / data, a dedicated DCI #1 for UE / data #1, a dedicated DCI #2 for UE / data #2, and a dedicated DCI #3 for UE / data #3 are shown. UE / data #1-#3 may correspond to sets of UE / data that are multiplexed by eMDMA.

[0155] Common DCI / dedicated DCI may be transmitted in the UE-specific search space or in the [UE / Cell] common search space.

[0156] The UE may set an RNTI for detecting the common DCI / dedicated DCI. The RNTI may be used to scramble the CRC bits assigned to the common DCI / dedicated DCI. At least one of the RNTIs may be a cell RNTI (C-RNTI) or an RNTI for eMDMA (e.g., eMDMA-RNTI).

[0157] For example, a UE may set at least one of the following: a group-common RNTI for detecting common DCIs, a [cell / UE]-common RNTI, and a UE-specific RNTI. A UE may also set a UE-specific RNTI for detecting dedicated DCIs.

[0158] At least one of these RNTIs may be the same as or different from the RNTI for DCIs that schedule non-eMDMA-based transmissions. Similarly, the RNTI for a common DCI may be the same as or different from the RNTI for a dedicated DCI.

[0159] The UE of the fourth embodiment may follow at least one of the following operations 1 and 2.

[0160] Operation 1 is as follows: - The UE attempts to detect the common DCI. - If the UE successfully detects the common DCI, it attempts to blindly detect (or blindly decode) the dedicated DCI. - If the UE successfully detects the dedicated DCI, it transmits or receives eMDMA-based transmissions according to the scheduling indicated by the common DCI / dedicated DCI. - If the UE does not detect the dedicated DCI, it does not transmit or receive eMDMA-based transmissions. - If the UE does not detect the common DCI, it does not transmit or receive eMDMA-based transmissions.

[0161] Operation 2 is as follows: - The UE attempts to detect the common DCI. - If the UE successfully detects the common DCI, and the common DCI indicates that the UE is scheduled, it attempts to blindly detect the dedicated DCI. - If the UE successfully detects the dedicated DCI, it sends or receives eMDMA-based transmissions according to the scheduling indicated by the common DCI / dedicated DCI. - If the UE does not detect the dedicated DCI, it does not send or receive eMDMA-based transmissions. - If the UE does not detect the common DCI or does not detect a common DCI indicating that the UE is scheduled, it does not send or receive eMDMA-based transmissions.

[0162] To schedule eMDMA-based transmissions of different data from the same UE, multiple RNTIs for eMDMA-based transmissions may be assigned to a single UE. A UE may assume at least one of the following: - There may be more than one common DCI / dedicated DCI with CRCs scrambled by the assigned RNTIs in one monitoring opportunity for scheduling eMDMA-based data transmissions; - Multiple common DCI / dedicated DCIs in one monitoring opportunity have CRCs scrambled by the same / different RNTIs.

[0163] One or more RNTIs for a common DCI / dedicated DCI may be set for the UE [by System Information / DCI / MAC CE / RRC]. The one or more RNTIs may be set / determined during the initial access procedure.

[0164] Furthermore, the number of common DCIs / dedicated DCIs that a UE monitors in a single monitoring opportunity [having CRCs scrambled by the same or different RNTIs] may be set for the UE [by System Information / DCI / MAC CE / RRC].

[0165] The common DCI for operation 1 described above does not have to include information for indicating whether a UE is scheduled for eMDMA-based transmission (which may be called scheduled UE instruction information, or simply UE instruction information). The common DCI for operation 2 described above includes one or more UE instruction pieces.

[0166] The portion (field, part) other than the UE instruction information transmitted by the common DCI may be called the first part, part A, etc. Part A may include at least one of the following: eMDMA parameters, data transmission-related parameters, common DCI / dedicated DCI setting-related parameters, etc. The portion (field, part) of the UE instruction information transmitted by the common DCI may be called the second part, part B, etc.

[0167] UE instruction information may indicate an ID assigned to the scheduled UE (which may also be called a UE assignment ID, or simply an assignment ID). The assignment ID may be derived based on at least one of the following: RNTI [for dedicated DCI], any value [assigned by cell / network], or any identifier for identifying the UE (which may also be called a UE ID). The UE ID may be, for example, a Subscription Permanent Identifier (SUPI).

[0168] The assignment ID is, for example, assignment ID = mod(RNTI, 2 Ｎ ) may be determined by the following: where N may correspond to the bit size of the assigned ID, may be a predetermined fixed value, may be associated with the eMDMA model, may be determined based on UE capabilities, or may be set for the UE.

[0169] In this disclosure, mod(a, b) may represent the modulo function (a function that finds the remainder when a is divided by b).

[0170] UE instruction information may include a bitmap (which may also be called a scheduling bitmap, scheduling bitmap, etc.) indicating whether one or more UEs are scheduled. Each bit (or field) in the bitmap may indicate whether one or more UEs are scheduled. At least one of the following pieces of information may be set for the UE [by System Information / DCI / MAC CE / RRC]: • The [start] position of the field [for the UE], • The size of the field [for the UE] (the value of N above), • The index of the field [for the UE], • Information about the UE associated with a field (e.g., the assignment ID, RNTI, UE ID, etc.).

[0171] The number of UE instruction pieces included in the common DCI may be a predetermined fixed value, may be associated with the eMDMA model, may be determined based on UE capability, or may be set for the UE. The number of UE instruction pieces included in the common DCI may be less than or equal to a certain number (e.g., K). This K may be determined based on the payload size of the common DCI and the N described above.

[0172] The payload size of a common DCI / dedicated DCI may be a predetermined fixed value, may be associated with the eMDMA model, may be determined based on UE capabilities, or may be set for the UE.

[0173] A single assignment ID or field may be associated with one or more UEs. If an assignment ID is included in a common DCI, it may be assumed that the UEs associated with that assignment ID are scheduled.

[0174] Additionally, a field may indicate whether the UE associated with that field is scheduled or not. If the size of a field is 1 bit, for example, a value of "0" may indicate that the associated UE is not scheduled, and a value of "1" may indicate that the associated UE is scheduled.

[0175] If the size of a field is multi-bit, for example, one value (e.g., "0") may indicate that none of the associated UEs are scheduled, another value may indicate that one of the associated UEs is scheduled (e.g., "1" indicates that the first associated UE is scheduled, and value "2" indicates that the second associated UE is scheduled), and yet another value may indicate that more than one of the associated UEs is scheduled (e.g., value "5" indicates that the first, second, and third associated UEs are scheduled).

[0176] In addition, in the above operations 1 / 2, a UE that successfully detects a common DCI may attempt blind detection of a dedicated DCI after receiving / detecting the common DCI until certain conditions are met. After these conditions are met, the UE may return to the attempt to detect the common DCI.

[0177] The above conditions may be either or a combination thereof: - A period of time specified by a pre-configured / common DCI has elapsed; - The detection of a number of dedicated DCIs [for the device] specified by a pre-configured / common DCI has been completed.

[0178] The passage of the above-mentioned period may be interpreted as the expiration of the timer for that period.

[0179] The condition that the above number of dedicated DCIs have been detected is suitable, for example, when a receiver (UE / gNB) receives multiple data sets to be eMDMA multiplexed for its own device. When the condition that the above number of dedicated DCIs have been detected is used, each dedicated DCI may include at least one field indicating the number (total number) of eMDMA-multiplexed data [for its own device], a field indicating the number of eMDMA-multiplexed data [for its own device], and so on. Based on these fields, the UE may attempt to receive dedicated DCIs until all of the dedicated DCIs to be received have been received.

[0180] The above-mentioned common DCI / dedicated DCI setting parameters may include parameters related to the timer length, parameters related to the number (total number) of dedicated DCIs [for the device itself], and so on.

[0181] Figure 7 shows an example of operation 1 according to the fourth embodiment. In this example, in step 1, the UE detects a common DCI. The common DCI is a DCI common to all UEs / data and includes part A which indicates common parameters (e.g., eMDMA parameters).

[0182] In step 2, a UE that detects a common DCI performs a blind detection of its dedicated DCI. In this example, different DCIs #1, #2, and #3 are sent to UEs / data #1, #2, and #3, respectively. A UE that detects a common DCI can obtain a dedicated DCI that schedules data for itself or its UE.

[0183] Figure 8 shows an example of operation 2 according to the fourth embodiment. In this example, in step 1, the UE detects a common DCI. The common DCI is a DCI common to all UEs / data and includes part A, which shows common parameters (e.g., eMDMA parameters), and part B, which shows UE instruction information.

[0184] In step 2, a UE that detects a common DCI determines whether the common DCI indicates that its own UE will be scheduled. For example, part B on the left shows an example including assignment IDs, indicating that four UEs, IDs #1, #6, #10, and #5, will be scheduled. Part B on the right shows an example including a bitmap. Each bit in this bitmap is associated with one or more UEs, and in this example, the second bit from the left indicates that IDs #7 / #2, the fifth bit from the left indicates that ID #9, and the sixth bit from the left indicates that ID #12, for a total of four (or three) UEs, will be scheduled.

[0185] In step 3, a UE that has detected a common DCI and is indicated to be scheduled by the common DCI performs a blind detection of its dedicated DCI. Figure 8 shows an example of the dedicated DCI in step 3 when the bitmap shown in step 2 is shown.

[0186] According to the fourth embodiment described above, different UE / data schedules for eMDMA can be suitably controlled using a common L1 signaling and a dedicated L1 signaling.

[0187] <Fifth Embodiment> The fifth embodiment relates to L1 signaling for eMDMA-based transmission. In the fifth embodiment, the UE may be the sender or receiver of the eMDMA-based data transmission.

[0188] In the fifth embodiment, a common L1 signaling may be used for all scheduled UE / data. This L1 signaling may include a first field (which may be called a common field) that is common to multiple UE / data, and a second field (which may be called a dedicated field) that is specific to each UE / data. Hereinafter, "multiple" may be read as "all".

[0189] Each UE / data schedule may use two fields in the common L1 signaling (a common field and a dedicated field).

[0190] In the fifth embodiment, the L1 signaling may be a DCI that schedules eMDMA-based transmissions. Hereinafter, the above L1 signaling, which is a DCI, will also be referred to as a hybrid DCI. This is because a hybrid DCI includes a part common to both UE and data (common fields) and a part specific to each UE and data (dedicated fields).

[0191] The format of a hybrid DCI may be the same as or different from the format of a DCI that schedules non-eMDMA-based transmissions.

[0192] Figure 9 shows an example of common L1 signaling for different UE / data schedules according to the fifth embodiment. In this example, a hybrid DCI is shown that includes a common field (Common) for all UE / data, a field for UE / data #1 (Part #1), a field for UE / data #2 (Part #2), and a field for UE / data #3 (Part #3). UE / data #1–#3 may correspond to sets of UE / data that are multiplexed by eMDMA.

[0193] Hybrid DCI may be transmitted in a UE-specific search space or in a [UE / Cell] common search space.

[0194] The UE may set an RNTI for detecting the hybrid DCI. The RNTI may be used to scramble the CRC bits assigned to the hybrid DCI. The RNTI may be a cell RNTI (C-RNTI) or an RNTI for eMDMA (e.g., eMDMA-RNTI).

[0195] For example, a UE may have at least one of the following set of identifiers for detecting hybrid DCI: a group-common RNTI, a [cell / UE]-common RNTI, and a UE-specific RNTI.

[0196] At least one of these RNTIs may be the same as or different from the RNTI for DCIs that schedule non-eMDMA-based transmissions.

[0197] The following describes an example of the hybrid DCI format. The common fields of the hybrid DCI include at least one of Part A (the part other than the UE instruction information) and Part B (the part containing the UE instruction information), as also shown in the fourth embodiment.

[0198] <<First Format for Hybrid DCI>> The common fields in the first format include Part A but do not include Part B. The dedicated fields in the first format may include dedicated subfields for each UE / data. In this disclosure, subfields, fields, bit blocks, etc., may be interpreted as interchangeable.

[0199] The dedicated subfield for each UE in the first format may be included regardless of whether the UE is scheduled or not. In this case, the DCI payload size can be fixed, thereby suppressing decoding errors caused by fluctuations in payload size.

[0200] At least one of the following pieces of information relating to the first format may be set for the UE by System Information / DCI / MAC CE / RRC: - the starting position of the dedicated subfield for the UE, - the size (N) of the dedicated subfield for the UE, - the index of the dedicated subfield for the UE, and - information about the UE associated with a particular dedicated subfield (e.g., the assignment ID shown in the fourth embodiment, the RNTI for hybrid DCI, the UE ID, etc.).

[0201] The number of dedicated subfields included in the first format may be a predetermined fixed value, may be associated with the eMDMA model, may be determined based on UE capabilities, or may be set for the UE. The number of dedicated subfields included in the first format may be less than or equal to a certain number (e.g., K). This K may be determined based on the payload size of the hybrid DCI and the above-mentioned N. N may be a predetermined fixed value, may be associated with the eMDMA model, may be determined based on UE capabilities, or may be set for the UE.

[0202] The payload size of the hybrid DCI may be a predetermined fixed value, may be associated with the eMDMA model, may be determined based on UE capabilities, or may be set for the UE.

[0203] A single dedicated subfield may be associated with one or more UEs.

[0204] A dedicated subfield may indicate whether the UE associated with that dedicated subfield is scheduled or not. If the size of a dedicated subfield is 1 bit, for example, a value of "0" may indicate that the associated UE is not scheduled, and a value of "1" may indicate that the associated UE is scheduled.

[0205] If a specific value is indicated by a dedicated subfield, it may indicate that the associated UE will be scheduled; otherwise, it may indicate that the associated UE will not be scheduled.

[0206] Figure 10 shows an example of a first format for a hybrid DCI according to a fifth embodiment. The DCI in this example includes a common field containing Part A and dedicated fields for each UE / data (here, UE#1 to UE#N). In this example, UE#1 and UE#3 are not scheduled, so the dedicated subfields corresponding to these UEs indicate that the associated UEs are not scheduled.

[0207] <<Second Format for Hybrid DCI>> The common fields in the second format include Part A but do not include Part B. The dedicated fields in the second format may include dedicated subfields for each scheduled UE / data.

[0208] The dedicated subfield for each UE in the second format may be omitted if the UE is not scheduled. The number of UEs / data scheduled by the second format may be a predetermined fixed value, may be associated with the eMDMA model, may be determined based on UE capabilities, or may be set for each UE.

[0209] Regarding the second format, unless otherwise specified, it may be the same as the first format.

[0210] A dedicated subfield may indicate an assignment ID as described in the fourth embodiment. A UE may determine that it is scheduled if one or more dedicated subfields in the dedicated field of the second format indicate an assignment ID corresponding to it. The dedicated subfield following (or preceding) the dedicated subfield indicating the assignment ID may be assumed to be the dedicated subfield for the UE / data corresponding to that assignment ID.

[0211] The number of UEs / data actually scheduled by a hybrid DCI may be less than the number of UEs / data that are configured (or predefined). In this case, at least one dedicated subfield indicating the assignment ID may indicate a specific value (e.g., all 0s) that does not indicate the UEs to be scheduled. This way, the payload size of the hybrid DCI can be fixed even if the number of UEs / data actually scheduled is small.

[0212] Figure 11 shows an example of a second format for a hybrid DCI according to a fifth embodiment. The DCI in this example includes a common field containing Part A and dedicated fields for each UE / data (here, four UEs: UE#1, #6, #10, and #5). The DCI includes dedicated subfields indicating the assigned IDs (ID#1, #6, #10, and #5) corresponding to UE#1, #6, #10, and #5.

[0213] <<Third Format for Hybrid DCI>> The common fields in the third format include Part B (Part A may or may not be included). The dedicated fields in the third format may include dedicated subfields for each scheduled UE / data.

[0214] Regarding the third format, unless otherwise specified, it may be the same as the second format.

[0215] If part B of the common field includes a subfield indicating an assignment ID, the UE may determine the order of the dedicated subfields in the dedicated field [corresponding to the UE / data] according to the order of the subfields in part B. For example, if the assignment ID corresponding to the UE is indicated by the nth (where n is an integer) subfield in part B of the common field, the UE may use the nth dedicated subfield in the dedicated field as the subfield corresponding to the UE for sending and receiving.

[0216] If part B of the common field includes a bitmap indicating whether one or more UEs are scheduled, the UE may determine the order of the dedicated subfields in the dedicated field [corresponding to the UE / data] according to the order of the schedule-indicating bits in the bitmap. For example, if the scheduling of its own UE is indicated by the nth (where n is an integer) schedule-indicating bit of the bitmap in part B of the common field, the UE may use the nth dedicated subfield in the dedicated field as the subfield corresponding to its own UE for sending and receiving.

[0217] Figures 12A and 12B show an example of a third format for a hybrid DCI according to the fifth embodiment. The DCI in this example includes a common field containing Part A and Part B, and dedicated fields for each UE / data.

[0218] Figure 12A shows a case where part B of the common field includes a subfield indicating the assignment ID. In this example, part B includes a subfield indicating the assignment IDs (ID #1, #6, #10, and #5) corresponding to UE #1, #6, #10, and #5. The DCI in Figure 12A includes dedicated subfields corresponding to UE #1, #6, #10, and #5.

[0219] Figure 12B shows a case where part B of the common field includes a subfield indicating the presence or absence of scheduling bitmaps. In this example, part B includes a subfield indicating bitmaps where the bit values ​​associated with UE#7, #9, and #12 are 1. In other words, the first scheduled [UE] field is associated with UE#7, the second scheduled [UE] field is associated with UE#9, and the third scheduled [UE] field is associated with UE#12. The dedicated subfields included in the DCI in Figure 12B correspond to the first, second, and third scheduled [UE] fields mentioned above, and correspond to the dedicated subfields for UE#7, #9, and #12, respectively.

[0220] Furthermore, the DCI in Figure 12B may include dedicated subfields for unscheduled UEs, for example, the dedicated subfields corresponding to unscheduled UEs #1, #4, #5, #8, and #6 may all be filled with a specific value (e.g., all 0) (they may be zero-padding).

[0221] According to the fifth embodiment described above, different UE / data schedules for eMDMA can be suitably controlled using common L1 signaling, including common fields and dedicated fields.

[0222] <Other Embodiments> In each embodiment, the transmitting side (receiving side) may transmit to the receiving side (transmitting side) information indicating the eMDMA module [or model for it] to be used for a certain channel. The receiving side (transmitting side) may use the eMDMA module [or model for it] indicated by the information to perform physical layer processing for the channel.

[0223] In each embodiment, when an eMDMA-related functionality / model is activated / notified / applied / configured / specified to a UE [for a certain channel], the UE may apply eMDMA processing [for that channel] (for example, it may perform eMDMA processing in the transmitter / receiver), or it may assume that such eMDMA processing is applied (for example, it may assume that eMDMA processing is applied in the transmitter / receiver).

[0224] Furthermore, if the UE or BS applies eMDMA processing (or assumes that eMDMA processing is applied by the communication partner), it may perform corresponding transmission / reception processing (e.g., modulation, demodulation, mapping, demapping, etc.) that takes into account the application of eMDMA processing.

[0225] Furthermore, eMDMA processing may be applied to at least one of the specific channels (e.g., PUSCH, PUCCH, PDSCH, PDCCH, PBCH). Alternatively, eMDMA processing common to multiple channels may be applied.

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

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

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

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

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

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

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

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

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

[0235] The above-mentioned specific UE capabilities may represent at least one of the following: supporting the above-mentioned specific processing / operation / control / assumment / information; supporting eMDMA processing [and corresponding models]; supporting configuration 1 / 2; supporting [separate / common / dedicated / hybrid] L1 signaling for eMDMA-based transmission; and supporting the first / second / third formats of hybrid L1 signaling for eMDMA-based transmission.

[0236] 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), a capability per feature set (FS) or feature set per component-carrier (FSPC), or a capability per functionality / model.

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

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

[0239] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having: a receiving unit that receives physical layer signaling (e.g., DCI) for scheduling the transmission or reception (e.g., UL transmission or DL ​​reception) of data to which encoding processing (e.g., eMDMA operation) based on an artificial intelligence model (e.g., AI model) is applied; and a control unit that performs control to perform the transmission or reception of the data based on the physical layer signaling. [Note 2] The terminal according to Note 1, wherein the receiving unit receives configuration information (e.g., RRC information element) for setting a plurality of wireless network temporary identifiers (e.g., RNTI) for the physical layer signaling. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit performs control to perform the transmission or reception of the data based on a first physical layer signaling (e.g., common DCI) which includes information common to a plurality of multiplexed data; and a second physical layer signaling (e.g., dedicated DCI) which includes information specific to the data among the plurality of data. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit performs control to transmit or receive the data based on the physical layer signaling (e.g., hybrid DCI) which includes information common to a plurality of multiplexed data and information specific to each of the plurality of data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0287] The control unit 110 may generate physical layer signaling for scheduling the transmission or reception of data to which encoding processing based on an artificial intelligence model is applied. The transmitting / receiving unit 120 may transmit the physical layer signaling to the user terminal 20.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0306] The transmitting / receiving unit 220 may also receive physical layer signaling (e.g., DCI) for scheduling the transmission or reception (e.g., UL transmission or DL ​​reception) of data to which encoding processing (e.g., eMDMA operation) based on an artificial intelligence model (e.g., an AI model) is applied. The control unit 210 may perform control to transmit or receive the data based on the physical layer signaling.

[0307] The transmitting / receiving unit 220 may receive configuration information (e.g., RRC information elements) that sets up a plurality of wireless network temporary identifiers (e.g., RNTI) for physical layer signaling.

[0308] The control unit 210 may perform control to transmit or receive the data based on a first physical layer signaling (e.g., common DCI) that includes information common to the multiple data to be multiplexed, and a second physical layer signaling (e.g., dedicated DCI) that includes information specific to the data among the multiple data.

[0309] The control unit 210 may perform control to transmit or receive the data based on the physical layer signaling (e.g., hybrid DCI) which includes information common to the multiplexed data and information specific to each of the multiple data.

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

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

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

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

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

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

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

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

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

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

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

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

[0322] Furthermore, each device, such as the processor 1001 and 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0358] 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,” “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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0408] 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 receiving unit that receives physical layer signaling for scheduling the transmission or reception of data to which encoding processing based on an artificial intelligence model is applied, and a control unit that performs control to perform the transmission or reception of the data based on the physical layer signaling.

2. The terminal according to claim 1, wherein the receiving unit receives configuration information for setting a plurality of temporary wireless network identifiers for physical layer signaling.

3. The terminal according to claim 1, wherein the control unit performs control to transmit or receive the data based on a first physical layer signaling that includes common information for a plurality of multiplexed data, and a second physical layer signaling that includes individual information for the data among the plurality of data.

4. The terminal according to claim 1, wherein the control unit performs control to transmit or receive the data based on the physical layer signaling which includes information common to a plurality of multiplexed data and information specific to each of the plurality of data.

5. A wireless communication method for a terminal, comprising the steps of: receiving a physical layer signaling for scheduling the transmission or reception of data to which encoding processing based on an artificial intelligence model is applied; and performing control to transmit or receive the data based on the physical layer signaling.

6. A base station having a control unit that generates physical layer signaling for scheduling the transmission or reception of data to which encoding processing based on an artificial intelligence model is applied, and a transmission unit that transmits the physical layer signaling.

Images