Terminal, wireless communication method, base station, and system

Abstract

To provide a terminal, a wireless communication method, a base station, and a system that appropriately control uplink (UL) transmissions even when multi transmission / reception points (TRP) are used.SOLUTION: In a next-generation mobile communication system, a user terminal 20 comprises: a reception unit that receives multiple DCIs for scheduling uplink shared channels (PUSCH) when control resource set (CORESET) pool indices are set to a plurality of CORESETs, respectively; and a control unit that determines the number of bits of the respective sounding reference signal resource identifier (SRI) fields of the multiple DCIs on the basis of the number of SRS resources included in an SRS resource set associated with the CORESET pool index of a CORESET having detected each of the multiple DCIs, and determines space related information for the PUSCH on the basis of the SRI field and the CORESET pool index.SELECTED DRAWING: Figure 13

Description

Technical Field

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

Background Art

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

[0003] A successor system 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.) is also under consideration.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In NR, communication using one or more transmission / reception points (TRPs) (multi-TRP) is being considered.

[0006] However, when attempting to perform transmission for multi-TRP using the existing Rel.15 / 16 specifications, problems arise such as limitations in performance and scheduling flexibility. Therefore, in accordance with the existing Rel.15 / 16 specifications, UL transmission across M-TRP may not be properly performed, potentially resulting in a throughput decrease or communication quality degradation.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, a base station, and a system that can appropriately control UL transmission even when multi-TRP is used.

Means for Solving the Problems

[0008] A terminal according to an aspect of the present disclosure includes a receiving unit that receives a plurality of DCIs for scheduling a Physical Uplink Shared Channel (PUSCH) when a control resource set (CORESET) pool index is set for each of a plurality of CORESETs, and a control unit that determines the number of bits of the sounding reference signal resource identifier (SRI) field of each of the plurality of DCIs based on the number of SRS resources included in an SRS resource set associated with the CORESET pool index of the CORESET in which each of the plurality of DCIs is detected, and determines spatial relation information for the PUSCH based on the SRI field and the CORESET pool index.

Advantages of the Invention

[0009] According to one aspect of the present disclosure, UL transmission can be appropriately controlled even when multi-TRP is used.

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

Embodiments for Carrying Out the Invention

[0011] (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, the UE repeatedly transmits UL data (e.g., an uplink shared channel (PUSCH)) a predetermined number of times.

[0012] FIG. 1A is a diagram showing an example of the repeated transmission of PUSCH. FIG. 1A shows an example in which a predetermined number of repeated PUSCHs are scheduled by a single DCI. The number of repetitions is also referred to as a repetition factor K or an aggregation factor K.

[0013] In FIG. 1A, the repetition factor K = 4, but the value of K is not limited to this. Also, the nth repetition may also be referred to as the nth transmission occasion, etc., and may be identified by a repetition index k (0 ≦ k ≦ K - 1). Further, FIG. 1A 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.

[0014] For example, in FIG. 1A, the UE quasi-statically receives information indicating the repetition factor K (e.g., aggregationFactorUL or aggregationFactorDL) 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.

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

[0016] The UE controls the reception processing (e.g., at least one of reception, demapping, demodulation, decoding) of the PDSCH or the transmission processing (e.g., at least one of transmission, mapping, modulation, encoding) of the PUSCH in K consecutive slots based on at least one of the following field values (or the information indicated by the field value) in the DCI: ·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 (RB), a predetermined number of resource block groups (RBG)), ·Modulation and coding scheme (MCS) index, ·Configuration of the Demodulation Reference Signal (DMRS) for PUSCH ·Spatial relation information of PUSCH, or the state of the Transmission Configuration Indication (TCI) (TCI-state).

[0017] The same symbol assignment may be applied among consecutive K slots. FIG. 1A shows a case where the PUSCH in each slot is assigned to a predetermined number of symbols starting from the beginning of the slot. The same symbol assignment among slots may be determined as described in the above time domain resource assignment.

[0018] For example, the UE may determine the symbol assignment 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) in the DCI.

[0019] On the other hand, among the consecutive K slots, the Redundancy Version (RV) applied to the transport block (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.

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

[0021] In Rel.15, as shown in Figure 1A, PUSCH is repeatedly transmitted over multiple 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 a unit of a predetermined number of symbols) (see Figure 1B).

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

[0023] 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., the TDRA field) in the DCI of 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., the TDRA field) of the DCI.

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

[0025] The slot-based repeated transmission shown in FIG. 1A may be referred to as repeated transmission type A (e.g., PUSCH repetition Type A), and the sub-slot-based repeated transmission shown in FIG. 1B may be referred to as repeated transmission type B (e.g., PUSCH repetition Type B).

[0026] The application of at least one of repeated transmission type A and repeated transmission type B may be set for the UE. For example, the repeated transmission type applied by the UE may be notified from the base station to the UE by means of upper layer signaling (e.g., PUSCHRepTypeIndicator).

[0027] Either repeated transmission type A or repeated transmission type B may be set for the UE for each DCI format that schedules the PUSCH.

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

[0029] (Invalid symbol pattern) When applying repetition transmission type B for PUSCH transmission, it is also being considered to notify the UE of information regarding symbols (or symbol patterns) that are not available for PUSCH transmission. The symbol pattern that is not available for PUSCH transmission may be called an invalid symbol pattern, an Invalid symbol pattern, an invalid symbol pattern, etc.

[0030] It is being considered to notify the invalid symbol pattern by using at least one of higher layer signaling and DCI. The DCI may be a predetermined DCI format (for example, at least one of DCI format 0_1 and 0_2).

[0031] For example, use the first higher layer parameter to notify the UE of information regarding the invalid symbol pattern that is not available for PUSCH transmission. Also, the UE may be notified using DCI about whether the information regarding the invalid symbol pattern is applicable. In this case, a bit field (field for notifying the applicability of the invalid symbol pattern) for instructing whether the information regarding the invalid symbol pattern is applicable may be set in the DCI.

[0032] Also, use the second higher layer parameter to notify the UE of whether the notification field (or additional bit) in the DCI is set. That is, when the UE is notified of information regarding the invalid symbol pattern by the first higher layer parameter, the UE may determine whether the information regarding the invalid symbol pattern is applicable based on the second higher layer parameter and the DCI.

[0033] If the first upper layer parameter is not notified or set, the UE may control the transmission of the PUSCH without considering the invalid symbol pattern. If the first upper layer parameter is notified or set, the UE may determine whether to apply the invalid symbol pattern based on the second upper layer parameter and the DCI. For example, if the second upper layer parameter instructs to add an additional bit (or a predetermined field) in the DCI to indicate whether to apply the invalid symbol pattern, the UE may determine whether to apply the invalid symbol pattern based on the said predetermined field.

[0034] The first upper layer parameter may be information that notifies a symbol pattern that is invalid for the transmission of the PUSCH. For example, a bitmap format may be applied (see Figure 2A). Figure 2A shows an example when the invalid symbol pattern is defined by a bitmap (1-D bitmap) in the time domain. The UE may determine the resources available for PUSCH transmission in one or more frequency bandwidths (e.g., Bandwidth Part (BWP)) based on the information regarding the invalid symbol pattern (see Figure 2B).

[0035] Here, a case where one or a common invalid symbol pattern is applied to multiple BWPs is shown, but different invalid symbol patterns may be set or applied for each BWP.

[0036] (Nominal repetitions / Actual repetitions) When type B of the repeated transmission is applied and the repeated transmission is performed in units of sub-slots, depending on the repetition factor (K), the data allocation unit, etc., there may be a case where a certain repeated transmission crosses the slot-boundary.

[0037] Figure 3A shows an example of applying the repetitive transmission type B when the repetition factor (K) is 4 and the PUSCH length (L) is 4. In Figure 3A, the PUSCH with k = 3 is arranged across the slot boundary. In such a case, the PUSCH may be divided (or segmented) based on the slot boundary and transmitted (see Figure 3B).

[0038] Also, a case is assumed where a symbol that cannot be used for PUSCH transmission (for example, a DL symbol or an invalid symbol, etc.) is included in the slot. In Figure 3A, a case is shown where a symbol that cannot be used for the PUSCH transmission (here, a DL symbol) is included in some of the symbols where the PUSCH with k = 1 is arranged. In such a case, PUSCH transmission may be performed using the symbols excluding the DL symbol (see Figure 3B).

[0039] In the allocated symbols of a certain PUSCH, if DL symbols (or invalid symbols) are included in the symbols other than both ends, PUSCH transmission may be performed using the symbols other than the DL symbol part. In this case, the PUSCH may be divided (or segmented).

[0040] In Figure 3B, a case is shown where the PUSCH with k = 1 (Rep#2) in the sub - slot - based repetitive transmission is divided into two (Rep#2 - 1 and #2 - 2) by DL symbols, and the PUSCH with k = 3 (Rep#4) is divided into two (Rep#4 - 1 and #4 - 2) by the slot boundary.

[0041] Note that the DL symbol, the invalid symbol, or the repetitive transmission before considering the slot boundary (Figure 3A) may be called nominal repetitions. The repetitive transmission considering the DL symbol, the invalid symbol, or the slot boundary (Figure 3B) may be called actual repetitions.

[0042] (Spatial relationship for SRS, PUSCH) In Rel.15 NR, the UE may receive information used for transmitting a measurement reference signal (e.g., a Sounding Reference Signal (SRS)), such as SRS configuration information (e.g., parameters within the "SRS-Config" of the RRC control element).

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

[0044] One SRS resource set may be related to a predetermined number of SRS resources (the 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).

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

[0046] Here, the SRS resource type may indicate any one 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.

[0047] 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 or non-codebook usage may be used for determining the precoder for codebook-based or non-codebook-based PUSCH transmission based on the SRI.

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

[0049] The SRS resource information may include the 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.), the hopping-related information, the SRS resource type, the sequence ID, the spatial relationship information of the SRS, etc.

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

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

[0052] Note that in the present disclosure, the SSB index, the SSB resource ID, and the SSB Resource Indicator (SSBRI) may be read interchangeably with each other. Also, the CSI-RS index, the CSI-RS resource ID, and the CSI-RS Resource Indicator (CRI) may be read interchangeably with each other. Also, the SRS index, the SRS resource ID, and the SRI may be read interchangeably with each other.

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

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

[0055] When the UE is configured with spatial relationship information regarding another SRS (reference SRS) and the 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 that for the transmission of 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.

[0056] The UE may determine the spatial relationship of the PUSCH scheduled by the DCI based on the value of a predetermined field (for example, SRS resource identifier (SRI) field) in the DCI (for example, DCI format 0_1). Specifically, the UE may use the spatial relationship 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.

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

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

[0059] However, when attempting to perform transmission for M-TRP using the existing Rel.15 / 16 specifications, there is a problem that performance, scheduling flexibility, etc. are restricted. Transmission for M-TRP corresponds to, for example, multiple PUSCH transmissions using different SRIs.

[0060] Figs. 5A and 5B are diagrams showing an example of a problem when attempting to perform transmission for M-TRP using the existing Rel.15 / 16 specifications. In this example, it is assumed that the value of the SRI field in the DCI = 0 corresponds to SRI#0 and the value of the SRI field = 0 corresponds to SRI#1.

[0061] Fig. 5A corresponds to a case where transmission for M-TRP is attempted using the existing Rel.15 specifications. In this example, PUSCH#1 corresponding to SRI#0 is scheduled using a certain DCI (DCI1), and PUSCH#2 corresponding to SRI#1 is scheduled using another DCI (DCI2).

[0062] Here, DCI1 and DCI2 have the same HARQ process ID (or HARQ process number) and indicate the same value of the new data indicator (NDI) field. That is, PUSCH#2 means retransmission of the same data (transport block) as PUSCH#1. According to this example, PUSCH of the same data can be transmitted (retransmitted, repeatedly transmitted) using different beams (SRIs) at short intervals.

[0063] On the other hand, in Rel. 15, since DCI2 for scheduling another PUSCH#2 cannot be issued (notified) unless after PUSCH#1 is transmitted, it is not preferable when PUSCH#1 and #2 are to be transmitted with a small time difference.

[0064] Figure 5B corresponds to a case where transmission for M-TRP is attempted using the existing Rel. 16 specification. In this example, PUSCH#1 corresponding to SRI#0 is scheduled using DCI (DCI1) detected in the CORESET with control resource set (CORESET) pool index = 0, and PUSCH#2 corresponding to SRI#1 is scheduled using DCI (DCI2) detected in the CORESET with CORESET pool index = 1.

[0065] In Rel. 16, when PUSCHs related to different values of the CORESET pool index are scheduled, and when the first PUSCH is scheduled by a CORESET (the first PDCCH) with a value of one of the CORESET pool indexes, the UE may schedule a second PUSCH that starts before the end of the first PUSCH by a CORESET (the second PDCCH) with a value of the other CORESET pool index that ends after the first PDCCH. Figure 5B corresponds to this case.

[0066] That is, in Rel. 16, even before the transmission of PUSCH#1 scheduled by DCI#1 is completed, DCI#2 for scheduling another PUSCH#2 can be issued (notified) when the CORESET pool indexes of these DCIs are different.

[0067] However, according to the existing Rel. 15 / 16 specifications, since the correspondence between the SRI field and the SRI is set in common regardless of the CORESET pool index in which the DCI is detected (corresponding to the SRI within the same SRS resource set), flexible transmission for M-TRP cannot be achieved.

[0068] Therefore, according to the existing Rel.15 / 16 specifications, UL transmission over M-TRP may not be properly performed, which may lead to a throughput reduction or communication quality degradation.

[0069] Thus, the inventors have conceived a method for controlling UL transmission over M-TRP. According to one aspect of the present disclosure, for example, a UE can perform UL transmission for multi-TRP using different beams.

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

[0071] In the present disclosure, "A / B" and "at least one of A and B" may be read interchangeably with each other.

[0072] In the present disclosure, activate, deactivate, indicate (or specify), select, configure, update, determine, etc. may be read interchangeably with each other.

[0073] In the present disclosure, RRC, RRC parameter, RRC message, RRC signaling, upper layer parameter, information element (IE), configuration may be read interchangeably with each other. In the present disclosure, MAC CE, update command, activation / deactivation command 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.

[0074] In the present disclosure, panel, beam, panel group, beam group, precoder, Uplink (UL) transmission entity, TRP, spatial relation information (SRI), spatial relation, SRS resource identifier (SRS Resource Indicator (SRI)), SRS resource, Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), codeword, base station, a predetermined antenna port (for example, a Demodulation Reference Signal (DMRS) port), a predetermined antenna port group (for example, a DMRS port group), a predetermined group (for example, a Code Division Multiplexing (CDM) group, a predetermined reference signal group, a CORESET group), a predetermined resource (for example, a predetermined reference signal resource), a predetermined resource set (for example, a predetermined reference signal resource set), a CORESET pool, a PUCCH group (PUCCH resource group), a spatial relation group, a downlink TCI state (DL TCI state), an uplink TCI state (UL TCI state), a unified TCI state, a common TCI state, QCL, QCL assumption, etc. may be read interchangeably with each other.

[0075] Also, the TCI state Identifier (ID) and the TCI state may be read interchangeably with each other. The TCI state and TCI may be read interchangeably with each other.

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

[0077] In the present disclosure, the TRP index, CORESET pool index (CORESETPoolIndex), pool index, group index, etc. may be read as each other.

[0078] In the present disclosure, a single PDCCH (DCI) may be referred to as a PDCCH (DCI) of a first scheduling type (for example, scheduling type A (or type 1)). Also, a multi-PDCCH (DCI) may be referred to as a PDCCH (DCI) of a second scheduling type (for example, scheduling type B (or type 2)).

[0079] In the present disclosure, for a single DCI, the i-th TRP (TRP#i) may mean the i-th TCI state, the i-th CDM group, etc. (i is an integer). For a multi-DCI, the i-th TRP (TRP#i) may mean the CORESET corresponding to the CORESET pool index = i, the i-th TCI state, the i-th CDM group, etc. (i is an integer).

[0080] In the present disclosure, a single PDCCH may be assumed to be supported when multi-TRP uses an ideal backhaul. A multi-PDCCH may be assumed to be supported when non-ideal backhaul is used between multi-TRPs.

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

[0082] In the present disclosure, multi-TRP (MTRP, M-TRP), multi-TRP system, multi-TRP transmission, multi-PDSCH may be read interchangeably with each other.

[0083] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, scheduling multiple (corresponding to different SRIs) PUSCHs by one DCI, sDCI-based MTRP transmission, activating two TCI states on at least one TCI code point may be read interchangeably with each other.

[0084] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, mDCI-based MTRP transmission, using multi-DCI for MTRP, scheduling multiple (corresponding to different SRIs) PUSCHs by two DCIs, setting two CORESET pool indexes or CORESET pool index = 1 (or a value of 1 or more) may be read interchangeably with each other.

[0085] The repetition in the present disclosure may be read interchangeably with MTRP-based repetition, Rel.17 repetition, repetition applying different spatial relationships, repeated PUSCH, repeated PUCCH, repeated transmission, etc. Also, the repeated transmission in the following embodiments may correspond to at least one of repeated transmission type A, repeated transmission type B, and other repeated transmission types.

[0086] Note that the PUSCH in the following embodiments assumes repetitive PUSCH, but it may not be repetitive PUSCH (it may be PUSCH with one transmission). Therefore, in this disclosure, repetitive PUSCH, PUSCH repetition, and PUSCH may be read interchangeably with each other. Note that in repetitive PUSCH, the same codeword / transport block may be transmitted in each PUSCH (each repetition). Repetitive PUSCH may be read interchangeably with a plurality of PUSCH having the same content (e.g., data / codeword / transport block).

[0087] Also, the SRS resource set in the following embodiments may be read interchangeably with an SRS resource set for codebook or non-codebook use, or may be read interchangeably with an SRS resource set for other uses.

[0088] Note that in this disclosure, hereinafter, "set to CORESET pool index = 0" may be read interchangeably with "set to CORESET pool index = 0 or the CORESET pool index is not set".

[0089] (Wireless communication method) <First Embodiment> In the first embodiment, each of a plurality of DCIs (mDCI) that schedules PUSCH repetition has an SRI field larger than 0 bits.

[0090] For example, consider a case where the UE sets mDCI-based MTRP, and PUSCH#1 among PUSCH repetitions (PUSCH#1 and #2) is scheduled by DCI1 related to a value of a certain CORESET pool index (e.g., CORESET pool index = 0), and PUSCH#2 is scheduled by DCI2 related to another value of the CORESET pool index (e.g., CORESET pool index = 1).

[0091] Note that the UE being configured with mDCI-based MTRP may also mean that at least one CORESET with a CORESET pool index (RRC parameter "CORESETPoolIndex") having a value of 1 or more is configured for the UE.

[0092] In the above case, for both DCI1 and DCI2, the UE may assume that the size of the SRI field is necessarily larger than 0 bits. Also, the UE may assume that the number of SRS resources included in one or more SRS resource sets (for example, one or more SRS resource sets with usage = CB / NCB) is necessarily more than 1. According to these configurations, different beams (SRI) can be specified for PUSCH#1 and PUSCH#2.

[0093] Note that the SRI field size of DCI1 and the SRI field size of DCI2 may be the same (Embodiment 1.1). In this case, the SRI field size may be determined by the number of SRS resources included in the above one or more SRS resource sets.

[0094] Also, the SRI field size of DCI1 and the SRI field size of DCI2 may be different (Embodiment 1.2). In this case, the SRI field size may be determined by the number of SRS resources included in the above one or more SRS resource sets for each related CORESET pool index. For example, the SRI field size of DCI1 may be determined by the number of SRS resources included in one or more SRS resource sets related to CORESET pool index = 0.

[0095] Here, the correspondence between the SRS resource / SRS resource set and the related CORESET pool index may be determined in advance by the specification, may be notified to the UE by at least one of the RRC parameter, MAC CE, and DCI, or may be determined based on the UE capability. The correspondence may be set, for example, as shown in the third embodiment described later.

[0096] In Embodiment 1.2, even if it is the same DCI format, the DCI payload size (number of bits) may be different for each CORESET pool index. Therefore, the UE may assume that a plurality of PDCCH candidates (or CORESET or monitoring opportunities) related to different CORESET pool indexes do not overlap in terms of time / frequency resources. According to this assumption, it is possible to suppress the excessive number of blind decoding (blind detection) times of the PDCCH at a certain timing and the increase in UE load.

[0097] According to the first embodiment described above, the decoding of the SRI for M-TRP can be appropriately performed.

[0098] <Second Embodiment> In the second embodiment, at least one of a plurality of DCIs (mDCI) that schedule PUSCH repetition may be allowed to have a 0-bit SRI field.

[0099] The second embodiment is roughly classified into Embodiment 2.1 in which one SRI field is included in the DCI and Embodiment 2.2 in which a plurality of SRI fields are included in the DCI.

[0100] Note that the content of the second embodiment may be applied to the first embodiment except that a 0-bit SRI field is not allowed.

[0101] [Embodiment 2.1] In Embodiment 2.1, the UE may determine the SRI to be applied to the PUSCH based on at least one of the SRI field of the DCI that schedules the PUSCH and the CORESET pool index of the CORESET for the DCI (for example, the CORESET that detects the DCI).

[0102] In other words, the actual SRI specified by the value of the SRI field may be selected based on the CORESET pool index related to the DCI.

[0103] FIG. 6 is a diagram showing an example of the control of the SRI of the PUSCH according to Embodiment 2.1. In this example, PUSCH#1 is scheduled using the DCI (DCI1) detected in the CORESET with the CORESET pool index = 0, and PUSCH#2 is scheduled using the DCI (DCI2) detected in the CORESET with the CORESET pool index = 1.

[0104] The correspondence between the value of the SRI field and the actual SRI is different for each CORESET pool index, as shown in the lower part of FIG. 6. In the present disclosure, SRI#i_j (where i and j are numbers) may mean the j-th SRI corresponding to the CORESET pool index = i. SRI#i_j may be set / activated by upper layer signaling explicitly or implicitly associated with the CORESET pool index.

[0105] In this example, since the SRI field value of DCI1 = 0, the UE determines that the SRI applied to PUSCH#1 is SRI#0_0. Also, since the SRI field value of DCI2 = 0, the UE determines that the SRI applied to PUSCH#2 is SRI#1_0.

[0106] Note that the SRI field size may be determined by the number of SRS resources included in one or more SRS resource sets for each related CORESET pool index. For example, the SRI field size of DCI1 may be determined by the number of SRS resources included in one or more SRS resource sets related to the CORESET pool index = 0.

[0107] Here, the correspondence between the SRS resource / SRS resource set and the associated CORESET pool index may be determined in advance by the specification, may be notified to the UE by at least one of the RRC parameter, MAC CE, and DCI, or may be determined based on the UE capability. The correspondence may be set as shown in, for example, the third embodiment described below.

[0108] Note that the SRI field size of DCI1 and the SRI field size of DCI2 may be the same. In this case, it may be assumed that the number of SRS resources included in one or more SRS resource sets of each CORESET pool index is the same. According to this assumption, since the payload size of the DCI for PUSCH can be made the same regardless of the CORESET pool index, it is possible to suppress the excessive number of blind decoding (blind detection) times of the PDCCH at a certain timing and the increase in UE load.

[0109] In Embodiment 2.1, the number of SRS resources corresponding to a certain CORESET pool may be 1. In this case, the SRI field size of the DCI detected by the CORESET pool index may be 0 bits. The UE may determine the actual SRI based only on the CORESET pool index without relying on the SRI field.

[0110] FIG. 7 is a diagram showing another example of the control of the SRI of the PUSCH according to Embodiment 2.1. FIG. 7 shows an example in which the SRI corresponding to one SRI code point (field value) is collectively set by a plurality of (two in this example) upper layer signalings (for example, RRC signaling) across a plurality of CORESET pool indexes. PUSCH#k (the k-th PUSCH) (k is an integer) may mean the SRI corresponding to the k-th TRP or the SRI corresponding to the k-th repetition. PUSCH#i may be read as the i-th SRI. Note that the present disclosure is also applicable when the PUSCH after the third is defined.

[0111] For the PUSCH scheduled in the CORESET with CORESET pool index = 0, the UE may determine the SRI by referring to the first SRI. For the PUSCH scheduled in the CORESET with CORESET pool index = 1, the UE may determine the SRI by referring to the second SRI. According to such a configuration, even if the field size of the DCI is not increased, the SRI can be flexibly indicated for the M-TRP (when different CORESET pool indexes are used).

[0112] In FIG. 7, SRI#0_0 and SRI#1_0 are set in relation to the value of the SRI field = 0. For example, SRI#0_0 corresponding to PUSCH#1 is applied to the PUSCH scheduled by the DCI with the value of the SRI field = 0 detected in the CORESET with CORESET pool index = 0. In FIG. 7, since DCI1 has the value of the SRI field = 0 and DCI2 has the value of the SRI field = 0, SRI#0_0 is applied to PUSCH#1 and SRI#1_0 is applied to PUSCH#2.

[0113] In FIG. 7, the CORESET pool index may not be explicitly associated with SRI#i_j. For example, the i-th SRI corresponding to the value of a certain SRI field may be determined to be associated with the CORESET pool index = i.

[0114] Note that the correspondence between the SRS field as shown in FIG. 7 and the actual SRI applied to PUSCH#1 and #2 is not limited to the case of mDCI-based MTRP, and may also be used in the case of sDCI-based MTRP.

[0115] [Embodiment 2.2] In Embodiment 2.2, the UE may select one of a plurality of SRI fields of DCI (also referred to as scheduling DCI) that schedules the PUSCH, and determine the SRI to be applied to the PUSCH based on the value of the selected SRI field. The selection of this SRI field may be performed, for example, based on the CORESET pool index of the CORESET (e.g., for detecting the DCI) for the DCI, or based on the repetition index of the scheduled PUSCH (in other words, which repetition).

[0116] For example, the SRI to be applied to the PUSCH may be determined based on the first SRI field (SRI field #1) when the scheduling DCI is related to the CORESET pool index = 0, or may be determined based on the second SRI field (SRI field #2) otherwise. More generally, the SRI to be applied to the PUSCH may be determined based on the (i + 1)-th SRI field when the related CORESET pool index is i (i is an integer).

[0117] For example, the SRI to be applied to the PUSCH may be determined based on the first SRI field (SRI field #1) when the scheduled PUSCH is the first transmission of the PUSCH repetition, or may be determined based on the second SRI field (SRI field #2) otherwise. More generally, the SRI to be applied to the PUSCH may be determined based on the i-th SRI field when the PUSCH is the i-th repetition (i is an integer).

[0118] FIG. 8 is a diagram showing an example of control of the SRI of the PUSCH according to Embodiment 2.2. In this example, PUSCH#1 is scheduled using DCI (DCI1) detected in the CORESET with the CORESET pool index = 0, and PUSCH#2 is scheduled using DCI (DCI2) detected in the CORESET with the CORESET pool index = 1.

[0119] Both DCI1 and DCI2 include a plurality of SRI fields (SRI field #1, #2). As shown in the lower part of FIG. 8, the correspondence between the value of each SRI field and the actual SRI is different for each CORESET pool index (or PUSCH repetition).

[0120] Here, an example is shown in which the UE determines the SRI of the scheduled PUSCH based on which repetition of the scheduled PUSCH it is, regardless of the CORESET pool index. Assuming that PUSCH#1 shown in the figure is the first repetition and PUSCH#2 is the second repetition, the UE determines the SRI applied to PUSCH#1 based on the value of SRI field #1 of DCI1, and determines the SRI applied to PUSCH#2 based on the value of SRI field #2 of DCI#2.

[0121] Note that the unused one of the plurality of SRI fields may be used as other information.

[0122] Note that the sizes of the plurality of SRI fields in a certain DCI may be different. For example, the size of SRI field #1 of DCI1 and the size of SRI field #2 of the DCI1 may be different. The size of each SRI field may be determined by the number of SRS resources included in one or more SRS resource sets for each related CORESET pool index. For example, the size of SRI field #1 of DCI1 may be determined by the number of SRS resources included in one or more SRS resource sets related to CORESET pool index = 0.

[0123] Here, the correspondence between the SRS resource / SRS resource set and the related CORESET pool index may be determined in advance by the specification, may be notified to the UE by at least one of RRC parameters, MAC CE, and DCI, or may be determined based on the UE capability. The correspondence may be set, for example, as shown in the third embodiment described later.

[0124] For a certain DCI format that schedules PUSCH, the sum of the sizes of a plurality of SRI fields may be the same regardless of the CORESET pool index, the scheduled PUSCH, etc.

[0125] In Embodiment 2.2, the number of SRS resources corresponding to a certain CORESET pool index / repetition may be 1. In this case, the size of the SRI field of the DCI for the CORESET pool index / repetition may be 0 bits.

[0126] Note that the determination of SRI in Embodiment 2.2 is not limited to the case of mDCI-based MTRP, and may also be used in the case of sDCI-based MTRP.

[0127] According to the second embodiment described above, the decoding of SRI for M-TRP can be appropriately performed. Also, for example, by setting the actual SRI indicated by the SRI field of the DCI for each CORESET pool index, it is possible to apply different SRIs to a plurality of PUSCHs while suppressing the overhead (increase in the number of bits) of the SRI field.

[0128] <Third Embodiment> In Rel.15 NR, the maximum number of SRS resource sets with usage = codebook (CB) is 1, the maximum number of SRS resources included in the SRS resource set with usage = codebook is 2, the maximum number of SRS resource sets with usage = non-codebook (NCB) is 1, and the maximum number of SRS resources included in the SRS resource set with usage = non-codebook is 4.

[0129] Therefore, in setting SRI for each of the above-mentioned TRPs (for example, for each CORESET pool index or for each repetition index of PUSCH), it is necessary to eliminate (or relax) the constraints on this SRS resource number or SRS resource set number.

[0130] The following embodiments will be described respectively. · Embodiment 3.1: The maximum number of SRS resource sets is P, and the maximum number of SRS resources per SRS resource set is defined as 2. · Embodiment 3.2: The maximum number of SRS resource sets is 1, and the maximum number of SRS resources per SRS resource set is defined as 2P.

[0131] Here, the value of P may correspond to the number of TRPs, or may correspond to the number of different CORESET pool indexes set for the UE (or the maximum CORESET pool index + 1 set for the UE). For example, when a CORESET with CORESET pool index = 1 is set, P may be 2. The value of P is of course not limited to 2.

[0132] In addition, in Embodiments 3.1 - 3.2, unless otherwise noted, on the premise that P = 2, the SRS resource sets and SRS resources for use = CB will be described, but they may be read as those for use = NCB and other uses of SRS resource sets and SRS resources. For example, when reading as the SRS resource sets and SRS resources for use = NCB, the number of SRS resource sets may be the same value, but the number of SRS resources per SRS resource set may be read as twice the number of SRS resources for use = CB (for example, 4 in Embodiment 3.1 and 4P in Embodiment 3.2).

[0133] Also, hereinafter, in the present disclosure, the CORESET pool index, the PUSCH repetition index, and the upper layer index may be read as each other.

[0134] [Embodiment 3.1] In Embodiment 3.1, the UE is configured with multiple SRS resource sets for the same application. One SRS resource set corresponds to one TRP (CORESET pool index). The correspondence between the CORESET pool index and the SRS resource set ID may be explicitly configured by upper layer signaling, or may be associated with CORESET pool index = 0, 1,... in ascending order of the SRS resource set ID (or SRS resource ID). Note that the "in ascending order" in the present disclosure may be read as "in descending order" interchangeably.

[0135] Figures 9A and 9B are diagrams showing an example of the configuration of the SRS resource set and SRS resources according to Embodiment 3.1. Figure 9A shows the SRS resources associated with SRS resource set ID = 0, and Figure 9B shows the SRS resources associated with SRS resource set ID = 1.

[0136] Here, SRS#x_y may mean the SRS resource of the y (or y + 1) - th entry of the SRS resource set with ID = x (the same applies to the following drawings). Also, the illustrated SRS resource set ID and SRS resource ID are merely examples and are not limited to these values (the same applies to the following drawings).

[0137] SRS resource set ID = 0 may be used to specify the SRI of the CORESET with CORESET pool index = 0 set. SRS resource set ID = 1 may be used to specify the SRI of the CORESET with CORESET pool index = 1 set.

[0138] In this example, SRI#0_0 and SRI#0_1 described above with reference to Figure 6 etc. may be SRS#0_0 (the SRS resource corresponding to SRS resource ID = 0) and SRS#0_1 (the SRS resource corresponding to SRS resource ID = 1), respectively.

[0139] Also, SRI#1_0 and SRI#1_1 described above with reference to FIG. 6 may be SRS#1_0 (SRS resource corresponding to SRS resource ID = 2) and SRS#1_1 (SRS resource corresponding to SRS resource ID = 2), respectively.

[0140] [Embodiment 3.2] In Embodiment 3.2, W (W is an integer) SRS resources included in one SRS resource set correspond to one TRP (CORESET pool index). The correspondence between the CORESET pool index and the SRS resource ID may be explicitly set by upper layer signaling, or may be associated in order of CORESET pool index = 0, 1,... for every W starting from the smaller SRS resource ID.

[0141] For each corresponding CORESET pool index, the value of W may be different. For example, among the four SRS resources in the SRS resource set, one SRS resource may be associated with CORESET pool index = 0, and the remaining three SRS resources may be associated with CORESET pool index = 1.

[0142] Note that the value of W may be the number of SRS resources that determines the SRI field size of DCI, or for example, a value obtained by applying a floor function or a ceiling function to the value obtained by dividing the number of SRS resources in the SRS resource set for use = CB / NCB by P.

[0143] FIG. 10 is a diagram showing an example of the configuration of an SRS resource set and SRS resources according to Embodiment 3.2. This example shows the SRS resources associated with SRS resource set ID = 0. The SRS resource set with SRS resource set ID = 0 in this example is associated with 2P = 4 SRS resources, and for example, W = 2.

[0144] Of the SRS resource set with ID = 0, the two smaller SRS resources may be used for specifying the SRI of the CORESET where the CORESET pool index = 0 is set. Of the SRS resource set with ID = 0, the next two smaller SRS resources may be used for specifying the SRI of the CORESET where the CORESET pool index = 1 is set.

[0145] In this example, SRI#0_0 and SRI#0_1 described above in FIG. 6 etc. may be SRS#0_0 (SRS resource corresponding to SRS resource ID = 0) and SRS#0_1 (SRS resource corresponding to SRS resource ID = 1), respectively.

[0146] Also, SRI#1_0 and SRI#1_1 described above in FIG. 6 etc. may be SRS#0_2 (SRS resource corresponding to SRS resource ID = 2) and SRS#0_3 (SRS resource corresponding to SRS resource ID = 3), respectively.

[0147] According to the third embodiment described above, the UE can appropriately determine the spatial relationship for the M-TRP.

[0148] <Others> At least one of the above-described embodiments may be applied only to a UE that supports a specific UE capability or a UE that has reported (supporting) the specific UE capability.

[0149] The specific UE capability may indicate at least one of the following: · Whether it supports PUSCH repetition using different spatial relationships (or SRI), · Whether it supports the association between the CORESET pool index and the SRI, · The maximum number of repetitions / SRI numbers it supports. · The maximum number of SRS resource sets / SRS resources it supports.

[0150] In addition, at least one of the above-described embodiments may be applied when the UE sets specific information related to the above-described embodiments by upper layer signaling (when not set, for example, the operation of Rel.15 / 16 is applied). For example, the specific information may be information indicating activation of different spatial relationships for PUSCH repetition, any RRC parameter for a specific release (e.g., Rel.17), etc.

[0151] Note that each of the above-described embodiments may be applied when multi-TRP or multi-panel (operation) is set for the UE, or may be applied when not.

[0152] Note that the CORESET pool index of each embodiment of the present disclosure may be read as the TCI state ID or the CORESET ID.

[0153] (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-described embodiments of the present disclosure.

[0154] FIG. 11 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) standardized by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), etc.

[0155] In addition, the wireless communication system 1 may support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple 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.

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

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

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

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

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

[0161] Also, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0162] The plurality of base stations 10 may be connected by wire (for example, an optical fiber compliant with Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (for example, 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.

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

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

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

[0166] 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 UL and DL wireless access methods.

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

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

[0169] User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH. User data, upper layer control information, etc. may be transmitted by the PUSCH. Also, a Master Information Block (MIB) may be transmitted by the PBCH.

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

[0171] 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 read as DL data, and the PUSCH may be read as UL data.

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

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

[0174] Uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (e.g., which may be referred to as 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 the cell may be transmitted by PRACH.

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

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

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

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

[0179] (Base station) FIG. 12 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a 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.

[0180] In this example, the functional blocks of the characteristic portions 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. A part of the processing of each unit described below may be omitted.

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

[0182] 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 signals, and transfer them to the transmission / reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of communication channels, state management of the base station 10, management of radio resources, etc.

[0183] 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., which are described based on the common knowledge in the technical field related to the present disclosure.

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

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

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

[0187] The transmission / reception unit 120 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.

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

[0189] The transceiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel encoding (which may include error correction encoding), 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.

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

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

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

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

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

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

[0196] Note that when the control resource set (CORESET) pool index is set in at least one CORESET, the transmission / reception unit 120 may transmit the DCI for scheduling the physical uplink shared channel (PUSCH) to the user terminal 20 based on a specific assumption regarding the size of the sounding reference signal resource indicator (SRI) field of the DCI.

[0197] The transmission / reception unit 120 may receive the PUSCH transmitted using a precoder based on spatial relationship information (or SRI) determined based on at least one of the CORESET pool index of the CORESET in which the SRI field and the DCI are detected by the user terminal 20.

[0198] (User Terminal) FIG. 13 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 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.

[0199] Note that in this example, mainly the functional blocks of the characteristic portions in the present embodiment are shown, and the user terminal 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.

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

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

[0202] 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. as described based on the common understanding in the technical field related to the present disclosure.

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

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

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

[0206] The transceiver unit 220 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.

[0207] The transmission / reception 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, for example, data and control information acquired from the control unit 210, and generate a bit sequence to be transmitted.

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

[0209] Note that 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 transmission processing to transmit the channel using the DFT-s-OFDM waveform, or otherwise may not perform DFT processing as the above transmission processing.

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

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

[0212] 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 to the acquired baseband signal, and may acquire user data and the like.

[0213] 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), reception 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.

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

[0215] Note that when the control resource set (CORESET) pool index is set in at least one CORESET, the transmission / reception unit 220 may receive (which may be read and replaced by decoding) the DCI based on a specific assumption regarding the size of the sounding reference signal resource identifier (SRI) field of the DCI that schedules the physical uplink shared channel (PUSCH).

[0216] Here, the specific assumption may be, for example, the assumption that the size of the SRI field is necessarily larger than 0 bits, or the assumption that the size of the SRI field being 0 bits is allowed.

[0217] The control unit 210 may determine spatial relation information (or SRI) for the PUSCH based on at least one of the CORESET pool index of the CORESET in which the SRI field and the DCI are detected.

[0218] The transceiver unit 220 may transmit the PUSCH using a precoder (or spatial domain transmission filter) based on the spatial relation information.

[0219] The control unit 210 may select one of a plurality of SRI fields (for example, SRI field #1, #2) included in the DCI based on the CORESET pool index (or PUSCH repetition index) of the CORESET in which the DCI is detected, and determine the spatial relation information for the PUSCH based on the selected SRI field.

[0220] (Hardware Configuration) Note that the block diagrams used in the description of the above embodiments show functional unit blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method for 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 (for example, 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.

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

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

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

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

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

[0226] The processor 1001 operates, for example, an operating system to control the entire computer. 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), etc. may be realized by the processor 1001.

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

[0228] The memory 1002 is a computer-readable recording medium and may be constituted by, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), and the like. The 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.

[0229] The storage 1003 is a computer-readable recording medium and may be constituted by, for example, at least one of 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. The storage 1003 may be referred to as an auxiliary storage device.

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

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

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

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

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

[0235] The 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, the 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) independent of numerology.

[0236] Here, the new numerology may be communication parameters 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 the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the time domain, etc.

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

[0238] 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. The PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called PDSCH (PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using a mini-slot may be called PDSCH (PUSCH) mapping type B.

[0239] A radio frame, sub-frame, slot, mini-slot, and symbol all represent time units for signal transmission. Different names may be used for the radio frame, sub-frame, slot, mini-slot, and symbol respectively. Note that the time units such as frame, sub-frame, slot, mini-slot, and symbol in this disclosure may be read interchangeably with each other.

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

[0241] 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 at each user terminal) to each user terminal in TTI units. Note that the definition of the TTI is not limited to this.

[0242] The TTI may be the transmission time unit for a channel-coded data packet (transport block), code block, codeword, etc., or may be the 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.

[0243] 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 for the scheduling may be controlled.

[0244] A TTI having a time length of 1 ms may be called 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 called a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini-slot, a sub-slot, a slot, etc.

[0245] 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 the long TTI and not less than 1 ms.

[0246] A resource block (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.

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

[0248] 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, or the like.

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

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

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

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

[0253] Note that the structures such as the above-described radio frames, sub-frames, slots, mini-slots, and symbols 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 variously changed.

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

[0255] The names used for parameters, etc. in the present disclosure are not limiting names in any way. Furthermore, mathematical formulas using these parameters, etc. 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.

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

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

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

[0259] The notification of information is not limited to the modes / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information in the present disclosure may be 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 combinations thereof.

[0260] 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 also 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, for example, using a MAC Control Element (CE).

[0261] Also, the notification of predetermined information (e.g., the notification of "being X") is not limited to 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).

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

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

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

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

[0266] 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. can be used interchangeably.

[0267] 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. can be used interchangeably. The base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0268] A base station can accommodate one or more (e.g., three) cells. When the base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area 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 a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services in this coverage.

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

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

[0271] 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 also 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 without a driver (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanoid or non-humanoid). 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.

[0272] Also, the base station in the present disclosure may be replaced by a user terminal. For example, for a configuration in which communication between the base station and the user terminal is replaced with 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 to be 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, "side"). For example, an uplink channel, a downlink channel, etc. may be replaced with a side channel.

[0273] 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 to be functions of the base station 10.

[0274] In the present disclosure, operations assumed to be performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having a base station, it is clear 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, but not limited to, Mobility Management Entity (MME), Serving-Gateway (S-GW), etc.) or a combination thereof.

[0275] 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 methods described in the present disclosure, the elements of various steps are presented using an exemplary order and are not limited to the specific order presented.

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

[0277] As used in the present disclosure, the description "based on" 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".

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

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

[0280] 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 a memory), etc.

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

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

[0283] 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 can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed".

[0284] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more electric 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.

[0285] In this disclosure, the term "A is different from B" 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".

[0286] In this disclosure, when the terms "include", "including", and their variations are used, these terms are intended to be inclusive in the same way as the term "comprising". Further, the term "or" used in this disclosure is not intended to be an exclusive disjunction.

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

[0288] 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 as modifications and variations 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 the purpose of illustrative explanation and does not bring any limiting meaning to the invention according to the present disclosure.

Claims

1. When a control resource set (CORESET) pool index is set for each of a plurality of CORESETs, a receiving unit that receives a plurality of DCI for scheduling a physical uplink shared channel (PUSCH); determining the number of bits of the sounding reference signal resource identifier (SRS Resource Indicator (SRI)) field of each of the plurality of DCI based on the number of SRS resources included in the SRS resource set associated with the CORESET pool index of the CORESET in which each of the plurality of DCI is detected; a control unit that determines spatial relationship information for the PUSCH based on the SRI field and the CORESET pool index. A terminal having the same.

2. The transmission of the PUSCH is non-codebook-based transmission, The precoder for the transmission of the PUSCH is determined based on the spatial relationship information. The terminal according to claim 1.

3. When a control resource set (CORESET) pool index is set for each of a plurality of CORESETs, receiving a plurality of DCI for scheduling a physical uplink shared channel (PUSCH); determining the number of bits of the sounding reference signal resource identifier (SRS Resource Indicator (SRI)) field of each of the plurality of DCI based on the number of SRS resources included in the SRS resource set associated with the CORESET pool index of the CORESET in which each of the plurality of DCI is detected; determining spatial relationship information for the PUSCH based on the SRI field and the CORESET pool index. A wireless communication method for a terminal having the same.

4. When a control resource set (CORESET) pool index is set for each of a plurality of CORESETs, a transmission unit that transmits a plurality of DCI for scheduling a physical uplink shared channel (PUSCH) to a terminal, The number of bits of the sounding reference signal (SRS) resource identifier (SRI) field of each of the plurality of DCI is determined based on the number of SRS resources included in the SRS resource set associated with the CORESET pool index of the CORESET in which each of the plurality of DCI is detected, A receiving unit that receives the PUSCH based on spatial relation information determined based on the SRI field and the CORESET pool index by the terminal. A base station having the same.

5. A system including a terminal and a base station, The terminal is, When a control resource set (CORESET) pool index is set for each of a plurality of CORESETs, a receiving unit that receives a plurality of DCI for scheduling a physical uplink shared channel (PUSCH), Determine the number of bits of the sounding reference signal (SRS) resource identifier (SRI) field of each of the plurality of DCI based on the number of SRS resources included in the SRS resource set associated with the CORESET pool index of the CORESET in which each of the plurality of DCI is detected, A control unit that determines spatial relation information for the PUSCH based on the SRI field and the CORESET pool index. The terminal having the same, The base station is, A transmission unit that transmits the plurality of DCI to a terminal, A receiving unit that receives the PUSCH. A system having the same.

Images