Terminal, radio communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives downlink control information indicating a transmission power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) and is associated with a sounding reference signal (SRS); and a control unit that controls the transmission power of the SRS on the basis of the downlink control information.

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, a scenario is being considered in which a terminal (user terminal, User Equipment (UE)) transmits and receives signals to multiple Transmission / Reception Points (TRPs). In this case, in order to mitigate SRS interference, it is necessary to appropriately control the transmission power of a Sounding Reference Signal (SRS) for each TRP.

[0006] Furthermore, the use of DCI to instruct transmission power control of SRS is being considered.

[0007] However, the details of the DCI have not been fully considered, which may result in a failure to appropriately control the UL (SRS) transmission power, resulting 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 the transmission power of an SRS.

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives downlink control information indicating a transmit power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) but is associated with a sounding reference signal (SRS), and a control unit that controls the transmit power of the SRS based on the downlink control information.

[0010] According to one aspect of the present disclosure, the transmission power of the SRS can be appropriately controlled.

[0011] FIG. 1 shows an example of an SRS resource set configuration information element. FIG. 2 shows an example of an SRS resource configuration information element. FIG. 3A shows an example of a typical arrangement of transmission and reception points. FIG. 3B shows an example of a high-density UL arrangement. FIG. 4 shows an example of DL / UL coverage in a Heterogeneous Network (HetNet). FIG. 5 shows an example of a table T1 for mapping between a TPC command field and a specified δ. FIG. 6 shows an example of a specified δ value for each value of a new TPC command field. FIG. 7 shows an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 8 shows an example of a configuration of a base station according to an embodiment. FIG. 9 shows an example of a configuration of a user terminal according to an embodiment. FIG. 10 shows an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 11 shows an example of a vehicle according to an embodiment.

[0012] (SRS) In NR, the use of the sounding reference signal (SRS) is diverse. NR's SRS is not only used for CSI measurement of the uplink (UL) used in the existing LTE (LTE Rel. 8-14), but also for CSI measurement of the downlink (DL), beam management, etc. It is also used.

[0013] A UE may be configured with one or more SRS resources, which may be identified by an SRS Resource Index (SRI).

[0014] Each SRS resource may have (correspond to) one or more SRS ports, for example, the number of ports per SRS may be 1, 2, 4, etc.

[0015] A UE may be configured with one or more SRS resource sets. One SRS resource set may be associated with a predetermined number of SRS resources. The UE may share higher layer parameters for the SRS resources included in one SRS resource set. Note that the term "resource set" in the present disclosure may be interpreted as a set, a resource group, a group, or the like.

[0016] Information regarding the SRS resource or resource set may be configured in the UE using higher layer signaling, physical layer signaling, or a combination thereof.

[0017] The SRS configuration information element (for example, the RRC information element "SRS-Config") may include an SRS resource set configuration information element (FIG. 1), an SRS resource configuration information element (FIG. 2), and the like.

[0018] The SRS resource set configuration information element (e.g., the RRC parameter "SRS-ResourceSet") may include an SRS resource set ID (Identifier) ​​(SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type (resourceType), and information on SRS usage.

[0019] Here, the SRS resource type may indicate the time domain behavior of the SRS resource configuration, and may indicate any of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic SRS (A(AP)-SRS). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation). The UE may transmit A-SRS based on an SRS request in the DCI.

[0020] Furthermore, the use of the SRS ("usage" of the RRC parameter, "SRS-SetUse" of the L1 (Layer-1) parameter) may be, for example, beam management, codebook (CB), non-codebook (NCB), antenna switching, etc. For example, the SRS for codebook or non-codebook use may be used to determine a precoder for codebook-based or non-codebook-based uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmission based on the SRI.

[0021] The beam management SRS may be assumed to be transmitted at a given time instant only once for each SRS resource set, and multiple SRS resources in the same Bandwidth Part (BWP) that have the same time domain behavior may be transmitted simultaneously if they belong to different SRS resource sets.

[0022] The SRS resource configuration information element (e.g., the RRC parameter "SRS-Resource") may include an SRS resource ID (SRS-ResourceId), the number of SRS ports, the SRS port number, the number of transmission combs, SRS resource mapping (e.g., time and / or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, an SRS resource type, a sequence ID, spatial relationship information, etc.

[0023] The value of the transmission comb number (transmissionComb) is {2,4}. The number of SRS ports (nrofSRS-Ports) N ap SRS The value of is {1,2,4}. Antenna port number p i The value of is {1000, 1001, ...}. The number of consecutive OFDM symbols for SRS (nrofSymbols) N symb SRS The value of is {1,2,4}. The offset in symbols, l, counting backward in the time domain from the end of the slot to the start position in the time domain (startPosition). offset is {0,1,...5} and the starting position is l0=N symb slot -1-l offset is given by

[0024] The setting of the number of combs to be transmitted may include a comb offset and a cyclic shift (CS index, CS number).

[0025] comb offset (subcarrier offset) = {0,1,...K TC −1} and CS may be multiplexed using the same number of transmission combs, the same RB, and the same symbol.

[0026] The UE may switch the Bandwidth Part (BWP) for transmitting the SRS for each slot, or may switch the antenna, and may apply at least one of intra-slot hopping and inter-slot hopping to the SRS transmission.

[0027] In the existing SRS, p i Frequency domain starting position k0 for (p_i) p_i is given by the following equation: k0 p_i =k - 0 p_i +Σ b=0 BSRS K TC M SC,b SRS n b (A1)

[0028] where k - denotes the variable k with an overline, which may also be called k-bar. - 0 p_i is comb offset K - TC It may be based on K TC is the number of combs sent. M SC,b SRS is the SRS bandwidth m SRS,b n is the number of subcarriers used for SRS transmission within [RB]. b is a constant.

[0029] (SRS Transmission Power Control) Using the power control adjustment state index l, the SRS 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 formula C1:

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

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

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

[0033] α ＳＲＳ，ｂ，ｆ，ｃ (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

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

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

[0036] 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, if the setting of the SRS power control adjustment state indicates different power control adjustment states during SRS transmission and PUSCH transmission, the SRS power control adjustment state h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ It may be based on (m).

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

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

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

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

[0041] In the present disclosure, power control adjustment state, power control adjustment state index l, closed loop (CL)-power control (PC) adjustment state, CL-PC adjustment state index l, CL state, and CL state index l may be read interchangeably.

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

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

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

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

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

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

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

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

[0050] (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, via the parameter srs-SwitchFromCarrier.

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

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

[0053] (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-complementary uplink carrier.

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

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

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

[0057] 3A shows a typical example of a transmission / reception point (TRP) arrangement. In this example, a UE receives DL signals from a transmission / reception point (TRP) and transmits UL signals to the TRP. For example, if the UE and the TRP are far apart, the path loss may be large, resulting in poor communication quality.

[0058] 3B is a diagram showing an example of a high-density UL deployment. As shown in this example, in order to expand UL coverage, it is considered to provide UL reception points in addition to the TRPs (DL transmission points) as in the general deployment example. In this example of a high-density UL deployment, a UE receives DL signals from a DL transmission point (TRP / Central TRP / DL 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 / received power). However, the UE can also perform UL transmission to a DL transmission point.

[0059] By using a configuration such as the UL high-density configuration example, it is possible to reduce path loss, improve UL signaling quality, and obtain a higher coding rate, thereby improving both coverage and UL data rate, compared to the general configuration example. 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.

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

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

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

[0063] (TPC command for SRS) As described above, in future wireless communication systems, a scenario in which a UE transmits and receives data for multiple TRPs is being considered. In this case, in order to mitigate SRS interference, it is necessary to appropriately control the transmission power of the SRS for each TRP. For example, the existing DCI2_3 supports carrier switching (multiple carriers), but in scenario 1 (UL high density deployment) or scenario 2 (HetNet), there may be multiple TRPs in one cell.

[0064] For FR1 and FR2, assuming the unified TCI framework of Rel. 17 / 18 and full reuse of existing QCL / UL spatial relationship rules, extensions for asymmetric DL sTRP / UL mTRP deployment scenarios (e.g., scenarios 1 / 2) are considered, with existing cell definitions unchanged or new cells defined. Two closed-loop power control (CL-PC) adjustment states for SRS, both separate from the CL adjustment state for PUSCH, and a pathloss offset setting for pathloss calculation to UL TRP(s) when the pathloss RS is from the DL sTRP are considered.

[0065] TPC command indication for SRS with CL-PC adjustment state not associated with PUSCH is considered.

[0066] For example, if two CL-PC adjustment states are configured for SRS for a UE, the following options may be applied as a method of indicating TPC commands for these two CL-PC adjustment states using DCI:

[0067] Option 1: Extension of existing DCI format 2_3 with upper layer parameter srs-TPC-PDCCH-Group = type A.

[0068] Option 2: Extension of existing DCI format 2_3 with upper layer parameter srs-TPC-PDCCH-Group = type B.

[0069] Option 3: Extension of existing DCI format 2_3 with upper layer parameter srs-TPC-PDCCH-Group = type A and type B.

[0070] Option 4: Extension of DCI format 1_1 / 0_1 indicating TPC command for CL-PC adjustment state for SRS.

[0071] Option 5: Extension of existing DCI format 2_3 by introducing a new type in the upper layer parameter srs-TPC-PDCCH-Group.

[0072] Option 6: Introduction of a new DCI format to indicate TPC commands for CL-PC adjustment status for SRS.

[0073] Other options may be applied, not limited to those listed above.

[0074] For the above options 1, 2, 3 and 5, at least one of the following options Alt1 to Alt4 may also be applied:

[0075] Alt1: In DCI format 2_3, add one TPC command for each CC with two CL-PC adjustment states for SRS, where the first TPC command is associated with the first CL-PC adjustment state and the second TPC command is associated with the second CL-PC adjustment state.

[0076] Alt2: A 1-bit dedicated field (CL-PC indication field) is introduced into each TPC command of DCI format 2_3, which indicates the first CL-PC adjustment state or the second CL-PC adjustment state for the SRS.

[0077] Alt3: Two different TPC-SRS-RNTIs are used for DCI format 2_3. DCI format 2_3 with CRCs scrambled by the first TPC-SRS-RNTI and the second TPC-SRS-RNTI indicates TPC commands in the first and second CL-PC adjustment states, respectively.

[0078] Alt4: Implicit indication method. For example, DCI format 2_3 transmitted in an even frame indicates a TPC command in the first CL-PC adjustment state, and DCI format 2_3 transmitted in an odd frame indicates a TPC command in the second CL-PC adjustment state.

[0079] It is considered that a UE configured with two SRS CLPC adjustment states may support the following options for indicating one of the two SRS CLPC adjustment states for the SRS: ◆ Options: If the parameter srs-PowerControlAdjustmentStates is set to 'separateClosedLoop', the closedLoopIndex-r17 for the SRS in the TCI state indicates one of the two SRS CLPC adjustment states.

[0080] When a UE is configured with two SRS CLPC adjustment states, the following option (the above-mentioned option 3) is being considered to be supported in order to indicate TPC commands for the two SRS CLPC adjustment states via DCI: ◆ Option: Extension of existing DCI format 2_3 with upper layer parameter srs-TPC-PDCCH-Group = type A and type B.

[0081] To extend the DCI format for the indication of TPC commands for two SRS CLPC adjustment states, the following option (Alt2 above) is being considered for support: ◆ Option: Within DCI format 2_3, a 1-bit closed-loop-indicator field is introduced for each TPC command. This 1-bit closed-loop indicator indicates the first or second CL-PC adjustment state for the SRS. This 1-bit closed-loop indicator is present in CCs where two SRS CLPC adjustment states are configured.

[0082] In an asymmetric DL sTRP / UL mTRP configuration scenario, when a UE is configured with two SRS CLPC adjustment states, it is considered whether to indicate a TPC command for the SRS CL-PC adjustment state via DCI format 1_1 / 0_1 and how to indicate the TPC command.

[0083] The P0-alpha set (P0AlphaSet-r17) may include a closed-loop index (CL-PC ID, closedLoopIndex-r17). The closedLoopIndex-r17 is set to a value {10, 11}. In this disclosure, CL-PC ID = {0, 1} and closedLoopIndex-r17 = {10, 11} may be interchangeable.

[0084] The TPC commands in the UE-specific DCI are based on the following: In DCI format 0_x, TPC commands for scheduled PUSCH are supported. In DCI format 1_x, TPC commands for scheduled PUCCH are supported.

[0085] Up to Rel. 18, TPC commands for SRS in UE-specific DCI are not supported.

[0086] (UE-specific DCI without dynamic scheduling of PUSCH) DCI format 0_x is used for several: ◆ Activation / deactivation (release) of type 2 configured grant (CG) ◆ Aperiodic (A) - PUSCH with CSI-only triggering ◆ A - SRS-only triggering

[0087] As special combinations (one or more special values) for DCI format 0_x, conditions are defined that determine that the DCI needs to be treated as something other than a dynamic grant (DG).

[0088] DCI formats 0_0 / 0_1 / 0_2 for activation / deactivation of Type 2CG PUSCH satisfy some of the following conditions (special values): ◆ CRC scrambling = CS-RNTI. ◆ new date indicator (NDI) field = '0'. ◆ downlink feedback information (DFI) flag field = '0' if present. ◆ time domain resource assignment (TDRA) field = single start and length indicator value (SLIV). ◆ HARQ process number (HPN) field = '0'. ◆ redundancy version (RV) field = '0' (for enabled transport blocks (TBs)). ◆ modulation and coding scheme (MCS) field = all '1's. ◆ frequency domain resource assignment (FDRA) field = value according to scheduling (all '0's for FDRA type 0 or dynamic switch, all '1's for FDRA type 1).

[0089] DCI format 0_x for PUSCH with A-CSI only triggering satisfies some conditions (special values) below: ◆ UL-SCH field = '0'. ◆ CSI request field = non-zero.

[0090] DCI format 0_x for A-SRS only triggering satisfies some conditions (special values) below: ◆ UL-SCH field = '0'. ◆ CSI request field = '0'.

[0091] (UE-specific DCI without dynamic scheduling of PDSCH) DCI format 1_x without PDSCH scheduling is used for several things: ◆ SPS PDSCH activation / deactivation ◆ SCell dormancy indication ◆ Type 3 HARQ-ACK codebook determination ◆ HARQ-ACK codebook retransmission ◆ Unified TCI status indication

[0092] As a special combination (one or more special values) for DCI format 1_x, a condition that determines that the DCI needs to be treated as something other than a dynamic grant (DG) is defined.

[0093] DCI formats 1_0 / 1_1 / 1_2 for SPS PDSCH activation / deactivation satisfy the following conditions (special values): ◆ CRC scrambling = CS-RNTI. ◆ NDI field = '0'. ◆ TDRA field = single SLIV. ◆ PDSCH-to-HARQ_feedback indicator field = not an inapplicable value. ◆ HPN field = '0'. ◆ RV field = '0' (for enabled transport blocks (TBs)). ◆ MCS field = All '1's. ◆ FDRA field = value according to scheduling (All '0's for FDRA type 0 or dynamic switch, All '1's for FDRA type 1).

[0094] DCI format 1_1 / 1_2 for determining the type 3 HARQ-ACK codebook satisfies some of the following conditions (special values): ◆ CRC scrambling = CS-RNTI or MCS-C-RNTI. ◆ MCS field = reused to determine the number of cells and the number of HPNs. ◆ FDRA field = All '0's for FDRA type 0 or dynamic switch, and All '1's for FDRA type 1. ◆ One-shot HARQ-ACK request field = '1'.

[0095] DCI format 1_1 / 1_2 for HARQ-ACK codebook retransmission satisfies some of the following conditions (special values): ◆ CRC scrambling = CS-RNTI or MCS-C-RNTI. ◆ MCS field = reused to determine slot m. ◆ FDRA field = All '0's for FDRA type 0 or dynamic switch, All '1's for FDRA type 1. ◆ HARQ-ACK retransmission indicator field = '1'.

[0096] DCI format 1_x for SCell latency indication without DL assignment satisfies some conditions (special values) below: ◆ CRC scrambling = CS-RNTI or MCS-C-RNTI. ◆ NDI field = reused for SCell index indication (for the first TB only). ◆ HPN field = reused for SCell index indication. ◆ RV field = reused for SCell index indication (for the first TB only). ◆ MCS field = reused for SCell index indication (for the first TB only). ◆ FDRA field = All '0's for FDRA type 0 or dynamic switch, All '1's for FDRA type 1. ◆ One-shot HARQ-ACK request field = not set or '0'. ◆ Carrier indicator field = not set or '0'.

[0097] DCI format 1_1 / 1_2 for unified TCI status indication without DL assignment satisfies some of the following conditions (special values): ◆ CRC scrambling = CS-RNTI. ◆ NDI field = All '0's. ◆ RV field = All '1's. ◆ MCS field = All '1's. ◆ FDRA field = All '0's for FDRA type 0 or dynamic switch, All '1's for FDRA type 1.

[0098] (Unified TCI status indication without DL assignment) DCI format 1_2 / 1_2 for retransmission of DL SPS includes the following special combinations (one or more special values): ◆ CRC scrambling = CS-RNTI. ◆ RV field = for scheduling. ◆ MCS field = for scheduling. ◆ NDI field = '1'. ◆ HPN field = for scheduling. ◆ Antenna port field = for scheduling. ◆ DMRS sequence initialization field = for scheduling. ◆ FDRA field = for scheduling.

[0099] DCI format 1_2 / 1_2 for DL ​​SPS activation without DL assignment includes the following special combinations (one or more special values): ◆ CRC scrambling = CS-RNTI. ◆ RV field = All '0's. ◆ MCS field = for scheduling. ◆ NDI field = '0'. ◆ HPN field = All '0's for single DL SPS release. ◆ Antenna port field = for scheduling. ◆ DMRS sequence initialization field = for scheduling. ◆ FDRA field = for scheduling.

[0100] DCI format 1_2 / 1_2 for DL ​​SPS release without DL assignment contains the following special combinations (one or more special values): ◆ CRC scrambling = CS-RNTI. ◆ RV field = All '0's. ◆ MCS field = All '1's. ◆ NDI field = '0'. ◆ HPN field = All '0's for single DL SPS release. ◆ Antenna port field = Not used. ◆ DMRS sequence initialization field = Not used. ◆ FDRA field = All '0's for FDRA type 0, All '1's for FDRA type 1, All '0's for dynamic switch.

[0101] DCI format 1_2 / 1_2 for SCell latency indication without DL assignment includes the following special combinations (one or more special values): ◆ CRC scrambling = CS-RNTI. ◆ RV field = reinterpreted for SCell latency indication. ◆ MCS field = reinterpreted for SCell latency indication. ◆ NDI field = reinterpreted for SCell latency indication. ◆ HPN field = reinterpreted for SCell latency indication. ◆ Antenna port field = reinterpreted for SCell latency indication. ◆ DMRS sequence initialization field = reinterpreted for SCell latency indication. ◆ FDRA field = All '0's for FDRA type 0, All '1's for FDRA type 1, All '0's or All '1's for dynamic switch.

[0102] DCI format 1_2 / 1_2 for beam indication without DL assignment includes the following special combinations (one or more special values): ◆ CRC scrambling = CS-RNTI. ◆ RV field = All '1's. ◆ MCS field = All '1's. ◆ NDI field = '0'. ◆ HPN field = Not used. ◆ Antenna port field = Not used. ◆ DMRS sequence initialization field = Not used. ◆ FDRA field = All '0's for FDRA type 0, All '1's for FDRA type 1, All '0's for dynamic switch.

[0103] (Type 3 HARQ-ACK Codebook Determination) When the UE detects a DCI format including a one-shot HARQ-ACK request field with the value 1 and the CRC of that DCI is scrambled by the C-RNTI or MCS-C-RNTI, if, for one or more serving cells, either: ◆ resourceAllocation = resourceAllocationType0 and all bits of the FDRA field in that DCI are equal to 0, ◆ resourceAllocation = resourceAllocationType1 and all bits of the FDRA field in that DCI are equal to 1, or ◆ resourceAllocation = dynamicSwitch and all bits of the FDRA field in that DCI are equal to 0 or 1, then the DCI format provides Type 3 HARQ-ACK codebook reporting and does not schedule PDSCH reception on the one or more serving cells. If the UE has been provided with pdsch-HARQ-ACK-EnhType3ToAddModList and the DCI format includes an Extended Type 3 Codebook Indicator field that provides a value for pdsch-HARQ-ACK-EnhType3Index, the UE shall select the size N of the set of indicated serving cells for each indicated serving cell and each indicated HARQ process number from the entries in the pdsch-HARQ-ACK-EnhType3ToAddModList that correspond to the pdsch-HARQ-ACK-EnhType3Index value. cells DL,ind and the size of the set of indicated HARQ process numbers N HARQ,c DL,indIf the DCI format does not include an Extended Type 3 Codebook Indicator field, the pdsch-HARQ-ACK-EnhType3Index value is provided by one of the following values: ◆ If the DCI format is DCI format 1_1, the MCS field for transport block 1, ◆ If the DCI format is DCI format 1_2, the MCS field, ◆ If the DCI format is DCI format 1_3, the MCS field for transport block 1 of the serving cell with the smallest index among the one or more serving cells.

[0104] (HARQ-ACK Codebook Retransmission) If the HARQ-ACK retransmission indicator field value in the DCI format is '1', the UE determines slot m as m = nl, where l is determined by a one-to-one mapping in ascending order between values ​​from -7 to 24 and the following values: ◆ MCS field for transport block 1 if the DCI format is DCI format 1_1, ◆ MCS field if the DCI format is DCI format 1_2, ◆ MCS field for transport block 1 of a serving cell if the DCI format is DCI format 1_3. Here, the serving cell has one of the following and is the serving cell with the smallest index: - resourceAllocation = resourceAllocationType0 and all bits of the FDRA field in the DCI are equal to 0; - resourceAllocation = resourceAllocationType1 and all bits of the FDRA field in the DCI are equal to 1; - resourceAllocation = dynamicSwitch and all bits of the FDRA field in the DCI are equal to 0 or 1;

[0105] (Issues) When DCI format 0_1 / 1_1 is used to indicate a TPC command for an SRS having a CL-PC adjustment state different from that of a PUSCH, how that DCI format indicates the TPC command has not been sufficiently considered. Furthermore, when two CL-PC adjustment states are given to an SRS that is not associated with a PUSCH, the indication of the CL-PC adjustment state has not been sufficiently considered. If these points are not sufficiently considered, the UL transmission power may not be appropriately controlled, which may result in a decrease in communication quality / throughput.

[0106] Therefore, the present inventors have conceived a method for appropriately controlling the transmission power of the SRS.

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

[0108] (Reinterpretation, etc.) 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.

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

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

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

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

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

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

[0115] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

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

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

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

[0119] In the present disclosure, the terms TRP, base station, gNB, and network (NW) may be interchangeable. In the present disclosure, the terms TRP, RS group, antenna port group, and control resource set (CORESET) group may be interchangeable.

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

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

[0122] In the present disclosure, the terms TRP, 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 certain conditions are met.

[0123] In the present disclosure, the terms TRP, 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.

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

[0125] In the present disclosure, the terms cell and cell ID may be interchangeable. In the present disclosure, the terms TRP and TRP ID may be interchangeable.

[0126] Each embodiment of the present disclosure may be premised on either Scenario 1 (UL high density deployment) or Scenario 2 (HetNet) above.

[0127] The number of TRPs in each embodiment of the present disclosure may be two or more (e.g., two or four). The number of TRPs may increase the number of fields or bits in the fields in the DCI related to the indication per TRP. The TRP of the present disclosure may be a TRP for UL (SRS) transmission.

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

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

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

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

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

[0133] In the present disclosure, the configuration / instruction for the SRS may be performed in units of resource sets or in units of resources. That is, in the present disclosure, the terms resource set and resource may be interchangeable.

[0134] In the present disclosure, the setting / instruction for the SRS may be in CC units or in BWP units, i.e., CC and BWP may be interchangeable.

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

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

[0137] (Wireless communication method) A UE may perform transmission power control based on at least one embodiment. A NW / BS / gNB may provide / transmit to the UE settings / instructions for the UE to realize the control.

[0138] For some embodiments, at least one of the following scenarios may be assumed: ◆ Scenario A1: An additional TPC field for SRS is introduced, and data is scheduled by the DCI. ◆ Scenario A2: An additional TPC field for SRS is introduced, and data is not scheduled by the DCI. A distinction may be made between a DCI that only indicates an SRS TPC command and a data scheduling DCI. ◆ Scenario B1: An existing DCI field is converted into a TPC indication for SRS, and data is scheduled by the DCI. Whether the existing TPC is converted into TPC for SRS may be switched (for example, when TPC for PUSCH / PUCCH is converted into TPC for SRS). ◆ Scenario B2: An existing DCI field is converted into a TPC indication for SRS, and data is not scheduled by the DCI. A distinction may be made between a DCI that only indicates an SRS TPC command and a data scheduling DCI.

[0139] First Embodiment This embodiment relates to scenarios A1 and A2.

[0140] An additional DCI field may be introduced to explicitly indicate the TPC command for SRS. A new DCI field may be added for SRS to indicate the TPC command associated with a different CL-PC adjustment state than PUSCH. The new DCI field may be, for example, a new TPC command field. The new DCI field may be based on at least one of the following options:

[0141] ◆ Option 1: The size (bit width) of the new DCI field may be based on at least one of the following several options 1-x: ◆ Option 1-1: 2 bits. In this case, Table T1 (Fig. 5) similar to the existing specification for mapping between the TPC command field and the indicated δ may be applied to the new TPC command field and referenced. Table T1 is used to reference the accumulated δPUSCH,b,f,c value or δ of the TPC command field in a DCI format scheduling a PUSCH transmission, or in DCI format 2_2 with CRC scrambled by the TPC-PUSCH-RNTI, or in DCI format 2_3. SRS,b,c The following shows the mapping to the value: -◆ Option 1-2: 1 bit. -◆ Option 1-3: More than 2 bits. The new DCI field may be at least one of a TPC command and a 1-bit field for distinguishing the CL-PC ID of the TPC command for SRS.

[0142] ◆ Option 2: The mapping between the value of the new TPC command field and the indicated value of δ may be determined based on at least one of a specific rule and "Notification of Information to UE" in the "Supplementary Note" described later. The mapping may be based on at least one of the following examples: - ◆ Example 1: Table T1. - ◆ Example 2: The indicated value of δ (e.g., Figure 6) for each value of the new TPC command field is configured by RRC. - ◆ Example 3: The indicated value of δ for each value of the new TPC command field is indicated by DL MAC CE / DCI.

[0143] The new DCI fields may be present only if the corresponding RRC parameters are configured.

[0144] The new DCI fields may be present whether or not the DCI schedules data, or may be present only if the DCI schedules data.

[0145] According to the first embodiment, for SRS, a TPC command associated with a CL-PC adjustment state different from that of PUSCH can be appropriately indicated using a new DCI field.

[0146] Second Embodiment This embodiment relates to scenarios B1 and B2.

[0147] An existing DCI field may be reused for the SRS TPC indication. This embodiment can prevent an increase in DCI overhead. This embodiment may be based on at least one of the following options:

[0148] ◆ Option 1: The existing DCI field repurposed for SRS TPC indication may be at least one of the following several options 1-x: - ◆ Option 1-1: TPC command field for PUSCH. - ◆ Option 1-2: TPC command field for PUCCH. - ◆ Option 1-3: Part or all of the TDRA field. For example, the 2 most significant bits (2 MSBs, upper 2 bits) or 2 least significant bits (2 LSBs, lower 2 bits) of the TDRA field. - ◆ Option 1-4: Part or all of the HPN field. - ◆ Option 1-5: Part or all of the RV field. - ◆ Option 1-6: Part or all of the NDI field. - ◆ Option 1-7: Part or all of the MCS field. - ◆ Option 1-8: Part or all of the antenna port field. - ◆ Option 1-9: Part or all of the PUCCH resource indicator field. - ◆ Option 1-10: SRS request field. -◆ Option 1-11: DMRS sequence initialization field. Option 1 may be based on at least one of the following examples: -◆ Example 1: The TPC command field for PUSCH in DCI format 0_1 ​​is reused as the TPC command for SRS. This example is preferred when DCI format 0_1 ​​is used for SRS TPC indication. -◆ Example 2: The TPC command field for PUCCH in DCI format 1_1 is reused as the TPC command for SRS. This example is preferred when DCI format 1_1 is used for SRS TPC indication. -◆ Example 3: The 2 MSBs of the TDRA field in DCI format x_1 are reused as the TPC command for SRS. -◆ Example 4: 1 MSB of the RV field and 1 MSB of the NDI are reused as the TPC command for SRS.

[0149] ◆ Option 2: Whether the UE substitutes an existing DCI field as a TPC command for SRS may be determined based on at least one of the rules in the specifications and "Notification of Information to the UE" in the "Supplementary Note" described later. The determination may be at least one of several options 2-x below. - ◆ Option 2-1: An additional bit in the DCI explicitly indicates whether a TPC command for PUSCH / PUCCH is substituted as a TPC command for SRS. The additional bit may be a new DCI field, or part or all of the existing DCI fields. - ◆ Option 2-2: Whether the UE substitutes an existing DCI field as a TPC command for SRS is implicitly determined based on specific conditions (special combination, one or more special values) of one or more other DCI fields. Details of the determination may follow embodiment 3.

[0150] ◆ Option 3: The size (bit width) of the TPC command for SRS based on the repurpose is based on Option 1 of the first embodiment.

[0151] ◆ Option 4: The mapping between the diversion-based TPC command values ​​and the indicated δ values ​​is based on Option 2 of the first embodiment.

[0152] According to the second embodiment, for SRS, a TPC command associated with a CL-PC adjustment state different from that of PUSCH can be appropriately indicated using an existing DCI field.

[0153] Third Embodiment This embodiment relates to scenario (A2, B1,) B2.

[0154] Whether the DCI indicates a TPC command for SRS may be distinguished explicitly or implicitly. According to this embodiment, the SRS TPC command can be indicated in a wider range of scenarios. For example, the SRS TPC command can be indicated in a scenario where data scheduling is not required.

[0155] The above-mentioned "whether the DCI indicates a TPC command for SRS" may be rephrased as follows: ◆ "whether the DCI schedules data", in which case a DCI that does not schedule data may imply that it indicates only a TPC command for SRS.

[0156] This embodiment may be applied in at least one of the following scenarios:

[0157] <<Assumption 1>> This embodiment is applied to scenario A2 / B2, DCI format 1_1. When a UE detects a DCI, if at least one of the RNTI and DCI fields in the DCI satisfies a specific condition, the UE may distinguish / determine that the DCI indicates a TPC command for SRS. The specific condition may be based on at least one of the following options:

[0158] ◆ Option 1: The RNTI is considered under the specific condition. The specific condition may be that the RNTI of the DCI is a specific RNTI. The specific RNTI may be at least one of several options 1-x below: - ◆ Option 1-1: C-RNTI. - ◆ Option 1-2: CS-RNTI. - ◆ Option 1-3: MCS-C-RNTI. - ◆ Option 1-4: Other RNTI.

[0159] ◆ Option 2: The value of the DCI field is taken into account in the specific condition. The DCI field may be at least one of several of the following options 2-x: - ◆ Option 2-2: TPC command field for PUCCH. - ◆ Option 2-3: Part or all of the TDRA field. - ◆ Option 2-4: Part or all of the HPN field. - ◆ Option 2-5: Part or all of the RV field. - ◆ Option 2-6: Part or all of the NDI field. - ◆ Option 2-7: Part or all of the MCS field. - ◆ Option 2-8: Part or all of the antenna port field. - ◆ Option 2-9: Part or all of the PUCCH resource indicator field. - ◆ Option 2-10: SRS request field. - ◆ Option 2-11: DMRS sequence initialization field. - ◆ Option 2-12: Part or all of the FDRA field.

[0160] Option 1 / 2 may be based on at least one of the following examples:

[0161] ◆ Case 1: If the condition is met, the UE interprets the DCI as indicating only an SRS TPC command. That is, if the condition is met, the UE may interpret the DCI as having no DL scheduling. The condition may be one of the following cases 1-x, or a combination of several of the following conditions: ◆ Condition 1: The CRC of the DCI is addressed to the CS-RNTI. ◆ Condition 2: The NDI field is set to '0'. ◆ Condition 3: The HPN field is set to '0'. ◆ Condition 4: The RV field is set to all '1's. The RV may be the RV for an enabled TB. ◆ Condition 5: The MCS field is set to all '0's. The special value may be a value other than all '1's instead of all '0's, or may be a value other than all '0's and all '1's. --◆Condition 6: For FDRA type 0 or dynamic switch, the FDRA field is set to all '0's. For FDRA type 1, the FDRA field is set to all '1's. --◆Variation: Condition 1 & Condition 2 & Condition 3 & Condition 4 & Condition 5. In other words, Condition 6 is not included.

[0162] ◆ Case 2: If the condition is met, the UE interprets the DCI as indicating only an SRS TPC command. That is, if the condition is met, the UE may interpret the DCI as not having DL scheduling. The condition may be one of the following cases 1-x, or a combination of multiple conditions: ◆ Condition 1: The CRC of the DCI is addressed to the CS-RNTI or the MCS-C-RNTI. ◆ Condition 2: The FDRA field is set to all '0's for FDRA type 0 or dynamic switch. The FDRA field is set to all '1's for FDRA type 1 or dynamic switch. ◆ Condition 3: An RRC parameter (e.g., an RRC parameter enabling the SRS TPC indication by DCI format 1_1) is configured. -◆Condition 4: A DCI field (e.g., a DCI field indicating whether an SRS TPC command is indicated) indicates that an SRS TPC command is indicated. -◆Variation: Condition 1 & Condition 2 & Condition 3. The conditions may include at least Condition 3. -◆Variation: Condition 1 & Condition 2 & Condition 4. The conditions may include at least Condition 4.

[0163] <<Assumption 2>> This embodiment is applied to scenario A2 / B2, DCI format 0_1. When a UE detects a DCI, if at least one of the RNTI and DCI fields in the DCI satisfies a specific condition, the UE may distinguish / determine that the DCI indicates a TPC command for SRS. The specific condition may be based on at least one of the following options:

[0164] ◆ Option 1: The RNTI is considered under the specific condition. The specific condition may be that the RNTI of the DCI is a specific RNTI. The specific RNTI may be at least one of several options 1-x below: - ◆ Option 1-1: C-RNTI. - ◆ Option 1-2: CS-RNTI. - ◆ Option 1-3: MCS-C-RNTI. - ◆ Option 1-4: Other RNTI.

[0165] ◆ Option 2: The value of the DCI field is taken into account in the specific condition. The DCI field may be at least one of several of the following options 2-x: - ◆ Option 2-2: TPC command field for PUCCH. - ◆ Option 2-3: Part or all of the TDRA field. - ◆ Option 2-4: Part or all of the HPN field. - ◆ Option 2-5: Part or all of the RV field. - ◆ Option 2-6: Part or all of the NDI field. - ◆ Option 2-7: Part or all of the MCS field. - ◆ Option 2-8: Part or all of the antenna port field. - ◆ Option 2-9: Part or all of the PUCCH resource indicator field. - ◆ Option 2-10: SRS request field. - ◆ Option 2-11: DMRS sequence initialization field. - ◆ Option 2-12: Part or all of the FDRA field.

[0166] Option 1 / 2 may be based on at least one of the following examples:

[0167] ◆ Case 1: If the condition is met, the UE interprets the DCI as indicating only an SRS TPC command. That is, if the condition is met, the UE may interpret the DCI as having no UL scheduling. The condition may be one of the following cases 1-x, or a combination of several of the following conditions: ◆ Condition 1: The CRC of the DCI is addressed to the CS-RNTI. ◆ Condition 2: The NDI field is set to '0'. ◆ Condition 3: The HPN field is set to '0'. ◆ Condition 4: The RV field is set to all '1's. The RV may be the RV for an enabled TB. ◆ Condition 5: The MCS field is set to all '0's. The special value may be a value other than all '1's instead of all '0's, or may be a value other than all '0's and all '1's. --◆Condition 6: For FDRA type 0 or dynamic switch, the FDRA field is set to all '0's. For FDRA type 1, the FDRA field is set to all '1's. --◆Variation: Condition 1 & Condition 2 & Condition 3 & Condition 4 & Condition 5. In other words, Condition 6 is not included.

[0168] ◆ Case 2: If the condition is met, the UE interprets the DCI as indicating only an SRS TPC command. That is, if the condition is met, the UE may interpret the DCI as having no UL scheduling. The condition may be one of the following cases 1-x, or a combination of several of the following conditions: ◆ Condition 1: The CRC of the DCI is addressed to the CS-RNTI or the MCS-C-RNTI. ◆ Condition 2: The FDRA field is set to all '0's for FDRA type 0 or dynamic switch. The FDRA field is set to all '1's for FDRA type 1 or dynamic switch. ◆ Condition 3: The UL-SCH field is set to '0'. ◆ Condition 4: The CSI request field is set to '0'. ◆ Condition 5: The SRS request field is set to '0'. -◆Condition 6: An RRC parameter (e.g., an RRC parameter that enables an SRS TPC instruction using DCI format 1_1) is set. -◆Condition 7: A DCI field (e.g., a DCI field that indicates whether an SRS TPC command is indicated) indicates that an SRS TPC command is indicated. -◆Variation: Condition 2 (& Condition 1) (& Condition 6) (& Condition 7). The conditions may include at least Condition 2. -◆Variation: Condition 3 & Condition 4 & Condition 5 (& Condition 1) (& Condition 6) (& Condition 7). The conditions may include at least Condition 3 & Condition 4 & Condition 5.

[0169] According to the third embodiment, the DCI indicates the TPC command for SRS, which can be determined appropriately.

[0170] <Embodiment 4> This embodiment relates to the target of the indicated SRS TPC command.

[0171] Which of the two CL-PC adjustment states for SRS not associated with a PUSCH is the target of the indicated SRS TPC command may be determined based on a specific rule, which may be based on at least one of several options:

[0172] ◆ Option 1: The specific rule may be based on at least one of several options 1-x below.

[0173] Option 1-1: Only one state defined in the specification is always considered. For example, CL-PC adjustment state = 0 for an SRS not associated with a PUSCH may always be the subject of a TPC command indicated via DCI format 0_1 / 1_1.

[0174] -◆ Option 1-2: One of the two states is determined based on the "Notification of Information to UE" in the "Supplementary Information" section below. This option may be based on at least one of the following examples: --◆ Example 1: A new RRC parameter may set one state as the target of a TPC command. --◆ Example 2: A new DCI field may set one state as the target of a TPC command. This example is suitable for a CL-PC ID indication for SRS, which requires only one additional bit of overhead. The presence of the new DCI field may depend on the setting of the new RRC parameter. That is, if the new RRC parameter is not set, the new DCI field is not present in the DCI.

[0175] -◆ Option 1-3: At least one of an existing RRC parameter and an existing DCI field is substituted to indicate one of two states. One or more existing DCI fields in Option 1 of embodiment 2 may be substituted to indicate one of two states. For example, the one or more existing DCI fields may be at least one of the MSB of the TDRA field, the MSB of the PUCCH resource indicator field, the MSB of the antenna port field, the SRS request field (CL-PC index of the indicated SRS resource set), the SRS resource set indicator field, the transmission configuration indication (TCI) field (CL-PC index of the indicated TCI state), and the TCI selection field. If the intended CL-PC index does not fit into the one or more existing DCI fields, the gNB may set the field for the TPC command for SRS to a value corresponding to 0 dB.

[0176] ◆ Option 2: Default rules / exceptions are defined for the specific rules in option 1. This option may be based on at least one of several options 2-x below.

[0177] -◆ Option 2-1: (For example, if the new DCI field in Option 1-2 is not present) The UE expects / assumes that the indicated TPC command applies to a specific CL-PC adjustment state index for an SRS not associated with a PUSCH. The specific CL-PC adjustment state index may be 0 or 1.

[0178] According to the fourth embodiment, the CL-PC adjustment state that is the target of the indicated SRS TPC command can be appropriately determined.

[0179] <DCI Format> At least one DCI format among the following options may be applied to each embodiment. ◆ Option 1: DCI format 0_0. ◆ Option 2: DCI format 0_1. ◆ Option 3: DCI format 0_2. ◆ Option 4: DCI format 0_3. ◆ Option 5: DCI format 1_0. ◆ Option 6: DCI format 1_1. ◆ Option 7: DCI format 1_2. ◆ Option 8: DCI format 1_3. ◆ Option 9: Other DCI formats. For example, DCI format 2_x (group-common DCI). For example, DCI format 4_x (DCI for scheduling multicast / broadcast service (MBS)).

[0180] <DCI Fields> When one or more DCI fields are diverted for at least one of an SRS TPC command indication and a CL-PC index indication (as in embodiment 2), at least one of the following behaviors may be defined regarding the handling of one or more DCI fields not used for the SRS TPC command indication: ◆ All or part of one or more DCI fields not used for the SRS TPC command indication are ignored. ◆ All or part of one or more DCI fields not used for the SRS TPC command indication are reserved.

[0181] When the DCI indicates at least one of an SRS TPC command indication and a CL-PC index indication and does not schedule data (as in embodiment 3), at least one of the following behaviors may be defined regarding the handling of one or more DCI fields not used for the SRS TPC command indication: ◆ All or part of one or more DCI fields not used for the SRS TPC command indication are ignored. ◆ All or part of one or more DCI fields not used for the SRS TPC command indication are reserved.

[0182] When the SRS TPC command indication is configured and the DCI schedules data only (e.g., when a new DCI field for at least one of the SRS TPC command indication and the CL-PC index indication is configured and the DCI schedules data only), at least one of the following behaviors may be defined regarding the handling of one or more DCI fields used for the SRS TPC command indication: ◆ All or part of one or more DCI fields used for the SRS TPC command indication are ignored. ◆ All or part of one or more DCI fields used for the SRS TPC command indication are reserved.

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

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

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

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

[0187] In the above embodiment, the UE may receive information on at least one of the following QCL rules from the NW: QCL Type A QCL Type B QCL Type C QCL Type D

[0188] In the above embodiment, the QCL source RS for each QCL type may be at least one of the following several RSs: ◆ SSB ◆ CSI-RS with / without repetition ◆ TRS ◆ DMRS of PDCCH / PDSCH

[0189] In the above-described embodiment, the information from the NW may be set / instructed by the following methods: Common to multiple UEs or UE-specific Cell-specific or common to multiple cells Per UE / per CC / per BWP / per band / per cell / per cell group (CG)

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

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

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

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

[0194] <<Regarding Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-mentioned 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.

[0195] At least one of the above-described embodiments may be applied only to UEs that have reported or support a specific UE capability. Note that "supporting" and "whether to support" may be interpreted as interchangeable.

[0196] The specific UE capability may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments; - Supporting SRS transmit power control per TRP; - Number of supported TRPs; - Supporting multi-TRP scenarios with single DCI; - Supporting scenario 1 (UL dense deployment); - Supporting scenario 2 (HetNet); - Supporting UL transmission (SRS / PUSCH / PUCCH / PRACH) to UL reception points; - Number of supported UL reception points / DL transmission points; - Supporting the same / different CL-PC adjustment state as PUSCH; - Supporting simultaneous setting of the same / different CL-PC adjustment state as PUSCH; - Supporting DCI format X_Y indicating first / second TPC command for a CC (X, Y are arbitrary); - srs-TPC-PDCCH-Group = for CL-PC adjustment state different from PUSCH Support {type A, type B}, - Support SRS carrier switching / HetNet-oriented functions (i.e., UE functions #1 / #2).

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

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

[0199] Furthermore, at least one of the above-described embodiments may be applied when the UE configures / activates / triggers specific information related to the above-described embodiment (or performs the operations of the above-described embodiment) through higher layer signaling / physical layer signaling. For example, the specific information may be any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

[0200] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, the behavior of Rel. 15 / 16 / 17.

[0201] (Supplementary Notes) The following inventions are supplementary notes with respect to one embodiment of the present disclosure (options 1 to 3 of the first embodiment). [Supplementary Note 1] A terminal comprising: a receiver that receives downlink control information indicating a transmit power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) but is associated with a sounding reference signal (SRS); and a controller that controls the transmit power of the SRS based on the downlink control information. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the TPC command is indicated by a field other than a TPC command field for a PUSCH and a TPC command field for a physical uplink control channel (PUCCH). [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the controller determines that the downlink control information indicates the TPC command if a condition is satisfied. [Supplementary Note 4] The terminal according to any of Supplementary Notes 1 to 3, wherein the controller determines the one power control adjustment state from two power control adjustment states for the SRS.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0229] (Base Station) Fig. 8 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0246] The transceiver 120 may transmit downlink control information indicating a transmit power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) but is associated with a sounding reference signal (SRS). The controller 110 may control reception of the SRS based on the downlink control information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0265] The transceiver 220 may receive downlink control information indicating a transmit power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) but is associated with a sounding reference signal (SRS). The controller 210 may control the transmit power of the SRS based on the downlink control information.

[0266] The TPC command may be indicated by a field other than the TPC command field for PUSCH and the TPC command field for Physical Uplink Control Channel (PUCCH).

[0267] If the condition is met, the controller 210 may determine that the downlink control information indicates the TPC command.

[0268] The controller 210 may determine the one power control adjustment state from two power control adjustment states for the SRS.

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

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

[0271] For example, a base station, a user terminal, or the like 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. 10 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, and the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0331] 11 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0354] 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 ...." "does not expect ..." may be interchangeably read as "be not expected ...." 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" (e.g., if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

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

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

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

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

[0365] 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 downlink control information indicating a transmit power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) but is associated with a sounding reference signal (SRS); and a control unit that controls the transmit power of the SRS based on the downlink control information.

2. The terminal according to claim 1, wherein the TPC command is indicated by a field other than a TPC command field for a PUSCH and a TPC command field for a physical uplink control channel (PUCCH).

3. The terminal according to claim 1, wherein, if a condition is met, the control unit determines that the downlink control information indicates the TPC command.

4. The terminal according to claim 1, wherein the control unit determines the one power control adjustment state from two power control adjustment states for the SRS.

5. A wireless communication method for a terminal, comprising: receiving downlink control information indicating a transmit power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) but is associated with a sounding reference signal (SRS); and controlling the transmit power of the SRS based on the downlink control information.

6. A base station having: a transmitter that transmits downlink control information indicating a transmit power control (TPC) command for one power control adjustment state that is not associated with a physical uplink shared channel (PUSCH) but is associated with a sounding reference signal (SRS); and a controller that controls reception of the SRS based on the downlink control information.

Images