Terminal, wireless communication method, and base station

Abstract

A terminal according to an aspect of the present disclosure comprises: a reception unit that receives either a first Radio Resource Control (RRC) parameter or a second RRC parameter, wherein the first RRC parameter and the second RRC parameter indicate a start position of a block in downlink control information (DCI) for a transmission power control (TPC) command instruction for a sounding reference signal (SRS), and the second RRC parameter is indicated as any one among 1 to a first integer greater than 31 or indicated as any one among a second integer greater than 31 to a third integer greater than 31; and a control unit that controls transmission of the SRS on the basis of any one among the first RRC parameter and the second RRC parameter. According to one aspect of the present disclosure, communications using a DL TRP and a UL TRP can be appropriately controlled.

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 (registered trademark)) 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, in order to expand UL coverage, it is being considered to install UL receiving points in addition to general transmitting and receiving points. Also, UL high-density deployment using DL transmitting points / macro Base Stations (BS) and UL receiving points / micro BSs is being considered.

[0006] However, there are cases where sufficient consideration has not been given to communications using DL TRP and UL TRP.

[0007] If this consideration is not sufficient, the UE may not be able to properly control communications using the DL TRP and the UL TRP, which may result in a decrease in throughput.

[0008] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control communications that use DL TRP and UL TRP.

[0009] A terminal according to one aspect of the present disclosure includes a receiver that receives either a first Radio Resource Control (RRC) parameter or a second RRC parameter, wherein the first RRC parameter and the second RRC parameter indicate a start position of a block in downlink control information (DCI) for transmit power control (TPC) command indication for a sounding reference signal (SRS), and the second RRC parameter is indicated by a first integer from 1 to greater than 31, or by a second integer from greater than 31 to a third integer greater than 31; and a controller that controls transmission of the SRS based on either the first RRC parameter or the second RRC parameter.

[0010] According to one aspect of the present disclosure, communications using DL TRP and UL TRP can be appropriately controlled.

[0011] Figure 1A is a diagram illustrating an example of a typical transmission / reception point deployment. Figure 1B is a diagram illustrating an example of an UL high-density deployment. Figure 2 is a diagram illustrating an example of DL / UL coverage in a Heterogeneous Network (HetNet). Figure 3A is a diagram illustrating an example of an association between RS indexes and PL values. Figure 3B is a diagram illustrating an example of an association between RS indexes and delta PL values. Figure 4 is a diagram illustrating an example of Option 1 in UL high-density deployment. Figure 5 is a diagram illustrating an example of Option 2 in UL high-density deployment. Figure 6 is a diagram illustrating an example of power control parameters related to TCI states. Figure 7 is a diagram illustrating an example of a TCI-State information element in Rel. 17. Figures 8A and 8B are diagrams illustrating an example of UL power control parameters in Rel. 17. Figure 9 is a conceptual diagram illustrating an example of an asymmetric DL sTRP / UL mTRP deployment scenario. Figure 10 is a conceptual diagram illustrating an example of SRS transmission according to Aspect 1. Figure 11 is a diagram illustrating an example of SRS configuration according to Aspect 1. 12A and 12B are diagrams illustrating an example of a TPC command (DCI) field. 13A and 13B are diagrams illustrating an example of the starting position of bits for each UE in DCI format 2_3. 14 is a diagram illustrating an example of RRC parameters according to embodiment 0-1. 15 is a diagram illustrating an example of RRC parameters according to embodiment 0-2. 16 is a diagram illustrating an example of setting the maximum value indicated by the second RRC parameter according to embodiment 1-2. 17 is a diagram illustrating another example of setting the maximum value indicated by the second RRC parameter according to embodiment 1-2. 18 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. 19 is a diagram illustrating an example of a configuration of a base station according to an embodiment. 20 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. 21 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. 22 is a diagram illustrating an example of a vehicle according to an embodiment.

[0012] (Scenario 1: UL Dense Deployment (UL-Only TRP)) In Rel. 15 NR, the coverage (reaching distance) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is uneven. PUSCH coverage is limited, especially at high frequencies. Future wireless communication systems (e.g., Rel. 18, Rel. 19, or later) are expected to improve at least one of UL coverage and UL throughput.

[0013] In order to expand UL coverage, the installation of UL reception points in addition to general transmission and reception points is being considered. Therefore, an example of the arrangement of general transmission and reception points and an example of an arrangement with UL reception points (UL high-density arrangement) will be described.

[0014] 1A is a diagram showing an example of a typical arrangement of transmission / reception points. In FIG. 1A, a UE receives a DL signal from a transmission / reception point (TRP) and transmits a UL signal to the TRP. For example, if the UE and the TRP are far apart, the path loss may be large, resulting in a deterioration in communication quality.

[0015] Figure 1B is a diagram showing an example of a high-density UL deployment. To expand UL coverage, it is considered to provide UL reception points as shown in Figure 1B in addition to the DL transmission points as shown in Figure 1A. In Figure 1B, a UE receives DL signals from a DL transmission point (TRP / Central TRP / DL TRP / Macro TRP) corresponding to a macro cell and transmits UL signals to a UL reception point (e.g., a reception point with a smaller path loss / reception power). However, the UE may also be capable of UL transmission to a DL transmission point.

[0016] By using a high-density UL configuration such as that shown in Figure 1B, it is possible to improve both coverage and UL data rates by reducing path loss, improving UL signaling quality, and obtaining a higher coding rate compared to a general configuration such as that shown in Figure 1A. Furthermore, since the UL reception point mainly performs reception, it requires fewer functions (e.g., power amplifiers) and is therefore less costly than a transmission / reception point corresponding to a general small cell, making deployment management much easier.

[0017] (Scenario 2: Decoupling of DL TRP and UL TRP in HetNet) In the present disclosure, a Heterogeneous Network (HetNet) using a macro Base Station (BS) (DL TRP) and a micro BS (UL TRP) may be applied (FIG. 2). In a typical HetNet, the transmission power of the macro BS and the micro BS is different. Also, the optimal DL coverage and the optimal UL coverage are different. For example, the DL coverage is determined by the RSRP, and the UL coverage is determined by the path loss (PL).

[0018] In the example of FIG. 2, the UE is included in the optimal DL coverage of the macro BS and the optimal UL coverage of the micro BS. In this case, the UE can receive DL from the macro BS and transmit UL to the micro BS. However, the UE may transmit some reference signals / channels (e.g., SRS with Antenna Switching (AS) usage, used to acquire DL CSI) to the macro BS. Therefore, the UE may require two timing advances (TAs) in this scenario. Note that the AS SRS is transmitted to the macro BS because it is intended for the base station (macro BS) to measure DL CSI (e.g., determine the DL MIMO precoder) based on the reception of the SRS using channel reciprocity. On the other hand, the codebook / non-codebook SRS is transmitted to the micro BS because it is used for determining the precoder / beam of the PUSCH.

[0019] In a HetNet, even if a micro BS has DL transmission capability, it can save energy by turning off DL most of the time, in which case the function of the micro BS is similar to a UL-only TRP (UL Reception Point).

[0020] (Receiving Path Loss (PL)) The UE may receive first information indicating a path loss (PL) used for transmission power control (TPC), which is estimated and notified (transmitted) by the network, via DL signaling. The DL signaling may be at least one of higher layer signaling (e.g., RRC or MAC CE) and physical layer signaling (e.g., Downlink Control Information (DCI)).

[0021] The UE receives the path loss (PL ｂ，ｆ，ｃ (q ｄ ), P.L. ｂ，ｆ，ｃ ) (index q ｄ The active UL BWP of carrier f of serving cell c (path loss for b) may be used to calculate the UL signal transmission power (for example, the transmission power of PUSCH / PUCCH / SRS / PRACH) for a reception point that does not transmit downlink data.

[0022] [Option 1] The absolute path loss (PL) value [dB] for each RS index may be reported (transmitted) from the network to the UE, and the UE may use the reported absolute path loss value directly in calculating the transmit power.

[0023] [Option 2] The network may notify (transmit) a relative path loss (Delta PL) value [dB] for each RS index to the UE. The UE may use the path loss value obtained by applying (adding or subtracting) the received Delta PL value to the conventional path loss value estimated from the DL RS transmitted from the macro cell (macro BS / central TRP) for calculating the transmission power.

[0024] The PL value / delta PL value in options 1 and 2 is q ｄThe PL value / delta PL value may be notified / configured for each index of the RS / SSB / CSI-RS / SRS resource / SRS resource set. One or more RS indices and the PL value / delta PL value corresponding to each RS index may be notified by DL signaling. The PL value / delta PL value may be interpreted as a PL parameter / delta PL parameter.

[0025] FIG. 3A is a diagram showing an example of the association between RS indexes and PL values. FIG. 3B is a diagram showing an example of the association between RS indexes and delta PL values. The association (correspondence) between RS indexes and PL values / delta PL values ​​is not limited to that shown in FIGS. 3A and 3B. For example, one RS index may correspond to multiple PL values / delta PL values. Note that a quantization table (range and step) for PL values / delta PL values ​​may be predefined in the specifications. The notified PL values / delta PL values ​​may be quantized values ​​or indices of quantized values.

[0026] Figure 4 shows an example of Option 1 in UL dense deployment. The UL reception point receives / measures the UL signal. If the DL transmission point (macro TRP / gNB) knows the transmission power of this UL signal, the DL transmission point can know the exact PL value of the UL reception point. In this case, the DL transmission point can notify the UE of the absolute PL value (X [dB]) of the UL reception point.

[0027] Figure 5 shows an example of Option 2 in a UL dense deployment. When both the DL transmission point (macro TRP / gNB) and the UL reception point measure the same resource, the DL transmission point can recognize the difference between the PL between the DL transmission point and the UE and the PL between the UL reception point and the UE. In this case, the DL transmission point may notify the UE of this difference (relative PL / delta PL). The relative PL / delta PL may also be referred to as PL offset.

[0028] As described above, even if the UE is not notified of the DL RS (RS index) used for path loss estimation, the UE can calculate the transmission power using the notified PL value / delta PL value.

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

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

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

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

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

[0034] A plurality of types of QCLs (QCL types) 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.

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

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

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

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

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

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

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

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

[0043] (UL Power Control Parameters for TCI States) Fig. 6 is a diagram showing examples of power control parameters related to TCI states. As shown in Fig. 6, the power control parameters of the path loss RS and the PUSCH / PUCCH / SRS are associated with the TCI states.

[0044] When the Rel. 17 TCI state is set, the Rel. 15 / 16 TCI state and spatial relationship information (except positioning) cannot be set in the same band. For channels / RSs that do not apply the indicated TCI state, the Rel. 17 TCI state may be set instead of the Rel. 15 / 16 TCI state and spatial relationship information.

[0045] The UE may transmit UE capability information indicating that different power control parameters are associated with each TCI state. If the UE does not support this UE capability, default power control parameters may be used. Figure 7 shows an example of the TCI-State information element in Rel. 17. The default power control parameter is, for example, the pathlossReferenceRS-Id (pathlossReferenceRS-Id-r17) in Figure 7.

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

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

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

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

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

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

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

[0053] RRC parameters (information elements) configure multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the configured multiple TCI states. DCI may indicate one of the activated multiple TCI states. DCI may be 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 UL TCI and DL TCI.

[0054] In this example, 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.

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

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

[0057] 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 UL and DL may be configured / activated.

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

[0059] It is assumed that in Rel. 17 NR and later, the MAC CE / DCI supports beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and in Rel. 18 NR and later, the MAC CE / DCI supports indicating a serving cell change to a cell with a different PCI.

[0060] [Channels / RSs to which the indicated TCI state in Rel. 17 applies] The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:

[0061] [PDCCH] - If followUnifiedTCIState is configured for CORESET0, the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs with USS / CSS type 3 and index other than 0, the indicated TCI state always applies. - For CORESETs with index other than 0 and at least CSS type other than 3, if followUnifiedTCIState is configured, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0062] [PDSCH] - The indicated TCI state always applies to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in CSS), the indicated TCI state may apply if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules that PDSCH). Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.

[0063] [CSI-RS] For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.

[0064] [PUCCH] - For all dedicated PUCCH resources, the indicated TCI state always applies.

[0065] [PUSCH] - For dynamic / configured grant PUSCH, the indication TCI state always applies.

[0066] [SRS] - When the SRS resource set for the A-SRS used for beam management and the A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state is applied. For other SRSs, the configured TCI state in the SRS resource set is applied.

[0067] [Channels / RSs to which the indicated TCI state applies in Rel. 18] When single DCI multi-TRP is applied, the indicated TCI state may be applied to the following channels / RSs: Note that applyIndicatedTCIState={1st, 2nd, both} in the following description is a parameter indicating whether the first TCI state, the second TCI state, or both the first and second TCI states apply.

[0068] [PDCCH] - For CORESET 0, followUnifiedTCIState is set and applyIndicatedTCIState={1st,2nd,both} is set to indicate that the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET 0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs other than index 0 with USS / CSS type 3, applyIndicatedTCIState={1st,2nd,both} is set per CORESET to indicate that the indicated TCI state applies. For CORESETs other than index 0 with at least a CSS other than CSS type 3, if the Unified TCI state is configured to be followed, applyIndicatedTCIState={1st,2nd,both} is set for each CORESET to indicate that the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0069] [PDSCH] - For all UE-dedicated PDSCHs, one or both of the indicated TCI states always apply. - For PDSCHs scheduled / activated by DCI1_1 / 1_2, the 2-bit TCI state selection field of that DCI1_1 / 1_2 can indicate {1st, 2nd, both}. If the TCI state selection field is not set, both indicated TCI states apply. - For PDSCHs scheduled / activated by DCI1_0, {1st, 2nd, both} are configured by RRC. - "both" can only be configured if PDSCH-CJT or PDSCH-SFN is configured.

[0070] [CSI-RS] If followUnifiedTCIState is set for an A-CSI-RS for CSI acquisition or beam management (for the CORESET of the PDCCH that triggers that A-CSI-RS), applyIndicatedTCIState={1st,2nd,both} is set for each CSI-RS resource or CSI-RS resource set to indicate that the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS resource applies.

[0071] [PUCCH] - applyIndicatedTCIState={1st, 2nd, both} is set for each PUCCH resource / PUCCH resource group.

[0072] [PUSCH] - For dynamic / configured grant PUSCH, the indicated TCI state is always applied. - For PUSCH scheduled / activated by DCI0_0, the first indicated TCI state is always applied. - For Type 1 CG PUSCH, applyIndicatedTCIState={1st,2nd,both} is set. - The SRS resource set indication field indicates one / both of the SRS resource sets used.

[0073] [SRS] When the SRS resource set for A-SRS used for beam management and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, applyIndicatedTCIState={1st,2nd,both} is set for each SRS resource set to indicate that the indicated TCI state applies. For other SRSs, the configured TCI state in that SRS resource set applies.

[0074] In the present disclosure, the terms "indicated TCI state," "unified TCI state," "TCI state applied to channels / signals configured to follow the unified TCI state," "TCI state applied to a UE-specific PDSCH and a CORESET / PDCCH associated with a USS," and "TCI state applied to a PUCCH and a PUSCH" may be interchangeable.

[0075] (UL Power Control Parameters for Unified TCI State in Rel. 17) In the unified TCI state in Rel. 17, the UE is provided with UL power control parameters (RRC information element "ul-powerControl-r17") included in the UE-specific UL BWP configuration (RRC information element "BWP-UplinkDedicated") (see Fig. 8A). If the UE is not configured with UL power control (ul-powerControl) for the UL TCI state / joint TCI state of the serving cell, these parameters are used for transmit power control of UL transmissions.

[0076] The UL power control parameter (RRC information element "ul-powerControl-r17") corresponds to a UL power control parameter ID (Uplink-powerControlId-r17), and the UL power control parameter is identified by this ID.

[0077] The UL power control parameters (RRC information element "uplink-powerControl-r17") corresponding to "ul-powerControl-r17" include at least one of a set of P0 and α for PUSCH (p0AlphaSetforPUSCH-r17), a set of P0 and α for PUCCH (p0AlphaSetforPUCCH-r17), and a set of P0 and α for SRS (p0AlphaSetforSRS-r17), and are used for transmission power control of each channel / signal (see FIG. 8B).

[0078] Also, in the Rel. 17 unified TCI framework, the RRC / MAC CE / DCI indicates one joint TCI or one set of {DL TCI, UL TCI} (separate TCI), where the indicated TCI applies to multiple UL / DL channels / RSs.

[0079] (Unified TCI Status for Multi-TRP in Rel. 18) In Rel. 18, the specification for unified TCI for multi-TRP has been extended. For example, in the case of multi-TRP with a single DCI, the UE may be indicated up to two joint TCIs or up to two sets of {DL TCI, UL TCI} by the RRC / MAC CE / DCI. In the case of multi-TRP with multi-DCI, the UE may be indicated one joint TCI or one set of {DL TCI, UL TCI} per coresetPoolIndex by the RRC / MAC CE / DCI. The indicated TCI applies to multiple UL / DL channels / RSs. The association of the first and second indicated TCIs with each UL / DL channel / RS may be predefined in the specification, configured by RRC signaling, or indicated by DCI.

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

[0081] 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 (PUSCH power control adjustment state) with index l, the transmission power (P ＰＵＳＣＨ、ｂ，ｆ，ｃ (i, j, q ｄ , l)) [dBm] is expressed as follows (Equation 1): ＣＭＡＸ，ｆ，ｃ（ｉ） , P Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j), M ＰＵＳＣＨ ＲＢ，ｂ，ｆ，ｃ (i), α ｂ，ｆ，ｃ (j), P.L. ｂ，ｆ，ｃ (q ｄ ), Δ ＴＦ，ｂ，ｆ，ｃ (i), f ｂ，ｆ，ｃ(i, l), may be based on at least one of

[0082] (Formula 1)

[0083] The power control adjustment state may be referred to as a closed loop (CL)-power control (PC) state, a value based on TPC commands of a power control adjustment state index l, an accumulated value of TPC commands, or a value due to closed loop, where l may be referred to as a closed loop index.

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

[0085] P ＣＭＡＸ，ｆ，ｃ (i) is, for example, the maximum transmit power of the user terminal configured for carrier f of serving cell c at transmission opportunity i (configured maximum output power, UE configured maximum output power).

[0086] P Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) 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, a target received power parameter, etc.) set for the active UL BWP b of the carrier f of the serving cell c at the transmission opportunity i. Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) is P Ｏ＿ＮＯＭＩＮＡＬ＿ＰＵＳＣＨ，ｆ，ｃ (j) and P Ｏ＿ＵＥ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ It may be the sum of (j).

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

[0088] PL ｂ，ｆ，ｃ (q ｄ) is, for example, an index q of a reference signal (RS, pathloss reference RS, pathloss (PL)-RS, pathloss reference RS, pathloss measurement DL-RS, 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 estimation [dB], path loss compensation) calculated by the user terminal using

[0089] If the UE is not provided with a pathloss 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 a synchronization signal (SS) / physical broadcast channel (PBCH) block (SS block (SSB)) used to obtain a Master Information Block (MIB). ｂ，ｆ，ｃ (q ｄ ) may be calculated.

[0090] 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-PathlossReferenceRSs) 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 channel state information (CSI)-reference signal (RS) resource indices. ｄ may be identified.

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

[0092] When a UE is provided with a power control configuration for the PUSCH by a sounding reference signal (SRS) resource indicator (SRI) (e.g., SRI-PUSCH-PowerControl) and with one or more values ​​of 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.

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

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

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

[0096] For the PUSCH transmission configured by the configuration grant configuration, if the configuration grant configuration does not include a specific parameter, the UE may determine 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.

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

[0098] f ｂ，ｆ，ｃ (i, l) is the PUSCH power control adjustment state for the active UL BWP b of carrier f of serving cell c at transmission opportunity i. ｂ，ｆ，ｃ (i,l) may be based on δPUSCH,b,f,c(i,l).

[0099] If TPC accumulation is valid, f ｂ，ｆ，ｃ (i,l) may be based on the accumulated value of δPUSCH,b,f,c(m,l).

[0100] If TPC accumulation is invalid, f ｂ，ｆ，ｃ (i,l) may be δPUSCH,b,f,c(i,l) (absolute value).

[0101] If information indicating that TPC accumulation is disabled (TPC-Accumulation) is not set (if information indicating that TPC accumulation is disabled is not provided, and TPC accumulation is set to be enabled), the UE accumulates TPC command values ​​and determines the transmit power based on the accumulation result (power control state) (applies the TPC command values ​​via accumulation).

[0102] When information indicating that TPC accumulation is disabled (TPC-Accumulation) is set (when information indicating that TPC accumulation is disabled is provided, when TPC accumulation is set to disabled), the UE does not accumulate TPC command values ​​and determines the transmission power based on the TPC command values ​​(power control state) (applies the TPC command values ​​without using accumulation).

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

[0104] Σ m=0 C(Di)-1 δPUCCH,b,f,c(m,l) is the group / cardinality C(D i ) a set of TPC command values ​​D i It may be the sum of the TPC command values ​​in i is the number of PUSCH transmission opportunities i-i0 on the active UL BWP b of carrier f of serving cell c for the PUSCH power control adjustment state l. PUSCH (i-i0)-1 symbols ago and K of PUSCH transmission opportunity i PUSCH (i) may be the set of TPC command values ​​received between symbols (i) and (ii) for PUSCH transmission opportunity i-i. PUSCH(i-i0) symbols ago is K of PUSCH transmission opportunity i PUSCH (i) It may be the smallest positive integer that is earlier than the symbol before.

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

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

[0107] <SRS Transmission Power Control> Using the index l of the power control adjustment state (closed-loop state), the transmission power (P ＳＲＳ、ｂ，ｆ，ｃ (i, q ｓ , l)) is P ＣＭＡＸ，ｆ，ｃ (i), P Ｏ＿ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ), M ＳＲＳ，ｂ，ｆ，ｃ (i), α ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ), P.L.ｂ，ｆ，ｃ (q ｄ ), h ｂ，ｆ，ｃ Based on (i, l), it is given by the following equation (Equation 2).

[0108] (Formula 2)

[0109] Furthermore, the SRS transmission opportunity i is a 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.

[0110] Here, 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.).

[0111] 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 μ;

[0112] α ＳＲＳ，ｂ，ｆ，ｃ (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 α (e.g., alpha) may be defined as a path loss compensation factor for UL power control.

[0113] 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] (path loss estimate [dB], path loss compensation) calculated by the UE using the RS resource index q ｄ is the SRS resource set q ｓ and a pathloss reference RS (pathloss reference RS, pathloss (PL)-RS, 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).

[0114] If the UE is not provided with pathloss reference RSs (pathlossReferenceRSs) or before the UE is provided with individual upper layer parameters, the UE may use RS resources obtained from the SS / PBCH block used by the UE to acquire the MIB. ｂ，ｆ，ｃ (q ｄ ) is calculated.

[0115] h ｂ，ｆ，ｃ (i, l) is the SRS power control adjustment state for the active UL BWP of carrier f of serving cell c at SRS transmission opportunity i. If the 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, when the setting of the SRS power control adjustment state indicates independent power control adjustment states for SRS transmission and PUSCH transmission, the SRS power control adjustment state h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ It may be based on (m).

[0116] If TPC accumulation is valid, h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ It may be based on the cumulative value of (m).

[0117] If TPC accumulation is invalid, h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ (i) (absolute value) may also be used.

[0118] where δ ＳＲＳ，ｂ，ｆ，ｃ (m) may be a TPC command value that is jointly coded with other TPC commands in a PDCCH having DCI (e.g., DCI format 2_3). m=0 C(Si)-1 δ SRS,b,f,c (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 ＳＲＳ (i-i ０ )-1 symbol before and K ＳＲＳ (i) The cardinality C(S ｉ ) a set S of TPC command values ｉ may be the sum of the TPC commands in ０ is the SRS transmission opportunity i-i ０ K ＳＲＳ (i-i ０ )-1 symbols before is K ＳＲＳ (i) It may be the smallest positive integer that is earlier than the symbol before.

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

[0120] (DCI Format 2_3) DCI Format 2_3 is used to transmit a TPC command group for SRS transmission by one or more UEs. An SRS request may also be transmitted together with the TPC command.

[0121] The following information is transmitted by DCI format 2_3 CRC-scrambled by TPC-SRS-RNTI: Block number 1, Block number 2, ..., Block number B. The starting position of a block is determined by the parameter startingBitOfFormat2-3 or startingBitOfFormat2-3SUL-v1530 provided by higher layers to the UE that configures the block.

[0122] If the UE is configured with the higher layer parameter srs-TPC-PDCCH-Group=typeA for an UL without PUCCH and PUSCH or for an UL where SRS power control is not associated with PUSCH power control, one block is configured for the UE by higher layers, in which the following fields are defined: SRS request: 0 or 2 bits. If present, this field is interpreted according to a specific table. TPC command number 1, TPC command number 2, ..., TPC command number N. Each TPC command applies to a respective UL carrier, as provided by the higher layer parameter cc-IndexInOneCC-Set.

[0123] If the UE is configured with higher layer parameter srs-TPC-PDCCH-Group=typeB for an UL without PUCCH and PUSCH or for an UL where SRS power control is not associated with PUSCH power control, the higher layers configure the UE with one or more blocks, each block applying to an UL carrier, and define the following fields for each block: SRS request: 0 or 2 bits. If present, this field is interpreted according to a specific table. TPC command: 2 bits.

[0124] The number of information bits of format 2_3 must be less than or equal to the payload size of format 1_0 monitored in the common search space in the same serving cell. If the number of information bits of format 2_3 is smaller than the payload size of format 1_0 monitored in the common search space in the same serving cell, zeros must be added to format 2_3 until the payload size is equal to the payload size of format 1_0 monitored in the common search space in the same serving cell.

[0125] (SRS Switching) DCI format 2_3 is applied to uplink carriers of a serving cell for which the UE is not configured for PUSCH / PUCCH transmission, or for which srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and PUSCH transmission. A UE for which the parameter carrierSwitching is configured by higher layers is provided with the following (1) to (7).

[0126] (1) TPC-SRS-RNTI of DCI format 2_3 with parameter tpc-SRS-RNTI.

[0127] (2) The index of the serving cell from which the UE stops transmitting in order to transmit SRS on one or more other serving cells, via the parameter srs-SwitchFromServCellIndex.

[0128] (3) Indication of the uplink carrier from which the UE will suspend transmission in order to transmit SRS on one or more other serving cells, using the parameter srs-SwitchFromCarrier.

[0129] (4) DCI format 2_3 field configuration type according to Type A or Type B. In the case of Type A, the index of the serving cell set is provided by cc-SetIndex, the index of the serving cell in the serving cell set is provided by cc-IndexInOneCC-Set, and the DCI format 2_3 field includes a TPC command for each serving cell from the serving cell set and may also include an SRS request for SRS transmission on the serving cell set. In the case of Type B, the DCI format 2_3 field includes a TPC command for the serving cell index and may also include an SRS request for SRS transmission on the serving cell.

[0130] (5) An indication to the serving cell whether the field in DCI format 2_3 contains an SRS request according to fieldTypeFormat2-3. A value of 0 / 1 of this indication indicates the absence / presence of an SRS request. The mapping between the 2-bit SRS request and the SRS resource set is as specified in the specification.

[0131] (6) startingBitOfFormat2-3: an index for the position in DCI format 2_3 of the first bit of the field for the serving cell's non-supplementary uplink carrier.

[0132] (7) startingBitOfFormat2-3: Index for the position in DCI format 2_3 of the first bit of the field for the supplementary uplink carrier of the serving cell according to SUL-v1530.

[0133] In the existing specifications (up to Rel. 18), startingBitOfFormat2-3 / startingBitOfFormat2-3SUL-v1530 is specified as an integer from 1 to 31.

[0134] (Two Closed Loop Power Control (CL-PC) Adjustment States for PUSCH) The higher layer parameters related to PUSCH power control (PUSCH-PowerControl) include twoPUSCH-PC-AdjustmentStates and the size of sri-PUSCH-PowerControlId. The higher layer parameters related to PUSCH power control using SRI (SRI-PUSCH-PowerCotrol) include sri-PUSCH-PowerControlId and sri-PUSCH-ClosedLoopIndex. When twoPUSCH-PC-AdjustmentStates is configured, the UE may configure sri-PUSCH-ClosedLoopIndex with l = {0, 1}.

[0135] sri-PUSCH-ClosedLoopIndex applies only to PUSCH. The UE determines whether the closedLoopIndex of the scheduled PUSCH is 0 or 1 based on the SRI. However, the closedLoopIndex for the SRS of the indicated CB / NCB follows the setting of srs-PowerControlAdjustmentStates.

[0136] When two SRS resource sets with usage = CB / NCB are configured, each SRS resource set corresponds to l = {0, 1}, i.e., one SRS resource set corresponds to l = 0 and the other SRS resource set corresponds to l = 1.

[0137] (CL-PC Adjustment State for SRS) The CL-PC adjustment state for SRS is specified according to at least one of the following cases 1 to 3. <Case 1> When srs-PowerControlAdjustmentStates = absent or sameAsFci2 (when following the CL-PC adjustment state of PUSCH), the UE may apply the same CL-PC adjustment state as that of PUSCH. <Case 2> When srs-PowerControlAdjustmentStates = separateClosedLoop and tpc-Accumulation is not provided (when an SRS-specific CL-PC adjustment state is configured and TPC accumulation is not configured), the UE may determine / decide / apply the CL-PC adjustment state of SRS by taking into account (based on) the sum of TPC commands for SRS jointly coded by DCI format 2_3. <Case 3> When srs-PowerControlAdjustmentStates = separateClosedLoop and tpc-Accumulation is provided (when an SRS-specific CL-PC adjustment state is set and TPC accumulation is set), a TPC command for an SRS jointly coded by DCI format 2_3 may be applied as the CL-PC adjustment state of the SRS.

[0138] Regardless of the above case, the UE may also apply a specific CL-PC adjustment state (separate from PUSCH) for SRS, where a new index k={0,1} may be introduced to indicate the SRS-specific CL-PC adjustment state separate from PUSCH.

[0139] In the present disclosure, the values ​​of l and k may be set / indicated for each SRS resource set / SRS resource.

[0140] (Asymmetric DL sTRP / UL mTRP Deployment Scenario) In this disclosure, the following may be assumed for the extension of the asymmetric DL sTRP / UL mTRP deployment scenario: - No change to existing cell definitions. - No need for new cell definitions (e.g., UL-only cells). - Unified TCI framework (Rel. 17 / 18). - Utilization of existing QCL / UL spatial relationship definitions. - Targeting FR1 / FR2.

[0141] (Assumed Scenarios) The present disclosure may assume the following scenarios: A UE receives DL signals (including, for example, PL-RS) from one DL TRP. A UE transmits UL signals to multiple UL TRPs.

[0142] Figure 9 is a conceptual diagram showing an example of an asymmetric DL sTRP / UL mTRP configuration scenario. As shown in Figure 9, a UE receives DL signals from one DL TRP. The UE may also transmit UL signals to the DL TRP / multiple UL TRPs (UL TRP #1 / #2). In this case, the UE may dynamically switch which TRP to transmit the UL signals to, for example, according to the indicated TCI status.

[0143] (Unified TCI Framework) In the present disclosure (in asymmetric DL sTRP / UL mTRP deployment scenario), a unified TCI framework for Rel. 17 / 18 may be supported. The following are examples of supported scenarios (intra-cell / inter-cell):

[0144] <Intra-cell scenario> Unified TCI for single TRP (Rel. 17) may be supported for only one UL TRP. Unified TCI for single DCI multi-TRP (Rel. 18) may be supported for multiple UL TRPs. Unified TCI for multi-DCI multi-TRP (Rel. 18) may not be supported.

[0145] <Inter-cell scenarios> - Unified TCI for single TRP (Rel. 17) may be supported in inter-cell scenarios (Inter cell beam management (ICBM) in Rel. 17). - Unified TCI for single DCI multi-TRP (Rel. 18) may not be supported. - Unified TCI for multi-DCI multi-TRP (Rel. 18) may be supported for inter-cell multi-TRP in Rel. 17.

[0146] (DCI Format 2_3) As described above, DCI format 2_3 may be used only for carrier switching of SRS. For example, DCI format 2_3 may be used according to the following conditions:

[0147] <Condition 1> The UE is configured with the higher layer parameter srs-TPC-PDCCH-Group=type A for an UL that does not have a PUCCH or PUSCH, or for an UL in which SRS power control is not associated with PUSCH power control. <Condition 2> The UE is configured with the higher layer parameter srs-TPC-PDCCH-Group=type B for an UL that does not have a PUCCH or PUSCH, or for an UL in which SRS power control is not associated with PUSCH power control.

[0148] Alternatively, <Condition A> Carrier switching in which there is no PUCCH / PUSCH in the carrier. <Condition B> Carrier switching in which a power control adjustment state separate (independent / separate) from that of PUSCH is set for SRS.

[0149] DCI format 2_3 may be used for any purpose, not limited to the case of carrier switching of SRS, for example, it may be applied to the case of SRS transmission having a CL-PC adjustment state different from that of PUSCH.

[0150] (SRS-Specific Closed-Loop Power Control (CL-PC) Adjustment State) <<Aspect 0>> In the Rel. 18 specifications, when srs-PowerControlAdjustmentStates = separateClosedLoop is set, there is only one closed-loop power control (CL-PC) adjustment state for SRS, separate from the PUSCH. The CL-PC adjustment state can be controlled by DCI format 2_3.

[0151] The UE may configure one or more (two) CL-PC adjustment states for SRS, and one or more (two) CL-PC adjustment states may be configured separately from PUSCH.

[0152] The higher layer parameter srs-PowerControlAdjustmentStates indicates whether twoPUSCH-PC-AdjustmentStates (one / two PUSCH power control adjustment states) or another closed-loop power control adjustment state is configured for the SRS. This higher layer parameter may only be applied to the UL where the UE also transmits PUSCH. If this higher layer parameter is absent / released, the UE may apply the value of sameAs-Fci1.

[0153] That is, when the SRS follows the CL-PC adjustment state of the PUSH, if there are two CL-PC adjustment states in the PUSH, the upper layer parameter srs-PowerControlAdjustmentStates may indicate which CL-PC adjustment state the SRS follows.

[0154] For example, if srs-PowerControlAdjustmentStates = absent, the SRS follows the CL-PC adjustment state (Fci1) of one of the PUSCHs, if srs-PowerControlAdjustmentStates = absent, the SRS follows the CL-PC adjustment state (Fci1), if srs-PowerControlAdjustmentStates = sameAsFci2, the SRS follows the CL-PC adjustment state (Fci2) of the other PUSCH, and if srs-PowerControlAdjustmentStates = separateClosedLoop, the SRS follows a dedicated (unique) CL-PC adjustment state.

[0155] <<Aspect 1>> The UE supports multiple (two) CL-PC adjustment states for the SRS, separate from the PUSCH, as a function independent of the SRS carrier switching.

[0156] The UE may be configured with multiple (two) CL-PC adjustment states separate from the PUSCH, regardless of the configuration for the PUSCH and the configuration for SRS carrier switching.

[0157] Fig. 10 is a conceptual diagram showing an example of SRS transmission according to aspect 1. As shown in Fig. 10, the UE can configure, for SRS #1 / #2, multiple (two) CL-PC adjustment states (l = 0, 1) that are the same as those for PUSCH #1 / #2, and multiple (two) CL-PC adjustment states (k = 0, 1) that are different from those for PUSCH #1 / #2.

[0158] Specifically, the UE may transmit SRS#1 for UL TRP#1 by applying the same CL-PC adjustment state (l=0) as for PUSCH#1.

[0159] The UE may transmit SRS#2 for UL TRP#2 by applying the same CL-PC adjustment state (l=1) as for PUSCH#2.

[0160] The UE may also transmit SRS#3 for DL ​​TRP by applying a first CL-PC adjustment state (k=0) different from that for PUSCH (independent from PUSCH). The UE may perform UL (SRS#3) transmission for DL ​​CSI acquisition.

[0161] Furthermore, the UE may transmit SRS#4 for any TRP (any direction) by applying a second CL-PC adjustment state (k=1) different from the PUSCH (independent from the PUSCH). The UE may perform UL (SRS#4) transmission for beam management.

[0162] In transmitting SRS#4, the "any direction" may refer to a predetermined angular range (e.g., a range of 180 degrees or 360 degrees) in which a certain TRP is assumed to exist. The UE may transmit multiple beams for beamforming in the any direction. The SRS for beamforming may be used for SRS-based beam sweeping.

[0163] In this way, the UE may be configured with multiple (two) CL-PC adjustment states (l = 0, 1) for SRS (#1 to #2) that are the same as those for PUSH, and may be configured with a CL-PC adjustment state (k = 0, 1) for SRS (#3 to #4) that is different from that for PUSH.

[0164] A new higher layer parameter may be introduced to enable a separate CL-PC adjustment state for SRS than for PUSCH.

[0165] 11 is a diagram illustrating an example of SRS configuration according to aspect 1. As illustrated in FIG. 11 , SRS resource set #1 (e.g., used for CB) corresponds to SRS resource #1, and the power control adjustment state can be set to, for example, Fci1 (srs-PowerControlAdjustmentStates = absent). SRS resource set #2 (e.g., used for CB) corresponds to SRS resource #2, and the power control adjustment state can be set to, for example, Fci2 (srs-PowerControlAdjustmentStates = sameAsFci2). SRS resource set #3 (e.g., used for AS) corresponds to SRS resource #3, and the power control adjustment state can be set to, for example, the first CL-PC (srs-PowerControlAdjustmentStates = separateClosedLoop). SRS resource set #4 corresponds to SRS resource #4 (e.g., usage is beam management (BM)), and the power control adjustment state can be set to, for example, a second CL-PC (srs-PowerControlAdjustmentStates = separateClosedLoop).

[0166] According to the above-mentioned aspects 0 to 1, the UE can be configured with one or more (two) SRS resource sets having the same CL-PC adjustment state as the PUSH within a certain CC, and one or more (two) SRS resource sets having a CL-PC adjustment state different from the PUSH.

[0167] These configurations may be supported per SRS resource set / resource, and may be supported regardless of whether the corresponding CC / BWP is configured for PUSCH or SRS antenna switching.

[0168] As mentioned above, an SRS-specific CL-PC adjustment state (an additional CL-PC adjustment state) separate from the PUSCH may be introduced (eg, k=0, 1).

[0169] In the new higher layer parameters, srs-TPC-PDCCH-Group = {typeA, typeB} may be supported.

[0170] DCI format 2_3 may be used to indicate a TPC command for the first / second CL-PC adjustment state separate from the PUSCH. For example, at least one of the following options 1 and 2 may be applied. That is, the UE may apply at least one of the following options 1 and 2 to determine the first / second CL-PC adjustment state separate from the PUSCH for SRS.

[0171] (Option 1) One group-common DCI (e.g., DCI format 2_3) may indicate two TPC commands associated with a first / second CL-PC adjustment state different from that of the PUSCH in a CC / BWP. Here, a second TPC command (new / additional TPC command) different from the first TPC command may be introduced to indicate the second CL-PC adjustment state. The second TPC command may be, for example, composed of two bits.

[0172] 12A and 12B are diagrams showing examples of TPC command (DCI) fields. Fig. 12A corresponds to the case where srs-TPC-PDCCH-Group = type A, and Fig. 12B corresponds to the case where srs-TPC-PDCCH-Group = type B. Note that the order of the fields in the TPC command of the present disclosure is merely an example and can be changed as appropriate. The same applies to the TPC commands in the other figures below.

[0173] As shown in FIG. 12A , the group-common DCI may include an indication of a TPC command for multiple CCs after (following) the SRS request field. In other words, the group-common DCI may include a TPC command for each CC. The TPC command field may be configured in ascending (or descending) order of cells (CCs), and in the case of the same cell, may be configured in ascending (or descending) order of CL-PC adjustment states (e.g., TPC command 1 for {1st CL-PC, CC #1}, TPC command 2 for {2nd CL-PC, CC #1}, ..., TPC command 1 for {1st CL-PC, CC #X}, TPC command 2 for {2nd CL-PC, CC #1}).

[0174] As shown in Figure 12B, the TPC command field for a CC (cell) may be configured with one field (as is) to indicate a TPC command for any TRP. In this case, an X bit may be added to indicate which TRP the TPC command is associated with (CL-PC adjustment state other than PUSCH). For example, if the number of CL-PC adjustment states other than PUSCH is two, X may be 1.

[0175] As shown in Figure 12B, the group-common DCI may include an indication of a TPC command for one CC after (following) the SRS request field. The setting order of the TPC command field may be set in ascending (or descending) order of the CL-PC adjustment state (e.g., TPC command 1 for {1st CL-PC}, TPC command 2 for {2nd CL-PC}).

[0176] (Option 2) One group-common DCI (e.g., DCI format 2_3) may indicate one TPC command associated with the first / second CL-PC adjustment state other than the PUSCH in a certain CC / BWP. The indication method can be further categorized into Alt2-1 to Alt2-2 below. That is, DCI format 2_3 may explicitly / implicitly indicate whether either the first / second CL-PC adjustment state other than the PUSCH is associated with the TPC command.

[0177] (Alt2-1) A new bit field may be added to indicate whether the first or second CL-PC adjustment state, separate from the PUSCH, is associated with the TPC command. The new bit field may consist of, for example, one bit.

[0178] (Alt2-2) An existing bit field (eg, SRS request field) may be used to implicitly indicate that either the first or second CL-PC adjustment state separate from PUSCH is associated with the TPC command.

[0179] According to this aspect, the UE can control SRS transmission by applying the same CL-PC adjustment state as that of the PUSCH, or an SRS-specific CL-PC adjustment state separate from the PUSCH, regardless of the SRS carrier switching setting.

[0180] <<Aspect 2>> Since the UE supports two CL-PC adjustment states for SRS, at least one of the following options 1 to 4 may be applied.

[0181] Option 1: The CL-PC adjustment state for SRS is associated with the SRS resource set. Option 2: If the higher layer parameter srs-PowerControlAdjustmentStates is set to separateClosedLoop, the TCI state closedLoopIndex-r17 indicates one CL-PC adjustment state for SRS. Option 3: In the TCI state P0AlphaSet-r17, add a parameter indicating one of two CL-PC adjustment states for SRS. Option 4: The CL-PC adjustment state for SRS is associated with the usage [type of] the SRS resource.

[0182] <<Aspect 3>> (Two [SRS-specific] CL-PC Adjustment States Separate from PUSCH) The UE may support a function for two [SRS-specific] CL-PC adjustment states separate from PUSCH as a function independent of SRS carrier switching. This function may be applied regardless of the configuration of PUSCH / SRS carrier switching within a CC.

[0183] (Extension of DCI format 2_3) Both srs-TPC-PDCCH-Group = type A and type B may be supported, provided that the existing SRS carrier switching function cannot be configured simultaneously within the same CC (simultaneous configuration is not supported).

[0184] (Introduction of Additional TPC Command) For each CC with two CL-PC adjustment states for SRS, one additional TPC command may be introduced.

[0185] For example, in the case of Type B, one DCI can indicate two TPC commands at the same time, which requires only one additional bit compared to the one-bit closed-loop-indicator field.

[0186] On the other hand, in the case of Type A, N additional bits are required compared to the 1-bit closed-loop-indicator field corresponding to N CCs.

[0187] Two (first / second) CL-PC adjustment states for SRS may be associated with an SRS resource set.

[0188] In the case where two CL-PC adjustment states are applied, it is assumed that one is for SRS carrier switching and the other is for SRS beam management. Considering this, there is no need to dynamically switch the association. In other words, there is no need to indicate two (first / second) CL-PC adjustment states for SRS in the TCI state.

[0189] Therefore, a new upper layer parameter (separateClosedLoopSecond_r19) may be introduced for each SRS resource set.

[0190] (Analysis) As mentioned above, in order to expand UL coverage, the installation of UL receiving points in addition to general transmitting and receiving points is being considered. Also, DL transmitting points (TRPs), macro base stations (BSs) and UL receiving points (TRPs), UL high-density deployment using micro BSs, Heterogeneous Networks (HetNets), etc. are being considered.

[0191] Incidentally, in future wireless communication systems (for example, Rel. 19 and later), it is being considered to make the size of DCI format 2_3 consistent with the size of existing DCI formats (for example, DCI format 1_0).

[0192] Specifically, one method under consideration is to extend the RRC parameter indicating the starting position of a block within a DCI format (e.g., startingBitOfFormat2-3 / startingBitOfFormat2-3SUL) from the existing range of values ​​(e.g., integers from 1 to 31) to an integer from 1 to 32 or more (e.g., 45).

[0193] However, specific methods for extending such RRC parameters have not been sufficiently studied.

[0194] Furthermore, since there are limited cases where it is necessary to extend the value notified by the RRC parameter to 45, it is considered unnecessary to define a new parameter that can always notify a maximum of 45.

[0195] For example, the size of DCI format 2_3 (and DCI format 1_0) in the case of FR1 / FR2-2 is 46 bits, and in the other cases (FR2-1) it is 44 bits, so there is no need to use parameters that can notify a maximum of 45 in cases other than FR1 / FR2-2.

[0196] In addition, in the case of FR1 / FR2-2, when each block corresponding to each UE in DCI format 2_3 is 2 bits (in other words, when there is one TPC command notified to each UE and there is no SRS request field) (see Figure 13A), a parameter that can notify up to 45 is required, but in other cases there is no need to use a parameter that can notify up to 45.

[0197] In cases where it is not necessary to use a parameter that can report a maximum of 45, the value reported by the RRC parameter can be less than 45.

[0198] For example, the maximum value signaled by the RRC parameter may be 43 in FR2-1.

[0199] Also, for example, even in the case of FR1 / FR2-2, if each block corresponding to a certain UE in DCI format 2_3 is more than 2 bits (e.g., 4 bits) (see Figure 13B, see the starting position for UE #X in Figure 13B), the maximum value notified by the RRC parameter can be smaller than 45 (e.g., 43) in FR2-1.

[0200] In this way, if the value notified by the RRC parameter can be made smaller than 45, it is possible to achieve a reduction in signaling overhead, but the details of how to achieve this have not been sufficiently considered.

[0201] Furthermore, the UE may be configured / instructed to have two CL-PC adjustment states for the SRS, which may be configured / instructed separately from the PUSCH.

[0202] A certain CL-PC adjustment state is indicated / enabled, for example, by a TPC command included in the DCI. For example, in addition to DCI format 2_3, the use of DCI formats for PUSCH scheduling (for example, DCI formats 0_1 / 0_2) is being considered.

[0203] However, there has been insufficient consideration of the method of indicating the two CL-PC adjustment states using DCI formats 0_1 / 0_2. If these considerations are insufficient, the UE may not be able to appropriately control communications using DL TRP and UL TRP, which may result in a decrease in throughput.

[0204] Therefore, the present inventors came up with a method for solving these problems.

[0205] Hereinafter, embodiments according to 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.

[0206] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

[0208] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0209] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0210] 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, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0211] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. 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.

[0212] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0213] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.

[0214] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0215] In the present disclosure, the terms single TRP, channel / signal 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.

[0216] In the present disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI states / spatial relationships, multi-TRP enabled by RRC / DCI, multiple TCI states / spatial relationships 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 read interchangeably.

[0217] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read interchangeably.

[0218] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, and setting two CORESET pool indices or CORESET pool index = 1 (or a value greater than or equal to 1) may be read interchangeably.

[0219] In the present disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within a CC, and band may be interchangeable. In the present disclosure, the terms cell, PCI, cell with an additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, target cell, neighbor cell, and inter-RAT neighbor cell may be interchangeable. The target cell may be a cell selected from multiple candidate cells. In the present disclosure, the terms switch, change, and update may be interchangeable. The term serving cell may be interchangeable with the serving cell before the switch or the serving cell after the switch.

[0220] The UL reception point may be connected to a TRP (e.g., a base station) or a core network via wired or wireless. The UL reception point may be treated as a network (NW) or a base station. The UL reception point may be capable of transmitting downlink (DL) signals (e.g., PL values) and may be applied to base stations forming a macrocell. For example, the UL reception point may not transmit downlink data but may transmit control signals / channels.

[0221] In the present disclosure, the terms base station, TRP, UL receiving point, UL TRP, UL only TRP, micro cell, micro BS, and micro TRP may be interchangeable. An UL receiving point primarily performs UL reception. An UL receiving point may perform only UL reception, or may perform UL reception and DL transmission.

[0222] In the present disclosure, the terms base station, TRP, DL transmission point, DL TRP, DL only TRP, UL / DL TRP, macro cell, macro BS, macro TRP, and central TRP may be interchangeable. A DL transmission point primarily performs DL transmission. A DL transmission point may perform only DL transmission, or may perform UL reception and DL transmission.

[0223] In the present disclosure, UL high density deployment, distributed TRP mode, separated location mode of transmitting / receiving points, distributed transmitting / receiving mode, separated TRP mode, TRP type 1, TRP type 2, TRP type A, and TRP type B may be read interchangeably.

[0224] The present disclosure may assume at least one of single TRP, multi-TRP with multi-DCI, multi-TRP with single DCI, scenario 1 or scenario 2 above.

[0225] In the present disclosure, being set and receiving a setting (setting information) may be read interchangeably.

[0226] In the present disclosure, TCI, TCI state, TCI state ID, TCI state list / set / pool / group, and TCI state list / set / pool / group ID may be read interchangeably.

[0227] In the present disclosure, a set of TCI states (separate TCI states) may refer to a set of UL TCI states and DL TCI states. The TCI state may refer to a TCI-State information element, which is an RRC information element.

[0228] In the present disclosure, the terms "indicated TCI state," "unified TCI state," "unified TCI state in which multi-TRP is not configured / used / applied," "unified TCI state defined in Rel. 17," "Rel. 17 unified TCI state," and "first unified TCI state" may be interchangeable.

[0229] In the present disclosure, the terms "indication TCI state," "unified TCI state," "unified TCI state in which multi-TRP is configured / used / applied," "unified TCI state in which multi-TRP can be configured / used / applied," "indication TCI state in which multi-TRP is configured / used / applied," "indication TCI state in which multi-TRP can be configured / used / applied," "unified TCI state specified in Rel. 18," "Rel. 18 unified TCI state," "unified TCI state for multi-TRP," and "second unified TCI state" may be interpreted interchangeably.

[0230] In the present disclosure, the terms "DCI-indicated TCI state," "indicated TCI state," "indicated TCI state," "unified TCI state," "TCI state applied to multiple types of channels / signals," "joint TCI state (for DL ​​and UL)," "DL TCI state," "UL TCI state," "Rel. 17 TCI state," "common TCI state," "single unified TCI state configured," and "single unified TCI state activated" may be read interchangeably.

[0231] In the present disclosure, the terms TCI state set by RRC parameters, configured TCI state, set TCI state, TCI state that does not conform to the unified TCI state, TCI state other than the unified TCI state, TCI state / spatial relationship set for a specific channel / signal, and individual TCI state may be read interchangeably.

[0232] Unified / common TCI state may refer to the indicated TCI state indicated using DCI / MAC CE / RRC (in Rel. 17).

[0233] The indicated TCI state may be shared with at least one of the UE-specific reception of PDSCH / PDCCH (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI / MAC CE / RRC may be referred to as the indicated TCI state.

[0234] If the indicated TCI state is supported (in Rel. 17), a TCI state other than the unified TCI state may refer to the TCI state configured using MAC CE / RRC (in Rel. 17) (configured TCI state).

[0235] The configured TCI state may not be shared with at least one of the UE-specific reception of PDSCH / PDCCH (updated using DCI / MAC CE / RRC in Rel. 17), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The configured TCI state may be configured by RRC / MAC CE per CORESET / per resource / per resource set, and may not be updated even if the indicated TCI state is updated.

[0236] In the present disclosure, a first TRP may correspond to a first TCI state. In the present disclosure, a second TRP may correspond to a second TCI state. In the present disclosure, an n-th TRP may correspond to an n-th TCI state.

[0237] In the present disclosure, a first CORESET pool index value (e.g., 0), a first TRP index value (e.g., 1), and a first TCI state (first DL / UL (joint / separate) TCI state) may correspond to each other. In the present disclosure, a second CORESET pool index value (e.g., 1), a second TRP index value (e.g., 2), and a second TCI state (second DL / UL (joint / separate) TCI state) may correspond to each other.

[0238] In the present disclosure, TA, TAG, and TA offset value may be interchangeable. DL reference timing and DL reception timing may be interchangeable. Two TAs / TAGs may be interchangeable with more than two TAs / TAGs.

[0239] In the present disclosure, the terms absolute PL, path loss (PL), PL value, and PL parameter may be interchangeable. Ｏ The offset of α, the offset of power / power density [x dBm], the path loss (PL), the PL value, and the PL parameter may be interchangeable. In the present disclosure, the PL, the PL value, the PL RS, and the PL RSID may be interchangeable.

[0240] In the present disclosure, using a relative PL (PL offset) value may mean using a PL value obtained by applying (adding or subtracting) a received (set) relative PL (PL offset) value to a PL value estimated based on a DL RS transmitted from a macro TRP to calculate the transmission power of an UL signal to be transmitted to a UL reception point.

[0241] In the present disclosure, the SRS may be at least one of aperiodic (A)-SRS, periodic (P)-SRS, and semi-persistent (SP)-SRS.

[0242] In the present disclosure, the path loss reference RS, the path loss reference RS for PUSCH, the path loss reference RS for PUCCH, the path loss reference RS for SRS, SSB, CSI-RS, and RS may be interchangeable. In the present disclosure, the path loss (PL), the path loss value, and the path loss parameter may be interchangeable.

[0243] In the present disclosure, the terms base station, UL receiving point, UL TRP, UL only TRP, and micro BS may be interchangeable. An UL receiving point may perform only UL reception, or may perform DL transmission if conditions are met.

[0244] In the present disclosure, the terms base station, DL transmission point, DL TRP, DL only TRP, macro BS, and central TRP may be interchangeable. A DL transmission point may only perform DL transmission, or may perform UL reception if certain conditions are met.

[0245] In the present disclosure, TA, TAG, and TA offset value may be interchangeable. DL reference timing and DL reception timing may be interchangeable. Two TAs / TAGs may be interchangeable with more than two TAs / TAGs.

[0246] In the present disclosure, coresetPoolIndex, CORESET pool index, and RRC parameters indicating the CORESET pool index may be interchanged. n-TimingAdvanceOffset and TA offset may be interchanged. TCI-UL-State, UL TCI state, and RRC parameters indicating the UL TCI state may be interchanged. dl-OrJointTCI-StateList, a list of DL or joint TCI states, and RRC parameters indicating a list of DL or joint TCI states may be interchanged. ul-TCI-StateList, a list of UL TCI states, and RRC parameters indicating a list of UL TCI states may be interchanged. n-TimingAdvanceOffset and n-TimingAdvanceOffset2 may be interchanged with a TA offset and an RRC parameter indicating a TA offset.

[0247] DL sTRP / UL mTRP may refer to, for example, the scenario applied in Rel. 19. DL sTRP / UL mTRP may refer to, for example, Scenario 1 ( FIG. 1B ) or Scenario 2 ( FIG. 2 ). Asymmetric DL sTRP / UL mTRP, DL sTRP / UL mTRP, and [asymmetric] HetNet may be interchangeable.

[0248] In the present disclosure, the terms resource set and resource may be read interchangeably.

[0249] In the present disclosure, SRS#X, SRS resource set#X, and SRS resource#X may be read as interchangeable.

[0250] In the present disclosure, CC and BWP may be read interchangeably.

[0251] In the present disclosure, a CL-PC adjustment state separate from the PUSCH, a CL-PC adjustment state specific to (dedicated to) the SRS, and a CL-PC adjustment state for the SRS for Rel. 19 may be read as interchangeable.

[0252] In the present disclosure, there may be one or more serving cells.

[0253] (Wireless communication method) A UE may apply the present disclosure to control UL transmission (SRS power control). A NW / BS / gNB may provide / transmit to the UE settings / instructions, etc., for the UE to realize the control. In addition, the NW / BS / gNB may perform various controls to receive UL transmission from a terminal to which each embodiment is applied.

[0254] In the present disclosure, the configuration / instruction for SRS may be transmitted per resource / resource set.

[0255] In the present disclosure, the configuration / instruction for the SRS may be transmitted per CC / BWP.

[0256] The present disclosure may apply only to a particular CC / BWP or only to a particular frequency band (e.g., FR2).

[0257] In this disclosure, the terms CL-PC indicator, CL-PC index, indicator / index for CL-PC [regulation state], closed-loop indicator, etc. may be read interchangeably.

[0258] In the present disclosure, DCI formats 2_3 / 1_1 / 1_2 may be interchangeably read as any DCI format (e.g., DCI format X_Y).

[0259] In the present disclosure, "one or two joint / DL / UL TCI states" may be written as "{1, 2} joint / DL / UL TCI (states)." In the present disclosure, "zero, one or two joint / DL / UL TCI states" may be written as "{0, 1, 2} joint / DL / UL TCI (states)." In the present disclosure, "two" and "multiple" may be read interchangeably.

[0260] In the present disclosure, the new upper layer parameters are not limited to the names shown below, and may have other names.

[0261] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0262] <Tenth Embodiment> The tenth embodiment relates to an RRC parameter that indicates the starting position of a block in a specific DCI format.

[0263] The specific DCI format may be, for example, a DCI format for instructing a TPC command for SRS transmission (for example, DCI format 2_3). The DCI format may be, for example, a DCI format common to a group (multiple UEs).

[0264] The UE may receive an RRC parameter indicating the starting position of the block of the DCI format (e.g., the index of the first bit position (for the UE) in the [supplementary / non-supplementary] UL carrier field of the serving cell).

[0265] The UE may assume that it receives either [only] the first RRC parameter or the second RRC parameter for that RRC parameter.

[0266] The UE may receive either the first RRC parameter or the second RRC parameter, and may control transmission of the SRS (may determine the transmission power of the SRS) based on the received RRC parameter.

[0267] <<Embodiment 0-1>> The first RRC parameter may be, for example, an existing RRC parameter (defined up to Rel. 18) (for example, startingBitOfFormat2-3 / startingBitOfFormat2-3SUL).

[0268] In this disclosure, parameters marked with "SUL" may refer to parameters for supplementary UL (SUL).

[0269] The first RRC parameter may be defined by an integer from 1 to 31. The first RRC parameter may indicate an integer from 1 to 31. The first RRC parameter may be indicated by 5 bits.

[0270] The second RRC parameter may be, for example, a new RRC parameter (specified in Rel. 19 or later) (e.g., startingBitOfFormat2-3-r19 / startingBitOfFormat2-3SUL-r19).

[0271] The second RRC parameter may be defined by an integer from 1 to X. The first RRC parameter may indicate an integer from 1 to X.

[0272] For example, X may be an integer greater than 31 (eg, 45).

[0273] Note that X is not limited to 45. For example, X may be determined in accordance with a number related to the maximum size of the second RRC parameter described in the first embodiment below.

[0274] According to this X, the payload size of a specific DCI format can be made consistent with that of other DCI formats (for example, DCI format 1_0).

[0275] If X=45, the second RRC parameter may be defined in 6 bits.

[0276] Fig. 14 is a diagram illustrating an example of RRC parameters according to embodiment 0-1. In the example illustrated in Fig. 14, a first RRC parameter (startingBitOfFormat2-3 / startingBitOfFormat2-3SUL) and a second RRC parameter (startingBitOfFormat2-3-r19 / startingBitOfFormat2-3SUL-r19) are defined in a TPC command configuration for SRS (SRS-TPC-CommandConfig).

[0277] In the example shown in FIG. 14, the second RRC parameter is represented by an integer between 1 and 45.

[0278] In embodiment 0-1, if 32 or less is notified about the start position of a block in a specific DCI format, the first RRC parameter or the second RRC parameter may be used. Otherwise, the second RRC parameter may be used.

[0279] <<Embodiment 0-2>> The first RRC parameter may be, for example, an existing RRC parameter (defined up to Rel. 18) (for example, startingBitOfFormat2-3 / startingBitOfFormat2-3SUL).

[0280] The first RRC parameter may be defined by an integer from 1 to 31. The first RRC parameter may indicate an integer from 1 to 31. The first RRC parameter may be indicated by 5 bits.

[0281] The second RRC parameter may be, for example, a new RRC parameter (specified in Rel. 19 or later) (e.g., startingBitOfFormat2-3-r19 / startingBitOfFormat2-3SUL-r19).

[0282] The second RRC parameter may be defined by an integer from Y to Z. The first RRC parameter may indicate an integer from Y to Z.

[0283] For example, Y may be an integer greater than 31 (for example, 32). For example, Z may be an integer greater than 32 (for example, 45).

[0284] Note that Z is not limited to 45. For example, Z may be determined in accordance with a number related to the maximum size of the second RRC parameter described in the first embodiment below.

[0285] According to Y and Z, the payload size of a specific DCI format can be matched with that of other DCI formats (for example, DCI format 1_0).

[0286] For example, when Y=32 and Z=45, the second RRC parameter can be defined using 4 bits, which can reduce the signaling overhead more than in the above embodiment 0-1.

[0287] In addition, the information bits {0000, 0001, 0010, . . .} indicated by the 4-bit second RRC parameter may correspond to {32, 33, 34, . . .}, respectively.

[0288] Fig. 15 is a diagram illustrating an example of RRC parameters according to embodiment 0 to 2. In the example illustrated in Fig. 15, a first RRC parameter (startingBitOfFormat2-3 / startingBitOfFormat2-3SUL) and a second RRC parameter (startingBitOfFormat2-3-r19 / startingBitOfFormat2-3SUL-r19) are defined in a TPC command configuration for SRS (SRS-TPC-CommandConfig).

[0289] In the example shown in FIG. 15, the second RRC parameter indicates any integer from 32 to 45.

[0290] In embodiment 0-2, if 32 or less start positions of blocks in a specific DCI format are notified, the first RRC parameter may be used. Otherwise, the second RRC parameter may be used.

[0291] <<Embodiment 0-3>> (For example, in an asymmetric HetNet scenario) Both the first RRC parameter for non-supplementary UL (for example, startingBitOfFormat2-3) and the first RRC parameter for SUL (for example, startingBitOfFormat2-3SUL) may be updated [simultaneously].

[0292] (e.g., in an asymmetric HetNet scenario) either the first RRC parameter for non-supplementary UL (SUL) (e.g., startingBitOfFormat2-3) or the first RRC parameter for SUL (e.g., startingBitOfFormat2-3SUL) may be updated. For example, only the first RRC parameter for non-supplementary UL (SUL) (e.g., startingBitOfFormat2-3) may be updated, since SUL may not be utilized in the asymmetric HetNet scenario.

[0293] (e.g., in an asymmetric HetNet scenario) both the second RRC parameter for the non-supplementary UL (SUL) (e.g., startingBitOfFormat2-3-r19) and the second RRC parameter for the SUL (e.g., startingBitOfFormat2-3SUL-r19) may be updated [simultaneously].

[0294] (e.g., in an asymmetric HetNet scenario) either the second RRC parameter for the non-supplementary UL (SUL) (e.g., startingBitOfFormat2-3-r19) or the second RRC parameter for the SUL (e.g., startingBitOfFormat2-3SUL-r19) may be updated. For example, only the second RRC parameter for the non-supplementary UL (SUL) (e.g., startingBitOfFormat2-3-r19) may be updated. This is because the SUL may not be utilized in the asymmetric HetNet scenario.

[0295] The second RRC parameter may be set [only] when multiple (e.g., two) CL-PC adjustment states for SRS separate from the PUSH are set.

[0296] For example, if multiple (e.g., two) CL-PC adjustment states for SRS separate from PUSH are configured, the UE may receive either the first RRC parameters or the second RRC parameters.

[0297] In this case, the second RRC parameter (setting) may mean that it corresponds to optional / separate UE capability for multiple (two) CL-PC adjustment states for SRS apart from PUSCH.

[0298] For example, if multiple (e.g., two) CL-PC adjustment states for SRS separate from PUSCH are configured, the UE may assume that it receives [only] the second RRC parameter.

[0299] In this case, the (configuration of) the second RRC parameter may mean that it corresponds to the basic UE capability for multiple (two) CL-PC adjustment states for SRS apart from PUSCH.

[0300] The second RRC parameter may be set regardless of whether multiple (e.g., two) CL-PC adjustment states for SRS other than PUSH are set.

[0301] For example, regardless of whether multiple (e.g., two) CL-PC adjustment states for SRS separate from PUSH are configured, the UE may receive either the first RRC parameter or the second RRC parameter.

[0302] In this case, the (configuration of) the second RRC parameter may mean that it corresponds to the UE capability independent of multiple (two) CL-PC adjustment states for SRS separate from PUSCH.

[0303] According to the 0th embodiment, the RRC parameters can be appropriately extended.

[0304] First Embodiment The first embodiment relates to the maximum value indicated by the above-described second RRC parameter.

[0305] The maximum value indicated by the second RRC parameter may be a fixed value or a variable value.

[0306] <<Embodiment 1-0>> The maximum value indicated by the second RRC parameter (eg, startingBitOfFormat2-3-r19 / startingBitOfFormat2-3SUL-r19) may be determined by RRC signaling.

[0307] In the present disclosure, the maximum value of the value indicated by the second RRC parameter and the maximum bit size of the second RRC parameter may be interpreted as interchangeable. For example, in the present embodiment, the maximum bit size of the second RRC parameter may be determined by RRC signaling.

[0308] The maximum value indicated by the second RRC parameter may be at least equal to or greater than the first value (e.g., 32). For example, if the maximum value is equal to or less than 31, there is no need to define / use the second RRC parameter, and the existing RRC parameter (first RRC parameter) can be used.

[0309] The maximum value indicated by the second RRC parameter may be at least equal to or less than the second value (e.g., 45). This is because, considering the size of DCI format 2_3, the maximum value does not need to be 46 or more.

[0310] According to embodiment 1-0, the maximum value is determined by RRC signaling, thereby enabling simple control.

[0311] <<Embodiment 1-1>> The maximum value indicated by the second RRC parameter may be determined based on at least one of the following conditions: A frequency range (used by the UE) (e.g., FR1 / 2-2 or FR2-1) A setting of a specific field (e.g., SRS request field / TPC command field) in a specific DCI format (e.g., DCI format 2_3).

[0312] For example, the specification may determine a maximum value (or a set of maximum values) of the value indicated by the second RRC parameter based on at least one of a frequency range condition and a condition of a specific field in a specific DCI format.

[0313] According to the embodiment 1-1, the maximum value can be determined depending on the conditions, and flexible control can be realized.

[0314] <<Embodiment 1-2>> The maximum value indicated by the second RRC parameter may be set using RRC signaling.

[0315] For example, the maximum value of the value indicated by the second RRC parameter may be set for each SRS TPC command configuration (e.g., RRC parameter SRS-TPC-CommandConfig) / PDCCH configuration (e.g., RRC parameter PDCCH-Config) / CORESET / BWP / CC / UW.

[0316] For example, since the size of DCI format 1_0 is determined by the number of physical resource blocks (PRBs) of the DL BWP, the size of DCI format 2_3 can also be changed for each BWP / CC. Therefore, it is preferable that the maximum value be set for each BWP / CC.

[0317] 16 is a diagram illustrating an example of setting the maximum value indicated by the second RRC parameter according to embodiment 1-2. In the example illustrated in FIG. 16, the second RRC parameter (startingBitOfFormat2-3-r19 / startingBitOfFormat2-3SUL-r19) is included in the TPC command configuration for SRS (SRS-TPC-CommandConfig). In addition, a parameter (maxNrofstartingBitOfFormat2-3-r19) indicating the maximum value indicated by the second RRC parameter is configured for the UE.

[0318] 16, the second RRC parameter is represented by an integer from 1 to maxNrofstartingBitOfFormat2-3-r19 (as in the above embodiment 0-1). Also, maxNrofstartingBitOfFormat2-3-r19 is represented by an integer from 32 to 45 (in INTEGER type).

[0319] 17 is a diagram illustrating another example of setting the maximum value indicated by the second RRC parameter according to embodiment 1-2. Differences from FIG. 16 above will be described below.

[0320] 17, the second RRC parameter is represented by any integer from 32 to maxNrofstartingBitOfFormat2-3-r19 (as in the above-described embodiment 0-2). Also, maxNrofstartingBitOfFormat2-3-r19 is represented by any integer from 32 to 45 (in INTEGER type).

[0321] In the examples shown in Figures 16 and 17, if the second RRC parameter is not specified / extended for SUL, the parameter indicating the maximum value of the value indicated by the second RRC parameter for SUL does not need to be used.

[0322] In the examples shown in Figures 16 and 17, the parameter (maxNrofstartingBitOfFormat2-3-r19) indicating the maximum value of the value indicated by the second RRC parameter may be indicated by an enumeration type (ENUMERATED type).

[0323] Furthermore, the examples shown in Figures 16 and 17 show a case where the size of DCI format 2_3 is 46 (i.e., in the case of FR1 / FR2-2), but this embodiment can also be applied to other cases.

[0324] According to embodiment 1-2, the maximum value is set using RRC signaling, thereby realizing simple and flexible control.

[0325] According to the first embodiment described above, the maximum value indicated by the second RRC parameter can be appropriately defined / set, and signaling overhead can be reduced.

[0326] Second Embodiment The second embodiment relates to a method for indicating the CL-PC adjustment state for SRS using a DCI format for scheduling a PUSCH (for example, DCI format 0_1 / 0_2).

[0327] In the present disclosure, the two CL-PC adjustment states [for SRS], the two CL-PC adjustment states separate from PUSCH, and the two CL-PC adjustment states specific to SRS may be read as interchangeable.

[0328] In the present disclosure, the CL-PC ID field, CL-PC indicator, and closed-loop indicator field may be read interchangeably.

[0329] <<Embodiment 2-1>> Embodiment 2-1 relates to a case where DCI format 0_1 / 0_2 indicates TPC commands for two CL-PC adjustment states.

[0330] That is, the UE may determine two CL-PC adjustment states for SRS based on DCI format 0_1 / 0_2.

[0331] When two CL-PC adjustment states are configured for a UE, a 2-bit second TPC command field and a 1-bit CL-PC ID field may be added / introduced in DCI format 0_1 / 0_2.

[0332] The second TPC command field may be used to indicate the TPC command, and the CL-PC ID field may be used to indicate which of the two CL-PC adjustment states the second TPC command is associated with.

[0333] A 2-bit second TPC command field and a 1-bit CL-PC ID field may be present in one CC in which two CL-PC adjustment states for SRS are set.

[0334] In this aspect, the existing TPC command (for PUSCH) may be indicated by utilizing the existing TPC command in DCI format 0_1 / 0_2.

[0335] For example, two CL-PC adjustment states may not be configured for the UE, in which case the TPC command may be used for legacy purposes (PUSCH).

[0336] For example, two CL-PC adjustment states may not be configured for the UE, in which case the existing TPC command (which may be referred to as the first TPC command) may be used for the existing purpose (PUSCH).

[0337] As mentioned above, the CL-PC ID field may be utilized to indicate which of the two CL-PC adjustment states the second TPC command is associated with.

[0338] <<Embodiment 2-2>> Similar to embodiment 2-1, embodiment 2-2 also relates to the case where DCI formats 0_1 / 0_2 indicate TPC commands for two CL-PC adjustment states.

[0339] The UE may determine two CL-PC adjustment states for SRS based on DCI format 0_1 / 0_2.

[0340] If two CL-PC adjustment states are configured for a UE, a 2-bit first TPC command field and a 2-bit second TPC command field may be added / introduced in DCI format 0_1 / 0_2.

[0341] The first / second TPC command field may be used to indicate TPC commands corresponding to two CL-PC adjustment states.

[0342] A 2-bit second TPC command field and a 1-bit CL-PC ID field may be present in one CC in which two CL-PC adjustment states for SRS are set.

[0343] In this embodiment, an existing TPC command (for PUSCH) may be indicated by utilizing an existing TPC command in DCI format 0_1 / 0_2.

[0344] In addition, by utilizing a new TPC command (first TPC command) in DCI format 0_1 / 0_2, a TPC command for the first CL-PC adjustment state of the two CL-PC adjustment states for SRS may be indicated.

[0345] In addition, by utilizing another new TPC command (second TPC command) in DCI format 0_1 / 0_2, a TPC command for the second CL-PC adjustment state of the two CL-PC adjustment states for SRS may be indicated.

[0346] For example, two CL-PC adjustment states may not be configured for the UE, in which case the TPC command may be used for legacy purposes (PUSCH).

[0347] For example, two CL-PC adjustment states may not be configured for the UE. In this case, a new TPC command (first TPC command) may correspond to the first CL-PC adjustment state of the two CL-PC adjustment states. Furthermore, another new TPC command (second TPC command) may correspond to the second CL-PC adjustment state of the two CL-PC adjustment states.

[0348] According to this embodiment, it is possible to clearly indicate two CL-PC adjustment states specific to the SRS using DCI formats 0_1 / 0_2.

[0349] <<Modification of the Second Embodiment>> The TPC command field in DCI format 0_1 / 0_2 (the existing TPC command field for PUSCH) may be used to indicate the TPC command for SRS, where the TCI state {i0, i1} may be used instead of the CL-PC ID field to indicate which of the two CL-PC adjustment states the TPC command is associated with.

[0350] For example, if the top-level parameter srs-PowerControlAdjustmentStates is set to "separateClosedLoop", the closedLoopIndex-r17 of the SRS in the TCI state may indicate one of the CL-PC adjustment states for the SRS.

[0351] Here, the candidate values ​​of i0 and i1 of the SRS closedLoopIndex-r17 may indicate the first / second CL-PC adjustment state different from the PUSCH, respectively. That is, the CL-PC IDs of the two CL-PC adjustment states may be associated with the TCI state {i0, i1}.

[0352] DCI formats 0_1 / 0_2 schedule PUSCH (i.e., UL data). Therefore, the TCI state of the PUSCH scheduled by DCI formats 0_1 / 0_2 may be associated with two CL-PC adjustment states, which allows further reduction of new fields.

[0353] That is, the TCI state {i0, i1} of the PUSH scheduled by DCI format 0_1 / 0_2 may be used to indicate the CL-PC adjustment state for the two SRSs associated with the TPC command in that DCI format 0_1 / 0_2.

[0354] In embodiment 2-1, the CL-PC ID may not be necessary. Therefore, the TCI state {i0, i1} of the PUSCH scheduled by the DCI format 0_1 / 0_2 may be used to indicate one of the CL-PC adjustment states for the two SRSs associated with the TPC command in the DCI format 0_1 / 0_2.

[0355] Furthermore, the TCI state {i0, i1} used to indicate one of the two SRS CL-PC adjustment states associated with a TPC command in DCI format 0_1 / 0_2 may be indicated by at least one of the TCI state field, the TCI selection field, the SRI field, and the SRS resource set indicator field. At least one of the TCI state field, the TCI selection field, the SRI field, and the SRS resource set indicator field may be included in the DCI format.

[0356] Furthermore, the 2-bit TPC command in the second embodiment may be configured as a 1-bit or 3-bit TPC command.

[0357] Also, a UE capability may be introduced as to whether to support DCI format 0_1 / 0_2 for indicating TPC commands for two CL-PC adjustment states for SRS.

[0358] In the present disclosure, a CC on which the new field may exist may refer to a scheduled CC indicated by a DCI, or may refer to a scheduling CC of a scheduling DCI.

[0359] <Supplementary Information> <<Notification of Information to UE>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0360] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0361] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0362] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0363] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0364] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0365] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0366] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0367] <<Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: - A higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured. - The specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters. - The specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS. - A specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported. - The application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.

[0368] The specific UE capability may indicate at least one of the following: Support for the specific process / operation / control / assumption / information Support for the multi-TRP scenario with a single DCI Support for scenario 1 (UL dense deployment) Support for scenario 2 (HetNet) Support for UL transmission (SRS / PUSCH / PUCCH / PRACH) to UL reception points Number of supported UL reception points / DL transmission points Support for the same / different CL-PC adjustment state as PUSCH Support for simultaneous configuration of the same / different CL-PC adjustment state as PUSCH Support for DCI format 2_3 indicating the first / second TPC command for a CC Support for srs-TPC-PDCCH-Group = {typeA, typeB} for CL-PC adjustment state different from PUSCH Supporting SRS carrier switching / HetNet-oriented functions (i.e., UE function #1 / #2). Supporting simultaneous configuration of UE function #1 / #2. Supporting DCI format 0_1 / 0_2 to indicate TPC commands for two CL-PC adjustment states for SRS.

[0369] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0370] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0371] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0372] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment of the present disclosure. [Supplementary Note 1] A terminal including: a receiver that receives either a first Radio Resource Control (RRC) parameter or a second RRC parameter, wherein the first RRC parameter and the second RRC parameter indicate a start position of a block in downlink control information (DCI) for transmit power control (TPC) command indication for a sounding reference signal (SRS), and the second RRC parameter is indicated by a first integer from 1 to greater than 31, or by a second integer from greater than 31 to a third integer greater than 31; and a controller that controls transmission of the SRS based on either the first RRC parameter or the second RRC parameter. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the third integer is determined based on at least one of a condition related to a frequency range used by the terminal and a condition related to a setting of a specific field included in a specific downlink control information format. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the third integer is set using RRC signaling. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the receiver receives downlink control information for scheduling a physical downlink shared channel, which indicates two closed-loop power control (CL-PC) adjustment states for the SRS.

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

[0374] 18 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as 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).

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

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

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

[0378] 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 location, number, shape, size, etc. of each cell and user terminal 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 the base station 10.

[0379] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

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

[0383] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn 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.

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

[0385] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0401] 19 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0418] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

[0419] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0420] The transceiver 120 may transmit either a first Radio Resource Control (RRC) parameter or a second RRC parameter. The first RRC parameter and the second RRC parameter may indicate a start position of a block in downlink control information (DCI) for indicating a transmit power control (TPC) command for a sounding reference signal (SRS). The second RRC parameter may be indicated by a first integer from 1 to greater than 31, or by a second integer greater than 31 to a third integer greater than 31. The control unit 110 may instruct transmission of an SRS using either the first RRC parameter or the second RRC parameter.

[0421] The third integer may be determined based on at least one of a condition related to a frequency range used by the terminal and a condition related to a setting of a specific field included in a specific downlink control information format.

[0422] The third integer may be configured using RRC signaling.

[0423] The transceiver unit 120 may transmit downlink control information that schedules a physical downlink shared channel, indicating two closed-loop power control (CL-PC) adjustment states for the SRS.

[0424] (User Terminal) Fig. 20 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0440] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0441] 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 and the transmitting / receiving antenna 230.

[0442] The transceiver 220 may receive either a first Radio Resource Control (RRC) parameter or a second RRC parameter. The first RRC parameter and the second RRC parameter may indicate a start position of a block in downlink control information (DCI) for transmit power control (TPC) command indication for a sounding reference signal (SRS). The second RRC parameter may be indicated by a first integer from 1 to greater than 31, or by a second integer greater than 31 to a third integer greater than 31. The controller 210 may control transmission of the SRS based on either the first RRC parameter or the second RRC parameter.

[0443] The third integer may be determined based on at least one of a condition related to a frequency range used by the terminal and a condition related to a setting of a specific field included in a specific downlink control information format.

[0444] The third integer may be configured using RRC signaling.

[0445] The transceiver 220 may receive downlink control information scheduling a physical downlink shared channel that indicates two closed loop power control (CL-PC) adjustment states for the SRS.

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

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

[0448] 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. Fig. 21 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.

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

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

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

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

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

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

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

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

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

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

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

[0460] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0479] 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."

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

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

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

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

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

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

[0486] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

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

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

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

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

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

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

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

[0494] In this 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," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0495] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0496] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0497] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0498] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0499] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0500] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0501] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

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

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

[0504] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

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

[0507] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0508] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0509] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that 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.

[0510] 22 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0511] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0512] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0513] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0514] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0515] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0516] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0517] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0518] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0519] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0520] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0521] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

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

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

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

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

[0526] 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 (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 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0527] 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."

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

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

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

[0531] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0532] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0533] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

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

[0535] 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."

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

[0537] 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."

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

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

[0540] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0541] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0542] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0543] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0544] 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 description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal having: a receiving unit that receives either a first Radio Resource Control (RRC) parameter or a second RRC parameter, wherein the first RRC parameter and the second RRC parameter indicate a start position of a block in downlink control information (DCI) for transmit power control (TPC) command indication for a sounding reference signal (SRS), and the second RRC parameter is indicated by a first integer from 1 to greater than 31, or by a second integer from greater than 31 to a third integer greater than 31; and a control unit that controls transmission of the SRS based on either the first RRC parameter or the second RRC parameter.

2. The terminal according to claim 1, wherein the third integer is determined based on at least one of a condition related to a frequency range used by the terminal and a condition related to the setting of a specific field included in a specific downlink control information format.

3. The terminal of claim 1, wherein the third integer is set using RRC signaling.

4. The terminal according to claim 1, wherein the receiver receives downlink control information that schedules a physical downlink shared channel and indicates two closed-loop power control (CL-PC) adjustment states for the SRS.

5. A wireless communication method for a terminal, comprising: a step of receiving either a first Radio Resource Control (RRC) parameter or a second RRC parameter, wherein the first RRC parameter and the second RRC parameter indicate a start position of a block in downlink control information (DCI) for transmit power control (TPC) command indication for a sounding reference signal (SRS), and the second RRC parameter is indicated by a first integer from 1 to greater than 31, or by a second integer from greater than 31 to a third integer greater than 31; and a step of controlling transmission of the SRS based on either the first RRC parameter or the second RRC parameter.

6. A base station having: a transmitter that transmits either a first Radio Resource Control (RRC) parameter or a second RRC parameter, wherein the first RRC parameter and the second RRC parameter indicate a start position of a block in downlink control information (DCI) for indicating a transmit power control (TPC) command for a sounding reference signal (SRS), and the second RRC parameter is indicated by a first integer from 1 to greater than 31, or by a second integer from greater than 31 to a third integer greater than 31; and a controller that instructs transmission of the SRS using either the first RRC parameter or the second RRC parameter.

Images