Terminal, wireless communication method, base station, and system

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives setting information, which indicates a physical uplink control channel (PUCCH) resource having a minimum ID and does not include spatial relationship information; and a control unit that controls the reception of a physical uplink shared channel (PUSCH) that will be scheduled by using a downlink control information (DCI) format 0_0.

Description

Technical Field

[0001] The present disclosure relates to a terminal in a next-generation mobile communication system 、 and a wireless communication method , Base Station and System thereof.

Background Art

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

[0003] A successor system to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), New Radio (NR), 3GPP Rel. 15 and later, etc.) is also under consideration.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In a future wireless communication system (e.g., NR), a user terminal (terminal, user terminal, User Equipment (UE)) is considered to control transmission and reception processing based on information regarding Quasi-Co-Location (QCL).

[0006] However, it is not clear how to determine a reference signal (RS) for at least one of QCL and path loss calculation in reception of a downlink (DL) signal or transmission of an uplink (UL) signal. If the UE does not determine an appropriate reference signal, there is a risk of degradation of system performance such as a throughput decrease.

[0007] Therefore, one object of the present disclosure is to provide a terminal that appropriately determines a reference signal for at least one of QCL and path loss calculation 、 wireless communication method , Base Station and System as one of the purposes.

Means for Solving the Problems

[0008] A terminal according to an aspect of the present disclosure includes a receiving unit that receives a downlink control information (DCI) format 0_0 for scheduling a physical uplink shared channel (PUSCH), and one or more physical uplink control channels (PUCCH) on an active uplink bandwidth part (BWP) of a cell of the PUSCH. When resources are set and spatial relation information is not included in all of the one or more PUCCH resources, a control unit that determines a spatial relation of the PUSCH based on a quasi co-location (QCL) assumption of a specific control resource set. Further, when the one or more PUCCH resources are configured on the active uplink link BWP and the spatial relation information is not included in all of the one or more PUCCH resources, the control unit estimates the path loss of the PUSCH based on the QCL assumption, and controls the transmission power of the PUSCH based on the path loss of the PUSCH and the transmission power control (TPC) command value in the DCI format 0_0 .

Effects of the Invention

[0009] According to an aspect of the present disclosure, a reference signal for at least one of QCL and path loss calculation can be appropriately determined.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

MODE FOR CARRYING OUT THE INVENTION

[0011] (Transmission Power Control) <Transmission Power Control for PUSCH> In NR, the transmission power of PUSCH is controlled based on the TPC command (also referred to as a value, an increment / decrement value, a correction value, etc.) indicated by the value of a predetermined field (also referred to as a TPC command field, etc.) in DCI.

[0012] For example, when a UE transmits PUSCH on an active UL BWP b of a carrier f of a serving cell c using a parameter set (open-loop parameter set) having an index j and an index l of a power control adjustment state (PUSCH power control adjustment state), the transmission power of PUSCH (P PUSCH、b,f,c (i,j,q d, l) may be represented by the following formula (1). The power control adjustment state may be referred to as a value based on the TPC command of the power control adjustment state index l, a cumulative value of the TPC command, or a value by a closed loop. l may be referred to as a closed loop index.

[0013] Also, the PUSCH transmission opportunity i is a period during which PUSCH is transmitted, and may be composed of, for example, one or more symbols, one or more slots, etc.

[0014] [Number]

[0015] Here, P CMAX,f,c(i) is, for example, the transmission power of the user terminal set for carrier f of serving cell c in transmission opportunity i (also referred to as the maximum transmission power, UE maximum output power, etc.). P O_PUSCH,b,f,c (j) is, for example, a parameter related to the target reception power set for the active UL BWP b of carrier f of serving cell c in transmission opportunity i (also referred to as a parameter related to the transmission power offset, transmission power offset P0, target reception power parameter, etc.).

[0016] M PUSCH RB,b,f,c (i) is, for example, the number of resource blocks (bandwidth) allocated to PUSCH for transmission opportunity i in the active UL BWP b of carrier f of serving cell c and subcarrier spacing μ. α b,f,c (j) is a value provided by a higher layer parameter (also referred to as msg3 - Alpha, p0 - PUSCH - Alpha, fractional factor, etc.).

[0017] PL b,f,c (q dis, for example, the index q of a reference signal (reference signal (RS), path loss reference RS, path loss reference RS for path loss measurement, DL-RS for path loss measurement, PUSCH-PathlossReferenceRS) for a downlink BWP associated with the active UL BWP b of carrier f of serving cell c d is the path loss (path loss estimation [dB], path loss compensation) calculated at the user equipment using

[0018] If the UE is not provided with a path loss reference RS (e.g., PUSCH-PathlossReferenceRS), or if the UE is not provided with individual upper layer parameters, the UE uses the RS resources from the synchronization signal (SS) / physical broadcast channel (PBCH) block (SS block (SSB)) used to obtain the Master Information Block (MIB) to calculate PL b,f,c (q d ) may be calculated.

[0019] If the UE is configured with a number of RS resource indexes up to the value of the maximum number of path loss reference RSs (e.g., maxNrofPUSCH-PathlossReferenceRSs), and a set of respective RS configurations for the RS resource indexes by the path loss reference RS, the set of RS resource indexes may include one or both of a set of SS / PBCH block indexes and a set of channel state information (CSI)-reference signal (RS) resource indexes. The UE may identify the RS resource index q within the set of RS resource indexes d for use.

[0020] If PUSCH transmission is scheduled by a Random Access Response (RAR) UL grant, the UE may use the same RS resource index q for the corresponding PRACH transmission d for use.

[0021] If the UE is provided with the setting of the power control of the PUSCH by the sounding reference signal (SRS) resource indicator (SRI) (for example, SRI-PUSCH-PowerControl), and is provided with one or more values of the ID of the path loss reference RS, the mapping between the set of values for the SRI field in DCI format 0_1 and the set of ID values of the path loss reference RS may be obtained from the upper layer signaling (for example, sri-PUSCH-PowerControl-Id in SRI-PUSCH-PowerControl). The UE determines the RS resource index q from the ID of the path loss reference RS mapped to the SRI field value in DCI format 0_1 that schedules the PUSCH d may be determined.

[0022] If the PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided with the PUCCH spatial relation information for the PUCCH resource having the lowest index for each carrier f and the serving cell c's active UL BWP b, the UE may use the same RS resource index q as the PUCCH transmission within the PUCCH resource d for use.

[0023] If the PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided with the spatial setting of the PUCCH transmission, or if the PUSCH transmission is scheduled by DCI format 0_1 that does not include the SRI field, or if the setting of the power control of the PUSCH by the SRI is not provided to the UE, the UE may use the RS resource index q having an ID of zero for the path loss reference RS d for use.

[0024] For PUSCH transmission configured by a configured grant configuration (e.g., ConfiguredGrantConfig), if the configured grant configuration includes a predetermined parameter (e.g., rrc-CofiguredUplinkGrant), the RS resource index q is determined by the path loss reference index (e.g., pathlossReferenceIndex) within the predetermined parameter. d may be provided to the UE.

[0025] For PUSCH transmission configured by a configured grant configuration, if the configured grant configuration does not include a predetermined parameter, the UE determines the RS resource index q from the value of the ID of the path loss reference RS mapped to the SRI field within the DCI format that activates the PUSCH transmission. d If the DCI format does not include an SRI field, the UE may determine the RS resource index q having an ID of zero for the path loss reference RS. d

[0026] Δ TF,b,f,c (i) is the transmission power adjustment component (offset, transmission format compensation) for the uplink BWP b of carrier f of serving cell c.

[0027] f b,f,c (i, l) is the PUSCH power control adjustment state for the active uplink BWP b of carrier f of serving cell c in transmission opportunity i. For example, f b,f,c (i, l) may be represented by Equation (2).

[0028]

Equation

[0029] Here, δ PUSCH,b,f,c ​(i, l) may be the TPC command value included in DCI format 0_0 or DCI format 0_1 that schedules the PUSCH transmission opportunity i on the active UL BWP b of carrier f of serving cell c, or the TPC command value encoded by combining with other TPC commands in DCI format 2_2 having a CRC scrambled by a specific RNTI (Radio Network Temporary Identifier) (e.g., TPC-PUSCH-RNTI).

[0030] Σ m=0 C(Di)-1 δ PUCCH,b,f,c (m, l) may be the sum of the TPC command values in the set D i having the cardinality C(D i ). D i is the set of TPC command values received by the UE between, for the PUSCH power control adjustment state l, before the K 0 of PUSCH transmission opportunity i - i PUSCH (i - i 0 ) - 1 symbols and before the K PUSCH (i) symbols of PUSCH transmission opportunity i. i 0 is the smallest positive integer such that the K 0 of PUSCH transmission opportunity i - i PUSCH (i - i 0 ) symbols is earlier than the K PUSCH (i) symbols of PUSCH transmission opportunity i.

[0031] If the PUSCH transmission is scheduled by DCI format 0_0 or DCI format 0_1, K PUSCH (i) may be the number of symbols in the active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUSCH transmission. If the PUSCH transmission is set by the configured grant configuration information (ConfiguredGrantConfig), KPUSCH (i) is the number of symbols per slot N in the active UL BWP b of carrier f in serving cell c symb slot and is equal to K, which is the product of the minimum value of the value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon). PUSCH,min It may be the number of symbols.

[0032] The power control adjustment state may be set to have a plurality of states (for example, two states) or a single state by upper layer parameters. Also, when a plurality of power control adjustment states are set, one of the plurality of power control adjustment states may be identified by an index l (for example, l ∈ {0, 1}).

[0033] Note that expressions (1) and (2) are merely examples and are not limited thereto. The user equipment may control the transmission power of the PUSCH based on at least one parameter exemplified in expressions (1) and (2), and additional parameters may be included or some parameters may be omitted. Also, in the above expressions (1) and (2), the transmission power of the PUSCH is controlled for each active UL BWP of a certain carrier in a certain serving cell, but this is not limiting. At least a part of the serving cell, carrier, BWP, and power control adjustment state may be omitted.

[0034] <Transmission Power Control for PUCCH> Also, in NR, the transmission power of the PUCCH is controlled based on the TPC command (also referred to as a value, increment / decrement value, correction value, indication value, etc.) indicated by the value of a predetermined field (also referred to as a TPC command field, first field, etc.) in the DCI.

[0035] For example, using the index l of the power control adjustment state (PUCCH power control adjustment state), the transmission power P of the PUCCH in the transmission occasion i (also referred to as the transmission period, etc.) of the active UL BWP b of the carrier f of the serving cell c for the PUCCH PUCCH、b,f,c (i,q u ,q d ,l)) may be represented by the following formula (3). The power control adjustment state may be referred to as a value based on the TPC command of the power control adjustment state index l, a cumulative value of the TPC command, or a value by a closed loop. l may be referred to as a closed loop index.

[0036] Also, the PUCCH transmission occasion i is a period during which the PUCCH is transmitted, and may be composed of, for example, one or more symbols, one or more slots, etc.

[0037]

Number

[0038] Here, P CMAX,f,c (i) is, for example, the transmission power of the user terminal set for the carrier f of the serving cell c in the transmission occasion i (also referred to as the maximum transmission power, UE maximum output power, etc.). P O_PUCCH,b,f,c (q u ) is, for example, a parameter related to the target reception power set for the active UL BWP b of the carrier f of the serving cell c in the transmission occasion i (also referred to as a parameter related to the transmission power offset, transmission power offset P0, or target reception power parameter, etc.).

[0039] M PUCCH RB,b,f,c (i) is, for example, the number of resource blocks (bandwidth) allocated to the PUCCH for the transmission occasion i in the active UL BWP b of the carrier f of the serving cell c and the subcarrier spacing μ. PL b,f,c (q dis, for example, the index q of a reference signal for a downlink BWP (pathloss reference RS, pathloss reference RS for pathloss measurement, DL-RS for pathloss measurement, PUCCH-PathlossReferenceRS) associated with the active UL BWP b of carrier f of serving cell c d is the pathloss (pathloss estimation [dB], pathloss compensation) calculated at the user equipment using

[0040] If the UE is not provided with pathloss reference RSs (pathlossReferenceRSs), or before the UE is provided with individual upper layer parameters, the UE calculates the pathloss PL b,f,c (q d ) using the RS resources obtained from the SS / PBCH block used by the UE to acquire the MIB

[0041] If the UE is given pathloss reference RS information (pathlossReferenceRSs within PUCCH power control information (PUCCH-PowerControl)) and is not given PUCCH spatial relation information (PUCCH-SpatialRelationInfo), the UE obtains the value of the reference signal within the PUCCH pathloss reference RS from the PUCCH pathloss reference RS-ID (PUCCH-PathlossReferenceRS-Id) having index 0 within the PUCCH pathloss reference RS information (PUCCH-PathlossReferenceRS). The resource of this reference signal is in either the same serving cell or, if given, on the serving cell indicated by the value of the pathloss reference linking information (pathlossReferenceLinking). The pathloss reference linking information indicates whether the UE applies the DL of either the special cell (SpCell) or the secondary cell (SCell) corresponding to this UL as the pathloss reference. The SpCell may be the primary cell (PCell) in the master cell group (MCG) or the primary secondary cell (PSCell) in the secondary cell group (SCG). The pathloss reference RS information indicates a set of reference signals (e.g., CSI-RS configuration or SS / PBCH block) used for PUCCH pathloss estimation.

[0042] Δ F_PUCCH (F) is a higher layer parameter given for each PUCCH format. Δ TF,b,f,c (i) is the transmission power adjustment component (offset) for the UL BWP b of carrier f of serving cell c.

[0043] g b,f,c(i, l) is a value based on the TPC command of the power control adjustment state index l of the active UL BWP of carrier f in serving cell c and transmission opportunity i (e.g., power control adjustment state, cumulative value of TPC command, value by closed loop, PUCCH power adjustment state). For example, g b,f,c (i, l) may be represented by Equation (4).

[0044]

Number

[0045] Here, δ PUCCH,b,f,c (i, l) is a TPC command value, which is included in DCI format 1_0 or DCI format 1_1 detected by the UE in the PUCCH transmission opportunity i of the active UL BWP b of carrier f in serving cell c, or may be combined with other TPC commands in DCI format 2_2 having a CRC scrambled by a specific RNTI (Radio Network Temporary Identifier) (e.g., TPC-PUSCH-RNTI) and encoded.

[0046] Σ m=0 C(Ci)-1 δ PUCCH,b,f,c (m, l) may be the sum of the TPC command values in a set C of TPC command values having a cardinality C (C i ). C i is a set of TPC command values received by the UE between K i (i - i 0 of the active UL BWP b of carrier f in serving cell c for the PUCCH power control adjustment state l, before the K PUCCH (i - i 0 ) - 1 symbols of the PUSCH transmission opportunity i - i and before the K PUCCH (i) symbols of the PUSCH transmission opportunity i. i 0 is the K 0 of the PUSCH transmission opportunity i - i PUCCH (i - i 0)K is the number of symbols before the symbol for PUSCH transmission opportunity i PUCCH (i) may be the smallest positive integer earlier than the symbol before.

[0047] If the PUCCH transmission is in response to the detection of DCI format 1_0 or DCI format 1_1 by the UE, K PUCCH (i) may be the number of symbols in the active UL BWP b of carrier f of serving cell c that is after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUCCH transmission. If the PUCCH transmission is set by the configured grant configuration information (ConfiguredGrantConfig), K PUSCH (i) is the number of symbols per slot N in the active UL BWP b of carrier f of serving cell c symb slot and is equal to the product of the minimum value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon). PUCCH,min It may be the number of symbols.

[0048] If the UE provides information indicating the use of two PUCCH power control adjustment states (twoPUCCH-PC-AdjustmentStates) and PUCCH spatial relation information (PUCCH-SpatialRelationInfo), l = {0,1}, and if the UE does not provide information indicating the use of two PUCCH power control adjustment states or PUCCH spatial relation information, l = 0 may be used.

[0049] If the UE obtains the TPC command value from DCI format 1_0 or 1_1, and the UE is provided with PUCCH spatial relation information, the UE may obtain the mapping between the PUCCH spatial relation information ID (pucch-SpatialRelationInfoId) value and the closed-loop index (closedLoopIndex, power adjustment state index l) according to the index provided by the P0 ID for PUCCH (p0-PUCCH-Id within p0-Set within PUCCH-PowerControl within PUCCH-Config). If the UE receives an activation command including the value of the PUCCH spatial relation information ID, the UE may determine the value of the closed-loop index that provides the value of l through the link to the corresponding P0 ID for PUCCH.

[0050] If, for the active UL BWP b of carrier f of serving cell c, the UE, for the corresponding PUCCH power adjustment state l, the setting of the P O_PUCCH,b,f,c (q u ) value is provided by the upper layer, then g b,f,c (i, l) = 0, k = 0, 1, …, i. If the UE is provided with PUCCH spatial relation information, the UE may determine the value of l from the value of q u based on the P0 ID for PUCCH corresponding to q, the closed-loop index value corresponding to l, and the PUCCH spatial relation information associated therewith. u

[0051] q u may be the P0 ID for PUCCH (p0-PUCCH-Id) indicating the P0 for PUCCH (P0-PUCCH) within the P0 set for PUCCH (p0-Set).

[0052] ​Note that formulas (3) and (4) are merely examples and are not limited thereto. The user terminal may control the transmission power of PUCCH based on at least one parameter exemplified in formulas (3) and (4), and additional parameters may be included or some parameters may be omitted. Further, in the above formulas (3) and (4), the transmission power of PUCCH is controlled for each active UL BWP of a certain carrier of a certain serving cell, but it is not limited thereto. At least a part of the serving cell, carrier, BWP, and power control adjustment state may be omitted.

[0053] <Transmission Power Control for SRS> For example, using the index l of the power control adjustment state, the transmission power (P SRS、b,f,c (i,q s ,l)) of SRS in the SRS transmission occasion (also referred to as the transmission period, etc.) i for the active UL BWP b of the carrier f of the serving cell c may be represented by the following formula (5). The power control adjustment state may be referred to as a value based on the TPC command of the power control adjustment state index l, a cumulative value of the TPC command, or a value by a closed loop. l may be referred to as a closed loop index.

[0054] Further, the SRS transmission occasion i is a period during which SRS is transmitted, and may be composed of, for example, one or more symbols, one or more slots, etc.

[0055]

Number

[0056] Here, P CMAX,f,c (i) is, for example, the UE maximum output power for the carrier f of the serving cell c in the SRS transmission occasion i. P O_SRS,b,f,c (q s ) is the active UL BWP b of the carrier f of the serving cell c and the SRS resource set q s(Provided by SRS-ResourceSet and SRS-ResourceSetId) and is a parameter related to the target received power provided by p0 (for example, also referred to as a parameter related to the transmission power offset, transmission power offset P0, or target received power parameter, etc.).

[0057] M SRS,b,f,c (i) is the SRS bandwidth represented by the number of resource blocks for the SRS transmission opportunity i on the active UL BWP b of carrier f with serving cell c and subcarrier spacing μ.

[0058] α SRS,b,f,c (q s ) is provided by α (for example, alpha) for the active UL BWP b of carrier f with serving cell c and subcarrier spacing μ, and the SRS resource set q. s And is provided by α (for example, alpha) for the active UL BWP b of carrier f with serving cell c and subcarrier spacing μ, and the SRS resource set q.

[0059] PL b,f,c (q d ) is the DL path loss estimate value [dB] (path loss estimation [dB], path loss compensation) calculated by the UE for the active DL BWP of serving cell c, the SRS resource set q, s And for the RS resource index q d Using. The RS resource index q d Is the path loss reference RS (path loss reference RS, DL-RS for path loss measurement, for example, provided by pathlossReferenceRS) associated with the SRS resource set q s And is the SS / PBCH block index (for example, ssb-Index) or CSI-RS resource index (for example, csi-RS-Index).

[0060] If the UE is not provided with pathloss reference RSs (pathlossReferenceRSs), or before the UE is provided with individual upper layer parameters, the UE calculates the PL using the RS resources obtained from the SS / PBCH block used by the UE to acquire the MIB. b,f,c (q d ) is calculated.

[0061] h b,f,c (i, l) is the SRS power control adjustment state for the active UL BWP of carrier f of serving cell c at SRS transmission opportunity i. If the setting of the SRS power control adjustment state (e.g., srs-PowerControlAdjustmentStates) indicates the same power control adjustment state for SRS transmission and PUSCH transmission, the current PUSCH power control adjustment state f b,f,c (i, l) is used. On the other hand, if the setting of the SRS power control adjustment state indicates independent power control adjustment states for SRS transmission and PUSCH transmission and no setting of TPC accumulation is provided, the SRS power control adjustment state h b,f,c (i) may be represented by Equation (6).

[0062]

Equation

[0063] Here, δ SRS,b,f,c (m) may be the TPC command value encoded in combination with other TPC commands in the PDCCH having DCI (e.g., DCI format 2_3). Σ m=0 C(Si)-1 δ SRS,b,f,c (m) is the set S of TPC command values having cardinality C(S 0 ) that the UE receives between K SRS (i - i 0 ) - 1 symbols before the SRS transmission opportunity i - i and K SRS (i) symbols before the SRS transmission opportunity i on the active UL BWP b of carrier f of serving cell c and subcarrier spacing μ. i )i It may be the sum of the TPC commands inside. Here, i 0 is the K of the SRS transmission opportunity i - i 0 of SRS (i - i 0 ) - 1 symbol before is earlier than before the K SRS (i) symbol of the SRS transmission opportunity i, and may be the smallest positive integer.

[0064] If the SRS transmission is aperiodic, K SRS (i) is the number of symbols in the active UL BWP b of carrier f of serving cell c, after the last symbol of the corresponding PDCCH that triggers the SRS transmission and before the first symbol of the SRS transmission. If the SRS transmission is semi - persistent or periodic, K SRS (i) is equal to the product of the number of symbols per slot N symb slot in the active UL BWP b of carrier f of serving cell c and the minimum value of the value provided by k2 in PUSCH - ConfigCommon. SRS,min It may be the number of symbols.

[0065] Note that the formulas (5) and (6) are merely illustrative and not limited thereto. The user equipment may control the transmission power of the SRS based on at least one of the parameters illustrated in the formulas (5) and (6), and additional parameters may be included or some parameters may be omitted. Also, in the above formulas (5) and (6), the transmission power of the SRS is controlled for each BWP of a certain carrier of a certain cell, but it is not limited thereto. At least a part of the cell, carrier, BWP, and power control adjustment state may be omitted.

[0066] (TCI, spatial relation, QCL) In NR, it is being considered to control at least one of signal and channel (referred to as signal / channel) in a UE, such as reception processing (e.g., at least one of reception, demapping, demodulation, and decoding), transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) based on a Transmission Configuration Indication state (TCI state).

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

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

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

[0070] Note that the spatial reception parameter may correspond to the reception beam (e.g., reception analog beam) of the UE, and the beam may be specified based on spatial QCL. The QCL (or at least one element of QCL) in the present disclosure may be read as sQCL (spatial QCL).

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

[0072] The UE's assumption that a given control resource set (Control Resource Set (CORESET)), channel, or reference signal is in a relationship with a specific QCL (e.g., QCL type D) with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

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

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

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

[0077] The physical layer signaling may be, for example, Downlink Control Information (DCI).

[0078] The channel for which the TCI state or spatial relation is set (specified) may be, for example, at least one of Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), and Physical Uplink Control Channel (PUCCH).

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

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

[0081] The UE may receive configuration information (e.g., PDSCH-Config, tci-StatesToAddModList) including a list of information elements of the TCI state by upper layer signaling.

[0082] The information element of the TCI state (the "TCI-state IE" in RRC) configured by upper layer signaling may include a TCI state ID and one or more QCL information ("QCL-Info"). The QCL information may include at least one of information related to the RS having a QCL relationship (RS relationship information) and information indicating a QCL type (QCL type information). The RS relationship information may include information such as an index of the RS (e.g., an SSB index, a Non-Zero-Power (NZP) CSI-RS resource ID (Identifier)), an index of the cell where the RS is located, and an index of the Bandwidth Part (BWP) where the RS is located.

[0083] In Rel.15 NR, as at least one TCI state of PDCCH and PDSCH, both the RS of QCL type A and the RS of QCL type D, or only the RS of QCL type A can be configured for the UE.

[0084] When the TRS is configured as the RS of QCL type A, unlike the demodulation reference signal (DMRS) of PDCCH or PDSCH, it is assumed that the same TRS is transmitted periodically over a long period of time. The UE can measure the TRS and calculate the average delay, delay spread, etc.

[0085] For the UE configured with the TRS as the RS of QCL type A in the TCI state of the DMRS of PDCCH or PDSCH, since it can be assumed that the QCL type A parameters (average delay, delay spread, etc.) of the DMRS of PDCCH or PDSCH and the TRS are the same, the type A parameters (average delay, delay spread, etc.) of the DMRS of PDCCH or PDSCH can be obtained from the measurement result of the TRS. When performing at least one channel estimation of PDCCH and PDSCH, the UE can use the measurement result of the TRS to perform more accurate channel estimation.

[0086] For the UE configured with the RS of QCL type D, the UE receive beam (spatial domain receive filter, UE spatial domain receive filter) can be determined using the RS of QCL type D.

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

[0088] <TCI state for PDCCH> Information regarding QCL between a PDCCH (or a DMRS antenna port related to the PDCCH) and a certain RS may be referred to as, for example, a TCI state for the PDCCH.

[0089] The UE may determine a TCI state for a UE-specific PDCCH (CORESET) based on upper layer signaling. For example, for each CORESET, one or more (K) TCI states may be configured for the UE by RRC signaling.

[0090] For each CORESET, the UE may activate one of the multiple TCI states configured by RRC signaling by means of a MAC CE. The said MAC CE may be referred to as a TCI State Indication for UE-specific PDCCH MAC CE. The UE may monitor a CORESET based on the active TCI state corresponding to the CORESET.

[0091] <TCI state for PDSCH> Information regarding QCL between a PDSCH (or a DMRS antenna port related to the PDSCH) and a certain DL-RS may be referred to as, for example, a TCI state for the PDSCH.

[0092] The UE may be notified (configured) by upper layer signaling of M (M≥1) TCI states for the PDSCH (M QCL information for the PDSCH). Note that the number M of TCI states configured for the UE may be restricted by at least one of the UE capability and the QCL type.

[0093] The DCI used for PDSCH scheduling may include a predetermined field (which may be referred to as, for example, a TCI field, a TCI state field, etc.) indicating the TCI state for the PDSCH. The DCI may be used for scheduling the PDSCH of one cell and may be referred to as, for example, DL DCI, DL assignment, DCI format 1_0, DCI format 1_1, etc.

[0094] Whether the TCI field is included in the DCI may be controlled by information notified from the base station to the UE. The information may be information indicating whether the TCI field exists in the DCI (present or absent) (for example, TCI presence information, TCI presence information in DCI, upper layer parameter TCI-PresentInDCI). The information may be set for the UE by, for example, upper layer signaling.

[0095] When more than eight types of TCI states are set for the UE, the TCI states of eight types or less may be activated (or specified) using a MAC CE. The MAC CE may be referred to as a TCI States Activation / Deactivation for UE-specific PDSCH MAC CE. The value of the TCI field in the DCI may indicate one of the TCI states activated by the MAC CE.

[0096] When the UE is set with TCI presence information set to "enabled" for a CORESET for scheduling the PDSCH (the CORESET used for PDCCH transmission for scheduling the PDSCH), the UE may assume that the TCI field exists in the DCI format 1_1 of the PDCCH transmitted on the CORESET.

[0097] For a CORESET that schedules the PDSCH, when the TCI presence information is not set, or when the PDSCH is scheduled by DCI format 1_0, if the time offset between the reception of the DL DCI (the DCI that schedules the PDSCH) and the reception of the PDSCH corresponding to the DCI is greater than or equal to the threshold, the UE may assume that the TCI state or QCL assumption for the PDSCH is the same as the TCI state or QCL assumption applied to the CORESET used for the PDCCH transmission that schedules the PDSCH, in order to determine the QCL of the PDSCH antenna port.

[0098] When the TCI presence information is set to "enabled", the TCI field in the DCI within the component carrier (CC) that schedules (the PDSCH) indicates the activated TCI state within the scheduled CC or DL BWP, and when the PDSCH is scheduled by DCI format 1_1, the UE may use the TCI according to the value of the TCI field in the detected PDCCH with the DCI to determine the QCL of the PDSCH antenna port. If the time offset between the reception of the DL DCI (that schedules the PDSCH) and the PDSCH corresponding to the DCI (the PDSCH scheduled by the DCI) is greater than or equal to the threshold, the UE may assume that the DM-RS port of the PDSCH of the serving cell is QCL with the RS within the TCI state regarding the QCL type parameter given by the indicated TCI state.

[0099] When the UE configures a single-slot PDSCH, the indicated TCI state may be based on the activated TCI state within the slot having the scheduled PDSCH. When the UE configures a multi-slot PDSCH, the indicated TCI state may be based on the activated TCI state within the first slot having the scheduled PDSCH, and the UE may expect to be the same across the slots having the scheduled PDSCH. When the UE configures a CORESET associated with a search space set for cross-carrier scheduling, if for the CORESET, the TCI presence information is set to "valid", and at least one of the TCI states configured for the serving cell scheduled by the search space set includes QCL type D, the UE may assume that the time offset between the detected PDCCH and the PDSCH corresponding to the PDCCH is greater than or equal to a threshold value.

[0100] In RRC connected mode, in both the case where the TCI information in DCI (higher layer parameter TCI-PresentInDCI) is set to "enabled" and the case where the TCI information in DCI is not set, if the time offset between the reception of the DL DCI (the DCI that schedules the PDSCH) and the corresponding PDSCH (the PDSCH scheduled by the DCI) is less than a threshold value, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are the RS and QCL regarding the QCL parameters used for the QCL indication of the PDCCH of the CORESET having the minimum (lowest) CORESET-ID in the latest (most recent, latest) slot within the active BWP of the serving cell where one or more CORESETs are monitored by the UE and are associated with the monitored search space (Figure 1). This RS may also be referred to as the default TCI state of the PDSCH or the default QCL assumption of the PDSCH.

[0101] The time offset between receiving a DL DCI and receiving a PDSCH corresponding to the DCI may be referred to as a scheduling offset.

[0102] Also, the above threshold may be referred to as a QCL time duration, "timeDurationForQCL", "Threshold", "Threshold for offset between a DCI indicating a TCI state and a PDSCH scheduled by the DCI", "Threshold-Sched-Offset", a scheduling offset threshold, a schedule offset threshold, etc.

[0103] The QCL time duration may be based on UE capabilities, for example, based on the delay for PDCCH decoding and beam switching. The QCL time duration may be the minimum time required for the UE to perform PDCCH reception and apply the spatial QCL information received within the DCI for PDSCH processing. The QCL time duration may be represented by the number of symbols per subcarrier spacing, or may be represented by time (e.g., μs). The information on the QCL time duration may be reported from the UE to the base station as UE capability information, or may be set for the UE by the base station using higher layer signaling.

[0104] For example, the UE may assume that the DMRS port of the above PDSCH is QCL with the DL-RS based on the TCI state activated for the CORESET corresponding to the above minimum CORESET-ID. The latest slot may be, for example, the slot for receiving the DCI that schedules the above PDSCH.

[0105] Note that the CORESET-ID may be an ID (controlResourceSetId for identifying the CORESET) set by the RRC information element "ControlResourceSet".

[0106] If no CORESET is configured for a CC, the default TCI state may be the activated TCI state that is applicable to the PDSCH within the active DL BWP of the CC and has the lowest ID.

[0107] In releases after Rel.16, in the case where the PDSCH and the PDCCH that schedules it are in different component carriers (CCs) (cross-carrier scheduling), if the delay from the PDCCH to the PDSCH (PDCCH-to-PDSCH delay) is shorter than the QCL time duration, or if the TCI state is not present in the DCI for the scheduling, the UE may obtain the QCL assumption for the scheduled PDSCH from the active TCI state that is applicable to the PDSCH within the active BWP of the scheduled cell and has the lowest ID.

[0108] <Spatial relation for PUCCH> The UE may be configured with parameters (PUCCH configuration information, PUCCH-Config) used for PUCCH transmission by upper layer signaling (e.g., Radio Resource Control (RRC) signaling). The PUCCH configuration information may be configured for each partial band (e.g., uplink bandwidth part (Bandwidth Part (BWP))) within a carrier (also referred to as a cell or a component carrier (Component Carrier (CC))).

[0109] The PUCCH configuration information may include a list of PUCCH resource set information (e.g., PUCCH-ResourceSet) and a list of PUCCH spatial relation information (e.g., PUCCH-SpatialRelationInfo).

[0110] The PUCCH resource set information may include a list (e.g., resourceList) of PUCCH resource indices (IDs, e.g., PUCCH-ResourceId).

[0111] Also, when the UE does not have the individual PUCCH resource configuration information (e.g., dedicated PUCCH resource configuration) provided by the PUCCH resource set information in the PUCCH configuration information (before RRC setup), the UE may determine a PUCCH resource set based on the parameters (e.g., pucch-ResourceCommon) in the system information (e.g., System Information Block Type1 (SIB1) or Remaining Minimum System Information (RMSI)). The PUCCH resource set may include 16 PUCCH resources.

[0112] On the other hand, when the UE has the above individual PUCCH resource configuration information (UE-specific uplink control channel configuration, dedicated PUCCH resource configuration) (after RRC setup), the UE may determine a PUCCH resource set according to the number of UCI information bits.

[0113] The UE may determine one PUCCH resource (index) within the above PUCCH resource set (e.g., cell-specific or UE-specific determined PUCCH resource set) based on at least one of the value of a predetermined field (e.g., PUCCH resource indicator field) in the downlink control information (Downlink Control Information (DCI)) (e.g., DCI format 1_0 or 1_1 used for scheduling of the PDSCH), the number of CCEs (N CCE ) in the control resource set (COntrol REsource SET (CORESET)) for receiving the PDCCH carrying the DCI, and the index (n CCE,0 ) of the first CCE of the PDCCH reception.

[0114] PUCCH spatial relation information (e.g., "PUCCH-spatialRelationInfo" in the RRC information element) may indicate multiple candidate beams (spatial domain filters) for PUCCH transmission. The PUCCH spatial relation information may indicate the spatial association between the RS (Reference signal) and the PUCCH.

[0115] The list of PUCCH spatial relation information may include several elements (PUCCH spatial relation information IE (Information Element)). Each PUCCH spatial relation information may include, for example, at least one of the index (ID, e.g., pucch-SpatialRelationInfoId) of the PUCCH spatial relation information, the index (ID, e.g., servingCellId) of the serving cell, and information regarding the RS (Reference RS) that has a spatial relation with the PUCCH.

[0116] For example, the information regarding the RS may be the SSB index, the CSI-RS index (e.g., NZP-CSI-RS resource configuration ID), or the SRS resource ID and the ID of the BWP. The SSB index, the CSI-RS index, and the SRS resource ID may be associated with at least one of the beam, resource, and port selected by the measurement of the corresponding RS.

[0117] When more than one piece of spatial relation information regarding the PUCCH is configured for the UE, the UE may control such that one piece of PUCCH spatial relation information becomes active for one PUCCH resource at a certain time based on the PUCCH spatial relation Activation / Deactivation MAC CE (PUCCH spatial relation Activation / Deactivation MAC CE).

[0118] The PUCCH spatial relation Activation / Deactivation MAC CE of Rel.15 NR is represented by a total of 3 octets (8 bits × 3 = 24 bits) in octets 1 - 3.

[0119] The MAC CE may include information such as the serving cell ID to which it applies (“Serving Cell ID” field), BWP ID (“BWP ID” field), PUCCH resource ID (“PUCCH Resource ID” field).

[0120] Also, the MAC CE includes fields of “S i ” (i = 0 - 7). When the field of a certain S i indicates 1, the UE activates the spatial relation information of spatial relation information ID#i. When the field of a certain S i indicates 0, the UE deactivates the spatial relation information of spatial relation information ID#i.

[0121] The UE may activate the PUCCH relation information specified by the MAC CE 3 ms after transmitting an acknowledgement (ACK) to the MAC CE that activates the predetermined PUCCH spatial relation information.

[0122] <Spatial relation for SRS, PUSCH> The UE may receive information used for transmitting a measurement reference signal (e.g., Sounding Reference Signal (SRS)), such as SRS configuration information (e.g., parameters in “SRS-Config” of the RRC control element).

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

[0124] One SRS resource set may be associated with 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 identifier (SRS Resource Indicator (SRI)) or an SRS resource ID (Identifier).

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

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

[0127] 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-based transmission (codebook: CB), non-codebook-based transmission (nonCodebook: NCB), antenna switching, etc. The SRS for the usage of codebook-based transmission or non-codebook-based transmission may be used for determining the precoder of codebook-based or non-codebook-based PUSCH transmission based on the SRI.

[0128] For example, in the case of codebook-based transmission, the UE may determine a 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 a precoder for PUSCH transmission based on the SRI.

[0129] The SRS resource information may include the SRS-ResourceId, the number of SRS ports, the SRS port numbers, 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 relation information of the SRS, etc.

[0130] The spatial relation information of the SRS (e.g., the "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 also be referred to as a Synchronization Signal Block (SSB).

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

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

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

[0134] In NR, the transmission of the uplink signal may be controlled based on the presence or absence of Beam Correspondence (BC). BC may be, for example, the ability of a certain node (e.g., a base station or a UE) to determine the beam (transmission beam, Tx beam) used for signal transmission based on the beam (reception beam, Rx beam) used for signal reception.

[0135] Note that BC may be referred to as transmission / reception beam correspondence, beam reciprocity, beam calibration, calibrated / non-calibrated, reciprocity calibrated / non-calibrated, correspondence, consistency, etc.

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

[0137] On one hand, when there is BC, the UE may transmit an uplink signal (e.g., PUSCH, PUCCH, SRS, etc.) using the same or corresponding beam (spatial domain transmission filter) as the beam (spatial domain reception filter) used for receiving a predetermined SSB or CSI-RS (or CSI-RS resource).

[0138] For a certain SRS resource, when the UE is configured with spatial relationship information regarding an SSB or CSI-RS and the SRS (e.g., when there is BC), 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.

[0139] For a certain SRS (target SRS) resource, when the UE is configured with spatial relationship information regarding another SRS (reference SRS) and the SRS (target SRS) (e.g., when there is no BC), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmission filter) as the spatial domain filter (spatial domain transmission filter) for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmission beam of the reference SRS and the UE transmission beam of the target SRS are the same.

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

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

[0142] Note that for the spatial relationship of the SRS resource used for PUSCH, DL-RS can be configured. For example, for SP-SRS, the UE can have the spatial relationships of a plurality (e.g., up to 16) of SRS resources configured by RRC, and one of the plurality of SRS resources can be indicated by a MAC CE.

[0143] (Default spatial relationship) The default spatial relationship is being considered. If in a certain frequency range (e.g., frequency range (FR) 2), for individual PUCCH (PUCCH based on individual PUCCH configuration (PUCCH-Config)) or individual SRS (SRS based on individual SRS configuration (SRS-Config)), excluding SRS with beam management usage ('usage='beamManagement')), the spatial relationship information is not configured, then for the individual PUCCH configuration or individual SRS configuration, in at least certain cases, the default spatial relationship may be applied. The certain case may be a case where the path loss reference RS is not configured by RRC signaling.

[0144] For example, in the case where a CORESET is configured on a CC, the default spatial relationship may be the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used for path loss calculation may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used for path loss calculation may be a periodic RS.

[0145] For example, in a case where no CORESET is configured on a CC, the default spatial relation may be the activated TCI state with the lowest ID applicable to the PDSCH within the active DL-BWP of the CC.

[0146] The default spatial relation may be applied to a UE that supports beam correspondence. The default spatial relation may be applied to a single TRP case.

[0147] When no path loss reference RS is configured, the RS used for path loss calculation may be referred to as the default path loss reference RS.

[0148] (Spatial relation of PUSCH scheduled by DCI format 0_0) In Rel.15 NR, for a PUSCH on a cell scheduled by DCI format 0_0, the UE transmits the PUSCH according to the spatial relation corresponding to the dedicated PUCCH resource with the lowest ID (within the active UL BWP) in the active UL BWP of the cell, if available. The dedicated PUCCH resource may be a PUCCH resource configured individually for the UE (configured by the higher layer parameter PUCCH-Config).

[0149] DCI format 0_1 includes an SRI, while DCI format 0_0 does not include an SRI.

[0150] Therefore, for a cell where no PUCCH resource is configured (e.g., a secondary cell (SCell)), PUSCH cannot be scheduled by DCI format 0_0.

[0151] When PUCCH on SCell (PUCCH transmitted on SCell) is not configured, UCI is transmitted on the PCell. When PUCCH on SCell is configured, UCI is transmitted on the PUCCH-SCell. Therefore, PUCCH resources and spatial relation information are not required to be configured for all SCell, and there may be cells for which PUCCH resources are not configured.

[0152] Also, DCI format 0_1 includes a carrier indicator field (CIF), while DCI format 0_0 does not include the CIF. Therefore, even if PUCCH resources are configured for the PCell, cross-carrier scheduling of PUSCH on the SCell cannot be performed by DCI format 0_0 on the PCell.

[0153] In Rel.15 NR, RRC connected mode, frequency range (FR) 2, the UE does not expect a PUSCH scheduled by DCI format 0_0 within the BWP without being configured with a PUCCH resource having PUCCH spatial relation information.

[0154] The following functions 1 and 2 are being considered for the PUSCH scheduled by DCI format 0_0.

[0155] [Function 1] In FR2 and RRC connected mode, when there is no PUCCH resource configured on the CC, the default spatial relation and default path loss reference RS of the PUSCH scheduled by DCI format 0_0 are supported. This function 1 may be applied to UEs that support the function of default spatial relation for individual PUCCH or individual SRS in Rel.16, or may be applied when a UE that supports the function of default spatial relation for individual PUCCH or individual SRS in Rel.16 is configured by the base station.

[0156] RRC parameters may be introduced to enable the function of default spatial relation for individual PUCCH or individual SRS. The default spatial relation may be the TCI state or QCL assumption of the CORESET with the lowest ID. The default path loss reference RS may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID. The default path loss reference RS may be a periodic RS.

[0157] [Function 2] In FR2 and RRC connected mode, it is supported to schedule PUSCH by DCI format 0_0 on the CC with the configured PUCCH resource. Here, none of all the configured PUCCH resources are configured with spatial relation.

[0158] For the PUSCH scheduled by DCI format 0_0, the spatial relation and path loss reference RS may respectively follow those of the spatial relation and path loss reference RS for the PUCCH resource. For the PUSCH scheduled by DCI format 0_0, the spatial relation and path loss reference RS for the PUCCH resource may respectively be the default spatial relation and default path loss reference RS for the PUCCH resource.

[0159] Function 1 deals with the case where no PUCCH resource is configured, and Function 2 deals with the case where a PUCCH resource is configured and no spatial relation is configured. The cell (CC) targeted by Function 2 is the PCell or PUCCH-SCell, and it is assumed that a PUCCH resource is configured. When the network uses the function of default spatial relation, it is conceivable that no spatial relation is configured for the PUCCH resource. The cells targeted by Function 1 are cells other than the PCell and PUCCH-SCell, and no PUCCH resource is configured.

[0160] (Problem) It is conceivable that no spatial relationship is set for some of the set plurality of PUCCH resources. As described above, in Rel.15 NR, since the spatial relationship of the lowest PUCCH resource ID is used, the spatial relationship in this case is not clear. Also, it is not clear which PUCCH resource in the cell is used. If the spatial relationship is not clear, there is a risk of degrading system performance, such as a throughput reduction.

[0161] When the path loss reference RS is not set and no CORESET is set on the CC, the RS used for path loss calculation is not clear. If the RS used for path loss calculation is not clear, there is a risk of degrading system performance, such as a throughput reduction.

[0162] Therefore, the inventors have conceived a method for appropriately determining a reference signal for at least one of QCL and path loss calculation for uplink transmission.

[0163] 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 alone or in combination.

[0164] In the present disclosure, cell, CC, carrier, BWP, band may be read interchangeably with each other.

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

[0166] In the present disclosure, specific UL transmission, specific UL signal, specific type of UL transmission, specific UL channel, PUSCH, PUCCH, SRS, P-SRS, SP-SRS, A-SRS may be read interchangeably with each other. In the present disclosure, specific DL signal, specific DL resource, specific type of DL transmission, specific DL transmission, specific DL reception, specific DL channel, PDSCH, PDCCH, CORESET, DL-RS, SSB, CSI-RS may be read interchangeably with each other.

[0167] The TCI state, the TCI state, or the QCL assumption, the QCL assumption, the QCL parameter, the spatial domain reception filter, the UE spatial domain reception filter, the spatial domain filter, the UE reception beam, the DL reception beam, the DL precoding, the DL precoder, the DL-RS, the RS of QCL type D of the TCI state or QCL assumption, the RS of QCL type A of the TCI state or QCL assumption, may be read interchangeably with each other. The RS of QCL type D, the DL-RS associated with QCL type D, the DL-RS having QCL type D, the source of the DL-RS, the SSB, the CSI-RS, may be read interchangeably with each other.

[0168] In the present disclosure, the TCI state may be information (such as DL-RS, QCL type, the cell where the DL-RS is transmitted, etc.) regarding the reception beam (spatial domain reception filter) instructed (set) for the UE. The QCL assumption may be information (such as DL-RS, QCL type, the cell where the DL-RS is transmitted, etc.) regarding the reception beam (spatial domain reception filter) assumed by the UE based on the transmission or reception of the associated signal (such as PRACH).

[0169] In the present disclosure, the latest slot, the most recent slot, the latest search space, the most recent search space, may be read interchangeably with each other. In the present disclosure, the lowest ID, the highest ID, the predetermined (specific) ID, may be read interchangeably with each other. For example, the CORESET having the lowest ID, the CORESET having the highest ID, the CORESET having the predetermined ID, may be read interchangeably with each other. For example, the active TCI state having the lowest ID, the active TCI state having the highest ID, the active TCI state having the predetermined ID, may be read interchangeably with each other.

[0170] In the present disclosure, spatial relationship, spatial relationship information, spatial relationship assumption, QCL parameter, spatial domain transmission filter, UE spatial domain transmission filter, spatial domain filter, UE transmission beam, UL transmission beam, UL precoding, UL precoder, spatial relationship RS, DL-RS, QCL assumption, SRI, spatial relationship based on SRI, UL TCI may be read interchangeably with each other.

[0171] In the present disclosure, default TCI state, default QCL, default QCL assumption may be read interchangeably with each other. Hereinafter, this TCI state or QCL (QCL assumption) is mainly referred to as the default TCI state, but the name is not limited thereto. Note that the definition of the default TCI state is not limited to this. The default TCI state may be, for example, a TCI state assumed when the TCI state / QCL specified by DCI is not available for a certain channel / signal (e.g., PDSCH), or a TCI state assumed when the TCI state / QCL is not specified (or set).

[0172] In the present disclosure, default spatial relationship, default spatial relationship assumption, RS of QCL for a specific DL resource, TCI state or QCL assumption of a specific DL resource, TCI state or QCL assumption of a specific DL signal, RS regarding QCL parameter given by the TCI state or QCL assumption of a specific DL signal, RS of QCL type D in the TCI state or QCL assumption of a specific DL signal, spatial relationship of reference UL transmission may be read interchangeably with each other.

[0173] In the present disclosure, TRS, CSI-RS for tracking, CSI-RS having TRS information (higher layer parameter trs-Info), NZP-CSI-RS resources in the NZP-CSI-RS resource set having TRS information may be read interchangeably with each other.

[0174] In the present disclosure, DCI format 0_0, DCI not including SRI, DCI not including an indication of spatial relationship, DCI not including CIF, may be mutually interchangeable. In the present disclosure, DCI format 0_1, DCI including SRI, DCI including an indication of spatial relationship, DCI including CIF, may be mutually interchangeable.

[0175] In the present disclosure, pathloss reference RS, RS for pathloss reference, RS for pathloss estimation, RS for pathloss calculation, pathloss(PL)-RS, index q d , RS used for pathloss calculation, RS resource used for pathloss calculation, calculation RS, may be mutually interchangeable. Calculation, estimation, measurement, may be mutually interchangeable.

[0176] In the present disclosure, "The UE transmits a specific UL transmission according to the default spatial relationship", "The UE uses the default spatial relationship for the spatial relationship of the specific UL transmission", "The UE assumes (considers) that the spatial relationship of the specific UL transmission is the same as the RS of the default spatial relationship", "The UE assumes (considers) that the spatial relationship of the specific UL transmission is the same as the RS of QCL type D of the default spatial relationship", may be mutually interchangeable.

[0177] (Wireless communication method) 《Default spatial relationship application conditions》 If the default spatial relationship application conditions are satisfied, the UE may apply the default spatial relationship to the spatial relationship of the specific UL transmission. The specific UL transmission may be at least one of PUSCH, PUCCH, SRS, P-SRS, SP-SRS, A-SRS.

[0178] The default spatial relationship application conditions may be obtained by the logical sum of a plurality of default spatial relationship application conditions, or may be obtained by the logical product of a plurality of default spatial relationship application conditions, or may be obtained by a combination of the logical sum and logical product of a plurality of default spatial relationship application conditions.

[0179] The specific UL transmission may be within a specific frequency range (e.g., frequency range (FR) 2), or it may be a UL transmission based on an individual PUCCH setting or an individual SRS setting excluding an SRS having a beam management usage (usage='beamManagement') and an SRS having a non-codebook-based transmission usage (usage='nonCodebook') with a setting of an associated CSI-RS (associatedCSI-RS). The specific UL transmission may be a PUSCH scheduled by DCI format 0_0. For example, the specific UL transmission may be a PUSCH on the cell scheduled by DCI format 0_0 when there is no PUCCH resource (e.g., a dedicated PUCCH resource) having a spatial relationship (e.g., an active spatial relationship) set within the active UL BWP of the cell. The specific UL transmission may be an SRS based on SRS resources spanning multiple slots within an SRS resource set for antenna switching usage (usage='antennaSwitching').

[0180] The default spatial relationship application conditions may include at least one of the following: that spatial relationship information for the specific UL transmission is not set, that the specific UL transmission is within a frequency range (e.g., frequency range (FR) 2), that the specific UL transmission is based on an individual PUCCH setting or an individual SRS setting excluding an SRS having a beam management usage (usage='beamManagement') and an SRS having a non-codebook-based transmission usage (usage='nonCodebook') with a setting of an associated CSI-RS (associatedCSI-RS), and that the UE supports beam correspondence. The spatial relationship information for the specific UL transmission may be the spatial relationship information within an individual PUCCH setting or an individual SRS setting. The associated CSI-RS may be the ID (index) of the CSI-RS resource associated with the SRS resource set in non-codebook-based transmission.

[0181] The default spatial relation application conditions may include that the path loss reference RS is not set for a specific UL transmission. The default spatial relation application conditions may include that the path loss reference RS is not set by upper layer signaling for a specific UL transmission.

[0182] The default spatial relation application conditions may include that only one TCI state is active for the PDCCH (the number of active TCI states for the PDCCH is 1). According to this default spatial relation application condition, the UE operation becomes simpler.

[0183] The default spatial relation application conditions may include that only one TCI state is active for the PDCCH and the PDSCH (the number of active TCI states for the PDCCH and the PDSCH is 1). When using a single active beam for UL and DL, the UE operation becomes simpler.

[0184] The default spatial relation application conditions may include that the PDCCH and the PUCCH scheduled by the PDCCH are in the same BWP or the same CC (cross-carrier scheduling is not used). In the case of cross-carrier scheduling, the UE may not be able to apply the same beam to the PDCCH and the PUCCH. Therefore, excluding cross-carrier scheduling simplifies the UE operation. For example, in the case of inter-band carrier aggregation (CA), different beams may be applied to the PDCCH and the PUCCH. Also, for example, in the case of FR1-FR2 CA, if the DCI is in FR1 and the PUCCH or SRS or PUSCH is in FR2, it is considered that the UE may not be able to determine the beam.

[0185] The default spatial relation application conditions may include that inter-band CA is not used.

[0186] The default spatial relation application conditions may include the absence of an SRI for a specific UL transmission of PUSCH. The default spatial relation application conditions may include the absence of an SRS resource corresponding to the SRI for PUSCH.

[0187] The default spatial relation application conditions may include that spatial relation information is not set for at least one SRS resource within the SRS resource set.

[0188] The default spatial relation may be the RS of the QCL of a specific DL resource. The RS of the QCL of a specific DL resource, the RS regarding the QCL parameters of a specific DL resource, the RS of the QCL for a specific DL resource, the RS of QCL type D for a specific DL resource, may be mutually interchangeable.

[0189] The RS of the default spatial relation may be the RS of QCL type D or the RS of QCL type A, or may be the RS of QCL type D or the RS of QCL type A if applicable.

[0190] The specific DL resource may be the latest slot for a specific UL transmission. The latest slot may be the latest slot for the start symbol of a specific UL transmission (or the slot before that symbol). The latest slot may be the latest slot for the first or last symbol of the DL signal corresponding to a specific UL transmission (the slot before that symbol). For example, if the specific UL transmission is PUCCH, the DL signal corresponding to the specific UL transmission may be the PDSCH corresponding to the PUCCH (the PDSCH corresponding to the HARQ-ACK carried on the PUCCH).

[0191] If a path loss reference signal (path loss reference RS) is not configured for a specific uplink transmission (when the default path loss reference RS application condition for the specific uplink transmission is satisfied), the UE may determine a reference signal (e.g., default path loss reference RS, calculated RS) used for path loss calculation based on at least one quasi-collocation (QCL) parameter corresponding to at least one specific DL resource (e.g., specific CORESET, specific PDCCH, specific SSB), and calculate the path loss.

[0192] 《Default spatial relation》 The default spatial relation may be the QCL RS of a specific DL resource.

[0193] The QCL RS of a specific DL resource, the default TCI state or default QCL assumption of a specific DL resource, the TCI state of the CORESET with the lowest CORESET ID in the most recent slot, the lowest CORESET-ID in the most recent slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE, the RS related to the QCL parameter used for the QCL indication of the PDCCH of the CORESET associated with the monitored search space, the TCI state or QCL assumption of the CORESET with the lowest CORESET-ID in the most recent slot and associated with the monitored search space, the TCI state or QCL assumption of the CORESET with the lowest CORESET-ID in a specific slot and associated with the monitored search space, the TCI state or QCL assumption of a specific CORESET, the TCI state or QCL assumption of the DL signal corresponding to a specific UL transmission (e.g., the DL channel that triggers a specific UL transmission, the DL channel that schedules a specific UL transmission, the DL channel that schedules the DL channel corresponding to a specific UL transmission), the RS related to the QCL parameter of a specific DL resource, the QCL RS for a specific DL resource, may be mutually interchangeable.

[0194] The RS for the default spatial relation or the default TCI state or the default QCL assumption may be the RS for QCL type D or the RS for QCL type A, or, if applicable, the RS for QCL type D or the RS for QCL type A.

[0195] The latest slot may be the latest slot for a specific DL resource. The latest slot may be the latest slot for (or before) the start symbol of a specific UL transmission. The latest slot may be the latest slot for (before) the first or last symbol of the DL signal corresponding to a specific UL transmission. For example, if the specific UL transmission is PUCCH, the DL signal corresponding to the specific UL transmission may be the PDSCH corresponding to the PUCCH (the PDSCH corresponding to the HARQ-ACK carried on the PUCCH).

[0196] The spatial relation of a specific UL transmission may be the default QCL of the PDSCH.

[0197] When a CORESET is configured on a CC to which the default spatial relation applies, the default QCL of the PDSCH may be the TCI state corresponding to the most recent slot or the lowest CORESET ID of the most recent search space. When no CORESET is configured on the CC to which the default spatial relation applies, the default QCL of the PDSCH may be applicable to the PDSCH within the active DL BWP of the CC and be the activated TCI state with the lowest ID.

[0198] The specific DL resource may be a PDSCH.

[0199] The default spatial relation may be one of the active TCI states (activated TCI states) of the CORESET.

[0200] Multiple TCI states may be active for a CORESET. In this case, the active TCI state selected as the default spatial relation may be the default RS, or it may be the default TCI state or the default QCL assumption.

[0201] The specific DL resource may be a PDCCH.

[0202] When a specific UL transmission corresponds to a PDCCH (aperiodic PDCCH or aperiodic SRS) (when the specific UL transmission is scheduled or triggered by a PDCCH (DL DCI) for scheduling of a PDSCH), the spatial relation of the specific UL transmission may be the TCI state of the PDCCH. The specific UL transmission may be an A-SRS triggered by the PDCCH, or it may be a PUCCH carrying a HARQ-ACK for a PDSCH scheduled by the PDCCH. For example, when the specific UL transmission is an A-SRS, the PDCCH corresponding to the specific UL transmission may be the PDCCH that triggers the A-SRS. Also, for example, when the specific UL transmission is a PUCCH carrying a HARQ-ACK, the PDCCH corresponding to the specific UL transmission may be the PDCCH that schedules the PDSCH and indicates the timing of the HARQ-ACK of the PDSCH. When the specific UL transmission does not correspond to a PDCCH, the spatial relation of the specific UL transmission may be the same as A-1 described above.

[0203] The specific DL resource may be a PDCCH or a PDSCH.

[0204] The default spatial relation may be the QCL assumption of CORESET#0 (the CORESET having an ID of 0).

[0205] The specific DL resource may be CORESET#0.

[0206] The spatial relationship of a specific UL transmission may be the RS used for the path loss calculation in Rel.15 (the RS for Rel.15 calculation, the TCI state of the RS used for the path loss calculation). The RS used for the path loss calculation, the RS resource used for the path loss calculation, the calculated RS, and the default path loss reference RS may be mutually interchangeable.

[0207] The calculated RS may be the RS resource obtained from the SS / PBCH block used by the UE to acquire the MIB.

[0208] The calculated RS may be the path loss reference RS having index 0 in the path loss reference RS information (list of path loss reference RSs). For example, if the UE is given path loss reference RS information (pathlossReferenceRSs in PUCCH power control information (PUCCH-PowerControl)) and not given PUCCH spatial relationship information (PUCCH-SpatialRelationInfo), the calculated RS may be the reference signal in the PUCCH path loss reference RS from the PUCCH path loss reference RS-ID (PUCCH-PathlossReferenceRS-Id) having index 0 in the PUCCH path loss reference RS information (PUCCH-PathlossReferenceRS).

[0209] <Embodiment 1> It may be supported to schedule the PUSCH by DCI format 0_0 on the CC having the configured PUCCH resource. Among the configured PUCCH resources, the PUCCH resource having the lowest ID may not have a spatial relationship (the PUCCH resource having the lowest ID may not be configured with a spatial relationship).

[0210] In FR2 and RRC connected mode, it may be supported to schedule PUSCH by DCI format 0_0 on a CC having a configured PUCCH resource. Among the configured PUCCH resources, the PUCCH resource having the lowest ID may not have a spatial relationship.

[0211] In FR2 and RRC connected mode, it may be supported to schedule PUSCH by DCI format 0_0 within the active UL BWP of a CC having a configured PUCCH resource. Among the configured PUCCH resources of the active UL BWP, the PUCCH resource having the lowest ID may not have a spatial relationship.

[0212] The condition for supporting scheduling of PUSCH by DCI format 0_0 may include that no path loss reference RS is configured for the PUSCH.

[0213] The spatial relationship for a PUSCH scheduled by DCI format 0_0 may follow the spatial relationship for a PUCCH resource (for example, the PUCCH resource having the lowest ID) or the default spatial relationship. For a PUSCH scheduled by DCI format 0_0, the RS used for path loss calculation may follow the path loss reference RS for a PUCCH resource (for example, the PUCCH resource having the lowest ID) or the default path loss reference RS.

[0214] For example, as shown in FIG. 2, when the PUCCH resource having the lowest ID is configured without spatial relationship information (S10: Y), PUSCH can be scheduled by DCI format 0_0 (S20). When the PUCCH resource having the lowest ID is not configured without spatial relationship information (S10: N), PUSCH cannot be scheduled by DCI format 0_0 (S30).

[0215] <Embodiment 2> In FR2 and RRC connected mode, when there is no PUCCH resource configured within the active UL BWP of a CC, the default spatial relation and default path loss reference RS of the PUSCH scheduled by DCI format 0_0 are supported. This function may be applicable to a UE that supports the function of the default spatial relation for individual PUCCH or individual SRS in Rel.16, or may be applicable when a UE that supports the function of the default spatial relation for individual PUCCH or individual SRS in Rel.16 is configured by the base station.

[0216] An RRC parameter for enabling the function of the default spatial relation for individual PUCCH or individual SRS may be introduced. The default spatial relation may be the TCI state or QCL assumption of the CORESET with the lowest ID. The default path loss reference RS may be an RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID. The default path loss reference RS may be a periodic RS.

[0217] <Embodiment 3> In FR2 and RRC connected mode, it is supported to schedule a PUSCH by DCI format 0_0 within the active UL BWP of a CC having a configured PUCCH resource. Here, all the configured PUCCH resources within the active UL BWP are not configured with spatial relations.

[0218] For the PUSCH scheduled by DCI format 0_0, the spatial relation and path loss reference RS may respectively follow those of the PUCCH resource. For the PUSCH scheduled by DCI format 0_0, the spatial relation and path loss reference RS of the PUCCH resource may respectively be the default spatial relation and default path loss reference RS of the PUCCH resource.

[0219] <Embodiment 4> The UE may report UE capability information indicating at least one of the following: the UE has a default spatial relationship, the UE supports a default path loss reference RS, and the UE supports any one of Embodiments 1 to 3. The UE capability information may indicate each of the following: the UE has a default spatial relationship, the UE supports a default path loss reference RS, and the UE supports any one of Embodiments 1 to 3. One piece of UE capability information may indicate all of the following: the UE has a default spatial relationship, the UE supports a default path loss reference RS, and the UE supports any one of Embodiments 1 to 3.

[0220] <Embodiment 5> When an RRC parameter indicating at least one of the following is configured: applying a default spatial relationship, applying a default path loss reference RS, and applying any operation of Embodiments 1 to 3, the UE may perform the configured operation. When this RRC parameter is not configured, the UE may perform Rel.15 operations. The RRC parameter may indicate each of the following: applying a default spatial relationship, applying a default path loss reference RS, and applying any operation of Embodiments 1 to 3. One RRC parameter may indicate all of the following: applying a default spatial relationship, applying a default path loss reference RS, and applying any operation of Embodiments 1 to 3.

[0221] <Embodiment 6> The RS used for path loss calculation (default path loss reference RS) may be the RS of QCL type D of the lowest ID active TCI state for PDSCH. The default spatial relationship and the default path loss reference RS may be combined. The UE may follow at least one of the following Operations 1 and 2.

[0222] 《Operation 1》 For individual PUCCH or individual SRS in FR2, when the path loss reference RS is not configured by RRC signaling, the default spatial relationship may be as follows.

[0223] In the case where a CORESET is configured on a CC, the default spatial relation may be the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used for path loss calculation may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used for path loss calculation may be a periodic RS.

[0224] In the case where no CORESET is configured on a CC, the default spatial relation may be the activated TCI state with the lowest ID applicable to the PDSCH within the active DL-BWP of the CC.

[0225] The RS used for path loss calculation may be the RS of QCL type D of the active TCI state with the lowest ID for the PDSCH.

[0226] 《Operation 2》 For an individual PUCCH or individual SRS in FR2, when a path loss reference RS is configured by RRC signaling, the default spatial relation may be as follows.

[0227] In the case where a CORESET is configured on a CC, the default spatial relation may be the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used for path loss calculation may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID, or the configured or activated path loss reference RS. The RS used for path loss calculation may be a periodic RS.

[0228] In the case where no CORESET is configured on a CC, the default spatial relation may be the activated TCI state with the lowest ID applicable to the PDSCH within the active DL-BWP of the CC.

[0229] The RS used for path loss calculation may be the RS of QCL type D of the active TCI state having the lowest ID for PDSCH, or may be the configured or activated path loss reference RS.

[0230] For example, as shown in Figure 3, when the UE uses the default spatial relationship for individual PUCCH or individual SRS in FR2 and the path loss reference RS is configured (S10:Y), the UE uses the default path loss reference RS or the configured or activated path loss reference RS (S20). When the UE uses the default spatial relationship for individual PUCCH or individual SRS in FR2 and the path loss reference RS is not configured (S10:N), the UE uses the default path loss reference RS (S30).

[0231] <Embodiment 7> Based on whether at least one of the spatial relationship of the SRS resource indicated by the SRI for PUSCH and the path loss reference RS is configured, the UE determines at least one of the default spatial relationship and the default path loss reference RS for the SRS, and may apply at least one of the determined default spatial relationship and the default path loss reference RS to the PUSCH. The determination of at least one of the default spatial relationship and the default path loss reference RS for the SRS may follow the aforementioned determination method (for example, at least one of Embodiments 1 to 6). The UE may follow at least one of the following Operations 1, 2, 3, and 4.

[0232] <<Operation 1>> In FR2, if PUSCH is scheduled by DCI format 0_1, and no spatial relation is set for the SRS resource indicated by SRI, and no path loss reference RS is set, and in the case where a CORESET is set on that CC, the default spatial relation for the PUSCH may be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID, or may be the set or activated path loss reference RS. The RS used for path loss calculation may be a periodic RS.

[0233] In this case, if no CORESET is set on that CC, the default spatial relation for the PUSCH may be the activated TCI state with the lowest ID applicable to the PDSCH within the active DL-BWP of that CC. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D of the active TCI state with the lowest ID for the PDSCH, or may be the set or activated path loss reference RS. The RS used for path loss calculation may be a periodic RS.

[0234] 《Operation 2》 In FR2, if PUSCH is scheduled by DCI format 0_1, and no spatial relation is set for the SRS resource indicated by SRI, and no path loss reference RS is set, and in the case where a CORESET is set on that CC, the default spatial relation for the PUSCH may be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used for path loss calculation may be a periodic RS.

[0235] In this case, if no CORESET is configured on the CC, the default spatial relation for the PUSCH may be the activated TCI state with the lowest ID applicable to the PDSCH within the active DL-BWP of the CC. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D of the active TCI state with the lowest ID for the PDSCH. The RS used for path loss calculation may be a periodic RS.

[0236] 《Operation 3》 In FR2, if the PUSCH is scheduled by DCI format 0_1, and no spatial relation is configured for the SRS resource indicated by the SRI, and no path loss reference RS is configured, and if a CORESET is configured on the CC, the default spatial relation for the PUSCH may be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID, or may be the configured or activated path loss reference RS. The RS used for path loss calculation may be a periodic RS.

[0237] In this case, if no CORESET is configured on the CC, the default spatial relation for the PUSCH may be the activated TCI state with the lowest ID applicable to the PDSCH within the active DL-BWP of the CC. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D of the active TCI state with the lowest ID for the PDSCH, or may be the configured or activated path loss reference RS. The RS used for path loss calculation may be a periodic RS.

[0238] 《Operation 4》 In FR2, if the PUSCH is scheduled by DCI format 0_1, and no spatial relation is set for the SRS resource indicated by the SRI, and a path loss reference RS is set, and a CORESET is set on that CC, the default spatial relation for the PUSCH may be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used for path loss calculation may be a periodic RS.

[0239] In this case, if no CORESET is set on that CC, the default spatial relation for the PUSCH may be the activated TCI state with the lowest ID applicable to the PDSCH within the active DL-BWP of that CC. In this case, the RS used for path loss calculation for the PUSCH may be the RS of QCL type D of the active TCI state with the lowest ID for the PDSCH. The RS used for path loss calculation may be a periodic RS.

[0240] The size (number of bits) of the SRI field of the PUSCH scheduled by DCI format 0_1 varies according to the number of SRS resources in the SRS resource set for which the use of codebook-based transmission or non-codebook-based transmission is set. For example, if the SRS resource is 1, the size of the SRI field is 0 bits, and if the number of SRS resources is 2, the size of the SRI field is 1 bit. The aforementioned "SRS resource indicated by the SRI" may include the SRS resource when the number of SRS resources is 1 (only one SRS resource within the SRS resource set for which the use of codebook-based transmission or non-codebook-based transmission is set).

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

[0242] FIG. 4 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0258] The PDCCH may be used to transmit lower layer control information. 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.

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

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

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

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

[0263] Note that in the present disclosure, downlink, uplink, etc. may be expressed without adding "link". Also, the prefix "Physical" may be omitted when expressing the beginning of various channels.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0285] Note that in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each part described below may be omitted.

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

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

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

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

[0290] The transmission / reception antenna 230 can be composed of an antenna described based on the common knowledge in the technical field related to the present disclosure, for example, an array antenna.

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

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

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

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

[0295] Whether or not 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 transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the above-described transmission processing to transmit the channel using the DFT-s-OFDM waveform, or may not perform DFT processing as the above-described transmission processing if not.

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

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

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

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

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

[0301] The transceiver unit 220 may receive setting information indicating a physical uplink control channel (PUCCH) resource that does not include spatial relationship information and has the lowest ID. The control unit 210 may control the reception of a physical uplink shared channel (PUSCH) scheduled by a downlink control information (DCI) format 0_0.

[0302] The transceiver unit 220 may receive the DCI format 0_0 in a frequency range (FR) 2 and a radio resource control (RRC) connected mode.

[0303] The transceiver unit 220 may receive the DCI format 0_0 in the active uplink bandwidth part (BWP) where the PUCCH resource is configured.

[0304] The transceiver unit 220 may receive the configuration information of one uplink transmission of a physical uplink control channel (PUCCH) and a sounding reference signal (SRS). The configuration information may not include spatial relation information and information of a reference signal for path loss reference. The control unit 210 may use the reference signal of the active transmission control indication (TCI) state having the lowest ID for the physical downlink shared channel (PDSCH) for path loss calculation for the uplink transmission.

[0305] The reference signal may be used for path loss calculation for a physical uplink shared channel (PUSCH).

[0306] The reference signal may be of quasi - co - location (QCL) type D.

[0307] (Hardware Configuration) Note that the block diagrams used in the description of the above - mentioned embodiment 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 (for example, using wired, wireless, etc.) connected and realized using these multiple devices. The functional block may be realized by combining software with the above - mentioned one device or the above - mentioned multiple devices.

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

[0309] 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. 7 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may physically be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

[0311] For example, although only one processor 1001 is shown in the figure, 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.

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

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

[0314] 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 that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operating in the processor 1001, and the same may be true for other functional blocks.

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

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

[0317] 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), transceiver antenna 130 (230), etc. may be implemented by the communication device 1004. The transceiver unit 120 (220) may be physically or logically separated into a transmitter unit 120a (220a) and a receiver unit 120b (220b).

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

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

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

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

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

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

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

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

[0326] A radio frame, sub-frame, slot, mini-slot, and symbol all represent time units for signal transmission. A radio frame, sub-frame, slot, mini-slot, and symbol may each be used with another corresponding name. Note that the time units such as frames, sub-frames, slots, mini-slots, and symbols in this disclosure may be read interchangeably with each other.

[0327] 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 may be a period shorter than 1 ms (for example, 1 - 13 symbols), or may be a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc. instead of a sub-frame.

[0328] 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 (frequency bandwidth, transmission power, etc. 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.

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

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

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

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

[0333] 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 more consecutive subcarriers. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, it may be 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0334] Also, an RB may include one or more 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 more resource blocks.

[0335] Note that one or more RBs may be referred to as Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

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

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

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

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

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

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

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

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

[0344] In addition, information, signals, etc. can 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.

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

[0346] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), 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.

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

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

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

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

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

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

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

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

[0355] 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 smaller area can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of a base station and a base station subsystem that provides communication services in this coverage.

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

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

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

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

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

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

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

[0363] Each aspect / embodiment described in the present disclosure may be applied to systems that utilize 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), 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.

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

[0365] Any reference to an element using designations such as "first", "second", etc. used in the present disclosure does not generally limit the quantity or order of those elements. These designations may be used in the present disclosure as a convenient way to distinguish between two or more elements. Therefore, 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.

[0366] As used herein, the term "determining" may encompass a variety of operations. For example, "determining" may be considered to be "judging", "calculating", "computing", "processing", "deriving", "investigating", "looking up, searching, inquiring" (e.g., searching in a table, database or another data structure), "ascertaining", etc.

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

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

[0369] Also, "determining" may be read as "assuming", "expecting", "considering", etc.

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

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

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

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

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

[0375] 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 defined based on the description of the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and does not bring any restrictive meaning to the invention according to the present disclosure.

[0376] This application is based on Japanese Patent Application No. 2019-210876 filed on November 21, 2019. The entire content of this application is incorporated herein by reference.

Claims

1. A receiving unit that receives a downlink control information (DCI) format 0_0 for scheduling a physical uplink shared channel (PUSCH); When one or more physical uplink control channel (PUCCH) resources are set on the active uplink bandwidth part (BWP) of the cell of the PUSCH and spatial relation information is not included in all of the one or more PUCCH resources, a control unit that determines the spatial relation of the PUSCH based on a quasi co-location (QCL) assumption of a specific control resource set; and When the one or more PUCCH resources are set on the active uplink BWP and the spatial relation information is not included in all of the one or more PUCCH resources, the control unit estimates the path loss of the PUSCH based on the QCL assumption, and controls the transmission power of the PUSCH based on the path loss of the PUSCH and a transmission power control (TPC) command value in the DCI format 0_0. A terminal that controls the transmission power of the PUSCH.

2. The terminal according to claim 1, wherein the control unit applies a reference signal of QCL type D corresponding to the QCL assumption of the specific control resource set to the spatial relation of the PUSCH.

3. Receiving a downlink control information (DCI) format 0_0 for scheduling a physical uplink shared channel (PUSCH); When one or more physical uplink control channel (PUCCH) resources are set on the active uplink bandwidth part (BWP) of the cell of the PUSCH and spatial relation information is not included in all of the one or more PUCCH resources, determining the spatial relation of the PUSCH based on a quasi co-location (QCL) assumption of a specific control resource set; and When the one or more PUCCH resources are set on the active uplink BWP and the spatial relation information is not included in all of the one or more PUCCH resources, estimating the path loss of the PUSCH based on the QCL assumption, and controlling the transmission power of the PUSCH based on the path loss of the PUSCH and a transmission power control (TPC) command value in the DCI format 0_0. A wireless communication method for a terminal having the steps of:

4. A transmitting unit that transmits downlink control information (DCI) format 0_0 for scheduling a physical uplink shared channel (PUSCH); A control unit that controls reception of the PUSCH transmitted using a spatial relationship based on a quasi co-location (QCL) assumption of a specific control resource set when one or more physical uplink control channel (PUCCH) resources are set on an active uplink bandwidth part (BWP) of a cell of the PUSCH and spatial relationship information is not included in all of the one or more PUCCH resources; A base station that estimates a path loss of the PUSCH based on the QCL assumption and controls transmission power of the PUSCH based on the path loss of the PUSCH and a transmission power control (TPC) command value in the DCI format 0_0 when the one or more PUCCH resources are set on the active uplink BWP and the spatial relationship information is not included in all of the one or more PUCCH resources;

5. A system including a terminal and a base station, wherein the terminal has a receiving unit that receives downlink control information (DCI) format 0_0 for scheduling a physical uplink shared channel (PUSCH), and a control unit that determines a spatial relationship of the PUSCH based on a quasi co-location (QCL) assumption of a specific control resource set when one or more physical uplink control channel (PUCCH) resources are set on an active uplink bandwidth part (BWP) of a cell of the PUSCH and spatial relationship information is not included in all of the one or more PUCCH resources; when the one or more PUCCH resources are set on the active uplink BWP and the spatial relationship information is not included in all of the one or more PUCCH resources, the control unit estimates a path loss of the PUSCH based on the QCL assumption and controls transmission power of the PUSCH based on the path loss of the PUSCH and a transmission power control (TPC) command value in the DCI format 0_0, wherein the base station has a receiving unit that receives the PUSCH from the terminal.

Images