Terminal, wireless communication method, base station, and system

Abstract

A terminal according to an aspect of the present disclosure comprises: a reception unit that receives information related to the setting of transmission of a plurality of physical uplink shared channels (PUSCHs) based on one piece of downlink control information (DCI); and a control unit that determines, from a plurality of reference signal indexes, one or more reference signal indexes that are to be used for at least one of the spatial relation about the plurality of PUSCHs and a path-loss reference signal (PL-RS). According to an aspect of the present disclosure, the PUSCH repetitive-transmission can be appropriately controlled even when a multi-TRP is applied.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In 3GPP Rel.15, repeated transmission is supported for UL data channels (e.g., Physical Uplink Shared Channel (PUSCH)). The UE is controlled to transmit PUSCH over a plurality of slots (e.g., consecutive K slots) based on the repetition factor K set by the network (e.g., base station). That is, when performing repeated transmission, each PUSCH is transmitted in a different slot (e.g., in slot units).

[0006] On the other hand, since Rel.16, when performing repeated transmission of PUSCH, it has been considered to perform a plurality of PUSCH transmissions within one slot. That is, each PUSCH is transmitted in a unit shorter than a slot (e.g., in sub - slot units or mini - slot units).

[0007] Also, since Rel.16, it has been considered to dynamically switch between a single PUSCH transmission and repeated transmission of PUSCH.

[0008] Also, in NR, communication using one or more Transmission / Reception Points (TRPs) (multi - TRP) has been considered.

[0009] However, in the existing NR specifications, how to control the repeated transmission of PUSCH in multi - panel / TRP has not been sufficiently studied. If the repeated transmission of PUSCH in multi - TRP is not properly performed, there is a risk of throughput reduction or communication quality deterioration.

[0010] Therefore, one object of the present disclosure is to provide a terminal and a wireless communication method that can appropriately control PUSCH repeated transmission 、 base station and system as one of the purposes. [[Means for Solving the Problem]]

[0011] A terminal according to one aspect of the present disclosure a transmitting unit that transmits capability information indicating whether to support a default beam for a physical uplink shared channel (PUSCH); the PUSC H a receiving unit that receives downlink control information (DCI) not including a sounding reference signal resource indicator (SRI) field and schedules the PUSCH; when the support for the default beam is indicated by the capability information and is scheduled by the DCI a control unit that determines, as a spatial relation of the PUSCH, a first TCI state among the plurality of TCI states when a plurality of transmission configuration indication (TCI) states are set for a control resource set (CORESET) used to determine the spatial relation of the PUSCH. [[Advantages of the Invention]]

[0012] According to one aspect of the present disclosure, even when multi-TRP is applied, PUSCH repeated transmission can be appropriately controlled. [[Brief Description of the Drawings]]

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

[0021] For example, the UE may determine the symbol allocation in each slot based on the start symbol S and the number of symbols L (e.g., Start and Length Indicator (SLIV)) determined based on the value m of a predetermined field (e.g., TDRA field) in the DCI. Note that the UE may determine the first slot based on the K2 information determined based on the value m of a predetermined field (e.g., TDRA field) of the DCI.

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

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

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

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

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

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

[0028] The slot - based repeated transmission shown in Figure 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 Figure 1B may be referred to as repeated transmission type B (e.g., PUSCH repetition Type B).

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

[0030] For each DCI format for scheduling the PUSCH, either repeated transmission type A or repeated transmission type B may be set for the UE.

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

[0032] Also, since Rel. 16, consideration has been given to performing a dynamic switch between a single PUSCH transmission and repeated PUSCH transmissions.

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

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

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

[0036] For example, use the first higher layer parameter to notify the UE of information regarding the invalid symbol pattern that cannot be used 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.

[0037] Also, the UE may be notified using the second higher layer parameter about whether to set a notification field (or additional bits) in the DCI. 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.

[0038] If the first upper layer parameter is not notified or configured, the UE may control the transmission of the PUSCH without considering the invalid symbol pattern. If the first upper layer parameter is notified or configured, 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 indicates the addition of an additional bit (or a predetermined field) that indicates whether to apply the invalid symbol pattern to the DCI, the UE may determine whether to apply the invalid symbol pattern based on the predetermined field.

[0039] The first upper layer parameter may be information that notifies a symbol pattern that becomes invalid for PUSCH transmission. 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) for the time domain. The UE may determine the resources available for PUSCH transmission in one or more frequency bandwidths (e.g., BWP) based on the information regarding the invalid symbol pattern (see Figure 2B).

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

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

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

[0043] In addition, a case 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 is also assumed. Figure 3A shows a case 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, the PUSCH may be transmitted using the symbols excluding the DL symbol (see Figure 3B).

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

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

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

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

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

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

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

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

[0052] 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 to determine the precoder for codebook-based or non-codebook-based PUSCH transmission based on the SRI.

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

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

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

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

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

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

[0059] When the UE is configured with spatial relation information regarding an 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.

[0060] 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 the spatial domain filter (spatial domain transmission filter) 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.

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

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

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

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

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

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

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

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

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

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

[0071] (Path loss RS) Path loss PL in the transmission power control of each of the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Sounding Reference Signal (SRS) b,f,c (q d ) [dB] is calculated by the UE using the index q of the reference signal (RS, PathlossReferenceRS) for the downlink BWP associated with the active UL BWP b of the carrier f of the serving cell c. d is calculated by the UE using the index q of the reference signal (RS, PathlossReferenceRS) for the downlink BWP associated with the active UL BWP b of the carrier f of the serving cell c.

[0072] In the present disclosure, PathlossReferenceRS, pathloss(PL) - RS, index q dThe RS used for path loss calculation, the RS resource used for path loss calculation, may be interchangeable with each other. In the present disclosure, calculation, estimation, measurement, track, may be interchangeable with each other.

[0073] The PL-RS may be at least one of DL RSs such as SSB and CSI-RS.

[0074] For accurate path loss measurement for transmit power control, the Rel.15 UE sets up to 4 PL-RSs by RRC signaling. Even when the UL transmit beam (spatial relationship) is updated by MAC CE, the PL-RS cannot be updated by MAC CE.

[0075] The Rel.16 UE sets up to 64 PL-RSs by RRC signaling and one PL-RS is indicated (activated) by MAC CE. The UE is required to track up to 4 active PL-RSs for all UL channels (SRS, PUCCH, and PUSCH). Tracking the PL-RS may be calculating the path loss based on the measurement of the PL-RS and storing (remembering) the path loss.

[0076] When the TCI state for PDCCH or PDSCH is updated by MAC CE, the PL-RS may also be updated to the TCI state.

[0077] (Default spatial relationship and default PL-RS) In Rel.15 NR, individual MAC CEs for activation / deactivation of PUCCH spatial relationship and for activation / deactivation of SRS spatial relationship are required. The PUSCH spatial relationship follows the SRS spatial relationship.

[0078] In Rel.16 NR, at least one of the MAC CE for activating / deactivating PUCCH spatial relation and the MAC CE for activating / deactivating SRS spatial relation may not be used.

[0079] The default spatial relation is considered as the spatial relation used by the UE when the spatial relation cannot be used (e.g., cannot be identified, not specified, not activated) for UL transmission. Also, the default PL-RS is considered as the PL-RS to be used when the PL-RS cannot be used (same as above) for UL transmission or when the default spatial relation is used. In the present disclosure, the UE operation using these default spatial relations / default PL-RS may be referred to as the default beam operation.

[0080] For example, the spatial relation used for the transmission of the PUSCH scheduled by DCI format 0_0 may be referred to as the default spatial relation, and the PL-RS used for the transmission power control (downlink path loss estimation in) of this PUSCH may be referred to as the default PL-RS. Hereinafter, the determination of the default spatial relation / default PL-RS in Rel.15 / 16 will be described.

[0081] In Rel.15, the spatial relation of the PUSCH scheduled by DCI format 0_0 follows the spatial relation (active spatial relation) corresponding to the PUCCH resource having the smallest PUCCH resource ID within the active UL BWP of the same cell.

[0082] In Rel.16, for the spatial relation of a PUSCH scheduled by DCI format 0_0 in a certain cell, when the enabling parameter of the default beam (enableDefaultBeamPL-ForPUSCH0-0) for the PUSCH is set to enabled and the UE has not set PUCCH resources for the active UL BWP (or although PUCCH resources are set, the spatial relations of all PUCCH resources are not set), it follows the spatial relation that refers to the RS of QCL type D corresponding to the QCL assumption of the CORESET with the smallest ID in the active DL BWP of the cell. Otherwise, the spatial relation of the PUSCH scheduled by DCI format 0_0 is the same as that in Rel.15.

[0083] When the UE is not provided with the upper layer parameters PUSCH-PathlossReferenceRS and enableDefaultBeamPL-ForSRS, or before the UE provides its own upper layer parameters, the UE calculates the downlink path loss using the RS resource from the SS / PBCH block that has the same index as the SS / PBCH block index used by the UE to obtain the MIB. This RS corresponds to the default PL-RS.

[0084] When PUSCH transmission is scheduled by DCI format 0_0 and a spatial setting is provided by the upper layer parameter PUCCH-SpatialRelationInf for the PUCCH resource with the smallest index among the active UL BWP indexes of each carrier and the serving cell, the UE uses the same RS resource index q as in the case of PUCCH transmission in the PUCCH resource with the smallest index d for estimating the downlink path loss.

[0085] In Rel.16, when PUSCH transmission is not scheduled by DCI format 0_0, and the upper layer parameter enableDefaultBeamPL-ForSRS-r16 is provided to the UE while the upper layer parameters PUSCH-PathlossReferenceRS and PUSCH-PathlossReferenceRS-r16 are not provided, the UE uses, for the PUSCH transmission, the same RS resource index q as the SRS resource set having the SRS resource associated with the PUSCH transmission d as the path loss estimation for the downlink.

[0086] When PUSCH transmission is scheduled by DCI format 0_0 and no spatial relation setting for PUCCH transmission is provided to the UE, or when PUSCH transmission is scheduled by DCI format 0_1 or 0_2 that does not include an SRI field, or when the upper layer parameter SRI-PUSCH-PowerControl is not provided to the UE, the UE uses the RS resource index q equal to 0 of the corresponding PUSCH-PathlossReferenceRS-Id d as the path loss estimation for the downlink. Note that this RS resource may be on the serving cell where the above PUSCH is transmitted, or may be on the serving cell indicated by this value when the upper layer parameter pathlossReferenceLinking is provided.

[0087] In Rel.16, for a PUSCH scheduled by DCI format 0_0 in a certain cell, the PL-RS of the PUSCH is the RS corresponding to the RS resource index that provides the periodic RS resource of QCL type D corresponding to the QCL assumption of the CORESET with the minimum ID in the active DL BWP of the cell, when the enable parameter of the default beam for the PUSCH (enableDefaultBeamPL-ForPUSCH0-0) is set to enabled and the UE has no PUCCH resources configured for the active UL BWP (or has PUCCH resources configured but all PUCCH resources have no spatial relationship configured).

[0088] (Multi-TRP) In NR, it is considered that one or more Transmission / Reception Points (TRPs) (multi-TRP) perform DL transmission to the UE using one or more panels (multi-panel). Also, it is considered that the UE performs UL transmission to one or more TRPs (see Figure 4).

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

[0090] (Mapping pattern) When determining to perform repeated transmission of PUSCH for multiple TRPs, the UE may determine that multiple SRIs and multiple repeated transmissions correspond based on a specific rule. The rule may be called a mapping pattern, a mapping rule, a correspondence pattern, a correspondence relationship, etc. The UE may assume that the number of repetitions of the PUSCH exceeds the number of beams used for PUSCH transmission.

[0091] For example, when determining to perform repeated transmission of PUSCH for multiple TRPs, the UE may determine that multiple SRIs correspond to multiple repeated transmissions in a cyclic manner. Such correspondence may be referred to as cyclic mapping, cyclic pattern, cyclic correspondence, etc.

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

[0093] For example, when determining to perform repeated transmission of PUSCH in multiple TRPs, the UE may determine that multiple SRIs correspond to multiple repeated transmissions sequentially, for example, in pairs of a specific number (e.g., two). Such correspondence may be referred to as sequential mapping, sequential pattern, sequential correspondence, etc.

[0094] FIG. 5B is a diagram showing an example in which multiple SRIs and multiple repeated transmissions correspond sequentially. In FIG. 5B, the UE is specified with a repetition number of 6 and performs repeated transmission of PUSCH using the first SRI and the second SRI. In the example shown in FIG. 5B, the UE sequentially performs PUSCH transmission using the first SRI and PUSCH transmission using the second SRI in pairs of two.

[0095] For example, when determining to perform repeated transmission of PUSCH in multiple TRPs, multiple SRIs and multiple repeated transmissions may correspond continuously such that the number of repetitions approximately matches the number obtained by dividing the number of repetitions by the number of SRIs. When the number of SRIs is 2, such correspondence may be referred to as a half-half pattern (mapping).

[0096] FIG. 5C is a diagram showing an example of using a half-half pattern for the correspondence between a plurality of SRIs and a plurality of repeated transmissions. In FIG. 5C, the UE performs repeated transmission of a PUSCH using a first SRI and a second SRI with 6 specified as the number of repetitions. In the example shown in FIG. 5C, the UE performs PUSCH transmission using the first SRI in the first half (the first 3 times) of the PUSCH transmission opportunity, and performs PUSCH transmission using the second SRI in the second half (the following 3 times) of the PUSCH transmission opportunity.

[0097] Note that, among the plurality of mapping patterns described with reference to FIGS. 5A to 5C above, one of the mapping patterns to be used may be defined in the specification. Also, the plurality of mapping patterns may be defined in the specification, and a mapping pattern to be applied may be set / instructed to the UE using at least one of upper layer signaling and physical layer signaling. Further, the UE may report to the NW about the UE capability regarding which mapping pattern among the plurality of mapping patterns it supports for application.

[0098] Note that the number of repetitions of PUSCH transmission, the number of SRIs, etc. shown in FIGS. 5A to 5C are merely examples and are not limited thereto. Also, in the following drawings, the number of repetitions of PUSCH transmission, the number of code points / code point names of each field, the number of bits, the number of SRIs, etc. are merely examples and are not limited to these examples.

[0099] Also, the above-described mapping pattern may be applied to the correspondence between a plurality of TPMI / TPC commands and a plurality of PUSCHs.

[0100] FIG. 6 is a diagram showing an example of repeated transmission of a PUSCH based on a single DCI for a plurality of TRPs. In FIG. 6, the UE performs repeated transmission of the PUSCH twice. The UE is instructed about information (RS resource) regarding the SRI to be applied to each of PUSCH#1 and PUSCH#2 included in one DCI.

[0101] By the way, in the existing NR specifications, how to control the repeated transmission of PUSCH in multi-panel / TRP (when multi-panel / TRP is configured) has not been sufficiently studied. If the repeated transmission of PUSCH in multi-TRP is not properly performed, there is a risk of throughput degradation or communication quality deterioration.

[0102] More specifically, the method for determining the spatial relationship of PUSCH scheduled by a specific DCI format (for example, DCI format 0_0), and how to control the default spatial relationship / PL-RS for the repeated transmission of PUSCH based on a single DCI have not been sufficiently studied. Therefore, the inventors have conceived a method for controlling PUSCH repeated transmission to solve the above problems.

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

[0104] In the present disclosure, a port, a panel, a beam, an Uplink (UL) transmission entity, a TRP, spatial relationship information (SRI), a spatial relationship, a control resource set (COntrol REsource SET (CORESET)), a PDSCH, a codeword, a 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 panel group, a beam group, a spatial relationship group, a PUCCH group), a CORESET pool, may be mutually replaced. Also, a panel Identifier (ID) and a panel may be mutually replaced. A TRP ID and a TRP may be mutually replaced.

[0105] In the present disclosure, index, ID, indicator, resource ID, etc. may be read interchangeably with each other.

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

[0107] In the present disclosure, list, group, cluster, subset, etc. may be read interchangeably with each other. In the present disclosure, spatial relation information (Spatial Relation Information (SRI)), SRS resource indicator (SRS Resource Indicator (SRI), (or SRI field)), SRS resource, precoder, etc. may be read interchangeably with each other.

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

[0109] In the present disclosure, the first TRP and the second TRP may be read interchangeably with the first PUSCH and the second PUSCH, the first PUSCH transmission opportunity and the second PUSCH transmission opportunity, the first SRI and the second SRI, etc.

[0110] In the following embodiments, the repeated transmission of PUSCH for multiple TRPs may be read interchangeably with PUSCH over multiple TRPs, repeated PUSCH over multiple TRPs, simply repeated PUSCH, repeated transmission, multiple PUSCH transmissions, etc. Also, a single PUSCH transmission for a single TRP may be referred to as simply a single PUSCH transmission, PUSCH transmission in a single TRP, etc.

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

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

[0113] In the present disclosure, determining the spatial relationship / TCI state of PUSCH may be read as determining the reference signal (index) applied (utilized) to the spatial relationship / PL-RS of PUSCH.

[0114] In each embodiment of the present disclosure, the PUSCH transmission for a plurality of TRPs using one DCI and the codebook-based PUSCH transmission will be described as examples, but it may also be applied to non-codebook-based PUSCH transmission, and the PUSCH transmission to which each embodiment can be applied is not limited to these. When each embodiment in the present disclosure is applied to non-codebook-based PUSCH transmission, one or more SRS resources (SRI) may be indicated to the UE by each SRI field. Also, common or different embodiments may be applied to codebook-based PUSCH transmission and non-codebook-based PUSCH transmission.

[0115] Also, in each embodiment of the present disclosure, although the main example will describe the case where the number of multiple TRPs, multiple SRIs, etc. is two, these numbers may be three or more. Also, the "dynamic switch" in the present disclosure may mean a "switch using at least one of upper layer signaling and physical layer signaling". Also, the "switch" in the present disclosure may be read interchangeably with switching, change, changing, application, etc.

[0116] (Wireless communication method) <First Embodiment> In the first embodiment, the UE may be configured with repeated transmission of PUSCH based on a single DCI (S-DCI based PUSCH repetition), and the PUSCH may be scheduled using a DCI format that does not have (or does not include) an SRI field (for example, DCI format 0_0). For the UE, setting the repeated transmission of PUSCH based on a single DCI may mean that a plurality of SRI fields / TPMI fields / TPC command fields are set in a specific DCI format (for example, DCI format 0_1 / 0_2).

[0117] When the PUSCH is scheduled using a specific DCI format (for example, DCI format 0_0), the UE may not perform the repeated transmission of the PUSCH (or it may be assumed that the PUSCH is not repeatedly transmitted (or transmitted once)) (Embodiment 1-1). That is, when the PUSCH is scheduled using a specific DCI format (for example, DCI format 0_0), the UE may control to perform the transmission of the PUSCH with the operations defined up to Rel.15.

[0118] Also, when the PUSCH is scheduled using a specific DCI format (e.g., DCI format 0_0), the UE may repeat the transmission of the PUSCH X (X is an arbitrary integer) times (Embodiment 1-2). In the present disclosure, this "X" may mean the number of beams applied to the repeated transmission of the PUSCH and may be different from the number of times the PUSCH is repeated.

[0119] In Embodiment 1-2, when at least one of the following Conditions 1 to 4 is satisfied, even when the PUSCH is scheduled using a specific DCI format (e.g., DCI format 0_0), the UE may repeat the transmission of the PUSCH X (X is an arbitrary integer) times.

[0120] Condition 1: A plurality of spatial relationships are set for the PUCCH resource (associated PUCCH resource) used to determine the PL-RS / spatial relationship of the PUSCH. Condition 2: A plurality of TCI states are set for the CORESET (associated CORESET) used to determine the PL-RS / spatial relationship of the PUSCH. Condition 3: A plurality of TCI states are set for the SRS resource (associated SRS resource) used to determine the PL-RS / spatial relationship of the PUSCH. Condition 4: A higher layer parameter for setting / enabling / activating the repeated transmission of the PUSCH scheduled using a specific DCI format (e.g., DCI format 0_0) is set.

[0121] Regarding Conditions 1 to 3, the setting of multiple spatial relationships / TCI states for PUCCH resources / CORESET / SRS resources may mean that multiple spatial relationships / TCI states are set for the PUCCH resources / CORESET / SRS resources for the default PL-RS / default spatial relationship determined according to the above-mentioned Rel.15 / 16 or the reference RS (such as CSI-RS, SSB, SRS, etc.).

[0122] Instead of or in addition to Conditions 1 to 3, the following Condition 5 may be used to determine whether the PUSCH can be repeatedly transmitted when the PUSCH is scheduled using a specific DCI format (for example, DCI format 0_0): Condition 5: Multiple spatial relationships / TCI states are set for the PUCCH resources / CORESET / SRS resources for the PL-RS / spatial relationship of the PUSCH or the reference RS (such as CSI-RS, SSB, SRS, etc.).

[0123] Note that the above X may be predefined in the specification (for example, X = 2), may be set using upper layer signaling, or may be a value reported to the network (NW) as the UE capability.

[0124] 《PL-RS / Spatial Relationship for PUSCH Transmission in Embodiment 1-1》 Hereinafter, a method for determining one PL-RS / spatial relationship for PUSCH transmission in the above Embodiment 1-1 will be described.

[0125] The UE may assume / expect that one spatial relationship / TCI state is set / associated with the PUCCH resources / CORESET / SRS resources used to determine the PL-RS / spatial relationship of the PUSCH.

[0126] Also, when one spatial relation / TCI state is set / associated with the PUCCH resource / CORESET / SRS resource used to determine the PL-RS / spatial relation of PUSCH, the UE may assume that the one spatial relation / TCI state is the default PL-RS / spatial relation for PUSCH.

[0127] When multiple spatial relations / TCI states are set / associated with the PUCCH resource / CORESET / SRS resource used to determine the PL-RS / spatial relation of PUSCH, the UE may determine / select one spatial relation / TCI state from the multiple spatial relations / TCI states as the default PL-RS / spatial relation for PUSCH.

[0128] The UE may determine / select one spatial relation / TCI state that corresponds to at least one of Rules 1 to 5 described below from the multiple spatial relations / TCI states as the default PL-RS / spatial relation for PUSCH: Rule 1: The spatial relation / TCI state corresponding to the maximum (minimum) spatial relation ID / TCI state ID, Rule 2: The spatial relation / TCI state corresponding to the maximum (minimum) PUCCH resource ID / CORESET ID / SRS resource ID, Rule 3: For each PUCCH resource / CORESET / SRS resource, the spatial relation / TCI state corresponding to the first / second beam / resource when the first / second beam / resource is set, and the first / second spatial relation ID / TCI state ID / PUCCH resource ID / CORESET ID / SRS resource ID, Rule 4: One spatial relation / TCI state determined / selected according to a specific rule set in the upper layer signaling, Rule 5: The spatial relation / TCI state corresponding to the specific (exact) spatial relation ID / TCI state ID set / instructed in the upper layer signaling.

[0129] 《PL-RS / Spatial Relation for PUSCH Transmission in Embodiments 1-2》 Hereinafter, a method for determining a plurality of PL-RS / space relationships for repeated transmission of PUSCH in the above Embodiments 1-2 will be described.

[0130] The UE may assume that X spatial relationships / TCI states are set / associated with the PUCCH resource / CORESET / SRS resource used to determine the PL-RS / space relationship of the PUSCH.

[0131] Also, when X spatial relationships / TCI states are set / associated with the PUCCH resource / CORESET / SRS resource used to determine the PL-RS / space relationship of the PUSCH, the UE may assume that the X spatial relationships / TCI states are the default PL-RS / space relationships for the PUSCH at each transmission opportunity of the PUSCH.

[0132] When a number of spatial relationships / TCI states greater than X are set / associated with the PUCCH resource / CORESET / SRS resource used to determine the PL-RS / space relationship of the PUSCH, the UE may determine / select X spatial relationships / TCI states from the number of spatial relationships / TCI states greater than X as the default PL-RS / space relationships for the PUSCH.

[0133] The UE may determine / select X spatial relationships / TCI states corresponding to at least one of Rules 1 to 5 described below from the number of spatial relationships / TCI states greater than X as the default PL-RS / space relationships for the PUSCH: Rule 1: The spatial relationships / TCI states corresponding to X spatial relationship IDs / TCI state IDs in descending (ascending) order from the maximum (minimum) spatial relationship ID / TCI state ID, Rule 2: The spatial relationships / TCI states corresponding to X PUCCH resource IDs / CORESET IDs / SRS resource IDs in descending (ascending) order from the maximum (minimum) PUCCH resource ID / CORESET ID / SRS resource ID, Rule 3: For each PUCCH resource / CORESET / SRS resource, the spatial relation / TCI state corresponding to the first / second beam / resource when the first / second spatial relation ID / TCI state ID / PUCCH resource ID / CORESET ID / SRS resource ID is set, Rule 4: X spatial relations / TCI states determined / selected according to specific rules set by upper layer signaling, Rule 5: The spatial relation / TCI state corresponding to X specific (exact) spatial relation IDs / TCI state IDs set / instructed by upper layer signaling.

[0134] Note that among the above rules, X spatial relations / TCI states may be determined / selected by combining two or more rules. For example, the UE may determine A (A is a number smaller than X) spatial relations / TCI states using one rule among the X spatial relations / TCI states to be determined, and then determine X - A spatial relations / TCI states using another rule.

[0135] When a number (Y (e.g., Y = 1)) of spatial relations / TCI states smaller than X is set / associated with the PUCCH resource / CORESET / SRS resource used to determine the PL-RS / spatial relation of PUSCH, the UE may assume that the Y spatial relations / TCI states are the default PL-RS / spatial relation for PUSCH.

[0136] Then, the UE may determine the remaining X - Y spatial relations / TCI states that at least one of Rules 6 and 7 described below applies to: Rule 6: The spatial relation / TCI state corresponding to the Nth (N is an integer greater than or equal to 2) / maximum / minimum PUCCH resource ID / CORESET ID, Rule 7: The spatial relation / TCI state corresponding to the specific (exact) spatial relation ID / TCI state ID set / instructed by upper layer signaling and used to determine the Y spatial relations / TCI states.

[0137] According to the first embodiment above, even when the repeated transmission of PUSCH is scheduled in DCI format 0_0, the spatial relationship / PL-RS of PUSCH can be appropriately determined.

[0138] <Second Embodiment> In the second embodiment, for the repeated transmission of PUSCH scheduled in a specific DCI format (e.g., DCI format 0_1 / 0_2) having an SRI field, the UE may apply the default PL-RS / spatial relationship in the method described in the first embodiment.

[0139] FIG. 7A is a diagram showing an example of the repeated transmission of PUSCH in existing Rel.15 / 16. In FIG. 7A, for the repeated transmission of PUSCH (PUSCH#1 and PUSCH#2) scheduled by a single DCI, a common beam / PL-RS (beam / PL-RS#1) is set / indicated. FIG. 7B is a diagram showing an example of the repeated transmission of PUSCH according to the second embodiment. In FIG. 7B, different beams / PL-RS (beam / PL-RS#1 or beam / PL-RS#2) are set / indicated for each of the repeated transmissions of PUSCH (PUSCH#1 and PUSCH#2) scheduled by a single DCI. In this embodiment, the switching of operations as shown in FIGS. 7A and 7B will be described.

[0140] In the second embodiment, "when the UE schedules PUSCH using a specific DCI format (e.g., DCI format 0_0)" in the first embodiment may be read as "when the UE schedules PUSCH with the default beam operation set" and "when the UE schedules PUSCH for which the PL-RS / spatial relationship is not set".

[0141] Unlike the default beam operation for PUSCH in Rel.16, the UE may assume that different beams / PL-RS are set for each repetition (transmission opportunity).

[0142] When a specific higher-layer parameter (e.g., enableDefaultBeamPL-ForSRS_r17) defined after Rel. 17 is set in the UE, it may be assumed that different beams / PL-RSs are set / indicated for each transmission opportunity of the PUSCH repeated transmission.

[0143] Also, when a specific higher-layer parameter (e.g., enableDefaultBeamPL-ForSRS) is set in the UE and the repeated transmission of the PUSCH is scheduled with a specific DCI format (e.g., DCI format 0_1 / 0_2) that includes a plurality of SRI fields / TPMI fields / TPC command fields, it may be assumed that different beams / PL-RSs are set / indicated for each transmission opportunity of the PUSCH repeated transmission.

[0144] When at least one of the following occurs: when a PUSCH with default beam operation set for the UE is scheduled, and when a PUSCH with no PL-RS / space relation set for the UE is scheduled, a specific field (e.g., SRI field) may not be included in the specific DCI format (e.g., DCI format 0_1 / 0_2) that schedules the PUSCH.

[0145] Also, when at least one of a specific higher-layer parameter (e.g., enableDefaultBeamPL-ForSRS) and a specific higher-layer parameter (e.g., enableDefaultBeamPL-ForSRS_r17) defined after Rel. 17 is set in the UE, it may be assumed that a specific field (e.g., SRI field) is not included in the specific DCI format (e.g., DCI format 0_1 / 0_2) that schedules the PUSCH.

[0146] Also, when a PUSCH with a default beam operation set for the UE is scheduled, and / or when a PUSCH with no PL-RS / space relation set for the UE is scheduled, a specific DCI format (e.g., DCI format 0_1 / 0_2) for scheduling the PUSCH may include a specific field (e.g., TPMI field / TPC command field).

[0147] Also, when a PUSCH with a default beam operation set for the UE is scheduled, and / or when a PUSCH with no PL-RS / space relation set for the UE is scheduled, a specific DCI format (e.g., DCI format 0_1 / 0_2) for scheduling the PUSCH may not include a specific field (e.g., TPMI field / TPC command field). The UE may determine / judge the value of the TPMI field / value of the TPC command field based on specific rules. The specific rules may be predefined in the specification or may be set for the UE by upper layer signaling.

[0148] Figures 8A and 8B are diagrams showing an example of a DCI format for setting repeated transmission of a PUSCH based on a single DCI. In the example shown in Figure 8A, the DCI format includes two SRI fields (SRI#1 and SRI#2), two TPMI fields (TPMI#1 and TPMI#2), and two TPC command fields (TPC#1 and TPC#2). On the other hand, in the example of Figure 8B showing DCI for a PUSCH with a default beam operation set, the DCI format includes two TPMI fields (TPMI#1 and TPMI#2) and two TPC command fields (TPC#1 and TPC#2).

[0149] By defining a DCI format related to the default beam operation as shown in Figures 8A and 8B, the overhead of the DCI can be reduced.

[0150] According to the second embodiment above, even when the repeated transmission of PUSCH is scheduled in DCI format 0_1 / 0_2, the spatial relation / PL-RS of PUSCH can be appropriately determined.

[0151] <Modification example> Even when a DCI format (e.g., DCI format 0_1 / 0_2) including a specific upper layer parameter (e.g., enableDefaultBeamPL-ForSRS) is set for the UE and includes a plurality of specific fields (e.g., SRI field / TPMI field / TPC command field), and PUSCH is scheduled, the UE may perform the operation of repeated transmission of PUSCH defined in Rel.15 / 16 (the operation using one default spatial relation / PL-RS as shown in FIG. 7A).

[0152] A UE that performs repeated transmission of PUSCH based on a single DCI does not necessarily have to perform the operation using the default spatial relation / PL-RS. In other words, for a UE that performs repeated transmission of PUSCH based on a single DCI, it may be assumed that the spatial relation / PL-RS for the PUSCH is always set.

[0153] <Third embodiment> Each embodiment of the present disclosure may be applied under at least one of the following conditions: when the UE reports to the NW the UE capabilities corresponding to at least one of the following, and when at least one of the following UE capabilities is set / activated / instructed by upper layer signaling for the UE. Each embodiment of the present disclosure may be applied when a specific upper layer parameter is set / activated / instructed for the UE.

[0154] The UE capability may be defined by whether repeated transmission of PUSCH based on a single DCI for a plurality of TRPs is supported.

[0155] Alternatively, the UE capability may be defined based on whether different SRI fields / TPMI fields / TPC command fields are supported for each transmission opportunity of the PUSCH repeated transmission.

[0156] The UE capability may be defined by the number of repetitions of the PUSCH.

[0157] The UE capability may be defined by the number of active beams / PL-RS for the PUSCH repeated transmission.

[0158] The UE capability may be defined based on whether the default spatial relation / PL-RS for the PUSCH repeated transmission is supported.

[0159] The UE capability may be defined based on whether the default spatial relation / PL-RS for the PUSCH repeated transmission for determining one beam / PL-RS for each PUCCH resource / CORESET / SRS resource in Embodiment 1-1 is supported.

[0160] According to the above-described third embodiment, the UE can implement the method described in the above-described embodiments while maintaining compatibility with the existing specifications.

[0161] (Wireless Communication System) Next, 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.

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

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

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

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

[0166] The wireless communication system 1 may include a base station 11 that forms a macro cell C1 with a relatively wide coverage, 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.

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

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

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

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

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

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

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

[0174] The wireless access method may also 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.

[0175] In the wireless communication system 1, as a downlink channel, 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.

[0176] Also, in the wireless communication system 1, as an uplink channel, 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.

[0177] 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, the Master Information Block (MIB) may be transmitted by the PBCH.

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

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

[0180] For the detection of the PDCCH, a control resource set (COntrol REsource SET (CORESET)) and a search space may be used. The CORESET corresponds to the resource for searching for the DCI. The search space corresponds to the search area and search method of 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 setting.

[0181] 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 setting", "search space set setting", "CORESET", "CORESET setting", etc. in the present disclosure may be read as each other.

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

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

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

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

[0186] Also, in the radio communication system 1, as an uplink reference signal (UL-RS), a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted. Note that DMRS may also be referred to as a UE-specific reference signal.

[0187] (Base station) FIG. 10 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

[0188] Note that in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and the base station 10 may be assumed to have other functional blocks necessary for radio communication. Some of the processes of each part described below may be omitted.

[0189] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, a control circuit, etc. described based on the common understanding in the technical field related to the present disclosure.

[0190] 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 transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal and transfer it to the transceiver unit 120. The control unit 110 may perform call processing (setting, release, etc.) of a communication channel, state management of the base station 10, management of radio resources, etc.

[0191] The transceiver unit 120 may include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc. described based on the common knowledge in the technical field related to the present disclosure.

[0192] The transceiver unit 120 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 1211 and the RF unit 122. The receiver unit may be composed of the reception processing unit 1212, the RF unit 122, and the measurement unit 123.

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

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

[0195] The transceiver 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), or the like.

[0196] The transceiver 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, control information, etc. acquired from the control unit 110, and generate a bit string to be transmitted.

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

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

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

[0200] The transmission / reception 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 to the acquired baseband signal, and may acquire user data and the like.

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

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

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

[0204] The transmission / reception unit 120 may transmit information regarding the setting of transmission of a plurality of physical uplink shared channels (PUSCHs) based on one piece of downlink control information (DCI). The control unit 110 may control the reception of the plurality of PUSCHs to which at least one of a spatial relationship in which one or more of a plurality of reference signal indexes are used and a path loss reference signal (PL-RS) is applied (first and second embodiments).

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

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

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

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

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

[0210] 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 a transmission processing unit 2211 and an RF unit 222. The receiver unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

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

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

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

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

[0215] 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, and digital-to-analog conversion on the bit sequence to be transmitted, and output a baseband signal.

[0216] 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, and if not, it may not perform DFT processing as the above transmission processing.

[0217] 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 radio frequency band signal via the transmission / reception antenna 230.

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

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

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

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

[0222] The transmission / reception unit 220 may receive information related to the setting of the transmission of a plurality of physical uplink shared channels (PUSCH) based on one piece of downlink control information (DCI). The control unit 210 may determine one or more reference signal indexes to be used for at least one of the spatial relationship and the path loss reference signal (PL-RS) for the plurality of PUSCH from a plurality of reference signal indexes (first and second embodiments).

[0223] The control unit 210 may determine the number of at least one of the spatial relationship and the PL-RS for the plurality of PUSCH based on the number of beams applied to the PUSCH (first embodiment).

[0224] The control unit 210 may assume that different PL-RS are applied to each transmission opportunity of the plurality of PUSCH when a specific upper layer parameter is set (second embodiment).

[0225] The format of the DCI may be at least one of DCI format 0_1 and DCI format 0_2. The DCI may not include a sounding reference signal resource indicator (Sounding Reference Signal Resource Indicator (SRI)) field.

[0226] (Hardware Configuration) Note that the block diagrams used in the description of the above embodiments show blocks of functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly connected (for example, using wired, wireless, etc.), 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.

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

[0228] 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. 12 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 be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0229] In the present disclosure, terms such as device, circuit, device, section, unit, etc. can be read interchangeably with each other. The hardware configurations 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.

[0230] For example, although only one processor 1001 is illustrated, 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.

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

[0232] The processor 1001 controls the entire computer by operating an operating system, for example. The processor 1001 may be constituted by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, etc. 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.

[0233] Also, 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 for causing 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.

[0234] 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 appropriate storage media. The memory 1002 may be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 can store a program (program code), software module, etc. executable for implementing the wireless communication method according to an embodiment of the present disclosure.

[0235] 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 appropriate storage media. The storage 1003 may be referred to as an auxiliary storage device.

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

[0237] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives an external input. The output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs an output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

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

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

[0240] (Modification example) In addition, with regard to the terms described in this disclosure and the terms necessary for understanding this 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.

[0241] A radio frame may be composed of one or a plurality of periods (frames) in the time domain. Each of the one or a plurality of periods (frames) constituting the radio frame may be called a subframe. Further, a subframe may be composed of one or a plurality of slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.

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

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

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

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

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

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

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

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

[0250] 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, a shortened subframe, a short subframe, a mini-slot, a sub-slot, a slot, etc.

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

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

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

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

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

[0256] A Bandwidth Part (BWP) (which may also be referred to as a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks 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.

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

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

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

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

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

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

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

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

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

[0266] Note that the 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, the RRC signaling may be referred to as an RRC message and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. Also, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

[0268] The determination may be made based on a value represented by 1 bit (either 0 or 1), or may be made based on a boolean value represented by true or false, or may be made by comparing numerical values (for example, comparison with a predetermined value).

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

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

[0271] The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may mean the devices (such as base stations) included in the network.

[0272] 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", and "panel" can be used interchangeably.

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

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

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

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

[0277] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), a moving body that moves 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.

[0278] In addition, 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 by communication between a plurality of user terminals (which may be referred to as, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), each aspect / embodiment of the present disclosure may be applied. In this case, the functions of the base station 10 described above may be configured 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, the uplink channel, downlink channel, etc. may be replaced with side channels.

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

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

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

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

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

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

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

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

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

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

[0289] 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 may be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed".

[0290] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and also, by way of 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.

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

[0292] 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" as used in this disclosure is not intended to be an exclusive disjunction.

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

[0294] 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 illustrative purposes and does not bring any restrictive meaning to the invention according to the present disclosure.

Claims

A transmitting unit that transmits capability information indicating whether to support a default beam for a Physical Uplink Shared Channel (PUSCH); A receiving unit that receives downlink control information (DCI) that schedules the PUSCH and does not include a sounding reference signal resource indicator (SRI) field; A control unit that, when the support for the default beam is indicated by the capability information and a plurality of transmission configuration indication (TCI) states are set for a control resource set (CORESET) used to determine the spatial relationship of the PUSCH scheduled by the DCI, determines the first TCI state among the plurality of TCI states as the spatial relationship of the PUSCH. A terminal having the above components.

2. The terminal according to claim 1, wherein the format of the DCI is DCI format 0_0. A step of transmitting capability information indicating whether to support a default beam for a Physical Uplink Shared Channel (PUSCH); A step of receiving downlink control information (DCI) that schedules the PUSCH and does not include a sounding reference signal resource indicator (SRI) field; A step of, when the support for the default beam is indicated by the capability information and a plurality of transmission configuration indication (TCI) states are set for a control resource set (CORESET) used to determine the spatial relationship of the PUSCH scheduled by the DCI, determining the first TCI state among the plurality of TCI states as the spatial relationship of the PUSCH. A wireless communication method for a terminal having the above steps. A receiving unit that receives capability information indicating whether to support a default beam for a Physical Uplink Shared Channel (PUSCH); A transmitting unit that transmits downlink control information (DCI) that schedules the PUSCH and does not include a sounding reference signal resource indicator (SRI) field; A base station having a control unit that determines a first transmission configuration indication (TCI) state among the plurality of TCI states as the spatial relation of the physical uplink shared channel (PUSCH) when the support for the default beam is indicated by the ability information and a plurality of transmission configuration indication (TCI) states are set for a control resource set (CORESET) used to determine the spatial relation of the PUSCH scheduled by the DCI. **Claim 5** A system having a terminal and a base station, wherein the terminal has a transmission unit that transmits ability information indicating whether or not it supports a default beam for a physical uplink shared channel (PUSCH), a reception unit that receives downlink control information (DCI) not including a sounding reference signal resource indicator (SRI) field that schedules the PUSCH, and a control unit that determines a first TCI state among the plurality of TCI states as the spatial relation of the PUSCH when the support for the default beam is indicated by the ability information and a plurality of transmission configuration indication (TCI) states are set for a control resource set (CORESET) used to determine the spatial relation of the PUSCH scheduled by the DCI; wherein the base station is a system having a transmission unit that transmits the DCI.

Images