Terminal, wireless communication method, base station and system

Abstract

A terminal according to one embodiment of the present disclosure is characterized by having: a control unit for determining the spatial relationship of physical uplink shared channels on the basis of the resource of a physical uplink control channel that has the lowest identifier or a control resource set that has the lowest identifier; and a transmission unit for simultaneously transmitting the physical uplink shared channels using a plurality of panels. According to one embodiment of the present invention, it is possible to properly perform simultaneous UL transmissions using a plurality of panels.

Description

[Technical Field]

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) has been specified 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) are also being considered.

[0004] In existing LTE systems (e.g., 3GPP Rel. 8-14), a user equipment (UE) transmits uplink control information (UCI) using at least one of an UL data channel (e.g., a Physical Uplink Shared Channel (PUSCH)) and an UL control channel (e.g., a Physical Uplink Control Channel (PUCCH)). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 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 Summary of the Invention [Problem to be solved by the invention]

[0006] In NR, a UE can use one of multiple panels (multiple beams) for uplink (UL) transmission. However, simultaneous UL transmission using multiple panels has not been fully studied. If simultaneous UL transmission using multiple panels is not performed properly, there is a risk of system performance degradation, such as reduced throughput.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately perform simultaneous UL transmission using multiple panels. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives a configuration related to transmission of a Physical Uplink Shared Channel (PUSCH) through higher layer signaling, and receives a single Downlink Control Information (DCI) that includes two Sounding Reference Signal Resource Indicator (SRI) fields and schedules the PUSCH; a transmitting unit that simultaneously transmits the PUSCH using multiple panels based on the configuration; and a control unit that controls transmission of the PUSCH using the multiple panels in the same time resource and the same frequency resource. and when a specific field included in the single DCI indicates that both of the two SRI fields are to be applied, the control unit applies each SRI field to the same number of layers. It is characterized by: [Effects of the Invention]

[0009] According to one aspect of the present disclosure, simultaneous UL transmission using multiple panels can be performed appropriately. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of the association between precoder types and TPMI indices. [Figure 2] 2A-2C are diagrams illustrating an example of PUSCH transmission using multiple panels. [Figure 3] 3A to 3C are diagrams showing examples of methods 1 to 3 of simultaneous UL transmission using multiple panels. [Figure 4] FIG. 4 is a diagram illustrating an example of PUSCH repeated transmission to which SDM is applied. [Figure 5] Fig. 5A is a diagram showing a first example of PUSCH repeated transmission to which FDM is applied, and Fig. 5B is a diagram showing a second example of PUSCH repeated transmission to which FDM is applied. [Figure 6] FIG. 6 shows an example of a table showing the association between the field values of the precoding information and the number of layers, and the number of layers and TPMI. [Figure 7] FIG. 7 is a diagram illustrating a first example of an extension of a table related to DMRS ports. [Figure 8] FIG. 8 is a diagram illustrating a second example of an extension of a table related to DMRS ports. [Figure 9] FIG. 9 is a diagram illustrating a third example of an extension of a table related to DMRS ports. [Figure 10] FIG. 10 is a diagram illustrating a fourth example of an extension of a table related to DMRS ports. [Figure 11] FIG. 11 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] (Repeated transmission) Rel. 15 supports repeated transmission in data transmission. For example, a base station (network (NW), gNB) may repeat transmission of DL data (e.g., downlink shared channel (PDSCH)) a predetermined number of times. Alternatively, a UE may repeat transmission of UL data (e.g., uplink shared channel (PUSCH)) a predetermined number of times.

[0012] The UE may be scheduled for a predetermined number of repetitions of PUSCH transmissions by a single DCI, which may also be referred to as a repetition factor K or aggregation factor K.

[0013] The n-th repetition may also be referred to as the n-th transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K−1). The repetitive transmission may be applied to a PUSCH that is dynamically scheduled in DCI (e.g., a dynamic grant-based PUSCH) or a configured grant-based PUSCH.

[0014] The UE semi-statically receives information indicating the repetition factor K (e.g., aggregationFactorUL or aggregationFactorDL) through higher layer signaling. Here, 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.

[0015] 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), etc.

[0016] The UE controls reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) of the PDSCH or transmission processing (e.g., at least one of transmission, mapping, modulation, and coding) of the PUSCH for K consecutive slots based on at least one of the following field values (or information indicated by the field value) in the DCI: Allocation of time domain resources (e.g., starting symbol, number of symbols in each slot, etc.), Allocation of frequency domain resources (e.g., a predetermined number of resource blocks (RBs) and a predetermined number of resource block groups (RBGs)), Modulation and Coding Scheme (MCS) index, Configuration of the PUSCH demodulation reference signal (DMRS: Demodulation Reference Signal), PUSCH spatial relation info or Transmission Configuration Indication (TCI) state (TCI-state).

[0017] The same symbol allocation may be applied to K consecutive slots. The UE may determine the symbol allocation for each slot based on the start symbol S and the number of symbols L (e.g., Start and Length Indicator (SLIV)) determined based on the value m of a predetermined field in the DCI (e.g., the Time Domain Resource Allocation (TDRA) field). The UE may also determine the first slot based on K2 information determined based on the value m of a predetermined field in the DCI (e.g., the TDRA field).

[0018] On the other hand, among the K consecutive slots, the redundancy versions (RVs) applied to TBs based on the same data may be the same or at least partially different. For example, the RV applied to the TB in the n-th slot (transmission opportunity, repetition) may be determined based on the value of a predetermined field (e.g., RV field) in the DCI.

[0019] In Rel. 15, the PUSCH can be repeatedly transmitted across multiple slots (in slot units). In Rel. 16 and later, repeated transmission of the PUSCH in units shorter than slots (for example, in subslot units, minislot units, or units of a predetermined number of symbols) is supported.

[0020] The UE may determine symbol allocation for PUSCH transmission (e.g., PUSCH with k=0) in a predetermined slot based on the start symbol S and the number of symbols L determined based on the value m of a predetermined field (e.g., the TDRA field) in the DCI of the PUSCH. Note that the UE may determine the predetermined slot based on Ks information determined based on the value m of a predetermined field (e.g., the TDRA field) of the DCI.

[0021] The UE may dynamically receive information indicating the repetition factor K (e.g., number of repetitions) via downlink control information. The repetition factor may be determined based on the value m of a predetermined field (e.g., the TDRA field) in the DCI. For example, a table may be supported that defines the correspondence between the bit value notified by the DCI, the repetition factor K, the start symbol S, and the number of symbols L.

[0022] Slot-based repetitive transmission may be referred to as repetition transmission type A (eg, PUSCH repetition Type A), and sub-slot-based repetitive transmission may be referred to as repetition transmission type B (eg, PUSCH repetition Type B).

[0023] The UE may be configured to apply at least one of repetitive transmission type A and repetitive transmission type B. For example, the base station may notify the UE of the repetitive transmission type applied by the UE by higher layer signaling (e.g., PUSCHRepTypeIndicator).

[0024] For each DCI format that schedules the PUSCH, either the repetitive transmission type A or the repetitive transmission type B may be configured in the UE.

[0025] For example, for a first DCI format (e.g., DCI format 0_1), if higher layer signaling (e.g., PUSCHRepTypeIndicator-AorDCIFormat0_1) is set to repetitive transmission type B (e.g., PUSCH-RepTypeB), the UE applies repetitive transmission type B for PUSCH repetitive transmissions scheduled in the first DCI format. Otherwise (e.g., if PUSCH-RepTypeB is not set or if PUSCH-RepTypA is set), the UE applies repetitive transmission type A for PUSCH repetitive transmissions scheduled in the first DCI format.

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

[0027] For example, it is being considered that a UE uses at least a sounding reference signal (SRS) resource indicator (SRI) to determine a precoder (precoding matrix) for CB-based and / or NCB-based Physical Uplink Shared Channel (PUSCH) transmission.

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

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

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

[0031] 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, and the like, or a combination thereof.

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

[0033] The UE may determine a 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.

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

[0035] Fully coherent may mean that all antenna ports used for transmission are synchronized (may also be expressed as being able to match the phase, being able to control the phase for each coherent antenna port, being able to apply a precoder appropriately for each coherent antenna port, 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.

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

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

[0038] 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 the DCI (e.g., DCI format 0_1, etc.) that schedules the UL transmission.

[0039] Figure 1 shows an example of the association between precoder types and TPMI indices. Figure 1 corresponds to a table of precoding matrix W for single-layer (rank 1) transmission using four antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, in which transform precoding is effective).

[0040] In FIG. 1, when the precoder type (codebookSubset) is fullyAndPartialAndNonCoherent, the UE is notified of a TPMI of one of 0 to 27 for single layer transmission. When the precoder type is partialAndNonCoherent, the UE is configured with a TPMI of one of 0 to 11 for single layer transmission. When the precoder type is noncoherent, the UE is configured with a TPMI of one of 0 to 3 for single layer transmission.

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

[0042] Non-coherent and partially coherent codebooks may be referred to as antenna selection precoders, and fully coherent codebooks may be referred to as non-antenna selection precoders.

[0043] 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 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, codebooks with TPMI=4 to 11).

[0044] In the present disclosure, a fully coherent codebook may refer 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 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, codebooks with TPMI=12 to 27).

[0045] (Spatial relations for SRS, PUSCH) The UE may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used to transmit a measurement reference signal (for example, a sounding reference signal (SRS)).

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

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

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

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

[0050] Furthermore, the use ("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 use of 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.

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

[0052] The SRS resource information may include an SRS resource ID (SRS-ResourceId), an SRS port number, an 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.

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

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

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

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

[0057] In NR, 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).

[0058] In addition, BC may also be called transmit / receive beam correspondence (Tx / Rx beam correspondence), beam reciprocity, beam calibration, calibrated / non-calibrated, reciprocity calibrated / non-calibrated, correspondence, agreement, etc.

[0059] For example, without 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 measurement results of one or more SRSs (or SRS resources).

[0060] On the other hand, when BC is present, the UE may transmit an uplink signal (e.g., PUSCH, PUCCH, 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).

[0061] When the UE is configured with spatial relationship information regarding the SSB or CSI-RS and the SRS 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.

[0062] When the UE is configured with spatial relationship information between another SRS (reference SRS) and the SRS (target SRS) for a resource of the SRS (target SRS) (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 (spatial domain transmit filter) for transmitting the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

[0063] 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). Specifically, the UE may use spatial relationship information of the SRS resource (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

[0064] 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 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 DCI (a 2-bit predetermined field). To use a spatial relationship other than the two or four spatial relationships configured by RRC, RRC reconfiguration is required.

[0065] 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 the MAC CE.

[0066] (UL TCI condition) In Rel.16 NR, the use of UL TCI status as a UL beam indication method is being considered. The notification of the UL TCI status is similar to the notification of the UE's DL beam (DL TCI status). Note that the DL TCI status may be interchangeably read as the TCI status for PDCCH / PDSCH.

[0067] The channel / signal (which may be referred to as a target channel / RS) to which the UL TCI state is set (specified) may be, for example, at least one of a PUSCH (DMRS of PUSCH), a PUCCH (DMRS of PUCCH), a random access channel (Physical Random Access Channel (PRACH)), an SRS, etc.

[0068] Furthermore, the RS (source RS) that has a QCL relationship with the channel / signal may be, for example, a DL RS (e.g., SSB, CSI-RS, TRS, etc.) or a UL RS (e.g., SRS, SRS for beam management, etc.).

[0069] In the UL TCI state, an RS that has a QCL relationship with the channel / signal may be associated with a panel ID for receiving or transmitting the RS, and the association may be explicitly configured (or specified) or implicitly determined by higher layer signaling (e.g., RRC signaling, MAC CE, etc.).

[0070] The correspondence between the RS and the panel ID may be set by being included in the UL TCI state information, or may be set by being included in at least one of the resource setting information, spatial relationship information, etc. of the RS.

[0071] The QCL type indicated by the UL TCI state may be the existing QCL type AD or may be another QCL type, and may include a predetermined spatial relationship, associated antenna ports (port index), etc.

[0072] When a UE is assigned an associated panel ID for an UL transmission (e.g., specified by DCI), the UE may perform the UL transmission using the panel corresponding to the panel ID. The panel ID may be associated with a UL TCI state, and when a UL TCI state is assigned (or activated) for a given UL channel / signal, the UE may identify the panel to use for the UL channel / signal transmission according to the panel ID associated with the UL TCI state.

[0073] (Multiple panel submission) <Transmission method> In Rel. 15 and Rel. 16 UEs, only one beam and panel are used for UL transmission at a time (Figure 2A). From Rel. 17 onwards, simultaneous UL transmission using multiple beams and panels for one or more TRPs is being considered to improve UL throughput and reliability. The following describes simultaneous transmission of PUSCH, but a similar process can also be used for PUCCH.

[0074] For simultaneous UL transmission using multiple beams and multiple panels, reception by one TRP with multiple panels (Fig. 2B) or reception by two TRPs with an ideal backhaul (Fig. 2C) is considered. A single PDCCH is considered for scheduling multiple PUSCHs (e.g., simultaneous transmission of PUSCH#1 and PUSCH#2). Panel-specific transmission is considered to be supported, and a panel ID is introduced.

[0075] The base station may use the UL TCI or Panel ID to configure or indicate panel-specific transmission for UL transmission. The UL TCI (UL TCI state) may be based on signaling similar to the 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. If 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).

[0076] The multi-panel UL transmission method or candidate multi-panel UL transmission method may be at least one of the following methods 1 to 3 (multi-panel UL transmission methods 1 to 3). Only one of methods 1 to 3 may be supported. Multiple methods including at least one of methods 1 to 3 may be supported, and one of the multiple methods may be configured in the UE.

[0077] 《Method 1》 Coherent multi-panel UL transmission

[0078] Multiple panels may be synchronized with each other. All layers are mapped to all panels. Multiple analog beams may be directed. The SRS Resource Indicator (SRI) field may be extended. This scheme may use up to 4 layers for the UL.

[0079] In the example of FIG. 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. Panel #1 and Panel #2 are coherent. 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.

[0080] 《Method 2》 Non-coherent multi-panel UL transmission of one codeword (CW) or transport block (TB)

[0081] Multiple panels may not be synchronized. Different layers are mapped to one CW or TB for different panels and PUSCHs from multiple panels. A layer corresponding to one CW or TB may be mapped to multiple panels. This scheme may use up to four layers or up to eight layers for the UL. If up to eight layers are supported, this scheme may support one CW or TB using up to eight layers.

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

[0083] 《Method 3》 Two CW or TB non-coherent multi-panel UL transmitters

[0084] The plurality of panels do not have to be synchronized. Different layers are mapped to different panels and to two CWs or TBs for PUSCH from the plurality of panels. A layer corresponding to one CW or TB may be mapped to one panel. Layers corresponding to a plurality of CWs or TBs may be mapped to different panels. This method may use up to 4 layers or up to 8 layers for UL. When supporting up to 8 layers, this method may support up to 4 layers per CW or TB.

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

[0086] <DCI Extension> When applying the above-described Methods 1 to 3, an existing DCI may be extended. For example, at least one of the following Options 1 to 6 may be applied.

[0087] [Option 1] A plurality of PUSCHs may be indicated (scheduled) by a single PDCCH (DCI) for Method 1. The SRI field may be extended to indicate a plurality of PUSCHs. A plurality of SRI fields in the DCI may be used to indicate a plurality of PUSCHs from a plurality of panels. For example, a DCI that schedules two PUSCHs may include two SRI fields.

[0088] The extension of the SRI field for Method 2 may be different from the extension of the SRI field for Method 1 in the following points.

[0089] For layers 1, 2, ..., k among the L layers, the UE may use the SRI (SRS#i) indicated first by the SRI field in the DCI as the spatial filter for UL transmission from panel 1. For the remaining layers k+1, k+2, ..., L among the L layers, the UE may use the SRI (SRS#j) indicated second by the SRI field in the DCI as the spatial filter for UL transmission from panel 2. k may follow a predefined rule or may be explicitly indicated by the DCI.

[0090] In addition to the extension of the SRI field for Scheme 2 to support two CWs or TBs for different TRPs, at least one of the following fields in the DCI may be extended to indicate multiple PUSCHs: modulation and coding scheme (MCS) field, precoding information and number of layers field, transmission power control (TPC) command for scheduled PUSCH field, frequency domain resource assignment field, and time domain resource assignment field. Different TRPs may have different path losses or SINRs.

[0091] [Option 2] Information regarding the repetition transmission type of the PUSCH may be notified to or configured in the UE by higher layer signaling. For example, if repetition transmission type B (e.g., PUSCH-RepTypeB) is not configured by higher layer signaling, the UE may apply repetition transmission type A. The repetition transmission type may be configured for each DCI format (or PUSCH type). The PUSCH type may include a dynamic grant-based PUSCH and a configuration grant-based PUSCH.

[0092] Information regarding the repetition factor, information regarding the PUSCH allocation, information regarding the spatial relationship (or precoder) to be used for PUSCH transmission, and information regarding the redundancy version to be used for PUSCH transmission may be notified to the UE by DCI or a combination of DCI and higher layer parameters.

[0093] For information on the repetition factor (e.g., K) and information on PUSCH allocation (e.g., start symbol S and PUSCH length L), multiple candidates may be defined in a table, and a specific candidate may be selected by DCI. In the following description, an example will be given in which the PUSCH repetition factor (K) is 4, but the applicable repetition factor is not limited to 4.

[0094] As for information regarding spatial relationships (hereinafter also referred to as spatial relationship information), multiple candidates may be set by higher layer signaling, and one or more pieces of spatial relationship information may be activated by at least one of DCI and MAC CE.

[0095] [Option 3] The following describes the number of bits in the TPC command field included in one DCI that schedules PUSCH transmissions across multiple TRPs, and the association between the TPC command field and a TPC-related index (e.g., a closed-loop index). A UE may control multiple PUSCH transmissions based at least on the index.

[0096] The number of bits of the TPC command field included in one DCI scheduling PUSCH transmission across multiple TRPs may be extended to a specific number (e.g., 2M) compared to the number of bits in Rel. 15 / 16. In the present disclosure, M may be the number of TRPs or the number of SRIs that may be indicated for PUSCH transmission across multiple TRPs.

[0097] For example, for codebook-based transmission, when the SRI for PUSCH transmission for two TRPs is indicated by the DCI, the TPC command field may be extended to 4 bits.

[0098] The correspondence between the extended TPC command field and a specific index (e.g., closed-loop index) related to the TPC may follow at least one of the following correspondence 1 and correspondence 2. Although the closed-loop index will be described below, the closed-loop index in the present disclosure may be replaced with any specific index related to the TPC.

[0099] [[Mapping 1]] If the extended TPC command field is divided into a specific number of bits (e.g., 2, 4, etc.), the xth (x being any integer) smallest (or largest) specific number of bits may be associated with the xth SRI / SRI combination indicated by the DCI.

[0100] [[Mapping 2]] If the extended TPC command field is divided into a specific number (e.g., two) of bits, the x-th smallest (or largest) specific number of bits may be associated with the SRI corresponding to the x-th smallest (or largest) closed-loop index indicated by the DCI.

[0101] [Option 4] When PUSCHs are repeatedly transmitted across multiple TRPs, the same number of antenna ports may be configured / instructed for different TRPs (different PUSCHs). In other words, the same number of antenna ports may be configured / instructed in common for multiple TRPs (multiple PUSCHs). In this case, the UE may assume that the same number of antenna ports is configured / instructed in common for multiple TRPs (multiple PUSCHs). In this case, the UE may determine the TPMI for PUSCH transmission according to at least one of Indication Method 1-1 or Indication Method 1-2 described below.

[0102] [[Instruction method 1-1]] The precoding information and number of layers field included in the scheduling DCI may have the same number of bits as specified in Rel.15 / 16. In this case, one precoding information and number of layers field included in one DCI may be indicated to the UE. In other words, the UE may determine a TPMI based on one precoding information and number of layers field included in one DCI. Then, the UE may apply the precoding information and number of layers field / TPMI to PUSCH transmissions of different TRPs.

[0103] [[Instruction method 1-2]] The number of bits of the precoding information and layer number fields included in the scheduling DCI may be expanded to a specific number compared to Rel. 15 / 16. The specific number may be represented as X×M.

[0104] The above X may be determined based on the size of the precoding information and the number of layers field included in the DCI for UL transmission for one TRP. For example, the above X may be determined based on at least one of the number of antenna ports and a number set by a specific upper layer parameter (e.g., at least one of ul-FullPowerTransmission, maxRank, codebookSubset, and transformPrecoder).

[0105] Alternatively, X may be a fixed value. The UE may assume that X has a fixed size regardless of the number of antenna ports configured by a higher layer. The UE may also assume that X has a fixed size regardless of the value of the Number of Antenna Ports field (the number of antenna ports indicated by the Number of Antenna Ports field).

[0106] Furthermore, when PUSCHs are repeatedly transmitted across multiple TRPs, different or the same number of antenna ports may be configured / instructed for different TRPs (different PUSCHs). In other words, the number of antenna ports may be configured / instructed separately for multiple TRPs (multiple PUSCHs). In this case, the UE may assume that the number of antenna ports is configured / instructed independently for each of the multiple TRPs (multiple PUSCHs). In this case, the UE may determine the TPMI for PUSCH transmission according to Indication Method 2 described below.

[0107] [[Instruction method 2]] The precoding information and layer number fields included in the scheduling DCI may have a bit number that is expanded to a specific number compared to Rel. 15 / 16. The specific number is X1 + X2 + ... + X M It may be expressed as:

[0108] Above X i (i is an integer from 1 to M) may be determined based on the size of the precoding information and layer number field included in the DCI for UL transmission of the i-th TRP. For example, the above X i may be determined based on at least one of the number of antenna ports and the number set by a specific upper layer parameter (e.g., at least one of ul-FullPowerTransmission, maxRank, codebookSubset, and transformPrecoder). i may be set to a fixed value.

[0109] The above M may be the number of TRPs or the number of spatial relationship information (SRI) that can be indicated for PUSCH transmission across multiple TRPs.

[0110] [Option 5] The UE may determine the SRI to apply to the PUSCH based on at least one of the SRI field of the DCI that schedules the PUSCH and the CORESET pool index of the control resource set (CORESET) for the DCI (e.g., where the DCI is detected).

[0111] The UE may determine the SRI to apply to each PUSCH based on multiple SRI fields included in the DCI scheduling the multiple PUSCHs.

[0112] The UE may determine the SRI to apply to each PUSCH based on one SRI field included in the DCI that schedules multiple PUSCHs.

[0113] The UE may determine the transmit power of the PUSCH based on the SRI field of the DCI that schedules the PUSCH. For example, the UE may determine transmit power control (TPC)-related parameters of the PUSCH based on the SRI field of the DCI that schedules the PUSCH.

[0114] [Option 6] The UE may decide to perform either repeated transmission for a single TRP or repeated transmission for multiple TRPs based on a specific field included in the DCI.

[0115] For example, when a field included in the DCI indicates that one of the first SRI field or the second SRI field is to be applied among multiple (e.g., two) SRI fields (a first SRI field and a second SRI field), the UE may determine that repeated transmission of multiple PUSCHs is to be performed at the applied SRI. In other words, when a field included in the DCI indicates that one SRI field is to be applied among multiple SRI fields, the UE may determine to perform repeated transmission of PUSCHs in a single TRP.

[0116] Furthermore, for example, when a field included in DCI indicates that both a first SRI field and a second SRI field among multiple (e.g., two) SRI fields (a first SRI field and a second SRI field) are to be applied, the UE may determine that repeated transmission of multiple PUSCHs is to be performed in multiple SRIs (e.g., multiple TRPs). In other words, when a field included in DCI indicates that multiple SRI fields are to be applied, the UE may determine to perform repeated transmission of PUSCHs in multiple TRPs.

[0117] (Problem) As described above, DCI extensions and the like for the examples of Schemes 1 to 3 have been studied. However, the details of the operation of simultaneous UL transmission using multiple beams and multiple panels have not been fully studied. For example, it is conceivable that multiple (multiple sets) SRI / TPMI / TPC are indicated. However, how to map the DMRS port of each PUSCH to each PUSCH / SRI / TPMI / TPC has not been fully studied. If simultaneous UL transmission using multiple panels is not performed appropriately, there is a risk of degradation in system performance, such as a decrease in throughput. Therefore, the present inventors have conceived a method for a UE to appropriately perform simultaneous UL transmission using multiple panels.

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

[0119] In the present disclosure, beam, 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, CORESET group, and CORESET pool may be read as interchangeable.

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

[0121] In the present disclosure, spatial relationship, spatial configuration, spatial relationship information, spatialRelationInfo, SRI, SRS resource, precoder, UL TCI, TCI state, Unified TCI, QCL, etc. may be read interchangeably.

[0122] In the present disclosure, the terms index, ID, indicator, and resource ID may be read interchangeably.

[0123] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP (MTRP) system based on single DCI, sDCI-based MTRP, scheduling multiple PUSCHs (corresponding to different SRIs) using one DCI, sDCI-based MTRP transmission, and activating two TCI states on at least one TCI codepoint may be read interchangeably.

[0124] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, mDCI-based MTRP transmission, use of multi-DCI for MTRP, scheduling of multiple PUSCHs (corresponding to different SRIs) using two DCIs, and setting two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read interchangeably.

[0125] In the present disclosure, the terms activate, deactivate, indicate, select, configure, update, determine, etc. may be read interchangeably.

[0126] In this disclosure, the terms repetition (one repetition), occasion, and channel may be interchangeable. In this disclosure, the terms UL data, TB, CW, and UCI may be interchangeable.

[0127] In the present disclosure, "A / B" may be read as "at least one of A and B." The transmission method and new transmission method of the present disclosure may mean at least one of the above-mentioned methods 1 to 3.

[0128] (Wireless communication method) In the first and second embodiments, the UE receives configuration related to transmission of a Physical Uplink Shared Channel (PUSCH) via higher layer signaling (RRC), and then transmits the PUSCH simultaneously using multiple panels, either coherent (first embodiment) or non-coherent (second embodiment), based on the configuration.

[0129] First Embodiment The PUSCH generation (transmission) operation when applying the coherent multi-panel UL transmission shown in the above-described Method 1 has not been sufficiently studied. Therefore, the inventors of the present invention conceived a method for appropriately performing PUSCH generation when applying coherent multi-panel UL transmission. In Method 1, multiple TRPs may be applied, and the two panels may be panels of different TRPs.

[0130] Note that Method 1 may be applied to a high speed train (HST)-single frequency network (SFN). For example, a plurality of small antennas (transmission / reception points) having the same cell ID and a predetermined distance form an SFN. During high-speed movement, transmission / reception points in the unit of several kilometers form one cell. Handover is performed when crossing cells.

[0131] In NR, in order to communicate with a UE included in a moving body (HST) such as a train moving at high speed, it is assumed to use a beam transmitted from a transmission point (for example, Remote Radio Head (RRH)). In an existing system (for example, Rel. 15), it is supported to transmit a unidirectional beam from the RRH to communicate with a moving body. By applying Method 1, the UL reliability during high-speed movement such as HST can be improved.

[0132] With the new RRC configuration, the UE can be scheduled to simultaneously transmit two PUSCH / CW / TBs, and the two PUSCH / CW / TBs may be the same. Or the two PUSCHs may be regarded as one PUSCH that is repeatedly transmitted simultaneously.

[0133] Regarding simultaneous PUSCH transmission based on a single DCI (scheduled by a single DCI), SRI / TPMI / TPC may use a DCI extended as shown in the above-described <DCI extension>.

[0134] For DMRS transmission of PUSCH, the UE may assume that multiple indicated SRIs (in case of CB-based PUSCH transmission) / multiple SRI sets (in case of NCB-based PUSCH transmission) for different PUSCH / CW / TB are applied to each DMRS port (each layer) of the PUSCH.

[0135] For time / frequency resource indication for recurring PUSCH, one of the following options may be applied:

[0136] [Option 1] The UE may assume that PUSCH repeat transmissions employing Space Division Multiplexing (SDM) are scheduled on the same time and frequency resources. That is, when using coherent panels, the UE may transmit PUSCH repeat transmissions employing SDM on the same time and frequency resources. Figure 4 is a diagram showing an example of PUSCH repeat transmissions employing SDM. In Figure 4, the time and frequency resources of the repeated PUSCHs A and B are the same.

[0137] [Option 2] The UE may assume that PUSCH repeat transmissions employing Frequency Division Multiplexing (FDM) are scheduled on the same time resources but different frequency resources. That is, when using multiple coherent panels, the UE may transmit PUSCH repeat transmissions employing FDM on the same time resources but different frequency resources. Figure 5A illustrates a first example of PUSCH repeat transmission employing FDM. In Figure 5A, the time resources of PUSCH A and PUSCH B, which are repeats, are the same but the frequency resources are different.

[0138] The UE may assume that for repeated PUSCH transmission using FDM, some (one or more symbols) are scheduled on overlapping time resources and different frequency resources. Figure 5B is a diagram showing a second example of repeated PUSCH transmission using FDM. In Figure 5B, some (one or more symbols) of the time resources of repeated PUSCH A and PUSCH B overlap, but the frequency resources are different.

[0139] [Variations] With the new RRC configuration, the UE may transmit one PUCCH repeatedly at the same time with SDM. The PUCCH resources may be configured with two TCI states / spatial relationships. For DMRS transmission of the PUCCH, the UE may assume that the two indicated TCI states / spatial relationships apply to each DMRS port of the PUCCH. The UE may assume that the PUCCH repeated transmissions with SDM are scheduled on the same time / frequency resources.

[0140] According to this embodiment, the UE can appropriately perform a PUSCH generation (transmission) operation when coherent multi-panel UL transmission is applied.

[0141] <Second embodiment> The mapping of DMRS ports when one / two CW or TB non-coherent multi-panel UL transmission is applied as shown in the above-mentioned Method 2 or Method 3 has not been sufficiently considered. For example, when multiple (multiple sets of) SRI / TPMI / TPC are specified, the mapping of DMRS ports corresponding to each PUSCH / SRI / TPMI / TPC has not been sufficiently considered. Therefore, the present inventors have come up with a method for appropriately mapping DMRS ports when one / two CW or TB non-coherent multi-panel UL transmission is applied.

[0142] When the new RRC configuration is used, the UE may be scheduled to simultaneously transmit one or two PUSCHs / CWs / TBs with different data / layers on different beams / panels to different TRPs. When this new RRC configuration is used, if multiple (multiple sets) of SRIs / TPMIs / TPCs are indicated in the DCI scheduling the PUSCHs, the following aspects 2-1 to 2-3 may be applied.

[0143] In aspects 2-1 to 2-3, when multiple non-coherent panels are used, the UE receives downlink control information (DCI) including at least one of a measurement reference signal resource indicator (SRI), a transmit precoding matrix index (TPMI), and a transmit power control command (TPC command) corresponding to a code division multiplexing (CDM) group.The UE then transmits a PUSCH based on the DCI.In the present disclosure, TPC and TPC command may be interpreted as interchangeable.

[0144] [Aspect 2-1] If the DCI field "Antenna Port(s)" indicates DM-RS ports in two CDM groups, the first (first set) SRI / TPMI / TPC may correspond to the CDM group of the first antenna port indicated by the antenna port indication table, and the second (second set) SRI / TPMI / TPC may correspond to the other CDM group.

[0145] [Aspect 2-2] If the DCI field "Antenna Port(s)" indicates a DM-RS port in the three CDM groups, any of the following options 1 to 3 may be applied.

[0146] [[Option 1]] The first (first set) SRI / TPMI / TPC corresponds to the CDM group of the first and second antenna ports shown in the antenna port indication table, and the second (second set) SRI / TPMI / TPC corresponds to the third CDM group.

[0147] [[Option 2]] The first (first set) SRI / TPMI / TPC corresponds to the CDM group of the first antenna port shown in the antenna port indication table, and the second (second set) SRI / TPMI / TPC corresponds to the second and third CDM groups.

[0148] [[Option 3]] In the new transmission schemes of multi-panel transmission (eg, at least one of schemes 1 to 3 above), the UE does not expect to be presented with three CDM groups.

[0149] [Aspect 2-3] If the DCI field "Antenna Port(s)" indicates a DM-RS port within one CDM group, the following options 1 or 2 may be applied.

[0150] [[Option 1]] The UE does not assume DM-RS ports in the CDM group indicated by multiple (multiple sets) SRI / TPMI / TPC.

[0151] [[Option 2]] A new codeword-layer mapping table may be defined to indicate two indications for each entry: layer (for the two panels) and TPMI. Figure 6 shows an example of the association (table) between the field values of precoding information and layer number, and the layer number and TPMI. This table is for four antenna ports when transform precoding is disabled and the maximum rank (maxRank) is 2, 3, or 4.

[0152] In this table, when only Panel #1 is used, the number of layers is expressed as "L layers", and when Panels #1 and #2 are used, the number of layers k for Panel #1 and the number of layers L - k for Panel #2 are expressed as "k+(L - k) layers". In this table, for 2 layers (L = 2), the number of layers for Panel #1 may be 1 (k = 1) and the number of layers for Panel #2 may be 1. In this table, 2 layers may be expressed as "2 layers" or as "1+1 layers".

[0153] Furthermore, for one or two PUSCH / CW / TBs having different data / layers from different beams / panels, the UE does not assume different DM-RS settings with respect to the actual number of front-loaded DM-RS symbols, the actual number of additional DM-RS symbols, the location of the actual DM-RS symbols, and the DM-RS configuration type.

[0154] When performing DCI extension for single DCI-based simultaneous PUSCH transmission, for SRI / TPMI / TPC having multiple indications, the examples of <DCI extension> described above may be applied.

[0155] [Expansion of the table showing DMRS ports] To support different layer mappings between two PUSCHs for two TRPs, an expansion of the table showing DMRS ports may be performed. For example, in the case of two DMRS CDM groups with rank = 3, in addition to 2+1 layers, 1+2 layers may be supported.

[0156] Fig. 7 is a diagram showing a first example of an extension of a table related to DMRS ports. Fig. 7 shows an extension of a table related to DMRS antenna ports when the precoder is disabled, DMRS type=1, maximum length=1, and rank=3. The maximum length is the number of OFDM symbols of the DMRS to be DL frontloaded. "Value" in Figs. 7 to 10 indicates the value of the DCI field "Antenna Port(s)." In Fig. 7, a column has been added in which "value" is 2 or 1, the number of DMRS CDM groups without data is 2, and the DMRS ports are 0, 2, and 3.

[0157] Figure 8 shows a second example of a table extension for DMRS ports. Figure 8 shows a table extension for DMRS antenna ports when the precoder is disabled, DMRS type=1, max length=2, and rank=3. In Figure 8, a column is added where "value" is 3, the number of DMRS CDM groups without data is 2, the DMRS ports are 0, 2, and 3, and the number of frontloaded symbols is 1.

[0158] Figure 9 shows a third example of a table extension for DMRS ports. Figure 9 shows a table extension for DMRS antenna ports when the precoder is disabled, DMRS type=2, max length=1, and rank=3. In Figure 9, a column is added where "value" is 3, the number of DMRS CDM groups with no data is 2, and DMRS ports are 0, 2, and 3.

[0159] Figure 10 shows a fourth example of a table extension for DMRS ports. Figure 10 shows a table extension for DMRS antenna ports when the precoder is disabled, DMRS type=2, max length=2, and rank=3. In Figure 10, a column is added where "value" is 6, the number of DMRS CDM groups without data is 2, the DMRS ports are 0, 2, and 3, and the number of frontloaded symbols is 1.

[0160] <Third embodiment> When spatial relationships are indicated for PUSCHs in DCI format 0_0 or in some cases (Cases 1 and 2 below), how to determine the spatial relationships of PUSCHs in a new transmission scheme (e.g., at least one of Schemes 1 to 3 above) has not been fully considered. For example, the spatial relationships of PUSCHs may differ between single-DCI-based PUSCH scheduling and multi-DCI-based PUSCH scheduling. Therefore, the present inventors have devised a method for appropriately assuming (determining) the spatial relationships of PUSCHs.

[0161] In this embodiment, a UE receives downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH), and determines the spatial relationship of the PUSCH based on the physical uplink control channel resource (PUCCH resource) with the lowest identifier (ID) or the control resource set (CORESET) with the lowest identifier (ID).Then, the UE uses multiple panels to simultaneously transmit the PUSCH.

[0162] In the present disclosure, the PUCCH resource with the lowest ID may be read as the PUCCH resource with the lowest PUCCH resource ID, and the TCI state / spatial relationship with the lowest ID may be read as the TCI state / spatial relationship with the lowest TCI state ID / spatial relationship information ID.

[0163] [Case 1] In PUSCH scheduling with DCI format 0_0 on a cell, the UE transmits the PUSCH according to a spatial relationship that corresponds to the dedicated PUCCH resource with the lowest ID, if available, within the active UL BWP of that cell.

[0164] That is, in Case 1, the PUSCH spatial relationship follows the PUCCH resource with the lowest ID. Case 1 is applied in 3GPP Rel. 15 and 16.

[0165] [Case 2] For PUSCH scheduling with DCI format 0_0 in a cell, if the higher layer parameter "enableDefaultBeamPlForPUSCH0_0" is set to 'enabled' and the UE is in RRC connected mode with no PUCCH resources configured in the active UL BWP, the UE transmits PUSCH according to a spatial relationship, if available, that refers to the RS with QCL type D corresponding to the QCL assumption of the CORESET with the lowest ID in the active DL BWP of the cell.

[0166] For PUSCH scheduling with DCI format 0_0 in a cell, if the higher layer parameter "enableDefaultBeamPlForPUSCH0_0" is set to 'enabled', the UE is configured with PUCCH resources in an active UL BWP, no spatial relationship is configured for all PUCCH resources, and the UE is in RRC connected mode, the UE transmits PUSCH according to the spatial relationship. If available, the spatial relationship refers to the RS with QCL type D corresponding to the QCL assumption of the CORESET with the lowest ID in the active DL BWP of the cell in case a CORESET is configured in the cell.

[0167] That is, in Case 2, the PUSCH spatial relationship follows the QCL of the CORESET with the lowest ID. Case 2 is applied in 3GPP Rel.16.

[0168] [Aspect 3-1] When new RRC parameters for indicating the above-mentioned schemes 1, 2, and 3 for PUSCH are configured, it is assumed that the UE is scheduled for simultaneous transmission of UL beams / panels using schemes 1, 2, and 3, and the UL is scheduled by a single DCI, in the above-mentioned case 1, the UE assumes PUSCH spatial relationships based on PUCCH resources as shown in the following options 1 to 4. Note that the UE may perform similar processing in case 2 when the higher layer parameter "enableDefaultBeamPlForPUSCH0_0" is not set to 'enabled'.

[0169] [[Option 1]] The UE may follow the existing method shown in Cases 1 and 2. That is, in this case, the UE may not predict that simultaneous transmissions of UL beams / panels will be scheduled. Instead, the UE may predict that PUSCH transmissions by one UL beam / panel will be scheduled.

[0170] [[Option 2]] The UE expects that one or more PUCCH resources are configured with two TCI state / spatial relationships. The PUSCH spatial relationship of the new transmission scheme may be determined according to the two TCI state / spatial relationships of the PUCCH resource with the lowest ID (PUCCH resource ID) among the one or more PUCCH resources, the TCI state / spatial relationship with the lowest ID (TCI state ID / spatial relationship information ID) from the two PUCCH resources with the lowest ID among the one or more PUCCH resources, or the TCI state / spatial relationship with the two lowest IDs. That is, a multi-panel UE configured for UL multi-beam / panel simultaneous transmission may also be configured for DL multi-beam / panel reception from multiple TRPs.

[0171] [[Option 3]] When one or more PUCCH resources are configured with two TCI state / spatial relationships, the PUSCH spatial relationship may be determined according to the two TCI state / spatial relationships of the PUCCH resource with the lowest ID among the one or more PUCCH resources, the TCI state / spatial relationship with the lowest ID from the two PUCCH resources with the lowest ID among the one or more PUCCH resources, or the TCI state / spatial relationship with the two lowest IDs.

[0172] When one or more PUCCH resources are configured with one TCI state / spatial relationship, the PUSCH spatial relationship may be determined according to the two TCI state / spatial relationships from the two PUCCH resources with the lowest IDs among the one or more PUCCH resources, or the two TCI state / spatial relationships with the lowest IDs among the two PUCCH resources.

[0173] In Option 2 / 3, if a PUCCH resource is configured with more than two TCI states / spatial relations, the PUSCH spatial relation may be determined according to the two TCI states / spatial relations of the PUCCH resources with the lowest IDs, the TCI state / spatial relation with the lowest ID from the two PUCCH resources with the lowest IDs, or the TCI state / spatial relation with the two lowest IDs. For example, if repeated transmission is applied between MTRPs, there may be PUCCH resources with more than two TCI states / spatial relations.

[0174] [[Option 4]] If a PUCCH resource is configured with one TCI state / spatial relationship, the PUSCH spatial relationship may be determined according to the two PUCCH spatial relationships of the PUCCH resources with the lowest and second lowest IDs. Option 4 may be applied to multiple PUCCH resources with different spatial relationship settings. The PUSCH spatial relationship in Option 4 may be the same as in Option 2 / 3.

[0175] [Aspect 3-2] When new RRC parameters are configured to indicate the above-mentioned schemes 1 / 2 / 3 for PUSCH, it is assumed that the UE is scheduled for simultaneous transmission of UL beams / panels using schemes 1 / 2 / 3, and the UL is scheduled by a single DCI. In the above-mentioned case 2, the UE assumes a PUSCH spatial relationship based on CORESET as shown in the following options 1 to 4.

[0176] [[Option 1]] The UE may follow the existing method shown in Cases 1 and 2. That is, in this case, the UE may not predict that simultaneous transmissions of UL beams / panels will be scheduled. Instead, the UE may predict that PUSCH transmissions by one UL beam / panel will be scheduled.

[0177] [[Option 2]] The UE expects that one or more CORESETs are configured with two TCI states. The PUSCH spatial relationship of the new transmission scheme may be determined according to the two TCI states of the CORESET with the lowest ID among one or more CORESETs, the TCI state with the lowest ID from two CORESETs with the lowest ID among one or more CORESETs, or the TCI state with the two lowest IDs. That is, a multi-panel UE configured for UL multi-beam / panel simultaneous transmission may also be configured for DL multi-beam / panel reception from multiple TRPs.

[0178] [[Option 3]] When one or more CORESETs are configured with two TCI states, the PUSCH spatial relationship may be determined according to the two TCI states of the CORESET with the lowest ID among the one or more CORESETs, the TCI state with the lowest ID from the two CORESETs with the lowest ID among the one or more CORESETs, or the TCI state with the two lowest IDs.

[0179] When one or more CORESETs are configured with one TCI state, the PUSCH spatial relationship may be determined according to the two TCI states from the two CORESETs with the lowest IDs among the one or more CORESETs, or the two TCI states with the lowest IDs from the two CORESETs.

[0180] In Option 2 / 3, if a CORESET is configured with more than two TCI states, the PUSCH spatial relationship may be determined according to the two TCI states of the CORESET with the lowest ID, the TCI state with the lowest ID from the two CORESETs with the lowest IDs, or the TCI state with the two lowest IDs. For example, if repeated transmission is applied between MTRPs, there may be a CORESET with more than two TCI states.

[0181] [[Option 4]] If a CORESET is configured with one TCI state, the PUSCH spatial relationship may be determined according to two TCI states: the CORESET with the lowest ID and the CORESET with the second lowest ID. Option 4 may be applied to multiple CORESETs with different TCI state / spatial relationship settings. The PUSCH spatial relationship in Option 4 may be the same as in Option 2 / 3.

[0182] [Aspect 3-3] When new RRC parameters are configured to indicate the above-mentioned schemes 1 / 2 / 3 for PUSCH, it is assumed that the UE is scheduled for simultaneous transmission of UL beams / panels using schemes 1 / 2 / 3, and the UL is scheduled by multiple (e.g., two) DCIs from different CORESET pool indices (possible in schemes 2 / 3), in the above-mentioned case 1, the UE assumes PUSCH spatial relationships based on PUCCH resources as per the following options 1 to 4.

[0183] [[Option 1]] The UE may follow the existing method shown in Cases 1 and 2. That is, in this case, the UE may not assume that simultaneous transmissions of UL beams / panels are scheduled. Instead, the UE may predict that PUSCH transmissions by one UL beam / panel are scheduled.

[0184] [[Option 2]] The spatial relationship of each PUSCH scheduled by multiple DCIs of the new transmission scheme may be determined according to the TCI state / spatial relationship of the PUCCH resource with the lowest ID among one or more PUCCH resources associated with the same CORESET pool index, or the TCI state / spatial relationship of the PUCCH resource with the lowest ID within the same CORESET pool index.

[0185] [[Option 3]] When a PUCCH resource is configured with more than one TCI state / spatial relationship, the spatial relationship of each PUSCH scheduled by multiple DCIs of the new transmission scheme may be determined according to the TCI state / spatial relationship with the lowest ID of the PUCCH resource with the lowest ID among one or more PUCCH resources associated with the same CORESET pool index, or the TCI state / spatial relationship with the lowest ID of the PUCCH within the same CORESET pool index.

[0186] Only in the case of repeated transmission between TRPs using single DCI-based scheduling, PUCCH resources may be configured with two beams (TCI state / spatial relationship). However, when single DCI and multi-DCI are configured simultaneously, PUCCH resources may be configured with two beams even in the case of repeated transmission between TRPs using multi-DCI-based scheduling.

[0187] [[Option 4]] If PUCCH resources are configured with one TCI state / spatial relationship, each PUSCH spatial relationship of the new transmission scheme may be determined according to the TCI state / spatial relationship of the PUCCH resource with the lowest ID among one or more PUCCH resources associated with each CORESET pool index.

[0188] [Aspect 3-4] When new RRC parameters are configured to indicate the above-mentioned schemes 1 / 2 / 3 for PUSCH, it is assumed that the UE is scheduled for simultaneous transmission of UL beams / panels using schemes 1 / 2 / 3, and the UL (PUSCH) is scheduled by multiple (e.g., two) DCIs from different CORESET pool indices (possible in schemes 2 / 3), in the above-mentioned case 2, the UE assumes PUSCH spatial relationships based on CORESET as per the following options 1 to 4.

[0189] [[Option 1]] The UE may follow the existing method shown in Cases 1 and 2. That is, in this case, the UE may not assume that simultaneous transmissions of UL beams / panels are scheduled. Instead, the UE may predict that PUSCH transmissions by one UL beam / panel are scheduled.

[0190] [[Option 2]] The spatial relationship of each PUSCH scheduled by multiple DCIs of the new transmission scheme may be determined according to the TCI state of the CORESET with the lowest ID among one or more CORESETs associated with the same CORESET pool index, or the TCI state of the CORESET with the lowest ID within the same CORESET pool index.

[0191] [[Option 3]] When a PUCCH resource is configured with more than one TCI state / spatial relationship, the spatial relationship of each PUSCH scheduled by multiple DCIs of the new transmission scheme may be determined according to the TCI state with the lowest ID of the CORESET with the lowest ID among one or more CORESETs associated with the same CORESET pool index, or the TCI state with the lowest ID of the CORESET within the same CORESET pool index.

[0192] Only in the case of repeated transmission between TRPs using single DCI-based scheduling, CORESET may be configured with two beams (TCI states). However, when single DCI and multi-DCI are configured simultaneously, CORESET may be configured with two beams even in the case of repeated transmission between TRPs using multi-DCI-based scheduling.

[0193] [[Option 4]] If a PUCCH resource is configured with one TCI state, each PUSCH spatial relationship of the new transmission scheme may be determined according to the TCI state with the lowest ID of the CORESET with the lowest ID among one or more CORESETs associated with each CORESET pool index.

[0194] According to this embodiment, the UE can appropriately assume (determine) the spatial relationship of PUSCHs in a new transmission scheme.

[0195] <Fourth embodiment> In the following Case 3 in 3GPP Rel.16, the spatial relationship is not indicated in the PUCCH. Therefore, when the above-mentioned Method 1 is applied to the PUCCH, or when one PUCCH is repeatedly transmitted at the same time using SDM as described in the modification of the first embodiment, how to determine the spatial relationship of the PUCCH has not been fully considered. Therefore, the present inventors have come up with a method for appropriately assuming (determining) the spatial relationship of the PUCCH.

[0196] In this embodiment, the UE determines the spatial relationship of the physical uplink control channel (PUCCH) based on the control resource set (CORESET) with the lowest identifier (ID), and transmits the PUCCH simultaneously using multiple coherent panels (Method 1) based on the spatial relationship.

[0197] In the present disclosure, PUCCH repeat transmission using SDM may be interpreted as PUCCH repeat transmission using TDM / FDM.

[0198] [Case 3] If the following conditions (1) to (4) are met, the spatial configuration of PUCCH transmission from a UE may be the same as the spatial configuration of PDCCH reception by a UE in a CORESET with the lowest ID of the active DL BWP of the Primary Cell (PCell). (1) The UE is provided with pathlossReferenceRSs in PUCCH-PowerControl. (2) The UE is provided with enableDefaultBeamPlForPUCCH. (3) PUCCH-SpatialRelationInfo is provided to the UE. (4) The UE is provided with a CORESET pool index value of one of several CORESETs in the ControlResourceSet, or a CORESET pool index value of one of all CORESETs, and there is no TCI field codepoint in the DCI format (if any) of the search space set that maps two TCI states.

[0199] That is, in Case 3, the PUCCH spatial relationship (spatial configuration) follows the QCL of the CORESET with the lowest ID.

[0200] [Aspect 4-1] In the above case 3, if new RRC parameters are configured to indicate the above method 1 for PUCCH, the UE is assumed to transmit PUCCH repetitions with SDM using multiple (two) beams / panels, and the CORESET pool index is not configured, the UE may assume a PUCCH spatial relationship based on CORESET, as in the following options 1 to 5.

[0201] For example, when a CORESET pool index is not set and a PUCCH is repeatedly transmitted using multiple panels with SDM applied, the UE may determine the spatial relationship of the PUCCH based on the two TCI states of the CORESET with the lowest ID among one or more CORESETs.

[0202] [[Option 1]] The UE may follow the existing method shown in Case 3. That is, in this case, the UE may not predict that simultaneous PUCCH transmissions by UL beams / panels are scheduled. Instead, the UE may predict simultaneous PUSCH transmissions by one UL beam / panel.

[0203] [[Option 2]] The PUCCH spatial relationship may be determined according to the two TCI states of the two CORESETs with the lowest IDs among one or more CORESETs, or the TCI states of the two CORESETs with the lowest IDs.

[0204] [[Option 3]] When two TCI states are set in a CORESET, the PUCCH spatial relationship may be determined according to the two TCI states of the CORESET with the lowest ID among one or more CORESETs.

[0205] [[Option 4]] If more than two TCI states are configured in a CORESET, the PUCCH spatial relationship may be determined according to the two TCI states with the lowest IDs of the CORESET that has the lowest ID among one or more CORESETs, or the two TCI states with the lowest IDs of the CORESET.

[0206] [[Option 5]] If one TCI state is set in a CORESET, the PUCCH spatial relationship may be determined according to the TCI state of the lowest CORESET ID and the TCI state of the second lowest CORESET ID.

[0207] [Aspect 4-2] In the above-mentioned case 3, if new RRC parameters are configured to indicate the above-mentioned method 1 for PUCCH, the UE predicts PUCCH repeated transmission with SDM using multiple (two) beams / panels, and a CORESET pool index is configured, the UE may assume a PUCCH spatial relationship based on CORESET, as in the following options 1 to 4.

[0208] For example, when a CORESET pool index is configured and repeated transmission of PUCCH with SDM applied is performed using multiple panels, the UE may determine the spatial relationship of the PUCCH based on the TCI state of the CORESET with the lowest ID among one or more CORESETs associated with the same CORESET pool index.

[0209] [[Option 1]] The UE may follow the existing method shown in Case 3. That is, in this case, the UE may not predict that simultaneous PUCCH transmissions by UL beams / panels are scheduled. Instead, the UE may predict simultaneous PUSCH transmissions by one UL beam / panel.

[0210] [[Option 2]] Each PUCCH spatial relation may be determined according to the TCI state of the CORESET with the lowest ID among one or more CORESETs associated with the same CORESET pool index, or the TCI state with the lowest ID of the CORESETs having the same CORESET pool index.

[0211] [[Option 3]] When one TCI state is set for a CORESET, each PUCCH spatial relation may be determined according to the TCI state of the CORESET with the lowest ID among one or more CORESETs associated with the same CORESET pool index, or the TCI state with the lowest ID of the CORESETs having the same CORESET pool index.

[0212] [[Option 4]] When one TCI state is set for a CORESET, each PUCCH spatial relation of the new transmission mode may be determined according to the TCI state of the CORESET with the lowest ID among one or more CORESETs associated with each CORESET pool index.

[0213] Only in the case of repeated transmission between TRPs using single DCI-based scheduling, the CORESET may be set with two beams (TCI states). However, when single DCI and multi DCI are set simultaneously, even in the case of repeated transmission between TRPs using multi DCI-based scheduling, the CORESET may be set with two beams.

[0214] According to this embodiment, the UE can appropriately determine the PUCCH spatial relation.

[0215] <UE capability (UE capability)> The UE may transmit (report) at least one of the UE capabilities (UE capability information) shown in the following (1) to (8). Note that Method 1 / 2 / 3 indicates the above-mentioned transmission methods. (1) Whether or not the method 1 / 2 / 3 for UL (PUSCH) transmission is supported. (2) Whether or not Scheme 1 for UL (PUCCH) transmission is supported. (3) Whether the same or different time / frequency resource indication is supported in methods 1 / 2 / 3 for PUSCH transmission. (4) Whether single DCI-based or multi-DCI-based PUSCH scheduling is supported in methods 1 / 2 / 3. (5) Whether one / two / three DMRS CDM groups are supported in PUSCH scheduling using methods 1 / 2 / 3. (6) Whether or not to support tables showing extended DMRS ports (e.g., Figures 7 to 10). (7) Whether to support two default beams for PUSCH (single DCI / multiple DCI based scheduling) using methods 1 / 2 / 3. (8) Whether to support two default beams for PUSCH using methods 1 / 2 / 3 (with or without two CORESET pool indexes).

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

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

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

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

[0220] 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 the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

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

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

[0223] 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 above 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 be a frequency band higher than FR2.

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

[0225] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, 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.

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

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

[0228] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio 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).

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

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

[0231] 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)), etc. may be used as an uplink channel.

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

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

[0234] 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 an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0235] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search 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 a CORESET associated with a certain search space based on the search space configuration.

[0236] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

[0237] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement 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.

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

[0239] 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, 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 as DL-RS.

[0240] 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 the SS (PSS, SSS) and the PBCH (and 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 reference signals.

[0241] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. 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).

[0242] (base station) 12 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.

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

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

[0245] 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 to be transmitted as signals, control information, sequences, etc., 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.

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

[0247] The transmitting / receiving unit 120 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 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0248] 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 pertains, such as an array antenna.

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

[0250] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

[0252] The transceiver 120 (transmission processor 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.

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

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

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

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

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

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

[0259] The transceiver 120 may transmit a configuration related to transmission of the physical uplink shared channel by higher layer signaling, and may receive the physical uplink shared channel simultaneously transmitted using multiple coherent or non-coherent panels based on the configuration.

[0260] The controller 110 may configure the spatial relationship of the physical uplink shared channel based on the resource of the physical uplink control channel with the lowest identifier or the control resource set with the lowest identifier. The transceiver 120 may receive the physical uplink shared channel simultaneously transmitted using multiple coherent or non-coherent panels based on the configuration.

[0261] The controller 110 may determine a spatial relationship of the physical uplink control channels based on the control resource set with the lowest identifier, and the transceiver 120 may receive the physical uplink control channels simultaneously transmitted using multiple coherent panels based on the spatial relationship.

[0262] (user terminal) 13 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 transmitting / receiving 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 transmitting / receiving antenna 230.

[0263] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, 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.

[0264] 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, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0265] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also 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.

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

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

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

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

[0270] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

[0272] The transceiver 220 (transmission processor 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.

[0273] 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 when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

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

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

[0276] The transceiver 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 to acquire user data, etc.

[0277] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, 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.

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

[0279] The transceiver 220 may receive a configuration for transmitting the physical uplink shared channel through higher layer signaling, and may simultaneously transmit the physical uplink shared channel using multiple coherent or non-coherent panels based on the configuration.

[0280] When using multiple coherent panels, the transceiver unit 220 may transmit the repeated transmission of the physical uplink shared channel to which space division multiplexing is applied in the same time resource and the same frequency resource.

[0281] When using multiple coherent panels, the transceiver unit 220 may transmit the repeated transmission of the physical uplink shared channel to which frequency division multiplexing is applied in the same time resource and different frequency resources.

[0282] When multiple non-coherent panels are used, the transceiver 220 may receive downlink control information including at least one of a measurement reference signal resource indicator, a transmit precoding matrix index, and a transmit power control command corresponding to a code division multiplexing group. The transceiver 220 may transmit the physical uplink shared channel based on the downlink control information.

[0283] The controller 210 may determine the spatial relationship of the physical uplink shared channels based on the physical uplink control channel resource with the lowest identifier or the control resource set with the lowest identifier. The transceiver 220 may simultaneously transmit the physical uplink shared channels using multiple panels.

[0284] The transceiver 220 may receive a single downlink control information scheduling the physical uplink shared channel. When one or more physical uplink control channel resources are configured with two transmission configuration indication (TCI) states, the spatial relationship of the physical uplink shared channel may follow the two TCI states of a physical uplink control channel resource with the lowest identifier among the one or more physical uplink control channel resources.

[0285] The transceiver 220 may receive a single downlink control information that schedules the physical uplink shared channel. When one or more control resource sets are configured with two transmission configuration indication (TCI) states, the spatial relationship of the physical uplink shared channel may follow the two TCI states of the control resource set with the lowest identifier among the one or more control resource sets.

[0286] The transceiver 220 may receive a plurality of downlink control information items scheduling the physical uplink shared channels, and a spatial relationship of each physical uplink shared channel scheduled in the plurality of downlink control information items may follow a transmission configuration indication (TCI) state of a physical uplink control channel resource having a lowest identifier among one or more physical uplink control channel resources associated with the same control resource set pool index, or a transmission configuration indication (TCI) state of a control resource set having a lowest identifier among one or more control resource sets associated with the same control resource set pool index.

[0287] The controller 210 may determine a spatial relationship of the physical uplink control channels based on the control resource set with the lowest identifier, and the transceiver 220 may simultaneously transmit the physical uplink control channels using multiple coherent panels based on the spatial relationship.

[0288] When a control resource set pool index is not set and the physical uplink control channel is repeatedly transmitted using the plurality of panels with spatial division multiplexing, the control unit 210 may determine the spatial relationship based on two transmission configuration indication (TCI) states of the control resource set with the lowest identifier.

[0289] When a control resource set pool index is set and the physical uplink control channel is repeatedly transmitted using the multiple panels with spatial division multiplexing applied, the control unit 210 may determine the spatial relationship based on a transmission configuration indication (TCI) state of a control resource set having the lowest identifier among one or more control resource sets associated with the same control resource set pool index.

[0290] (Hardware configuration) 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 also be realized by combining the single device or multiple devices with software.

[0291] 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 mentioned above, the implementation method of each is not particularly limited.

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

[0293] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read 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.

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

[0295] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as 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.

[0296] 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), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0297] 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 realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0298] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0299] Storage 1003 is a computer-readable recording medium and may be constituted by 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, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

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

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

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

[0303] 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 such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0304] (Variation) Note that terms explained 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.

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

[0306] 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, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

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

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

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

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

[0311] 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. However, the definition of TTI is not limited to this.

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

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

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

[0315] 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 equal to or greater than 1 ms.

[0316] 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 also be determined based on numerology.

[0317] 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. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0318] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0320] A Bandwidth Part (BWP), which may also be referred to as a fractional 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 given BWP and numbered within that BWP.

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

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

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

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

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

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

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

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

[0329] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, 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.

[0330] Note that the physical layer signaling may be called 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 called 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).

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

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

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

[0334] 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), then these wired and / or wireless technologies are included within the definition of transmission media.

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

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

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

[0338] 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 divided 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 term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.

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

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

[0341] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, or the mobile object itself. 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). 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.

[0342] 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 uplink channel and downlink channel may be read as sidelink channel.

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

[0344] 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) and a Serving-Gateway (S-GW)), or a combination thereof.

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

[0346] Each aspect / embodiment described in the present disclosure may be related to 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) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on and extend these systems. Furthermore, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

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

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

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

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

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

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

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

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

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

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

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

[0358] 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 receiving unit configured to receive a configuration for transmitting a Physical Uplink Shared Channel (PUSCH) via higher layer signaling, and to receive a single Downlink Control Information (DCI) including two Sounding Reference Signal Resource Indicator (SRI) fields and scheduling the PUSCH; a transmitting unit that simultaneously transmits the PUSCH using a plurality of panels based on the setting; a control unit that controls transmission of the PUSCH in the same time resource and the same frequency resource using the plurality of panels, When a specific field included in the single DCI indicates that both of the two SRI fields are to be applied, the control unit applies each SRI field to the same number of layers. Terminal.

2. When the PUSCH is transmitted to a plurality of Transmission / Reception Points (TRPs) using the plurality of panels, the same number of antenna ports is set for the plurality of TRPs. The terminal according to claim 1 .

3. receiving, via higher layer signaling, configuration for transmission of a Physical Uplink Shared Channel (PUSCH), and receiving a single Downlink Control Information (DCI) that includes two Sounding Reference Signal Resource Indicator (SRI) fields and schedules the PUSCH; transmitting the PUSCH simultaneously using a plurality of panels based on the setting; Controlling transmission of the PUSCH in the same time resource and the same frequency resource using the plurality of panels; applying each SRI field to the same number of layers when a specific field included in the single DCI indicates that both SRI fields of the two SRI fields are to be applied; A wireless communication method for a terminal having the above configuration.

4. a transmitter configured to transmit a configuration for transmitting a Physical Uplink Shared Channel (PUSCH) via higher layer signaling and to transmit a single Downlink Control Information (DCI) including two Sounding Reference Signal Resource Indicator (SRI) fields and scheduling the PUSCH; a receiving unit that receives the PUSCH simultaneously transmitted using a plurality of panels based on the setting, The PUSCH is transmitted from a terminal using the plurality of panels in the same time resource and the same frequency resource; When a specific field included in the single DCI indicates that both of the two SRI fields are to be applied, each SRI field is to be applied to the same number of layers. Base station.

5. A system including a terminal, a first base station, and a second base station, The terminal a receiving unit configured to receive a configuration for transmitting a Physical Uplink Shared Channel (PUSCH) via higher layer signaling, and to receive a single Downlink Control Information (DCI) including two Sounding Reference Signal Resource Indicator (SRI) fields and scheduling the PUSCH; a transmitter that simultaneously transmits the PUSCH to the first base station and the second base station using a plurality of panels based on the setting; a control unit that controls transmission of the PUSCH in the same time resource and the same frequency resource using the plurality of panels, When a specific field included in the single DCI indicates that both SRI fields of the two SRI fields are to be applied, the control unit applies each SRI field to the same number of layers; The first base station or the second base station a transmitter for transmitting the configuration and the single DCI; system.

Images