Terminal, wireless communication method, base station, and system

Abstract

A terminal according to an aspect of the present disclosure comprises: a reception unit that receives setting information related to two linked search space sets and that uses the two linked search space sets to receive downlink control information for scheduling a plurality of physical uplink shared channel repetitions; and a control unit that controls the transmission of the plurality of physical uplink shared channel repetitions on the basis of two values of parameter in the downlink control information. According to an aspect of the present disclosure, the transmission of uplink channel repetitions can be appropriately performed for the setting of PDCCH.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In a future wireless communication system, it has been considered to perform multiple transmissions of an uplink channel for one transmission / reception point (TRP) or multiple TRPs.

[0006] In a future wireless communication system, it has been considered that a terminal receives a physical downlink control channel (PDCCH) based on the settings of the PDCCH and a control resource set (CORESET). In a future wireless communication system, further, cases where at least one of one or two transmission configuration indication (TCI) states and repetition is used for PDCCH reception have been considered. For at least one of these cases, it is not clear how the UE performs the transmission of the uplink channel repetition. If the transmission is not performed appropriately, there is a risk of causing a deterioration in communication quality, a decrease in communication throughput, etc.

[0007] Therefore, one object of the present disclosure is to provide a terminal and a wireless communication method that appropriately perform the transmission of the uplink channel repetition with respect to the setting of the PDCCH. 、 Base station and system as one of the purposes.

Means for Solving the Problems

[0008] A terminal according to one aspect of the present disclosure includes object a reception unit that schedules repetitions for a physical uplink shared channel (PUSCH) downlink control information, and a control unit that controls the repeated transmission based on the value within the (DCI) receives reception unit that believes, and the DCI inside two fields of the sounding reference signal (SRS) indicator (SRI) included in of the value, and the PUSCH repeated transmission. When supporting physical downlink control channel (PDCCH) repetitions based on two linked search space sets, the receiving unit receives the DCI using the two linked search space sets .

Effects of the Invention

[0009] According to one aspect of the present disclosure, for the configuration of PDCCH, the uplink channel repetition transmission can be appropriately performed.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

DETAILED DESCRIPTION OF THE INVENTION

[0011] (TCI, Spatial Relationship, QCL) In NR, based on the Transmission Configuration Indication state (TCI state), at least one of a signal and a channel (referred to as a signal / channel) in a UE, reception processing (for example, at least one of reception, demapping, demodulation, and decoding), and transmission processing (for example, at least one of transmission, mapping, precoding, modulation, and encoding) are considered to be controlled.

[0012] The TCI state may represent what is applied to the downlink signal / channel. What corresponds to the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information regarding the Quasi-Co-Location (QCL) of the signal / channel, and may be called a spatial reception parameter, Spatial Relation Information, etc. The TCI state may be set for each channel or each signal in the UE.

[0014] QCL is an indicator that represents the statistical properties of a signal / channel. For example, when a certain signal / channel and other signal / channels are in a QCL relationship, it may mean that at least one of Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (for example, spatial Rx parameter) is the same (QCL for at least one of these) among these different multiple signals / channels.

[0015] Note that the spatial Rx parameter may correspond to the receiving beam of the UE (for example, the receiving analog beam), and the beam may be determined based on spatial QCL. QCL (or at least one element of QCL) in the present disclosure may be read as sQCL (spatial QCL).

[0016] Multiple types (QCL types) of QCL may be defined. For example, four QCL types A - D with different parameters (or parameter sets) that can be assumed to be the same may be provided, and the parameters (which may also be called QCL parameters) are shown below: · QCL type A (QCL - A): Doppler shift, Doppler spread, average delay, and delay spread, · QCL type B (QCL - B): Doppler shift and Doppler spread, · QCL type C (QCL - C): Doppler shift and average delay, · QCL type D (QCL - D): spatial Rx parameter.

[0017] It may be called a QCL assumption that a UE assumes that a certain control resource set (CORESET), channel, or reference signal is in a relationship of a specific QCL (for example, QCL type D) with another CORESET, channel, or reference signal.

[0018] Based on the TCI state or QCL assumption of a signal / channel, the UE may determine at least one of the transmission beam (Tx beam) and the reception beam (Rx beam) of the signal / channel.

[0019] The TCI state may be, for example, information regarding the QCL between a target channel (in other words, a reference signal (RS) for the channel) and another signal (for example, another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0020] Note that the channel / signal to which the TCI state is applied may be called a target channel / reference signal (target channel / RS), simply a target, etc., and the above-mentioned another signal may be called a reference reference signal (reference RS), a source RS (source RS), simply a reference, etc.

[0021] The channel for which the TCI state or the spatial relationship is set (specified) may be, for example, at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), and a physical uplink control channel (PUCCH).

[0022] In addition, the RS related to the channel and QCL may be, for example, at least one of a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a CSI-RS for tracking (also called a Tracking Reference Signal (TRS)), a reference signal for QCL detection (also called a QRS), a Demodulation Reference Signal (DMRS), etc.

[0023] The SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). The SSB may be called an SS / PBCH block.

[0024] The RS of QCL type X in the TCI state may mean an RS in relation to a certain channel / signal (DMRS) and QCL type X, and this RS may be called the QCL source of QCL type X in the TCI state.

[0025] (Repeated transmission) In Rel.15, repeated transmission is supported in data transmission. For example, a base station (network (NW), gNB) repeatedly transmits DL data (e.g., a downlink shared channel (PDSCH)) a predetermined number of times. Alternatively, a UE repeatedly transmits UL data (e.g., an uplink shared channel (PUSCH)) a predetermined number of times.

[0026] Figure 1A is a diagram showing an example of repeated transmission of PUSCH. In Figure 1A, an example is shown in which a predetermined number of repeated PUSCHs are scheduled by a single DCI. The number of repetitions is also called a repetition factor K or an aggregation factor K.

[0027] In Figure 1A, the repetition factor K = 4, but the value of K is not limited to this. Also, the n-th repetition may also be called the n-th transmission occasion, etc., and may be identified by a repetition index k (0 ≦ k ≦ K - 1). Further, Figure 1A shows repeated transmission of PUSCH dynamically scheduled by DCI (for example, PUSCH based on dynamic grant), but it may also be applied to repeated transmission of PUSCH based on configured grant.

[0028] For example, in Figure 1A, the UE receives information indicating the repetition factor K (for example, aggregationFactorUL or aggregationFactorDL) quasi-statically by upper layer signaling. Here, the upper layer signaling may be any one of, for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information, or a combination thereof.

[0029] MAC signaling may use, for example, MAC control element (MAC CE (Control Element)), MAC PDU (Protocol Data Unit), etc. The broadcast information may be, for example, master information block (MIB), system information block (SIB), remaining minimum system information (RMSI), etc.

[0030] The UE controls the reception process (e.g., at least one of reception, demapping, demodulation, and decoding) of the PDSCH or the transmission process (e.g., at least one of transmission, mapping, modulation, and coding) of the PUSCH based on at least one of the following field values (or the information indicated by the field value) in the DCI in K consecutive slots: ·Allocation of time-domain resources (e.g., start symbol, number of symbols in each slot, etc.), ·Allocation of frequency-domain resources (e.g., a predetermined number of resource blocks (RBs), a predetermined number of resource block groups (RBGs)), ·Modulation and coding scheme (MCS) index, ·Configuration of the demodulation reference signal (DMRS) for the PUSCH, ·Spatial relation information of the PUSCH, or the state (TCI state) of the transmission configuration indication (TCI or Transmission Configuration Indicator).

[0031] The same symbol allocation may be applied among K consecutive slots. FIG. 1A shows a case where the PUSCH in each slot is allocated to a predetermined number of symbols from the start of the slot. The same symbol allocation among slots may be determined as described in the above time-domain resource allocation.

[0032] For example, the UE may determine the symbol allocation in 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 (e.g., TDRA field) in the DCI. Note that the UE may determine the first slot based on the K2 information determined based on the value m of a predetermined field (e.g., TDRA field) of the DCI.

[0033] On the other hand, between the K consecutive slots, the redundancy version (RV) applied to the TB based on the same data may be the same, or at least part of them may be different. For example, the RV applied to the TB in the nth slot (transmission opportunity, repetition) may be determined based on the value of a predetermined field (e.g., RV field) in the DCI.

[0034] If the resources allocated in K consecutive slots differ in communication direction by at least one symbol between UL, DL, or Flexible of each slot specified by at least one of the uplink-downlink communication direction indication information (e.g., "TDD-UL-DL-ConfigCommon", "TDD-UL-DL-ConfigDedicated" of RRC IE) for TDD control and the slot format indicator of the DCI (e.g., DCI format 2_0), the resources of the slot including the symbol may not be transmitted (or received).

[0035] In Rel.15, as shown in Figure 1A, PUSCH is repeatedly transmitted over a plurality of slots (in slot units), but from Rel.16 onwards, it is assumed that PUSCH is repeatedly transmitted in units shorter than a slot (e.g., sub-slot units, mini-slot units, or units of a predetermined number of symbols) (see Figure 1B).

[0036] In Fig. 1B, the repetition factor K = 4, but the value of K is not limited to this. Also, the n-th repetition may also be referred to as the n-th transmission occasion, etc., and may be identified by the repetition index k (0 ≦ k ≦ K - 1). Further, Fig. 1B shows the repeated transmission of PUSCH dynamically scheduled by DCI (e.g., dynamic grant-based PUSCH), but it may also be applied to the repeated transmission of configured grant-based PUSCH.

[0037] The UE may determine the 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 (e.g., StartSymbol and length) determined based on the value m of a predetermined field (e.g., TDRA field) in the DCI of the PUSCH. Note that the UE may also determine a predetermined slot based on the Ks information determined based on the value m of a predetermined field (e.g., TDRA field) of the DCI.

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

[0039] The slot-based repeated transmission shown in Fig. 1A may be called repeated transmission type A (e.g., PUSCH repetition Type A), and the subslot-based repeated transmission shown in Fig. 1B may be called repeated transmission type B (e.g., PUSCH repetition Type B).

[0040] The UE may be configured with the application of 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 through upper layer signaling (e.g., PUSCHRepTypeIndicator).

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

[0042] For example, for the first DCI format (e.g., DCI format 0_1), when upper layer signaling (e.g., PUSCHRepTypeIndicator-AorDCIFormat0_1) is configured for repetitive transmission type B (e.g., PUSCH-RepTypeB), the UE applies repetitive transmission type B for the PUSCH repetitive transmission scheduled by the first DCI format. Otherwise (e.g., when PUSCH-RepTypeB is not configured or PUSCH-RepTypA is configured), the UE applies repetitive transmission type A for the PUSCH repetitive transmission scheduled by the first DCI format.

[0043] Also, from Rel. 16 onwards, a dynamic switch between a single PUSCH transmission and a PUSCH repetitive transmission is being considered.

[0044] When upper layer parameters related to the time domain allocation of PUSCH (e.g., pusch-TimeDomainAllocationListDCI-0-1-r16 or pusch-TimeDomainAllocationListDCI-0-2-r16) are configured for a UE, the number of repetitions (e.g., 1, 2, 3, 4, 7, 8, 12, or 16) of the PUSCH may be configured by a parameter related to the number of repetitions of the PUSCH (e.g., numberOfRepetitions-r16) included in the upper layer parameters. The UE may determine the number of repetitions of the PUSCH scheduled by the DCI based on the time domain resource allocation field of the DCI. When the number of repetitions is configured / specified as 1, the UE may perform a single PUSCH transmission.

[0045] (Spatial relation for SRS, PUSCH) In Rel.15 NR, the UE may receive information (SRS configuration information, e.g., parameters within the "SRS-Config" of the RRC control element) used for the transmission of measurement reference signals (e.g., Sounding Reference Signal (SRS)).

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

[0047] One SRS resource set may be related to a predetermined number (e.g., 1 or more, or a plurality) of SRS resources (a predetermined number of SRS resources may be grouped). Each SRS resource may be identified by an SRS Resource Indicator (SRI) or an SRS resource ID (Identifier).

[0048] The SRS resource set information may include the SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, the SRS resource type (e.g., any of Periodic SRS, Semi-Persistent SRS, Aperiodic CSI), and information on the usage of the SRS.

[0049] Here, the SRS resource type may indicate any of Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), and Aperiodic SRS (A-SRS). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation), and may transmit A-SRS based on the SRS request in DCI.

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

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

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

[0053] The spatial relation information of the SRS (e.g., "spatialRelationInfo" of the RRC information element) may indicate the spatial relation 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 relation information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as the index of the above-mentioned predetermined reference signal.

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

[0056] The spatial relation information of the SRS may include a serving cell index corresponding to the above-mentioned predetermined reference signal, a BWP index (BWP ID), and the like.

[0057] When the UE is configured with spatial relation information regarding an SSB or CSI-RS and an SRS for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmission filter) as the spatial domain filter (spatial domain reception filter) for receiving the SSB or CSI-RS. In this case, the UE may assume that the UE reception beam of the SSB or CSI-RS and the UE transmission beam of the SRS are the same.

[0058] When the UE is configured with spatial relation information regarding another SRS (reference SRS) and a certain SRS (target SRS) for a certain SRS (target SRS) resource, the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmission filter) as the spatial domain filter (spatial domain transmission filter) for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmission beam of the reference SRS and the UE transmission beam of the target SRS are the same.

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

[0060] For PUSCH, when codebook-based transmission is used, the UE may have two SRS resources configured by RRC for each SRS resource set, and one of the two SRS resources may be indicated by DCI (1-bit SRI field). For PUSCH, when non-codebook-based transmission is used, the UE may have four SRS resources configured by RRC for each SRS resource set, and one of the four SRS resources may be indicated by DCI (2-bit SRI field).

[0061] (TPMI and Transmission Rank) In Rel.16, for codebook-based PUSCH transmission, it is being considered that the Transmitted Precoding Matrix Indicator (TPMI) and transmission rank are specified by specific fields (e.g., precoding information and layer number field) included in downlink control information (e.g., DCI format 0_1).

[0062] The precoder used by the UE for codebook-based PUSCH transmission may be selected from the uplink codebook with the same number of antenna ports as the value set by the upper layer parameter (e.g., nrofSRS-Ports) configured for the SRS resource.

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

[0064] The specific field may be 0 bits when the upper layer parameter (e.g., txConfig) configured for the UE is set to nonCodebook.

[0065] Also, for one antenna port, when the higher layer parameter (e.g., txConfig) set for the UE is set in the codebook, the specific field may be 0 bits.

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

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

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

[0069] (Multi - TRP PDSCH) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRP (MTRP)) perform DL transmission to a UE using one or more panels (multi-panel). Also, it is being considered that a UE performs UL transmission to one or more TRPs using one or more panels.

[0070] Note that the plurality of TRPs may correspond to the same cell identifier (cell Identifier (ID)), or may correspond to different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0071] The multi-TRP (e.g., TRP#1, #2) is connected by an ideal / non-ideal backhaul, and information, data, etc. may be exchanged. Different code words (Code Word (CW)) and different layers may be transmitted from each TRP of the multi-TRP. As one form of multi-TRP transmission, Non-Coherent Joint Transmission (NCJT) may be used.

[0072] In NCJT, for example, TRP#1 modulates and maps the first code word, layer-maps it to the first number of layers (e.g., 2 layers), and transmits the first PDSCH using the first precoding. Also, TRP#2 modulates and maps the second code word, layer-maps it to the second number of layers (e.g., 2 layers), and transmits the second PDSCH using the second precoding.

[0073] Note that the plurality of PDSCHs (multi-PDSCH) subject to NCJT may be defined to partially or completely overlap in at least one of the time and frequency domains. That is, the first PDSCH from the first TRP and the second PDSCH from the second TRP may overlap in at least one of the time and frequency resources.

[0074] These first PDSCH and second PDSCH may be assumed to be not quasi-co-located. The reception of multi-PDSCH may be interpreted as the simultaneous reception of PDSCH that is not of a certain QCL type (e.g., QCL type D).

[0075] Multiple PDSCH from multiple TRP (which may be referred to as multiple PDSCH) may be scheduled using one DCI (single DCI, single PDCCH) (single master mode, single-DCI based multi-TRP). Multiple PDSCH from multiple TRP may be scheduled respectively using multiple DCI (multiple PDCCH) (multi-master mode, multi-DCI based multi-TRP).

[0076] In URLLC for multi-TRP, it is being considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs is supported. Repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4) across multiple TRPs in the frequency domain or layer (spatial) domain or time domain are being considered. In scheme 1, multi-PDSCH from multiple TRPs is space division multiplexing (SDM). In schemes 2a and 2b, PDSCH from multiple TRPs is frequency division multiplexing (FDM). In scheme 2a, the redundancy version (RV) for multiple TRPs is the same. In scheme 2b, the RV for multiple TRPs may be the same or different. In schemes 3 and 4, multi-PDSCH from multiple TRPs is time division multiplexing (TDM). In scheme 3, multi-PDSCH from multiple TRPs is transmitted within one slot. In scheme 4, multi-PDSCH from multiple TRPs is transmitted in different slots.

[0077] According to such a multi-TRP scenario, more flexible transmission control using a good-quality channel is possible.

[0078] To support multi-TRP transmission within a cell (intra-cell, having the same cell ID) and between cells (inter-cell, having different cell IDs) based on multiple PDCCHs, in the RRC configuration information for linking multiple pairs of PDCCH and PDSCH having multiple TRPs, one control resource set (CORESET) within the PDCCH configuration information (PDCCH-Config) may correspond to one TRP.

[0079] If at least one of the following Conditions 1 and 2 is satisfied, the UE may determine that it is a multi-TRP based on multi-DCI. In this case, the TRP may be rewritten to a CORESET pool index. [Condition 1] One CORESET pool index is set. [Condition 2] Two different values (for example, 0 and 1) of the CORESET pool index are set.

[0080] If the following condition is satisfied, the UE may determine that it is a multi-TRP based on single-DCI. In this case, the two TRPs may be rewritten to two TCI states indicated by MAC CE / DCI. [Condition] "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to indicate one or two TCI states for one code point of the TCI field in DCI.

[0081] The common beam indication DCI may be a UE-specific DCI format (for example, DL DCI format (for example, 1_1, 1_2), UL DCI format (for example, 0_1, 0_2)), or a UE-group common DCI format.

[0082] (Multi-TRP PUSCH) It is considered that the UE performs UL transmission for one or more TRPs (see Figure 2).

[0083] The multiple TRPs may correspond to the same cell identifier (cell Identifier (ID)), or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0084] Figs. 3A to 3C are diagrams showing an example of a single PUSCH transmission, a repeated PUSCH transmission for a single TRP, and a repeated PUSCH transmission for a plurality of TRPs. In the example shown in Fig. 3A, the UE performs a single PUSCH transmission using a first SRI determined from a first SRI field. In the example shown in Fig. 3B, the UE performs a repeated PUSCH transmission for a single TRP using a first SRI determined from a first SRI field. In the example shown in Fig. 3C, the UE performs a repeated PUSCH transmission for a plurality of TRPs using a first SRI determined from a first SRI field and a second SRI determined from a second SRI field. The repeated PUSCH transmission may be scheduled based on one DCI.

[0085] It is being considered that the DCI has a 1- or 2-bit field indicating whether it is a single TRP PUSCH repetition or a multi-TRP PUSCH repetition.

[0086] It is being considered that the multi-TRP PUSCH repetition is scheduled by a single DCI. Here, it is being considered that the PUSCH repetition is TDM, that two SRIs / two TPMIs / two power control parameters are set / indicated, and that different PUSCH repetitions have different SRIs / TPMIs / power control parameters.

[0087] A mapping pattern of one or more SRIs (beams) for a plurality of PUSCH repetitions may be defined.

[0088] The mapping pattern may be indicated by an SRI / SRI field / SRS resource / SRS resource set / TRP applicable to or corresponding to PUSCH repeated transmission (e.g., each PUSCH transmission). For example, when repeated transmission for multiple TRPs is supported, multiple SRI fields may be notified / set to the UE (or multiple SRI fields are included in the DCI), or multiple SRS resources / SRS resource sets may be notified / set.

[0089] Alternatively, one SRI field is set in the DCI, and the UE may switch and apply the SRS resource set / SRS resource to be applied for each PUSCH transmission based on the SRI field. For example, the UE may apply the first SRS resource set / SRS resource (corresponding to the first SRI field) to PUSCH#1 and the second SRS resource set / SRS resource (corresponding to the first SRI field) to PUSCH#2.

[0090] As a mapping pattern applicable to repeated transmission of PUSCH for multiple TRPs, multiple SRIs / SRI fields (hereinafter also simply referred to as SRI) may correspond to multiple repeated transmissions cyclically. This mapping pattern may be referred to as cyclic mapping (e.g., cyclical mapping), cyclic pattern, cyclic correspondence, etc.

[0091] FIG. 4A is a diagram showing an example in which multiple SRIs correspond to multiple repeated transmissions cyclically. In this example, the UE is specified with a repetition number of 4 and performs repeated transmission of PUSCH using the first SRI and the second SRI. In this example, the UE performs the PUSCH transmission using the first SRI and the PUSCH transmission using the second SRI cyclically. For example, the first SRI may be applied to odd-numbered repetitions (repetitions #1, #3), and the second SRI may be applied to even-numbered repetitions (repetitions #2, #4) (e.g., SRI#1, SRI#2, SRI#1, SRI#2).

[0092] Alternatively, as a mapping pattern (e.g., the second mapping pattern) applied to the repeated transmission of PUSCH for a plurality of TRPs, it may be determined that a plurality of SRIs (or SRI fields) sequentially correspond to a plurality of repeated transmissions one by one in a specific number (e.g., two). This mapping pattern may be referred to as sequential mapping (e.g., sequential mapping), sequential pattern, sequential correspondence, etc.

[0093] FIG. 4B is a diagram showing an example in which a plurality of SRIs and a plurality of repeated transmissions sequentially correspond. In this example, the UE is specified with a repetition number of 4 and performs repeated transmission of PUSCH using the first SRI and the second SRI. In this example, the UE sequentially performs PUSCH transmission using the first SRI and PUSCH transmission using the second SRI two times each (e.g., SRI#1, SRI#1, SRI#2, SRI#2).

[0094] Two SRS resource sets having the usage of codebook (CB) or non-codebook (NCB) may be configured. For the indication for PUSCH to each TRP, two SRI fields / TPMI fields may exist.

[0095] As in the example of FIG. 5A, the first SRS resource set with usage = CB / NCB (e.g., 1 st SRS resource set with usage = CB / NCB) may mean an SRS resource set having the smallest (or largest) SRS resource set ID associated with usage = CB / NCB. Also, as in the example of FIG. 5B, the second SRS resource set with usage = CB / NCB (e.g., 2 nd SRS resource set with usage = CB / NCB) may mean an SRS resource set having the second smallest (or second largest) SRS resource set ID associated with usage = CB / NCB.

[0096] In Fig. 5A, it shows the case where the first SRS resource set corresponds to the smallest SRS resource set ID (here, SRS resource set ID = 0) associated with usage = CB. In Fig. 5B, it shows the case where the second SRS resource set corresponds to the second smallest SRS resource set ID (here, SRS resource set ID = 1) associated with usag = CB. The SRS resource set ID = 0 and the SRS resource set ID = 1 may each contain different SRS resources.

[0097] (Multi-TRP PDCCH) For the reliability of multi-TRP PDCCH based on non-single frequency network (SFN), the following Considerations 1 to 3 are being considered. [Consideration 1] Channel coding / rate matching is based on one repetition, and the same coded bits are repeated in other repetitions. [Consideration 2] Each repetition has the same number of control channel elements (CCEs), the same coded bits, and corresponds to the same DCI payload. [Consideration 3] Two or more PDCCH candidates are explicitly linked to each other. The UE knows that link before decoding.

[0098] The following Options 1-2, 1-3, 2, 3 for PDCCH repetition are being considered.

[0099] [Option 1-2] Two sets of PDCCH candidates (within a given search space (SS) set) are each associated with two TCI states of a CORESET. Here, the same CORESET, the same SS set, and PDCCH repetition in different monitoring occasions are used.

[0100] [Option 1-3] Two sets of PDCCH candidates are respectively associated with two SS sets. Both SS sets are associated with a CORESET, and each SS set is associated with only one TCI state of its CORESET. Here, the same CORESET, two SS sets, are used.

[0101] [Option 2] One SS set is associated with two different CORESETs.

[0102] [Option 3] Two SS sets are respectively associated with two CORESETs.

[0103] For non-SFN mode and Consideration 2 and Option 3, it is being considered to support Consideration 3.

[0104] For the extension of multi-TRP PDCCH reliability, the following multiplexing methods are being considered. [FDM]Either two sets of REG bundles, the CCEs of the transmitted PDCCH, two non-overlapping (in frequency) transmitted PDCCH repetitions, or a multi-chance transmitted PDCCH (in frequency) is associated with different TCI states. [SFN]PDCCH DMRS is associated with two TCI states within all REGs / CCEs of the PDCCH.

[0105] It is being considered that two linked SS sets for PDCCH repetition are set by RRC IE / MAC CE. It is being considered that two linked PDCCH candidates for PDCCH repetition are two PDCCH candidates having the same aggregation level and the same candidate index within the two linked SS sets.

[0106] (PDCCH / CORESET configuration) For the PDCCH / CORESET configuration of Rel.15, there is the following Case 0. [Case 0] One CORESET is configured with one TCI state without a CORESET pool index (information related to the TRP).

[0107] In the Rel.16 extension for PDCCH / CORESET, there is the following Case 1. [Case 1] For multi-DCI-based multi-TRP, a CORESET pool index (information related to the TRP) is configured for each CORESET (a CORESET pool index is associated with a certain CORESET).

[0108] For the Rel.17 extension for PDCCH / CORESET, there are the following Cases 2 / 3. [Case 2] As an extension of the SFN, one CORESET is configured / activated with up to two TCI states by the RRC IE / MAC CE (two TCI states are associated with a certain CORESET). The SFN may be used for both high speed train (HST) and reliability extension. [Case 3] As an extension of repetition, for PDCCH repetition, two PDCCH candidates within two search space (SS) sets are linked, and each SS set is associated with the corresponding CORESET (two PDCCH candidates / two SS sets / two CORESETS are linked). The two SS sets are associated with the same or different CORESETS. By the RRC IE / MAC CE, one CORESET can be associated with up to one TCI state. If the two SS sets are associated with different CORESETS, the PDCCH repetition is multi-TRP repetition. If the two SS sets are associated with the same CORESET (same TCI state), the PDCCH repetition is single-TRP repetition.

[0109] [Problem 1] The problem is whether any one of the above-mentioned cases 0 to 3 can be set simultaneously (in combination) for the UE in at least one of the following cases A to D. [Case A] Case 1 + 2 [Case B] Case 1 + 3 [Case C] Case 2 + 3 [Case D] Case 1 + 2 + 3

[0110] <Problem 2> The problem is whether an extension is required for the rules for setting / determining RLM-RS / BFD-RS for each of the above combination cases.

[0111] <Problem 3> The problem is whether an extension is required for handling QCL type D collisions for each of the above combination cases.

[0112] It is not clear whether any of these cases (PDCCH / CORESET) and multi-TRP PUSCH can be set simultaneously. If the setting is not done properly, there is a risk of causing a decrease in communication quality, a decrease in communication throughput, etc.

[0113] Therefore, the inventors conceived a method for setting CORESET and PUSCH.

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

[0115] In the present disclosure, "A / B / C", "at least one of A, B, and C" may be read interchangeably with each other. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, band may be read interchangeably with each other. In the present disclosure, index, ID, indicator, resource ID may be read interchangeably with each other. In the present disclosure, sequence, list, set, group, cluster, subset, etc. may be read interchangeably with each other. In the present disclosure, support, control, be able to control, operate, be able to operate may be read interchangeably with each other.

[0116] In the present disclosure, configure, activate, update, indicate, enable, specify, select may be read interchangeably with each other.

[0117] In the present disclosure, link, have a linkage, associate, correspond, map, repeat, relate may be read interchangeably with each other. In the present disclosure, allocate, assign, monitor, map may be read interchangeably with each other.

[0118] In the present disclosure, the upper layer signaling may be any one of, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameter, upper layer parameter, RRC information element (IE), RRC message, configuration may be read interchangeably with each other.

[0119] MAC signaling may use, for example, a MAC control element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0120] In the present disclosure, the MAC CE and the activation / deactivation command may be read as each other.

[0121] In the present disclosure, a beam, a spatial domain filter, a spatial setting, a TCI state, a UL TCI state, a unified TCI state, a unified beam, a common TCI state, a common beam, a TCI assumption, a QCL assumption, QCL parameters, a spatial domain reception filter, a UE spatial domain reception filter, a UE reception beam, a DL beam, a DL reception beam, DL precoding, a DL precoder, DL-RS, an RS of QCL type D for a TCI state / QCL assumption, an RS of QCL type A for a TCI state / QCL assumption, a spatial relationship, a spatial domain transmission filter, a UE spatial domain transmission filter, a UE transmission beam, a UL beam, a UL transmission beam, UL precoding, a UL precoder, PL-RS, an antenna port, a panel group, a beam group may be read as each other. In the present disclosure, a QCL type X-RS, a DL-RS associated with QCL type X, a DL-RS having QCL type X, a source of DL-RS, an SSB, a CSI-RS, an SRS may be read as each other.

[0122] In the present disclosure, panel, Uplink (UL) transmission entity, TRP, spatial relationship, Control Resource SET (CORESET), PDSCH, codeword, base station, an antenna port of a signal (e.g., a port of a Demodulation Reference Signal (DMRS)), an antenna port group of a signal (e.g., a DMRS port group), a group for multiplexing (e.g., a Code Division Multiplexing (CDM) group, a reference signal group, a CORESET group), a CORESET pool, a CORESET subset, CW, redundancy version (RV), layer (MIMO layer, transmission layer, spatial layer) may be mutually interchangeable.

[0123] The panel may be related to at least one of a group index of an SSB / CSI-RS group, a group index of group-based beam reporting, and a group index of an SSB / CSI-RS group for group-based beam reporting.

[0124] Also, the panel Identifier (ID) and the panel may be mutually interchangeable. That is, the TRP ID and the TRP, the CORESET group ID and the CORESET group, etc. may be mutually interchangeable.

[0125] In the present disclosure, the TRP, the transmission point, the panel, the DMRS port group, the CORESET pool, and one of two TCI states associated with one code point of the TCI field may be mutually interchangeable.

[0126] In the present disclosure, it may be assumed that single PDCCH is supported when multi-TRP uses an ideal backhaul. It may be assumed that multi-PDCCH is supported when non-ideal backhaul is used between multi-TRP.

[0127] Note that the ideal backhaul may also be referred to as DMRS port group type 1, reference signal related group type 1, antenna port group type 1, CORESET pool type 1, etc. The non-ideal backhaul may also be referred to as DMRS port group type 2, reference signal related group type 2, antenna port group type 2, CORESET pool type 2, etc. The names are not limited to these.

[0128] In the present disclosure, single TRP, single TRP system, single TRP transmission, single PDSCH may be read interchangeably with each other. In the present disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, multi-PDSCH may be read interchangeably with each other. In the present disclosure, single DCI, single PDCCH, multi-TRP based on single DCI, activation of two TCI states on at least one TCI code point may be read interchangeably with each other.

[0129] In the present disclosure, single TRP, a channel using single TRP, a channel using one TCI state / space relation, non-activation of multi-TRP by RRC / DCI, non-activation of multiple TCI states / space relations by RRC / DCI, no setting of one CORESET pool index (CORESETPoolIndex) value for any CORESET, and no mapping of any code point of the TCI field to two TCI states may be read interchangeably with each other.

[0130] In the present disclosure, multi-TRP, channels using multi-TRP, channels using multiple TCI states / spatial relations, the activation of multi-TRP by RRC / DCI, the activation of multiple TCI states / spatial relations by RRC / DCI, at least one of multi-TRP based on single DCI and multi-TRP based on multi-DCI may be mutually interchangeable. In the present disclosure, multi-TRP based on multi-DCI, the setting of a CORESET pool index (CORESETPoolIndex) value of 1 for a CORESET may be mutually interchangeable. In the present disclosure, multi-TRP based on single DCI, the mapping of at least one code point of a TCI field to two TCI states may be mutually interchangeable.

[0131] In the present disclosure, TRP#1 (the first TRP, TRP#0) may correspond to CORESET pool index = 0, or may correspond to another CORESET where the CORESET pool index is not set when the CORESET pool index = 1 is set for a certain CORESET, or may correspond to the first TCI state among two TCI states corresponding to one code point of the TCI field. TRP#2 (the second TRP, TRP#1) may correspond to CORESET pool index = 1, or may correspond to the second TCI state among two TCI states corresponding to one code point of the TCI field.

[0132] In the present disclosure, a plurality of SS sets (SS set pairs) having a linkage (linkage, connection, cooperation), linked SS sets, may mean that, for PDCCH repetition, one SS set is linked to another SS set via RRC IE / MAC CE. An SS set having no linkage (an individual SS set) may mean, via RRC IE / MAC CE, that the SS set is not linked to another SS set via RRC IE / MAC CE.

[0133] In the present disclosure, linked pairs with linkages may be read interchangeably with each other. In the present disclosure, single entities without linkages may be read interchangeably with each other.

[0134] In the present disclosure, linked SS sets, linked CORESETs, linked PDCCH candidates / PDCCHs, CORESETs associated with linked SS sets, PDCCH candidates / PDCCHs within linked SS sets, may be read interchangeably with each other. In the present disclosure, two linked CORESETs may mean two CORESETs respectively associated with two linked SS sets. In the present disclosure, two linked PDCCH candidates / PDCCHs may be two PDCCH candidates / PDCCHs having the same aggregation level and the same candidate index within two linked SS sets.

[0135] In the present disclosure, receiving a DL signal (PDSCH / PDCCH) using an SFN may mean at least one of using the same time and frequency resources in reception from multiple TRPs and receiving the same data (PDSCH) or control information (PDCCH). Also, receiving a DL signal using an SFN may mean at least one of using the same time and frequency resources in reception using multiple TCI states / spatial domain filters / beams / QCLs and receiving the same data or control information.

[0136] In the present disclosure, spatial relation information (SRI), combinations of SRI, SRI for codebook-based transmission, combinations of non-codebook-based SRI, spatialRelationInfo, UL TCI, TCI states, Unified TCI, QCL, etc. may be read interchangeably with each other.

[0137] In the present disclosure, the first TRP and the second TRP may be mutually interchanged with the first PUSCH and the second PUSCH, the first PUSCH transmission opportunity and the second PUSCH transmission opportunity, the first SRI and the second SRI, etc.

[0138] In the following embodiments, the repeated transmission of PUSCH for multiple TRPs may be mutually interchanged with PUSCH across multiple TRPs, repeated PUSCH across multiple TRPs, simply repeated PUSCH, repeated transmission, multiple PUSCH transmissions, etc. Also, a single PUSCH transmission for a single TRP may be referred to as simply a single PUSCH transmission, PUSCH transmission in a single TRP, etc.

[0139] In the present disclosure, the repeated transmission of PUSCH for a single TRP may mean the repeated transmission of multiple PUSCHs transmitted using the same SRI / beam / precoder.

[0140] In the present disclosure, the repeated transmission of PUSCH for multiple TRPs may mean the repeated transmission of multiple PUSCHs transmitted using different multiple SRI / beam / precoders. The repeated transmission and the multiple SRI / beam / precoders may correspond cyclically, sequentially by a specific number, or in a correspondence using a half - half pattern (mapping), as detailed in the above mapping pattern.

[0141] In the present disclosure, multi - TRP PUSCH repetition, multi - TRP PUSCH repetition in Rel.17, multiple PUSCH repetitions for multiple TRPs, single - DCI - based multi - TRP PUSCH repetition, may be mutually interchanged.

[0142] In the present disclosure, the first TRP (e.g., TRP#0, CORESET pool index = 0) and the second TRP (e.g., TRP#1, CORESET pool index = 1) have a first spatial relationship (e.g., 1st It may correspond to the first spatial relation / beam / UL TCI / QCL and the second spatial relation / beam / UL TCI / QCL respectively. Alternatively, the first TRP and the second TRP may correspond to the spatial relation / beam / UL TCI / QCL associated with the first SRI field or the first TPMI field and the spatial relation / beam / UL TCI / QCL associated with the second SRI field or the second TPMI field respectively. Alternatively, the first TRP and the second TRP may correspond to the first SRS resource set with the usage of CB / NCB (for example, usage = CB / NCB) and the second SRS resource set with the usage of CB / NCB (for example, usage = CB / NCB) respectively.

[0143] In each embodiment of the present disclosure, the case where the number of multiple TRPs, multiple SRIs, etc. is two is taken as the main example for description, but these numbers may also be three or more.

[0144] In addition, each embodiment of the present disclosure is also appropriately applicable to the repeated transmission of any UL signal / channel for multiple TRPs, and the PUSCH of the present disclosure may be read as any UL signal / channel. For example, each embodiment of the present disclosure is also appropriately applicable to the repeated transmission of PUCCH for multiple TRPs, and the PUSCH of the present disclosure may be read as PUCCH.

[0145] (Wireless communication method) In the present disclosure, the indication of multi-TRP PUSCH repetition may be two fields / values for at least one piece of indication information among an SRI (SRS resource indicator), a TPMI / transmission rank (precoding information and number of layers), a TPC (TPC command for scheduled PUSCH), an OLPC (open-loop power control parameter set indication), and a phase tracking reference signal (PTRS)-demodulation reference signal (DMRS) association in DCI.

[0146] At least one RRC IE of multi-TRP PUSCH repetition and the presence of two fields for the indication information thereof may be configured. This RRC IE may be configured for at least one of a serving cell, a CORESET, a search space (SS) set, a BWP, and a PUSCH configuration (PUSCH-Config).

[0147] In the present disclosure, SRI#1, the first SRI, the first SRI field, the first value of the SRI field, and the first value associated with the code point of the SRI field may be read interchangeably with each other. In the present disclosure, SRI#2, the second SRI, the second SRI field, the second value of the SRI field, and the second value associated with the code point of the SRI field may be read interchangeably with each other.

[0148] In the present disclosure, the SRI field, the field of precoding information (TPMI) and the number of layers, the TPC command field, the OLPC parameter set indication field, and the PTRS-DMRS association field may be read interchangeably with each other.

[0149] The UE may receive configuration information (e.g., RRC IE / MAC CE) regarding one or more TCI states / CORESET pool indexes for one or more CORESETs.

[0150] In Case 3 / B / C / D, the UE may receive configuration information (e.g., RRC IE / MAC CE) regarding two linked SS sets / CORESETs / PDCCHs.

[0151] <First Embodiment> For the combination of Case 1 and multi-TRP PUSCH repetition, either of the following Option 1 and Option 2 may be applicable.

[0152] 《Option 1》 The combination of Case 1 and multi-TRP PUSCH repetition is not supported.

[0153] For the serving cell (or the BWP within the serving cell), if the CORESET pool index is configured, the UE may follow at least one of the following Configuration Methods 1 to 4.

[0154] [Configuration Method 1] Any CORESET within the serving cell (or the BWP within the serving cell) cannot be configured with an indication of multi-TRP PUSCH repetition. The indication of multi-TRP PUSCH repetition may be two SRI / TPMI / TPC / OLPC / PTRS-DMRS fields in the DCI.

[0155] [Configuration Method 2] Any SS set within the serving cell (or the BWP within the serving cell) cannot be configured with an indication of multi-TRP PUSCH repetition. The indication of multi-TRP PUSCH repetition may be two SRI / TPMI / TPC / OLPC / PTRS-DMRS fields in the DCI.

[0156] [Configuration Method 3] The serving cell (or the BWP within the serving cell) cannot be configured with an indication of multi-TRP PUSCH repetition. The indication of multi-TRP PUSCH repetition may be two SRI / TPMI / TPC / OLPC / PTRS-DMRS fields within the DCI.

[0157] [Configuration Method 4] The SRS resource set may follow at least one of the following Options 1 and 2. [[Option 1]] Only one SRS resource set having a CB / NCB use can be configured. [[Option 2]] Two SRS resource sets having a CB / NCB use can be configured. The two SRS resource sets respectively correspond to two CORESET pool indexes. Only one SRI is indicated by the DCI.

[0158] According to this Option 1, it is clear that the combination of Case 1 and multi-TRP PUSCH repetition is not supported.

[0159] 《Option 2》 The combination of Case 1 and multi-TRP PUSCH repetition is supported.

[0160] The UE may follow at least one of the following Options 2-1 to 2-3.

[0161] 《Option 2-1》 For the serving cell (or the BWP within the serving cell), if a CORESET pool index is configured for (any (at least one) CORESET), the UE may follow at least one of the following Configuration Methods 1 to 4.

[0162] [Configuration Method 1] Any CORESET within the serving cell (or the BWP within the serving cell) can be configured with an indication of multi-TRP PUSCH repetition.

[0163] [Configuration Method 2] Any SS set within the serving cell (or the BWP within the serving cell) can be configured with an indication of multi-TRP PUSCH repetition.

[0164] [Configuration Method 3] The serving cell (or the BWP within the serving cell) can be configured with an indication of multi-TRP PUSCH repetition.

[0165] [Configuration Method 4] Only two SRI fields corresponding to the same SRS resource set are supported. The SRS resource set may follow at least one of the following Options 1 and 2. [[Option 1]] Only one SRS resource set having a CB / NCB use can be configured. Both of the two SRI fields correspond to that one SRS resource set. [[Option 2]] Two SRS resource sets having a CB / NCB use can be configured. The two SRS resource sets respectively correspond to two CORESET pool indexes. The two SRI fields correspond to the same SRS resource set corresponding to the CORESET pool index of the PDCCH.

[0166] In Option 2-1, the example in FIG. 6 may be supported. In this example, in the PDCCH corresponding to CORESET Pool Index = 1, DCI for scheduling PUSCH repetitions #1 to #4 is transmitted. In that DCI, the first SRI field indicates SRI #1, and the second SRI field indicates SRI #2. Each of PUSCH repetitions #1 and #3 corresponds to SRI #1, and each of PUSCH repetitions #2 and #4 corresponds to SRI #2.

[0167] In Option 1, this example may not be supported.

[0168] 《Option 2-2》 For a serving cell (or a BWP within that serving cell), if a CORESET pool index is set (for any CORESET), the UE may follow at least one of the following setting methods 1 and 2.

[0169] [Setting method 1] For one CORESET with an explicitly set CORESET pool index, that CORESET, or the SS set associated with that CORESET, cannot have an indication of multi-TRP PUSCH repetition set.

[0170] [Setting method 2] For one CORESET without an explicitly set CORESET pool index, that CORESET, or the SS set associated with that CORESET, can have an indication of multi-TRP PUSCH repetition set.

[0171] In Option 2-2, the example of FIG. 6 described above may not be supported, and the example of FIG. 7 may be supported. In this example, in the PDCCH in the CORESET where the CORESET pool index is not set, DCI that schedules PUSCH repetitions #1 to #4 is transmitted. In that DCI, the first SRI field indicates SRI #1, and the second SRI field indicates SRI #2. Each of PUSCH repetitions #1 and #3 corresponds to SRI #1, and each of PUSCH repetitions #2 and #4 corresponds to SRI #2.

[0172] 《Option 2-3》 For a serving cell (or a BWP within that serving cell), if a CORESET pool index is set (for any (at least one) CORESET), only one specific TRP transmits DCI for multi-TRP repetition (PDCCH from one specific CORESET pool index is transmitted).

[0173] For example, the specific TRP may correspond to CORESET pool index = 0 (the specific CORESET pool index may be 0). Only the CORESET or SS set associated with CORESET pool index = 0 may transmit DCI for multi-TRP repetition.

[0174] If the specific TRP corresponds to CORESET pool index = 0, the example of FIG. 8A may not be supported. In this example, in the PDCCH in the CORESET where CORESET pool index = 1 is set, DCI that schedules PUSCH repetitions #1 to #4 is transmitted. In that DCI, the first SRI field indicates SRI #1, and the second SRI field indicates SRI #2. Each of PUSCH repetitions #1 and #3 corresponds to SRI #1, and each of PUSCH repetitions #2 and #4 corresponds to SRI #2.

[0175] When a specific TRP corresponds to CORESET pool index = 0, the example of FIG. 8B may be supported. In this example, in the PDCCH in the CORESET set to CORESET pool index = 0, DCI that schedules PUSCH repetitions #1 to #4 is transmitted. In that DCI, the first SRI field indicates SRI #1, and the second SRI field indicates SRI #2. Each of PUSCH repetitions #1 and #3 corresponds to SRI #1, and each of PUSCH repetitions #2 and #4 corresponds to SRI #2.

[0176] For example, a specific TRP may correspond to CORESET pool index = 1 (the specific CORESET pool index may be 1). Only the CORESET or SS set associated with CORESET pool index = 1 may transmit DCI for multi-TRP repetitions.

[0177] When a specific TRP corresponds to CORESET pool index = 1, the example of FIG. 8A may be supported, and the example of FIG. 8B may not be supported.

[0178] According to this Option 2, the operation for the combination of Case 1 and multi-TRP PUSCH repetitions is clarified.

[0179] <Second Embodiment> For the combination of Case 2 and multi-TRP PUSCH repetitions, either of the following Options 1 and 2 may be applied.

[0180] 《Option 1》 The combination of Case 2 and multi-TRP PUSCH repetitions is not supported.

[0181] For a CORESET with two TCI states set / activated, the CORESET or the SS set associated with the CORESET cannot be set with an instruction for multi-TRP PUSCH repetitions.

[0182] According to this Option 1, it is clear that the combination of Case 2 and multi-TRP PUSCH repetition is not supported.

[0183] 《Option 2》 The combination of Case 2 and multi-TRP PUSCH repetition is supported.

[0184] For two TCI states configured / activated for a CORESET, the CORESET or the SS set associated with the CORESET can be configured with an indication of multi-TRP PUSCH repetition.

[0185] The default QCL / spatial relationship for multiple PUSCH repetitions for two TRPs may follow the two TCI states of the PDCCH.

[0186] In Option 2, the example in Figure 9 may be supported. In this example, in the PDCCH of a CORESET with two activated TCI states, DCI for scheduling PUSCH repetitions #1 to #4 is transmitted. In the DCI, the first SRI field indicates SRI#1, and the second SRI field indicates SRI#2. Each of PUSCH repetitions #1 and #3 corresponds to SRI#1, and each of PUSCH repetitions #2 and #4 corresponds to SRI#2.

[0187] In Option 1, this example may not be supported.

[0188] According to this Option 2, the operation for the combination of Case 2 and multi-TRP PUSCH repetition is clarified.

[0189] 《Variant 1》 If a CORESET (PDCCH / DCI within that CORESET) with a CORESET pool index (the CORESET pool index is set) schedules PUSCH repetitions, the PUSCH repetitions are affected by the CORESET pool index of the CORESET that schedules them. For example, which SRI / TPMI field is used for each PUSCH repetition may be based on the CORESET pool index of the CORESET that schedules it.

[0190] The SRI for the first (odd-numbered (1st, 3rd,...)) PUSCH repetitions may correspond to the SRI / TPMI field associated with the CORESET pool index (TRP index).

[0191] In the example of FIG. 10A, in the PDCCH in the CORESET with the CORESET pool index = 0 (the PDCCH from the first TRP (TRP#0)), a DCI that schedules PUSCH repetitions #1 to #4 is transmitted. This DCI contains two SRI fields. The first PUSCH repetition #1 is based on the first SRI field corresponding to the CORESET pool index = 0 (the first TRP) corresponding to that PDCCH (uses the beam (spatial relationship) indicated in the first SRI field). PUSCH repetition #2 is based on the second SRI field corresponding to a CORESET pool index = 1 (the second TRP) different from that PDCCH (uses the beam (spatial relationship) indicated in the second SRI field).

[0192] The mapping of the SRI field (beam) for subsequent PUSCH repetitions is repeated. That is, PUSCH repetition #3 is based on the first SRI field, just like PUSCH repetition #1. PUSCH repetition #4 is based on the second SRI field, just like PUSCH repetition #2.

[0193] In the example of FIG. 10B, in the PDCCH (PDCCH from the second TRP (TRP#1)) in the CORESET with the CORESET pool index = 1 set, a DCI that schedules PUSCH repetitions #1 to #4 is transmitted. This DCI includes two SRI fields. The first PUSCH repetition #1 is based on the second SRI field corresponding to the CORESET pool index = 1 (second TRP) corresponding to that PDCCH (uses the beam (spatial relationship) indicated in the second SRI field). PUSCH repetition #2 is based on the first SRI field corresponding to a CORESET pool index = 0 (first TRP) different from that PDCCH (uses the beam (spatial relationship) indicated in the first SRI field).

[0194] The mapping of the SRI field (beam) for subsequent PUSCH repetitions is repeated. That is, PUSCH repetition #3 is based on the second SRI field, similar to PUSCH repetition #1. PUSCH repetition #4 is based on the first SRI field, similar to PUSCH repetition #2.

[0195] According to this modification example, the overhead of the instruction of the beam mapping order can be reduced.

[0196] 《Modification Example 2》 If a CORESET (PDCCH / DCI within that CORESET) without a CORESET pool index (the CORESET pool index is not set) schedules PUSCH repetitions, the PUSCH repetitions may be based on the CORESET pool index of the CORESET that schedules them. For example, which SRI / TPMI field is used for each repetition is affected by the CORESET pool index of the CORESET that schedules it (the fact that there is no CORESET pool index). In this case, the PUSCH repetitions may be single-TRP PUSCH repetitions (PUSCH repetitions using the same beam (spatial relationship)).

[0197]

[0197] In the example of FIG. 11, in the PDCCH in a CORESET where the CORESET pool index is not set, DCI that schedules PUSCH repetitions #1 to #4 is transmitted. This DCI may include one or two SRI fields. Each of PUSCH repetitions #1 to #4 is based on the first SRI field (uses the beam (spatial relationship) indicated in the first SRI field).

[0198] According to this modification example, even when the CORESET pool index is not set, the beam for each PUSCH repetition can be appropriately determined.

[0199] <<Modification Example 3>> If a CORESET having a CORESET pool index (a CORESET in which the CORESET pool index is set) (PDCCH / DCI within that CORESET) schedules a PUSCH repetition, the PUSCH repetition is affected by the CORESET pool index of the CORESET that schedules it. The PUSCH repetition scheduled using a CORESET having a CORESET pool index may be a single TRP PUSCH repetition (PUSCH repetitions using the same beam (spatial relationship)).

[0200] For codebook PUSCH, if the PUSCH is scheduled using CORESET pool index = 0, the first SRI field and the SRS resource set having the CB usage (usage = CB) and having the first ID from the lowest (minimum) or highest (maximum) ID may be applied. If the PUSCH is scheduled using CORESET pool index = 1, the second SRI field and the SRS resource set having the CB usage (usage = CB) and having the second ID from the lowest (minimum) or highest (maximum) ID may be applied. If a single TRP is indicated, the first TPMI field may be applied.

[0201] In the example of FIG. 12A, in the PDCCH (PDCCH from the first TRP) in the CORESET with the CORESET pool index = 0 set, DCI that schedules PUSCH repetitions #1 to #4 is transmitted. This DCI may include one or two SRI fields. Each of PUSCH repetitions #1 to #4 is based on the first SRI field / the first SRS resource set (uses the beam (spatial relationship) indicated in the first SRI field / the first SRS resource set).

[0202] In the example of FIG. 12B, in the PDCCH (PDCCH from the second TRP) in the CORESET with the CORESET pool index = 1 set, DCI that schedules PUSCH repetitions #1 to #4 is transmitted. This DCI may include two SRI fields. Each of PUSCH repetitions #1 to #4 is based on the second SRI field / the second SRS resource set (uses the beam (spatial relationship) indicated in the second SRI field / the second SRS resource set).

[0203] For non-codebook PUSCH, if the PUSCH is scheduled using the CORESET pool index = 0, the first SRI field and the SRS resource set having the NCB usage (usage = NCB) and having the first ID from the lowest (minimum) or highest (maximum) ID may be applied. If the PUSCH is scheduled using the CORESET pool index = 1, the second SRI field and the SRS resource set having the NCB usage (usage = NCB) and having the second ID from the lowest (minimum) or highest (maximum) ID may be applied.

[0204] According to this modification example, when the CORESET pool index is set, the beam of the PUSCH repetition to a single TRP can be appropriately determined.

[0205] <Third Embodiment> For the combination of Case 3 and multi-TRP PUSCH repetition, either of the following Options 1 and 2 may be applicable.

[0206] 《Option 1》 The combination of Case 3 and multi-TRP PUSCH repetition is not supported.

[0207] For the linked SS set / CORESET configured for PDCCH repetition, the linked SS set / CORESET cannot be configured with an indication of multi-TRP PUSCH repetition.

[0208] According to this Option 1, it is clear that the combination of Case 3 and multi-TRP PUSCH repetition is not supported.

[0209] 《Option 2》 The combination of Case 3 and multi-TRP PUSCH repetition is supported.

[0210] For the linked SS set / CORESET configured for PDCCH repetition, the linked SS set / CORESET can be configured with an indication of multi-TRP PUSCH repetition.

[0211] The indication regarding the timing for multiple PUSCH repetitions may follow the indication from the reference PDCCH. The reference PDCCH may refer to the earlier or later one of the two linked PDCCHs in terms of time, or the first or last one in terms of time, or the PDCCH corresponding to the highest or lowest CORESET ID, or the PDCCH corresponding to the highest or lowest SS set ID.

[0212] In Option 2, the example in FIG. 13 may be supported. In this example, PDCCH repetitions #1 and #2 (two CORESET / SS sets corresponding to PDCCH repetitions #1 and #2 respectively) are linked. Each of the two CORESETs may activate one TCI state. In PDCCH repetitions #1 and #2, DCI for scheduling PUSCH repetitions #1 to #4 is transmitted. In the DCI, the first SRI field indicates SRI #1, and the second SRI field indicates SRI #2. Each of PUSCH repetitions #1 and #3 corresponds to SRI #1, and each of PUSCH repetitions #2 and #4 corresponds to SRI #2.

[0213] In Option 1, this example may not be supported.

[0214] According to this Option 2, the operation for the combination of Case 3 and multi-TRP PUSCH repetitions is clarified.

[0215] <Fourth Embodiment> For the combination of Case B (Case 1 + 3) and multi-TRP PUSCH repetitions, either of the following Option 1 and Option 2 may be applied.

[0216] 《Option 1》 If a CORESET pool index is set for any (at least one) CORESET in a serving cell (or a BWP within the serving cell), and two linked CORESETs for PDCCH repetitions are set with the same CORESET pool index, the two linked CORESET / SS sets cannot be set with an indication of multi-TRP PUSCH repetitions.

[0217] For an unlinked (having no linkage) CORESET / SS set, the first embodiment may be applied.

[0218] Regarding the SRS resource set, Option 1 of the first embodiment may be applied.

[0219] According to this Option 1, it is clear that the combination of Case B and multi-TRP PUSCH repetition is not supported.

[0220] 《Option 2》 If a CORESET pool index is set for any (at least one) CORESET in a serving cell (or a BWP within that serving cell), and two linked CORESETs for PDCCH repetition are set with the same CORESET pool index, then the two linked CORESET / SS sets can be set with an indication of multi-TRP PUSCH repetition.

[0221] For unlinked (having no linkage) CORESET / SS sets, the first embodiment may be applied.

[0222] Regarding the SRS resource set, Option 2-1 of the first embodiment may be applied.

[0223] In Option 2, the example in FIG. 14 may be supported. In this example, PDCCH repetitions #1 and #2 (two CORESET / SS sets corresponding to PDCCH repetitions #1 and #2 respectively) are linked. The two CORESETs corresponding to PDCCH repetitions #1 and #2 respectively are set with the same CORESET pool index = 0. In each of PDCCH repetitions #1 and #2, DCI for scheduling PUSCH repetitions #1 to #4 is transmitted. In that DCI, the first SRI field indicates SRI#1, and the second SRI field indicates SRI#2. Each of PUSCH repetitions #1 and #3 corresponds to SRI#1, and each of PUSCH repetitions #2 and #4 corresponds to SRI#2.

[0224] In Option 1, this example does not have to be supported.

[0225] Only when both of the two linked CORESETs for PDCCH repetition are set with CORESET pool index = 0, the two linked CORESET / SS sets may be able to set the indication of multi-TRP PUSCH repetition.

[0226] Only when both of the two linked CORESETs for PDCCH repetition are set with CORESET pool index = 1, the two linked CORESET / SS sets may be able to set the indication of multi-TRP PUSCH repetition.

[0227] According to this Option 2, the operation for the combination of Case B and multi-TRP PUSCH repetition is clarified.

[0228] <Fifth Embodiment> For the combination of Case B (Case 1 + 3) and multi-TRP PUSCH repetition, either of the following Option 1 and Option 2 may be applied.

[0229] 《Option 1》 If the CORESET pool index is set for any (at least one) CORESET in a serving cell (or a BWP within the serving cell), and the two linked CORESETs for PDCCH repetition are set with two different CORESET pool indexes respectively, the two linked CORESET / SS sets cannot set the indication of multi-TRP PUSCH repetition.

[0230] For a non-linked (having no linkage) CORESET / SS set, the first embodiment may be applied.

[0231] According to this Option 1, it is clear that the combination of Case B and multi-TRP PUSCH repetition is not supported.

[0232] 《Option 2》 If the CORESET pool index is set for any (at least one) CORESET in a serving cell (or the BWP within that serving cell), and two linked CORESETs for PDCCH repetition are set with different two CORESET pool indexes respectively, the two linked CORESET / SS sets can be set with an indication of multi-TRP PUSCH repetition.

[0233] For an unlinked (without linkage) CORESET / SS set, the first embodiment may be applied.

[0234] In Option 2, the example in Figure 15 may be supported. In this example, PDCCH repetitions #1 and #2 (two CORESET / SS sets corresponding to PDCCH repetitions #1 and #2 respectively) are linked. The CORESET corresponding to PDCCH repetition #1 is set with CORESET pool index = 0, and the CORESET corresponding to PDCCH repetition #2 is set with CORESET pool index = 1. In each of PDCCH repetitions #1 and #2, DCI for scheduling PUSCH repetitions #1 to #4 is transmitted. In that DCI, the first SRI field indicates SRI#1, and the second SRI field indicates SRI#2. Each of PUSCH repetitions #1 and #3 corresponds to SRI#1, and each of PUSCH repetitions #2 and #4 corresponds to SRI#2.

[0235] In Option 1, this example may not be supported.

[0236] According to this Option 2, the operation for the combination of Case B and multi-TRP PUSCH repetition becomes clear.

[0237] <Embodiment 6> This embodiment relates to the combination of Case B (Case 1 + 3) and multi-TRP PUSCH repetition.

[0238] When two linked CORESETs for PDCCH repetition are set with the same CORESET pool index, the fourth embodiment (Option 1 or 2) may be applied.

[0239] When Option 1 of the fourth embodiment is applied, the example of FIG. 14 described above may not be supported. When Option 2 of the fourth embodiment is applied, the example of FIG. 14 described above may be supported.

[0240] When two linked CORESETs for PDCCH repetition are set with two different CORESET pool indexes respectively, the fifth embodiment (Option 1 or 2) may be applied.

[0241] When Option 1 of the fifth embodiment is applied, the example of FIG. 15 described above may not be supported. When Option 2 of the fifth embodiment is applied, the example of FIG. 15 described above may be supported.

[0242] According to this embodiment, the operation for the combination of Case B and multi-TRP PUSCH repetition is clarified.

[0243] <Embodiment 7> This embodiment relates to the combination of Case C (Case 2 + 3) and multi-TRP PUSCH repetition.

[0244] When a certain CORESET has no linkage and two TCI states are activated, and the same CORESET pool index is set, the second embodiment (Option 1 or 2) may be applied.

[0245] When Option 1 of the second embodiment is applied, the example in FIG. 9 described above may not be supported. When Option 2 of the second embodiment is applied, the example in FIG. 9 described above may be supported.

[0246] When two CORESETs are linked for PDCCH repetition and each CORESET activates one TCI state, the third embodiment (Option 1 or 2) may be applied.

[0247] When Option 1 of the third embodiment is applied, the example in FIG. 13 described above may not be supported. When Option 2 of the third embodiment is applied, the example in FIG. 13 described above may be supported.

[0248] According to this embodiment, the operation for the combination of Case C and multi-TRP PUSCH repetition is clarified.

[0249] <Eighth Embodiment> This embodiment relates to whether each of the above embodiments is applied to the configured grant PUSCH.

[0250] If the dynamic multi-TRP PUSCH repetition based on any of the above embodiments is not supported, the configured grant multi-TRP PUSCH repetition may follow any one of Options 1 to 4 below.

[0251] [Option 1] Both type 1 and type 2 configured grant multi-TRP PUSCH repetitions cannot be configured / indicated.

[0252] [Option 2] Both type 1 and type 2 configured grant multi-TRP PUSCH repetitions can be configured / indicated.

[0253] [Option 3] Type 1 configured grant multi-TRP PUSCH repetition can be configured / indicated. Type 2 configured grant multi-TRP PUSCH repetition cannot be configured / indicated.

[0254] [Option 4] Type 2 configured grant multi-TRP PUSCH repetition can be configured / indicated. Type 1 configured grant multi-TRP PUSCH repetition cannot be configured / indicated.

[0255] In this disclosure, the support for Type 1 / Type 2 configured grant multi-TRP PUSCH repetition may mean the following provisions. [Provisions] · For Type 1 or Type 2 configured grant multi-TRP PUSCH repetition, in the ConfiguredGrantConfig, the second field of P0-α (p0-PUSCH-Alpha) and the powerControlLoopToUse is introduced. · For Type 1 configured grant multi-TRP PUSCH repetition, in the rrc-ConfiguredUplinkGrant, the second fields of pathlossReferenceIndex, srs-ResourceIndicator, and precodingAndNumberOfLayers are introduced. · For Type 1 configured grant multi-TRP PUSCH repetition, two SRI / TPMI / TPC / OLPC / PTRS-DMRS are indicated via the activated DCI.

[0256] According to this embodiment, it becomes clear whether any of the foregoing embodiments is applied to the configured grant multi-TRP PUSCH repetition.

[0257] [Other Embodiments] Upper layer parameters (RRC information elements) / UE capabilities corresponding to at least one function (feature) in each embodiment may be defined. The UE capabilities may indicate whether this function is supported or not.

[0258] A UE with upper layer parameters corresponding to that function set may perform that function. It may be specified that "a UE for which upper layer parameters corresponding to that function are not set does not perform that function (for example, applying the operation of Rel.15 / 16)".

[0259] A UE that has reported UE capabilities indicating support for that function may perform that function. It may be specified that "a UE that has not reported UE capabilities indicating support for that function does not perform that function (for example, applying the operation of Rel.15 / 16)".

[0260] If a UE has reported UE capabilities indicating support for that function and upper layer parameters corresponding to that function are set, the UE may perform that function. It may be specified that "if a UE does not report UE capabilities indicating support for that function or upper layer parameters corresponding to that function are not set, the UE does not perform that function (for example, applying the operation of Rel.15 / 16)".

[0261] UE capabilities may indicate at least one of the following. · Whether it supports Option 2 / Variation 1 / Variation 2 / Variation 3 of the first to fifth embodiments. · Whether it supports the sixth / seventh / eighth embodiments. · Whether it supports Case A. · Whether it supports Case B. · Whether it supports Case C. · Whether it supports Case D.

[0262] According to the above UE capabilities / upper layer parameters, the UE can implement the above functions while maintaining compatibility with existing specifications.

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

[0264] FIG. 16 is a diagram showing an example of the 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), 5th generation mobile communication system New Radio (5G NR), etc., which are specified by the Third Generation Partnership Project (3GPP).

[0265] Further, the wireless communication system 1 may support dual connectivity (multi-RAT dual connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

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

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

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

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

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

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

[0272] The plurality of base stations 10 may be connected by wire (e.g., an optical fiber compliant with Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11 corresponding to the upper-level 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.

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

[0274] The user terminal 20 may be a terminal corresponding to at least one of communication systems such as LTE, LTE-A, 5G, etc.

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

[0276] The wireless access method may be referred to as a waveform. Note that in the wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the wireless access methods of the UL and the DL.

[0277] In the wireless communication system 1, as downlink channels, a physical downlink shared channel (PDSCH) shared by each user terminal 20, a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc. may be used.

[0278] Also, in the wireless communication system 1, as uplink channels, a physical uplink shared channel (PUSCH) shared by each user terminal 20, a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. may be used.

[0279] The PDSCH is used to transmit user data, upper layer control information, System Information Block (SIB), etc. The PUSCH may be used to transmit user data, upper layer control information, etc. Also, the PBCH may be used to transmit the Master Information Block (MIB).

[0280] The PDCCH may be used to transmit lower layer control information. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.

[0281] Note that the DCI for scheduling the PDSCH may be called DL assignment, DL DCI, etc., and the DCI for scheduling the PUSCH may be called UL grant, UL DCI, etc. Note that the PDSCH may be overwritten with DL data, and the PUSCH may be overwritten with UL data.

[0282] For the detection of the PDCCH, a control resource set (COntrol REsource SET (CORESET)) and a search space may be used. The CORESET corresponds to the resource for searching for DCI. The search space corresponds to the search area and search method for PDCCH candidates (PDCCH candidates). One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0283] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc. in the present disclosure may be read interchangeably with each other.

[0284] Uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be referred to as, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) may be transmitted by PUCCH. A random access preamble for connection establishment with a cell may be transmitted by PRACH.

[0285] Note that in the present disclosure, downlink, uplink, etc. may be expressed without "link". Also, the beginning of various channels may be expressed without "Physical".

[0286] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. may be transmitted.

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

[0288] Also, in the wireless communication system 1, as the uplink reference signal (Uplink Reference Signal (UL-RS)), a sounding reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted. Note that DMRS may also be called a UE-specific reference signal.

[0289] (Base station) FIG. 17 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 transmission / reception unit 120, a transmission / reception antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may be provided.

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

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

[0292] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission / reception, measurement, etc. using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal, and transfer it to the transmission / reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of a communication channel, state management of the base station 10, management of radio resources, etc.

[0293] The transmission / reception 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 transmission / reception unit 120 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc. described based on the common knowledge in the technical field related to the present disclosure.

[0294] The transmission / reception unit 120 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122. The reception unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0295] The transmission / reception antenna 130 can be composed of an antenna described based on the common understanding in the technical field related to the present disclosure, such as an array antenna.

[0296] The transmission / reception unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, etc. The transmission / reception unit 120 may receive the above-described uplink channel, uplink reference signal, etc.

[0297] The transmission / reception unit 120 may form at least one of a transmission beam and a reception beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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

[0299] The transceiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit sequence to be transmitted, and output a baseband signal.

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

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

[0302] The transceiver unit 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 on the acquired baseband signal, and acquire user data, etc.

[0303] The transmission / reception unit 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)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0304] The transmission path interface 140 may transmit and receive signals (backhaul signaling) to and from 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.

[0305] Note that the transmission unit and reception unit of the base station 10 in the present disclosure may be configured by at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140.

[0306] The transmission / reception unit 120 may transmit setting information (e.g., RRC IE / MAC CE) regarding one or more transmission configuration indication (TCI) states for one or more control resource sets (CORESET), and may transmit downlink control information for scheduling a plurality of physical uplink shared channel repetitions using the CORESET. The control unit 110 may control the reception of the plurality of physical uplink shared channel repetitions based on two values of parameters in the downlink control information.

[0307] The transmission / reception unit 120 may transmit setting information (e.g., RRC IE / MAC CE) regarding two linked search space sets, and may transmit downlink control information for scheduling a plurality of physical uplink shared channel repetitions using the two linked search space sets. The control unit 110 may control reception of the plurality of physical uplink shared channel repetitions based on two values of parameters in the downlink control information.

[0308] (User Equipment) FIG. 18 is a diagram showing an example of the configuration of a user equipment according to an embodiment. The user equipment 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. Note that one or more of the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may be provided.

[0309] Note that in this example, the functional blocks of the characteristic portions in the present embodiment are mainly shown, and the user equipment 20 may be assumed to have other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

[0310] The control unit 210 controls the entire user equipment 20. The control unit 210 may be configured from a controller, a control circuit, etc., which are described based on common knowledge in the technical field related to the present disclosure.

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

[0312] 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 composed of 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 the common understanding in the technical field related to the present disclosure.

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

[0314] The transceiver antenna 230 may be composed of an antenna described based on the common understanding in the technical field related to the present disclosure, such as an array antenna.

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

[0316] The transceiver unit 220 may form at least one of a transmission beam and a reception beam by using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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

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

[0319] Whether to apply DFT processing may be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is enabled, the transmission / reception unit 220 (transmission processing unit 2211) may perform DFT processing as the above-mentioned transmission processing to transmit the channel using the DFT-s-OFDM waveform, or if not, it may not perform DFT processing as the above-mentioned transmission processing.

[0320] The transmission / reception unit 220 (RF unit 222) may perform modulation to the radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the signal in the radio frequency band via the transmission / reception antenna 230.

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

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

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

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

[0325] The transmission / reception unit 220 may receive configuration information (e.g., RRC IE / MAC CE) regarding one or more transmission configuration indication (TCI) states for one or more control resource sets (CORESET), and receive downlink control information for scheduling a plurality of physical uplink shared channel repetitions using the CORESET. The control unit 210 may control the transmission of the plurality of physical uplink shared channel repetitions based on two values of parameters in the downlink control information.

[0326] The two values are two fields of a sounding reference signal indicator, and the control unit 210 may map the two fields to the plurality of physical uplink shared channel repetitions.

[0327] The configuration information may indicate two TCI states for one CORESET (Option 2 of the first embodiment).

[0328] The configuration information may indicate a CORESET pool index for one CORESET (Option 2 / Variant 1 / Variant 3 of the second embodiment).

[0329] The transmission / reception unit 220 may receive configuration information (e.g., RRC IE / MAC CE) regarding two linked search space sets, and receive downlink control information for scheduling a plurality of physical uplink shared channel repetitions, using the two linked search space sets. The control unit 210 may control the transmission of the plurality of physical uplink shared channel repetitions based on two values of parameters in the downlink control information (Option 2 of the third embodiment).

[0330] The two values are two fields of a sounding reference signal indicator, and the control unit 210 may map the two fields to the plurality of physical uplink shared channel repetitions.

[0331] For two CORESETs respectively associated with the two linked search space sets, one same CORESET pool index may be configured (Option 2 of the fourth embodiment).

[0332] For two CORESETs respectively associated with the two linked search space sets, two different CORESET pool indexes may be configured (Option 2 of the fifth embodiment).

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

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

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

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

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

[0338] Each function in the base station 10 and the user terminal 20 is realized, for example, by causing a predetermined software (program) to be loaded onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and controls communication via a communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage 1003.

[0339] The processor 1001 controls the entire computer by operating an operating system, for example. The processor 1001 may be constituted by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, at least a part of the above-described control unit 110 (210), transmission / reception unit 120 (220), and the like may be realized by the processor 1001.

[0340] In addition, the processor 1001 reads a program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes the computer to execute at least a part of the operations described in the above embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operating in the processor 1001, and the same may be true for other functional blocks.

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

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

[0343] The communication device 1004 is hardware (a transceiver device) for performing communication 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, a communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to implement at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-described transceiver unit 120 (220), the transceiver antenna 130 (230), etc. may be implemented by the communication device 1004. The transceiver unit 120 (220) may be physically or logically separated and implemented by a transmitter unit 120a (220a) and a receiver unit 120b (220b).

[0344] 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 an external input. The output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs an output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

[0345] Also, 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 for each device.

[0346] In addition, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0347] (Modification example) Regarding the terms described in the present disclosure and the terms necessary for understanding the present disclosure, they may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be read interchangeably with each other. Also, a signal may be a message. A reference signal may also be abbreviated as RS and may be called a pilot, a pilot signal, etc. depending on the applicable standard. Also, a Component Carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, etc.

[0348] 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 the radio frame may be called a subframe. Further, a subframe may be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.

[0349] Here, the new numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The new numerology may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

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

[0351] A slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, a mini-slot may be called a sub-slot. A mini-slot may be composed of a smaller number of symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called PDSCH (PUSCH) mapping type B.

[0352] A radio frame, subframe, slot, minislot, and symbol all represent time units for signal transmission. A radio frame, subframe, slot, minislot, and symbol may each be given another corresponding name. Note that the time units such as frame, subframe, slot, minislot, and symbol in this disclosure may be read interchangeably with each other.

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

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

[0355] The TTI may be a transmission time unit for a channel - encoded data packet (transport block), code block, codeword, etc., or may be a processing unit for scheduling, link adaptation, etc. Note that when the TTI is given, the time interval (for example, the number of symbols) in which the transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

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

[0357] A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI, a partial TTI, a shortened subframe, a short subframe, a mini-slot, a sub-slot, a slot, etc.

[0358] Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be read as a TTI having a TTI length less than that of a long TTI and equal to or more than 1 ms.

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

[0360] Also, the RB may include one or a plurality of symbols in the time domain, and may have a length of one slot, one mini-slot, one subframe, or one TTI. One TTI, one subframe, etc. may each be constituted by one or a plurality of resource blocks.

[0361] One or more RBs may be referred to as a Physical Resource Block (PRB), a Sub-Carrier Group (SCG), a Resource Element Group (REG), a PRB pair, an RB pair, etc.

[0362] Also, a resource block may be composed of one or more Resource Elements (REs). For example, 1 RE may be a radio resource region of 1 sub-carrier and 1 symbol.

[0363] A Bandwidth Part (BWP) (which may also be referred to as a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (common RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. The PRB is defined in a certain BWP and may be numbered within the BWP.

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

[0365] At least one of the set BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0366] Note that the structures such as the above-described radio frame, sub-frame, slot, mini-slot, and symbol are merely examples. For example, the number of sub-frames included in a radio frame, the number of slots per sub-frame or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of sub-carriers included in an RB, and the number of symbols, symbol length, cyclic prefix (CP) length, etc. within a TTI can be changed in various ways.

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

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

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

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

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

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

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

[0374] Also, the notification of predetermined information (e.g., the notification of "being X") is not limited to an explicit notification and may be performed implicitly (e.g., by not performing the notification of the predetermined information or by the notification of another piece of information).

[0375] The determination may be made based on a value represented by 1 bit (either 0 or 1), a boolean value represented by true or false, or a numerical comparison (e.g., comparison with a predetermined value).

[0376] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether called software, firmware, middleware, microcode, a hardware description language, or by some other name.

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

[0378] The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may mean the devices (e.g., base stations) included in the network.

[0379] 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", "transmission 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.

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

[0381] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each of the smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to part or all of the coverage area of at least one of a base station and a base station subsystem that provides communication services in this coverage.

[0382] In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" can be used interchangeably.

[0383] A mobile station may also be called a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.

[0384] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), a moving body that moves unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanoid or unmanned). Note that at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0385] Also, the base station in the present disclosure may be replaced by a user terminal. For example, for a configuration in which the communication between the base station and the user terminal is replaced by communication between a plurality of user terminals (which may be referred to as, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), each aspect / embodiment of the present disclosure may be applied. In this case, the functions of the base station 10 described above may be configured as functions of the user terminal 20. Also, terms such as "uplink" and "downlink" may be replaced with terms corresponding to inter-terminal communication (for example, "sidelink"). For example, an uplink channel, a downlink channel, etc. may be replaced with a sidelink channel.

[0386] Similarly, the user terminal in the present disclosure may be replaced by a base station. In this case, the functions of the user terminal 20 described above may be configured as functions of the base station 10.

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

[0388] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, for the method described in the present disclosure, the elements of various steps are presented using an exemplary order, and it is not limited to the specific order presented.

[0389] Each aspect / embodiment described in the present disclosure may be applied to systems using Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (x is, for example, an integer or 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 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable wireless communication methods, and next-generation systems extended based on these. Further, a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G) may be applied.

[0390] The description "based on" used in the present disclosure does not mean "only based on" unless otherwise specified. In other words, the description "based on" means both "only based on" and "at least based on".

[0391] Any reference to an element using terms such as "first", "second", etc. used in this disclosure does not generally limit the quantity or order of those elements. These terms can be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not mean that only two elements can be employed or that the first element must precede the second element in any way.

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

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

[0394] Also, "determining" may be considered to be "resolving", "selecting", "choosing", "establishing", "comparing", etc. That is, "determining" may be considered to be making some kind of operation.

[0395] Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

[0396] The "maximum transmit power" described in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0397] As used in this disclosure, the terms "connected" and "coupled", or any variations thereof, mean 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 "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 "accessed".

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

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

[0400] In the present disclosure, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0401] In the present disclosure, for example, when articles are added by translation, such as a, an and the in English, the present disclosure may include that the nouns following these articles are in the plural form.

[0402] As described above, the invention according to the present disclosure has been described in detail. However, it is obvious 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 changed forms without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for illustrative purposes and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiving unit that receives downlink control information (DCI) for scheduling physical uplink shared channel (PUSCH) repetitions, and a control unit that controls transmission of the PUSCH repetitions based on values of two fields of a sounding reference signal (SRS) indicator (SRI) included in the DCI. When supporting physical downlink control channel (PDCCH) repetitions based on two linked search space sets, the receiving unit is a terminal that receives the DCI using the two linked search space sets.

2. The terminal according to claim 1, which does not support that the PUSCH repetitions are indicated when two different CORESET pool indexes are set.

3. When two different CORESET pool indexes are set, two SRS resource sets having specific uses are set, wherein the two SRS resources correspond to each of the two CORESET pool indexes, the terminal according to claim 1 or claim 2.

4. A step of receiving downlink control information (DCI) for scheduling physical uplink shared channel (PUSCH) repetitions, and a step of controlling transmission of the PUSCH repetitions based on values of two fields of a sounding reference signal (SRS) indicator (SRI) included in the DCI. When supporting physical downlink control channel (PDCCH) repetitions based on two linked search space sets, a terminal receives the DCI using the two linked search space sets, a wireless communication method of the terminal.

5. A transmitting unit that transmits downlink control information (DCI) for scheduling physical uplink shared channel (PUSCH) repetitions, and a control unit that controls reception of the PUSCH repetitions transmitted from a terminal based on values of two fields of a sounding reference signal (SRS) indicator (SRI) included in the DCI. When supporting physical downlink control channel (PDCCH) repetitions based on two linked search space sets, the transmitting unit is a base station that transmits the DCI using the two linked search space sets.

6. A system including a terminal and a base station, The terminal is configured to: receive downlink control information (DCI) that schedules physical uplink shared channel (PUSCH) repetitions; and include a control unit configured to control transmission of the PUSCH repetitions based on values of two fields of a sounding reference signal (SRS) indicator (SRI) included in the DCI. When supporting physical downlink control channel (PDCCH) repetitions based on two linked search space sets, the receiving unit receives the DCI using the two linked search space sets. The base station is configured to: have a transmitting unit that transmits the DCI.

Images