Terminal, wireless communication method, base station and system

JPWO2023152902A5Active Publication Date: 2025-02-04NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023579980
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-02-10
Filing Date
2022-02-10
Publication Date
2025-02-04
Estimated Expiration
2042-02-10

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in effectively controlling uplink (UL) transmission using multiple panels, which can lead to system performance degradation such as throughput degradation if not properly managed.

Method used

A terminal and wireless communication method that supports multiple panels for UL transmission, using a receiving unit to receive parameters for scheduling UL channels with single or multiple downlink control information, allowing for appropriate control of UL transmission even when multiple panels are used, by configuring precoders and SRS resources through higher layer signaling.

Benefits of technology

Enables efficient and controlled UL transmission using multiple panels, improving throughput and reliability by appropriate scheduling and configuration of UL channels and precoders, thereby preventing system performance degradation.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

A terminal according to an aspect of the present disclosure comprises: a reception unit that, when UL transmission using a plurality of panels including at least a first panel and a second panel is supported, receives a first parameter which is set in common for a first UL channel and a second UL channel or a second parameter which is set separately for the first UL channel and the second UL channel, the first UL channel being related to at least one transmission / reception point (TRP) and the first panel, the second UL channel being related to at least one TRP and the second panel; and a control unit that applies the first parameter or the second parameter to transmission of the second UL channel and the first UL channel scheduled with either a single piece of downlink control information or a plurality of pieces of downlink control information.
Need to check novelty before this filing date? Find Prior Art

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

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

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

[0005] In future wireless communication systems, a UE will be able to use one of multiple panels (or multiple beams) for uplink (UL) transmission. Furthermore, in Rel. 18 and beyond, support for simultaneous UL transmission (e.g., simultaneous multi-panel UL transmission (SiMPUL)) using multiple panels to one or more Transmission / Reception Points (TRPs) is being considered to improve UL throughput / reliability.

[0006] However, there has been insufficient consideration on how to control UL transmission using multiple panels (e.g., simultaneous UL transmission). If UL transmission using multiple panels is not performed appropriately, there is a risk of degradation of system performance, such as a decrease in throughput.

[0007] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission even when UL transmission is performed using multiple panels.

[0008] A terminal according to one aspect of the present disclosure, when UL transmission using multiple panels including at least a first panel and a second panel is supported, has a receiving unit that receives a first parameter that is set commonly or a second parameter that is set separately for a first UL channel associated with the first panel and at least one of a transmission / reception point (TRP), and a second UL channel associated with the second panel and at least one of the TRP, and a control unit that applies the first parameter or the second parameter to transmission of the first UL channel and the second UL channel scheduled by a single downlink control information or multiple downlink control information.

[0009] According to one aspect of the present disclosure, even when UL transmission is performed using multiple panels, UL transmission can be appropriately controlled.

[0010] FIG. 1 is a diagram illustrating an example of association between precoder types and TPMI indexes. FIGS. 2A and 2B are diagrams illustrating an example of UL transmission for a single panel. FIGS. 3A to 3C are diagrams illustrating examples of methods 1 to 3 of simultaneous UL transmission using multiple panels. FIGS. 4A and 4B are diagrams illustrating an example of PUSCH transmission according to a first embodiment. FIGS. 5A and 5B are diagrams illustrating an example of higher layer parameter configuration according to a second embodiment. FIGS. 6A and 6B are diagrams illustrating an example of higher layer parameter configuration according to a third embodiment. FIGS. 7A and 7B are diagrams illustrating an example of UE operation #1 / UE operation #2. FIGS. 8A and 8B are diagrams illustrating an example of multiple PUSCH transmission according to a fourth embodiment. FIG. 9 is a diagram illustrating another example of multiple PUSCH transmission according to the fourth embodiment. FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 11 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 12 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 13 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 14 is a diagram illustrating an example of a vehicle according to an embodiment.

[0011] (PUSCH Precoder) In NR, it is being considered that a UE will support at least one of codebook (CB)-based transmission and non-codebook (NCB)-based transmission.

[0012] For example, it is being considered that the UE determines a precoder (precoding matrix) for CB-based and / or NCB-based Physical Uplink Shared Channel (PUSCH) transmission using at least a Sounding Reference Signal (SRS) resource indicator (SRI).

[0013] In the case of CB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), a Transmitted Precoding Matrix Indicator (TPMI), etc. In the case of NCB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI.

[0014] The SRI, TRI, TPMI, etc. may be notified to the UE using Downlink Control Information (DCI). The SRI may be specified by the SRS Resource Indicator field (SRI field) of the DCI, or may be specified by the parameter "srs-ResourceIndicator" included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH. The TRI and TPMI may be specified by the "Precoding information and number of layers" field of the DCI.

[0015] The UE may report UE capability information related to a precoder type, and the base station may configure the precoder type based on the UE capability information through higher layer signaling. The UE capability information may be information on the precoder type used by the UE in PUSCH transmission (which may be represented by the RRC parameter "pusch-TransCoherence").

[0016] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

[0017] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), etc.

[0018] The UE may determine the precoder to be used for PUSCH transmission based on precoder type information (which may be represented by the RRC parameter "codebookSubset") included in PUSCH configuration information ("PUSCH-Config" information element of RRC signaling) notified by higher layer signaling. The UE may be configured with a subset of the PMI specified by the TPMI by the codebookSubset.

[0019] The precoder type may be specified by any one of full coherent, partial coherent, and non-coherent, or a combination of at least two of these (for example, it may be expressed by parameters such as "fully and partial and non-coherent" or "partial and non-coherent").

[0020] Fully coherent may mean that all antenna ports used for transmission are synchronized (may be expressed as being able to match the phase, using the same precoder, etc.). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those some ports cannot be synchronized with other ports. Non-coherent may mean that each antenna port used for transmission cannot be synchronized.

[0021] Note that a UE that supports a fully coherent precoder type may be assumed to support partially coherent and non-coherent precoder types, and a UE that supports a partially coherent precoder type may be assumed to support a non-coherent precoder type.

[0022] The precoder type may be interpreted as coherency, PUSCH transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, or the like.

[0023] The UE may determine, from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmission, a precoding matrix corresponding to a TPMI index obtained from a DCI (e.g., DCI format 0_1, etc.) that schedules an UL transmission.

[0024] Fig. 1 is a diagram showing an example of association between precoder types and TPMI indexes. Fig. 1 corresponds to a table of precoding matrices W for single-layer (rank 1) transmission using four antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, transform precoding is effective).

[0025] In Fig. 1, when the precoder type (codebookSubset) is fully, partial, and noncoherent (fullyAndPartialAndNonCoherent), the UE is notified of a TPMI of any one of 0 to 27 for single layer transmission. Also, when the precoder type is partial and noncoherent (partialAndNonCoherent), the UE is configured with a TPMI of any one of 0 to 11 for single layer transmission. When the precoder type is noncoherent, the UE is configured with a TPMI of any one of 0 to 3 for single layer transmission.

[0026] As shown in Fig. 1, a precoding matrix in which only one element in each column is non-zero may be called a non-coherent codebook. A precoding matrix in which a predetermined number (not all) of elements in each column are non-zero may be called a partially coherent codebook. A precoding matrix in which all elements in each column are non-zero may be called a fully coherent codebook.

[0027] The non-coherent codebook and the partially coherent codebook may be referred to as an antenna selection precoder, and the fully coherent codebook may be referred to as a non-antenna selection precoder.

[0028] In the present disclosure, a partially coherent codebook may correspond to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a partially coherent codebook subset (e.g., RRC parameter “codebookSubset”=“partialAndNonCoherent”), excluding a codebook corresponding to a TPMI specified by DCI for a UE configured with a non-coherent codebook subset (e.g., RRC parameter “codebookSubset”=“nonCoherent”) (i.e., in the case of single-layer transmission with four antenna ports, a codebook with TPMI=4 to 11).

[0029] In the present disclosure, a fully coherent codebook may correspond to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a fully coherent codebook subset (e.g., RRC parameter “codebookSubset”=“fullyAndPartialAndNonCoherent”), excluding a codebook corresponding to a TPMI specified by DCI for a UE configured with a partially coherent codebook subset (e.g., RRC parameter “codebookSubset”=“partialAndNonCoherent”) (i.e., in the case of single-layer transmission with four antenna ports, a codebook with TPMI=12 to 27).

[0030] (Spatial Relationship for SRS, PUSCH) The UE may receive information (SRS configuration information, e.g., parameters in the RRC control element "SRS-Config") used for transmitting measurement reference signals (e.g., Sounding Reference Signals (SRS)).

[0031] Specifically, the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

[0032] An SRS resource set may be associated with (or group together) a predetermined number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

[0033] The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type, and information on SRS usage.

[0034] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic SRS (A-SRS, AP-SRS). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation), and transmit A-SRS based on an SRS request in the DCI.

[0035] Furthermore, the usage ("usage" of the RRC parameter, "SRS-SetUse" of the L1 (Layer-1) parameter) may be, for example, beam management, codebook-based transmission (codebook: CB), non-codebook-based transmission (non-Codebook: NCB), antenna switching, etc. The SRS for the codebook-based transmission or non-codebook-based transmission may be used to determine a precoder for codebook-based or non-codebook-based PUSCH transmission based on the SRI.

[0036] For example, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI) in the case of codebook-based transmission. The UE may determine a precoder for PUSCH transmission based on the SRI in the case of non-codebook-based transmission.

[0037] The SRS resource information may include an SRS resource ID (SRS-ResourceId), the number of SRS ports, the SRS port number, a transmission comb, an SRS resource mapping (e.g., time and / or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

[0038] The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS / PBCH block may be referred to as a Synchronization Signal Block (SSB).

[0039] The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the predetermined reference signal.

[0040] In the present disclosure, the SSB index, SSB resource ID, and SSBRI (SSB Resource Indicator) may be interchangeable. Also, the CSI-RS index, CSI-RS resource ID, and CRI (CSI-RS Resource Indicator) may be interchangeable. Also, the SRS index, SRS resource ID, and SRI may be interchangeable.

[0041] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the predetermined reference signal.

[0042] In NR, the transmission of uplink signals may be controlled based on the presence or absence of beam correspondence (BC). BC may be, for example, the ability of a node (e.g., a base station or a UE) to determine the beam to be used for transmitting a signal (transmit beam, Tx beam) based on the beam to be used for receiving the signal (receive beam, Rx beam).

[0043] BC may also be referred to as transmit / receive beam correspondence (Tx / Rx beam correspondence), beam reciprocity, beam calibration, calibrated / non-calibrated, reciprocity calibrated / non-calibrated, correspondence, agreement, etc.

[0044] For example, in the absence of BC, the UE may transmit an uplink signal (e.g., PUSCH, PUCCH, SRS, etc.) using the same beam (spatial domain transmit filter) as the SRS (or SRS resource) instructed by the base station based on the measurement results of one or more SRSs (or SRS resources).

[0045] On the other hand, when BC is present, the UE may transmit an uplink signal (e.g., a PUSCH, a PUCCH, an SRS, etc.) using a beam (spatial domain transmit filter) that is the same as or corresponds to the beam (spatial domain receive filter) used to receive a specified SSB or CSI-RS (or CSI-RS resource).

[0046] When the UE is configured with spatial relationship information regarding the SRS and an SSB or CSI-RS for a certain SRS resource (e.g., with BC), the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter). In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0047] When the UE is configured with spatial relationship information between another SRS (reference SRS) and the target SRS for a certain SRS (target SRS) resource (e.g., without BC), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmit beam for the reference SRS and the UE transmit beam for the target SRS are the same.

[0048] The UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., an SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information of the SRS resources (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

[0049] When codebook-based transmission is used for PUSCH, two SRS resources may be configured for the UE by RRC, and one of the two SRS resources may be indicated by a DCI (a 1-bit predetermined field). When non-codebook-based transmission is used for PUSCH, four SRS resources may be configured for the UE by RRC, and one of the four SRS resources may be indicated by a DCI (a 2-bit predetermined field). To use a spatial relationship other than the two or four spatial relationships configured by RRC, an RRC reconfiguration is required.

[0050] In addition, the DL-RS can be configured for the spatial relationship of the SRS resources used for the PUSCH. For example, for SP-SRS, the UE can be configured by RRC with the spatial relationship of multiple (e.g., up to 16) SRS resources, and one of the multiple SRS resources can be indicated by MAC CE.

[0051] (TPMI and Transmission Rank) In Rel. 16, it is considered that a Transmitted Precoding Matrix Indicator (TPMI) and a transmission rank for codebook-based PUSCH transmission are specified by specific fields (e.g., precoding information and number of layers fields) included in downlink control information (e.g., DCI format 0_1). Note that in the present disclosure, the term "rank" may be interchangeable with the term "layer."

[0052] The precoder used by the UE for codebook-based PUSCH transmission may be selected from an uplink codebook with a number of antenna ports equal to the value configured in the higher layer parameter configured for the SRS resources (e.g., nrofSRS-Ports).

[0053] The size (number of bits) of this particular field is variable depending on the number of antenna ports for PUSCH (e.g., the number of ports indicated by nrofSRS-Ports above) and some higher layer parameters.

[0054] The particular field may be a 0 bit if the higher layer parameters (e.g., txConfig) configured for the UE are set to non-codebook.

[0055] Furthermore, the particular field may be a 0 bit when the higher layer parameters (e.g., txConfig) configured for the UE for one antenna port are set to the codebook.

[0056] Furthermore, for four antenna ports, when an upper layer parameter (e.g., txConfig) configured for the UE is set to a codebook, the specific field may have a bit length of 2 to 6 bits based on at least one of another upper layer parameter configured for the UE and the presence or absence (enabled or disabled) of a transform precoder.

[0057] Furthermore, for two antenna ports, when an upper layer parameter (e.g., txConfig) configured for the UE is set to a codebook, the specific field may have a bit length of 1 to 4 bits based on at least one of another upper layer parameter configured for the UE and the presence or absence (enabled or disabled) of a transform precoder.

[0058] The other upper layer parameter may be at least one of a parameter for specifying a UL full power transmission mode (e.g., ul-FullPowerTransmission, ul-FullPowerTransmission-r16), a parameter indicating the maximum value of the UL transmission rank (e.g., maxRank), a parameter indicating a subset of a certain precoding matrix indicator (PMI) (e.g., codebookSubset), and a parameter for specifying a transform precoder (e.g., transformPrecoder).

[0059] (Single Panel Transmission) The single panel UL transmission method or the single panel UL transmission method candidate may apply at least one of the following transmission methods A and B (single panel UL transmission methods A and B). Note that in the present disclosure, panel / UE panel may be interpreted as a UE capability value set (e.g., UE capability value set) reported for each UE capability.

[0060] Transmission Scheme A: Single Panel Single TRP UL Transmission In Rel. 15 and Rel. 16, a transmission scheme is used in which a UE transmits UL for one TRP at a time from only one beam and panel (FIG. 2A).

[0061] [Transmission Scheme B: Single Panel Multi-TRP UL Transmission] Rel. 17 considers UL transmission from only one beam and panel at a time and repeated transmission for multiple TRPs (Fig. 2B). In the example of Fig. 2B, the UE transmits a PUSCH from panel #1 to TRP #1 (switching beams and panels), and then transmits a PUSCH from panel #2 to TRP #2. The two TRPs are connected via an ideal backhaul.

[0062] (Multi-Panel Transmission) In Rel. 18 and later, in order to improve UL throughput / reliability, support for simultaneous UL transmission using multiple panels for one or more TRPs is being considered. Also, a multi-panel UL transmission scheme is being considered for a specific UL channel (e.g., PUSCH / PUCCH).

[0063] For example, up to X (e.g., X = 2) and up to Y (e.g., Y = 2) panels may be supported for multi-panel UL transmission. In multi-panel UL transmission, if UL precoding indication for PUSCH is supported, a codebook of a legacy system (e.g., pre-Rel. 16) may be supported for simultaneous multi-panel transmission. Considering single DCI and multi-DCI-based multi-TRP operation, the number of layers may be up to x (e.g., x = 4) across all panels, and the number of codewords (CWs) may be up to y (e.g., y = 2) across all panels.

[0064] At least one of the following methods 1 to 3 (multi-panel UL transmission methods 1 to 3) is being considered as a multi-panel UL transmission method or a candidate multi-panel UL transmission method. Only one of transmission methods 1 to 3 may be supported. Multiple methods including at least one of transmission methods 1 to 3 may be supported, and one of the multiple transmission methods may be configured in the UE.

[0065] Transmission Scheme 1: Coherent Multi-Panel UL Transmission Multiple panels may be synchronized with each other. All layers are mapped to all panels. Multiple analog beams are directed. The SRS Resource Indicator (SRI) field may be extended. This scheme may use up to 4 layers for UL.

[0066] In the example of Figure 3A, the UE maps one codeword (CW) or one transport block (TB) to L layers (PUSCH (1, 2, ..., L)) and transmits the L layers from each of two panels. Panels #1 and #2 are coherent. Transmission scheme 1 can obtain diversity gain. The total number of layers in the two panels is 2L. If the maximum total number of layers is 4, the maximum number of layers in one panel is 2.

[0067] [Transmission Scheme 2: Non-coherent Multi-Panel UL Transmission of One Codeword (CW) or Transport Block (TB)] The multiple panels may not be synchronized. Different layers are mapped to different panels and one CW or TB for PUSCH from multiple panels. A layer corresponding to one CW or TB may be mapped to multiple panels. This transmission scheme may use up to four layers or up to eight layers for the UL. If up to eight layers are supported, this transmission scheme may support one CW or TB using up to eight layers.

[0068] In the example of FIG. 3B, the UE maps 1 CW or 1 TB to k layers (PUSCH(1, 2, ..., k)) and L-k layers (PUSCH(k+1, k+2, ..., L)), transmits k layers from panel #1, and transmits L-k layers from panel #2. Transmission scheme 2 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.

[0069] [Transmission Scheme 3: Non-coherent Multi-Panel UL Transmission of Two CWs or TBs] The multiple panels may not be synchronized. Different layers are mapped to different panels and two CWs or TBs for PUSCH from multiple panels. A layer corresponding to one CW or TB may be mapped to one panel. Layers corresponding to multiple CWs or TBs may be mapped to different panels. This transmission scheme may use up to four layers or up to eight layers for the UL. If up to eight layers are supported, this transmission scheme may support up to four layers per CW or TB.

[0070] In the example of FIG. 3C , the UE maps CW#1 or TB#1 of the 2CWs or 2TBs to k layers (PUSCH (1, 2, ..., k)), maps CW#2 or TB#2 to L-k layers (PUSCH (k+1, k+2, ..., L)), and transmits k layers from panel #1 and L-k layers from panel #2. Transmission scheme 3 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.

[0071] In each of the above transmission schemes, the base station may configure or indicate panel-specific transmission for UL transmission using UL TCI or panel ID. UL TCI (UL TCI state) may be based on signaling similar to DL beam indication supported in Rel. 15. The panel ID may be implicitly or explicitly applied to transmission of at least one of the target RS resource or target RS resource set, PUCCH, SRS, and PRACH. When the panel ID is explicitly signaled, the panel ID may be configured in at least one of the target RS, target channel, and reference RS (e.g., DL RS resource configuration or spatial relationship information).

[0072] In one or more of the transmission methods / modes described above, multi-panel UL transmission (e.g., simultaneous multi-panel UL transmission (SiMPUL)) for scheduling a PUSCH based on one DCI (single DCI) / scheduling a PUSCH based on multiple DCIs (multi-DCI) is being considered.

[0073] However, when at least one of single DCI-based simultaneous multi-panel UL transmission (case #1) and multiple DCI-based simultaneous multi-panel UL transmission (case #2) is supported, the question arises as to how to control the UL transmission.

[0074] For example, in multi-DCI-based simultaneous multi-panel UL transmission, how to control the time / frequency resources of the PUSCH for each panel (or corresponding to each panel) becomes an issue.

[0075] Alternatively, the problem in each case is how to control the codebook configuration (e.g., codebook subset configuration) for each CW / panel / TRP / PUSCH / TB. Alternatively, the problem in each case is how to control the UL transmission power configuration (e.g., UL full power configuration) for each CW / panel / TRP / PUSCH / TB.

[0076] Alternatively, the issue in each case is how to control UL rank constraints (e.g., UL rank constrictions) for each CW / panel / TRP / PUSCH / TB.

[0077] Alternatively, in multi-DCI-based simultaneous multi-panel UL transmission, the issue arises as to how to control the transmission / scheduling order / whether or not time domain overlap is supported for the PUSCHs corresponding to each panel.

[0078] Therefore, the present inventors have studied UL transmission control that solves at least one of the above problems and have come up with the idea for this embodiment.

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

[0080] In the present disclosure, "A / B" may mean "at least one of A and B." Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0081] In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be interchangeable.

[0082] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0083] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), and RRC messages may be read interchangeably.

[0084] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0085] In the present disclosure, MAC CE and activation / deactivation command may be read interchangeably.

[0086] In the present disclosure, panel, beam, spatial domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameters, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D for TCI state / QCL assumption, RS of QCL type A for TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS may be read interchangeably. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, source of DL-RS, SSB, CSI-RS, and SRS may be read interchangeably.

[0087] In the present disclosure, panel, Uplink (UL) transmitting entity, TRP, spatial relationship, control resource set (CONTROLLER RESOLUTION SET (CORESET)), PDSCH, codeword, base station, antenna port of a certain signal (e.g., Demodulation Reference Signal (DMRS) port), antenna port group of a certain signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CORESET subset, CW, redundancy version (RV), layer (MIMO layer, transmission layer, spatial layer) may be interchangeable. Also, panel identifier (ID) and panel may be interchangeable. In the present disclosure, the terms TRP ID, TRP Associated ID, CORESET Pool Index, the position of one of two TCI states corresponding to one code point of a field in a DCI (ordinal number, first TCI state or second TCI state), and TRP may be read interchangeably.

[0088] In the present disclosure, panel, UE panel, RS port group, DMRS port group, SRS port group, RS resource group, DMRS resource group, SRS resource group, beam group, TCI state group, spatial relationship group, SRS resource indicator (SRI) group, antenna port group, antenna group, and CORESET group may be read as interchangeable.

[0089] The panel may be associated with at least one of a panel ID, a UL TCI state, a UL beam, an L beam, a DL RS resource, and spatial relationship information.

[0090] In the present disclosure, the terms "multi-TRP," "multi-TRP system," "multi-TRP transmission," "multi-PDSCH," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, the terms "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, the terms "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0091] In the present disclosure, the terms single TRP, single DCI, single PDCCH, multi-TRP based on single DCI, single TRP system, single TRP transmission, single PDSCH, channel using single TRP, channel using one TCI state / spatial relationship, multi-TRP not being enabled by RRC / DCI, multiple TCI states / spatial relationships not being enabled by RRC / DCI, a CORESETPoolIndex value of 1 not being set for any CORESET and no code point in the TCI field being mapped to two TCI states, and two TCI states on at least one TCI code point being activated may be read interchangeably.

[0092] In the present disclosure, the terms "switch," "decide," and "select" may be read interchangeably.

[0093] (Wireless communication method) A UE may be configured for simultaneous multi-beam / multi-panel (hereinafter also simply referred to as multi-panel) UL transmission. The configuration may be performed using higher layer signaling (e.g., RRC signaling / MAC CE) / physical layer signaling (e.g., DCI).

[0094] The setting may be a setting for simultaneous UL transmission of multiple panels, or a setting for simultaneous UL transmission of multiple panels across multiple (multiple types of) UL channels / signals.

[0095] The UE may report capability information regarding simultaneous multi-panel UL transmission to the network (NW, e.g., base station).

[0096] The UE capability information may be capability information for simultaneous multi-panel UL transmission, or capability information for simultaneous multi-panel UL transmission across multiple (multiple types of) UL channels / signals.

[0097] The UE may report capability information regarding simultaneous multi-panel UL transmission to the NW and may be configured for simultaneous multi-panel UL transmission.

[0098] The NW may transmit information regarding collision handling of the UL channel / signal to the UE. The information may be transmitted using higher layer signaling / physical layer signaling.

[0099] Although the following mainly describes a case where the number of panels is two, the number of panels may be two or more. Each embodiment of the present disclosure can also be applied as appropriate to transmission using three or more panels.

[0100] In the present disclosure, the base station may receive at least one of multiple UL channels / signals simultaneously transmitted by the UE, which may mean that at least a portion of each UL channel / signal is supported / allowed to overlap in the time domain.

[0101] In the first embodiment, resource allocation in multiple DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) will be described. In the following description, PUSCH transmission will be used as an example of UL transmission, but the present invention may be applied to other UL channels / UL signals.

[0102] Whether or not the multi-DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is applied may be configured for the UE by a network (e.g., a base station). For example, the base station configures the multi-DCI-based simultaneous multi-panel UL transmission for the UE using higher layer parameters (e.g., RRC parameters).

[0103] In this case, the UE may assume that up to two PUSCHs associated with multiple (e.g., two) TRPs / panels are scheduled. Each PUSCH may correspond to up to X (e.g., X = 1) CWs. Each PUSCH may be scheduled (e.g., transmission parameters may be indicated) by multiple DCIs. For example, if two PUSCHs (e.g., PUSCH #1 and PUSCH #2) are transmitted using multiple panels, PUSCH #1 may be scheduled by DCI #1, and PUSCH #2 may be scheduled by DCI #2.

[0104] The association between the TRP / panel and the PUSCH may be determined based on at least one of the association established between the TRP / panel and the PUSCH, the association established between the TRP / panel and the TCI of the PUSCH, the association established between the spatial relationship of the TRP / panel and the PUSCH, the association established between the TRP / panel and the DCI used for scheduling the PUSCH, and the association established between the TRP / panel and the CORESET for scheduling the PUSCH.

[0105] The TRP / Panel ID may be indicated by at least one of a CORESET pool index, a panel ID, a UE antenna group ID, an RS group ID, and a UE capability set ID.

[0106] Multiple (e.g., two) PUSCHs (e.g., PUSCH #1 and PUSCH #2) transmitted using a multi-panel system may be transmitted overlapping in the time domain. In this case, PUSCH #1 and PUSCH #2 may be scheduled / transmitted / mapped to completely overlap in the time domain (see FIG. 4A). Alternatively, PUSCH #1 and PUSCH #2 may be scheduled / transmitted / mapped to at least partially overlap in the time domain (see FIG. 4B).

[0107] 4A shows a case where DCI #1 scheduling PUSCH #1 and DCI #2 scheduling PUSCH #2 correspond to different CORESET pool indices. FIG. 4B shows a case where DCI #1 scheduling PUSCH #1 and DCI #2 scheduling PUSCH #2 have the same pair index. The pair index may be defined / configured on a multi-DCI basis. For example, the same pair index may be defined / configured for a combination of DCIs corresponding to multiple panels / TRPs (e.g., a combination of DCI #1 corresponding to panel #1 / TRP #1 and DCI #2 corresponding to panel #2 / TRP #2). Note that the relationship between DCI #1 and DCI #2 is not limited to this.

[0108] As a frequency domain (or frequency domain) allocation of multiple PUSHs (e.g., PUSH #1 and PUSH #2) that overlap in the time domain, at least one of the following options 1-1 to 1-3 may be applied.

[0109] [Option 1-1] Non-overlapping, partial-overlapping, and full-overlapping are supported.

[0110] [Option 1-2] Only some cases of non-overlapping, partial-overlapping, and full-overlapping are supported. The supported cases may be defined in the specifications or may be configured in the UE by the base station using higher layer parameters, etc.

[0111] [Option 1-3] In Option 1-1 or Option 1-2, in the case where there is no overlap in the frequency domain (non-overlapping), a configuration may be adopted in which the gap between two frequency domain resource allocations (e.g., the gap / offset between PUSCH #1 and PUSCH #2) satisfies a predetermined condition / predetermined range. For example, the gap between the two frequency domain resource allocations may be limited to be smaller than X subcarriers / X resource blocks (RBs) / X physical resource blocks (PRBs). X may be defined in a specification (e.g., defined as a fixed value) or may be configured in the UE by the base station using higher layer parameters, etc.

[0112] Also, UE capabilities may be introduced / supported for each option.

[0113] In Option 1-1 to Option 1-3, a predetermined condition may be applied to multiple (e.g., two) PUSCHs (e.g., PUSCH #1 and PUSCH #2). The predetermined condition may be the setting of a demodulation reference signal (e.g., DMRS).

[0114] For example, a configuration may be adopted in which at least one DMRS configuration is the same (or commonly configured) for multiple (e.g., two) PUSCHs (e.g., PUSCH #1 and PUSCH #2). The DMRS configuration may include at least one of a DMRS configuration type (e.g., DMRS configuration type), a mapping time (e.g., mapping time), a mapping type (e.g., mapping type), the number of additional DMRSs (e.g., the number of additional DMRSs), and single-symbol DMRS or double-symbol DMRS.

[0115] Alternatively, the DMRS symbol index may be the same (or commonly set) for multiple (e.g., two) PUSCHs (e.g., PUSCH #1 and PUSCH #2).

[0116] Alternatively, for multiple (e.g., two) PUSHs (e.g., PUSH #1 and PUSH #2), the CDM groups of the DMRS may be configured to be different, or the CDM groups may be configured to be the same (or commonly set).

[0117] Second Embodiment In a second embodiment, codebook setting / UL power control in simultaneous multi-panel UL transmission (e.g., SiMPUL) will be described. In the following description, PUSCH transmission will be used as an example of UL transmission, but the present invention may be applied to other UL channels / UL signals.

[0118] <<Single DCI-based>> When single DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is configured, at least one of the following options 2A-1 and 2A-2 may be applied to the codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission).

[0119] Whether or not single DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is applied may be configured for a UE by a network (e.g., a base station). For example, the base station configures the UE with single DCI-based simultaneous multi-panel UL transmission using higher layer parameters (e.g., RRC parameters). The UE may determine that the transmission is single DCI-based when the CORESET pool index is not configured (or when only one value is configured as the CORESET pool index).

[0120] [Option 2A-1] For single DCI-based simultaneous multi-panel UL transmissions (e.g., multiple PUSCHs), a codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) may be configured in the same manner as in existing systems (e.g., Rel. 16 and earlier). For example, for single DCI-based simultaneous multi-panel UL transmissions (e.g., multiple PUSCHs), a codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) may be commonly configured by higher layer signaling (see FIG. 5A ).

[0121] The UE may apply higher layer parameters related to codebook configuration to multiple PUSCHs in common, regardless of the TRP / panel to which each PUSCH is associated. For example, a codebook subset configuration (e.g., codebookSubset) for a predetermined DCI format (e.g., DCI format 0_1 / 0_2) may be applied to multiple PUSCHs in common by higher layer signaling. More specifically, fully coherent, partially coherent, or noncoherent ({fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent}) may be configured for multiple PUSCHs depending on the codebook subset (e.g., codebookSubset) included in the PUSCH configuration (e.g., PUSCH-Config).

[0122] The UE may apply higher layer parameters related to UL full power transmission to multiple PUSCHs in common, regardless of the TRP / panel to which each PUSCH is associated. For example, a full power transmission mode (e.g., ul-FullPowerTransmission) may be applied to multiple PUSCHs in common by higher layer signaling. More specifically, full power, full power mode 1, or full power mode 2 ({fullpower, fullpowerMode1, fullpowerMode2}) may be configured for multiple PUSCHs by a full power transmission mode (e.g., ul-FullPowerTransmission) included in a PUSCH configuration (e.g., PUSCH-Config).

[0123] [Option 2A-2] For single DCI-based simultaneous multi-panel UL transmissions (e.g., multiple PUSCHs), the codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) may be configured individually / separately. That is, it may be supported that the codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) is configured differently for multiple PUSCHs associated with each TRP / panel.

[0124] For example, a first upper layer parameter corresponding to codebook setting / UL full power transmission may be configured for PUSCH#1 associated with a first TRP / panel, and a second upper layer parameter corresponding to codebook setting / UL full power transmission may be configured for PUSCH#2 associated with a second TRP / panel (see FIG. 5B). The first upper layer parameter may be an upper layer parameter corresponding to codebook setting / UL full power transmission supported in a legacy system (e.g., Rel. 16 or earlier), and the second upper layer parameter may be a new upper layer parameter.

[0125] Depending on a codebook subset (e.g., codebookSubset) included in a PUSCH configuration (e.g., PUSCH-Config), fully coherent, partially coherent, or noncoherent ({fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent}) may be configured separately for multiple PUSCHs. Alternatively, depending on a full power transmission mode (e.g., ul-FullPowerTransmission) included in a PUSCH configuration (e.g., PUSCH-Config), full power, full power mode 1, and full power mode 2 ({fullpower, fullpowerMode1, fullpowerMode2}) may be configured separately for multiple PUSCHs.

[0126] Note that, although FIG. 5B illustrates a case where the first upper layer parameter and the second upper layer parameter are included in the same PUSCH configuration (for example, PUSCH-Config), they may be included in different PUSCH configurations.

[0127] Even when single DCI-based simultaneous multi-panel UL transmission is configured, the UE may apply different configurations depending on whether simultaneous multi-panel UL transmission is applied. For example, when simultaneous multi-panel UL transmission is not performed, a specific upper layer parameter may be applied to PUSCH transmission, and when simultaneous multi-panel UL transmission is performed, multiple upper layer parameters may be applied to multiple PUSCH transmissions, respectively.

[0128] <<Multi-DCI based>> When multi-DCI based simultaneous multi-panel UL transmission (e.g., SiMPUL) is configured, at least one of the following options 2B-1 and 2B-2 may be applied to the codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission).

[0129] Whether or not the multi-DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is applied may be configured for the UE by a network (e.g., a base station). For example, the base station configures the multi-DCI-based simultaneous multi-panel UL transmission for the UE using higher layer parameters (e.g., RRC parameters). The UE may determine that the UE is multi-DCI-based if the CORESET pool index is configured.

[0130] [Option 2B-1] For multi-DCI-based simultaneous multi-panel UL transmissions (e.g., multiple PUSCHs), a codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) may be configured in the same manner as in existing systems (e.g., Rel. 16 and earlier). For example, for multi-DCI-based simultaneous multi-panel UL transmissions (e.g., multiple PUSCHs), a codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) may be commonly configured by higher layer signaling (see FIG. 5A ).

[0131] The UE may apply higher layer parameters related to codebook configuration to multiple PUSCHs in common, regardless of the TRP / panel to which each PUSCH is associated. For example, a codebook subset configuration (e.g., codebookSubset) for a predetermined DCI format (e.g., DCI format 0_1 / 0_2) may be applied to multiple PUSCHs in common by higher layer signaling. More specifically, fully coherent, partially coherent, or noncoherent ({fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent}) may be configured for multiple PUSCHs depending on the codebook subset (e.g., codebookSubset) included in the PUSCH configuration (e.g., PUSCH-Config).

[0132] The UE may apply higher layer parameters related to UL full power transmission to multiple PUSCHs in common, regardless of the TRP / panel to which each PUSCH is associated. For example, a full power transmission mode (e.g., ul-FullPowerTransmission) may be applied to multiple PUSCHs in common by higher layer signaling. More specifically, full power, full power mode 1, or full power mode 2 ({fullpower, fullpowerMode1, fullpowerMode2}) may be configured for multiple PUSCHs by a full power transmission mode (e.g., ul-FullPowerTransmission) included in a PUSCH configuration (e.g., PUSCH-Config).

[0133] [Option 2B-2] For multiple DCI-based simultaneous multiple-panel UL transmissions (e.g., multiple PUSCHs), the codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) may be configured individually / separately. That is, it may be supported that the codebook configuration (e.g., codebook subset configuration) / UL full power transmission (e.g., ul-FullPowerTransmission) is configured differently for multiple PUSCHs associated with each TRP / panel.

[0134] For example, a first upper layer parameter corresponding to codebook setting / UL full power transmission may be configured for PUSCH#1 associated with a first TRP / panel, and a second upper layer parameter corresponding to codebook setting / UL full power transmission may be configured for PUSCH#2 associated with a second TRP / panel (see FIG. 5B). The first upper layer parameter may be an upper layer parameter corresponding to codebook setting / UL full power transmission supported in a legacy system (e.g., Rel. 16 or earlier), and the second upper layer parameter may be a new upper layer parameter.

[0135] Depending on a codebook subset (e.g., codebookSubset) included in a PUSCH configuration (e.g., PUSCH-Config), fully coherent, partially coherent, or noncoherent ({fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent}) may be configured separately for multiple PUSCHs. Alternatively, depending on a full power transmission mode (e.g., ul-FullPowerTransmission) included in a PUSCH configuration (e.g., PUSCH-Config), full power, full power mode 1, and full power mode 2 ({fullpower, fullpowerMode1, fullpowerMode2}) may be configured separately for multiple PUSCHs.

[0136] Note that, although FIG. 5B illustrates a case where the first upper layer parameter and the second upper layer parameter are included in the same PUSCH configuration (for example, PUSCH-Config), they may be included in different PUSCH configurations.

[0137] Alternatively, multiple codebook setting candidates (or entries) / multiple UL full power transmission candidates (or entries), or a set including a codebook setting and UL full power transmission may be configured by higher layer parameters. In this case, the codebook subset / UL full power transmission to be applied to each PUSCH may be indicated by DCI used for scheduling each PUSCH.

[0138] For single DCI-based simultaneous multi-panel UL transmission / multiple DCI-based simultaneous multi-panel UL transmission, UE capability for codebook subset configuration / UL full power transmission per panel may be introduced / supported.

[0139] Third Embodiment In a third embodiment, a setting of a rank (e.g., maximum rank) in simultaneous multi-panel UL transmission (e.g., SiMPUL) will be described. In the following description, PUSCH transmission will be used as an example of UL transmission, but the setting may also be applied to other UL channels / UL signals.

[0140] <<Multi-DCI based>> When multi-DCI based simultaneous multi-panel UL transmission (e.g., SiMPUL) is configured, at least one of the following options 3-1 and 3-4 may be applied to the maximum rank configuration (e.g., maxrank configuration).

[0141] Whether or not the multi-DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is applied may be configured for the UE by a network (e.g., a base station). For example, the base station configures the UE with the multi-DCI-based simultaneous multi-panel UL transmission using higher layer parameters (e.g., RRC parameters). The UE may determine that the UE is multi-DCI-based if a CORESET pool index is configured. In addition, a maximum rank configuration (e.g., maxrank configuration) may be configured by higher layer parameters.

[0142] [Option 3-1] For multi-DCI-based simultaneous multi-panel UL transmissions (e.g., multiple PUSCHs), a maximum rank (e.g., maxRank / maxRankDCI-0-2-r16) may be configured in the same way as in existing systems (e.g., Rel. 16 and earlier). For example, a maximum rank (e.g., maxRank / maxRankDCI-0-2-r16) may be commonly configured for multiple PUSCHs associated with each TRP / panel by higher layer signaling (see FIG. 6A).

[0143] When ranks are configured for two PUSCHs scheduled by two DCIs, the UE may control UE operation (e.g., how to configure ranks) based on a scheduling case. The scheduling cases may include the following scheduling cases #3-1 / #3-2.

[0144] - Scheduling case #3-1: When two scheduled PUSHs (e.g., PUSH #1 and PUSH #2) overlap in the time domain. - Scheduling case #3-2: When one scheduled PUSH (e.g., PUSH #1) does not overlap in the time domain with another PUSH (e.g., PUSH #2). Note that PUSH #1 and PUSH #2 correspond to PUSHs corresponding to different TRPs / panels.

[0145] The UE may determine the relationship between the configured rank (e.g., the maximum rank) and the rank to be applied to each PUSCH depending on whether the two PUSCHs overlap in the time domain. For example, the UE may apply at least one of the following options 3-1-1 and 3-1-2 depending on scheduling case #3-1 / #3-2.

[0146] [[Option 3-1-1]] The UE may understand that the maximum rank set by higher layer parameters is the maximum total rank of multiple PUSCHs (e.g., time-varying PUSCHs between TRPs / panels).

[0147] That is, in the case of scheduling case #3-2, it may mean that the total rank of one scheduled PUSCH must not exceed the value (maximum rank) set by RRC. Also, in the case of scheduling case #3-1, it may mean that the total rank of two PUSCHs must not exceed the value (maximum rank) set by RRC.

[0148] [[Option 3-1-2]] The UE may understand that the maximum rank set by higher layer parameters is the maximum total rank of each PUSCH (e.g., PUSCH per TRP / panel).

[0149] In this case, only a predetermined value (for example, 1 or 2) may be a candidate value for the rank. For example, in the case of scheduling case #3-1, this may mean that each PUSCH must not exceed the value (maximum rank) set by RRC. In addition, in the case of scheduling case #3-2, this may mean that one PUSCH must not exceed the value (maximum rank) set by RRC, or must not exceed twice the value set.

[0150] [Option 3-2] The maximum rank (e.g., maxRank / maxRankDCI-0-2-r16) may be configured individually / separately for multiple DCI-based simultaneous multi-panel UL transmissions (e.g., multiple PUSCHs). That is, higher layer signaling may support separate configuration of the maximum rank (e.g., maxRank / maxRankDCI-0-2-r16) for multiple PUSCHs associated with each TRP / panel.

[0151] For example, a first upper layer parameter corresponding to the maximum rank may be configured for PUSCH #1 associated with a first TRP / panel, and a second upper layer parameter corresponding to the maximum rank may be configured for PUSCH #2 associated with a second TRP / panel. The first upper layer parameter may be an upper layer parameter (e.g., maxRank / maxRankDCI-0-2-r16) corresponding to the maximum rank supported in a legacy system (e.g., Rel. 16 or earlier), and the second upper layer parameter may be a new upper layer parameter (e.g., maxRank-secondpanel / maxRankDCI-0-2-secondpanel) (see FIG. 6B).

[0152] The UE may determine the rank to be applied to each PUSCH based on the maximum rank set for each PUSCH. For example, the UE may apply at least one of the following options 3-2-1 and 3-2-2.

[0153] Option 3-2-1: The UE may assume that the sum of two values ​​set for each PUSCH (e.g., the maximum rank number set for PUSCH #1 and the maximum rank number set for PUSCH #2) does not exceed the UE capability / predetermined value. The predetermined value may be, for example, 4.

[0154] The base station may control the setting of the maximum rank for each PUSCH so that the total value does not exceed a predetermined value. In this case, the base station may determine the maximum rank corresponding to each PUSCH in consideration of the UE capability regarding the maximum rank number reported from the UE.

[0155] [[Option 3-2-2]] It may be permitted / supported that the sum of two values ​​set for each PUSCH (e.g., the maximum rank number set for PUSCH #1 and the maximum rank number set for PUSCH #2) exceeds the UE capability / predetermined value. In this case, control may be performed so that the sum of the ranks of the PUSCHs actually scheduled does not exceed the UE capability / predetermined value.

[0156] For example, the base station / UE may set a maximum rank of 4 for PUSCH #1 (e.g., PUSCH #1 corresponding to panel #1) and a maximum rank of 2 for PUSCH #2 (e.g., PUSCH #2 corresponding to panel #2). Furthermore, when PUSCH #1 and PUSCH #2 overlap in the time domain, the base station / UE may control the actual rank number (the total rank number of PUSCH #1 and PUSCH #2) so that it does not exceed 4.

[0157] [Option 3-3] For multi-DCI based simultaneous multi-panel UL transmission (e.g., multiple PUSCHs), the allowed rank distribution (e.g., allowed rank distribution) may be directly configured for two panels (or PUSCHs corresponding to each panel).

[0158] For example, for two panels (or PUSCHs corresponding to each panel), a rank to be set for each panel may be selected from predefined combinations. The predefined combination may support, for example, at least one of (1,1), (2,2), (1,2), (2,1), (1,0), (2,0), (3,0), and (4,0). Note that a panel / PUSCH corresponding to 0 may not be scheduled. For example, if (2,0) is set, this may mean that PUSCH #2 corresponding to the second panel is not scheduled / set.

[0159] [Option 3-4] For multiple DCI-based simultaneous multi-panel UL transmission (e.g., multiple PUSCHs), a scheduling case may be configured separately for each scheduling case, which may be the above-mentioned scheduling case #3-1 / #3-2.

[0160] For example, a first upper layer parameter corresponding to the maximum rank may be set for scheduling case #3-2, and a second upper layer parameter corresponding to the maximum rank may be set for scheduling case #3-1. For example, the first upper layer parameter may be an upper layer parameter (e.g., maxRank / maxRankDCI-0-2-r16) corresponding to the maximum rank supported in an existing system (e.g., Rel. 16 or earlier). The second upper layer parameter may be a new upper layer parameter (e.g., maxRank-secondpanel / maxRankDCI-0-2-secondpanel).

[0161] As new upper layer parameters to be set for scheduling case #3-1, at least one of the following options 3-4-1 / 3-4-2 may be applied.

[0162] [[Option 3-4-1]] A parameter that applies to two panels (e.g., maxrank-twopanels) may be set, and the parameter may be set to a predetermined range (e.g., 1 or 2).

[0163] [[Option 3-4-2]] The rank distribution for the two panels may be set. For example, rank distributions such as (1,1) and (2,2) may be supported. Of course, other rank distributions may also be supported.

[0164] <<Single DCI Based>> When single DCI based simultaneous multi-panel UL transmission (e.g., SiMPUL) is configured, at least one of the above options 3-1 and 3-4 may be applied / reused for the maximum rank configuration (e.g., maxrank configuration).

[0165] Whether or not single DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is applied may be configured for a UE by a network (e.g., a base station). For example, the base station configures the UE with single DCI-based simultaneous multi-panel UL transmission using higher layer parameters (e.g., RRC parameters). The UE may determine that the transmission is single DCI-based when the CORESET pool index is not configured (or when only one value is configured as the CORESET pool index). In addition, a maximum rank configuration (e.g., maxrank configuration) may be configured by higher layer parameters.

[0166] When at least one of the above Option 3-1 and Option 3-4 is applied / reused for single DCI-based simultaneous multi-panel UL transmission, "PUSCH" may be replaced with "CW". Also, in single DCI-based simultaneous multi-panel UL transmission, only a specific scheduling case (e.g., scheduling case #3-1) may be supported.

[0167] For single DCI based simultaneous multi-panel UL transmission / multiple DCI based simultaneous multi-panel UL transmission, a UE capability for maximum rank per panel may be introduced / supported.

[0168] <Variations> In the above-described embodiment, when UE capabilities corresponding to codebook / full power / rank are defined for each panel (or UE capability set), higher layer parameters may be configured for each panel.

[0169] In the above embodiment, if the UE capabilities corresponding to the codebook / full power / rank are defined not on a panel basis but on a UE / BWP / CC / band basis, higher layer parameters may be configured for each panel.

[0170] Although the above embodiment has been described taking as an example a UE having two semi-statically active panels, this is not limiting. The two panels for simultaneous multi-panel UL transmission (SiMPUL) may be selected from two or more (or more) panels, or the two panels may be dynamically selected. In this case, new higher layer parameters associated with each panel may exist / be supported, and the corresponding higher layer parameters may be applied based on the scheduled / selected panel.

[0171] Both UE capabilities for codebook / full power / rank per panel and UE capabilities for codebook / full power / rank per UE / BWP / CC / band may be defined. In this case, the configuration (values ​​to be set) of higher layer parameters may be restricted based on both UE capabilities.

[0172] <Fourth embodiment> In the fourth embodiment, a transmission timing / scheduling order between multiple PUSCHs / DCIs in simultaneous multi-panel UL transmission (e.g., SiMPUL) will be described. In the following description, PUSCH transmission will be used as an example of UL transmission, but the present invention may be applied to other UL channels / UL signals.

[0173] In existing systems (e.g., Rel. 16 / 17 and earlier), certain rules are defined for the transmission timing / scheduling order of multiple PUSCHs, e.g., for any HARQ process ID(s) in a given scheduled cell, the UE does not assume / expect PUSCH transmissions that overlap in time with other PUSCHs (UE Action #1) (see FIG. 7A).

[0174] For example, as shown in FIG. 7A, in a certain cell, PUSCH #1 scheduled by DCI #1 and PUSCH #2 scheduled by DCI #2 are not allowed to overlap in the time domain.

[0175] Also, if the UE is scheduled to start the first PUSH transmission starting at symbol j with a PDCCH ending at symbol i, the UE does not assume / expect to be scheduled to transmit a PUSH that starts earlier than the end of the first PUSH with a PDCCH ending after symbol i (UE action #2) (see Figure 7B).

[0176] For example, as shown in FIG. 7B, if a UE is scheduled to start transmitting a PUSH #2 starting at symbol j with a PDCCH #2 (DCI #2) ending at symbol i, it is not permitted to be scheduled to transmit a PUSH #1 starting before the end of a PUSH #2 with a PDCCH #1 (DCI #1) ending after symbol i.

[0177] Note that in UE Operation #2, a predetermined case may be excluded. The predetermined case may be a case where higher layer parameters (e.g., PDCCH-Config) including two different CORESET pool index values ​​are configured in the control resource set (ControlResourceSet) of the active BWP of the serving cell, and multiple PDCCHs scheduling two PUSCHs that do not overlap in the time domain are associated with different control resource sets (ControlResourceSets) having different CORESET pool index values ​​for any two HARQ process IDs in a scheduled cell.

[0178] <<Multiple DCI-based>> [UE Operation #1] When multiple DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is configured, UE Operation #1 may be applied to PUSCHs scheduled by the same TRP / panel. In this case, there may be no restriction on UE Operation #1 for PUSCHs scheduled by multiple (e.g., two) TRPs / panels.

[0179] In this case, for any HARQ process ID(s) in a given scheduled cell, the UE does not assume / expect to transmit a PUSCH that overlaps in the time domain with another PUSCH associated with the same panel ID (e.g. same new-panel-ID).

[0180] For example, in a certain cell, it may be permitted / supported that PUSH #1 scheduled by PDCCH #1 (or DCI #1) corresponding to a first TRP / panel and PUSH #2 scheduled by PDCCH #2 (or DCI #2) corresponding to a second TRP / panel overlap in the time domain (see Figure 8A).

[0181] [UE Action #2] When multiple DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is configured, UE Action #2 may be applied to PUSCHs scheduled by the same TRP / panel. In this case, there may be no restriction on UE Action #2 for PUSCHs scheduled by multiple (e.g., two) TRPs / panels.

[0182] In this case, a predetermined case in which UE Operation #2 does not apply may be defined as follows. The predetermined case may be when higher layer parameters (e.g., PDCCH-Config) are configured to include two different CORESET pool index values ​​in the control resource set (ControlResourceSet) of the active BWP of the serving cell, and multiple PDCCHs scheduling two PUSCHs that do not overlap or overlap in the time domain are associated with different control resource sets (ControlResourceSets) having different CORESET pool index values ​​for any two HARQ process IDs in a scheduled cell. The overlapping may include at least one of partial overlap (e.g., partial-overlapping) and full overlap (e.g., full-overlapping). Alternatively, the case of non-overlapping in the time domain may be deleted from the predetermined case.

[0183] For example, assume that PUSCH #1 is scheduled by PDCCH #1 (or DCI #1) corresponding to a first TRP / panel, and PUSCH #2 is scheduled by PDCCH #2 (or DCI #2) corresponding to a second TRP / panel. In this case, if a UE is scheduled to start PUSCH #2 transmission starting at symbol j by PDCCH #2 (DCI #2) ending at symbol i, it may be permitted / supported to schedule PUSCH #1 transmission starting before the end of PUSCH #2 by PDCCH #1 (DCI #1) ending after symbol i (see FIG. 8B ).

[0184] In addition, in the case of multi-DCI-based simultaneous multi-panel UL transmission, when association is set between multiple DCIs (for example, when pair indices are defined / set), UE operation #1 / UE operation #2 may be configured to be applied to PUSCHs scheduled by PDCCHs (or DCIs) with different pair indices. On the other hand, the restrictions of UE operation #1 / UE operation #2 may not be applied to PUSCHs scheduled by PDCCHs (or DCIs) with the same pair index.

[0185] In addition, UE capabilities related to the restrictions of UE operation #1 / #2 (e.g., UE capabilities related to out-of-order PUSCH enhancement) may be introduced / supported.

[0186] If a UE does not have the UE capability for the restrictions of UE Operation #1 / #2 (or does not support out-of-order), scheduling of multiple PUSCHs only satisfying the requirement that two PUSCHs do not overlap in the time domain may be permitted / supported. Furthermore, in this case, the scheduling order of each PUSCH (e.g., the order of DCI scheduling a certain PUSCH and another PUSCH, etc.) may also be controlled to satisfy UE Operation #2 (see FIG. 9).

[0187] <Application of Transmission Scheme> The first to fourth embodiments may support application to some or all of the transmission schemes #1 to #3 shown in Figures 3A to 3C. Which of the transmission schemes #1 to #3 to apply may be defined in the specifications, or may be configured / instructed by the base station to the UE.

[0188] Furthermore, in the first to fourth embodiments, whether to apply single DCI-based simultaneous multi-panel UL transmission (SiMPUL) or multiple DCI-based simultaneous multi-panel UL transmission may be defined in the specifications, or may be configured / instructed by the base station to the UE.

[0189] Transmission methods #1 to #3 and single DCI-based SiMPUL / multi-DCI-based SiMPUL may be applied in appropriate combination.

[0190] For example, transmission scheme #1 (or transmission schemes #1 and #2) may be applied / configured / supported for single DCI-based SiMPUL, in which case one MIMO codebook may be applied to two PUSCHs / panels.

[0191] Alternatively, transmission scheme #3 (or transmission schemes #3 and #2) may be applied / configured / supported for multi-DCI-based SiMPUL, in which case one MIMO codebook may be applied to each of the two PUSCHs / panels.

[0192] <UE Capability Information> In the first to fourth embodiments, the following UE capabilities may be set. Note that the following UE capabilities may be interpreted as parameters (e.g., upper layer parameters) set in the UE from a network (e.g., a base station).

[0193] UE capability information regarding whether or not single DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) is supported may be defined.

[0194] UE capability information regarding whether or not to support multiple DCI-based simultaneous multi-panel UL transmission (e.g., SiMPUL) may be defined.

[0195] UE capability information may be defined regarding whether full overlapping / partial overlapping / non-overlapping is supported for multiple PUSCH time / frequency resources.

[0196] UE capability information regarding whether or not out-of-order multiple PUSCHs is supported may be defined.

[0197] The first to fourth embodiments may be applied to a UE that supports / reports at least one of the above-mentioned UE capabilities, or may be applied to a UE configured by the network.

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

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

[0200] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

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

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

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

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

[0206] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

[0208] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

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

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

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

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

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

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

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

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

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

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

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

[0220] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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

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

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

[0224] 11 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

[0226] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0228] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

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

[0231] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

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

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

[0237] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0238] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

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

[0240] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0241] The transceiver 120 may transmit first downlink control information for scheduling a first UL channel associated with at least one of a first panel and a transceiver point (TRP), and second downlink control information for scheduling a second UL channel associated with at least one of a second panel and a TRP. The controller 110 may control reception of the first UL channel and the second UL channel. At least a portion of the first UL channel and the second UL channel may be transmitted in the same time domain.

[0242] When UL transmission using multiple panels including at least a first panel and a second panel is supported, the transceiver 120 may transmit a first parameter set commonly to a first UL channel associated with at least one of the first panel and a transmission / reception point (TRP) and a second UL channel associated with at least one of the second panel and a TRP, or a second parameter set separately. The control unit 110 may control the schedules of the first UL channel and the second UL channel using a single piece of downlink control information or multiple pieces of downlink control information. The transceiver 120 may receive the first UL channel and the second UL channel to which the first parameter or the second parameter is applied.

[0243] The transceiver 120 may transmit first downlink control information for scheduling a first UL channel and second downlink control information for scheduling a second UL channel. The controller 110 may control at least one of application of a first UE operation related to the first UL channel transmission and the second UL channel transmission in the time domain and application of a second UE operation related to the transmission order of each downlink control information and each UL channel, based on whether the panels or transmission / reception points (TRPs) corresponding to the first downlink control information and the second downlink control information, respectively, are the same.

[0244] (User Terminal) Fig. 12 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

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

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

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

[0249] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

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

[0251] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

[0255] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

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

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

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

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

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

[0261] The transceiver 220 may receive first downlink control information for scheduling a first UL channel associated with at least one of a first panel and a transmission / reception point (TRP) and second downlink control information for scheduling a second UL channel associated with at least one of a second panel and a TRP. The controller 210 may control transmission of the first UL channel and the second UL channel. At least a portion of the first UL channel and the second UL channel may be transmitted in the same time domain.

[0262] The first UL channel and the second UL channel may correspond to the same number of codewords (e.g., CW=1), or may be transmitted at least partially in the same frequency region, or may be transmitted in different frequency regions set within a predetermined gap range.

[0263] When UL transmission using multiple panels including at least a first panel and a second panel is supported, the transceiver unit 220 may receive first parameters commonly set for a first UL channel associated with at least one of the first panel and a transmission / reception point (TRP) and a second UL channel associated with at least one of the second panel and a TRP, or second parameters separately set for the first UL channel and the second UL channel associated with at least one of the second panel and a TRP. The control unit 210 may apply the first parameters or the second parameters to transmission of the first UL channel and the second UL channel scheduled by a single downlink control information or a plurality of downlink control information.

[0264] The first parameter or the second parameter may be a parameter related to at least one of a codebook subset setting and UL full power transmission. Alternatively, the first parameter or the second parameter may be a parameter related to a maximum rank setting. The control unit 210 may determine a relationship between the maximum rank setting and the ranks to be applied to the first UL channel and the second UL channel based on whether the first UL channel and the second UL channel overlap in the same time domain.

[0265] The transceiver 220 may receive first downlink control information for scheduling a first UL channel and second downlink control information for scheduling a second UL channel. The controller 210 may control at least one of application of a first UE operation related to the first UL channel transmission and the second UL channel transmission in the time domain and application of a second UE operation related to the transmission order of each downlink control information and each UL channel, based on whether the panels or transmission / reception points (TRPs) corresponding to the first downlink control information and the second downlink control information, respectively, are the same.

[0266] The control unit 210 may apply at least one of the first UE operation (restriction) and the second UE operation (restriction) when the panels or transmission / reception points (TRPs) corresponding to the first downlink control information and the second downlink control information are the same. Alternatively, the control unit 210 may not apply at least one of the first UE operation (restriction) and the second UE operation (restriction) when the panels or transmission / reception points (TRPs) corresponding to the first downlink control information and the second downlink control information are different. The control unit 210 may apply the first UE operation (restriction) and the second UE operation (restriction) when the UE does not have a predetermined UE capability.

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

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

[0269] For example, a base station, a user terminal, or the like according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

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

[0271] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0286] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

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

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

[0289] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0290] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0291] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

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

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

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

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

[0296] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

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

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

[0299] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0300] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

[0302] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0303] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0304] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0305] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

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

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

[0308] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0309] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0310] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

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

[0312] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

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

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

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

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

[0317] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

[0319] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0320] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

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

[0324] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

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

[0326] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

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

[0328] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

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

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

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

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

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

[0334] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

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

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

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

[0338] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0339] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0340] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0341] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0342] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0343] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

[0344] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0345] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0346] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

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

[0348] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0349] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. a receiver for receiving a single Downlink Control Information (DCI) for scheduling simultaneous transmission of Uplink (UL) channels associated with a first and a second Transmission / Reception Point (TRP) and a higher layer parameter for maximum rank setting; and a control unit that determines that a rank to be applied to each of the simultaneously transmitted UL channels does not exceed the maximum rank.

2. The terminal described in claim 1, wherein the control unit determines whether or not to apply simultaneous transmission of the UL channels based on the single DCI based on upper layer parameters regarding simultaneous transmission of the UL channels based on the single DCI.

3. The terminal according to claim 1 , wherein the control unit determines a relationship between the maximum rank setting and a rank to be applied to each of the UL channels based on whether the UL channels overlap in a time domain.

4. receiving a single Downlink Control Information (DCI) scheduling simultaneous transmission of uplink (UL) channels associated with a first and a second transmission / reception point (TRP) and higher layer parameters related to a maximum rank setting; determining that a rank to be applied to each of the simultaneously transmitted UL channels does not exceed the maximum rank.

5. a transmitter for transmitting a single Downlink Control Information (DCI) for scheduling simultaneous transmission of Uplink (UL) channels associated with a first and a second Transmission / Reception Point (TRP) and higher layer parameters related to maximum rank setting; A base station comprising: a receiver unit for receiving the simultaneously transmitted UL channels, each of which is assigned a rank not exceeding the maximum rank.

6. A system having a terminal and a base station, The terminal includes a receiver for receiving a single Downlink Control Information (DCI) for scheduling simultaneous transmission of uplink (UL) channels associated with a first and a second transmission / reception point (TRP) and a higher layer parameter related to a maximum rank setting; a control unit that determines that a rank to be applied to each of the UL channels to be simultaneously transmitted does not exceed the maximum rank; The base station includes a transmitter that transmits the single DCI and the higher layer parameters; a receiver for receiving the simultaneously transmitted UL channels.