Terminal, wireless communication method, base station, and system

Abstract

A terminal according to an aspect of the present disclosure has: a reception unit that receives a radio resource control (RRC) information element related to uplink channel configuration, the RRC information element being associated with configuration information related to a list of transmission configuration indication (TCI) states to be applied to at least one of a plurality of channels and signals; and a control unit that determines a TCI state to be applied to each uplink channel on the basis of the configuration information. According to the aspect of the present disclosure, it is possible to appropriately perform transmission power control for UL channels / signals even when TCI states that can be applied to a plurality of channels / signals are used.

Description

Terminal, wireless communication method and base station

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

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

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

[0004] 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

[0005] In future wireless communication systems (e.g., NR), it is being considered that user terminals (terminals, user terminals, User Equipment (UE)) will control transmission and reception processing based on information (QCL assumptions / Transmission Configuration Indication (TCI) states / spatial relationships) regarding quasi-co-location (QCL) applicable to multiple channels / signals.

[0006] However, a method for controlling the transmission power of an uplink (UL) channel / signal when using TCI states applicable to multiple channels / signals is unclear, which may result in degradation of communication quality, degradation of throughput, etc.

[0007] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately perform transmission power control of UL channels / signals even when using TCI states that are applicable to multiple channels / signals.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives Radio Resource Control (RRC) information elements related to uplink channel configuration, the RRC information elements being associated with configuration information related to a list of transmission configuration indication (TCI) states to be applied to at least one of a plurality of channels and signals, and a control unit that determines a TCI state to be applied to each uplink channel based on the configuration information.

[0009] According to one aspect of the present disclosure, it is possible to appropriately control the transmit power of UL channels / signals even when using TCI states that are applicable to multiple channels / signals.

[0010] Fig. 1 is a diagram illustrating an example of RRC information elements related to PUSCH transmission power control in Rel. 16. Fig. 2 is a diagram illustrating an example of RRC information elements related to open-loop power control in Rel. 16. Fig. 3 is a diagram illustrating an example of RRC information elements related to PUCCH transmission power control in Rel. 16. Fig. 4 is a diagram illustrating an example of RRC information elements related to SRS transmission power control in Rel. 16. Fig. 5 is a diagram illustrating an example of simultaneous beam updating across multiple CCs. Figs. 6A and 6B are diagrams illustrating an example of a common beam. Fig. 7 is a diagram illustrating an example of setting transmission power control parameters for PUSCH, PUCCH, and SRS in Rel. 15 / 16. Fig. 8 is a diagram illustrating an example of a set of multiple TPC parameters according to embodiment 1-1. Figs. 9A and 9B are diagrams illustrating an example of a set of multiple TPC parameters and information elements according to embodiment 1-1-1. Figs. 10A and 10B are diagrams illustrating an example of a set of multiple TPC parameters and information elements according to embodiment 1-1-2. FIG. 11 is a diagram illustrating an example of application of TPC parameters according to embodiment 1-2. FIGS. 12A to 12C are diagrams illustrating an example of a set of TPC parameters for an UL channel / signal according to the second embodiment. FIGS. 13A and 13B are diagrams illustrating an example of a set of TPC parameters and information elements according to embodiment 2-1. FIGS. 14A and 14B are diagrams illustrating an example of a set of TPC parameters and information elements according to embodiment 2-2. FIGS. 15A and 15B are diagrams illustrating an example of a set of TPC parameters according to a comparison between the first embodiment and the second embodiment. FIG. 16 is a diagram illustrating an example of configuration of an SRS resource set, an SRS resource, a TCI state, and a TPC parameter set ID according to Modification 3. FIG. 17 is a diagram illustrating another example of configuration of an SRS resource set, an SRS resource, a TCI state, and a TPC parameter set ID according to Modification 3. FIG. 18 is a diagram illustrating an example of RRC information elements according to embodiment 4-1-1. FIG. 19 is a diagram illustrating an example of RRC information elements according to embodiment 4-1-2. Fig. 20 is a diagram illustrating an example of an RRC information element according to embodiment 4-2. Fig. 21 is a diagram illustrating an example of a set of a plurality of TPC parameters according to the fifth embodiment.Fig. 22 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 23 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 24 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 25 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment.

[0011] (TCI, spatial relationship, QCL) In NR, it is considered 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 encoding) in a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).

[0012] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0014] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0015] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0016] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.

[0017] The UE's assumption that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

[0018] The UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for a signal / channel based on the TCI condition or QCL assumption of the signal / channel.

[0019] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

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

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

[0022] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).

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

[0024] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

[0025] For the PDCCH and PDSCH, the QCL Type A RS is always configured, and the QCL Type D RS may be configured additionally. Since it is difficult to estimate Doppler shift, delay, etc. by one-shot reception of the DMRS, the QCL Type A RS is used to improve the accuracy of channel estimation. The QCL Type D RS is used to determine the receiving beam when receiving the DMRS.

[0026] For example, TRS1-1, 1-2, 1-3, and 1-4 are transmitted, and TRS1-1 is notified as a QCL type C / D RS depending on the TCI status of the PDSCH. By notifying the TCI status, the UE can use information obtained from past periodic reception / measurement results of TRS1-1 for reception / channel estimation of the DMRS for the PDSCH. In this case, the QCL source of the PDSCH is TRS1-1, and the QCL target is the DMRS for the PDSCH.

[0027] (Transmission power control) <Transmission power control for PUSH> In NR, the transmission power of PUSH is controlled based on the TPC command (also called a value, increase / decrease value, correction value, etc.) indicated by the value of a specified field in DCI (also called a TPC command field, etc.).

[0028] For example, when a UE transmits a PUSCH on an active UL BWP b of a carrier f of a serving cell c using a parameter set (open loop parameter set) with index j and a power control adjustment state index l, the transmission power (P ＰＵＳＣＨ、ｂ，ｆ，ｃ (i, j, q ｄ , l)) may be expressed by the following formula (1):

[0029] Here, the power control adjustment state may be configured to have multiple states (e.g., two states) or a single state depending on a higher layer parameter. Furthermore, when multiple power control adjustment states are configured, one of the multiple power control adjustment states may be identified by an index l (e.g., l∈{0, 1}). The power control adjustment state may be referred to as a PUSCH power control adjustment state, a first or second state, etc. In the present disclosure, the index l may be referred to as a closed-loop index.

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

[0031]

[0032] In formula (1), P ＣＭＡＸ，ｆ，ｃ（ｉ） is, for example, the transmission power of the user terminal (also referred to as maximum transmission power, UE maximum output power, etc.) set for carrier f of serving cell c at transmission opportunity i. Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) is, for example, a parameter related to the target received power set for the active UL BWP b of the carrier f of the serving cell c in the parameter set setting j (e.g., a parameter related to the transmit power offset, also referred to as the transmit power offset P0, the target received power parameter, etc.).

[0033] M ＰＵＳＣＨＲＢ，ｂ，ｆ，ｃ (i) is the number of resource blocks (bandwidth) allocated to the PUSCH for transmission opportunity i in serving cell c and active UL BWP b of carrier f with subcarrier spacing μ, for example. ｂ，ｆ，ｃ (j) is a value provided by a higher layer parameter (e.g., also called msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

[0034] PL ｂ，ｆ，ｃ (q ｄ ) is, for example, an index q of a reference signal (path loss (PL) reference RS, PL-RS, DL RS for path loss measurement, PUSCH-PathlossReferenceRS) for downlink BWP associated with an active UL BWP b of carrier f of serving cell c. ｄ is the path loss (path loss compensation) calculated by the user terminal using

[0035] Δ ＴＦ，ｂ，ｆ，ｃ (i) is the transmission power adjustment component (offset, transmission format compensation) for UL BWP b of carrier f of serving cell c.

[0036] f ｂ，ｆ，ｃ (i, l) is the TPC command-based value (e.g., power control adjustment state, accumulated value of TPC commands, closed loop value) of the power control adjustment state index l of the active UL BWP of carrier f of serving cell c and transmission opportunity i. For example, f ｂ，ｆ，ｃ (i, l) may be expressed by equation (2), where l may be called the closed-loop index.

[0037]

[0038] In equation (2), δPUSCH,b,f,c(m,l) is the TPC command value at PUSCH transmission opportunity m. Ｃ（Ｄ_ｉ）－１ ｍ＝０ δPUSCH,b,f,c(m,l) is the PUSCH transmission opportunity i-i ０ K before ＰＵＳＣＨ (i-i０ )-1 symbols and K symbols before PUSCH transmission opportunity i ＰＵＳＣＨ (i) The group C(D ｉ ) where i ０ is an integer equal to or greater than 1. The TPC command value for a certain PUSCH transmission opportunity may be a TPC command indicated by a TPC command field value in a DCI (e.g., DCI format 1_0 or 1_1) detected in the active UL BWP b of carrier f of serving cell c, or may be a TPC command indicated by a TPC command field value in a DCI (e.g., DCI format 2_2) having CRC parity bits scrambled with a specific Radio Network Temporary Identifier (RNTI) (e.g., TPC-PUSCH-RNTI) (CRC-scrambled).

[0039] If the UE is not provided with a path loss reference RS (e.g., PUSCH-PathlossReferenceRS) or if the UE is not provided with individual upper layer parameters, the UE may use RS resources from the SSB used to obtain the Master Information Block (MIB) to obtain the PL. ｂ，ｆ，ｃ (q ｄ ) may be calculated.

[0040] When the UE is configured with a number of RS resource indices up to the value of the maximum number of pathloss reference RSs (e.g., maxNrofPUSCH-PathlossReferenceRS) and a set of RS configurations for the RS resource indices according to the pathloss reference RSs, the set of RS resource indices may include one or both of a set of SS / PBCH block indices and a set of CSI-RS resource indices. ｄ may be identified.

[0041] If a PUSCH transmission is scheduled by a Random Access Response (RAR) UL grant, the UE uses the same RS resource index q as for the corresponding PRACH transmission. ｄ may also be used.

[0042] When the UE is provided with a power control configuration of the PUSCH by the SRI (e.g., SRI-PUSCH-PowerControl) and one or more values ​​of the ID of the pathloss reference RS, the UE may obtain a mapping between a set of values ​​for the SRI field in DCI format 0_1 ​​and a set of ID values ​​of the pathloss reference RS from higher layer signaling (e.g., sri-PUSCH-PowerControl-Id in SRI-PUSCH-PowerControl). The UE may obtain the RS resource index q from the ID of the pathloss reference RS mapped to the SRI field value in DCI format 0_1 ​​that schedules the PUSCH. ｄ may be determined.

[0043] If a PUSCH transmission is scheduled by 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 active UL BWP b of each carrier f and serving cell c, the UE shall transmit the PUCCH spatial relationship information for the PUCCH resource with the same RS resource index q as the PUCCH transmission in that PUCCH resource. ｄ may also be used.

[0044] If the PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided with a spatial setting for the PUCCH transmission, or if the PUSCH transmission is scheduled by DCI format 0_1 ​​that does not include an SRI field, or if the UE is not provided with a power control setting for the PUSCH by the SRI, the UE shall select an RS resource index q with an ID of a path loss reference RS of zero. ｄ may also be used.

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

[0046] For the PUSCH transmission configured by the configuration grant configuration, if the configuration grant configuration does not include a predetermined parameter, the UE determines the RS resource index q from the value of the ID of the path loss reference RS mapped to the SRI field in the DCI format that activates the PUSCH transmission. ｄ If the DCI format does not include an SRI field, the UE may determine an RS resource index q with an ID of a pathloss reference RS of zero. ｄ may be determined.

[0047] Note that equations (1) and (2) are merely examples and are not limited thereto. The UE only needs to control the transmission power of the PUSCH based on at least one parameter exemplified in equations (1) and (2), and additional parameters may be included, or some parameters may be omitted. Furthermore, while equations (1) and (2) above control the transmission power of the PUSCH for each active UL BWP of a carrier of a serving cell, this is not limiting. At least some of the serving cell, carrier, BWP, and power control adjustment state may be omitted.

[0048] Fig. 1 is a diagram showing an example of RRC information elements related to PUSCH transmission power control in Rel. 16. As shown in Fig. 1, the UE controls the transmission power of the PUSCH based on the RRC information element related to PUSCH transmission power control (PUSCH-PowerControl). The PUSCH-PowerControl is included in the RRC information element for PUSCH configuration (PUSCH-Config).

[0049] As shown in FIG. 1, PUSCH-Power Control includes at leastＯ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) and α ｂ，ｆ，ｃ The parameter (p0-AlphaSets) represents a set of parameters for giving (j). Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) and α ｂ，ｆ，ｃ The parameter (P0-PUSCH-AlphaSet) for providing (j) is included. That is, a plurality of combinations of P0 and α are configured for the UE for each PUSCH configuration parameter (PUSCH-Config).

[0050] 1, P0-PUSCH-AlphaSet includes a parameter (p0-PUSCH-AlphaSetID) indicating the IDs of the P0 and α sets, a parameter (P0) related to P0, and a parameter (alpha) related to α. A plurality of P0 and α sets are configured for the UE based on the P0-PUSCH-AlphaSet.

[0051] Furthermore, PUSCH-PowerControl includes a parameter (twoPUSCH-PC-AdjustmentStates) for setting two transmission power control adjustment states. When twoPUSCH-PC-AdjustmentStates is set, the UE may determine that two power adjustment states (closed-loop power control states) can be set.

[0052] 1, the power control setting parameter (SRI-PUSCH-PowerControl) mapped to the SRI field value includes at least a PUSCH closed-loop index setting parameter (sri-PUSCH-ClosedLoopIndex). The power control setting parameter (SRI-PUSCH-PowerControl) mapped to the SRI field value is identified by sri-PUSCH-PowerControlID.

[0053] The UE determines the value of the closed-loop index based on the PUSCH closed-loop index configuration parameter (sri-PUSCH-ClosedLoopIndex). That is, the UE configures P0, α, and the closed-loop index for each sri-PUSCH-PowerControlID.

[0054] <Open-loop transmission power control of PUSCH> In Rel. 16, the introduction of open-loop power control that can control the value of P0 using DCI is under consideration.

[0055] In Rel. 16 NR, a case is supported in which a UE is provided with multiple PUSCH P0 and α set ID (p0-PUSCH-AlphaSetId) values ​​from an SRI-based PUSCH power control configuration (e.g., SRI-PUSCH-PowerControl) and the DCI format for scheduling PUSCH includes an SRI field. In such a case, the UE derives a mapping from the SRI-based PUSCH power control ID (sri-PUSCH-PowerControlId) in the SRI-based PUSCH power control configuration (e.g., SRI-PUSCH-PowerControl) between a set of SRI field values ​​in the DCI format and a set of indexes provided by the PUSCH P0 and α set ID (p0-PUSCH-AlphaSetId) that map to a set of PUSCH P0 and α set values ​​(P0-PUSCH-AlphaSet). Then, the UE determines P from the values ​​of the P0 and α set IDs (p0-PUSCH-AlphaSetId) for the PUSCH mapped to the SRI field. Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) is determined.

[0056] If the DCI format includes an open loop power control parameter set indication field, and the open loop power control parameter set indication field indicates 1, the UE shall select the first value of the P0 set (p0-PUSCH-Set) of the P0 set ID (p0-PUSCH-SetId) of the P0 set of the PUSCH corresponding to the value of the SRI field.Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) is determined.

[0057] If a PUSCH P0 set (P0-PUSCH-Set) is provided to the UE and the DCI format includes an open loop power control parameter set indication field, the UE shall select the P0 from the lowest PUSCH P0 set ID (p0-PUSCH-SetId, p0-PUSCH-SetId-r16) when the open loop power control parameter set indication field indicates 1 or 01. Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) is determined.

[0058] If a PUSCH P0 set (P0-PUSCH-Set) is provided to the UE and the DCI format includes an open loop power control parameter set indication field, the UE shall select the P0 from the second value of the PUSCH P0 set (p0-PUSCH-Set) of the lowest PUSCH P0 set ID (p0-PUSCH-SetId, p0-PUSCH-SetId-r16) when the open loop power control parameter set indication field indicates 10. Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) is determined.

[0059] Fig. 2 is a diagram showing an example of RRC information elements related to open-loop power control in Rel. 16. Fig. 2 shows a parameter (PUSCH-PowerControl-v1610) for setting the PUSCH transmission power included in the RRC information element (PUSCH-Config) for setting the PUSCH.

[0060] 2, the parameter for setting the transmission power of the PUSCH (PUSCH-PowerControl-v1610) includes information on a set of P0s of multiple PUSCHs (p0-PUSCH-SetList-r16). P0-PUSCH-SetList-r16 is identified by p0-PUSCH-SetId-r16 and includes a list of P0s (p0-List-r16).

[0061] As shown in Figure 2, p0-List-r16 is set for each p0-PUSCH-SetId-r16. Each value of p0-PUSCH-SetId-r16 corresponds to an SRI field.

[0062] <Transmission power control for PUCCH> In addition, in NR, the transmission power of PUCCH is controlled based on the TPC command (also called a value, an increase / decrease value, a correction value, an instruction value, etc.) indicated by the value of a predetermined field (also called a TPC command field, a first field, etc.) in DCI.

[0063] For example, the power control adjustment state index l is used to determine the PUCCH transmission power (P ＰＵＣＣＨ、ｂ，ｆ，ｃ (i, q ｕ , q ｄ , l) may be expressed by the following formula (3).

[0064] The power control adjustment state may also be referred to as a PUCCH power control adjustment state, a first or second state, and so on.

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

[0066]

[0067] In formula (3), P ＣＭＡＸ，ｆ，ｃ (i) is, for example, the transmit power of the user terminal (also referred to as maximum transmit power, UE maximum output power, etc.) set for carrier f of serving cell c at transmission opportunity i. Ｏ＿ＰＵＣＣＨ，ｂ，ｆ，ｃ (q ｕ) is, for example, a parameter related to the target received power (e.g., a parameter related to the transmit power offset, also referred to as a transmit power offset P0 or a target received power parameter) set for the active UL BWP b of the carrier f of the serving cell c at the transmission opportunity i.

[0068] M ＰＵＣＣＨ ＲＢ，ｂ，ｆ，ｃ (i) is the number of resource blocks (bandwidth) allocated to PUCCH for transmission opportunity i in active UL BWP b of carrier f with serving cell c and subcarrier spacing μ, for example. ｂ，ｆ，ｃ (q ｄ ) is, for example, the index q of the reference signal (path loss reference RS, DL RS for path loss measurement, PUCCH-PathlossReferenceRS) for downlink BWP associated with the active UL BWP b of carrier f of serving cell c. ｄ is the path loss calculated at the user terminal using

[0069] Δ Ｆ＿ＰＵＣＣＨ (F) is a higher layer parameter given for each PUCCH format. ＴＦ，ｂ，ｆ，ｃ (i) is the transmission power adjustment component (offset) for UL BWP b of carrier f of serving cell c.

[0070] g ｂ，ｆ，ｃ (i, l) is a value based on the TPC command of the power control adjustment state index l of the active UL BWP of the serving cell c and carrier f of the transmission opportunity i (e.g., power control adjustment state, accumulated value of TPC commands, closed-loop value, PUCCH power adjustment state). For example, g ｂ，ｆ，ｃ (i, l) may be expressed by equation (4).

[0071]

[0072] In equation (4), δPUCCH,b,f,c(m,l) is the TPC command value at PUCCH transmission opportunity m. Ｃ（Ｃ_ｉ）－１ ｍ＝０δPUCCH,b,f,c(m,l) is the PUCCH transmission opportunity i-i ０ K before ＰＵＣＣＨ (i-i ０ )-1 symbols and K symbols before PUCCH transmission opportunity i ＰＵＣＣＨ (i) The group C (C ｉ ) where i ０ is an integer equal to or greater than 1. The TPC command value for a certain PUCCH transmission opportunity may be the TPC command indicated by the TPC command field value in DCI (e.g., DCI format 1_0 or 1_1) detected in the active UL BWP b of carrier f of serving cell c, or may be the TPC command indicated by the TPC command field value in DCI (e.g., DCI format 2_2) having CRC parity bits scrambled with a specific Radio Network Temporary Identifier (RNTI) (e.g., TPC-PUCCH-RNTI) (CRC-scrambled).

[0073] If the UE is provided with information indicating the use of two PUCCH power control adjustment states (twoPUCCH-PC-AdjustmentStates) and PUCCH spatial relation 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 relation information, l = 0.

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

[0075] If the UE has an active UL BWP b for carrier f of serving cell c, then P Ｏ＿ＰＵＣＣＨ，ｂ，ｆ，ｃ (q ｕ ) value setting is provided by a higher layer, ｂ，ｆ，ｃ (i, l) = 0, k = 0, 1, ..., i. If the UE is provided with PUCCH spatial related information, the UE ｕ , and the PUCCH spatial relationship information associated with q ｕ The value of l may be determined from the value of

[0076] q ｕ may be a P0 ID for PUCCH (p0-PUCCH-Id) indicating P0 for PUCCH (P0-PUCCH) in a P0 set for PUCCH (p0-Set).

[0077] Note that equations (3) and (4) are merely examples and are not limited to these. The user terminal only needs to control the transmission power of the PUCCH based on at least one parameter exemplified in equations (3) and (4), and additional parameters may be included, or some parameters may be omitted. Furthermore, while equations (3) and (4) above control the transmission power of the PUCCH for each active UL BWP of a carrier of a serving cell, this is not limiting. At least some of the serving cell, carrier, BWP, and power control adjustment state may be omitted.

[0078] Fig. 3 is a diagram showing an example of RRC information elements for PUCCH transmission power control in Rel. 16. As shown in Fig. 3, the UE controls the PUCCH transmission power based on RRC information elements (PUCCH-PowerControl) related to PUCCH transmission power control. The PUCCH-PowerControl is included in the PUCCH configuration RRC information element (PUCCH-Config).

[0079] As shown in FIG. 3, the PUCCH-Power Control includes at least Ｏ＿ＰＵＣＣＨ，ｂ，ｆ，ｃ (q ｕ ) is included. Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ The parameter (P0-PUCCH) for providing (j) is included.

[0080] 3, P0-PUCCH includes a parameter (p0-PUCCH-Id) indicating the P0 ID for PUCCH and a parameter (p0-PUCCH-Value) relating to the value of P0 for PUCCH. A set of multiple P0s is configured for the UE based on p0-Set. That is, a set of multiple P0s is configured for the UE for each PUCCH configuration parameter (PUCCH-Config).

[0081] Furthermore, PUCCH-PowerControl includes a parameter (twoPUCCH-PC-AdjustmentStates) for setting two transmission power control adjustment states. When twoPUCCH-PC-AdjustmentStates is set, the UE may determine that two power adjustment states (closed-loop power control states) can be set.

[0082] Furthermore, as shown in the example of Figure 3, a parameter (PUCCH-SpatialRelationInfo) related to spatial relation information of the PUCCH is configured in the UE. The parameter (PUCCH-SpatialRelationInfo) related to spatial relation information of the PUCCH is identified by a PUCCH spatial accounting information ID (pucch-SpatialRelationInfoId). The parameter (PUCCH-SpatialRelationInfo) related to spatial relation information of the PUCCH includes at least a parameter (p0-PUCCH-Id) indicating a P0 ID for the PUCCH and a parameter (closedLoopIndex) for setting a closed-loop index. In other words, when controlling the transmission power of the PUCCH, a P0 and a closed-loop index are configured for each spatial relation of the PUCCH.

[0083] <SRS Transmission Power Control> For example, the index l of the power control adjustment state is used to determine the transmission power (P ＳＲＳ、ｂ，ｆ，ｃ (i, q ｓ , l) may be expressed by the following formula (5).

[0084] The power control adjustment state may be referred to as an SRS power control adjustment state, a value based on a TPC command, an accumulated value of a TPC command, a value by a closed loop, a first or second state, etc. 1 may be referred to as a closed loop index.

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

[0086]

[0087] In formula (5), P ＣＭＡＸ，ｆ，ｃ (i) is, for example, the UE maximum output power for carrier f of serving cell c at SRS transmission opportunity i. P Ｏ＿ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ) is the active UL BWP b of carrier f of serving cell c and the SRS resource set q ｓ (provided by SRS-ResourceSet and SRS-ResourceSetId), and a parameter related to the target received power provided by p0 for (for example, a parameter related to the transmit power offset, also referred to as the transmit power offset P0 or the target received power parameter, etc.).

[0088] M ＳＲＳ，ｂ，ｆ，ｃ (i) is the SRS bandwidth in number of resource blocks for SRS transmission opportunity i on active UL BWP b of carrier f of serving cell c and subcarrier spacing μ;

[0089] α ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ) is the active UL BWP b of a serving cell c and carrier f with subcarrier spacing μ and an SRS resource set q ｓ and α (e.g., alpha) for

[0090] PL ｂ，ｆ，ｃ (q ｄ ) is the active DL BWP of serving cell c and the SRS resource set q ｓ and, for RS resource index q ｄ is the DL path loss estimate [dB] calculated by the UE using the RS resource index q ｄ is the SRS resource set q ｓand a pathloss reference RS (a DL RS for pathloss measurement, e.g., provided by pathlossReferenceRS) associated with the SS / PBCH block index (e.g., ssb-Index) or a CSI-RS resource index (e.g., csi-RS-Index).

[0091] h ｂ，ｆ，ｃ (i, l) is the SRS power control adjustment state for the active UL BWP of carrier f of serving cell c and SRS transmission opportunity i. If the SRS power control adjustment state configuration (e.g., srs-PowerControlAdjustmentStates) indicates the same power control adjustment state for SRS transmission and PUSCH transmission, the current PUSCH power control adjustment state f ｂ，ｆ，ｃ On the other hand, if the setting of the SRS power control adjustment state indicates independent power control adjustment states for SRS transmission and PUSCH transmission, and the setting of TPC accumulation is not provided, the SRS power control adjustment state h ｂ，ｆ，ｃ (i) may be expressed by equation (6).

[0092]

[0093] In formula (6), δ ＳＲＳ，ｂ，ｆ，ｃ (m) is coded together with other TPC commands in a PDCCH with DCI (e.g., DCI format 2_3). ＳＲＳ，ｂ，ｆ，ｃ (m) is the TPC command value at SRS transmission opportunity m. Ｃ（Ｓ_ｉ）－１ ｍ＝０ δ ＳＲＳ，ｂ，ｆ，ｃ (m) is the SRS transmission opportunity i-i on the active UL BWP b of carrier f with serving cell c and subcarrier spacing μ. ０ K before ＳＲＳ (i-i ０ )-1 symbols and K before SRS transmission opportunity i ＳＲＳ (i) The group C(S ｉ ) where i ０ is an integer of 1 or greater.

[0094] Note that equations (5) and (6) are merely examples and are not limited to these. The user terminal only needs to control the transmission power of the SRS based on at least one parameter exemplified in equations (5) and (6), and additional parameters may be included, or some parameters may be omitted. Furthermore, while equations (5) and (6) above control the transmission power of the SRS for each BWP of a certain carrier in a certain cell, this is not limiting. At least some of the cell, carrier, BWP, and power control adjustment state may be omitted.

[0095] Fig. 4 is a diagram showing an example of RRC information elements for SRS transmission power control in Rel. 16. As shown in Fig. 4, the UE controls the SRS transmission power based on information included in an RRC information element (SRS-ResourceSet) related to the configuration of an SRS resource set.

[0096] As shown in FIG. 4, the SRS-ResourceSet includes at least P Ｏ＿ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ) parameter (P0) and α ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ) and a parameter (alpha) related to the SRS resource set. That is, the UE is configured with one P0 and one α for each SRS resource set.

[0097] (Power Control Setting Indication) In Rel. 15 NR, the SRI field in the DCI allows switching between multiple states of open-loop (OL)-TPC or closed-loop (CL)-TPC to track changes in spatial relationship. If the usage of the SRS resource set is codebook transmission, the maximum number of SRI field values ​​is 2 (the SRI field length is 1 bit), and if the usage of the SRS resource set is non-codebook transmission, the maximum number of SRI field values ​​is 4 (the SRI field length is 2 bits).

[0098] To configure power control settings for the PUSCH, PUSCH power control information (PUSCH-PowerControl) in PUSCH configuration information (PUSCH-Config) includes a list (sri-PUSCH-MappingToAddModList) of power control settings (SRI-PUSCH-PowerControl) mapped to SRI field values. The power control settings include a power control setting ID (sri-PUSCH-PowerControlId) corresponding to the SRI field value, a pathloss reference RS ID (sri-PUSCH-PathlossReferenceRS-Id) indicating a pathloss reference RS, a P0-α set ID (sri-P0-PUSCH-AlphaSetId) indicating a set of P0 and α, and a closed loop (CL) ID (sri-PUSCH-ClosedLoopIndex) corresponding to power control state l.

[0099] At least one of the path loss reference RS ID, the P0-α set ID, and the closed loop ID may be referred to as a power control (transmit power control, TPC) parameter. At least one of the path loss reference RS ID and the P0-α set ID may be referred to as an open loop (OL) power control (TPC) parameter because they are used for OL power control. The closed loop ID may be referred to as a closed loop (CL) power control (TPC) parameter because they are used for CL power control.

[0100] For example, a power control setting #0 including P0#0, α#0, path loss reference RS#0, and power control adjustment state #0 (l=0) may be associated with an SRI field value 0, and a power control setting #1 including P0#1, α#1, path loss reference RS#1, and power control adjustment state #1 (l=1) may be associated with an SRI field value 1. The UE is instructed on the associated power control setting by the SRI field.

[0101] If the UE is configured with only one SRS resource, the SRI field length is 0 bits.

[0102] In order to set the power control setting for the PUCCH, the PUCCH setting information (PUCCH-Config) includes a power control setting (PUCCH-PowerControl). The power control setting includes a correction value Δ Ｆ＿ＰＵＣＣＨ (F) (deltaF-PUCCH-f0, deltaF-PUCCH-f1, deltaF-PUCCH-f2, deltaF-PUCCH-f3, deltaF-PUCCH-f4), a set of P0 (p0-Set), a set of pathloss reference RSs (pathlossReferenceRSs), and information indicating whether two PUCCH power adjustment states are used (twoPUCCH-PC-AdjustmentStates). The pathloss reference RS may be represented by an SSB index (SSB-Index) or a CSI-RS (NZP-CSI-RS resource ID (NZP-CSI-RS-ResourceId)).

[0103] In this way, Rel. 15 NR allows switching of power control settings.

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

[0105] Note that multiple TRPs may correspond to the same cell identifier (cell identifier (ID)) or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0106] Multi-TRPs (e.g., TRPs #1 and #2) may be connected by ideal / non-ideal backhauls to exchange information, data, etc. Each TRP of a multi-TRP may transmit a different code word (CW) and a different layer. Non-Coherent Joint Transmission (NCJT) may be used as a form of multi-TRP transmission.

[0107] In the NCJT, for example, TRP#1 modulates and layer-maps a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding, and TRP#2 modulates and layer-maps a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

[0108] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in time and / or frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in time and / or frequency resources.

[0109] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (QCL). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0110] Multiple PDSCHs from multiple TRPs (which may be referred to as multiple PDSCHs) may be scheduled using one DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Multiple PDSCHs from multiple TRPs may be scheduled using multiple DCIs (multiple DCI, multiple PDCCHs) (multi-master mode, multi-DCI based multi-TRP).

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

[0112] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

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

[0114] If at least one of the following conditions 1 and 2 is satisfied, the UE may determine that the transmission is a multi-TRP transmission based on the multi-DCI. In this case, the TRP may be replaced with the CORESET pool index. [Condition 1] A CORESET pool index of 1 is set. [Condition 2] Two different values ​​of the CORESET pool index (e.g., 0 and 1) are set.

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

[0116] The DCI for common beam instruction may be a UE-specific DCI format (e.g., DL DCI format (e.g., 1_1, 1_2), UL DCI format (e.g., 0_1, 0_2)), or may be a UE-group common DCI format.

[0117] (Simultaneous Beam Update of Multiple CCs) In Rel. 16, one MAC CE can update the beam index (TCI state) of multiple CCs.

[0118] The UE can be configured with up to two applicable CC lists (e.g., applicable-CC-list) by RRC. When two applicable CC lists are configured, the two applicable CC lists may correspond to in-band CA in FR1 and in-band CA in FR2, respectively.

[0119] The PDCCH TCI state activation MAC CE activates the TCI states associated with the same CORESET ID on all BWP / CCs in the applicable CC list.

[0120] Activation of TCI State for PDSCH The MAC CE activates the TCI state on all BWP / CCs in the applicable CC list.

[0121] A-SRS / SP-SRS Spatial Relationship Activation The MAC CE activates the spatial relationships associated with the same SRS resource ID on all BWPs / CCs in the applicable CC list.

[0122] In the example of Figure 5, the UE is configured with an applicable CC list indicating CCs #0, #1, #2, and #3, and a list indicating 64 TCI states for CORESET or PDSCH of each CC. If one TCI state of CC #0 is activated by a MAC CE, the corresponding TCI state is activated in CCs #1, #2, and #3.

[0123] Such simultaneous beam updating is considered applicable only to the single TRP case.

[0124] For PDSCH, the UE may follow the procedure A. [Procedure A] The UE receives an activation command to map up to eight TCI states to codepoints of the DCI field (TCI field) within one CC / DL BWP or within one set of CCs / BWPs. If one set of TCI state IDs is activated for one set of CCs / DL BWPs, then the applicable list of CCs is determined by the CC indicated in the activation command, and the same set of TCI states applies to all DL BWPs within the indicated CCs. Only if the UE is not provided with different values ​​of the CORESETPoolIndex in the CORESET information element (ControlResourceSet) and is not provided with at least one TCI codepoint that maps to two TCI states, can one set of TCI state IDs be activated for one set of CC / DL BWPs.

[0125] For PDCCH, the UE may follow procedure B. [Procedure B] If the UE is provided with up to two lists of cells for simultaneous TCI state activation by the simultaneous TCI cell list (simultaneousTCI-CellList) via the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList-r16 and simultaneousTCI-UpdateListSecond-r16), the UE shall apply antenna port quasi co-location (QCL) provided by TCI states with the same activated TCI state ID value to CORESET with index p in all configured DL BWPs of all configured cells in one list determined from the serving cell index provided by the MAC CE command. A simultaneous TCI cell list can be provided for simultaneous TCI state activation only if the UE is not provided with multiple different values ​​of the CORESETPoolIndex in the CORESET information element (ControlResourceSet) and is not provided with at least one TCI codepoint that maps to two TCI states.

[0126] For semi-persistent (SP) / aperiodic (AP)-SRS, the UE may follow procedure C. [Procedure C] When spatial relation information (spatialRelationInfo) for SP or AP-SRS resources configured by the SRS resource information element (higher layer parameter SRS-Resource) for one set of CCs / BWPs is activated / updated by MAC CE, where the applicable list of CCs is indicated by the simultaneous spatial update list (higher layer parameter simultaneousSpatial-UpdateList-r16 or simultaneousSpatial-UpdateListSecond-r16), the spatial relation information is applied to SP or AP-SRS resources with the same SRS resource ID in all BWPs within the indicated CC. The spatial relation information (spatialRelationInfo) for the SP or AP-SRS resources configured by the SRS resource information element (higher layer parameter SRS-Resource) for one set of CCs / BWPs is activated / updated by the MAC CE only if the UE is not provided with different values ​​of the CORESETPoolIndex in the CORESET information element (ControlResourceSet) and is not provided with at least one TCI codepoint that maps to two TCI states.

[0127] The simultaneous TCI cell list (simultaneousTCI-CellList) and the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16) are lists of serving cells whose TCI relationships can be updated simultaneously using MAC CE. simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16 do not include the same serving cell.

[0128] The simultaneous spatial update list (at least one of the upper layer parameters simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16) is a list of serving cells whose spatial relationships can be updated simultaneously using MAC CE. simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16 do not include the same serving cell.

[0129] Here, the simultaneous TCI update list and the simultaneous spatial update list are configured by the RRC, the CORESET pool index of the CORESET is configured by the RRC, and the TCI code point mapped to the TCI state is indicated by the MAC CE.

[0130] (Unified / Common TCI Framework) The unified TCI framework allows UL and DL channels to be controlled by a common framework. Instead of specifying TCI states or spatial relationships for each channel as in Rel. 15, the unified TCI framework may specify a common beam (common TCI state) and apply it to all UL and DL channels, or a common beam for UL may apply to all UL channels and a common beam for DL ​​may apply to all DL channels.

[0131] One common beam for both DL and UL, or one common beam for DL ​​and one common beam for UL (two common beams overall) are considered.

[0132] The UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE may assume different TCI states for UL and DL (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).

[0133] The default beams for UL and DL may be aligned via MAC CE based beam management (MAC CE level beam indication). The default TCI state of the PDSCH may be updated to align with the default UL beam (spatial relationship).

[0134] DCI-based beam management (DCI-level beam indication) may indicate a common beam / unified TCI state from the same TCI pool for both UL and DL (joint common TCI pool, joint TCI pool, set). X (>1) TCI states may be activated by the MAC CE. The UL / DL DCI may select one from the X active TCI states. The selected TCI state may apply to both UL and DL channels / RS.

[0135] The TCI pool (set) may be multiple TCI states configured by RRC parameters, or multiple TCI states (active TCI states, active TCI pools, sets) activated by MAC CE among the multiple TCI states configured by RRC parameters. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be configured as the QCL type A / D RS.

[0136] The number of TCI states corresponding to each of one or more TRPs may be specified. For example, the number N (≧1) of TCI states applied to UL channels / RSs (UL TCI states) and the number M (≧1) of TCI states applied to DL channels / RSs (DL TCI states) may be specified. At least one of N and M may be notified / configured / instructed to the UE via higher layer signaling / physical layer signaling.

[0137] In the present disclosure, when N=M=X (X is any integer), it may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / indicated to the UE. Also, when N=X (X is any integer) and M=Y (Y may be any integer, Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (i.e., separate TCI states) (corresponding to Y TRPs) are notified / configured / indicated to the UE.

[0138] For example, when N=M=1 is written, this may mean that a TCI state common to one UL and DL for a single TRP is notified / configured / indicated to the UE (joint TCI state for a single TRP).

[0139] Also, for example, when N=1 and M=1 are written, this may mean that one UL TCI state and one DL TCI state for a single TRP are separately notified / configured / instructed to the UE (separate TCI states for a single TRP).

[0140] Also, for example, when N=M=2 is written, this may mean that a TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs is notified / configured / instructed to the UE (joint TCI state for multiple TRPs).

[0141] Also, for example, when N=2 and M=2, it may mean that multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs are notified / configured / instructed to the UE (separate TCI states for multiple TRPs).

[0142] In the above example, the values ​​of N and M are 1 or 2, but the values ​​of N and M may be 3 or more, and N and M may be different.

[0143] In the example of Figure 6A, the RRC parameters (information elements) configure multiple TCI states for both DL and UL. The MAC CE may activate multiple TCI states from the configured multiple TCI states. The DCI may indicate one of the activated multiple TCI states. The DCI may be a UL / DL DCI. The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both the UL TCI and the DL TCI.

[0144] In the example of FIG. 6A, a point may be one TCI state that applies to both UL and DL, or two TCI states that apply to UL and DL, respectively.

[0145] At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).

[0146] In the present disclosure, higher layer parameters (RRC parameters) for setting multiple TCI states may be referred to as configuration information for setting multiple TCI states, or simply as "configuration information." Also, in the present disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information instructing one of the multiple TCI states included in DCI, or may simply mean receiving "instruction information."

[0147] In the example of Figure 6B, the RRC parameters configure multiple TCI states (joint common TCI pools) for both DL and UL. The MAC CE may activate multiple TCI states (active TCI pools) from the configured multiple TCI states. Separate active TCI pools for each of the UL and DL may be configured / activated.

[0148] The DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) DL channels / RSs. The DL channels may be PDCCH / PDSCH / CSI-RS. The UE may determine the TCI state of each DL channel / RS using the TCI state behavior (TCI framework) of Rel. 16. The UL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) UL channels / RSs. The UL channels may be PUSCH / SRS / PUCCH. In this way, different DCIs may indicate UL TCI and DL DCI separately.

[0149] The existing DCI formats 1_1 / 1_2 may be used to indicate the common TCI state.

[0150] A common TCI framework may have separate TCI states for DL ​​and UL.

[0151] (Analysis) Regarding the transmission power control of PUSCH, PUCCH, and SRS in Rel. 15 / 16, the parameters to be set are as shown in FIG.

[0152] Specifically, for the transmission power control of the PUSCH in Rel. 15 / 16, P0, α, and a closed-loop index (CL-loop index) are set.

[0153] For PUCCH transmission power control in Rel. 15 / 16, P0 and a closed-loop index are set.

[0154] For the transmission power control of the SRS in Rel. 15 / 16, P0 and α are set.

[0155] It is considered that in Rel. 17 and later, the PL-RS will be defined to be included / associated with the UL TCI state or the joint TCI state.

[0156] In addition, in Rel. 17 and later, it is being considered to define parameters related to TPC other than PL-RS (e.g., P0, α, and closed-loop index) in relation to the UL TCI state or the joint TCI state.

[0157] More specifically, it is being considered to specify that the combination (setting) of P0, α, and closed-loop index is set / indicated for each PUSCH / PUCCH / SRS and for each UL TCI state / joint TCI state.

[0158] However, there has been insufficient consideration given to the method of setting / instructing each parameter when implementing this provision. Furthermore, there has also been insufficient consideration given to the method of setting / instructing the open loop power control (OLPC) that accompanies this provision. If these considerations are insufficient, it may be impossible to perform appropriate transmission power control, which may result in degradation of communication quality, throughput, etc.

[0159] Therefore, the present inventors have conceived of a method for controlling the transmission power of UL channels / signals when utilizing TCI conditions applicable to multiple channels / signals.

[0160] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0161] In the present disclosure, "A / B / C" and "at least one of A, B, and C" may be read as interchangeable. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be read as interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be read as interchangeable.

[0162] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0163] 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. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), and RRC messages may be read interchangeably.

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

[0165] In the present disclosure, MAC CE and activation / deactivation command may be read interchangeably.

[0166] In the present disclosure, the terms pool, set, group, list, and candidate may be read interchangeably.

[0167] In the present disclosure, DMRS, DMRS port, and antenna port may be read interchangeably.

[0168] In the present disclosure, the terms special cell, SpCell, PCell, and PSCell may be read interchangeably.

[0169] In the present disclosure, beam, spatial domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D for TCI state / QCL assumption, RS of QCL type A for TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS may be read interchangeably. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, source of DL-RS, SSB, CSI-RS, and SRS may be read interchangeably.

[0170] In the present disclosure, common beam, common TCI, common TCI state, unified TCI, unified TCI state, TCI state applicable to DL and UL, TCI state applicable to multiple (multiple types) channels / RS, TCI state applicable to multiple types of channels / RS, PL-RS, TCI state may be read interchangeably.

[0171] In the present disclosure, multiple TCI states configured by RRC, multiple TCI states activated by MAC CE, pool, TCI state pool, active TCI state pool, common TCI state pool, joint TCI state pool, separate TCI state pool, common TCI state pool for UL, common TCI state pool for DL, common TCI state pool configured / activated by RRC / MAC CE, and TCI state information may be read interchangeably.

[0172] In the present disclosure, panel, Uplink (UL) transmitting entity, TRP, spatial relationship, control resource set (CONTROLLER RESOLUTION SET (CORESET)), PDSCH, codeword, base station, antenna port of a certain signal (e.g., Demodulation Reference Signal (DMRS) port), antenna port group of a certain signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CORESET subset, CW, redundancy version (RV), layer (MIMO layer, transmission layer, spatial layer) may be interchangeable. Also, panel identifier (ID) and panel may be interchangeable. In the present disclosure, the terms TRP ID, TRP Associated ID, CORESET Pool Index, the position of one of two TCI states corresponding to one code point of a field in a DCI (ordinal number, first TCI state or second TCI state), and TRP may be read interchangeably.

[0173] In the present disclosure, the terms TRP, transmission point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in the TCI field may be read interchangeably.

[0174] In this disclosure, the terms "single TRP," "single TRP system," "single TRP transmission," and "single PDSCH" may be interchangeable. In this disclosure, the terms "multiple TRP," "multiple TRP system," "multiple TRP transmission," and "multiple PDSCH" may be interchangeable. In this disclosure, the terms "single DCI," "single PDCCH," "multiple TRP based on a single DCI," and "activating two TCI states on at least one TCI codepoint" may be interchangeable.

[0175] In the present disclosure, single TRP, channel using single TRP, channel using one TCI state / spatial relationship, multi-TRP not enabled by RRC / DCI, multiple TCI states / spatial relationships not enabled by RRC / DCI, a CORESETPoolIndex value of 1 not set for any CORESET, and no code point in the TCI field mapped to two TCI states may be read interchangeably.

[0176] In the present disclosure, "multi-TRP," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0177] In the present disclosure, TRP#1 (first TRP) may correspond to CORESET pool index = 0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field, and TRP#2 (second TRP) may correspond to CORESET pool index = 1 or may correspond to the second of two TCI states corresponding to one code point in the TCI field.

[0178] In the present disclosure, cell, serving cell, CC, BWP, BWP within a CC, and band may be read interchangeably.

[0179] (Wireless Communication Method) In the present disclosure, DL TCI, DL only TCI, separate DL only TCI, DL common TCI, DL unified TCI, common TCI, and unified TCI may be interchangeable. In the present disclosure, UL TCI, UL only TCI, separate UL only TCI, UL common TCI, UL unified TCI, common TCI, and unified TCI may be interchangeable.

[0180] In the present disclosure, setting / indicating / updating a separate TCI state, setting / indicating / updating a DL-only TCI state, setting / indicating / updating a UL-only TCI state, and setting / indicating / updating a DL and UL TCI state may be read as interchangeable.

[0181] In the present disclosure, in the case of a joint TCI pool, "when a joint TCI pool is configured" and "when a separate TCI pool is configured" may be read interchangeably.

[0182] In the present disclosure, the following terms may be read interchangeably: a joint TCI pool is configured; a TCI pool configured for DL ​​and a TCI pool configured for UL are common; a TCI pool for both DL and UL is configured; and one TCI pool (one set of TCIs) is configured.

[0183] In the present disclosure, the following terms may be interchangeable: a separate TCI pool is configured; a TCI pool configured for DL ​​and a TCI pool configured for UL are different; a TCI pool for DL ​​(first TCI pool, first TCI set) and a TCI pool for UL (second TCI pool, second TCI set) are configured; a plurality of TCI pools (a plurality of sets of TCIs) are configured; and a TCI pool for DL ​​is configured. When a TCI pool for DL ​​is configured, the TCI pool for UL may be equal to the configured TCI pool.

[0184] In the present disclosure, the channels / RS to which the common TCI is applied may be PDSCH / PDCCH / HARQ-ACK information / PUCCH / PUSCH / CSI-RS / SRS.

[0185] In each embodiment of the present disclosure, a pool (list) including multiple unified TCI states may be configured / activated for a UE, and one or more of the multiple unified TCI states may be indicated. The configuration / activation may be performed by configuration information transmitted via higher layer signaling (e.g., RRC signaling / MAC CE), or the indication may be performed by indication information transmitted using DCI.

[0186] In addition, in the present disclosure, signaling configuration, signaling, setting, configuration, setting information, information element, instruction, instruction information, list, pool, etc. may be read interchangeably.

[0187] In the present disclosure, the terms UL channel / signal, transmission of UL channel / signal, and UL transmission may be read interchangeably.

[0188] <First embodiment> In a first embodiment, a set of TPC-related parameters (which may also be referred to as TPC parameters) common to each TCI state may be configured for a UE across multiple UL channels / signals, and a component dependent on each channel / signal may be applied.

[0189] The multiple UL channels / signals may be, for example, PUSCH / PUCCH / SRS.

[0190] The TPC parameter may be at least one of a parameter related to P0 (which may be simply referred to as "P0"), a parameter related to α (which may be simply referred to as "α"), and a parameter related to a closed-loop index (which may be simply referred to as "CL loop index").

[0191] A UE may be configured with a plurality of sets of TPC parameters (hereinafter, simply referred to as "sets"). For example, the set may include a combination of a parameter related to P0, a parameter related to α, and a parameter related to a closed-loop index.

[0192] This setting may be performed using higher layer signaling (e.g., RRC signaling / MAC CE). In the following embodiments of the present disclosure, a case where RRC signaling is mainly used will be described, but MAC CE may also be used as appropriate.

[0193] The set may be a common set for multiple UL channels / signals. The set may be identified by an ID.

[0194] The ID of the set may be associated with each TCI state, and the set may be configured / applied for each TCI state.

[0195] 8 is a diagram illustrating an example of a plurality of sets of TPC parameters according to embodiment 1-1. In the example illustrated in FIG. 8, a plurality of sets of P0, α (alpha), and CL loop index are configured for a UE. One of the sets is identified by a P0-alpha-CL-loop set ID.

[0196] The names of the parameters shown in the embodiments of the present disclosure are merely examples and are not limited to the examples described.

[0197] The UE may be configured with one set of multiple TPC parameters corresponding to one TCI state (embodiment 1-1-1). In other words, the UE may be configured with an ID of one set of TPC parameters corresponding to one TCI state. The UE may apply the one set to multiple UL channels / signals corresponding to the one TCI state.

[0198] 9A is a diagram illustrating an example of a method for configuring multiple TPC parameter sets according to embodiment 1-1-1. A UE is configured with multiple sets as shown in FIG. 8. Next, the UE is configured with the sets (IDs of the sets, P0-alpha-CL-loop set IDs) corresponding to TCI states (TCI state IDs). The UE determines TPC parameters for each TCI state based on the correspondence relationships as shown in FIG. 9A.

[0199] 9B is a diagram illustrating an example of information elements related to TPC parameters according to embodiment 1-1-1. As illustrated in FIG. 9B, a P0-alpha-CL-loop set ID may be included in the TCI state setting parameter (TCI-state).

[0200] Furthermore, the TCI state setting parameter (TCI-state) may not include the P0-alpha-CL-loop set ID, in which case the TCI state setting parameter (TCI-state) and the P0-alpha-CL-loop set ID may be associated with each other via a specific parameter.

[0201] According to embodiment 1-1-1, it is possible to configure a plurality of TPC parameters for a UE while suppressing an increase in signaling overhead.

[0202] The UE may be configured with a plurality of sets of IDs corresponding to a plurality of UL channels / signals, each corresponding to one TCI state (embodiment 1-1-2).

[0203] 10A is a diagram illustrating an example of a method for configuring multiple TPC parameter sets according to embodiment 1-1-2. A UE is configured with multiple sets as shown in FIG. 8. Next, the UE is configured with a set (ID of the set, P0-alpha-CL-loop set ID) corresponding to each UL channel / signal (PUSCH / PUCCH / SRS) corresponding to the TCI state (TCI state ID). The UE determines TPC parameters for each UL channel / signal and each TCI state based on the correspondence relationship as shown in FIG. 10A.

[0204] 10B is a diagram illustrating an example of information elements related to TPC parameters according to embodiment 1-1-2. As shown in FIG. 10B, the TCI state setting parameter (TCI-state) may include a P0-alpha-CL-loop set ID for PUSCH, a P0-alpha-CL-loop set ID for PUCCH, and a P0-alpha-CL-loop set ID for SRS.

[0205] Furthermore, the TCI state configuration parameter (TCI-state) does not necessarily include the P0-alpha-CL-loop set ID for PUSCH, the P0-alpha-CL-loop set ID for PUCCH, or the P0-alpha-CL-loop set ID for SRS. In this case, the TCI state configuration parameter (TCI-state) and the P0-alpha-CL-loop set ID for PUSCH, the P0-alpha-CL-loop set ID for PUCCH, or the P0-alpha-CL-loop set ID for SRS may be associated via a specific parameter.

[0206] According to embodiment 1-1-2, different transmission power control is performed for each different UL channel / signal, but it is possible to set the same level of transmission power for each different UL channel / signal.

[0207] <<Embodiment 1-2>> When one set ID is configured for multiple channels / signals, the UE may determine / select at least one parameter for calculating the TPC to be applied to the UL channel / signal.

[0208] The UE may decide to use / not use (ignore) certain parameters based on the (type of) UL channel / signal.

[0209] For example, if one set ID is configured and P0, α, and CL loop index corresponding to the ID are configured, the UE may use the configured P0, α, and CL loop index to calculate the TPC of the PUSH.

[0210] Also, for example, when one set ID is configured and P0, α, and a CL loop index corresponding to the ID are configured, the UE may use the configured P0 and CL loop index to calculate the TPC of the PUCCH. In this case, the UE may determine not to use (or may ignore) the configured α.

[0211] Also, for example, when one set ID is configured and P0, α, and a CL loop index corresponding to the ID are configured, the UE may use the configured P0 and α to calculate the TPC of the SRS. In this case, the UE may determine not to use (or may ignore) the configured CL loop index.

[0212] Fig. 11 is a diagram showing an example of application of TPC parameters according to embodiment 1-2. The correspondence relationship shown in Fig. 11 is the same as the correspondence relationship shown in Fig. 8. The UE is configured with this correspondence relationship, and P0-alpha-CL-loop set ID = 0 is set as the set ID (P0-alpha-CL-loop set ID) corresponding to a certain TCI state.

[0213] In this case, the UE applies P0=-10, alpha=1.0, and CL loop index=0, which correspond to P0-alpha-CL-loop set ID=0, to the calculation of the TPC of the PUSCH.

[0214] At this time, the UE applies P0=-10 and CL loop index=0, which correspond to P0-alpha-CL-loop set ID=0, to calculate the TPC of the PUCCH, and ignores the value of alpha.

[0215] At this time, the UE applies P0=-10, alpha=1.0 corresponding to P0-alpha-CL-loop set ID=0 to calculate the TPC of the SRS, and ignores the value of the CL loop index.

[0216] According to the first embodiment, it is possible to appropriately control the transmission power for each UL channel / signal and for each TCI state.

[0217] Second Embodiment In a second embodiment, a set of TPC parameters for each TCI state may be configured for a UE for each of a plurality of UL channels / signals.

[0218] The parameters included in the TPC parameter sets for different UL channels / signals may be defined differently. Different parameters included in the TPC parameter sets for different UL channels / signals may be supported.

[0219] For example, the set of TPC parameters for PUSCH may include P0, α, and a closed-loop index (see FIG. 12A).

[0220] Also, for example, P0 and a closed-loop index may be included in the set of TPC parameters for PUCCH (see FIG. 12B).

[0221] Also, for example, P0 and α may be included in the set of TPC parameters for SRS (see FIG. 12C).

[0222] The UE may be configured with one set of multiple TPC parameters corresponding to one TCI state (embodiment 2-1). In other words, the UE may be configured with an ID of one set of the TPC parameters corresponding to one TCI state. The UE may apply the one set to multiple UL channels / signals corresponding to the one TCI state.

[0223] 13A is a diagram showing an example of a method for configuring multiple TPC parameter sets according to embodiment 2-1. A UE is configured with multiple sets as shown in FIGS. 12A to 12C. Then, the UE is configured with the set (ID of the set, P0-alpha-CL-loop set ID) corresponding to the TCI state (TCI state ID). The UE determines TPC parameters for each TCI state that are common to multiple UL channels / signals (e.g., PUSCH / PUCCH / SRS) based on the correspondence relationship as shown in FIG. 13A.

[0224] 13B is a diagram illustrating an example of information elements related to TPC parameters according to embodiment 2-1. As illustrated in FIG. 13B, a P0-alpha-CL-loop set ID may be included in the TCI state setting parameter (TCI-state).

[0225] Furthermore, the TCI state setting parameter (TCI-state) may not include the P0-alpha-CL-loop set ID, in which case the TCI state setting parameter (TCI-state) and the P0-alpha-CL-loop set ID may be associated with each other via a specific parameter.

[0226] According to embodiment 2-1, it is possible to set a plurality of TPC parameters for a UE while suppressing an increase in signaling overhead.

[0227] The UE may be configured with a plurality of sets of IDs corresponding to a plurality of UL channels / signals, each corresponding to one TCI state (embodiment 2-2).

[0228] 14A is a diagram showing an example of a method for configuring multiple TPC parameter sets according to embodiment 2-2. A UE is configured with multiple sets as shown in FIGS. 12A to 12C. Next, the UE is configured with a set (ID of the set, P0-alpha-CL-loop set ID) corresponding to each UL channel / signal (PUSCH / PUCCH / SRS) corresponding to the TCI state (TCI state ID). The UE determines TPC parameters for each UL channel / signal and each TCI state based on the correspondence relationship shown in FIG. 14A.

[0229] 14B is a diagram illustrating an example of information elements related to TPC parameters according to embodiment 2-2. As shown in FIG. 14B, the TCI state setting parameter (TCI-state) may include a P0-alpha-CL-loop set ID for PUSCH, a P0-alpha-CL-loop set ID for PUCCH, and a P0-alpha-CL-loop set ID for SRS.

[0230] Furthermore, the TCI state configuration parameter (TCI-state) does not necessarily include the P0-alpha-CL-loop set ID for PUSCH, the P0-alpha-CL-loop set ID for PUCCH, or the P0-alpha-CL-loop set ID for SRS. In this case, the TCI state configuration parameter (TCI-state) and the P0-alpha-CL-loop set ID for PUSCH, the P0-alpha-CL-loop set ID for PUCCH, or the P0-alpha-CL-loop set ID for SRS may be associated via a specific parameter.

[0231] According to embodiment 2-2, different transmission power control is performed for different UL channels / signals, but it is possible to set the same level of transmission power for each of the different UL channels / signals.

[0232] According to the first embodiment, it is possible to appropriately control the transmission power for each UL channel / signal and for each TCI state.

[0233] Comparison Between First and Second Embodiments From the viewpoint of flexibility, it is possible to ensure the same degree of flexibility for both the first and second embodiments.

[0234] For example, if the total number of sets (IDs) of TPC parameters in the first embodiment is the same as the total number of sets (IDs) of TPC parameters for multiple UL channels / signals in the second embodiment, the same degree of flexibility can be ensured for both the first and second embodiments.

[0235] More specifically, for example, the total number of P0-alpha-CL-loop set IDs in the first embodiment may be specified / set as N (e.g., N = 12). Also, the total number of P0-alpha-CL-loop set IDs for PUSCH, the total number of P0-alpha-CL-loop set IDs for PUCCH, and the total number of P0-alpha-CL-loop set IDs for SRS in the second embodiment may each be specified / set as M (e.g., M = 4). In this case, the total number of P0-alpha-CL-loop sets that can be configured for one TCI state for a UE is the same in the first and second embodiments.

[0236] If the same / duplicate combination / value of parameters may be set across multiple UL channels / signals, in this case, it is preferable to apply the above-described first embodiment in terms of signaling overhead and flexibility.

[0237] 15A and 15B are diagrams illustrating an example of a set of TPC parameters for comparison between the first embodiment and the second embodiment. As shown in Fig. 15A, a P0-alpha-CL-loop set for PUSCH, a P0-alpha-CL-loop set for PUCCH, and a P0-alpha-CL-loop set for SRS are configured for a UE, as described in the second embodiment. Each parameter with ID=0 in each set has a duplicate value for each channel / signal (each set includes at least two of P0=-10, alpha=1.0, and CL loop index=0).

[0238] In such a case, it is preferable to be able to set TPC parameters to be applied to multiple channels / signals using one ID using one correspondence, as shown in FIG. 15B.

[0239] That is, when the same / duplicate parameter combinations / values ​​are configured across multiple UL channels / signals, it is preferable to apply the first embodiment in terms of the overhead of higher layer signaling. On the other hand, when the same / duplicate parameter combinations / values ​​are not configured across multiple UL channels / signals, the first embodiment and the second embodiment are comparable in terms of the overhead of higher layer signaling.

[0240] <Modifications of the First and Second Embodiments> <Modification 1> For multiple UL channels / signals, the IDs of sets of multiple TPC parameters do not need to be configured within each TCI state. The set IDs may be configured separately from the TCI state.

[0241] In this case, the set ID and the TCI state may be associated with each other via a specific parameter, and the (set of) the specific parameter may be set / defined separately from the set ID and the TCI state.

[0242] <<Modification 2>> The UE may receive information for updating the setting of the association between the TCI state ID and the ID of the set of TPC parameters for a plurality of UL channels / signals.

[0243] The information may be notified to the UE using, for example, a MAC CE, and the UE may support updating of the association via the MAC CE.

[0244] The MAC CE may include association settings for one or more TCI states.

[0245] This allows for faster updating / setting of parameters related to transmit power control for TCI states.

[0246] <<Variation 3>> The UE may assume / expect that the IDs of the TPC parameter sets (P0-alpha-CL-loop sets) for the associated SRSs are the same for the TCI states of the SRSs of source RSs belonging to the same SRS resource set.

[0247] Fig. 16 is a diagram showing an example of configuration of an SRS resource set, an SRS resource, a TCI state, and a TPC parameter set ID according to Modification 3. In Fig. 16, the same SRS resource set includes SRS resource #0 and SRS resource set #1. SRS resource #0 and SRS resource set #1 correspond to TCI state #0 and TCI state #1, respectively.

[0248] At this time, the UE may assume / expect that TCI state #0 and TCI state #1 are associated with the same TPC parameter set ID (P0-alpha-CL-loop set ID for SRS).

[0249] According to the third modification, similar to Rel. 15 / 16, it is possible to equalize the parameters related to the transmission power control for the SRS resource set. According to the third modification, it is possible to avoid repeating the transmission of SRS for multiple TRPs using different powers.

[0250] Furthermore, when the purpose of the SRS resource set is set to "antenna switching," it is preferable to use the same TPC parameter set for SRS (P0-alpha-CL-loop set) in order to maintain the same transmission power. Variation 3 may be applied based on the purpose of the SRS resource set. Specifically, Variation 3 may be applied when the SRS resource set is set to a specific purpose (e.g., antenna switching). Note that when the purpose of the SRS resource set is set to "antenna switching," the UE may transmit SRS across multiple slots using multiple SRS resource sets.

[0251] Fig. 17 is a diagram showing another example of configuration of an SRS resource set, an SRS resource, a TCI state, and a TPC parameter set ID according to Modification 3. In Fig. 17, a plurality of SRS resource sets (SRS resource set #0, SRS resource set #1) are configured for a UE. SRS resource set #0 includes at least SRS resource #0, and SRS resource set #1 includes at least SRS resource #1. SRS resource #0 and SRS resource set #1 correspond to TCI state #0 and TCI state #1, respectively.

[0252] At this time, the UE may assume / expect that TCI state #0 and TCI state #1 are associated with the same TPC parameter set ID (P0-alpha-CL-loop set ID for SRS).

[0253] The UE may also support the configuration of different SRS TPC parameter set IDs among SRS resources in the same SRS resource set, and may report whether or not it supports this configuration.

[0254] Third Embodiment In a third embodiment, the use of the SRI field will be described.

[0255] <<Embodiment 3-1>> When a common TCI state (joint TCI state / (separate) UL TCI state) is set for a PUSCH, the SRI field may not be included in a DCI format (e.g., DCI format 0_1 / 0_2) that schedules the PUSCH (Embodiment 3-1-1).

[0256] In the present disclosure, a common TCI state is configured for a PUSCH may mean that the TCI state is configured within the parameters of the PUSCH configuration.

[0257] Also, when the common TCI state is set for the PUSCH, the SRI field of the DCI format that schedules the PUSCH may be 0 bits.

[0258] In embodiment 3-1-1, the UE may determine the TPC parameters for the PUSCH based on the TCI field included in the DCI format (for example, DCI format 1_1 / 1_2) that schedules the PDSCH.

[0259] When the common TCI state is set for the PUSCH, a parameter (PUSCH-PowerControl) related to transmission power control of the PUSCH may not be set (embodiment 3-1-2). Also, when the common TCI state is set for the PUSCH, setting of a parameter (PUSCH-PowerControl) related to transmission power control of the PUSCH may not be required.

[0260] When the common TCI state is set for the PUSCH, some specific parameters in the parameters related to the transmission power control of the PUSCH (PUSCH-PowerControl) may not be set (embodiment 3-1-3).

[0261] <<Embodiment 3-2>> When the common TCI state (joint TCI state / (separate) UL TCI state) is not configured for the PUSCH, the UE may determine the SRI based on the method specified in Rel. 15 / 16.

[0262] The SRI field may or may not be present depending on the number of SRS resources whose usage is codebook / non-codebook.

[0263] The UE may determine the TPC parameters for the PUSCH based on the SRI field included in the DCI format that schedules the PUSCH (e.g., DCI format 0_1 / 0_2).

[0264] When the common TCI state is not set for the PUSCH, parameters related to the transmission power control of the PUSCH (PUSCH-PowerControl) may be set. When the common TCI state is not set for the PUSCH, it may be assumed that parameters related to the transmission power control of the PUSCH (PUSCH-PowerControl) are set.

[0265] According to the third embodiment described above, it is possible to appropriately control whether or not to use the SRI field depending on whether or not the common TCI state is set.

[0266] Fourth Embodiment In a fourth embodiment, the setting of a common TCI state for each UL channel / signal will be described.

[0267] <<Embodiment 4-1>> In embodiment 4-1, the setting of a common TCI state (joint TCI state / (separate) UL TCI state) for PUSCH will be described.

[0268] In place of / in addition to a parameter (pusch-PowerControl) related to transmission power control of the PUSCH in the RRC parameters of the PUSCH configuration (e.g., PUSCH-Config), a parameter related to a list of TCI states may be included (Embodiment 4-1-1). The UE may determine the common TCI state for the PUSCH based on a parameter other than the parameter (pusch-PowerControl) related to transmission power control of the PUSCH included in the PUSCH configuration.

[0269] When the RRC parameters for PUSCH configuration include parameters related to a list of TCI states, the parameters related to PUSCH transmission power control (pusch-PowerControl) may not include a specific parameter, which may be, for example, a parameter related to a list of mapping between SRI and PUSCH (e.g., sri-PUSCH-MappingToAddModList / sri-PUSCH-MappingToReleaseList).

[0270] The parameter related to the list of TCI states may be at least one of a parameter related to a list of TCI states to be added / modified (e.g., tci-StateToAddModList, tci-StateToAddModList-r17) and a parameter related to a list of TCI states to be released (e.g., tci-StateToReleaseList, tci-StateToReleaseList-r17). That is, the UE may be configured with multiple TCI states based on the parameter related to the list of TCI states.

[0271] The parameters for the list of TCI states to add / modify may include a specific number of TCI states (e.g., the number specified by maxNrofTCI-States).The parameters for the list of TCI states to release may include a specific number of TCI state IDs (e.g., the number specified by maxNrofTCI-States).

[0272] For the configuration of a common TCI state, the RRC information element (TCI-state) of the TCI state defined up to Rel. 15 may be reused for the TCI state configured by the parameters related to the list of TCI states.

[0273] Furthermore, for the TCI state set by the parameters related to the list of TCI states for configuring the common TCI state, an RRC information element for the common TCI state (e.g., Unified-TCI-state, TCI-state-r17) may be defined / used separately from the RRC information element for the TCI state (TCI-state) defined up to Rel. 15. The parameters related to the list of TCI states may be associated with the RRC information element for the common TCI state (e.g., Unified-TCI-state, TCI-state-r17).

[0274] The RRC information element of the common TCI state (e.g., Unified-TCI-state, TCI-state-r17) may include at least one of a TCI state ID (tci-StateID), a parameter related to QCL type 1 (qcl-Type1), a parameter related to QCL type 2 (qcl-Type2), a parameter related to path loss RS ID (e.g., PUSCH-PathlossReferenceRS-Id), and a parameter (flag) for determining whether the state is joint TCI state or separate TCI state.

[0275] The UE may determine that the common TCI state is configured for the PUSCH when the parameter related to the list of TCI states for the PUSCH is configured, otherwise (e.g., when the parameter related to the transmit power control of the PUSCH (pusch-PowerControl) is configured), the UE may determine that the SRI / spatial relationship of the PUSCH in Rel. 15 / 16 is configured.

[0276] 18 is a diagram illustrating an example of an RRC information element according to embodiment 4-1-1. In FIG. 18, PUSCH-Config includes parameters related to a list of TCI states (tci-StateToAddModList, tci-StateToReleaseList) in addition to pusch-PowerControl. The UE is configured with a common TCI state based on the parameters related to the list of TCI states.

[0277] In place of / in addition to a specific parameter included in a parameter (pusch-PowerControl) related to PUSCH transmission power control in the RRC parameters for PUSCH configuration (e.g., PUSCH-Config), a parameter related to a list of TCI states may be included (Embodiment 4-1-2). In Embodiment 4-1-2, the parameter (PUSCH-PowerControl) related to PUSCH transmission power control may include a parameter related to a list of TCI states.

[0278] The specific parameter may be, for example, at least one of a parameter of a list related to mapping of SRI (spatial relationship) and PUSCH (e.g., sri-PUSCH-MappingToAddModList / sri-PUSCH-MappingToReleaseList) and a parameter related to a list of pathloss reference RSs (e.g., pathlossReferenceRSToAddModList / pathlossReferenceRSToReleaseList).

[0279] For example, the UE may determine the common TCI state for the PUSCH based on parameters other than the parameters related to the mapping of the PUSCH and the SRI (spatial relationship) included in the parameters related to the transmission power control of the PUSCH (pusch-PowerControl).

[0280] The parameter related to the list of TCI states may be at least one of a parameter related to a list of TCI states to be added / modified (e.g., tci-StateToAddModList, tci-StateToAddModList-r17) and a parameter related to a list of TCI states to be released (e.g., tci-StateToReleaseList, tci-StateToReleaseList-r17). That is, the UE may be configured with multiple TCI states based on the parameter related to the list of TCI states.

[0281] The parameters for the list of TCI states to add / modify may include a specific number of TCI states (e.g., the number specified by maxNrofTCI-States).The parameters for the list of TCI states to release may include a specific number of TCI state IDs (e.g., the number specified by maxNrofTCI-States).

[0282] For the configuration of a common TCI state, the RRC information element (TCI-state) of the TCI state defined up to Rel. 15 may be reused for the TCI state configured by the parameters related to the list of TCI states.

[0283] Furthermore, for the TCI state set by the parameters related to the list of TCI states for configuring the common TCI state, an RRC information element for the common TCI state (e.g., Unified-TCI-state, TCI-state-r17) may be defined / used separately from the RRC information element for the TCI state (TCI-state) defined up to Rel. 15. The parameters related to the list of TCI states may be associated with the RRC information element for the common TCI state (e.g., Unified-TCI-state, TCI-state-r17).

[0284] The RRC information element of the common TCI state (e.g., Unified-TCI-state, TCI-state-r17) may include at least one of a TCI state ID (tci-StateID), a parameter related to QCL type 1 (qcl-Type1), a parameter related to QCL type 2 (qcl-Type2), a parameter related to path loss RS ID (e.g., PUSCH-PathlossReferenceRS-Id), and a parameter (flag) for determining whether the state is joint TCI state or separate TCI state.

[0285] The UE may determine that the common TCI state for the PUSCH is configured when the parameter related to the list of TCI states for the PUSCH is configured. Otherwise (e.g., when the above specific parameter is configured), the UE may determine that the SRI / spatial relationship for the PUSCH in Rel. 15 / 16 is configured.

[0286] 19 is a diagram illustrating an example of an RRC information element according to embodiment 4-1-2. In FIG. 19, pusch-PowerControl in PUSCH-Config includes parameters related to a list of TCI states (tci-StateToAddModList, tci-StateToReleaseList). The UE is configured with a common TCI state based on the parameters related to the list of TCI states.

[0287] In embodiment 4-1-2, as shown in FIG. 19, even if PUSCH-PowerControl includes parameters related to the list of TCI states (tci-StateToAddModList, tci-StateToReleaseList), at least one of a parameter related to TPC accumulation (tpc-Accumulation), a parameter related to α of message 3 (msg3-Alpha), a parameter related to P0 of configured grant transmission / SPS transmission (p0-NominalWithoutGrant), and a parameter indicating the application of delta MCS (deltaMCS) may be included in PUSCH-PowerControl.

[0288] <<Embodiment 4-2>> In embodiment 4-2, the setting of a common TCI state (joint TCI state / (separate) UL TCI state) for PUCCH will be described.

[0289] A parameter related to a list of TCI states may be included instead of / in addition to a parameter related to a list of spatial relationship information in the RRC parameters of the PUCCH configuration (e.g., PUCCH-Config). For example, the UE may determine the common TCI state for the PUCCH based on a parameter other than the parameter related to the list of spatial relationship information (pusch-PowerControl) included in the PUCCH configuration.

[0290] The parameters related to the list of spatial relationship information may be, for example, at least one of spatialRelationInfoToAddModList, spatialRelationInfoToReleaseList, pucch-PowerControl, spatialRelationInfoToAddModListSizeExt-v1610, spatialRelationInfoToReleaseListSizeExt-v1610, spatialRelationInfoToAddModListExt-v1610, and spatialRelationInfoToReleaseListExt-v1610.

[0291] The parameters relating to the list of TCI states may be at least one of parameters relating to the list of TCI states to be added / modified (e.g., tci-StateToAddModList, tci-StateToAddModList-r17) and parameters relating to the list of TCI states to be released (e.g., tci-StateToReleaseList, tci-StateToReleaseList-r17).

[0292] The parameters for the list of TCI states to add / modify may include a specific number of TCI states (e.g., the number specified by maxNrofTCI-States).The parameters for the list of TCI states to release may include a specific number of TCI state IDs (e.g., the number specified by maxNrofTCI-States).

[0293] For the configuration of a common TCI state, the RRC information element (TCI-state) of the TCI state defined up to Rel. 15 may be reused for the TCI state configured by the parameters related to the list of TCI states.

[0294] Furthermore, for the TCI state set by the parameters related to the list of TCI states for configuring the common TCI state, an RRC information element for the common TCI state (e.g., Unified-TCI-state, TCI-state-r17) may be defined / used separately from the RRC information element for the TCI state (TCI-state) defined up to Rel. 15. The parameters related to the list of TCI states may be associated with the RRC information element for the common TCI state (e.g., Unified-TCI-state, TCI-state-r17).

[0295] The RRC information element of the common TCI state (e.g., Unified-TCI-state, TCI-state-r17) may include at least one of a TCI state ID (tci-StateID), a parameter related to QCL type 1 (qcl-Type1), a parameter related to QCL type 2 (qcl-Type2), a parameter related to pathloss RS ID (e.g., PUCCH-PathlossReferenceRS-Id), and a parameter (flag) for determining whether the state is joint TCI state or separate TCI state.

[0296] The UE may determine that a common TCI state is configured for the PUCCH when the parameter for the list of TCI states for the PUCCH is configured, otherwise (e.g., when the parameter for the list of spatial relationship information is configured), the UE may determine that the SRI / spatial relationship of the PUCCH in Rel. 15 / 16 is configured.

[0297] 20 is a diagram illustrating an example of an RRC information element according to embodiment 4-2. In FIG. 20, PUCCH-Config includes parameters related to a list of TCI states (tci-StateToAddModList, tci-StateToReleaseList) in addition to parameters related to a list of spatial relationship information. The UE is configured with a common TCI state based on the parameters related to the list of TCI states.

[0298] According to the above embodiments 4-1 and 4-2, it is possible to determine whether or not a common TCI state is applied for each UL channel / signal. The UE may determine whether or not a common TCI state is applied to each UL channel / signal.

[0299] The UE may receive a MAC CE that associates each of the configured PUCCH resources with a TCI state ID, and may determine the TCI state corresponding to the PUCCH resource based on the MAC CE.

[0300] In the present disclosure, the UE may control the accumulation of TPC commands to be performed for each UL channel / signal. Also, the UE may control the accumulation of TPC commands to be performed for each TCI state (for each common TCI state). Also, the UE may control the accumulation of TPC commands to be performed for each UL channel / signal and for each TCI state (for each common TCI state).

[0301] According to the fourth embodiment described above, the common TCI state of the PUSCH / PUCCH is appropriately set, and based on the set TCI state, transmission power control can be performed appropriately by combining with the first to third embodiments.

[0302] Fifth Embodiment In a fifth embodiment, open loop power control (OLPC) will be described.

[0303] When a common TCI state (joint TCI state / (separate) UL TCI state) is set for the PUSCH, open-loop power control parameters (e.g., p0-List / p0-List-r16 / p0-List-r17) may be added to the set of TPC parameters described in the first embodiment / second embodiment.

[0304] The UE may determine whether to apply the open-loop power control parameters based on at least one of the open-loop power control parameters configured using higher layer signaling, the open-loop power control parameter set indication field included in the DCI, and the presence or absence of a common TCI state (TCI field) in the DCI.

[0305] For example, when the DCI format includes an open-loop power control parameter set indication field and the value of the field indicates a first value (e.g., 1), the UE may apply the open-loop power control parameters (p0-List). In this case, the DCI may include the common TCI state (TCI field thereof), or the DCI may not include the common TCI state (TCI field thereof), and one open-loop P0 may be configured in the open-loop power control parameters (e.g., p0-List-r16).

[0306] Furthermore, when the DCI format includes an open-loop power control parameter set indication field and the value of the field indicates a second value (e.g., 10 or 01), the UE may apply the open-loop power control parameters (p0-List). In this case, the DCI does not include the common TCI state (TCI field), and two open-loop P0s may be configured in the open-loop power control parameters (e.g., p0-List-r16).

[0307] For example, when the DCI format includes an open-loop power control parameter set indication field and the value of the field indicates a first value (e.g., 1), the UE may apply the open-loop power control parameters (p0-List). In this case, the DCI may include an SRI field, or the DCI may not include an SRI field and one open-loop P0 may be configured in the open-loop power control parameters (e.g., p0-List-r16).

[0308] Furthermore, when the DCI format includes an open-loop power control parameter set indication field and the value of the field indicates a second value (e.g., 10 or 01), the UE may apply the open-loop power control parameters (p0-List). In this case, the DCI may not include an SRI field, and two open-loop P0s may be configured in the open-loop power control parameters (e.g., p0-List-r16).

[0309] Fig. 21 is a diagram illustrating an example of a plurality of sets of TPC parameters according to the fifth embodiment. In the example illustrated in Fig. 21, a plurality of sets of P0, α (alpha), CL loop index, and open loop power control parameters (referred to as p0-List) are configured for a UE. The sets are identified by a P0-alpha-CL-loop set ID.

[0310] Each open-loop power control parameter (p0-List) may include one P0 value under a first condition. The first condition may be, for example, when a common TCI state is set for the PUSCH. Alternatively, the first condition may be, for example, when a common TCI state is not set for the PUSCH and both a first specific upper layer parameter (e.g., olpc-ParameterSetDCI-0-1) and a second specific upper layer parameter (olpc-ParameterSetDCI-0-2) are set to N bits (e.g., N=1).

[0311] Alternatively, the first condition may be, for example, when an SRI field is present in the DCI. Alternatively, the first condition may be, for example, when an SRI field is not present in the DCI and both a first specific upper layer parameter (e.g., olpc-ParameterSetDCI-0-1) and a second specific upper layer parameter (olpc-ParameterSetDCI-0-2) are set to N bits (e.g., N=1).

[0312] Furthermore, each open-loop power control parameter (p0-List) may include two P0 values ​​under a second condition, which may be, for example, when the common TCI state is not configured for the PUSCH and either the first specific upper layer parameter (e.g., olpc-ParameterSetDCI-0-1) or the second specific upper layer parameter (olpc-ParameterSetDCI-0-2) is set to M bits (e.g., M=2).

[0313] Furthermore, each open-loop power control parameter (p0-List) may include two P0 values ​​under a second condition, which may be when the SRI field is not present in the DCI and either the first specific upper layer parameter (e.g., olpc-ParameterSetDCI-0-1) or the second specific upper layer parameter (olpc-ParameterSetDCI-0-2) is set to M bits (e.g., M=2).

[0314] The open loop power control parameters (p0-List) may be included and set in the TCI state setting parameters (TCI-state).

[0315] Also, the parameters for open loop power control (p0-List) may be associated with the TCI state separately from the P0 / α / CL loop index. This association may be via a specific parameter.

[0316] In addition, the parameters for open loop power control (p0-List) may be associated with the SRI.

[0317] According to the fifth embodiment, even when TCI states that are applied to a plurality of channels are set, open-loop transmission power control can be performed appropriately.

[0318] Sixth Embodiment An upper layer parameter (RRC IE) / UE capability corresponding to a function (feature) in at least one of the above embodiments may be defined. The UE capability may indicate that the function is supported.

[0319] A UE configured with higher layer parameters corresponding to the function (enabling the function) may perform the function. It may also be specified that "a UE not configured with higher layer parameters corresponding to the function shall not perform the function (for example, in accordance with Rel. 15 / 16)."

[0320] A UE that reports a UE capability indicating that it supports the function may perform the function. It may also be specified that a UE that does not report a UE capability indicating that it supports the function shall not perform the function (e.g., in accordance with Rel. 15 / 16).

[0321] If the UE reports a UE capability indicating that it supports the function and the corresponding higher layer parameters are configured, the UE may perform the function. It may also be specified that "if the UE does not report a UE capability indicating that it supports the function or if the corresponding higher layer parameters are not configured, the UE shall not perform the function (e.g., in accordance with Rel. 15 / 16)."

[0322] The UE capability may indicate whether the UE supports this feature.

[0323] The functionality may be a unified TCI state framework.

[0324] UE capability may be defined as whether or not it supports the unified TCI state.

[0325] UE capability may be defined as whether or not it supports the unified TCI state for a particular channel / signal.

[0326] UE capability may be defined as whether or not it supports unified TCI state for PUSCH.

[0327] UE capability may be defined as whether or not it supports the unified TCI state for PUCCH.

[0328] UE capability may be defined as whether or not it supports the unified TCI state for SRS.

[0329] UE capability may be defined as whether or not it supports configuration of TPC parameters / PL-RS per unified TCI state for a particular channel / signal, and whether or not it supports updating of TPC parameters / PL-RS by MAC CE per unified TCI state for a particular channel / signal.

[0330] The UE capability may be defined by whether or not it supports configuration of TPC parameters / PL-RS for each unified TCI state for PUSCH, and whether or not it supports updating of TPC parameters / PL-RS by MAC CE for each unified TCI state for PUSCH.

[0331] The UE capability may be defined by whether or not it supports configuration of TPC parameters / PL-RS per unified TCI state for PUCCH, and whether or not it supports updating of TPC parameters / PL-RS by MAC CE per unified TCI state for PUCCH.

[0332] The UE capability may be defined by whether it supports configuration of TPC parameters / PL-RS per unified TCI state for SRS, and whether it supports updating of TPC parameters / PL-RS by MAC CE per unified TCI state for SRS.

[0333] The UE capability may be defined by the number of IDs of the sets of TPC parameters that the UE supports in the first and second embodiments.

[0334] UE capability may be defined as whether or not the UE operations related to the descriptions of each of the above embodiments are supported.

[0335] According to the sixth embodiment, the UE can achieve the above functions while maintaining compatibility with existing specifications.

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

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

[0338] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0339] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (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.

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

[0341] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

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

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

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

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

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

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

[0348] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0349] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0350] In the wireless communication system 1, 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. may be used as the downlink channel.

[0351] Furthermore, in the wireless communication system 1, 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)), or the like may be used as an uplink channel.

[0352] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

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

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

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

[0356] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0357] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0358] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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

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

[0361] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0362] 23 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

[0364] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0366] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0367] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0368] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

[0370] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

[0375] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0376] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

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

[0378] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0379] The transceiver 120 may transmit first information including a plurality of sets of transmission power control parameters and second information relating to a transmission configuration indication (TCI) state corresponding to one of the sets. The controller 110 may use the first information and the second information to set transmission power control for each TCI state to be applied to at least one of a specific uplink channel and a signal (first, second, and fifth embodiments).

[0380] The transceiver 120 may transmit a Radio Resource Control (RRC) information element related to the configuration of an uplink channel, the RRC information element being associated with configuration information related to a list of transmission configuration indication (TCI) states to be applied to at least one of a plurality of channels and signals. The controller 110 may use the configuration information to configure a TCI state to be applied to each uplink channel (fourth embodiment).

[0381] (User terminal) Fig. 24 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0382] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

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

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

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

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

[0387] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

[0389] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

[0392] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

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

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

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

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

[0397] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220, the transmitting / receiving antenna 230, and the transmission path interface 240.

[0398] The transceiver 220 may receive first information including a plurality of sets of transmission power control parameters and second information related to a transmission configuration indication (TCI) state corresponding to one of the sets. The controller 210 may perform transmission power control for each TCI state to be applied to at least one of a specific uplink channel and a signal based on the first information and the second information (first, second, and fifth embodiments).

[0399] The parameters included in the set may be at least two of a parameter related to a transmit power offset (e.g., P0), a parameter related to a fractional factor (e.g., α), a parameter related to a closed-loop index, and a parameter related to a transmit power offset in open-loop transmit power control (first, second, and fifth embodiments).

[0400] The plurality of sets of transmission power control parameters may be a set common to at least one of a plurality of uplink channels and signals (first and fifth embodiments).

[0401] When a TCI state to be applied to at least one of a plurality of channels and signals is set, the control unit 210 may determine a parameter for transmission power control of the uplink shared channel based on a TCI field included in downlink control information that schedules the downlink shared channel (third embodiment).

[0402] The transceiver 220 may receive Radio Resource Control (RRC) information elements related to uplink channel configuration, the RRC information elements being associated with configuration information related to a list of transmission configuration indication (TCI) states to be applied to at least one of a plurality of channels and signals. The controller 210 may determine the TCI state to be applied to each uplink channel based on the configuration information (fourth embodiment).

[0403] The setting information may be included in a physical uplink shared channel (PUSCH) setting. The control unit 210 may determine the TCI state based on a parameter other than a parameter related to transmission power control of the PUSCH (fourth embodiment).

[0404] The setting information may be included in a parameter related to transmission power control of a physical uplink shared channel (PUSCH) included in a PUSCH setting. The control unit 210 may determine the TCI state based on a parameter other than the parameter related to mapping between the PUSCH and spatial relationship information (fourth embodiment).

[0405] The configuration information may be included in a physical uplink control channel (PUCCH) configuration. The control unit 210 may determine the TCI state based on a parameter other than the parameter related to the list of spatial relationship information (fourth embodiment).

[0406] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0407] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

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

[0409] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0410] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

[0412] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0413] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

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

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

[0416] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0417] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0418] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0419] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0420] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0421] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0422] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

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

[0424] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0425] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

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

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

[0428] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

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

[0430] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0431] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

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

[0433] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0434] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0436] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

[0438] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0439] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

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

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

[0443] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0444] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

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

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

[0447] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0448] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0449] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0450] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0451] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0452] 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," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

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

[0454] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0455] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

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

[0457] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0458] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0459] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0460] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0461] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0462] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), 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.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (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 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on these and are extended thereto. In addition, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0463] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0464] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

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

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

[0467] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0468] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

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

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

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

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

[0473] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

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

[0475] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiving unit that receives configuration information regarding a list of uplink (UL) transmission configuration indication (TCI) states, a first set of transmission power control (TPC) parameters for a physical uplink shared channel (PUSCH), a second set of TPC parameters for a physical uplink control channel (PUCCH), and a third set of TPC parameters for a sounding reference signal, and for each UL TCI state ID configured by the configuration information, the first set, the second set, and the third set correspond to each other. A terminal having a control unit that controls the transmission power of the PUSCH based on the configuration information and the first set.

2. The first set includes parameters related to P0, parameters related to α, and parameters related to a closed-loop index. The terminal according to claim 1, wherein the second set includes parameters related to P0 and parameters related to a closed-loop index, and does not include parameters related to α.

3. A step of receiving configuration information regarding a list of uplink (UL) transmission configuration indication (TCI) states, a first set of transmission power control (TPC) parameters for a physical uplink shared channel (PUSCH), a second set of TPC parameters for a physical uplink control channel (PUCCH), and a third set of TPC parameters for a sounding reference signal, and for each UL TCI state ID configured by the configuration information, the first set, the second set, and the third set correspond to each other. A wireless communication method for a terminal having a step of controlling the transmission power of the PUSCH based on the configuration information and the first set.

4. A transmitting unit that transmits configuration information regarding a list of uplink (UL) transmission configuration indication (TCI) states, a first set of transmission power control (TPC) parameters for a physical uplink shared channel (PUSCH), a second set of TPC parameters for a physical uplink control channel (PUCCH), and a third set of TPC parameters for a sounding reference signal, and for each UL TCI state ID configured by the configuration information, the first set, the second set, and the third set correspond to each other. A base station having a control unit that uses the setting information and the first set to instruct control of the transmission power of PUSCH. **Claim 5**: A system having a base station and a terminal, wherein the base station transmits setting information regarding a list of uplink (UL) transmission configuration indication (TCI) states, a first set of transmission power control (TPC) parameters for a physical uplink shared channel (PUSCH), a second set of TPC parameters for a physical uplink control channel (PUCCH), and a third set of TPC parameters for a sounding reference signal, and has a transmission unit in which the first set, the second set, and the third set correspond to each UL TCI state ID set by the setting information. wherein the terminal has a receiving unit that receives the setting information, the first set, the second set, and the third set, and has a control unit that controls the transmission power of PUSCH based on the setting information and the first set.