Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a radio resource control parameter for enabling at least one of a transmission power control (TPC) command instruction for a plurality of closed-loop power control (CL-PC) adjustment states for a sounding reference signal different from a physical uplink shared channel using a first downlink control information (DCI) format for a plurality of terminals, and the TPC command instruction using a second DCI format for each terminal; and a control unit that, on the basis of the RRC parameter, determines the application of at least one of a TPC command field included in the first DCI format and a TPC command field included in the second DCI format. According to this one aspect of the present disclosure, communications using a DL TRP and a UL TRP can be appropriately controlled.

Description

Terminal, wireless communication method, and base station

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) 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, the addition of UL receiving points in addition to general transmitting and receiving points is being considered to expand UL coverage. Furthermore, high-density UL deployments using DL transmitting points / macro base stations (BS) and UL receiving points / micro BS are being explored.

[0006] However, in cases where communication using DL TRP and UL TRP is performed, there are instances where the considerations are insufficient.

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

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

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a Radio Resource Control parameter that enables at least one of a plurality of transmit power control (TPC) command instructions for a plurality of closed-loop power control (CL-PC) adjustment states for a sounding reference signal separate from a physical uplink sharing channel, using a first downlink control information (DCI) format for a plurality of terminals, and the TPC command instructions using a second DCI format specific to each terminal; and a control unit that determines, based on the RRC parameter, the application of at least one of the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format.

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

[0011] Figure 1A shows an example of a typical transmission / reception point arrangement. Figure 1B shows an example of a UL high-density arrangement. Figure 2 shows an example of DL / UL coverage for a Heterogeneous Network (HetNet). Figure 3A shows an example of the association between RS index and PL value. Figure 3B shows an example of the association between RS index and delta PL value. Figure 4 shows an example of option 1 in a UL high-density arrangement. Figure 5 shows an example of option 2 in a UL high-density arrangement. Figure 6 is a conceptual diagram showing an example of an asymmetric DL sTRP / UL mTRP arrangement scenario. Figure 7 is a conceptual diagram showing an example of SRS transmission according to embodiment 1. Figure 8 shows an example of SRS settings according to embodiment 1. Figures 9A and 9B show examples of TPC command (DCI) fields. Figure 10 shows an example of a TPC command instruction according to the 0th embodiment. Figure 11 shows an example of a TPC command instruction according to the 1st embodiment. Figure 12 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 13 shows an example of the configuration of a base station according to one embodiment. Figure 14 shows an example of the configuration of a user terminal according to one embodiment. Figure 15 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 16 shows an example of a vehicle according to one embodiment.

[0012] (Scenario 1: UL high-density configuration (UL only TRP)) In Rel. 15 NR, the coverage (range) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is not uniform. PUSCH coverage is particularly limited at high frequencies. Future wireless communication systems (e.g., Rel. 18, Rel. 19, or later) are being considered to improve at least one of UL coverage and UL throughput.

[0013] To expand UL coverage, the addition of UL receiving points in addition to general transmit / receive points is being considered. Therefore, examples of general transmit / receive point arrangements and arrangements with UL receiving points (UL high-density arrangement) are described below.

[0014] FIG. 1A is a diagram showing an example of the arrangement of general transmission / reception points. In FIG. 1A, a UE receives a DL signal from a transmission / reception point (transmission / reception point (TRP)) and transmits a UL signal to the TRP. For example, when the UE and the TRP are far apart, the path loss is large, and there is a risk that the communication quality will deteriorate.

[0015] FIG. 1B is a diagram showing an example of UL high-density arrangement. In order to expand the UL coverage, in addition to the DL transmission points as shown in FIG. 1A, it is being considered to provide UL reception points as shown in FIG. 1B. In FIG. 1B, the UE receives a DL signal from a DL transmission point (TRP / central TRP / DL TRP / macro TRP) corresponding to a macro cell and transmits a UL signal to a UL reception point (for example, a reception point with less path loss / reception power). However, the UE may be able to perform UL transmission to the DL transmission point.

[0016] By using the UL high-density arrangement as shown in FIG. 1B, compared with the general arrangement as shown in FIG. 1A, the path loss can be reduced, the UL signaling quality can be improved, and by obtaining a higher coding rate, both the coverage and the UL data rate can be improved. In addition, since the UL reception point mainly performs reception, compared with the transmission / reception point corresponding to a general small cell, the necessary functions (such as a power amplifier, etc.) are reduced, the cost is reduced, and the deployment management becomes very easy.

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

[0018] In the example of FIG. 2, the UE is included in the optimal DL coverage of the macro BS and the optimal UL coverage of the micro BS. In this case, the UE can receive DL from the macro BS and transmit UL to the micro BS. However, the UE may transmit some reference signals / channels (e.g., the SRS whose usage is Antenna switching (AS) and is used for obtaining DL CSI) to the macro BS. Therefore, the UE may need two timing advances (Timing Advance (TA)) in this scenario. Note that the SRS of AS is for the macro BS to perform DL CSI measurement (e.g., determine the DL MIMO precoder) based on the reception of the SRS by using the channel reciprocity, so it is transmitted to the macro BS. On the other hand, the SRS whose usage is Codebook / Non-codebook is transmitted to the micro BS because it is used for the precoder / beam determination of PUSCH.

[0019] In a HetNet, if the micro BS has DL transmission capability, most of the time, turning off the DL can save the energy of the micro BS. In this case, the function of the micro BS is the same as that of a UL-only TRP (UL reception point).

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

[0021] The UE receives the received path loss (PL ｂ，ｆ，ｃ (q ｄ ), PL ｂ，ｆ，ｃ ), (index q ｄThe UL signal transmission power (e.g., the transmission power of PUSCH / PUCCH / SRS / PRACH) for a receiving point that does not transmit downlink data may be calculated using the active UL BWP (path loss for b) of the carrier f of serving cell c.

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

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

[0024] In options 1 and 2, the PL value / Delta PL value is q ｄ Notifications / settings may be made for each index of / SSB / CSI-RS / SRS Resource / SRS Resource Set. DL signaling may notify one or more RS indexes and the PL value / Delta PL value corresponding to each RS index. PL value / Delta PL value may be interpreted as PL parameter / Delta PL parameter.

[0025] Figure 3A shows an example of the association between an RS index and a PL value. Figure 3B shows an example of the association between an RS index and a delta PL value. The association (correspondence) between an RS index and a PL value / delta PL value is not limited to Figures 3A and 3B. For example, one RS index may correspond to multiple PL values / delta PL values. Note that a quantization table (range and step) for PL values / delta PL values ​​may be defined in advance in the specification. The notified PL values / delta PL values ​​may be quantized values ​​or indices of quantized values.

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

[0027] Figure 5 shows an example of Option 2 in a UL high-density configuration. When both the DL transmit point (macro TRP / gNB) and the UL receive point measure the same resource, the DL transmit point can recognize the difference between the PL between the DL transmit point and the UE and the PL between the UL receive point and the UE. In this case, the DL transmit point may notify the UE of this difference (relative PL / delta PL). The relative PL / delta PL may also be called the PL offset.

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

[0029] (Unified / Common TCI Framework) According to the Unified TCI Framework, multiple types of channels / RS (UL / DL) can be controlled by a common framework. The Unified TCI Framework does not define TCI states or spatial relationships for each channel, as in Rel. 15, but may specify a common beam (common TCI state) and apply it to all UL and DL channels, or a common beam for UL may be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

[0030] One common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (two common beams in total) are being considered.

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

[0032] The default beams for UL and DL may be aligned by beam management based on MAC CE (MAC CE level beam instruction). Alternatively, the default TCI status of PDSCH may be updated to match the default UL beam (spatial relationship).

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

[0034] A TCI pool (set) may be a set of multiple TCI states configured by the RRC parameter, or it may be a set of multiple TCI states (active TCI states, active TCI pool, set) activated by MAC CE from among the multiple TCI states configured by the RRC parameter. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be set as the QCL type A / D RS.

[0035] The number of TCI states corresponding to each of the one or more TRPs may be defined. For example, the number of TCI states applied to the UL channel / RS (UL TCI states) N (≧1) and the number of TCI states applied to the DL channel / RS (DL TCI states) M (≧1) may be defined. At least one of N and M may be notified / set / instructed to the UE via upper layer signaling / physical layer signaling.

[0036] The RRC parameter (information element) sets up multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the set up TCI states. DCI may indicate one of the activated TCI states. DCI may be a UL / DL DCI. The indicated TCI state may be applied to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both UL TCI and DL TCI.

[0037] In this example, one point may be a single TCI state that applies to both UL and DL, or it may be two TCI states that apply to UL and DL respectively.

[0038] At least one of the multiple TCI states set by the RRC parameters and the multiple TCI states activated by MAC CE may be called a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by MAC CE may be called an active TCI pool (active common TCI pool).

[0039] In this disclosure, the higher-layer parameters (RRC parameters) that set up multiple TCI states may also be referred to as setting information that sets up multiple TCI states, or simply as "setting information." Furthermore, in this disclosure, being instructed to select one of multiple TCI states using DCI may mean receiving instruction information that instructs one of the multiple TCI states included in DCI, or simply receiving "instruction information."

[0040] The RRC parameter sets up multiple TCI states (joint common TCI pools) for both DL and UL. MAC CE may activate multiple TCI states (active TCI pools) from among the set up TCI states. Separate active TCI pools for UL and DL may be set up / activated.

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

[0042] From Rel. 17 NR onward, MAC CE / DCI is expected to support beam activation / instruction to TCI states associated with different physical cell identifiers (PCIs). Furthermore, from Rel. 18 NR onward, MAC CE / DCI is expected to support instruction to change serving cells to cells with different PCIs.

[0043] [SRS to which the indicated TCI state in Rel. 17 applies] The indicated TCI state by MAC CE / DCI may apply to SRSs that satisfy the following conditions: The indicated TCI state applies to SRS resource sets for beam management applications (A-SRS) and codebook (CB) / non-codebook (NCB) / antenna switching applications (A / SP / P-SRS) if they are configured to follow a unified TCI state. For other SRSs, the configured TCI state within their SRS resource set applies.

[0044] [SRS to which the indicated TCI state in Rel. 18 applies] When single DCI multi-TRP is applied, the indicated TCI state may be applied to SRS that satisfy the following conditions. Note that applyIndicatedTCIState={1st,2nd,both} in the following description is a parameter that indicates that the first TCI state, the second TCI state, or both the first and second TCI states will be applied. • For SRS resource sets for A-SRS whose application is beam management and A / SP / P-SRS whose application is codebook (CB) / non-codebook (NCB) / antenna switching, if it is set to follow a unified TCI state, applyIndicatedTCIState={1st,2nd,both} is set for each SRS resource set to indicate that the indicated TCI state will be applied. For other SRS, the configured TCI state within that SRS resource set will be applied.

[0045] In this disclosure, the terms "indicator TCI state," "unified TCI state," "TCI state applied to a channel / signal configured to conform to a unified TCI state," "TCI state applied to UE individual PDSCH and CORESET / PDCCH associated with USS," and "TCI state applied to PUCCH and PUSCH" may be interpreted interchangeably.

[0046] (SRS Transmission Power Control) Using the index l of the power control adjustment state (power control adjustment state, closed-loop state), the SRS transmission power (P ＳＲＳ、ｂ，ｆ，ｃ (i, q ｓ , l)) of the SRS for the active UL BWP b of the carrier f of the serving cell c at the SRS transmission opportunity (transmission occasion) (also referred to as the transmission period, etc.) i is given by the following equation based on P ＣＭＡＸ，ｆ，ｃ (i), P Ｏ＿ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ), M ＳＲＳ，ｂ，ｆ，ｃ (i), α ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ), PL ｂ，ｆ，ｃ (q ｄ ), h ｂ，ｆ，ｃ (i, l).

[0047]

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

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

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

[0051] α ＳＲＳ，ｂ，ｆ，ｃ (q ｓ) is an active UL BWP b of the serving cell c and carrier f with subcarrier spacing μ, and an SRS resource set q ｓ This is provided by α (e.g., alpha) for , where α (e.g., alpha) may be defined as a path loss compensation coefficient for UL power control.

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

[0053] If the UE is not provided with pathlossReferenceRSs, or before the UE is provided with individual higher-layer parameters, the UE uses the RS resources obtained from the SS / PBCH block that the UE uses to obtain the MIB to perform PL ｂ，ｆ，ｃ (q ｄ ) calculate.

[0054] h ｂ，ｆ，ｃ (i, l) is the SRS power control adjustment state for the active UL BWP of the carrier f of serving cell c during an SRS transmission opportunity i. If the SRS power control adjustment state setting (e.g., srs-PowerControlAdjustmentStates) indicates the same power control adjustment state for SRS transmission and PUSCH transmission, then the current PUSCH power control adjustment state f is... ｂ，ｆ，ｃ(i, l). On the other hand, if the setting of the SRS power control adjustment state indicates an independent power control adjustment state for SRS transmission and PUSCH transmission, the SRS power control adjustment state h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ (m) may also be used as a basis.

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

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

[0057] Here, δ ＳＲＳ，ｂ，ｆ，ｃ (m) may be a TPC command value encoded in combination with other TPC commands within a PDCCH having DCI (e.g., DCI format 2_3). Σ m=0 C(Si)-1 δ SRS,b,f,c (m) is on the active UL BWP b of the serving cell c and carrier f with subcarrier spacing μ, SRS transmission opportunity i-i ０ K ＳＲＳ (i-i ０ )-1 symbol before and K of SRS transmission opportunity i ＳＲＳ (i) The cardinality C(S) that the UE receives between the symbol and the symbol. ｉ A set of TPC command values ​​S that have ) ｉ The sum of the TPC commands within may also be used. Here, i ０ is SRS transmission opportunity i-i ０ K ＳＲＳ (i-i ０ ) - 1 symbol before, SRS transmission opportunity i K ＳＲＳ (i) The smallest positive integer that is faster than the symbol before it.

[0058] If SRS transmission is aperiodic, K SRS(i) may be the number of symbols in the active UL BWP b of the 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 in the active UL BWP b of the carrier f of serving cell c, N symb slot The product of the minimum value of the k2 in the PUSCH Common Configuration Information (PUSCH-ConfigCommon) and K is equal to the product of the minimum value of the k2 and in the PUSCH Common Configuration Information (PUSCH-ConfigCommon). SRS,min It could also be the number of symbols.

[0059] (DCI Format 2_3) DCI Format 2_3 is used to send a group of TPC commands for SRS transmission by one or more UEs. An SRS request may also be sent along with the TPC commands.

[0060] The following information is transmitted in 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 the upper layer to the UE that sets up the block.

[0061] If the UE has set the upper layer parameter srs-TPC-PDCCH-Group=typeA for ULs that do not have PUCCH and PUSCH, or for ULs where SRS power control is not associated with PUSCH power control, the upper layer sets a block in the UE, and that block defines the following fields: • SRS request: 0 or 2 bits. If this field exists, it is interpreted according to a specific table. • TPC command number 1, TPC command number 2, ..., TPC command number N. Each TPC command applies to the respective UL carrier, provided by the upper layer parameter cc-IndexInOneCC-Set.

[0062] If the UE is configured with the upper layer parameter srs-TPC-PDCCH-Group=typeB for ULs without PUCCH and PUSCH, or for ULs where SRS power control is not associated with PUSCH power control, the upper layer configures the UE with one or more blocks, each block of which is applied to the UL carrier, and defines the following fields for each block: • SRS Request: 0 or 2 bits. If this field exists, it is interpreted according to a specific table. • TPC Command: 2 bits.

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

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

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

[0066] (2) The index of the serving cell from which the UE will interrupt transmission in order to send SRS in one or more other serving cells, as specified by the parameter srs-SwitchFromServCellIndex.

[0067] (3) An instruction by the parameter srs-SwitchFromCarrier for an uplink carrier on which the UE will interrupt transmission in order to transmit SRS on one or more other serving cells.

[0068] (4) DCI format 2_3 field setting type by type A or type B. In type A, the index of the serving cell set is provided by cc-SetIndex, the index of the serving cells within 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 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.

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

[0070] (6) An index for the position in DCI format 2_3 of the first bit of the field for the non-supplementary uplink carrier of the serving cell, according to startingBitOfFormat2-3.

[0071] (7) An index for the position in DCI Format 2_3 of the first bit of the field for the supplemental uplink carrier of the serving cell, according to startingBitOfFormat2-3SUL-v1530.

[0072] Note that in existing specifications (up to Rel. 18), startingBitOfFormat2-3 / startingBitOfFormat2-3SUL-v1530 is defined as an integer between 1 and 31.

[0073] (Two Closed Loop Power Control (CL-PC) adjustment states for PUSCH) The higher-level parameter for PUSCH power control (PUSCH-PowerControl) includes the size of twoPUSCH-PC-AdjustmentStates and sri-PUSCH-PowerControlId. The higher-level parameter for SRI-PUSCH power control (SRI-PUSCH-PowerControl) includes sri-PUSCH-PowerControlId and sri-PUSCH-ClosedLoopIndex. If twoPUSCH-PC-AdjustmentStates is set, the UE may set l = {0, 1} in sri-PUSCH-ClosedLoopIndex.

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

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

[0076] (CL-PC Adjustment State for SRS) The CL-PC adjustment state for SRS is defined according to at least one of the following cases 1 to 3: <Case 1> If srs-PowerControlAdjustmentStates = absent or sameAsFci2 (following the CL-PC adjustment state of PUSCH), the UE may apply the same CL-PC adjustment state as PUSCH. <Case 2> If srs-PowerControlAdjustmentStates = separateClosedLoop and tpc-Accumulation is not provided (SRS-specific CL-PC adjustment state is set and TPC accumulation is not set), the UE may determine / decide / apply the CL-PC adjustment state for SRS by considering (based on) the sum of TPC commands for SRS jointly coded by DCI format 2_3. <Case 3> If srs-PowerControlAdjustmentStates = separateClosedLoop and tpc-Accumulation is provided (i.e., SRS-specific CL-PC adjustment states are set and TPC accumulation is set), then a TPC command for the SRS jointly coded by DCI format 2_3 may be applied as the CL-PC adjustment state for the SRS.

[0077] Furthermore, regardless of the above cases, UE may apply a unique (different from PUSCH) CL-PC tuning state to SRS. Here, a new index k = {0, 1} may be introduced to indicate a CL-PC tuning state specific to SRS that is different from PUSCH.

[0078] In this disclosure, the values ​​of l and k may be set / instructed for each SRS resource set / SRS resource.

[0079] (Asymmetric DL sTRP / UL mTRP Placement Scenario) In this disclosure, when extending the asymmetric DL sTRP / UL mTRP placement scenario, the following may be assumed: - No changes to existing cell definitions. - No need for new cell definitions (e.g., UL-only cells). - Unified TCI framework (Rel. 17 / 18). - Use of existing QCL / UL space relationship provisions. - Targeting FR1 / FR2.

[0080] (Conceptual Scenarios) The following scenarios may be assumed in this disclosure: - A UE receives a DL signal (including, for example, PL-RS) from one DL TRP. - A UE transmits UL signals to multiple UL TRPs.

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

[0082] (Unified TCI Framework) In this disclosure (in the asymmetric DL sTRP / UL mTRP deployment scenario), the Unified TCI Framework for Rel. 17 / 18 may be supported. The supported scenarios (intra-cell / inter-cell) are exemplified below.

[0083] <In-cell scenarios> - A unified TCI for single TRP (Rel. 17) may be supported for only one UL TRP. - A unified TCI for single DCI multi-TRP (Rel. 18) may be supported for multiple UL TRPs. - A unified TCI for multi-DCI multi-TRP (Rel. 18) may not be supported.

[0084] <Inter-cell scenarios> - The unified TCI for single TRP (Rel. 17) may be supported in inter-cell scenarios (Inter cell beam management (ICBM) of Rel. 17). - The unified TCI for single DCI multi-TRP (Rel. 18) does not need to be supported. - The unified TCI for multi-DCI multi-TRP (Rel. 18) may be supported for inter-cell multi-TRP of Rel. 17.

[0085] (DCI Format 2_3) As mentioned above, DCI Format 2_3 may be used only for SRS carrier switching. For example, DCI Format 2_3 may be used under the following conditions:

[0086] <Condition 1> The UE is set to the upper layer parameter srs-TPC-PDCCH-Group=typeA for ULs that do not have PUCCH and PUSCH, or for ULs where SRS power control is not associated with PUSCH power control. <Condition 2> The UE is set to the upper layer parameter srs-TPC-PDCCH-Group=typeB for ULs that do not have PUCCH and PUSCH, or for ULs where SRS power control is not associated with PUSCH power control.

[0087] Alternatively, <Condition A> Carrier switching without PUCCH / PUSCH on the carrier. <Condition B> Carrier switching with a power control adjustment state set that is different from PUSCH (independent / individual) for the SRS.

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

[0089] (SRS-specific closed-loop power control (CL-PC) adjustment state) <<Aspect 0>> In the specification of Rel. 18, when srs-PowerControlAdjustmentStates = separateClosedLoop is set, there is only one closed-loop power control (CL-PC) adjustment state for the SRS, separate from PUSCH. This CL-PC adjustment state can be controlled by DCI format 2_3.

[0090] UE may be configured with one or more (two) CL-PC adjustment states for SRS. One or more (two) CL-PC adjustment states may be configured separately from PUSCH.

[0091] The upper-layer parameter srs-PowerControlAdjustmentStates indicates whether twoPUSCH-PC-AdjustmentStates (one / two push power control adjustment states) or another closed-loop power control adjustment state is set for the SRS. This upper-layer parameter may only be applied to ULs that the UE also transmits pushes for. If this upper-layer parameter is absent / released, the UE may apply the value of sameAs-Fci1.

[0092] In other words, the upper-layer parameter srs-PowerControlAdjustmentStates may indicate which CL-PC adjustment state to follow when the SRS follows the CL-PC adjustment state of the PUSCH, and there are two CL-PC adjustment states for the PUSCH.

[0093] For example, if srs-PowerControlAdjustmentStates = absent, the SRS follows the CL-PC adjustment state (Fci1) of one PUSCH; if srs-PowerControlAdjustmentStates = sameAsFci2, the SRS follows the CL-PC adjustment state (Fci2) of the other PUSCH; if srs-PowerControlAdjustmentStates = separateClosedLoop, the SRS follows its own (unique) CL-PC adjustment state.

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

[0095] Regardless of the settings related to PUSCH and the settings for SRS carrier switching, UE can be configured with multiple (two) CL-PC adjustment states separate from PUSCH.

[0096] Figure 7 is a conceptual diagram showing an example of SRS transmission according to Embodiment 1. As shown in Figure 7, the UE can set the same (two) CL-PC adjustment states (l=0,1) as PUSCH#1 / #2 for SRS#1 / #2, and a different (two) CL-PC adjustment states (k=0,1) from PUSCH#1 / #2.

[0097] Specifically, UE may apply the same CL-PC adjustment state (l=0) as PUSCH#1 to UL TRP#1 and transmit SRS#1.

[0098] UE may send SRS#2 to UL TRP#2 with the same CL-PC adjustment state (l=1) as PUSCH#2.

[0099] The UE may also transmit SRS#3 to DL TRP by applying a first CL-PC adjustment state (k=0) that is different from (independent of) PUSCH. The UE may then transmit the UL (SRS#3) to obtain DL CSI.

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

[0101] In the transmission of SRS#4, any direction may mean a predetermined angular range (for example, 180 degrees or 360 degrees) in which a certain TRP is assumed to exist. The UE may transmit multiple beams for BM in that any direction. The SRS for BM may be used for SRS-based beam sweeping.

[0102] Thus, the UE may set multiple (two) CL-PC adjustment states (l=0,1) for SRS (#1 to #2) as in PUSCH, and set a different CL-PC adjustment state (k=0,1) for SRS (#3 to #4) than that of PUSCH.

[0103] A new higher-level parameter may be introduced for SRS to enable a CL-PC adjustment state separate from PUSCH.

[0104] Figure 8 shows an example of SRS settings according to Embodiment 1. As shown in Figure 8, SRS resource set #1 (for example, use is CB) corresponds to SRS resource #1, and the power control adjustment state may be set to, for example, Fci1 (srs-PowerControlAdjustmentStates = absent). SRS resource set #2 (for example, use is CB) corresponds to SRS resource #2, and the power control adjustment state may be set to, for example, Fci2 (srs-PowerControlAdjustmentStates = sameAsFci2). SRS resource set #3 (for example, use is AS) corresponds to SRS resource #3, and the power control adjustment state may be set to, for example, the first CL-PC (srs-PowerControlAdjustmentStates = separateClosedLoop). SRS resource set #4 corresponds to SRS resource #4 (for example, with the application beam management (BM)), and the power control adjustment state may be set to, for example, a second CL-PC (srs-PowerControlAdjustmentStates = separateClosedLoop).

[0105] According to embodiments 0 to 1 described above, a UE may set up one or more (two) SRS resource sets having the same CL-PC adjustment state as PUSCH, and one or more (two) SRS resource sets having a different CL-PC adjustment state from PUSCH, within a certain CC.

[0106] These settings may be supported for each SRS resource set / SRS resource. Furthermore, these settings may be supported regardless of whether the corresponding CC / BWP is configured for PUSCH or SRS antenna switching.

[0107] As mentioned above, a separate SRS-specific CL-PC adjustment state (an additional CL-PC adjustment state) from that of PUSCH may be introduced (for example, k = 0, 1).

[0108] In the new upper-level parameters, srs-TPC-PDCCH-Group = {typeA, typeB} may be supported.

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

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

[0111] Figures 9A and 9B show examples of TPC command (DCI) fields. Figure 9A corresponds to the case srs-TPC-PDCCH-Group = typeA, and Figure 9B corresponds to srs-TPC-PDCCH-Group = typeB. Note that the order of the fields in the TPC command in this disclosure is merely an example and can be changed as appropriate. The same applies to the TPC commands in the other figures below.

[0112] As shown in Figure 9A, the group-common DCI may include instructions for TPC commands for multiple CCs after the SRS request field. In other words, the group-common DCI may include TPC commands for each CC. The setting order of the TPC command fields may be set in ascending (or descending) order of cells (CCs), and if the cells are the same, in ascending (or descending) order of CL-PC adjustment status (e.g., TPC command 1 for {1st CL-PC, CC#1}, TPC command 2 for {2nd CL-PC, CC#1}, ..., TPC command 1 for {1st CL-PC, CC#X}, TPC command 2 for {2nd CL-PC, CC#1}).

[0113] As shown in Figure 9B, the TPC command field for a given CC (cell) may consist of one field (as existing) to indicate a TPC command for any of the TRPs. In this case, an X bit may be added to indicate which TRP the TPC command is associated with (a CL-PC tuning state other than PUSCH). For example, if there are two CL-PC tuning states other than PUSCH, X = 1.

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

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

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

[0117] (Alt2-2) It may be implicitly indicated using an existing bit field (e.g., SRS request field) that either of the first or second CL-PC adjustment states, separate from PUSCH, is associated with the TPC command.

[0118] According to this embodiment, the UE can control SRS transmission by applying the same CL-PC adjustment state as PUSCH, or a different SRS-specific CL-PC adjustment state from PUSCH, regardless of the SRS carrier switching settings.

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

[0120] Option 1: The CL-PC adjustment state for SRS is associated with the SRS resource set. Option 2: If the upper layer parameter srs-PowerControlAdjustmentStates is set to separateClosedLoop, the closedLoopIndex-r17 in the TCI state indicates one CL-PC adjustment state for SRS. Option 3: Add a parameter to P0AlphaSet-r17 in the TCI state that indicates one of the two CL-PC adjustment states for SRS. Option 4: The CL-PC adjustment state for SRS is associated with the use [type] of the SRS resource.

[0121] <<Aspect 3>> (Two CL-PC adjustment states [SRS specific] separate from PUSCH) The UE may support functions for two CL-PC adjustment states [SRS specific] separate from PUSCH, as functions independent of SRS carrier switching. These functions may be applied regardless of the PUSCH / SRS carrier switching settings in the CC.

[0122] (Extension of DCI Format 2_3) Assuming that existing SRS carrier switching functions cannot be configured simultaneously within the same CC (simultaneous configuration is not supported), both srs-TPC-PDCCH-Group = typeA and typeB may be supported.

[0123] (Introduction of additional TPC commands) For each CC having two CL-PC adjustment states for SRS, one additional TPC command may be introduced.

[0124] For example, in the case of Type B, one DCI can indicate two TPC commands simultaneously. In this case, only one bit is needed compared to a one-bit closed-loop-indicator field.

[0125] On the other hand, in the case of type A, N bits are added compared to the 1-bit closed-loop-indicator field corresponding to N CCs.

[0126] The two (first / second) CL-PC adjustment states for SRS may be associated with the SRS resource set.

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

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

[0129] (Analysis) As mentioned above, in order to expand UL coverage, the establishment of UL receiving points in addition to general transmitting and receiving points is being considered. Furthermore, UL high-density deployment / heterogeneous network (HetNet) using DL transmitting points (TRP) / macro base stations (BS) and UL receiving points (TRP) / micro BS is being considered.

[0130] It is being considered that two DCI formats (DCI formats 1_1 and 2_3) will be used to instruct the two CL-PC adjustment status TPC commands for SRS, separate from PUSCH.

[0131] However, there are cases where the use of these DCI formats has not been adequately considered. For example, it has not been sufficiently considered whether both of these DCI formats can simultaneously issue two TPC commands for CL-PC adjustment states for SSRS.

[0132] If these considerations are insufficient, it may not be possible to properly implement the UL high-density arrangement described above, potentially hindering throughput improvements.

[0133] Therefore, the inventors of this invention conceived a way to solve these problems.

[0134] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0135] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0136] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0137] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0138] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0139] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0140] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0141] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0142] In this disclosure, terms such as drop, suspend, cancel, puncture, rate match, postpone, and not send may be interpreted interchangeably.

[0143] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, 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 relationship group, Code Division Multiplexing (CDM) group, Reference Signal group, CORESET group, Physical Uplink Control The following terms may be interchangeable: 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.

[0144] In this disclosure, the following can be interpreted interchangeably: single TRP, channel / signal using a single TRP, channel using one TCI state / spatial relationship, multi-TRP not being activated by RRC / DCI, multiple TCI states / spatial relationships not being activated by RRC / DCI, no CORESET pool index value being set for any CORESET, and no code point in a TCI field being mapped to two TCI states.

[0145] In this disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI state / spatial relationships, multi-TRP being activated by RRC / DCI, multiple TCI state / spatial relationships being activated by RRC / DCI, and at least one of a single DCI-based multi-TRP and a multi-DCI-based multi-TRP may be interpreted as mutually exclusive.

[0146] In this disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI code point may be interpreted as mutually exclusive.

[0147] In this disclosure, the terms "multi-DCI (mDCI)," "multi-PDCCH," "multi-TRP system based on multi-DCI," "mDCI-based MTRP," "two CORESET pool indexes," or "CORESET pool index = 1 (or one or more values)" may be interpreted interchangeably.

[0148] In this disclosure, cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band may be interpreted interchangeably. In this disclosure, cell, PCI, cell with additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the current serving cell's PCI, another serving cell, target cell, adjacent cell, and inter-RAT adjacent cell may be interpreted interchangeably. A target cell may be a cell selected from among several candidate cells. In this disclosure, switch, change, and update may be interpreted interchangeably. A serving cell may be interpreted as a serving cell before a switch or a serving cell after a switch.

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

[0150] In this disclosure, base station, TRP, UL receiving point, UL TRP, UL only TRP, microcell, microBS, and microTRP may be interpreted as interchangeable. A UL receiving point primarily performs UL receiving. A UL receiving point may perform UL receiving only, or it may perform UL receiving and DL transmission.

[0151] In this disclosure, base station, TRP, DL transmission point, DL TRP, DL only TRP, UL / DL TRP, macrocell, macro BS, macro TRP, and central TRP may be interpreted interchangeably. A DL transmission point primarily performs DL transmission. A DL transmission point may perform DL transmission only, or it may perform UL reception and DL transmission.

[0152] In this disclosure, UL high-density arrangement, distributed TRP mode, separated location mode for transmit / receive points, distributed transmit / receive mode, separated TRP mode, TRP type 1, TRP type 2, TRP type A, and TRP type B may be interpreted as interchangeable.

[0153] This disclosure may assume a single TRP, a multi-DCI multi-TRP, a single DCI multi-TRP, or at least one of Scenario 1 or Scenario 2 described above.

[0154] In this disclosure, "to be set" and "to receive a setting (setting information)" may be interpreted interchangeably.

[0155] In this disclosure, TCI, TCI status, TCI status ID, TCI status list / set / pool / group, and TCI status list / set / pool / group ID may be interpreted as interchangeable.

[0156] In this disclosure, a set of TCI states (separate TCI states) may mean a set of UL TCI states and DL TCI states. A TCI state may mean a TCI-state information element which is an RRC information element.

[0157] In this disclosure, the terms "indicated TCI state," "unified TCI state," "unified TCI state in which multi-TRP is not set / used / applied," "unified TCI state as defined in Rel. 17," "Rel. 17 unified TCI state," and "first unified TCI state" may be interpreted interchangeably.

[0158] In this disclosure, the terms "indicating TCI state," "unified TCI state," "unified TCI state to which a multi-TRP is set / used / applied," "unified TCI state to which a multi-TRP may be set / used / applied," "indicating TCI state to which a multi-TRP is set / used / applied," "indicating TCI state to which a multi-TRP may be set / used / applied," "unified TCI state as defined in Rel. 18," "Rel. 18 unified TCI state," "unified TCI state for multi-TRP," and "second unified TCI state" may be interpreted interchangeably.

[0159] In this disclosure, the terms DCI-indicated TCI state, indicated TCI state, unified TCI state, TCI state applicable to multiple types of channels / signals, joint TCI state (for DL ​​and UL), DL TCI state, UL TCI state, Rel. 17 TCI state, common TCI state, single unified TCI state to be set, and single unified TCI state to be activated may be interpreted as one another.

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

[0161] The unified / common TCI state may also mean the indicated TCI state indicated using DCI / MAC CE / RRC (Rel. 17).

[0162] The indicated TCI state may be shared with at least one of the following: UE-specific receptions in PDSCH / PDCCH (updated using DCI / MAC CE / RRC of Rel. 17), dynamic grant (DCI) / configured grant PUCCH, and multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI / MAC CE / RRC may be called the indicated TCI state.

[0163] If an indicative TCI state is supported (in Rel. 17), a TCI state other than a unified TCI state may mean a TCI state set using MAC CE / RRC (in Rel. 17) (a set TCI state).

[0164] The configured TCI state does not have to be shared with at least one of the following: UE-specific reception in PDSCH / PDCCH (updated using DCI / MAC CE / RRC of Rel. 17), dynamic grant (DCI) / configured grant PUCCH, and multiple (e.g., all) dedicated PUCCH resources. The configured TCI state may be set in RRC / MAC CE for each CORESET / resource / resource set, and the configured TCI state may not be updated even if the instructed TCI state described above is updated.

[0165] In this disclosure, a first TRP may correspond to a first TCI state. In this disclosure, a second TRP may correspond to a second TCI state. In this disclosure, an nth TRP may correspond to an nth TCI state.

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

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

[0168] In this disclosure, path loss reference RS, path loss reference RS for PUSCH, path loss reference RS for PUCCH, path loss reference RS for SRS, SSB, CSI-RS, and RS may be interpreted interchangeably. In this disclosure, path loss (PL), path loss value, and path loss parameter may be interpreted interchangeably.

[0169] In this disclosure, base station, UL receiving point, UL TRP, UL only TRP, and microBS may be interpreted interchangeably. A UL receiving point may only perform UL receiving, or may perform DL transmission if certain conditions are met.

[0170] In this disclosure, base station, DL transmission point, DL TRP, DL only TRP, macro BS, and central TRP may be interpreted as interchangeable. A DL transmission point may perform DL transmission only, or UL reception if certain conditions are met.

[0171] DL sTRP / UL mTRP may mean, for example, a scenario applied in Rel. 19. DL sTRP / UL mTRP may also mean, for example, Scenario 1 (Figure 1B) or Scenario 2 (Figure 2) above. Asymmetric DL sTRP / UL mTRP, DL sTRP / UL mTRP, and [Asymmetric] HetNet may be interpreted as mutually exclusive.

[0172] In this disclosure, "resource set" and "resource" may be interpreted interchangeably.

[0173] In this disclosure, SRS[#X], SRS Resource Set[#X], and SRS Resource[#X] may be interpreted interchangeably.

[0174] In this disclosure, CC and BWP may be interpreted interchangeably.

[0175] In this disclosure, the two CL-PC settings other than PUSCH, the two CL-PC settings specific to (dedicated to) SRS, and the two CL-PC settings for SRS for Rel. 19 may be interpreted interchangeably.

[0176] In this disclosure, there may be one serving cell or multiple serving cells.

[0177] In this disclosure, the terms [A-] Available Slot Offset Settings / List for SRS, Available Slot Offset Settings / List, [A-] Available Slot Offset Settings / List for SRS, Available Slot Offset Settings / List, and availableSlotOffsetList, AvailableSlotOffset, etc. may be interpreted interchangeably.

[0178] In this disclosure, DCI format 2_3, DCI format for multiple UEs, DCI format for TPC command [group] instruction for multiple UEs, and the first DCI format (for multiple UEs) may be interpreted as interchangeable.

[0179] In this disclosure, DCI format 1_1, UE-specific DCI format, DCI format for PUSCH scheduling, DCI format including TPC command fields for PUSCH, and the (UE-specific) second DCI format may be interpreted as interchangeable.

[0180] In this disclosure, count, application, accumulation, etc., may be interpreted interchangeably.

[0181] (Wireless communication method) The UE may apply the present disclosure to perform control of UL transmission (SRS power control). The NW / BS / gNB may provide / transmit to the UE settings / instructions, etc., for the UE to implement such control. The NW / BS / gNB may also perform various controls to receive UL transmissions from terminals to which each embodiment is applied.

[0182] In this disclosure, CL-PC indicator, CL-PC index, indicator / index for CL-PC [adjusted state], closed-loop indicator, etc. may be interpreted interchangeably.

[0183] The following description primarily uses DCI (e.g., DCI format 2_3) for instructing / transmitting TPC commands [groups] for SRS transmission as an example, but the applicable DCI formats are not limited to this. In this disclosure, DCI formats 2_3 / 1_1 / 1_2 may be interpreted as any DCI format (e.g., DCI format X_Y).

[0184] In this disclosure, the new upper layer / RRC parameter may have a name other than those shown below.

[0185] In the embodiments described below, examples are shown in which a specific release number (e.g., "-rXX", where XX is, for example, 19) is assigned to the RRC parameter, but this is merely an example. The RRC parameter in each embodiment may or may not be assigned such a release number, or may be assigned a different release number.

[0186] In this disclosure, each embodiment / option may be applied individually or in combination with others.

[0187] <Embodiment 0> Embodiment 0 relates to setting / instruction using RRC parameters.

[0188] The UE may receive RRC parameters that enable specific features / functions.

[0189] The specific feature / function may be at least one of the following: Feature 1: Instructions for TPC commands for CL-PC control states for multiple (e.g., two) SRSs, separate from PUSCH, using a first DCI format (e.g., DCI format 2_3). Feature 2: Instructions for TPC commands for CL-PC control states for multiple (e.g., two) SRSs, separate from PUSCH, using a second DCI format (e.g., DCI format 1_1).

[0190] When Feature 1 is enabled / configured, a CL-PC ID (which may be 1 bit) may be added to the first DCI format (e.g., DCI format 2_3) to indicate which CL-PC adjustment state corresponds to the TPC command field (for an SRS other than PUSCH).

[0191] When Feature 2 is enabled / configured, a second DCI format (e.g., DCI format 1_1) may include a second TPC command field (which may be 2 bits) (for an SRS other than PUSCH) and a CL-PC ID (which may be 1 bit) indicating which CL-PC adjustment state the second TPC command field corresponds to.

[0192] Furthermore, the specific feature / function may be at least one of the following: • Feature 1-1: Instructions for TPC commands for CL-PC control states for multiple (e.g., two) SRSs, separate from PUSCH, using a first DCI format (e.g., DCI format 2_3). • Feature 1-2: Instructions for TPC commands for CL-PC control states for one SRS, separate from PUSCH, using a first DCI format (e.g., DCI format 2_3). • Feature 2-1: Instructions for TPC commands for CL-PC control states for multiple (e.g., two) SRSs, separate from PUSCH, using a second DCI format (e.g., DCI format 1_1). • Feature 2-2: Instructions for TPC commands for CL-PC control states for one SRS, separate from PUSCH, using a second DCI format (e.g., DCI format 1_1).

[0193] When Feature 1-1 is enabled / configured, a CL-PC ID (which may be 1 bit) may be added to the first DCI format (e.g., DCI format 2_3) to indicate which CL-PC adjustment state corresponds to the TPC command field (for an SRS other than PUSCH).

[0194] When features 1-2 are enabled / configured, the first DCI format (e.g., DCI format 2_3) may or may not include a CL-PC ID (which may be 1 bit) indicating which CL-PC adjustment state the TPC command field (for an SRS other than PUSCH) corresponds to. If a CL-PC ID is included, the UE may assume its value is a specific value (e.g., 0).

[0195] When Feature 2-1 is enabled / configured, a second DCI format (e.g., DCI format 1_1) may include a second TPC command field (which may be 2 bits) (for an SRS other than PUSCH) and a CL-PC ID (which may be 1 bit) indicating which CL-PC adjustment state the second TPC command field corresponds to.

[0196] When Feature 2-2 is enabled / configured, the second DCI format (e.g., DCI format 1_1) may be further modified by adding only a second TPC command field (which may be 2 bits) (for a different SRS than PUSCH), or by adding the second TPC command field and a CL-PC ID (which may be 1 bit) indicating which CL-PC adjustment state the second TPC command field corresponds to. If a CL-PC ID is added, the UE may assume its value is a specific value (e.g., 0).

[0197] The RRC parameter may be defined / introduced as two RRC parameters, for example, an RRC parameter that enables feature 1 (or feature 1-1 or feature 1-2) and an RRC parameter that enables feature 2 (or feature 2-1 or feature 2-2) (Option 0-1).

[0198] In options 0-1, each RRC parameter may individually enable a new DCI field in the first / second DCI format for instructing TPC commands for CL-PC control states for one or more (e.g., two) SRSs, separate from PUSCH.

[0199] Furthermore, the RRC parameter may be defined / introduced as a single RRC parameter that enables, for example, Feature 1 (or Feature 1-1 or Feature 1-2) and Feature 2 (or Feature 2-1 or Feature 2-2) (Option 0-2).

[0200] In option 0-2, the single RRC parameter may enable a [new] DCI field in the first / second DCI format for instructing TPC commands for CL-PC control states for multiple (e.g., two) or one SRS, separate from PUSCH.

[0201] Activation of options 0-1 / 0-2 via RRC parameters may be set for each BWP / CC.

[0202] (For example, in option 0-1,) restrictions on the setting between feature 1 and feature 2 may be specified / introduced in the specification.

[0203] For example, Feature 1 may be set / enabled only if Feature 2 is enabled / configured in the same BWP / CC.

[0204] Furthermore, for example, feature 2 may be set / enabled only if feature 1 is enabled / configured in the same BWP / CC.

[0205] Furthermore, for example, UE does not need to assume that both Feature 1 and Feature 2 are set / enabled in the same BWP / CC.

[0206] If features 1 / 1-1 / 1-2 / 2 / 2-1 / 2-2 are supported / configured in multiple BWP / CCs, the UE does not need to assume that different features will be configured for each cell group (master cell group / secondary cell group) or for each UE.

[0207] Both Feature 1 and Feature 2 may be set in a BWP / CC. In this case, the UE may determine / control the accumulation of TPC commands indicated by the first DCI format and the second DCI format.

[0208] For example, the UE may count TPC commands from a first DCI format and a second DCI format, and update one of several CL-PC adjustment states for an SRS other than PUSCH.

[0209] Figure 10 shows an example of a TPC command instruction according to the first embodiment. In the example shown in Figure 10, both Feature 1 and Feature 2 for a given BWP / CC are enabled for the UE. In this case, the first DCI format (e.g., DCI format 2_3) is amended with a CL-PC ID (e.g., h1 or h2) indicating which CL-PC adjustment state the TPC command field included in the DCI format corresponds to, and the second DCI format (e.g., DCI format 1_1) is amended with a second TPC command field and a CL-PC ID (e.g., h1 or h2) indicating which CL-PC adjustment state the second TPC command field corresponds to, in addition to the existing TPC command field.

[0210] The UE determines the cumulative TPC commands for the SRS based on the CL-PC ID and TPC command field included in each DCI format, and then determines the transmit power of the SRS.

[0211] According to the first embodiment described above, it is possible to appropriately instruct TPC commands for an SRS separate from PUSCH, using the first / second DCI format.

[0212] <First Embodiment> In the first embodiment, the operation in the case where the reception of the first DCI format and the reception of the second DCI format overlap in time will be described.

[0213] Both Feature 1 and Feature 2 may be set in a BWP / CC. In this case, the UE may determine / control the accumulation of TPC commands indicated by the first DCI format and the second DCI format.

[0214] Two DCIs (a first DCI format and a second DCI format) that instruct multiple (e.g., two) CL-PC adjustment states for the SRS, separate from PUSCH, may be transmitted / received on the same / overlapping time resource (e.g., symbol / slot) (hereinafter referred to as Case 1).

[0215] In this disclosure, "two DCIs transmitted in the same time resource" may mean that two DCIs (or PDCCHs transmitting two DCIs) are transmitted in exactly the same time domain (symbol / slot) (i.e., they completely overlap).

[0216] In this disclosure, "two DCIs transmitted in overlapping time resources" may mean that at least a portion of the two DCIs (or the PDCCHs transmitting the two DCIs) are transmitted in the same time domain (symbol / slot) (i.e., partially overlapping).

[0217] In Case 1, the UE may count (or ignore) at least one of the TPC command instructions in the first DCI format and the TPC command instructions in the second DCI format.

[0218] For example, in Case 1, the UE may count both the TPC command instruction in the first DCI format and the TPC command instruction in the second DCI format.

[0219] Figure 11 shows an example of a TPC command instruction according to the first embodiment. In the example shown in Figure 11, the UE counts both the TPC command instruction in the first DCI format (DCI format 2_3) and the TPC command instruction in the second DCI format (DCI format 1_1) in the case of Case 1.

[0220] Furthermore, for example, in Case 1, the UE may count either the TPC command instruction in the first DCI format or the TPC command instruction in the second DCI format, and ignore the other.

[0221] For example, the UE may count TPC command instructions in the first DCI format (or the second DCI format) and ignore TPC command instructions in the second DCI format (or the first DCI format).

[0222] Alternatively, for example, the UE does not have to assume or expect that two DCIs (a first DCI format and a second DCI format) instructing multiple (e.g., two) TPC commands for SRS-related CL-PC adjustment states, separate from PUSCH, will be transmitted / received in the same / overlapping time resources (e.g., symbols / slots) (i.e., Case 1 will occur).

[0223] Alternatively, for example, the UE may determine whether to count or ignore a TPC command based on the CL-PC adjustment status (ID) corresponding to the two DCI format TPC commands that fall under Case 1.

[0224] For example, if the CL-PC adjustment status (ID) corresponding to two DCI format TPC commands in Case 1 is the same, the UE may count one TPC command and ignore the other. For example, if the CL-PC adjustment status (ID) corresponding to two DCI format TPC commands in Case 1 is different, the UE may count / apply both TPC commands.

[0225] Alternatively, for example, the UE does not need to anticipate receiving multiple TPC command instructions corresponding to different CL-PC adjustment states (IDs) within the same / overlapping time resources.

[0226] According to the first embodiment described above, even in cases where the reception of the first DCI format and the reception of the second DCI format overlap in time, TPC commands can be applied appropriately.

[0227] <Second Embodiment> The second embodiment relates to UE capability.

[0228] For example, a UE may transmit UE capability information indicating support for feature 1 (or feature 1-1 / 1-2) / feature 2 (or feature 2-1 / 2-2).

[0229] The UE capability information may be defined / implemented as two (or four) pieces of UE capability information, for example, UE capability information indicating support for feature 1 (or feature 1-1 / 1-2), and UE capability information indicating support for feature 2 (or feature 2-1 / 2-2) (Option 2-1).

[0230] In Option 2-1, each UE capability information may be used to report [individually] that it supports a [new] DCI field in a first / second DCI format for instructing TPC commands for CL-PC control states for multiple (e.g., two) or one SRS, separate from PUSCH.

[0231] In Option 2-1, a UE capability that supports Feature 1 (or Feature 1-1) may also include supporting Feature 1-2. Conversely, a UE capability that supports Feature 1-2 does not necessarily have to include supporting Feature 1 (or Feature 1-1).

[0232] In Option 2-1, a UE capability that supports Feature 2 (or Feature 2-1) may also include supporting Feature 2-2. Conversely, a UE capability that supports Feature 2-2 does not necessarily have to include supporting Feature 2 (or Feature 2-1).

[0233] Furthermore, the UE capability information may be defined / implemented as a single UE capability information indicating, for example, support for Feature 1 (or Feature 1-1 or Feature 1-2) and Feature 2 (or Feature 2-1 or Feature 2-2) (Option 2-2).

[0234] In Option 2-2, the single UE capability information may be used to report that it supports a [new] DCI field in a first / second DCI format for instructing TPC commands for CL-PC control states for multiple (e.g., two) or one SRS, separate from PUSCH.

[0235] Support from UE capability information related to Option 2-1 / 2-2 may be reported per band / per band combination / per band within a band combination / per UE.

[0236] (For example, in Option 2-1,) support for Feature 1 (or Feature 1-1 / 1-2) may be a prerequisite for support for Feature 2 (or Feature 2-1 / 2-2). In other words, support for Feature 1 (or Feature 1-1 / 1-2) may be required for support for Feature 2 (or Feature 2-1 / 2-2). This is because, in existing specifications (up to Rel. 18), TPC command instructions for SRS other than PUSCH are only possible in the first DCI format.

[0237] Furthermore, (for example, in Option 2-1,) support for Feature 2 (or Feature 2-1 / 2-2) may be a prerequisite for support for Feature 1 (or Feature 1-1 / 1-2). In other words, support for Feature 2 (or Feature 2-1 / 2-2) may be required for support for Feature 1 (or Feature 1-1 / 1-2). This is because, in the existing specifications (up to Rel. 18), all NR-compliant UEs support the second DCI format.

[0238] (For example, in Option 2-1,) support for Feature 1 (or Feature 1-1 / 1-2) and support for Feature 2 (or Feature 2-1 / 2-2) may be reported independently.

[0239] According to the second embodiment described above, the UE capabilities corresponding to each feature can be appropriately defined, and appropriate communication operations can be carried out.

[0240] <Variations> In each embodiment of this disclosure, "CL-PC control states for multiple (e.g., two) SRSs" may be read as "CL-PC control states for one SRS" or "CL-PC control states for one or more (e.g., two) SRSs."

[0241] When a TPC command for a CL-PC control state for a separate SRS from PUSCH is instructed using DCI format 1_1, the DCI format does not need to include a 1-bit field indicating the CL-PC ID (which indicates which CL-PC adjustment state the second TPC command field corresponds to).

[0242] Furthermore, even when a TPC command for a CL-PC control state for a separate SRS from PUSCH is instructed using DCI format 1_1, the DCI format may include a 1-bit field indicating a CL-PC ID (which indicates which CL-PC adjustment state the second TPC command field corresponds to).

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

[0244] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0245] If the above 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 the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0246] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0247] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting 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), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0248] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0249] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0250] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0251] <<Regarding the Application of Each Embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set. - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter. - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS. - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported. - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0252] The above specific UE capabilities may indicate at least one of the following: • Supporting the above specific processing / operation / control / assumption / information; • Supporting a single DCI multi-TRP scenario; • Supporting Scenario 1 (UL high density arrangement); • Supporting Scenario 2 (HetNet); • Supporting UL transmission to UL receiving points (SRS / PUSCH / PUCCH / PRACH); • The number of UL receiving points / DL transmitting points to support; • Supporting the same / different CL-PC tuning state as PUSCH; • Supporting simultaneous setting of the same / different CL-PC tuning state as PUSCH; • Supporting DCI format 2_3 for specifying a first / second TPC command for a given CC; • Supporting srs-TPC-PDCCH-Group = {typeA, typeB} for a CL-PC tuning state different from PUSCH. - Support for SRS carrier switching / HetNet functions (i.e., UE functions #1 / #2). - Support for simultaneous configuration of UE functions #1 / #2. - Support for first / second DCI formats to specify TPC commands for two CL-PC adjustment states for SRS. - Support for Feature 1 (Feature 1-1 / 1-2) / Feature 2 (Feature 2-1 / 2-2).

[0253] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0254] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

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

[0256] Information on whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: • The information is set by one or more higher-layer parameters / RRC IEs. • The information is determined by one or more relevant higher-layer parameters / RRC IEs. • The information is indicated by MAC CE / DCI. • The information is based on one or more UE capabilities. • The information is described / defined in the specification. • The information is based on conditions described / defined in the specification. • The information is determined by a combination of several of the above. For example, the information is determined by the setting / indication of higher-layer parameters / MAC CE / DCIs and reported by UE capabilities.

[0257] The above multiple embodiments / options / choices may be combined into a single embodiment / option / choice.

[0258] In the embodiments described above, the measured RS may be a QCL source RS in an active TCI state / indicated / unified TCI state.

[0259] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having a receiving unit that receives a Radio Resource Control parameter that enables at least one of a plurality of transmit power control (TPC) command instructions for a plurality of closed-loop power control (CL-PC) adjustment states for a sounding reference signal separate from a physical uplink sharing channel, using a first downlink control information (DCI) format for a plurality of terminals, and the TPC command instructions using a terminal-specific second DCI format; and a control unit that determines, based on the RRC parameter, the application of at least one of a TPC command field included in the first DCI format and a TPC command field included in the second DCI format. [Note 2] The terminal according to Note 1, wherein if at least a portion of a physical downlink control channel (PDCCH) transmitting the first DCI format and a PDCCH transmitting the second DCI format overlap in the time domain, the control unit applies both a TPC command field included in the first DCI format and a TPC command field included in the second DCI format. [Note 3] The terminal according to Note 1 or Note 2, wherein, if at least a portion of the physical downlink control channel (PDCCH) transmitting the first DCI format and the PDCCH transmitting the second DCI format overlap in the time domain, the control unit applies only one of the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit controls the reporting of terminal capability information corresponding to at least one of the support for the TPC command instruction using the first DCI format and the support for the TPC command instruction using the second DCI format.

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

[0261] Figure 12 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0262] Furthermore, the wireless communication system 1 may 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)), and the like.

[0263] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

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

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

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

[0267] 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 (CC) and Dual Connectivity (DC).

[0268] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

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

[0270] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0271] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0272] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0273] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0274] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0275] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0276] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each user terminal 20.

[0277] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0278] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0280] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0281] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0282] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

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

[0284] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0285] 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, the DL-RS may include 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.

[0286] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0287] Furthermore, in the wireless communication system 1, an uplink reference signal (UL-RS) may be transmitted, such as a sounding reference signal (SRS) or a demodulation reference signal (DMRS). The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0288] (Base Station) Figure 13 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0289] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0290] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0292] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0293] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0294] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

[0296] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

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

[0298] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0299] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

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

[0301] The transmitting / receiving unit 120 (receiving 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 (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0302] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.

[0303] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing 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.

[0304] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

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

[0306] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0307] The transmitting / receiving unit 120 may transmit a Radio Resource Control parameter that enables at least one of the following: a transmit power control (TPC) command instruction for a plurality of closed-loop power control (CL-PC) adjustment states for a sounding reference signal separate from the physical uplink shared channel, using a first downlink control information (DCI) format for a plurality of terminals; and the TPC command instruction using a second DCI format specific to each terminal. The control unit 110 may use the RRC parameter to instruct the application of at least one of the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format (0th embodiment).

[0308] (User Terminal) Figure 14 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0309] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

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

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

[0312] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0314] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

[0316] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0317] The transmitting / receiving 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 and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0318] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0319] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0320] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

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

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

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

[0324] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. 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 interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0325] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0326] The transmitting / receiving unit 220 may receive Radio Resource Control parameters that enable at least one of the following: a transmit power control (TPC) command instruction for a plurality of closed-loop power control (CL-PC) adjustment states for a sounding reference signal separate from the physical uplink shared channel, using a first downlink control information (DCI) format for a plurality of terminals; and the TPC command instruction using a second DCI format specific to each terminal. The control unit 210 may determine, based on the RRC parameters, whether to apply at least one of the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format (0th embodiment).

[0327] If at least a portion of the physical downlink control channel (PDCCH) transmitting the first DCI format and the PDCCH transmitting the second DCI format overlap in the time domain, the control unit 210 may apply both the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format (first embodiment).

[0328] If at least a portion of the physical downlink control channel (PDCCH) transmitting the first DCI format and the PDCCH transmitting the second DCI format overlap in the time domain, the control unit 210 may apply only one of the TPC command fields included in the first DCI format or the TPC command fields included in the second DCI format (first embodiment).

[0329] The control unit 210 may control the reporting of terminal capability information corresponding to at least one of the support for the TPC command instruction using the first DCI format and the support for the TPC command instruction using the second DCI format (second embodiment).

[0330] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0331] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0333] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0334] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.

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

[0336] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0337] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.

[0338] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0339] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

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

[0341] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0342] 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 different buses may be configured for each device.

[0343] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0344] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0345] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0346] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0347] Here, the neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0348] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

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

[0350] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0351] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0352] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0353] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0354] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0355] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0356] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0357] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0358] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0359] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0360] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0361] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0362] A BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be configured within a single carrier for a UE.

[0363] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0364] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

[0366] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0368] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

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

[0370] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0371] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0372] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0373] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0374] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0375] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0377] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0378] 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,” and “receiving entity” may be used interchangeably.

[0379] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0380] The above group may include, for example, at least one of the following: 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, or a panel group.

[0381] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0382] Furthermore, in this disclosure, 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 interpreted interchangeably.

[0383] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0384] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.

[0385] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0386] In this disclosure, terms such as “Base Station (BS),” “wireless 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,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0387] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services 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 ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0388] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

[0389] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

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

[0391] 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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0392] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0393] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0394] Figure 16 shows an example of a vehicle according to one 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, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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.

[0395] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. 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 the user.

[0396] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0397] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0398] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0399] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0400] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0401] 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0402] 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 external devices. For example, it can send and receive various types of information to and from external devices 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. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

[0404] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0405] 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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0406] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.

[0407] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

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

[0409] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0410] Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0411] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0412] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0413] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0414] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0415] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0416] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0417] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

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

[0419] As used in this disclosure, the terms "connected" and "coupled", or any variations thereof, mean 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 of these. For example, "connected" may be read as "accessed".

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

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

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

[0423] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0424] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0425] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0426] In this disclosure, phrases 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. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0427] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0428] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0429] This application is based on Japanese Patent Application No. 2024-194597, filed on November 6, 2024. All of its contents are included here.

Claims

1. A terminal having a Radio Resource Control parameter that enables at least one of the following: a first downlink control information (DCI) format for multiple terminals, which is used for multiple transmit power control (TPC) command instructions for multiple closed-loop power control (CL-PC) adjustment states for a sounding reference signal separate from a physical uplink sharing channel; and a second DCI format specific to each terminal, which is used for the TPC command instructions; and a control unit that determines, based on the RRC parameter, the application of at least one of the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format.

2. The terminal according to claim 1, wherein, if at least a portion of the physical downlink control channel (PDCCH) transmitting the first DCI format and the PDCCH transmitting the second DCI format overlap in the time domain, the control unit applies both the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format.

3. The terminal according to claim 1, wherein, if at least a portion of the physical downlink control channel (PDCCH) transmitting the first DCI format and the PDCCH transmitting the second DCI format overlap in the time domain, the control unit applies only one of the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format.

4. The terminal according to claim 1, wherein the control unit controls the reporting of terminal capability information corresponding to at least one of the support for the TPC command instruction using the first DCI format and the support for the TPC command instruction using the second DCI format.

5. A wireless communication method for a terminal, comprising: receiving a Radio Resource Control parameter that enables at least one of a plurality of transmit power control (TPC) command instructions for a plurality of closed-loop power control (CL-PC) adjustment states for a sounding reference signal separate from a physical uplink sharing channel, using a first downlink control information (DCI) format for multiple terminals, and the TPC command instructions using a terminal-specific second DCI format; and determining, based on the RRC parameter, the application of at least one of the TPC command fields included in the first DCI format and the TPC command fields included in the second DCI format.

6. A base station having a transmission unit that transmits a Radio Resource Control parameter to enable at least one of the following: a transmission power control (TPC) command instruction for a plurality of closed-loop power control (CL-PC) adjustment states for a sounding reference signal separate from a physical uplink sharing channel, using a first downlink control information (DCI) format for multiple terminals, and the TPC command instruction using a second DCI format specific to each terminal; and a control unit that uses the RRC parameter to instruct the application of at least one of the TPC command field included in the first DCI format and the TPC command field included in the second DCI format.

Images