Terminal and wireless communication method

Abstract

A terminal involved in one embodiment of the present disclosure comprises: a receiving unit that receives setting information, wherein the setting information does not include spatial relationship information and indicates a physical uplink control channel (PUCCH) resource with the lowest ID; and a control unit that controls the reception of a physical uplink shared channel (PUSCH) scheduled via downlink control information (DCI) format 0_0.

Description

Technical Field

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized to achieve even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) has been standardized to further enhance the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Releases (Rel.) 8 and 9).

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

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-Patent Document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (e.g., NR), research is underway to control transmission and reception processing in user terminals (terminal, user terminal, User Equipment (UE)) based on information related to Quasi-Co-Location (QCL)).

[0009] However, it is not clear how to determine at least one reference signal (RS) used for QCL and path loss calculation in downlink (DL) signal reception or uplink (UL) signal transmission. If the UE does not determine an appropriate reference signal, there is a concern that throughput and other system performance may be reduced.

[0010] Therefore, one of the objects of the present disclosure is to provide a terminal and a wireless communication method that appropriately determine at least one reference signal used for QCL and path loss calculation.

[0011] Means for solving problems

[0012] A terminal involved in one embodiment of the present disclosure comprises: a receiving unit that receives setting information, wherein the setting information does not include spatial relationship information and indicates a physical uplink control channel (PUCCH) resource with the lowest ID; and a control unit that controls the reception of a physical uplink shared channel (PUSCH) scheduled via downlink control information (DCI) format 0_0.

[0013] Effects of the Invention

[0014] According to one aspect of the present disclosure, it is possible to appropriately determine at least one reference signal used for QCL and path loss calculation. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a diagram showing an example of QCL assumptions for PDSCH.

[0016] Figure 2 This is a diagram showing an example of the operation according to the first embodiment.

[0017] Figure 3 This is a diagram showing an example of the operation involved in the sixth embodiment.

[0018] Figure 4 This is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment.

[0019] Figure 5 This is a diagram showing an example of the configuration of a base station according to one embodiment.

[0020] Figure 6 This is a diagram showing an example of the configuration of a user terminal according to one embodiment.

[0021] Figure 7 This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment. DETAILED DESCRIPTION

[0022] (Transmit Power Control)

[0023] <Transmission Power Control for PUSCH>

[0024] In NR, the transmission power of PUSCH is controlled based on the TPC command (also referred to as value, increment / decrement value, correction value, etc.) indicated by the value of a specific field (also called TPC command field, etc.) within the DCI.

[0025] For example, when the UE uses a parameter set with index j (open-loop parameter set) and index l of the power control adjustment state (PUSCH power control adjustment state) to transmit PUSCH on the active UL BWP b of carrier f in serving cell c, the transmission power (P PUSCH、b，f，c (i, j, q d , l)) of PUSCH in PUSCH transmission occasion (also called transmission period, etc.) i can also be expressed by the following formula (1). The power control adjustment state is the value of the TPC command based on the power control adjustment state index l, and can also be referred to as the accumulated value of the TPC command, the value based on closed-loop. l can also be called the closed-loop index.

[0026] In addition, the PUSCH transmission occasion i is the period during which PUSCH is transmitted, and can be composed of, for example, more than one symbol, more than one time slot, etc.

[0027] [Equation 1]

[0028] Formula (1)

[0029]

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

[0031] M PUSCH RB，b，fc (i) is, for example, the number of resource blocks (bandwidth) allocated to PUSCH for transmission occasion 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 (e.g., also called msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

[0032] PL b，f，c (q d ) For example, the index q of the reference signal (reference signal (RS), path loss reference RS, path loss reference RS, path loss measurement DL-RS, PUSCH-PathlossReferenceRS) for the downlink BWP associated with the activated UL BWP b of the carrier f of the serving cell c is used d The path loss calculated by the user terminal (path loss estimation [dB], path loss compensation).

[0033] If the UE is not provided with a path loss reference RS (e.g., PUSCH-PathlossReferenceRS) or if the UE is not provided with dedicated higher layer parameters, the UE may also use the RS resources from the synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB) used to obtain the master information block (MIB) to calculate the PL. b，f，c (q d ).

[0034] In the case where the UE is configured with a set of RS resource indices and path loss reference RSs up to the value of the maximum number of path loss reference RSs (e.g., maxNrofPUSCH-PathlossReferenceRSs), the set of RS resource indices may include one or both of a set of SS / PBCH block indices and a set of channel state information (CSI)-reference signal (RS) resource indices. The UE may also identify the RS resource index q within the set of RS resource indices. d .

[0035] When a PUSCH transmission is scheduled by a Random Access Response (RAR) UL grant, the UE may also use the same RS resource index q as that used for the corresponding PRACH transmission. d .

[0036] When a UE is provided with a PUSCH power control configuration based on a sounding reference signal (SRS) resource indicator (SRI) (e.g., SRI-PUSCH-PowerControl) and is provided with one or more values ​​of the path loss reference RS ID, the mapping between the set of values ​​for the SRI field in DCI format 0_1 ​​and the set of path loss reference RS ID values ​​may be obtained from higher layer signaling (e.g., sri-PUSCH-PowerControl-Id in SRI-PUSCH-PowerControl). The UE may also determine the RS resource index q from the path loss reference RS ID mapped to the SRI field value in DCI format 0_1 ​​for scheduling the PUSCH. d .

[0037] In the case where PUSCH transmission is scheduled using DCI format 0_0 and the UE is not provided with PUCCH spatial relationship information for the PUCCH resource with the lowest index for the activated UL BWP b for each carrier f and serving cell c, the UE may also use the same RS resource index q as the PUCCH transmission within the PUCCH resource. d .

[0038] In the case where PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided with the spatial configuration of PUCCH transmission, or in the case where PUSCH transmission is scheduled by DCI format 0_1 ​​that does not include the SRI field, or in the case where the configuration of SRI-based PUSCH power control is not provided to the UE, the UE may also use the RS resource index q with the ID of the zero path loss reference RS. d .

[0039] When the PUSCH transmission is configured by configuring a grant configuration (e.g., ConfiguredGrantConfig), and the grant configuration includes a specific parameter (e.g., rrc-ConfiguredUplinkGrant), the RS resource index q d It may also be provided to the UE via a path loss reference index (eg, pathlossReferenceIndex) within a specific parameter.

[0040] In the case where the permission setting does not include specific parameters for PUSCH transmission configured by the permission setting, the UE may also determine the RS resource index q from the value of the path loss reference RS ID mapped to the SRI field in the DCI format that activates PUSCH transmission. dIn the case where the DCI format does not contain the SRI field, the UE may also determine the RS resource index q of the ID of the reference RS with zero path loss. d .

[0041] Δ TF，b，f，c (i) is a transmission power adjustment component (offset, transmission format compensation) for UL BWP b of carrier f of serving cell c.

[0042] f b，f，c (i, l) is the PUSCH power control adjustment state of the activated UL BWP b for carrier f of serving cell c in transmission opportunity i. For example, f b，f，c (i, l) can also be expressed by formula (2).

[0043] [Number 2]

[0044] Formula (2)

[0045]

[0046] Here, δ PUSCH，b，f，c (i, 1) is the TPC command value contained in DCI format 0_0 or DCI format 0_1 ​​of the PUSCH transmission opportunity i on the activated UL BWP b of the carrier f scheduling the service cell c, or it can also be the TPC command value encoded in combination with other TPC commands in DCI format 2_2 with a CRC encrypted by a specific RNTI (Radio Network Temporary Identifier) ​​(for example, TPC-PUSCH-RNTI).

[0047] ∑m=0 C(Di)-1 δ PUCCH，b，f，c (m, l) can also have a concentration (cardinality) C (D i ) of the TPC command value set D i The total of TPC command values ​​within D i It can also be the K of the UE for PUSCH power control adjustment state 1, on the activated UL BWP b of carrier f in serving cell c, and PUSCH transmission opportunity i-i0 PUSCH (i-i0)-1 symbol ago and K of PUSCH transmission opportunity i PUSCH (i) The set of TPC command values ​​received between symbols before. i0 can also be the K of PUSCH transmission opportunity i-i0. PUSCH (i-i0) symbols ago becomes K higher than PUSCH transmission opportunity i PUSCH(i) The earliest, smallest positive integer before the symbol.

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

[0049] The power control adjustment state can also be set by a higher layer parameter to have multiple states (e.g., 2 states) or a single state. In addition, when multiple power control adjustment states are set, one of the multiple power control adjustment states can be identified by an index l (e.g., l ∈ {0, 1}).

[0050] In addition, Equations (1) and (2) are only examples, but not limited to this. The user terminal only needs to control the transmission power of the PUSCH based on at least one parameter exemplified in Equations (1) and (2). It can include additional parameters or omit some parameters. In addition, in the above Equations (1) and (2), the transmission power of the PUSCH is controlled for each active UL BWP of a certain carrier of a certain serving cell, but not limited to this. At least a part of the serving cell, carrier, BWP, and power control adjustment state can also be omitted.

[0051] <PUCCH Transmission Power Control>

[0052] In addition, in NR, the transmission power of the PUCCH can also be controlled based on the TPC command (also known as value, increment / decrement value, correction value, indication value, etc.) indicated by the value of a specific field (also known as TPC command field, first field, etc.) in the DCI.

[0053] For example, using the index 1 of the power control adjustment state (PUCCH power control adjustment state), the PUCCH transmission power (P PUCCH、b，f，c (i,q u ,q d , 1)) can also be expressed by the following equation (3). The power control adjustment state can also be referred to as the value of the TPC command based on the power control adjustment state index 1, the accumulated value of the TPC command, or the value based on the closed loop. 1 can also be referred to as the closed loop index.

[0054] Furthermore, the PUCCH transmission opportunity i is a period during which the PUCCH is transmitted, and may be composed of, for example, one or more symbols, one or more time slots, or the like.

[0055] [Number 3]

[0056] Formula (3)

[0057]

[0058] Here, P CMAX，f，v (i) For example, the user terminal's transmission power (also referred to as maximum transmission power, UE maximum output power, etc.) set for carrier f of serving cell c in transmission opportunity i. O_PUCCH，b，f，c (qu) is, for example, a parameter related to the target receiving power for the activated UL BWP b of the carrier f of the serving cell c set in the transmission opportunity i (for example, also called a parameter related to the transmission power offset, the transmission power offset P0, or the target receiving power parameter, etc.).

[0059] M PUCCH RB，b，f，c (i) For example, PL is the number of resource blocks (bandwidth) allocated to the PUCCH for transmission opportunity i in the active ULBWPb of the serving cell c and carrier f with a subcarrier spacing μ. b，f，c (q d ) For example, the index q of the reference signal for downlink BWP (path loss reference RS, path loss reference RS, path loss measurement DL-RS, PUCCH-PathlossReferenceRS) associated with the activated UL BWP b of carrier f of serving cell c is used. d The path loss calculated by the user terminal (path loss estimation [dB], path loss compensation).

[0060] If the UE is not given a path loss reference RS (pathlossReferenceRSs) or before the UE is given dedicated higher layer parameters, the UE calculates the path loss PL using the RS resources obtained from the SS / PBCH block used for the UE to obtain the MIB b，f，c (q d ).

[0061] If the UE is given path loss reference RS information (pathlossReferenceRSs within PUCCH power control information (PUCCH-PowerControl)) and is not given PUCCH spatial relationship information (PUCCH-SpatialRelationInfo), the UE obtains the value of the reference signal within the PUCCH path loss reference RS with the PUCCH path loss reference RS-ID (PUCCH-PathlossReferenceRS-Id) indexed 0 within the PUCCH path loss reference RS information (PUCCH-PathlossReferenceRS). The resource of this reference signal is located on the same serving cell or, if given, on the serving cell indicated by the value of path loss reference linking information (pathlossReferenceLinking). The path loss reference linking information indicates which DL of the special cell (SpCell) or the secondary cell (SCell) corresponding to the UL should be used by the UE as a path loss reference. An SpCell can be either a primary cell (PCell) in a master cell group (MCG) or a primary secondary cell (PSCell) in a secondary cell group (SCG). Path loss reference RS information indicates the set of reference signals (e.g., CSI-RS structure or SS / PBCH blocks) used in PUCCH path loss estimation.

[0062] Δ F_PUCCH (F) is a high-level parameter given for each PUCCH format. TF，b，f，c (i) is a transmission power adjustment component (offset) for UL BWP b of carrier f of serving cell c.

[0063] g b，f，c(i, 1) is the value of the TPC command for the power control adjustment state index 1 based on the activated UL BWP of carrier f in serving cell c and transmission opportunity i (e.g., power control adjustment state, accumulated value of TPC commands, closed-loop value, PUCCH power adjustment state). For example, g b，f，c (i, l) can also be expressed by formula (4).

[0064] [Number 4]

[0065] Formula (4)

[0066]

[0067] Here, δ PUCCH，b，f，c (i, l) is the 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 activated UL BWPb of the carrier f of the serving cell c, or can also be encoded in combination with other TPC commands in DCI format 22 with a CRC encrypted with a specific RNTI (Radio Network Temporary Identifier) ​​(for example, TPC-PUSCH-RNTI).

[0068] ∑ m＝0 C(Ci)-1 δ PUCCH，b，f，c (m, l) can also be a cardinality C(C i ) of the TPC command value set C i The total of TPC command values ​​in C i It can also be the K of the UE for PUCCH power control adjustment state 1, the activated UL BWP b of carrier f in serving cell c, and the PUCCH transmission opportunity i-i0 PUCCH (i-i0)-1 symbol ago and K of PUSCH transmission opportunity i PUCCH (i) The set of TPC command values ​​received between symbols before. i0 can also be the K of PUSCH transmission opportunity i-i0. PUCCH (i-i0) symbols ago becomes K higher than PUSCH transmission opportunity i PUCCH (i) The smallest positive integer preceding the symbol.

[0069] If PUCCH is sent according to UE-based DCI format 1_0 or DCI format 1_1 detection, K PUCCH(i) It can also be the number of symbols in the activated ULBWP b of carrier f of serving cell c after the last symbol received on the corresponding PDCCH and before the first symbol transmitted on the corresponding PUCCH. If PUCCH transmission is configured by configuring the grant structure information (ConfiguredGrantConfig), K PUSCH (i) It can also be the number of symbols per time slot N in the activated UL BWP b of carrier f of serving cell c. symb slot , K equal to the product of the minimum value of the value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon) PUCCH，min The number of code elements.

[0070] It can also be that if the UE is provided with information indicating the use of two PUCCH power control adjustment states (twoPUCCH-PC-AdjustmentStates) and PUCCH spatial relationship information (PUCCH-SpatialRelationInfo), l = {0, 1}; if the UE is not provided with information indicating the use of two PUCCH power control adjustment states or PUCCH spatial relationship information, l = 0.

[0071] If the UE receives a TPC command value from DCI format 1_0 or 1_1 and is not provided with PUCCH spatial relationship information, the UE can also obtain the mapping between the PUCCH spatial relationship information ID (pucch-SpatialRelationInfoId) value and the closed loop index (closedLoopIndex, power adjustment state index 1) using the index provided by the PUCCH P0 ID (p0-PUCCH-Id in p0-Set in PUCCH-PowerControl in PUCCH-Config). If the UE receives an activation command including the PUCCH spatial relationship information ID value, the UE can also determine the closed loop index value provided with the value 1 through the link for the corresponding PUCCH P0 ID.

[0072] If the UE activates ULBWPb for carrier f of serving cell c, the higher layers are provided with the corresponding PUCCH power adjustment state 1. O_PUCCH，b，f，c (q u ) value, g b，f，c (i, l) = 0, k = 0, 1, ..., i. If the UE is provided with PUCCH spatial relationship information, the UE may also uThe P0 ID for PUCCH and the PUCCH spatial relation information associated with the closed-loop index value corresponding to l are from q u The value of determines the value of l.

[0073] q u It can also be the PUCCH P0 ID (p0-PUCCH-Id) representing the PUCCH P0 (P0-PUCCH) within the P0 set (p0-Set) for PUCCH.

[0074] In addition, Equations (3) and (4) are just examples and are not limited to this. The user equipment only needs to control the transmission power of PUCCH based on at least one of the parameters exemplified in Equations (3) and (4). It can include additional parameters or omit some parameters. Moreover, in the above Equations (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 to this. At least a part of the serving cell, carrier, BWP, and power control adjustment state can also be omitted.

[0075] <Transmission Power Control for SRS>

[0076] For example, using the index l of the power control adjustment state, for the SRS transmission occasion (also referred to as the transmission period, etc.) i in the active UL BWP b of the carrier f of the serving cell c, the transmission power (P SRS、b，f，c (i, q s , 1)) of the SRS can also be represented by the following Equation (5). The power control adjustment state can also be referred to as the TPC command value based on the power control adjustment state index 1, the accumulated value of the TPC command, and the value based on the closed loop. 1 can also be referred to as the closed-loop index.

[0077] In addition, the SRS transmission occasion i is the period during which the SRS is transmitted. For example, it can be composed of more than one symbol, more than one time slot, etc.

[0078] [Equation 5]

[0079] Equation (5)

[0080]

[0081] Here, P CMAX，f，c (i) is, for example, the maximum output power of the UE for the carrier f of the serving cell c in the SRS transmission occasion i. P O_SRS，b，f，c (q s ) is obtained through the active UL BWP b of the carrier f of the serving cell c and the SRS resource set q sParameters related to the target reception power provided by p0 (provided by SRS-ResourceSet and SRS-ResourceSetId) (for example, also called parameters related to the transmission power offset, transmission power offset P0, or target reception power parameters, etc.).

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

[0083] α SRS，b，f，c (q s ) by activating UL BWP b, and SRS resource set q for serving cell c and carrier f with subcarrier spacing μ s α (e.g., alpha) is provided.

[0084] PL b，f，c (q d ) is the activated DL BWP and SRS resource set q for serving cell c s , using RS resource index q d The DL path loss estimate [dB] calculated by the UE (path loss estimate [dB], path loss compensation). RS resource index q d Is the same as SRS resource set q s The associated path loss reference RS (path loss reference RS, path loss measurement DL-RS, for example, provided by pathlossReferenceRS) is an SS / PBCH block index (for example, ssb-Index) or a CSI-RS resource index (for example, csi-RS-Index).

[0085] If the UE is not given path loss reference RSs or before the UE is given dedicated higher layer parameters, the UE calculates the PL using the RS resources obtained from the SS / PBCH block used for UE to obtain the MIB b，f，c (q d ).

[0086] h b，f，c (i, 1) is the SRS power control adjustment state for the activated UL BWP of carrier f of serving cell c in SRS transmission opportunity i. If the SRS power control adjustment state setting (e.g., srs-PowerControlAdjustmentStates) indicates the same power control adjustment state for SRS transmission and PUSCH transmission, it is the current PUSCH power control adjustment state f.b，f，c On the other hand, if the SRS power control adjustment state setting indicates independent power control adjustment states for SRS transmission and PUSCH transmission, and no TPC accumulation setting is provided, the SRS power control adjustment state h b，f，c (i) can also be expressed by formula (6).

[0087] [Number 6]

[0088] Formula (6)

[0089]

[0090] Here, δ SRS，b，f，c (m) may also be a TPC command value encoded in conjunction with its TPC command within a PDCCH with DCI (e.g., DCI format 2_3). m＝0 C(Si)-1 δ SRS，b，f，c (m) It can also be on the activated UL BWP b of the serving cell c and the carrier f with subcarrier spacing μ, at the K of the SRS transmission opportunity i-i0 SRS (i-i0)-1 symbol ago and K of SRS transmission opportunity i SRS (i) The code element received by the UE before the cardinality C(S i ) of the TPC command value set S i Here, i0 can also be the K of SRS transmission opportunity i-i0. SRS (i-i0)-1 symbol ago becomes K higher than SRS transmission opportunity i SRS (i) The smallest positive integer preceding the symbol.

[0091] If SRS transmission is aperiodic, K SRS (i) It can also be the number of symbols in the activated 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) It can also be the number of symbols per time slot N in the activated ULBWPb of carrier f of serving cell c. symb slot K is equal to the product of the minimum value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon) SRS，min The number of code elements.

[0092] Equations (5) and (6) are examples only and are not intended to be limiting. A user terminal may control the SRS transmit power based on at least one of the parameters exemplified in Equations (5) and (6), and may include additional parameters or omit some parameters. Furthermore, in Equations (5) and (6), the SRS transmit power is controlled for each BWP of a certain carrier in a certain cell, but this is not limiting. At least some of the cell, carrier, BWP, and power control adjustment state may also be omitted.

[0093] (TCI, spatial relationship, QCL)

[0094] In NR, research is underway to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and coding) in the UE based on the transmission configuration indication state (TCI state) to control at least one of the signal and the channel (expressed as signal / channel).

[0095] The TCI state may also indicate the state of a signal / channel applied to a downlink. The state corresponding to the TCI state applied to an uplink signal / channel may also be expressed as a spatial relation.

[0096] The TCI status is information related to Quasi-Co-Location (QCL) of signals / channels and may also be referred to as spatial reception parameters, spatial relation information, etc. The TCI status may be set for each channel or each signal for the UE.

[0097] QCL is an indicator of the statistical properties of a signal / channel. For example, the fact that a signal / channel is in a QCL relationship with other signals / channels may also mean that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameters (e.g., spatial Rx parameters) can be assumed to be the same among these different signals / channels (at least one of these is QCL).

[0098] In addition, the spatial reception parameter may also correspond to the UE's receive beam (e.g., receive analog beam), or the beam may be determined based on spatial QCL. The QCL (or at least one element of QCL) in this disclosure may also be replaced with sQCL (spatial QCL).

[0099] QCLs can also be specified in multiple types (QCL types). For example, four QCL types AD can be set. In these four QCL types AD, the parameters (or parameter sets) that can be assumed to be the same are different. The parameters (also called QCL parameters) are shown below:

[0100] QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread,

[0101] QCL type B (QCL-B): Doppler shift and Doppler spread,

[0102] QCL Type C (QCL-C): Doppler shift and average delay,

[0103] QCL type D (QCL-D): spatial reception parameters.

[0104] The situation where the UE assumes that a specific control resource set (CORESET), channel or reference signal is in a specific QCL (e.g., QCL type D) relationship with other CORESETs, channels or reference signals can also be called QCL assumption.

[0105] The UE determines at least one of the transmit beam (Tx beam) and receive beam (Rx beam) of the signal / channel based on the TCI status or QCL assumption of the signal / channel.

[0106] The TCI status may also be information related to the QCL of the target channel (in other words, the reference signal (RS) used for the channel) and another signal (for example, another RS). The TCI status may also be set (indicated) through higher layer signaling, physical layer signaling, or a combination thereof.

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

[0108] MAC signaling may also use, for example, MAC control elements (MAC Control Element (MAC CE)), MAC Protocol Data Unit (PDU), etc. Broadcast information may also include, for example, Master Information Block (MIB), System Information Block (SIB), minimum system information (Remaining Minimum System Information (RMSI)), and other system information (Other System Information (OSI)).

[0109] The physical layer signaling may be, for example, downlink control information (Downlink Control Information (DCI))).

[0110] The channel for setting (specifying) the TCI state or spatial relationship may also be, for example, at least one of the downlink shared channel (Physical Downlink Shared Channel (PDSCH)), the downlink control channel (Physical Downlink Control Channel (PDCCH)), the uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and the uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0111] In addition, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SynchronizationSignal Block (SSB)), a channel state information reference signal (CSI-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called QRS).

[0112] The SSB is a signal block that includes at least one of the primary synchronization signal (PSS), the secondary synchronization signal (SSS), and the broadcast channel (physical broadcast channel (PBCH)). The SSB may also be referred to as an SS / PBCH block.

[0113] The UE may also receive configuration information of a list of information elements containing TCI states (e.g., PDSCH-Config, tci-StatesToAddModList) through higher layer signaling.

[0114] The TCI state information element set by high-layer signaling (RRC's "TCI-state IE") may also include one or more QCL information ("QCL-Info"). The QCL information may also include at least one of information related to the RS that forms a QCL relationship (RS relationship information) and information indicating the QCL type (QCL type information). The RS relationship information may also include information such as the RS index (e.g., SSB index, non-zero-power CSI-RS (Non-Zero-Power (NZP) CSI-RS) resource ID (Identifier)), the index of the cell where the RS is located, and the index of the bandwidth part (Bandwidth Part (BWP)) where the RS is located.

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

[0116] When TRS is configured as a QCL Type A RS, it differs from the Demodulation Reference Signal (DMRS) for PDCCH or PDSCH, and is assumed to be transmitted periodically over a long period of time. UEs can measure TRS and calculate average delay, delay spread, and other parameters.

[0117] A UE in which the TCI state of the DMRS of a PDCCH or PDSCH is set as a QCL Type A RS using the TRS can assume that the QCL Type A parameters (average delay, delay spread, etc.) of the DMRS of the PDCCH or PDSCH and the TRS are the same. Therefore, the Type A parameters (average delay, delay spread, etc.) of the DMRS of the PDCCH or PDSCH can be calculated based on the measurement results of the TRS. When performing channel estimation for at least one of the PDCCH and PDSCH, the UE can use the measurement results of the TRS to perform more accurate channel estimation.

[0118] A UE configured with a QCL type D RS can determine a UE reception beam (spatial domain reception filter, UE spatial domain reception filter) using the QCL type D RS.

[0119] The RS of QCL type X in the TCI state may also mean an RS that is in a QCL type X relationship with a certain channel / signal (DMRS), and the RS may also be referred to as a QCL source of QCL type X in the TCI state.

[0120] <TCI Status for PDCCH>

[0121] Information about the PDCCH (or the DMRS antenna port associated with the PDCCH) and the QCL of a specific RS may also be referred to as a TCI state for the PDCCH, etc.

[0122] The UE may also determine the TCI state for a UE-specific PDCCH (CORESET) based on higher layer signaling. For example, the UE may also configure one or more (K) TCI states for each CORESET via RRC signaling.

[0123] For each CORESET, the UE can also activate one of multiple TCI states set by RRC signaling through a MAC CE. This MAC CE is also called a TCI State Indication for UE-specific PDCCH MAC CE. The UE can also monitor the CORESET based on the activated TCI state corresponding to the CORESET.

[0124] <TCI status for PDSCH>

[0125] Information about the PDSCH (or the DMRS antenna port associated with the PDSCH) and the QCL of a certain DL-RS may also be referred to as the TCI state for the PDSCH, etc.

[0126] The UE may also be notified (configured) of M (M≥1) TCI states for PDSCH (QCL information for M PDSCHs) through higher layer signaling. Furthermore, the number M of TCI states configured for the UE may be limited by at least one of the UE capability and the QCL type.

[0127] The DCI used for scheduling the PDSCH may also include a field indicating a specific TCI state for the PDSCH (which may also be referred to as, for example, a TCI field, a TCI state field, etc.). This DCI may also be used in scheduling the PDSCH of a cell and may be referred to as, for example, DL DCI, DL allocation, DCI format 1_0, DCI format 1_1, etc.

[0128] Whether the TCI field is included in the DCI can also be controlled by information notified to the UE from the base station. This information can also be information indicating whether the TCI field is present or absent in the DCI (for example, TCI presence information, TCI presence information in DCI, or the higher-layer parameter TCI-PresentInDCI). This information can also be set to the UE through higher-layer signaling, for example.

[0129] When more than eight TCI states are configured for a UE, a MAC CE may be used to activate (or specify) fewer than eight TCI states. This MAC CE may also be referred to as a TCI States Activation / Deactivation MAC CE for UE-specific PDSCH. The value of the TCI field within the DCI may also indicate one of the TCI states activated by the MAC CE.

[0130] When the UE sets TCI presence information to "enabled" for the CORESET that schedules PDSCH (the CORESET used for PDCCH transmission that schedules PDSCH), the UE may also assume that the TCI field exists in DCI format 1_1 of the PDCCH transmitted on the CORESET.

[0131] In the case where TCI existence information is not set for the CORESET that schedules the PDSCH or the PDSCH is scheduled through DCI format 1_0, when the time offset between the reception of the DL DCI (DCI that schedules the PDSCH) and the reception of the PDSCH corresponding to the DCI is greater than the threshold, in order to determine the QCL of the PDSCH antenna port, the UE may also 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 sent by the PDCCH used to schedule the PDSCH.

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

[0133] In the case where the UE is configured with a single time slot PDSCH, the indicated TCI state may also be based on the activated TCI state in the time slot with the scheduled PDSCH. In the case where the UE is configured with multiple time slot PDSCHs, the indicated TCI state may also be based on the activated TCI state in the initial time slot with the scheduled PDSCH, and the UE may also expect it to be the same across time slots with scheduled PDSCHs. In the case where the UE is configured with a CORESET associated with a search space set for cross-carrier scheduling, when the UE includes TCI presence information for the CORESET as "valid" and at least one of the TCI states configured for the service cells scheduled by the search space set is QCL type D, the UE may also assume that the time offset between the detected PDCCH and the PDSCH corresponding to the PDCCH is above a threshold.

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

[0135] The time offset between the reception of DL DCI and the reception of the PDSCH corresponding to the DCI may also be referred to as a scheduling offset.

[0136] In addition, the above threshold can also be referred to as QCL time duration, "timeDurationForQCL", "Threshold", "Threshold for offset between a DCIindicating a TCI state and a PDSCH scheduled by the DCI", "Threshold-Sched-Offset", scheduling offset threshold, scheduling offset threshold, etc.

[0137] The QCL time length may also be based on UE capabilities, for example, based on the delays in decoding the PDCCH and switching beams. The QCL time length may also be the minimum time required for the UE to receive the PDCCH and apply the spatial QCL information received in the DCI for PDSCH processing. The QCL time length may also be expressed as the number of symbols per subcarrier spacing, or as time (e.g., μs). The information about the QCL time length may also be reported from the UE to the base station as UE capability information, or may be set from the base station to the UE using higher-layer signaling.

[0138] For example, the UE may also assume that the DMRS port of the PDSCH and the DL-RS based on the TCI state activated for the CORESET corresponding to the smallest CORESET-ID are in QCL. The latest time slot may also be the time slot for receiving the DCI scheduling the PDSCH.

[0139] Alternatively, the CORESET-ID may be an ID (an ID for identifying the CORESET, controlResourceSetId) set by the RRC information element "ControlResourceSet".

[0140] When none of the CORESETs are configured for a CC, the default TCI state may be the activated TCI state with the lowest ID applicable to the PDSCH within the activated DL BWP of the CC.

[0141] After Rel.16, when the PDSCH and the PDCCH that schedules it are in different component carriers (CCs) (cross-carrier scheduling), if the delay from PDCCH to PDSCH (PDCCH-to-PDSCH delay) is shorter than the time length for QCL, or if the TCI state does not exist in the DCI used for the scheduling, the UE can also obtain the QCL assumption for the PDSCH scheduled by the activated TCI state with the lowest ID of the PDSCH in the activated BWP of the cell that can be applied to the scheduling.

[0142] <Spatial Relationship for PUCCH>

[0143] For the UE, parameters for PUCCH transmission (PUCCH configuration information, PUCCH-configuration) can also be configured via higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). PUCCH configuration information can also be configured for a portion of the band (e.g., uplink bandwidth part (BWP)) within each carrier (also known as a cell or component carrier (CC)).

[0144] The PUCCH configuration information may also include a list of PUCCH resource set information (eg, PUCCH-ResourceSet) and a list of PUCCH spatial relationship information (eg, PUCCH-SpatialRelationInfo).

[0145] The PUCCH resource set information may also include a list (eg, resourceList) of PUCCH resource indices (IDs, eg, PUCCH-ResourceId).

[0146] In addition, when the UE does not contain dedicated PUCCH resource setting information (e.g., dedicated PUCCH resource configuration) provided by the PUCCH resource set information in the PUCCH setting information (before RRC is established), the UE may also determine the PUCCH resource set based on parameters (e.g., pucch-ResourceCommon) in system information (e.g., System Information Block Type 1 (SIB1) or Remaining Minimum System Information (RMSI)). The PUCCH resource set may also include 16 PUCCH resources.

[0147] On the other hand, when the UE contains the above-mentioned dedicated PUCCH resource setting information (UE-dedicated uplink control channel structure, dedicated PUCCH resource structure) (after RRC is established), the UE can also determine the PUCCH resource set based on the number of UCI information bits.

[0148] The UE may also determine the number of CCEs (N) in the control resource set (CORESET) for PDCCH reception based on the value of a specific 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 for scheduling PDSCH) and the number of CCEs (N) in the control resource set (CORESET) for PDCCH reception that transports the DCI. CCE ), and the index of the front (initial) CCE received by the PDCCH (n CCE，0 ) to determine at least one of the PUCCH resource sets (e.g., a PUCCH resource set dedicated to the cell or determined individually for the UE) a PUCCH resource (index) within the above-mentioned PUCCH resource set.

[0149] PUCCH spatial relationship information (e.g., "PUCCH-spatialRelationInfo" in the RRC information element) may also indicate multiple candidate beams (spatial domain filters) for PUCCH transmission. PUCCH spatial relationship information may also indicate the spatial relationship between RS (Reference Signal) and PUCCH.

[0150] The list of PUCCH spatial relationship information may also include some elements (PUCCH spatial relationship information IE (Information Element)). Each PUCCH spatial relationship information may also include, for example, at least one of an index of the PUCCH spatial relationship information (ID, e.g., pucch-SpatialRelationInfoId), an index of the serving cell (ID, e.g., servingCellId), and information related to the RS with which the PUCCH has a spatial relationship (reference RS).

[0151] For example, the RS-related information may include an SSB index, a CSI-RS index (e.g., an NZP-CSI-RS resource structure ID), an SRS resource ID, and a BWP ID. The SSB index, CSI-RS index, and SRS resource ID may also be associated with at least one of the beam, resource, and port selected by the measurement of the corresponding RS.

[0152] When more than one piece of spatial relation information related to PUCCH is set, the UE may be controlled so that one piece of PUCCH spatial relation information is activated for one PUCCH resource at a time based on the PUCCH spatial relation activation / deactivation MAC CE.

[0153] The PUCCH spatial relationship activation / deactivation MAC CE of Rel.15 NR can also be expressed in 3 octets (8 bits × 3 = 24 bits) of octets (Octet, Oct) 1-3.

[0154] The MAC CE may also include information such as the serving cell ID ("Serving Cell ID" field) of the application object, the BWP ID ("BWP ID" field), and the PUCCH resource ID ("PUCCH Resource ID" field).

[0155] In addition, the MAC CE contains "S i ” (i=0-7) field. UE is in a certain S iIf the field indicates 1, the spatial relationship information of spatial relationship information ID#i is activated. i When the field indicates 0, the spatial relationship information of the spatial relationship information ID#i is deactivated.

[0156] The UE may also activate the PUCCH relation information specified by the MAC CE 3 ms after sending an ACK to the MAC CE for activating specific PUCCH spatial relation information.

[0157] <Spatial Relationship for SRS and PUSCH>

[0158] The UE may also receive information (SRS configuration information, for example, parameters in the "SRS-Config" of the RRC control element) used for transmission of a measurement reference signal (for example, a sounding reference signal (SRS)).

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

[0160] One SRS resource set may be associated with a specific number of SRS resources (or a specific 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).

[0161] The SRS resource set information may also 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.

[0162] Here, the SRS resource type can also represent any one of periodic SRS (Periodic SRS (P-SRS)), semi-persistent SRS (Semi-Persistent SRS (SP-SRS)), and aperiodic SRS (Aperiodic SRS (A-SRS, AP-SRS)). In addition, the UE can also send P-SRS and SP-SRS periodically (or periodically after activation) and send A-SRS based on the SRS request of the DCI.

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

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

[0165] SRS resource information may also include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port sequence number, sending comb, SRS resource mapping (for example, time and / or frequency resource location, resource offset, resource period, number of repetitions, number of SRS code elements, SRS bandwidth, etc.), hopping association information, SRS resource type, sequence ID, SRS spatial relationship information, etc.

[0166] The spatial relationship information of the SRS (e.g., the "spatialRelationInfo" element of the RRC information element) may also indicate the spatial relationship information between a specific reference signal and the SRS. This specific reference signal may also 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).

[0167] The spatial relationship information of the SRS may also include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the above-mentioned specific reference signal.

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

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

[0170] In NR, uplink signal transmission can also be controlled based on the presence or absence of beam correspondence (BC). BC can also be the ability of a node (e.g., base station or UE) to determine the beam used for signal transmission (transmit beam, Tx beam) based on the beam used for signal reception (receive beam, Rx beam).

[0171] In addition, BC can also be called transmit / receive beam correspondence (Tx / Rx beam correspondence), beam reciprocity (beam reciprocity), beam calibration (beam calibration), calibrated / non-calibrated (Calibrated / Non-calibrated), reciprocity calibrated / non-calibrated (reciprocity calibrated / non-calibrated), correspondence, consistency, etc.

[0172] For example, in the absence of BC, the UE may also send uplink signals (e.g., PUSCH, PUCCH, SRS, etc.) using the same beam (spatial domain transmit filter) as the SRS (or SRS resources) indicated from the base station based on the measurement results of one or more SRS (or SRS resources).

[0173] On the other hand, in the presence of BC, the UE may also use the same or corresponding beam (spatial domain transmit filter) as the beam (spatial domain receive filter) used to receive a specific SSB or CSI-RS (or CSI-RS resource) to send uplink signals (such as PUSCH, PUCCH, SRS, etc.).

[0174] When spatial relationship information related to SSB or CSI-RS and SRS is set for a certain SRS resource (for example, when BC is present), the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) used to receive the SSB or CSI-RS. In this case, the UE may also assume that the UE receive beam for the SSB or CSI-RS is the same as the UE transmit beam for the SRS.

[0175] When spatial relationship information about another SRS (reference SRS) and a target SRS (target SRS) is set for a specific SRS (target SRS) resource (for example, when there is no BC), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as that used to transmit the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam for the reference SRS and the UE transmit beam for the target SRS are the same.

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

[0177] When codebook-based transmission is used for PUSCH, the UE may be configured with two SRS resources via RRC, with one of the two SRS resources indicated via DCI (a 1-bit specific field). When non-codebook-based transmission is used for PUSCH, the UE may be configured with four SRS resources via RRC, with one of the four SRS resources indicated via DCI (a 2-bit specific field). Using spatial relationships other than the two or four configured via RRC requires RRC reconfiguration.

[0178] In addition, the spatial relationship of SRS resources used for PUSCH can be configured with DL-RS. For example, for SP-SRS, the UE can be configured with the spatial relationship of multiple (e.g., up to 16) SRS resources through RRC, and one of the multiple SRS resources can be indicated through MAC CE.

[0179] (Default spatial relationship)

[0180] Research is underway on the default spatial relationship. If, in a certain frequency range (e.g., frequency range (FR) 2), spatial relationship information for a dedicated PUCCH (PUCCH based on a dedicated PUCCH configuration (PUCCH-Config)) or a dedicated SRS (SRS based on a dedicated SRS configuration (SRS-Config)) is not configured, in addition to the SRS with beam management usage (usage = 'beamManagement'), the default spatial relationship may be applied to the dedicated PUCCH configuration or dedicated SRS configuration in at least specific circumstances. This specific situation may also be when the path loss reference RS is not configured through RRC signaling.

[0181] For example, when CORESETs are 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 in the path loss calculation may also 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 RS used in the path loss calculation may also be a periodic RS.

[0182] For example, when none of the CORESETs are configured on a CC, the default spatial relationship may be the activated TCI state with the lowest ID applicable to the PDSCH within the activated DL-BWP of the CC.

[0183] The default spatial relationship can also be applied to UEs that support beam correspondence. The default spatial relationship can also be applied to single TRP scenarios.

[0184] When the path loss reference RS is not set, the RS used in the path loss calculation can also be called a default path loss reference RS.

[0185] (Spatial relationship of PUSCH scheduled by DCI format 0_0)

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

[0187] DCI format 0_1 ​​includes SRI, but DCI format 0_0 does not include SRI.

[0188] Therefore, for a cell (eg, a secondary cell (SCell)) in which PUCCH resources are not configured, PUSCH cannot be scheduled using DCI format 0_0.

[0189] If PUCCH on SCell is not configured (PUCCH transmitted on SCell), UCI is transmitted on PCell. If PUCCH on SCell is configured, UCI is transmitted on PUCCH-SCell. Therefore, PUCCH resources and spatial relationship information do not need to be configured for all SCells, and some cells may not have PUCCH resources configured.

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

[0191] In Rel.15 NR, RRC connected mode, frequency range (FR) 2, the UE is not configured with PUCCH resources having PUCCH spatial relationship information and does not expect PUSCH scheduled by DCI format 0_0 within the BWP.

[0192] For the PUSCH scheduled through DCI format 0_0, the following functions 1 and 2 are under study.

[0193] [Function 1]

[0194] In FR2 and RRC connected mode, when no PUCCH resources are configured on a CC, the default spatial relationship and default path loss reference RS for PUSCH scheduled using DCI format 0_0 are supported. This function 1 can be applied to UEs that support the default spatial relationship for dedicated PUCCH or dedicated SRS in Rel.16, or when the default spatial relationship for dedicated PUCCH or dedicated SRS in Rel.16 is configured by the base station.

[0195] Alternatively, RRC parameters can be imported to activate the default spatial relationship function for dedicated PUCCH or dedicated SRS. The default spatial relationship can also be the TCI state or QCL assumption of the core set with the lowest ID. The default path loss reference RS can also be an RS of QCL type D that is the same as the TCI state or QCL assumption of the core set with the lowest ID. The default path loss reference RS can also be a periodic RS.

[0196] [Function 2]

[0197] In FR2 and RRC connected mode, PUSCH scheduling is supported using DCI format 0_0 on CCs with configured PUCCH resources. Here, all configured PUCCH resources are configured without any spatial relationship.

[0198] For PUSCH scheduled using DCI format 0_0, the spatial relationship and path loss reference RS may also be based on the spatial relationship and path loss reference RS for PUCCH resources, respectively. For PUSCH scheduled using DCI format 0_0, the spatial relationship and path loss reference RS for PUCCH resources may also be based on the default spatial relationship and default path loss reference RS for PUCCH resources, respectively.

[0199] Function 1 handles the case where PUCCH resources are not configured, while Function 2 handles the case where PUCCH resources are configured but spatial relations are not configured. The target cell (CC) of Function 2 is a PCell or PUCCH-SCell, and it is assumed that PUCCH resources are configured. When the network uses the default spatial relation function, it is considered that the spatial relation is not configured for PUCCH resources. The target cell of Function 1 is a cell other than a PCell or PUCCH-SCell, and PUCCH resources are not configured.

[0200] (Problem)

[0201] Consider the case where the spatial relationship is not set for some of the multiple configured PUCCH resources. As mentioned above, in Rel.15 NR, the spatial relationship of the lowest PUCCH resource ID is used, so the spatial relationship in this case is unclear. Furthermore, it is unclear which PUCCH resource within the cell is used. If the spatial relationship is unclear, there is a concern that throughput and other system performance may be reduced.

[0202] If the path loss reference RS is not configured and no CORESET is configured on the CC, the RS used for path loss calculation is unclear. If the RS used for path loss calculation is unclear, there is a risk of reduced throughput and other system performance.

[0203] Here, the inventors of the present invention have conceived a method for appropriately determining at least one reference signal used for QCL and path loss calculation for uplink transmission.

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

[0205] In the present disclosure, cell, CC, carrier, BWP, and band may be used interchangeably.

[0206] In this disclosure, index, ID, indicator, and resource ID may be used interchangeably.

[0207] In the present disclosure, the terms "specific UL transmission," "specific UL signal," "specific type of UL transmission," "specific UL channel," "PUSCH," "PUCCH," "SRS," "P-SRS," "SP-SRS," and "A-SRS" may be used interchangeably. In the present disclosure, the terms "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," and "CSI-RS" may also be used interchangeably.

[0208] TCI state, TCI state or QCL assumption, QCL assumption, QCL parameter, spatial domain reception filter, UE spatial domain reception filter, spatial domain filter, UE receive beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D in TCI state or QCL assumption, RS of QCL type A in TCI state or QCL assumption can also be replaced with each other. RS of QCL type D, DL-RS associated with QCL type D, DL-RS with QCL type D, DL-RS source, SSB, and CSI-RS can also be replaced with each other.

[0209] In the present disclosure, the TCI state may also be information related to the receive beam (spatial domain receive filter) indicated (set) for the UE (e.g., DL-RS, QCL type, cell to which DL-RS is transmitted, etc.). QCL assumes transmission or reception based on the associated signal (e.g., PRACH), and may also be information related to the receive beam (spatial domain receive filter) assumed by the UE (e.g., DL-RS, QCL type, cell to which DL-RS is transmitted, etc.).

[0210] In the present disclosure, the terms "latest time slot," "most recent time slot," "latest search space," and "most recent search space" may be interchangeable. In the present disclosure, the terms "lowest ID," "highest ID," and "specified (specific) ID" may be interchangeable. For example, the CORESET with the lowest ID, the CORESET with the highest ID, and the CORESET with a specific ID may be interchangeable. For example, the activated TCI state with the lowest ID, the activated TCI state with the highest ID, and the activated TCI state with a specific ID may be interchangeable.

[0211] In the present disclosure, spatial relationship, spatial relationship information, spatial relationship assumption, QCL parameter, spatial domain transmit filter, UE spatial domain transmit filter, spatial domain filter, UE transmit beam, UL transmit beam, UL precoding, UL precoder, RS of spatial relationship, DL-RS, QCL assumption, SRI, SRI-based spatial relationship, and UL TCI can also be replaced with each other.

[0212] In the present disclosure, the default TCI state, the default QCL, and the default QCL assumption may also be interchangeable. Hereinafter, the TCI state or QCL (QCL assumption) will be primarily labeled as the default TCI state, but the name is not limited thereto. In addition, the definition of the default TCI state is not limited thereto. The default TCI state, for example, for a certain channel / signal (e.g., PDSCH), may be a TCI state assumed when the TCI state / QCL specified by DCI cannot be used, or a TCI state assumed when the TCI state / QCL is not specified (or set).

[0213] In the present disclosure, the default spatial relationship, the default spatial relationship assumption, the RS of the QCL of a specific DL resource, the TCI state or QCL assumption of a specific DL resource, the TCI state or QCL assumption of a specific DL signal, the RS related to the QCL parameters given by the TCI state or QCL assumption of a specific DL signal, the RS of QCL type D in the TCI state or QCL assumption of a specific DL signal, and the spatial relationship of the reference UL transmission can also be replaced with each other.

[0214] In the present disclosure, TRS, tracking CSI-RS, CSI-RS with TRS information (higher layer parameter trs-Info), and NZP-CSI-RS resources within an NZP-CSI-RS resource set with TRS information may also be interchangeable.

[0215] In the present disclosure, DCI format 0_0, DCI not including SRI, DCI not including spatial relationship indication, and DCI not including CIF can also be replaced with each other. In the present disclosure, DCI format 0_1, DCI including SRI, DCI including spatial relationship indication, and DCI including CIF can also be replaced with each other.

[0216] The terms path loss reference RS, path loss reference RS, path loss estimation RS, path loss calculation RS, path loss (PL)-RS, index qd, RS for path loss calculation, RS resource for path loss calculation, and calculation RS are interchangeable. Calculation, estimation, and measurement are also interchangeable.

[0217] In the present disclosure, "UE sends a specific UL transmission based on the default spatial relationship", "UE uses the spatial relationship of the specific UL transmission for the default spatial relationship", "UE assumes (regards) the spatial relationship of the specific UL transmission to be the same as the RS of the default spatial relationship", and "UE assumes (regards) the spatial relationship of the specific UL transmission to be the same as the RS of QCL type D of the default spatial relationship" can also be replaced with each other.

[0218] (Wireless Communication Method)

[0219] Default Spatial Relationship Application Conditions

[0220] If the default spatial relationship application conditions are met, the UE may also apply the default spatial relationship in the spatial relationship of a specific UL transmission. The specific UL transmission may also be at least one of PUSCH, PUCCH, SRS, P-SRS, SP-SRS, and A-SRS.

[0221] The default spatial relationship application condition can be obtained by the logical sum of multiple default spatial relationship application conditions, the logical product of multiple default spatial relationship application conditions, or the combination of the logical sum and the logical product of multiple default spatial relationship application conditions.

[0222] A specific UL transmission may be within a specific frequency range (e.g., frequency range (FR) 2), or may be an UL transmission based on a dedicated PUCCH configuration or a dedicated SRS configuration, excluding an SRS with beam management usage (usage = 'beamManagement') and an SRS with associated CSI-RS (associatedCSI-RS) configuration and based on non-codebook transmission usage (usage = 'nonCodebook'). A specific UL transmission may also be a PUSCH scheduled using DCI format 0_0. For example, a specific UL transmission may also be a PUSCH on a cell scheduled using DCI format 0_0 when PUCCH resources (e.g., dedicated PUCCH resources) with a spatial relationship (e.g., an activated spatial relationship) within the cell's activated ULBWP are not configured. A specific UL transmission may also be an SRS based on SRS resources of multiple time slots within an SRS resource set for cross-antenna switching usage (usage = 'antennaSwitching').

[0223] The default spatial relationship application conditions may also include: no spatial relationship information is configured for a specific UL transmission; the specific UL transmission is within a frequency range (e.g., frequency range (FR) 2); the specific UL transmission is based on a dedicated PUCCH configuration or a dedicated SRS configuration other than an SRS with beam management usage (usage = 'beamManagement') and an SRS with non-codebook-based transmission usage (usage = 'nonCodebook') including an associated CSI-RS (associated CSI-RS); and the UE supports at least one of the beam correspondences. The spatial relationship information for the specific UL transmission may also be spatial relationship information within a dedicated PUCCH configuration or a dedicated SRS configuration. The associated CSI-RS may also be the ID (index) of a CSI-RS resource associated with an SRS resource set in non-codebook-based transmission.

[0224] The default spatial relationship application condition may also include: for a specific UL transmission, the path loss reference RS is not configured. The default spatial relationship application condition may also include: for a specific UL transmission, the path loss reference RS is not configured through higher layer signaling.

[0225] The default spatial relationship application condition may also include: only one TCI state is activated for the PDCCH (the number of activated TCI states for the PDCCH is 1). According to the default spatial relationship application condition, the UE operation becomes simple.

[0226] The default spatial relationship application condition may also include: only one TCI state is activated for PDCCH and PDSCH (the number of activated TCI states for PDCCH and PDSCH is 1). When a single activated beam is used for UL and DL, UE operation becomes simple.

[0227] The default spatial relationship application condition may also include: 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 is not limited to being able to apply the same beam to the PDCCH and PUCCH, so by excluding cross-carrier scheduling, the UE operation becomes simpler. For example, in the case of inter-band carrier aggregation (CA), it can be considered that different beams are applied to the PDCCH and PUCCH. In addition, 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 can be considered that the UE cannot determine the beam.

[0228] The default spatial relationship application condition may also include not using inter-domain CA.

[0229] The default spatial relationship application condition may also include that a specific UL transmission SRI for PUSCH does not exist. The default spatial relationship application condition may also include that an SRS resource corresponding to the SRI for PUSCH does not exist.

[0230] The default spatial relationship application condition may include that spatial relationship information is not set for at least one SRS resource in the SRS resource set.

[0231] The default spatial relationship may also be the RS of the QCL of a specific DL resource. The RS of the QCL of a specific DL resource, the RS related to the QCL parameters of a specific DL resource, the RS for the QCL of a specific DL resource, and the RS of QCL type D for a specific DL resource may also be replaced with each other.

[0232] The RS of the default spatial relationship can be either a QCL type D RS or a QCL type A RS, and if applicable, it can also be a QCL type D RS or a QCL type A RS.

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

[0234] If the path loss reference signal (path loss reference RS) is not set for a specific uplink transmission (for a specific uplink transmission, the default path loss reference RS application conditions are met), the UE can also calculate the path loss based on at least one quasi-co-site (QCL) parameter corresponding to at least one specific DL resource (for example, a specific CORESET, a specific PDCCH, a specific SSB) to determine the reference signal used in the path loss calculation (for example, the default path loss reference RS, the calculation RS).

[0235] Default Spatial Relationships

[0236] The default spatial relationship may also be the RS of the QCL of a specific DL resource.

[0237] RS of QCL for a specific DL resource, default TCI state or default QCL assumption for a specific DL resource, lowest CORESET in the most recent time slot The TCI status of the CORESET with the ID, one or more CORESETs within the activated BWP of the serving cell have the lowest CORESET-ID in the latest time slot monitored by the UE, the RS related to the QCL parameters of the CORESET associated with the monitored search space and the QCL indication used for the PDCCH, the TCI status or QCL assumption of the CORESET with the lowest CORESET-ID in the latest time slot and associated with the monitored search space, the TCI status or QCL assumption of the CORESET with the lowest CORESET-ID in a specific time slot and associated with the monitored search space, the TCI status or QCL assumption of the specific CORESET, the TCI status or QCL assumption of the DL signal corresponding to the specific UL transmission (for example, 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 the specific UL transmission), the RS related to the QCL parameters of the specific DL resources, and the RS for the QCL of the specific DL resources can also be replaced with each other.

[0238] The RS of the default spatial relationship or the default TCI state or the default QCL assumption can be either the RS of QCL type D or the RS of QCL type A. If applicable, it can also be the RS of QCL type D or the RS of QCL type A.

[0239] The latest time slot may also be the latest time slot for a specific DL resource. The latest time slot may also be the latest time slot of the starting codeword for a specific UL transmission (or before the codeword). The latest time slot may also be the latest time slot of the first or last codeword for the DL signal corresponding to the specific UL transmission (before the codeword). For example, when the specific UL transmission is a PUCCH, the DL signal corresponding to the specific UL transmission may also be the PDSCH corresponding to the PUCCH (the PDSCH corresponding to the HARQ-ACK transmitted on the PUCCH).

[0240] The spatial relationship of a specific UL transmission may also be the default QCL of the PDSCH.

[0241] When CORESET is set on the CC to which the default spatial relationship is applied, the default QCL of PDSCH may also be the TCI state corresponding to the lowest CORESET ID of the most recent time slot or the most recent search space. On the CC to which the default spatial relationship is applied, if no CORESET is set, the default QCL of PDSCH can be applied to the PDSCH within the activated DL BWP of the CC, or it may be the activated TCI state with the lowest ID.

[0242] The specific DL resource may also be PDSCH.

[0243] The default spatial relationship may also be one of the activated TCI states (activated TCI states) of the CORESET.

[0244] There can also be multiple TCI states active for a CORESET. In this case, the active TCI state selected as the default spatial relation can be either the default RS, the default TCI state, or the default QCL assumption.

[0245] The specific DL resource may also be PDCCH.

[0246] In the case where a specific UL transmission corresponds to a PDCCH (aperiodic PDCCH or aperiodic SRS) (in the case where a specific UL transmission is scheduled or triggered by a PDCCH (DL DCI) for PDSCH scheduling), the spatial relationship of the specific UL transmission may also be the TCI state of the PDCCH. The specific UL transmission may be either an A-SRS triggered by the PDCCH or a PUCCH that transmits HARQ-ACK for the PDSCH scheduled by the PDCCH. For example, in the case where the specific UL transmission is an A-SRS, the PDCCH corresponding to the specific UL transmission may also be the PDCCH that triggers the A-SRS. In addition, for example, in the case where the specific UL transmission is a PUCCH that transmits HARQ-ACK, the PDCCH corresponding to the specific UL transmission may also be a PDCCH that schedules the PDSCH and indicates the timing of the HARQ-ACK of the PDSCH. In the case where the specific UL transmission does not correspond to the PDCCH, the spatial relationship of the specific UL transmission may also be the same as the aforementioned A-1.

[0247] The specific DL resource may also be PDCCH or PDSCH.

[0248] The default spatial relationship may also be the QCL assumption of CORESET#0 (the CORESET with an ID of 0).

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

[0250] The spatial relationship of a specific UL transmission can also be the RS used in the path loss calculation of Rel.15 (Rel.15 calculation RS, TCI status of the RS used in the path loss calculation). The RS used in the path loss calculation, the RS resource used in the path loss calculation, the calculation RS, and the default path loss reference RS can also be replaced with each other.

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

[0252] The calculated RS may also be the path loss reference RS with 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 is not given PUCCH spatial relationship information (PUCCH-SpatialRelationInfo), the calculated RS may also be the reference signal (reference signal) in the PUCCH path loss reference RS with index 0 in the PUCCH path loss reference RS information (PUCCH-PathlossReferenceRS) and the PUCCH path loss reference RS-ID (PUCCH-PathlossReferenceRS-Id).

[0253] <Implementation Method 1>

[0254] PUSCH scheduling using DCI format 00 on a CC with configured PUCCH resources may also be supported. Among the configured PUCCH resources, the PUCCH resource with the lowest ID may not have a spatial relationship (spatial relationship information, PUCCH-SpatialRelationInfo) (the PUCCH resource with the lowest ID may not be configured with a spatial relationship).

[0255] In FR2 and RRC connected mode, PUSCH scheduling using DCI format 0_0 may be supported on a CC with configured PUCCH resources. Among the configured PUCCH resources, the PUCCH resource with the lowest ID may not have a spatial relationship.

[0256] In FR2 and RRC connected mode, PUSCH scheduling using DCI format 00 may be supported within the activated UL BWP of a CC with configured PUCCH resources. The PUCCH resource with the lowest ID among the configured PUCCH resources of the activated UL BWP may not have a spatial relationship.

[0257] The condition for supporting the scheduling of PUSCH using DCI format 0_0 may also include that the path loss reference RS for the PUSCH is not set.

[0258] The spatial relationship for the PUSCH scheduled using DCI format 0_0 may also be based on the spatial relationship for the PUCCH resource (e.g., the PUCCH resource with the lowest ID) or the default spatial relationship. For the PUSCH scheduled using DCI format 0_0, the RS used in the path loss calculation may also be based on the path loss reference RS for the PUCCH resource (e.g., the PUCCH resource with the lowest ID) or the default path loss reference RS.

[0259] For example, Figure 2 As shown, if the PUCCH resource with the lowest ID is configured without spatial relationship information (S10: Yes), the PUSCH can be scheduled using DCI format 0_0 (S20). If the PUCCH resource with the lowest ID is not configured without spatial relationship information (S10: No), the PUSCH cannot be scheduled using DCI format 0_0 (S30).

[0260] <Implementation Method 2>

[0261] In FR2 and RRC connected mode, when there are no PUCCH resources configured within the CC's active UL BWP, the default spatial relationship and default path loss reference RS for PUSCH scheduled using DCI format 0_0 are supported. This function can be applied to UEs that support the default spatial relationship for dedicated PUCCH or dedicated SRS in Rel.16, or when the default spatial relationship for dedicated PUCCH or dedicated SRS in Rel.16 is configured by the base station.

[0262] RRC parameters can also be imported to activate the default spatial relationship function for dedicated PUCCH or dedicated SRS. The default spatial relationship can also be the TCI state or QCL assumption of the core set with the lowest ID. The default path loss reference RS can also be an RS of QCL type D that is the same as the TCI state or QCL assumption of the core set with the lowest ID. The default path loss reference RS can also be a periodic RS.

[0263] <Implementation Method 3>

[0264] In FR2 and RRC connected mode, PUSCH is scheduled using DCI format 0_0 within the active UL BWP of a CC with configured PUCCH resources. Here, all configured PUCCH resources within the active UL BWP are configured without any spatial relationship.

[0265] For PUSCH scheduled using DCI format 0_0, the spatial relationship and path loss reference RS may also be based on the spatial relationship and path loss reference RS for PUCCH resources, respectively. For PUSCH scheduled using DCI format 0_0, the spatial relationship and path loss reference RS for PUCCH resources may also be based on the default spatial relationship and default path loss reference RS for PUCCH resources, respectively.

[0266] <Implementation Method 4>

[0267] UE capability information indicating at least one of whether the UE is set to the default spatial relationship, whether the UE supports the default path loss reference RS, and which of implementation modes 1 to 3 the UE supports may also be reported. UE capability information may also indicate whether the UE is set to the default spatial relationship, whether the UE supports the default path loss reference RS, and which of implementation modes 1 to 3 the UE supports. A single piece of UE capability information may also indicate all of the following: whether the UE is set to the default spatial relationship, whether the UE supports the default path loss reference RS, and which of implementation modes 1 to 3 the UE supports.

[0268] <Implementation Method 5>

[0269] When at least one of the RRC parameters indicating the application of the default spatial relationship, the application of the default path loss reference RS, and the application of one of the operations of implementation modes 1 to 3 is set, the UE may also perform the set operation. When the RRC parameter is not set, the UE may also perform the Rel.15 operation. The RRC parameter may also indicate the application of the default spatial relationship, the application of the default path loss reference RS, and the application of one of the operations of implementation modes 1 to 3. A single RRC parameter may also indicate the application of the default spatial relationship, the application of the default path loss reference RS, and the application of all of the operations of implementation modes 1 to 3.

[0270] <Implementation Method 6>

[0271] The RS used in the path loss calculation (default path loss reference RS) may also be a QCL type D RS in the activated TCI state for the lowest ID of the PDSCH. The default spatial relationship and the default path loss reference RS may also be combined. The UE may also perform at least one of operations 1 or 2 below.

[0272] Operation 1

[0273] For dedicated PUCCH or dedicated SRS in FR2, when the path loss reference RS is not set through RRC signaling, the default spatial relationship may also be as follows.

[0274] When a core set is configured on a CC, the default spatial relationship may be the TCI state or QCL assumption of the core set with the lowest ID. The RS used in the path loss calculation may also be a QCL type D RS with the same TCI state or QCL assumption as the core set with the lowest ID. The RS used in the path loss calculation may also be a periodic RS.

[0275] In the case where no CORESET1 is configured on a CC, the default spatial relationship may also be the activated TCI state with the lowest ID that can be applied to the PDSCH in the activated DL-BWP of the CC.

[0276] The RS used in the path loss calculation may also be the RS of QCL type D with the lowest ID and the activated TCI state for the PDSCH.

[0277] Operation 2

[0278] In the case where the path loss reference RS is set through RRC signaling for a dedicated PUCCH or dedicated SRS in FR2, the default spatial relationship may also be as follows.

[0279] When a CORESET is configured on a CC, the default spatial relationship may also be the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used in the path loss calculation 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, or a configured or activated path loss reference RS. The RS used in the path loss calculation may also be a periodic RS.

[0280] In the case where no CORESET1 is configured on a CC, the default spatial relationship may also be the activated TCI state with the lowest ID that can be applied to the PDSCH in the activated DL-BWP of the CC.

[0281] The RS used in the path loss calculation can be either the RS of QCL type D with the lowest ID and activated TCI state for PDSCH, or a configured or activated path loss reference RS.

[0282] For example, Figure 3As shown, when the UE uses the default spatial relationship for the dedicated PUCCH or dedicated SRS in FR2 and the path loss reference RS is configured (S10: Yes), 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 the dedicated PUCCH or dedicated SRS in FR2 and the path loss reference RS is not configured (S10: No), the UE uses the default path loss reference RS (S30).

[0283] <Implementation Method 7>

[0284] The UE may also determine a default spatial relationship for the SRS and at least one default path loss reference RS based on whether the spatial relationship of the SRS resources indicated by the SRI for the PUSCH and at least one of the path loss reference RSs are set, and apply the determined default spatial relationship and at least one default path loss reference RS to the PUSCH. The determination of the default spatial relationship for the SRS and at least one default path loss reference RS may also be based on the aforementioned determination method (e.g., at least one of Embodiments 1 to 6). The UE may also perform at least one of the following operations 1, 2, 3, or 4.

[0285] Operation 1

[0286] In FR2, if a PUSCH is scheduled using DCI format 0_1 ​​and the spatial relationship is not configured for the SRS resource indicated by the SRI, and a path loss reference RS is configured, then if a CORESET is configured on the CC, the default spatial relationship for the PUSCH may also be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used in the path loss calculation for the PUSCH may be either an RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID, or a configured or activated path loss reference RS. The RS used in the path loss calculation may also be a periodic RS.

[0287] In this case, if no CORESET1 is configured on the CC, the default spatial relationship for the PUSCH may be the activated TCI state with the lowest ID applicable to the PDSCH within the CC's activated DL-BWP. In this case, the RS used in the path loss calculation for the PUSCH may be either a QCL type D RS with the activated TCI state with the lowest ID for the PDSCH, or a configured or activated path loss reference RS. The RS used in the path loss calculation may also be a periodic RS.

[0288] Operation 2

[0289] In FR2, if a PUSCH is scheduled using DCI format 0_1 ​​and the spatial relationship is not configured for the SRS resources indicated by the SRI, and the path loss reference RS is not configured, then if a CORESET is configured on the CC, the default spatial relationship for the PUSCH may be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used in the path loss calculation for the PUSCH may be an RS of the same QCL type D as the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used in the path loss calculation may also be a periodic RS.

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

[0291] Operation 3

[0292] In FR2, if a PUSCH is scheduled using DCI format 0_1 ​​and the spatial relationship is not configured for the SRS resources indicated by the SRI, and the path loss reference RS is not configured, then if a CORESET is configured on the CC, the default spatial relationship for the PUSCH may also be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used in the path loss calculation for the PUSCH may be either an RS of QCL type D that is the same as the TCI state or QCL assumption of the CORESET with the lowest ID, or a configured or activated path loss reference RS. The RS used in the path loss calculation may also be a periodic RS.

[0293] In this case, if no CORESET1 is configured on the CC, the default spatial relationship for the PUSCH may be the activated TCI state with the lowest ID applicable to the PDSCH within the CC's activated DL-BWP. In this case, the RS used in the path loss calculation for the PUSCH may be either a QCL type D RS with the activated TCI state with the lowest ID for the PDSCH, or a configured or activated path loss reference RS. The RS used in the path loss calculation may also be a periodic RS.

[0294] Operation 4

[0295] In FR2, if a PUSCH is scheduled using DCI format 0_1 ​​and the spatial relationship is not configured for the SRS resource indicated by the SRI, and a path loss reference RS is configured, then if a CORESET is configured on the CC, the default spatial relationship for the PUSCH may be the TCI state or QCL assumption of the CORESET with the lowest ID. In this case, the RS used in the path loss calculation for the PUSCH may be an RS of the same QCL type D as the TCI state or QCL assumption of the CORESET with the lowest ID. The RS used in the path loss calculation may also be a periodic RS.

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

[0297] The PUSCH scheduled via DCI format 0_1 ​​may also have a different SRI field size (number of bits) depending on the number of SRS resources in the SRS resource set configured for codebook-based or non-codebook transmission. For example, if the number of SRS resources is 1, the SRI field size is 0 bits, and if the number of SRS resources is 2, the SRI field size is 1 bit. The aforementioned "SRS resource indicated by the SRS" may also include: an SRS resource when the number of SRS resources is 1 (only one SRS resource in an SRS resource set configured for codebook-based or non-codebook transmission).

[0298] (Wireless Communication System)

[0299] The following describes the configuration of a wireless communication system according to an embodiment of the present disclosure. In this wireless communication system, communication is performed using one or a combination of the wireless communication methods according to the above-described embodiments of the present disclosure.

[0300] Figure 4 This figure shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may also be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP) or the fifth generation mobile communication system New Radio (5G NR).

[0301] In addition, the wireless communication system 1 can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple radio access technologies (Radio Access Technology (RAT)). MR-DC can also 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 (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

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

[0304] The wireless communication system 1 may also include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are narrower than the macrocell C1. User terminals 20 may also be located within at least one of the cells. The arrangement and number of cells and user terminals 20 are not limited to those shown. Hereinafter, when not distinguishing between base stations 11 and 12, they are collectively referred to as base stations 10.

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

[0306] Each CC may also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may also be included in FR1, and the small cell C2 may also be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these. For example, FR1 may also be equivalent to a frequency band higher than FR2.

[0307] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0308] Multiple base stations 10 can also be connected by wired (for example, optical fiber compliant with the Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (for example, NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, the base station 11 equivalent to the upper station can also be called an integrated access backhaul link (Integrated Access Backhaul (IAB)) host, and the base station 12 equivalent to the relay station (relay) can also be called an IAB node.

[0309] The base station 10 may also be connected to the core network 30 via other base stations 10 or directly. The core network 30 may also include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0310] The user terminal 20 may also be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0311] In the wireless communication system 1, a radio access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), or single carrier frequency division multiple access (SC-FDMA) may be used.

[0312] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the radio access schemes for UL and DL.

[0313] In the wireless communication system 1, as downlink channels, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH))), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. can also be used.

[0314] In addition, in the wireless communication system 1, as uplink channels, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH))), a random access channel (Physical Random Access Channel (PRACH)), etc. can also be used.

[0315] User data, higher-layer control information, and system information blocks (SIBs) are transmitted via the PDSCH. User data, higher-layer control information, and the like can also be transmitted via the PUSCH. Furthermore, the Master Information Block (MIB) can also be transmitted via the PBCH.

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

[0317] In addition, the DCI that schedules the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI that schedules the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, PDSCH may also be replaced by DL data, and PUSCH may also be replaced by UL data.

[0318] In PDCCH detection, a control resource set (CORESET) and a search space can also be used. A CORESET corresponds to the resources for searching for DCI. A search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a search space based on the search space settings.

[0319] A search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. Furthermore, the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," and "CORESET setting" in this disclosure may be used interchangeably.

[0320] Uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also known as hybrid automatic repeat request confirmation (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) can also be transmitted via the PUCCH. The random access preamble used to establish a connection with a cell can also be transmitted via the PRACH.

[0321] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Furthermore, various channels may be expressed without adding "Physical" at the beginning.

[0322] In wireless communication system 1, synchronization signals (Synchronization Signal (SS)), downlink reference signals (Downlink Reference Signal (DL-RS)), etc. can also be transmitted. In wireless communication system 1, as DL-RS, cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), phase tracking reference signals (PTRS), etc. can also be transmitted.

[0323] For example, a synchronization signal may be at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SSs (PSS, SSS) and PBCH (and DMRS for PBCH) may also be referred to as an SS / PBCH block, SS Block (SSB), etc. Furthermore, SSs and SSBs may also be referred to as reference signals.

[0324] In addition, in wireless communication system 1, an uplink reference signal (UL-RS), a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. can also be transmitted. In addition, DMRS can also be called a user terminal specific reference signal (UE-specific Reference Signal).

[0325] (Base Station)

[0326] Figure 5 This figure shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Furthermore, more than one of each of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0327] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, but it is also assumed that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0328] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which this disclosure relates.

[0329] The control unit 110 may also control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission, reception, measurement, etc. using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140. The control unit 110 may also generate data, control information, sequences, etc. to be transmitted as signals and forward them to the transceiver unit 120. The control unit 110 may also perform call processing (setting up, releasing, etc.) of communication channels, manage the status of the base station 10, manage radio resources, etc.

[0330] The transceiver unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, and the like, which are described based on common knowledge in the technical fields involved in this disclosure.

[0331] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured as a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0332] The transmitting and receiving antenna 130 can be formed of an antenna described based on common knowledge in the technical field to which this disclosure relates, such as an array antenna.

[0333] The transmitting and receiving unit 120 may also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the aforementioned uplink channel, uplink reference signal, etc.

[0334] The transmitting and receiving unit 120 may also form at least one of a transmitting beam and a receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0335] The sending and receiving unit 120 (sending processing unit 1211) can also perform processing on the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (for example, RLC retransmission control), the Medium Access Control (MAC) layer (for example, HARQ retransmission control), etc. on the data and control information obtained from the control unit 110 to generate a bit string to be sent.

[0336] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, discrete Fourier transform (DFT) processing (as needed), inverse fast Fourier transform (IFFT) processing), precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent to output a baseband signal.

[0337] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0338] On the other hand, the transmitting and receiving unit 120 (RF unit 122 ) may also perform amplification, filter processing, and demodulation into a baseband signal on the radio frequency band signal received by the transmitting and receiving antenna 130 .

[0339] The transmitting and receiving unit 120 (receiving processing unit 1212) can also apply analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

[0340] The transmitting and receiving unit 120 (measuring unit 123) may also perform measurements related to the received signal. For example, the measuring unit 123 may also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc. based on the received signal. The measuring unit 123 may also 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 also be output to the control unit 110.

[0341] The transmission path interface 140 can also send and receive signals (backhaul signaling) between devices included in the core network 30 and other base stations 10, etc., and obtain and transmit user data (user plane data) and control plane data for the user terminal 20.

[0342] In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 120 , the transmitting and receiving antenna 130 , and the transmission path interface 140 .

[0343] (User Terminal)

[0344] Figure 6 This figure shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Furthermore, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided in one or more units.

[0345] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and the user terminal 20 may also be assumed to have other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0346] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which this disclosure relates.

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

[0348] The transceiver unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, and the like, which are described based on common knowledge in the technical fields involved in this disclosure.

[0349] The transmitting and receiving unit 220 may be configured as an integrated transmitting and receiving unit or may be composed of a transmitting unit and a receiving unit. The transmitting unit may also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0350] The transmitting and receiving antenna 230 can be formed of an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0351] The transmitting and receiving unit 220 may also receive the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the aforementioned uplink channel, uplink reference signal, etc.

[0352] The transmitting and receiving unit 220 may form at least one of a transmitting beam and a receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0353] The sending and receiving unit 220 (sending processing unit 2211) can also perform PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, HARQ retransmission control), etc. on the data and control information obtained from the control unit 210 to generate a bit string to be sent.

[0354] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent to output a baseband signal.

[0355] In addition, whether or not to apply DFT processing may also be based on the transform precoding setting. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transmitting / receiving unit 220 (transmitting processing unit 2211) may perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, DFT processing is not performed as the above-mentioned transmission processing.

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

[0357] On the other hand, the transmitting and receiving unit 220 (RF unit 222 ) may also perform amplification, filter processing, and demodulation into a baseband signal on the radio frequency band signal received by the transmitting and receiving antenna 230 .

[0358] The transmitting and receiving unit 220 (receiving processing unit 2212) can also apply receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

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

[0360] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be constituted by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230 .

[0361] The transmitting and receiving unit 220 receives configuration information that does not include spatial relationship information and indicates the physical uplink control channel (PUCCH) resource with the lowest ID. The control unit 210 can also control the reception of the physical uplink shared channel (PUSCH) scheduled using downlink control information (DCI) format 0_0.

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

[0363] The transmitting and receiving unit 220 may also receive the DCI format 0_0 in the activated uplink bandwidth part (BWP) in which the PUCCH resources are set.

[0364] The transmitting and receiving unit 220 may also receive configuration information for uplink transmission of one of the physical uplink control channel (PUCCH) and the sounding reference signal (SRS). The configuration information may not include spatial relationship information and information about the reference signal for path loss reference. The control unit 210 may also use the reference signal with the lowest ID for the activated transmission control indication (TCI) state for the physical downlink shared channel (PDSCH) in the path loss calculation for the uplink transmission.

[0365] The reference signal may also be used in path loss calculations for the Physical Uplink Shared Channel (PUSCH).

[0366] The reference signal may also be of quasi co-located (QCL) type D.

[0367] (Hardware Structure)

[0368] In addition, the block diagrams used for the description of the above-mentioned embodiments represent blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a device that is physically or logically combined, or two or more devices that are physically or logically separated can be directly or indirectly (for example, using wired, wireless, etc.) connected and implemented using these multiple devices. The functional block can also be implemented by combining software in the above-mentioned one device or the above-mentioned multiple devices.

[0369] Here, the term "function" includes, but is not limited to, judging, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (structural unit) that performs a transmitting function may also be referred to as a transmitting unit, a transmitter, or the like. As described above, the implementation method is not particularly limited.

[0370] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 7 This figure shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. The base station 10 and user terminal 20 described above may also be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0371] In addition, in this disclosure, the terms "apparatus," "circuit," "device," "section," and "unit" are interchangeable. The hardware structure of the base station 10 and the user terminal 20 may include one or more of the illustrated devices, or may exclude some of the devices.

[0372] For example, only one processor 1001 is shown, but multiple processors may be provided. Furthermore, a process may be performed by a single processor, or by two or more processors simultaneously, sequentially, or using other methods. Furthermore, the processor 1001 may be implemented using one or more chips.

[0373] The various functions in the base station 10 and the user terminal 20 are realized, for example, by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations, controls the communication via the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0374] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be configured as a central processing unit (CPU) including interfaces with peripheral devices, a control device, a computing device, registers, and the like. For example, at least a portion of the aforementioned control unit 110 (210) and the transceiver unit 120 (220) may also be implemented by the processor 1001.

[0375] In addition, the processor 1001 reads programs (program code), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and performs various processes according to them. As a program, a program that causes the computer to execute at least a part of the operations described in the above-mentioned embodiments is used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated by the processor 1001, and the same can be achieved for other functional blocks.

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

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

[0378] The communication device 1004 is hardware (a transmitting and receiving device) used to communicate between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may also include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., for example, to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the aforementioned transmitting and receiving unit 120 (220), transmitting and receiving antenna 130 (230), etc. may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be implemented so that the transmitting unit 120a (220a) and the receiving unit 120b (220b) are physically or logically separated.

[0379] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to the outside (e.g., a display, speaker, LED light, etc.). Alternatively, the input device 1005 and the output device 1006 may be integrated (e.g., a touch panel).

[0380] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or different buses between the devices.

[0381] Furthermore, the base station 10 and the user terminal 20 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and may use such hardware to implement part or all of each functional block. For example, the processor 1001 may also be implemented using at least one of these hardware components.

[0382] (Variation)

[0383] In addition, the terms described in this disclosure and the terms required for understanding this disclosure may also be replaced with terms having the same or similar meanings. For example, channel, code element, and signal (signal or signaling) may also be replaced with each other. In addition, a signal may also be a message. A reference signal may also be abbreviated as RS, or may be referred to as a pilot, pilot signal, etc. depending on the applied standard. In addition, a component carrier (CC) may also be referred to as a cell, frequency carrier, carrier frequency, etc.

[0384] A radio frame can also be composed of one or more periods (frames) in the time domain. Each period (frame) of the one or more periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (for example, 1ms) that is independent of the parameter set (numerology).

[0385] Here, a parameter set may also be a communication parameter applied to at least one of the transmission and reception of a signal or channel. A parameter set (numerology) may also represent, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, specific windowing processing performed by the transmitter and receiver in the time domain, and the like.

[0386] A time slot may also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. In addition, a time slot may also be a time unit based on a parameter set.

[0387] A time slot may also contain multiple mini-slots. Each mini-slot may also be composed of one or more symbols in the time domain. Furthermore, a mini-slot may also be referred to as a sub-slot. A mini-slot may also be composed of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as PDSCH (PUSCH) mapping type B.

[0388] Radio frames, subframes, time slots, mini-slots, and symbols all represent time units used for signal transmission. Radio frames, subframes, time slots, mini-slots, and symbols may also be referred to by their respective names. Furthermore, the terms frame, subframe, time slot, mini-slot, and symbol may be used interchangeably in this disclosure.

[0389] For example, a subframe can be called a TTI, multiple consecutive subframes can be called a TTI, and a time slot or a mini-time slot can be called a TTI. In other words, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. Furthermore, the unit representing a TTI can be called a time slot, a mini-time slot, or the like, rather than a subframe.

[0390] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communications. For example, in the LTE system, a base station schedules each user terminal by allocating radio resources (such as the available frequency bandwidth and transmit power) in TTI units. The definition of TTI is not limited to this.

[0391] The TTI can be a unit of time for transmitting data packets (transport blocks), code blocks, code words, etc. after channel coding, and can also be a unit of processing for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the time interval (e.g., the number of symbols) to which the transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

[0392] Furthermore, when one time slot or one mini-time slot is referred to as a TTI, one or more TTIs (i.e., one or more time slots or one or more mini-time slots) can also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) that constitute this minimum time unit for scheduling can also be controlled.

[0393] A TTI having a time length of 1 ms may also 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 time slot, etc. A TTI shorter than a normal TTI may also 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 subslot, a time slot, etc.

[0394] In addition, long TTI (for example, normal TTI, subframe, etc.) can also be replaced by TTI with a time length exceeding 1ms, and short TTI (for example, shortened TTI, etc.) can also be replaced by TTI with a TTI length smaller than long TTI and longer than 1ms.

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

[0396] In addition, an RB may also include one or more symbols in the time domain, and may be the length of one slot, one mini-slot, one subframe, or one TTI. One TTI, one subframe, etc. may also be composed of one or more resource blocks.

[0397] In addition, one or more RBs may also be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.

[0398] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0399] A Bandwidth Part (BWP) (also referred to as a fractional bandwidth) can also represent a subset of contiguous common resource blocks (RBs) used for a particular parameter set within a particular carrier. Common RBs can also be identified by their index relative to the common reference point for that carrier. PRBs can also be defined by a BWP and assigned a sequence number within that BWP.

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

[0401] At least one of the configured BWPs may be activated, and the UE may not assume that it will transmit or receive specific signals / channels outside of the activated BWP. In addition, "cell", "carrier", etc. in this disclosure may also be replaced with "BWP".

[0402] The structures of radio frames, subframes, slots, mini-slots, and symbols described above are merely examples. For example, the number of subframes in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots within a slot, the number of symbols and RBs within a slot or mini-slot, the number of subcarriers within an RB, the number of symbols within a TTI, the symbol length, and the cyclic prefix (CP) length can be varied in various ways.

[0403] Furthermore, information and parameters described in this disclosure may be expressed using absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may be indicated by specific indexes.

[0404] The names used for parameters, etc. in this disclosure are not intended to be limiting in any way. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore the names assigned to these channels and information elements are not intended to be limiting in any way.

[0405] Information, signals, and the like described in this disclosure may also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like referred to throughout the foregoing description may also be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0406] Furthermore, information, signals, etc. can be output from at least one of a higher layer (upper layer) to a lower layer (lower layer), and from a lower layer to a higher layer. Information, signals, etc. can also be input and output via multiple network nodes.

[0407] Input and output information, signals, etc. can be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, signals, etc. can be overwritten, updated, or appended. Output information, signals, etc. can also be deleted. Input information, signals, etc. can also be sent to other devices.

[0408] The notification of information is not limited to the methods / implementations described in the present disclosure, and other methods may also be used. For example, the notification of information in the present disclosure may also be implemented through physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI))), high-layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB)), system information block (SIB), etc.), medium access control (MAC) signaling), other signals, or a combination thereof.

[0409] In addition, 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. In addition, RRC signaling may also be referred to as RRC message, for example, RRC Connection Setup message, RRC Connection Reconfiguration message, etc. In addition, MAC signaling may also be notified using MAC Control Element (CE), for example.

[0410] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0411] The judgment can be made by a value represented by 1 bit (0 or 1), a true or false value (Boolean value) represented by true (true) or false (false), or by comparing numerical values ​​(for example, comparison with a specific value).

[0412] Whether software is referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, it shall be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or the like.

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

[0414] The terms "system" and "network" used in this disclosure are interchangeable. "Network" may also refer to devices included in the network (eg, base stations).

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

[0416] In this disclosure, terms such as “base station (BS)”, “wireless base station”, “base station device”, “fixed station”, “NodeB”, “eNB (eNodeB)”, “gNB (gNodeB)”, “access point”, “transmission point (TP))”, “reception point (RP))”, “transmission / reception point (TRP))”, “panel”, “cell”, “sector”, “cell group”, “carrier”, and “component carrier” are used interchangeably. A base station is also sometimes referred to as a macro cell, a small cell, a femto cell, or a pico cell.

[0417] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the entire coverage area of ​​at least one of the base station and the base station subsystem that provide communication services within the coverage area.

[0418] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (User Equipment (UE))”, and “terminal” can be used interchangeably.

[0419] A mobile station is also sometimes called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, hand set, user agent, mobile client, client or some other appropriate terminology.

[0420] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Furthermore, at least one of the base station and the mobile station may also be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), a mobile object that moves unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, 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 also be an Internet of Things (IoT) device such as a sensor.

[0421] In addition, the base station in the present disclosure can also be replaced by a user terminal. For example, the various methods / implementations of the present disclosure can also be applied to a structure in which the communication between a base station and a user terminal is replaced by communication between multiple user terminals (for example, which can also be called device-to-device (D2D)), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the user terminal 20 has the functions of the above-mentioned base station 10. In addition, the language such as "uplink" and "downlink" can also be replaced by the language corresponding to the communication between terminals (for example, "side"). For example, the uplink channel, downlink channel, etc. can also be replaced by the side channel.

[0422] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0423] In this disclosure, operations performed by a base station may also be performed by its upper node depending on the situation. In a network including one or more network nodes including a base station, various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (for example, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0424] The various methods / implementations described in this disclosure may be used individually, in combination, or switched as they are executed. Furthermore, the processing procedures, sequence, flow charts, and the like of the various methods / implementations described in this disclosure may be swapped in order, as long as there is no conflict. For example, the methods described in this disclosure use an illustrative order to present various step elements, and are not limited to the specific order presented.

[0425] The various modes and embodiments described in the present disclosure may also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER3G, 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.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems utilizing other appropriate systems, and next-generation systems based on these systems. In addition, a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G) may also be used.

[0426] The phrase “based on” used in this disclosure does not mean “based only on” unless otherwise explicitly stated. In other words, the phrase “based on” means both “based only on” and “based at least on.”

[0427] Any reference to an element using the designations "first," "second," etc., as used in this disclosure, does not necessarily define the quantity or order of these elements. These designations can be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and a second element does not imply that only two elements can be used or that the first element must precede the second element in some form.

[0428] The term "determining" as used in this disclosure may sometimes encompass a variety of operations. For example, "determining" may also include judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching a table, database, or other data structure), ascertaining, etc. as instances of performing a "determination."

[0429] In addition, "judgment (decision)" can also be a situation where receiving (for example, receiving information), transmitting (for example, sending information), input (input), output (output), accessing (for example, accessing data in a memory), etc. are regarded as making a "judgment (decision)".

[0430] Furthermore, "judgment (decision)" can also refer to resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can also refer to certain operations being considered "judgment (decision)."

[0431] In addition, “judgment (decision)” can also be replaced by “assuming (assuming)”, “expecting (expecting)”, “considering (considering)”, etc.

[0432] As used in this disclosure, the terms "connected," "coupled," and any variations thereof mean any direct or indirect connection or coupling between two or more elements, including the presence of one or more intermediate elements between the two "connected" or "coupled" elements. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be replaced by "connected."

[0433] In the present disclosure, when connecting two elements, it is possible to consider using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave domain, and light (visible light and invisible light) domain, the two elements are "connected" or "combined" with each other.

[0434] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other." Alternatively, the term may also mean "A and B are each different from C." Terms such as "separate" and "bound" may also be interpreted in the same way as "different."

[0435] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," are inclusive. Furthermore, the term "or" used in this disclosure does not mean exclusive or.

[0436] In the present disclosure, when an article is added by translation, such as a, an, and the in English, the present disclosure may also include the case where the noun following the article is in a plural form.

[0437] While the invention disclosed herein has been described in detail above, it will be apparent to those skilled in the art that the invention disclosed herein is not limited to the embodiments described herein. The invention disclosed herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description herein is for illustrative purposes only and is not intended to limit the invention disclosed herein in any way.

[0438] This application is based on Japanese Patent Application No. 2019-210876, filed on November 21, 2019, the entire contents of which are incorporated herein by reference.

Claims

1. A terminal comprising: A receiving unit receives a downlink control information format (DCI format 0_0) for scheduling a physical uplink shared channel (PUSCH); and a control unit that, when one or more physical uplink control channel resources (PUCCH resources) are configured in an activated uplink bandwidth part (BWP) of the cell of the PUSCH and none of the one or more PUCCH resources contain spatial relationship information, determines the spatial relationship of the PUSCH based on a quasi co-location (QCL) assumption of a specific control resource set, When the one or more PUCCH resources are set on the activated uplink BWP and all of the one or more PUCCH resources do not contain spatial relationship information, 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 and the TPC command in the DCI format 0_0.

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 relationship of the PUSCH.

3. A wireless communication method, which is a wireless communication method of a terminal, comprising: The step of receiving a downlink control information format (DCI format 0_0) for scheduling a physical uplink shared channel (PUSCH); and In a case where one or more physical uplink control channel resources (PUCCH resources) are configured in an activated uplink bandwidth part (BWP) of the cell of the PUSCH and none of the one or more PUCCH resources contain spatial relationship information, determining the spatial relationship of the PUSCH based on a quasi co-location (QCL) assumption of a specific set of control resources, When the one or more PUCCH resources are set on the activated uplink BWP and all of the one or more PUCCH resources do not contain spatial relationship information, the path loss of the PUSCH is estimated based on the QCL assumption, and the transmission power of the PUSCH is controlled based on the path loss and the TPC command in the DCI format 0_0.

4. A base station comprising: A sending unit, sending a downlink control information format (DCI format 0_0) for scheduling a physical uplink shared channel (PUSCH); and a control unit for controlling reception of the PUSCH transmitted using a spatial relationship assumed by quasi co-location (QCL) based on a specific set of control resources, when one or more physical uplink control channel resources (PUCCH resources) are set in an activated uplink bandwidth part (BWP) of the cell of the PUSCH and none of the one or more PUCCH resources include spatial relationship information; When the one or more PUCCH resources are set on the activated uplink BWP and all of the one or more PUCCH resources do not include spatial relationship information, the path loss of the PUSCH is estimated based on the QCL assumption, and the transmission power of the PUSCH is controlled based on the path loss and the TPC command in the DCI format 0_0.

5. A system comprising a terminal and a base station, wherein: The terminal has: A receiving unit receives a downlink control information format (DCI format 0_0) for scheduling a physical uplink shared channel (PUSCH); and a control unit that, when one or more physical uplink control channel resources (PUCCH resources) are configured in an activated uplink bandwidth part (BWP) of the cell of the PUSCH and none of the one or more PUCCH resources contain spatial relationship information, determines the spatial relationship of the PUSCH based on a quasi co-location (QCL) assumption of a specific control resource set, When the one or more PUCCH resources are configured on the activated uplink BWP and none of the one or more PUCCH resources include spatial relationship information, the control unit estimates a path loss of the PUSCH based on the QCL assumption, and controls the transmit power of the PUSCH based on the path loss and a TPC command in DCI format 0_0. The base station has: A sending unit sends the PUSCH to the terminal.

Images