WO2024023984A1

WO2024023984A1 - Terminal, base station, and wireless communication method

Info

Publication number: WO2024023984A1
Application number: PCT/JP2022/028993
Authority: WO
Inventors: 大輔栗田; 浩樹原田; チーピンピ; ジンワン; ランチン; チャオピンチェン; ヨンリ
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2022-07-27
Filing date: 2022-07-27
Publication date: 2024-02-01

Abstract

One aspect of the present disclosure provides a terminal having: a control unit that sets a first transmission power for subband non-overlapping full duplex (SBFD) operation, according to a first power calculation formula, and sets a second transmission power for non-SBFD operation, according to a second power calculation formula; and a transmission unit that transmits an uplink channel using the first transmission power during the SBFD operation, and transmits the uplink channel using the second transmission power during the non-SBFD operation.

Description

Terminals, base stations and wireless communication methods

The present disclosure relates to a terminal, a base station, and a wireless communication method.

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of higher data rates, lower delay, etc. In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9). .

Successor systems of LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system m (6G), New Radio (NR), 3GPP Rel.15 or later) are also being considered. .

In future wireless communication systems (for example, NR), it is assumed that a plurality of user terminals (user terminals, user equipment (UE)) will communicate in an ultra-high-density and high-traffic environment.

Under such an environment, it is assumed that uplink (UL) resources are insufficient compared to downlink (DL) resources.

However, in the existing NR specifications, sufficient consideration has not been given to methods for increasing uplink resources. If the method cannot be properly controlled, system performance may deteriorate, such as increased delay and reduced coverage performance.

Therefore, one of the purposes of the present disclosure is to provide a terminal, a base station, and a wireless communication method that improve resource usage efficiency.

One aspect of the present disclosure is to set a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first transmission power setting, and set a second transmission power in a non-SBFD operation according to a second transmission power setting. and a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation. Regarding.
Other aspects of the present disclosure set a first transmit power in SBFD (Subband non-overlapping Full Duplex) operation according to a first closed loop, and set a second transmit power in non-SBFD operation according to a second closed loop. The present invention relates to a terminal having a control unit, and a transmitting unit that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation.
Another aspect of the present disclosure is to set the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation according to a first power calculation formula, and set the second transmission power in non-SBFD operation according to a second power calculation formula. a control unit that sets power; and a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation. Regarding the terminal.

FIG. 1 is a block diagram showing the functional configuration of a base station (gNB) according to an embodiment of the present disclosure. FIG. 2 is a block diagram showing the functional configuration of a terminal (UE) according to an embodiment of the present disclosure. 3A and 3B are diagrams illustrating an example of arrangement of radio resources of XDD (Cross Division Duplex) or SBFD (Subband non-overlapping Full Duplex) according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating XDD operation or SBFD operation according to an embodiment of the present disclosure. 5A and 5B are diagrams illustrating TDD and SBFD according to one embodiment of the present disclosure. 6A-6E are diagrams illustrating pure time units and SBFD time units according to one embodiment of the present disclosure. 7A and 7B are diagrams illustrating cross-link interference (CLI) according to one embodiment of the present disclosure. 8A and 8B are diagrams illustrating a PUSCH-Config information element (IE) according to one embodiment of the present disclosure. 9A and 9B are diagrams illustrating the PUSCH-Config IE according to an embodiment of the present disclosure. 10A and 10B are diagrams illustrating the PUSCH-PowerControl IE according to an embodiment of the present disclosure. 11A and 11B are diagrams illustrating the PUCCH-PowerControl IE according to one embodiment of the present disclosure. 12A and 12B are diagrams illustrating the RACH-ConfigGeneric IE according to one embodiment of the present disclosure. 13A and 13B are diagrams illustrating the RACH-ConfigGenericTwoStepRA-r16 IE according to an embodiment of the present disclosure. 14A and 14B are diagrams illustrating the PUSCH-ConfigCommon IE according to an embodiment of the present disclosure. FIG. 15 is a diagram illustrating the PUSCH-PowerControl IE according to an embodiment of the present disclosure. FIG. 16 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure. FIG. 17 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure. FIG. 18 is a diagram illustrating the SRI-PUSCH-PowerControl IE according to an embodiment of the present disclosure. FIG. 19 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure. FIG. 20 is a diagram illustrating closed-loop mapping according to an embodiment of the present disclosure. FIG. 21 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure. FIG. 22 is a diagram illustrating the SRI-PUSCH-PowerControl IE according to an embodiment of the present disclosure. FIG. 23 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure. FIG. 24 is a diagram illustrating power adjustment according to one embodiment of the present disclosure. FIG. 25 is a diagram illustrating power adjustment according to one embodiment of the present disclosure. FIG. 26 is a diagram illustrating power adjustment according to one embodiment of the present disclosure. FIG. 27 is a block diagram showing the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. FIG. 28 is a block diagram showing the hardware configuration of a vehicle according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

(wireless communication system)
The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof. Wireless communication systems include Long Term Evolution (LTE), which is specified by the Third Generation Partnership Project (3GPP), and 5th generation mobile communication system Ne. w Radio (5G NR), realizing communication using these successor wireless communication systems, etc. It may be a system that

Additionally, the wireless communication system may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), N Dual connectivity between R and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).

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

A wireless communication system has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) where both the MN and SN are NR base stations (gNB)). ) may be supported.

The wireless communication system may include a base station forming a macro cell C1 with relatively wide coverage, and a base station forming a small cell C2 that is located within the macro cell C1 and narrower than the macro cell C1. A terminal (UE) may be located within at least one cell. The arrangement, number, etc. of each cell and terminal are not limited to a specific aspect.

A terminal may connect to at least one of the plurality of base stations. The terminal may use at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

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

Further, the terminal may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

The plurality of base stations may be connected by wire (for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between two base stations, the base station that corresponds to the upper station is called the Integrated Access Backhaul (IAB) donor, and the base station that corresponds to the relay station is called the integrated access backhaul (IAB) donor. , may be called an IAB node.

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

The terminal may be a terminal compatible with at least one of communication systems such as LTE, LTE-A, 5G, and 6G.

In a wireless communication system, an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used. For example, in at least one of the downlink (DL) and uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA) or the like may be used.

A wireless access method may also be called a waveform. Note that in the wireless communication system, other wireless access methods (for example, other single carrier transmission methods, other multicarrier transmission methods) may be used as the UL and DL wireless access methods.

In wireless communication systems, downlink channels include a physical downlink shared channel (PDSCH) shared by each terminal, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical　Downlink　Control　Channel (PDCCH)) etc. may be used.

In a wireless communication system, uplink channels include a physical uplink shared channel (PUSCH) shared by each terminal, a physical uplink control channel (PUCCH), and a random access channel ( Physical Random Access Channel (PRACH) or the like may be used.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted via the PDSCH. User data, upper layer control information, etc. may be transmitted via PUSCH. Furthermore, a Master Information Block (MIB) may be transmitted via the PBCH.

Lower layer control information may be transmitted by PDCCH. The lower layer control information may include, for example, downlink control information (DCI) that includes scheduling information for at least one of PDSCH and PUSCH.

Note that 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. Note that PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

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

One search space may correspond to PDCCH candidates that correspond to one or more aggregation levels. One or more search spaces may be referred to as a search space (SS) set. Note that "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. in the present disclosure may be read interchangeably.

PUCCH provides channel state information (CSI), delivery confirmation information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK /NACK, etc.) and scheduling request (Scheduling Request). Uplink Control Information (UCI) including at least one of SR)) may be transmitted. A random access preamble for establishing a connection with a cell may be transmitted by PRACH.

Note that in the present disclosure, various channels may be expressed without adding "Physical" at the beginning.

In a wireless communication system, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In a wireless communication system, DL-RS includes a cell-specific reference signal (CRS) and a channel state information reference signal (CSI-RS). , demodulation reference signal (DeModulation Reference signal A positioning reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

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.

Furthermore, in the wireless communication system, a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). . Note that DMRS may be referred to as a UE-specific reference signal (UE-specific Reference Signal).

(Device configuration)
Next, an example of the functional configuration of the base station (gNB) 100 and the terminal (UE) 200 that execute the processes and operations described below will be described. The gNB 100 and the UE 200 include functions that implement the embodiments described below. However, the gNB 100 and the UE 200 may each have only some of the functions in the embodiment.

(gNB100)
FIG. 1 is a diagram showing an example of the functional configuration of the gNB 100. As shown in FIG. 1, the gNB 100 includes a receiving section 101, a transmitting section 102, and a control section 103. The functional configuration shown in FIG. 1 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.

The receiving unit 101 includes a function of receiving various signals transmitted from the UE 200 and acquiring, for example, information on a higher layer from the received signals. The transmitting unit 102 includes a function of generating a signal to be transmitted to the UE 200 and transmitting the signal by wire or wirelessly.

The control unit 103 stores preset setting information and various setting information to be transmitted to the UE 200 in a storage device, and reads them from the storage device as necessary. Further, the control unit 103 executes processing related to communication with the UE 200. A functional unit related to signal transmission in the control unit 103 may be included in the transmitting unit 102, and a functional unit related to signal reception in the control unit 103 may be included in the receiving unit 101.

(UE200)
FIG. 2 is a diagram showing an example of the functional configuration of the UE 200. As shown in FIG. 2, the UE 200 includes a transmitter 201, a receiver 202, and a controller 203. The functional configuration shown in FIG. 2 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.

The transmitter 201 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 202 wirelessly receives various signals and obtains higher layer signals from the received physical layer signals. Further, the receiving unit 202 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signal, reference signal, etc. transmitted from the gNB 100.

The control unit 203 stores various setting information received from the gNB 100 by the receiving unit 202 in a storage device, and reads it from the storage device as necessary. Further, the control unit 203 executes processing related to communication with the gNB 100. A functional unit related to signal transmission in the control unit 203 may be included in the transmitting unit 201, and a functional unit related to signal reception in the control unit 203 may be included in the receiving unit 202.

(SBFD operation)
Rel. Considering the transmission/reception time ratio (for example, DL:UL=4:1) by Time Division Duplex (TDD) up to There may be cases where the number of opportunities decreases. In such a case, the UE 200 may not be able to frequently transmit UL signals/channels, and there is a concern that transmission delays of important UL signals/channels may occur. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also concern about signal/channel congestion during UL transmission opportunities. Furthermore, in TDD, the time resources available for transmitting UL signals/channels are limited, so that the application of UL coverage expansion techniques, such as repetition, is also limited.

In future wireless communication systems (for example, Rel. 18 and later), it is being considered that a division duplexing method that combines TDD and frequency division duplexing (FDD) will be introduced for UL and DL. has been done.

The division duplex method may be called XDD (Cross Division Duplex) or subband non-overlapping Full Duplex (SBFD). XDD or SBFD may refer to a duplex method in which DL and UL are frequency division multiplexed within one component carrier (CC) of the TDD band (DL and UL can be used simultaneously).

FIG. 3A shows Rel. 16 is a diagram illustrating an example of TDD settings defined up to No. 16. FIG. In the example shown in FIG. 3A, TDD slots or symbols are configured for the UE in the bandwidth of one component carrier (CC) (cell, may also be called serving cell), bandwidth portion (BWP), etc. .

In the example shown in FIG. 3A, the time ratio of DL slots and UL slots is 4:1. With such conventional slot or symbol settings in TDD, sufficient UL time resources cannot be secured, and there is a risk that UL transmission delay will occur and coverage performance will deteriorate.

FIG. 3B is a diagram showing an example of the configuration of the SBFD. In the example shown in FIG. 3B, within one component carrier (CC), the resources used for DL reception and the resources used for UL transmission overlap in time. According to such a resource configuration, more UL resources can be secured, and resource utilization efficiency can be improved.

For example, as in the example shown in FIG. 3B, both ends of the frequency domain may be set as DL resources, and a UL resource may be sandwiched between these DL resources. Thereby, it is possible to avoid and alleviate the occurrence of cross link interference (CLI) with neighboring carriers. Further, a guard area may be set at the boundary between the DL resource and the UL resource.

Considering the complexity of processing self-interference, it is conceivable that only the base station 100 uses DL resources and UL resources at the same time. That is, in a radio resource where DL and UL overlap in time, one UE 200 may use the DL resource, and another UE 200 may use the UL resource.

FIG. 4 is a diagram showing an example of SBFD operation. In the example shown in FIG. 4, part of the DL resources of the TDD band is set as the UL resource, and the DL and UL are configured to partially overlap in the time domain.

In the example shown in FIG. 4, during the DL only period, each of the plurality of UEs 200 (UE#1 and UE#2 in FIG. 4) receives a DL channel/signal.

Furthermore, during a period when DL and UL overlap in time, one UE 200 (UE#1 in the example of FIG. 4) receives the DL channel/signal, and another UE 200 (UE#2 in the example of FIG. 4) receives the DL channel/signal. ) transmits the UL channel/signal. During this period, the base station 100 performs simultaneous transmission and reception of DL and UL.

Furthermore, during the UL only period, each of the plurality of UEs 200 (UE#1 and UE#2 in FIG. 4) transmits a UL channel/signal.

In existing NR (for example, defined by Rel. 15/16/17), DL frequency resources and UL frequency resources in the UE carrier are configured as DL BWP and UL BWP, respectively. Multiple BWP configurations and BWP adaptation mechanisms are required to switch one DL/UL frequency resource to another DL/UL frequency resource.

Furthermore, in the existing NR, as shown in FIG. 5A, the time resources (time units such as symbols and slots) in the TDD carrier for UE 200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration. Ru.

SBFD symbols may be advertised or configured as UL (or DL) on some frequency resources, or advertised or configured for UL transmission (or DL reception) while on other frequency resources, as shown in FIG. 5B. On the frequency resource, it may be notified or set as DL (or UL), or it may be a symbol notified or set for DL reception (or UL transmission). Alternatively, the SBFD symbol may be a symbol that is notified or configured as UL (or DL) in a part of the frequency resource, or a symbol that is notified or configured for UL transmission (or DL reception). Alternatively, the SBFD symbol may be notified or set as DL (or UL) in a part of the frequency resource, or may be a symbol notified or set for DL reception (or UL transmission).

Here, the time unit may be a symbol level, a slot/subslot level, or a group of symbols/slots/subslots. That is, an SBFD time unit may be an SBFD symbol, a slot/subslot that includes or overlaps the SBFD symbol, or a group of symbols/slots/subslots that includes or overlaps the SBFD symbol.

A pure time unit is a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol), a slot/subslot that does not contain or overlap an SBFD symbol, or a symbol/slot/subslot that does not contain or overlap an SBFD symbol. It may be a group of subslots and may be referred to as a non-SBFD time unit. For example, a pure time unit may be referred to as a time unit consisting only of DL on a frequency resource, as shown in FIG. 6A, or as a time unit consisting of only DL on a frequency resource, as shown in FIG. 6B. It may also be referred to as a time unit consisting of.

Furthermore, regarding the SBFD time unit, DL resources and UL resources may have various arrangement patterns in the frequency domain. For example, the SBFD time units of frequency domain pattern #1 may have an arrangement pattern as shown in FIG. 6C. Further, the SBFD time units of frequency domain pattern #2 may have an arrangement pattern as shown in FIG. 6D. Further, the SBFD time units of frequency domain pattern #3 may have an arrangement pattern as shown in FIG. 6E. These placement patterns are merely examples, and other placement patterns may be used. The frequency domain pattern for the SBFD time unit may mean a resource repetition pattern in the frequency domain for the SBFD time unit.

(PUSCH transmission power control)
Rel. In step 15, the UE performs transmission power control (TPC) for each transmission opportunity i. Transmission opportunity i may be a PUSCH, PUCCH, SRS, or PRACH transmission opportunity. Transmission opportunity i has a slot index n _{s, f} ^μ for subcarrier interval setting μ in a frame having a system frame number (SFN), and the first symbol in the slot (the first symbol of transmission opportunity i). index) S and the number L of consecutive symbols.

The transmission power of the PUSCH is controlled based on the TPC command (also referred to as a value, increase/decrease value, correction value, etc.) indicated by the value of a predetermined field (also referred to as a TPC command field, first field, etc.) in the DCI.

For example, if a UE transmits PUSCH on BWP b of carrier f in cell c with a parameter set (e.g., open loop parameter set) with index j, index l of power control adjustment state, then PUSCH transmission opportunity The transmission power of PUSCH (P _{PUSCH, b, f, c} (i, j, q _d , l)) in i (also referred to as transmission period etc.) may be expressed by the following formula (1).

In equation (1), P _CMAX,f,c (i) is, for example, the transmission power (for example, also referred to as maximum transmission power) of UE 200 set for carrier f of cell c in transmission opportunity i. P _{O_PUSCH, b, f, c} (j) is, for example, a parameter related to the target received power set for BWP b of carrier f of cell c in transmission opportunity i (e.g., a parameter related to transmit power offset, a transmit power offset (also referred to as PO, target received power parameter, etc.).

M ^PUSCH _RB,b,f,c (i) is, for example, the number of resource blocks (bandwidth) allocated to PUSCH for transmission opportunity i in uplink BWP b of cell c and carrier f with subcarrier spacing μ . α _b,f,c (j) are values provided by upper layer parameters (eg, also referred to as msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

PL _{b, f, c} (q _d ) is, for example, a path loss (path loss compensation) calculated by the UE using an index q _d of a reference signal for downlink BWP associated with uplink BWP b of carrier f of cell c. It is.

Δ _TF,b,f,c (i) is a Transmission Power Adjustment Component (eg, also referred to as offset, transmission format compensation, etc.) for uplink BWP b of carrier f of cell c.

f _b,f,c (i,l) is a TPC command-based value (e.g., cumulative value of TPC commands, closed loop value). For example, the cumulative value of TPC commands may be expressed by a predetermined formula.

The TPC command may be determined based on the value of a predetermined field (also referred to as a TPC command field, first field, etc.) in the DCI used for PUSCH or PDSCH scheduling. These DCIs may be referred to as DCI formats 0_0, 0_1. The power control information may be called a TPC command (also referred to as a value, increase/decrease value, correction value, etc.).

Furthermore, NR supports the DCI format (for example, DCI format 2_2) used for transmitting at least one TPC command of PUCCH and PUSCH. UE 200 may control the transmission power of at least one of PUCCH and PUSCH based on the value indicated by the TPC command in the DCI format. The DCI format used for transmitting TPC commands may have a configuration that is not used for PDSCH or PUSCH scheduling (does not include scheduling information).

Additionally, TPC commands specified by DCI (for example, at least one of DCI formats 0_0, 0_1, and 2_2) for each PUSCH or PUCCH transmission may be accumulated (tpc-Accumulation). The UE 200 may be configured by the network (for example, the base station 100) as to whether or not to store TPC commands. The base station 100 may notify the UE 200 of whether TPC commands are accumulated using upper layer signaling (eg, TPC-Accumulation).

When accumulation of TPC commands is enabled, the UE 200 may determine the transmission power in consideration of the TPC commands notified on a predetermined DCI (or PDCCH). Further, the TPC command may be included in one of the parameters of the power control adjustment state defined by a predetermined formula (for example, as part of the predetermined formula).

(PUCCH transmission power control)
The transmission power of the PUCCH is controlled based on the TPC command (also referred to as a value, increase/decrease value, correction value, etc.) indicated by the value of a predetermined field (also referred to as a TPC command field, first field, etc.) in the DCI.

For example, PUCCH transmission power (P _{PUCCH, b, f, c} (i, q _u , q _d , l)) may be expressed by equation (2).

Here, the power control adjustment state may be set to have a plurality of states (for example, two states) or a single state by upper layer parameters. Further, when a plurality of power control adjustment states are set, one of the plurality of power control adjustment states may be identified by an index l (for example, lε{0,1}). The power control adjustment state may be referred to as a PUCCH power control adjustment state, a first state, a second state, or the like.

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

In equation (2), P _CMAX,f,c (i) is, for example, the transmission power (also referred to as maximum transmission power) of the UE 200 set for carrier f of cell c in transmission opportunity i. P _{O_PUCCH,b,f,c} (q _u ) is, for example, a parameter related to the target received power (for example, a parameter related to the transmit power offset, a parameter related to the transmit power (also referred to as offset P0 or target received power parameter).

M ^PUCCH _RB,b,f,c (i) is, for example, the number of resource blocks (bandwidth) allocated to PUCCH for transmission opportunity i in uplink BWP b of cell c and carrier f with subcarrier spacing μ . PL _{b, f, c} (q _d ) is, for example, a path loss calculated by the UE 200 using the index q _d of the reference signal for downlink BWP associated with uplink BWP b of carrier f of cell c.

_{ΔF_PUCCH} (F) is an upper layer parameter given for each PUCCH format. Δ _TF,b,f,c (i) is the Transmission Power Adjustment Component (offset) for uplink BWP b of carrier f of cell c.

g _{b, f, c} (i, l) is the TPC command-based value (e.g., cumulative value of TPC commands) of the uplink BWP power control adjustment state index l of carrier f of cell c and transmission opportunity i . For example, the cumulative value of TPC commands may be expressed by a predetermined formula.

In this way, in NR, transmission power is determined for uplink channels (for example, at least one of PUSCH and PUCCH) based on parameters notified from the network (for example, base station 100).

Note that equations (1) and (2) are merely examples, and are not limited thereto. The UE 200 only needs to control the transmission power of the PUSCH and PUCCH based on at least one parameter illustrated in equations (1) and (2), and may include additional parameters or some parameters. may be omitted. Furthermore, in Equations (1) and (2), the transmission power of PUSCH and PUCCH is controlled for each BWP of a certain carrier in a certain cell, but the invention is not limited to this. At least some of the cells, carriers, BWPs, and power control adjustment states may be omitted.

(Closed loop transmit power control)
In NR, the transmission power of UE 200 is controlled using open loop transmission power control and/or closed loop transmission power control. UE 200 corrects open-loop control errors using closed-loop control using TPC commands received from base station 100.

For example, the transmit power of uplink shared channels (e.g., PUSCH), uplink control channels (e.g., PUCCH), sounding reference signals (SRS), random access channels (e.g., PRACH), etc. are subject to transmit power control. .

NR specifies that a maximum of two closed loops are supported for each carrier in the serving cell.

In NR, the transmission power of the PUSCH in the transmission period i for the bandwidth part (BWP) b of the carrier f of the serving cell c may be expressed by the above equation (1). Here, the transmission period may be, for example, any time unit such as a symbol, slot, subframe, or frame.

In Equation (1), f _{b, f, c} (i, l) are values based on TPC commands (for example, cumulative values based on TPC commands). l is the index of the power control adjustment state. For example, when the UE 200 is set to maintain a plurality (for example, two) of power control adjustment states of a predetermined channel (for example, PUSCH, PUCCH, etc.) using upper layer signaling, the UE 200 sets at least one of a plurality of values as l. One can be used (eg, l∈{0,1}). If there is no such setting, the UE 200 may assume that one value (for example, l=0) is used as l.

For example, when the RRC parameter "twoPUSCH-PC-AdjustmentStates" is set for the PUSCH, the UE 200 may determine that two power control states are applied to the transmission power control of the PUSCH. Furthermore, when the RRC parameter "two PUCCH-PC-AdjustmentStates" is set for the PUCCH, the UE may determine that two power control states are applied to the transmission power control of the PUCCH.

Other uplink signals (e.g., SRS, PRACH, etc.) can also determine transmit power using multiple power control adjustment states, similar to PUSCH and/or PUCCH, although the parameters utilized are different. .

In this disclosure, closed loop and power control adjustment state may be read interchangeably.

By the way, in NR, TPC commands can be notified to multiple UEs at once. For example, Downlink Control Information (DCI) format 2_2 transmitted in the common search space is used to transmit a TPC command for at least one of PUCCH and PUSCH. DCI format 2_2 may be called DCI for UE group common TPC command. The TPC command notified by DCI format 2_2 may be called a group common TPC command.

The DCI format 2_2 may be cyclic redundancy check (CRC) scrambled by the PUSCH TPC identifier (TPC-PUSCH-RNTI (Radio Network Temporary Identifier)). PUCCH TPC identifier (TPC -PUCCH-RNTI).

[assignment]
According to SBFD operation or dynamic TDD, inter-gNB cross-link interference (CLI) and inter-UE CLI need to be considered. For UE-to-UE CLI, the aggressor UE's uplink signal may cause interference to downlink reception at the victim UE, as shown in FIG. 7A. From the victim UE's perspective, it may be desirable to reduce the uplink transmit power of the aggressor UE to reduce interference to reception at the victim UE.

On the other hand, for inter-gNB CLI, as shown in FIG. 7B, the downlink signal to the aggressor UE may cause interference to the uplink signal from the victim UE to the gNB. From the perspective of the victim UE's gNB, it may be desirable to increase the victim UE's uplink transmit power in order to improve the received signal power.

In particular, in SBFD operation, different UEs will perform uplink transmission and downlink reception in the same time unit, such as the same symbol/slot, which may result in inter-UE CLI and/or inter-gNB CLI. . The transmit power control of the UE is defined by specifications, may be configured semi-statically by RRC configuration, etc., and/or may be dynamically notified by DCI notification. Proposals 1 to 3 below discuss the power control of uplink signals in SBFD symbols/slots through specifications that support both SBFD and non-SBFD operations, and RRC configuration and/or DCI notification. A separate power control application is proposed for SBFD operation.

[Summary of proposal]
As proposal 1, separate transmit power settings may be applied for SBFD and non-SBFD operations.

Specifically, in option 1, for transmission power control IEs such as PUSCH-PowerControl IE and PUCCH-PowerControl IE, separate transmission power control IEs (for example, PUSCH-PowerControl IE) are used for SBFD operation and non-SBFD operation. and PUSCH-PowerControl-SBFD, PUCCH-PowerControl and PUCCH-PowerControl-SBFD, etc.) may be set.

In addition, in option 2, fields related to power control in PUSCH-PowerControl IE, PUCCH-PowerControl IE, etc. are set to separate transmission power control fields for SBFD operation and non-SBFD operation (for example, p0-NominalWithGrant and p0-NominalWithGrant). tGrant -SBFD, p0-Set and p0-Set-SBFD) may be set.

As proposal 2, separate closed loops may be applied for SBFD and non-SBFD operations.

Specifically, for problem 1, regarding the closed loop of PUSCH and/or PUCCH in SBFD operation, in Alt-a, a maximum of two existing closed loops are set, and each closed loop is divided into SBFD operation and non-SBFD operation. can be applied to either one.

Also, according to Alt-b, the maximum number to be configured is expanded to X, and at most two closed loops among the X can be configured for non-SBFD operation, and the others can be applied for SBFD operation.

Furthermore, according to Alt-c, the closed loop for SBFD operation is not explicitly set, and the closed loop for SBFD operation can be mapped in response to the setting for non-SBFD operation.

Regarding problem 2, regarding the mapping between SRI (SRS (Sounding Reference Signal) Resource Index) and closed-loop index, according to Atl-1, a single SRI/closed-loop index is used for non-SBFD operation or SBFD operation. can be mapped to an action.

Also, according to Alt-2, a single SRI/closed loop index can be commonly mapped for SBFD and SBFD operations.

Also, regarding problem 3, regarding the closed-loop index for Configured Grant (CG) PUSCH, according to Alt-1, a single closed-loop index can be mapped to non-SBFD operation or SBFD operation.

According to Alt-2, a single closed-loop index can be commonly mapped for SBFD and SBFD operations.

As proposal 3, a method for calculating transmission power in SBFD operation may be defined. According to option 1, scaling factors for SBFD operation may be defined, configured, notified and/or applied.

According to option 2, a power offset for SBFD operation may be defined, configured, notified and/or applied.

According to option 3, a reference resource block (RB) size for SBFD operation may be defined, configured, notified and/or applied.

[Proposal 1]
In proposal 1, the UE transmits the uplink channel in SBFD operation with the transmit power set according to the PUSCH and/or PUCCH transmit power setting for SBFD operation, and according to the PUSCH and/or PUCCH transmit power setting for non-SBFD operation. Transmit the uplink channel in non-SBFD operation with the configured transmit power. That is, the PUSCH and/or PUCCH transmission power is semi-statically set via RRC configuration or the like according to the PUSCH and/or PUCCH transmission power setting for SBFD operation and the PUSCH and/or PUCCH transmission power setting for non-SBFD operation. .

Specifically, according to option 1, separate PUSCH and/or PUCCH transmit power settings for SBFD and non-SBFD operations (e.g., PUSCH-PowerControl IE and PUSCH-PowerControl-SBFD IE, and/or PUCCH- PowerControl IE and PUCCH-PowerControl-SBFD IE, etc.) may be defined, configured, notified and/or applied.

Also, according to option 2, for specific parameters or fields in the PUSCH and/or PUCCH transmit power settings (e.g., PUSCH-PowerControl IE and/or PUCCH-PowerControl IE, etc.), SBFD operation and non-SBFD operation are settings (eg, p0-NominalWithoutGrant and p0-NominalWithoutGrant-SBFD, and/or p0-Set and p0-Set-SBFD, etc.) may be defined, configured, notified, and/or applied. Additionally or alternatively, power control related parameters in RACH-ConfigGeneric (e.g. preambleReceivedTargetPower), power control related parameters in RACH-ConfigGenericTwoStepRA (e.g. msgA-PreambleReceivedTargetPower) er), and/or power control related parameters in PUSCH-ConfigCommon (for example, msg3 -DeltaPreamble, p0-NominalWithGrant), separate settings may be prescribed, configured, notified, and/or applied for SBFD and non-SBFD operations.

(Option 1)
Option 1 provides separate PUSCH and/or PUCCH transmit power settings for SBFD and non-SBFD operations (e.g., PUSCH-PowerControl IE and PUSCH-PowerControl-SBFD IE, and/or PUCCH-PowerControl IE and PUCCH-Power Control - SBFD IE, etc.) may be defined, configured, notified and/or applied.

Note that hereinafter, PUSCH and/or PUCCH in SBFD operation means PUSCH and/or PUCCH that overlaps with SBFD time units such as SBFD symbols and SBFD slots. Furthermore, PUSCH and/or PUCCH in non-SBFD operation means PUSCH and/or PUCCH that do not overlap with SBFD time units such as SBFD symbols and SBFD slots.

Specifically, additional fields such as PUSCH-PowerControl-SBFD may be set in the PUSCH-Config IE. For example, in the existing NR, as shown in FIG. 8A, "pusch-PowerControl" is set as the PUSCH power control IE in the PUSCH-Config IE. On the other hand, according to option 1, as shown in FIG. 8B, "pusch-PowerControl-SBFD" may be additionally set as the PUSCH power control IE for SBFD operation. That is, "pusch-PowerControl-SBFD" as a PUSCH power control IE for SBFD operation and "pusch-PowerControl" as a PUSCH power control IE for non-SBFD operation may be set in the PUSCH-Config IE. . The UE may transmit the PUSCH using the transmission power of the push-PowerControl-SBFD IE in SBFD operation, and may transmit the PUSCH using the transmission power of the push-PowerControl IE in non-SBFD operation. This makes it possible to set different PUSCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.

Additionally, additional fields such as PUCCH-PowerControl-SBFD may be set in PUCCH-Config. For example, in the existing NR, as shown in FIG. 9A, "pucch-PowerControl" is set as the PUCCH power control IE in PUCCH-Config. On the other hand, according to option 1, as shown in FIG. 9B, "pucch-PowerControl-SBFD" may be additionally set as the PUCCH power control IE for SBFD operation. That is, "pucch-PowerControl-SBFD" as a PUCCH power control IE for SBFD operation and "pucch-PowerControl" as a PUCCH power control IE for non-SBFD operation may be set in the PUCCH-Config IE. . The UE may transmit the PUCCH using the transmission power from the pucch-PowerControl-SBFD IE in the SBFD operation, and may transmit the PUCCH using the transmission power from the pucch-PowerControl IE during the non-SBFD operation. This makes it possible to set different PUCCH transmission powers to the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing UE-to-UE CLI and/or gNB-to-gNB CLI during SBFD operation. Can be done.

According to option 1, it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, resulting in inter-UE CLI and/or inter-gNB CLI during SBFD operation. The possibility can be reduced.

(Option 2)
In option 2, separate configurations may be specified, configured, notified and/or applied for SBFD and non-SBFD operations for specific fields/parameters in the PUSCH-PowerControl IE and/or PUCCH-PowerControl IE. good.

Specifically, additional fields such as "p0-NominalWithoutGrant-SBFD" and "p0-AlphaSets-SBFD" may be set in the PUSCH-PowerControl IE. For example, in the existing NR, as shown in FIG. 10A, "p0-NominalWithoutGrant", "p0-AlphaSets", etc. are set as PUSCH power control fields in the PUSCH-PowerControl IE. Meanwhile, according to option 2, as shown in FIG. 10B, "p0-NominalWithoutGrant-SBFD" and "p0-AlphaSets-SBFD" may be additionally set as PUSCH power control fields for SBFD operation. That is, "p0-NominalWithoutGrant-SBFD" and "p0-AlphaSets-SBFD" as PUSCH power control fields for SBFD operation, and "p0-NominalWithoutGrant" and "p0-AlphaS" as PUSCH power control fields for non-SBFD operation. ets ” may be set in the PUSCH-PowerControl IE. The UE transmits PUSCH with the transmission power according to the PUSCH power control field such as "p0-NominalWithoutGrant-SBFD", "p0-AlphaSets-SBFD" in SBFD operation, and "p0-NominalWithoutGrant", "p0-AlphaSets-SBFD" in non-SBFD operation. -AlphaSets" PUSCH may be transmitted using the transmission power. This makes it possible to set different PUSCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.

Additionally, additional fields such as "p0-Set-SBFD" may be set in the PUCCH-PowerControl IE. For example, in the existing NR, as shown in FIG. 11A, "p0-Set" etc. are set as the PUCCH power control field in the PUCCH-PowerControl IE. Meanwhile, according to option 2, as shown in FIG. 11B, "p0-Set-SBFD" may be additionally set as a PUCCH power control field for SBFD operation. That is, "p0-Set-SBFD" as a PUCCH power control field for SBFD operation and "p0-Set" as a PUCCH power control field for non-SBFD operation may be set in the PUCCH-PowerControl IE. . In SBFD operation, the UE transmits the PUCCH with the transmit power according to the PUCCH power control field such as "p0-Set-SBFD", and in non-SBFD operation, the UE transmits the PUCCH with the transmit power according to the PUCCH power control field such as "p0-Set". may also be sent. This makes it possible to set different PUCCH transmission powers to the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.

Also, additional fields such as "preambleReceivedTargetPower-SBFD" may be set in the RACH-ConfigGeneric IE. For example, in the existing NR, as shown in FIG. 12A, "preambleReceivedTargetPower" and the like are set as the RACH power control field in the RACH-ConfigGeneric IE. Meanwhile, according to option 2, as shown in FIG. 12B, "preambleReceivedTargetPower-SBFD" may be additionally set as the RACH power control field for SBFD operation. That is, "preambleReceivedTargetPower-SBFD" as a RACH power control field for SBFD operation and "preambleReceivedTargetPower" as a RACH power control field for non-SBFD operation are RACH-ConfigGeneric. It may be set in IE. The UE transmits the PRACH with the transmit power according to the PRACH power control field such as "preambleReceivedTargetPower-SBFD" in SBFD operation, and transmits PRACH with the transmit power according to the PRACH power control field such as "preambleReceivedTargetPower" in non-SBFD operation. to send H You may also do so. This makes it possible to set different PRACH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing UE-to-UE CLI and/or gNB-to-gNB CLI during SBFD operation. Can be done.

Additionally, additional fields such as "msgA-PreambleReceivedTargetPower-SBFD" may be set in the RACH-ConfigGenericTwoStepRA IE. For example, in the existing NR, as shown in FIG. 13A, a PRACH power control field such as "msgA-PreambleReceivedTargetPower" is set in the RACH-ConfigGenericTwoStepRA IE. Meanwhile, according to option 2, as shown in FIG. 13B, "msgA-PreambleReceivedTargetPower-SBFD" may be additionally set as a PRACH power control field for SBFD operation. That is, "msgA-PreambleReceivedTargetPower-SBFD" as the RACH power control field for SBFD operation and "msgA-PreambleReceivedTargetPower" as the RACH power control field for non-SBFD operation are gGenericTwoStepRA May be set in IE . The UE transmits the PRACH with the transmission power according to the PRACH power control field such as "msgA-PreambleReceivedTargetPower-SBFD" in SBFD operation, and the PRACH power such as "msgA-PreambleReceivedTargetPower" in non-SBFD operation. PRACH by transmit power by control field You may also send This makes it possible to set different PRACH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing UE-to-UE CLI and/or gNB-to-gNB CLI during SBFD operation. Can be done.

Additionally, additional fields such as "msg3-DeltaPreamble-SBFD" and "p0-NominalWithGrant-SBFD" may be set in the PUSCH-ConfigCommon IE. For example, in the existing NR, as shown in FIG. 14A, "msg3-DeltaPreamble", "p0-NominalWithGrant", etc. are set as PUSCH power control fields in the PUSCH-ConfigCommon IE. Meanwhile, according to option 2, as shown in FIG. 14B, "msg3-DeltaPreamble-SBFD" and "p0-NominalWithGrant-SBFD" may be additionally set as the PUSCH power control field for SBFD operation. That is, "msg3-DeltaPreamble-SBFD" and "p0-NominalWithGrant-SBFD" as PUSCH power control fields for SBFD operation, and "msg3-DeltaPreamble" and "p0-Nominal" as PUSCH power control fields for non-SBFD operation. WithGrant ” may be set in the PUSCH-ConfigCommon IE. The UE transmits the PUSCH with the transmission power according to the PUSCH power control field such as "msg3-DeltaPreamble-SBFD" and "p0-NominalWithGrant-SBFD" in SBFD operation, and "msg3-DeltaPreamble" and "p0 NominalWithGrant-SBFD" in non-SBFD operation. PUSCH may be transmitted using the transmission power according to the PUSCH power control field such as "-NominalWithGrant". This makes it possible to set different PUSCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.

Note that the PUSCH and/or PUCCH power control field is not limited to the above-mentioned fields, and may include "p0-NominalWithGrant", "p0-PUSCH-Alpha", "p0-AlphaSets", "delta-MCS", and "deltaF-PUCCH". -f0”, “deltaF-PUCCH-f1”, “deltaF-PUCCH-f2”, “deltaF-PUCCH-f3”, “deltaF-PUCCH-f4”, etc. also for other PUSCH/PUCCH power control fields. , separate settings for SBFD and non-SBFD operations may be defined, configured, notified, and/or applied.

According to option 2, it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, resulting in inter-UE CLI and/or inter-gNB CLI during SBFD operation. The possibility can be reduced.

In proposal 1, the UE may set the transmission power in SBFD operation according to the transmission power setting for SBFD, and may set the transmission power in non-SBFD operation according to the transmission power setting for non-SBFD. Here, the transmission power setting for SBFD and/or the transmission power setting for non-SBFD is defined by the specifications, semi-statically set by RRC settings, etc., or dynamically notified by DCI notification etc. It's okay. Further, the transmission power setting for SBFD and/or the transmission power setting for non-SBFD may be specified, set, notified, or applied explicitly or implicitly. Furthermore, option 1 and option 2 may or may not be used together.

The UE may transmit the uplink channel with the transmission power according to the SBFD transmission power setting in SBFD operation, and may transmit the uplink channel with the transmission power according to the non-SBFD transmission power setting in non-SBFD operation. For example, in option 1, the transmit power settings for SBFD and the transmit power settings for non-SBFD are separate transmit power settings information elements for SBFD and non-SBFD operations (e.g., PUSCH-PowerControl-SBFD IE and PUSCH -PowerControl IE, PUCCH-PowerControl-SBFD IE, PUCCH-PowerControl IE, etc.). In this case, the UE determines the PUSCH and/or PUCCH transmission power according to the PUSCH-PowerControl-SBFD IE and/or the PUCCH-PowerControl-SBFD IE in the SBFD operation, and in the non-SBFD operation, the UE determines the PUSCH-PowerControl-SBFD IE and/or the PUCCH-PowerControl-SBFD IE. IE and/or Alternatively, the PUSCH and/or PUCCH transmission power may be determined according to the PUCCH-PowerControl IE.

In addition, in option 2, the transmit power setting for SBFD and the transmit power setting for non-SBFD are the transmit power parameter for SBFD operation and the transmit power parameter for non-SBFD operation in the same transmit power setting information element. may be defined by For example, in the SBFD operation, the UE determines the PUSCH transmission power according to p0-NominalWithoutGrant-SBFD, p0-AlphaSets-SBFD, etc. in the PUSCH-PowerControl IE, and in the non-SBFD operation, the UE determines the PUSCH transmission power according to the PUSCH-PowerControl IE. p0-Nominal Without Grant in IE, PUSCH transmission power may be determined according to p0-AlphaSets or the like. In addition, in SBFD operation, the UE determines PUCCH transmission power according to p0-Set-SBFD, etc. in PUCCH-PowerControl IE, and in non-SBFD operation, determines PUCCH transmission power according to p0-Set, etc. in PUCCH-PowerControl IE. You may.

The uplink channel may also include one or more of an uplink shared channel, an uplink control channel, and a random access channel. Specifically, the UE may transmit the PUSCH, PUCCH and/or PRACH according to the PUSCH transmission power setting, the PUCCH transmission power setting and/or the PRACH transmission power setting.

On the other hand, the gNB may set the transmission power for SBFD operation to the UE according to the transmission power setting for SBFD, and may set the transmission power for non-SBFD operation to the UE according to the transmission power setting for non-SBFD. Here, the transmission power setting for SBFD and/or the transmission power setting for non-SBFD is either specified by the specifications, semi-statically set by RRC settings, or dynamically notified by MAC CE etc. It's okay. Further, the transmission power setting for SBFD and/or the transmission power setting for non-SBFD may be specified, set, notified, or applied explicitly or implicitly.

The gNB may receive an uplink channel transmitted from the UE with a transmission power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE with transmission power for non-SBFD in non-SBFD operation. For example, in option 1, the transmit power settings for SBFD and the transmit power settings for non-SBFD are separate transmit power settings information elements for SBFD and non-SBFD operations (e.g., PUSCH-PowerControl-SBFD IE and PUSCH -PowerControl IE, PUCCH-PowerControl-SBFD IE, PUCCH-PowerControl IE, etc.). In this case, the gNB sets the PUSCH and/or PUCCH transmission power for SBFD operation to the UE according to the PUSCH-PowerControl-SBFD IE and/or the PUCCH-PowerControl-SBFD IE, and UCCH-PowerControl IE Accordingly, the PUSCH and/or PUCCH transmission power for non-SBFD operation may be set in the UE.

In addition, in option 2, the transmit power setting for SBFD and the transmit power setting for non-SBFD are the transmit power parameter for SBFD operation and the transmit power parameter for non-SBFD operation in the same transmit power setting information element. may be defined by For example, the gNB sets the PUSCH transmission power in the SBFD operation to the UE using p0-NominalWithoutGrant-SBFD, p0-AlphaSets-SBFD, etc. in the PUSCH-PowerControl IE, and p0 in the PUSCH-PowerControl IE. - Nominal Without Grant, p0 - AlphaSets etc. PUSCH transmission power in SBFD operation may be set in the UE. In addition, the gNB sets the PUCCH transmission power in SBFD operation to the UE using p0-Set-SBFD etc. in the PUCCH-PowerControl IE, and sets the PUCCH transmission power in non-SBFD operation to the UE using p0-Set etc. in the PUCCH-PowerControl IE. You may.

The uplink channel may also include one or more of an uplink shared channel, an uplink control channel, and a random access channel. Specifically, the gNB may receive the PUSCH, PUCCH, and/or PRACH transmitted from the UE according to the PUSCH transmission power setting, the PUCCH transmission power setting, and/or the PRACH transmission power setting.

Note that the UE may report the UE capability regarding whether to support separate PUSCH and/or PUCCH transmission power settings for SBFD operation and non-SBFD operation to the gNB. The gNB may determine whether to perform separate PUSCH and/or PUCCH transmission power settings for SBFD operation and non-SBFD operation based on the acquired UE capability.

As described above, in Proposal 1, different transmission power settings are applied to SBFD operation and non-SBFD operation. Therefore, it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. can be reduced.

[Proposal 2]
In proposal 2, the UE transmits the uplink channel in SBFD operation with the transmission power adjusted by the PUSCH and/or PUCCH closed loop for SBFD operation, and the transmission adjusted by the PUSCH and/or PUCCH closed loop for non-SBFD operation. Transmit uplink channel in non-SBFD operation by power. That is, PUSCH and/or PUCCH transmit power is dynamically adjusted according to closed loop for SBFD operation and closed loop for non-SBFD operation via DCI notification or the like.

In Proposal 2, the setting of PUSCH and/or PUCCH closed loop in cell SBFD operation is considered as Problem 1. Also, the mapping relationship between uplink transmission beams (eg, SRI and/or PUCCH spatial relation info, etc.) and PUSCH and/or PUCCH closed loop index is considered as issue 2. Additionally, the mapping relationship between the PUSCH configuration of a configured grant (eg, Configured Grant) and the PUSCH closed loop index is considered as issue 3.

(Problem 1)
As problem 1, the configuration of PUSCH and/or PUCCH closed loop in cell SBFD operation may be considered.

<Alt-a>
In Alt-a, up to two PUSCH and/or PUCCH closed loops may be configured for a cell, one closed loop applied for SBFD operation and the other closed loop applied for non-SBFD operation. That is, in Alt-a, up to two PUSCH and/or PUCCH closed loops may be configured for a cell according to the restrictions of Release 15/16/17. For example, the UE may determine that twoPUSCH-PC-AdjustmentStates and/or twoPUCCH-PC-AdjustmentStates are PUSCH-PowerControl IE and/or PUCCH-PowerCo of a serving cell or BWP with SBFD operation. Assuming that it is always set in ntrol IE Good too.

Here, which closed loop among up to two closed loops is set for SBFD operation and/or non-SBFD operation is determined by the specifications, or is set semi-statically by RRC settings, etc. It may be dynamically notified by DCI notification or the like, or it may be determined by the UE according to predetermined rules. Furthermore, which closed loop of up to two closed loops is configured for SBFD operation and/or non-SBFD operation may be explicitly or implicitly defined, configured, notified, or applied.

According to Alt-a, up to two closed-loop configurations of the existing NR can be applied to provide a closed-loop for SBFD operation and a closed-loop for non-SBFD operation, and the PUSCH and/or It becomes possible to dynamically control PUCCH transmission power.

<Alt-b>
In Alt-b, a total of up to X PUSCH and/or PUCCH closed loops may be configured, and up to 2 of the X PUSCH and/or PUCCH closed loops may be configured for non-SBFD operation. Typically, the value of X may be greater than two. Further, the number of PUSCH and/or PUCCH closed loops for SBFD operation may be smaller than 2, may be equal to 2, or may be larger than 2.

Here, the value of . Further, the value of X may be explicitly or implicitly defined, set, notified, or applied. Also, which closed loops among up to It may be dynamically notified, such as by notification, or may be determined by the UE according to predetermined rules. Further, which closed loop among up to X closed loops is set for SBFD operation and/or non-SBFD operation may be explicitly or implicitly defined, set, notified, or applied.

For example, as shown in Figure 15, the number of PUSCH closed loops for non-SBFD operation is set by the existing twoPUSCH-PC-AdjustmentStates field in the PUSCH-PowerControl IE, and the number of PUSCH closed loops for SBFD operation is set by the PUSCH- May be set by the new SBFD-PUSCH-PC-AdjustmentStates field in the PowerControl IE. For example, PUSCH closed loop index #0, #1 may indicate a closed loop for non-SBFD operation, and PUSCH closed loop index #2, #3 may indicate a closed loop for SBFD operation.

Similarly, the number of PUCCH closed loops for non-SBFD operation is set by the existing two PUCCH-PC-AdjustmentStates field in the PUCCH-PowerControl IE, and the number of PUCCH closed loops for SBFD operation is set by the existing two PUCCH-PC-AdjustmentStates field in the PUCCH-PowerControl IE. New SBFD in It may be set by the PUCCH-PC-AdjustmentStates field. For example, PUCCH closed loop index #0, #1 may indicate a closed loop for non-SBFD operation, and PUCCH closed loop index #2, #3 may indicate a closed loop for SBFD operation.

Here, the number of PUSCH and/or PUCCH closed loops for SBFD operation is defined by the specifications, semi-statically set by RRC settings, etc., dynamically notified by DCI notification, etc., or determined by a predetermined number. It may be determined by the UE according to rules.

Note that the number of PUSCH and/or PUCCH closed loops for SBFD operation may be greater than, equal to, or smaller than the number of PUSCH and/or PUCCH closed loops for non-SBFD operation. In addition, if twoPUSCH-PC-AdjustmentStates and/or twoPUCCH-PC-AdjustmentStates are not set, the UE determines whether twoStates is SBFD-PUSCH-PC-AdjustmentStates and/or SBF Must be set in D-PUCCH-PC-AdjustmentStates. There is no need to assume that Also, if OneState is set to SBFD-PUSCH-PC-AdjustmentStates and/or SBFD-PUCCH-PC-AdjustmentStates, the UE sets twoPUSCH-PC-AdjustmentStates and/or two PUCCH-PC-AdjustmentStates must be set. There is no need to assume that

According to Alt-b, for non-SBFD operations, up to two closed-loop configurations of existing NR can be applied to provide a closed loop for SBFD operations and a closed loop for non-SBFD operations, and It becomes possible to dynamically control PUSCH and/or PUCCH transmission power.

<Alt-c>
In Alt-c, the PUSCH and/or PUCCH closed loop for SBFD operation is not explicitly configured, but one-to-one mapping from the PUSCH and/or PUCCH closed loop configured for non-SBFD operation. ) may be implicitly set by That is, when PUSCH and/or PUCCH closed loop for non-SBFD operation is configured, based on a predetermined one-to-one mapping, corresponding to the configured PUSCH and/or PUCCH closed loop for non-SBFD operation, PUSCH and/or PUCCH closed loops are identified. In non-SBFD operation, the UE adjusts the PUSCH and/or PUCCH transmit power by the PUSCH and/or PUCCH closed loop for non-SBFD operation, and in SBFD operation, the UE adjusts the PUSCH and/or PUCCH transmit power implicitly from the PUSCH and/or PUCCH closed loop for non-SBFD operation. The PUSCH and/or PUCCH transmission power may be adjusted according to the PUSCH and/or PUCCH closed loop for SBFD operation configured as follows.

For example, if twoPUSCH-PC-AdjustmentStates is not set, i.e. if a single PUSCH closed-loop index #i0 is set for non-SBFD operation, it means that PUSCH closed-loop index #i1 or #i2 is set for SBFD operation. PUSCH closed-loop index #i0 for non-SBFD operation may be associated with PUSCH closed-loop index #i1 or #i2 for SBFD operation. Note that the wording "#i1 or #i2" is used because it is not certain whether the PUSCH closed loop for SBFD operation starts from i2 or i1.

Also, for example, if twoPUSCH-PC-AdjustmentStates is set, that is, if PUSCH closed-loop index #i0 and #i1 are set for non-SBFD operation, it means that PUSCH closed-loop index #i2 or #i3 is set for SBFD operation. As shown in FIG. 16, PUSCH closed loop index #i0 for non-SBFD operation is associated with PUSCH closed loop index #i1 for SBFD operation, and as shown in FIG. The PUSCH closed-loop index #i1 for operation may be associated with the PUSCH closed-loop index #i3 for SBFD operation.

Similarly, if, for example, two PUCCH-PC-AdjustmentStates is not set, i.e., a single PUCCH closed-loop index #i0 is configured for non-SBFD operation, it means that the PUCCH closed-loop index #i1 or #i2 is Implicitly meaning that it is configured for SBFD operation, PUCCH closed loop index #i0 for non-SBFD operation may be associated with PUCCH closed loop index #i1 or #i2 for SBFD operation. Note that the wording "#i1 or #i2" is used because it is not certain whether the PUCCH closed loop for SBFD operation starts from i2 or i1.

Also, for example, if two PUCCH-PC-AdjustmentStates is set, that is, if PUCCH closed-loop index #i0 and #i1 are set for non-SBFD operation, it means that PUCCH closed-loop index #i2 or #i3 is set for SBFD operation. Implicitly means that the PUCCH closed-loop index #i0 for non-SBFD operation is associated with the PUCCH closed-loop index #i1 for SBFD operation, and the PUCCH closed-loop index #i1 for non-SBFD operation may be associated with PUCCH closed loop index #i3 for SBFD operation.

Here, the one-to-one mapping may be defined by specifications, semi-statically configured by RRC configuration, etc., dynamically notified by DCI notification, etc., or determined by the UE according to predetermined rules. . Additionally, one-to-one mapping may be explicitly or implicitly defined, configured, notified, or applied. In addition, multiple different one-to-one mappings are defined, and which one-to-one mapping is applied is either defined by the specifications, semi-statically set by RRC settings, or dynamically notified by DCI notifications, etc. or may be determined by the UE according to predetermined rules. Further, which one-to-one mapping is applied may be explicitly or implicitly defined, set, notified, or applied.

According to Alt-c, for non-SBFD operation, the existing closed-loop configuration can be applied to provide a closed-loop for SBFD operation and a closed-loop for non-SBFD operation, and PUSCH and/or PUCCH transmission by the UE via DCI. It becomes possible to dynamically control power.

(Problem 2)
As issue 2, mapping between uplink transmit beam indexes such as SRI and/or PUCCH spatial relation info and PUSCH and/or PUCCH closed loop indexes may be considered.

<Alt-1>
In Alt-1, one SRI and/or uplink transmit beam index such as PUCCH spatial relation info is mapped to one PUSCH and/or PUCCH closed loop index for either non-SBFD operation or SBFD operation. It's okay. For example, each candidate value of the sri-PUSCH-ClosedLoopIndex field in the SRI-PUSCH-PowerControl IE may be a PUSCH closed-loop index for either non-SBFD operation or SBFD operation. Similarly, each candidate value of the pucch-ClosedLoopIndex-r17 field in the PUCCH-PowerControlSetInfo-r17 IE may be a PUCCH closed-loop index for either non-SBFD operation or SBFD operation.

Here, for example, when Alt-a is applied to problem 1 mentioned above, each candidate value of the sri-PUSCH-ClosedLoopIndex field and/or the pucch-ClosedLoopIndex-r17 field is still the same as that of {i0, i1}. You can leave it as is. For example, as shown in FIG. 17, SRI #m may be mapped to PUSCH closed loop #i0 for non-SBFD operation, and SRI #n may be mapped to PUSCH closed loop #i1 for SBFD operation.

Alternatively, when Alt-b is applied to problem 1 above, each candidate value of the sri-PUSCH-ClosedLoopIndex field and/or pucch-ClosedLoopIndex-r17 field is set to {i0, i1, i2, i3}. It can be. For example, each candidate value of the sri-PUSCH-ClosedLoopIndex field can be {i0, i1, i2, i3}, as shown in FIG. For example, as shown in FIG. 19, SRI #m may be mapped to PUSCH closed loop #i0 for non-SBFD operation, and SRI #n may be mapped to PUSCH closed loop #i3 for SBFD operation. Furthermore, when Alt-b is applied to problem 1 mentioned above, the following several cases can be considered.

- In the case where twoPUSCH-PC-AdjustmentStates is not set and only one PUSCH closed loop is set for SBFD operation, the candidate value of sri-PUSCH-ClosedLoopIndex is {i0, i1} or { i0, i2}. Note that it is not known whether the PUSCH closed loop for SBFD operation starts from i2 or i1.

- In the case where twoPUSCH-PC-AdjustmentStates is not set and two PUSCH closed loops are set for SBFD operation, the candidate value of sri-PUSCH-ClosedLoopIndex is {i0, i1, i2} or { i0, i2, i3}. Note that it is not known whether the PUSCH closed loop for SBFD operation starts from i2 or i1.

- In the case where twoPUSCH-PC-AdjustmentStates is set and only one PUSCH closed loop is set for SBFD operation, the candidate value of sri-PUSCH-ClosedLoopIndex is {i0, i1, i2}. sell.

- In the case where two PUSCH-PC-AdjustmentStates is set and two PUSCH closed loops are set for SBFD operation, the candidate value of sri-PUSCH-ClosedLoopIndex is {i0, i1, i2, i3}. sell.

Similarly, for example, each candidate value of pucch-ClosedLoopIndex-r17 can be {i0, i1, i2, i3}. In this case as well, the following several cases may be considered.

- In the case where two PUCCH-PC-AdjustmentStates is not set and only one PUCCH closed loop is set for SBFD operation, the candidate value of pucch-ClosedLoopIndex-r17 is {i0, i1} or { i0, i2}. Note that it is not known whether the PUCCH closed loop for SBFD operation starts from i2 or i1.

- In the case where two PUCCH-PC-AdjustmentStates is not set and two PUCCH closed loops are set for SBFD operation, the candidate value of pucch-ClosedLoopIndex-r17 is {i0, i1, i2} or { i0, i2, i3}. Note that it is not known whether the PUCCH closed loop for SBFD operation starts from i2 or i1.

- In the case where two PUCCH-PC-AdjustmentStates is set and only one PUCCH closed loop is set for SBFD operation, the candidate value of pucch-ClosedLoopIndex-r17 is {i0, i1, i2}. sell.

- In the case where two PUCCH-PC-AdjustmentStates is set and two PUCCH closed loops are set for SBFD operation, the candidate value of pucch-ClosedLoopIndex-r17 is {i0, i1, i2, i3}. sell.

Furthermore, the following various modifications may be envisaged.
・Modification #1
If the SRI is mapped to the PUSCH closed loop index for non-SBFD operation, the UE may not assume that the SRI is signaled for PUSCH on the SBFD.

・Modification #2
If the SRI is mapped to the PUSCH closed loop index for SBFD operation, the UE may not assume that the SRI is signaled for PUSCH on non-SBFD.

・Modification #3
The UE does not have to assume DCI formats that schedule PUSCH on non-SBFD and other DCI formats that schedule PUSCH on SBFD due to the SRI field reporting the same TPC loop index.

・Modification #4
The UE does not have to assume DCI formats for scheduling PUSCH on non-SBFD and other DCI formats for scheduling PUSCH on non-SBFD due to the SRI field reporting different TPC loop indexes.

・Modification #5
The UE does not have to assume the DCI format for scheduling PUSCH on SBFD and other DCI formats for scheduling PUSCH on SBFD due to the SRI field reporting different TPC loop indexes.

・Modification #6
If two PUCCH resources are configured or notified by the same PUCCH spatial relation info, the UE assumes a DCI format that notifies PUCCH resources on non-SBFD and another DCI format that notifies PUCCH resources on SBFD. You don't have to.

・Variation #7
If two PUCCH resources are configured or notified by different PUCCH spatial relation info, the UE assumes a DCI format that notifies the PUCCH resource on a non-SBFD and another DCI format that notifies the PUCCH resource on a non-SBFD. You don't have to.

・Variation #8
When two PUCCH resources are configured or notified by different PUCCH spatial relation info, the UE does not assume the DCI format that reports the PUCCH resource on the SBFD and the other DCI format that reports the PUCCH resource on the SBFD. It's okay.

Note that Modifications #3 to #8 may be applicable to cases where any PUSCH and/or PUCCH closed loop is for SBFD operation or non-SBFD operation, or is transparent or non-transparent.

According to Alt-1, an example mapping between uplink transmit beam index, such as SRI and/or PUCCH spatial relation info, and PUSCH and/or PUCCH closed loop index may be provided.

<Alt-2>
In Alt-2, the uplink transmit beam index such as one SRI and/or PUCCH spatial relation info is one PUSCH and/or PUCCH closed loop index for non-SBFD operation and one PUSCH and/or PUCCH closed loop index for SBFD operation. PUCCH closed loop index. For example, as shown in FIG. 20, SRI #m is mapped to PUSCH closed loop #i0 for non-SBFD operation and PUSCH closed loop #i3 for SBFD operation, and SRI #n is mapped to PUSCH closed loop #i1 for non-SBFD operation. and PUSCH closed loop #i2 for SBFD operation.

For example, a case can be assumed in which SRI is notified in DCI format 0_1/0_2 for scheduling PUSCH, or a case in which PUCCH resources are notified or determined for PUCCH according to specific PUCCH spatial relation info. In these cases, if the PUSCH and/or PUCCH is on the SBFD, the associated PUSCH and/or PUCCH closed-loop index for SBFD operation may be applied to the PUSCH and/or PUCCH power calculation. On the other hand, if the PUSCH and/or PUCCH is on a non-SBFD, the associated PUSCH and/or PUCCH closed-loop index for non-SBFD operation may be applied to the PUSCH and/or PUCCH power calculation.

For example, the following Opt-a and Opt-b may be executed for DCI format 0_1/0_2 in which the TPC adjustment command field exists. In Opt-a, if the scheduled PUSCH is on SBFD, the notified adjustment may be applied only to the PUSCH closed-loop index for the SBFD operation associated with the notified SRI. On the other hand, if the scheduled PUSCH is on a non-SBFD, the notified adjustment may be applied only to the PUSCH closed-loop index for non-SBFD operations associated with the notified SRI.

Also, in Opt-b, regardless of whether the scheduled PUSCH is on an SBFD or a non-SBFD, the advertised adjustment is the PUSCH closed-loop index for SBFD operations associated with the advertised SRI and It may be applied to the PUSCH closed loop index for operation.

Furthermore, for example, the following Opt-a and Opt-b may be executed for DCI format 1_1/1_2 in which the TPC adjustment command field exists. In Opt-a, when the notified PUCCH is on SBFD, the notified adjustment is applied only to the PUCCH closed loop index for SBFD operation related to the PUCCH spatial relation info of the notified PUCCH resource. Good too. On the other hand, if the notified PUCCH is on a non-SBFD, the notified adjustment may be applied only to the PUCCH closed loop index for non-SBFD operations associated with the PUCCH spatial relation info of the notified PUCCH resource. good.

In addition, in Opt-b, regardless of whether the notified PUCCH is on an SBFD or a non-SBFD, the notified adjustment is made on the PUCCH for SBFD operation related to the PUCCH spatial relation info of the notified PUCCH resource. It may be applied to the closed loop index and the PUCCH closed loop index for non-SBFD operations.

For example, in the example shown in FIG. 21, the TPC adjustment command field exists in DCI #1 and DCI #2. In Opt-a, the adjustment notified by DCI #1 may be applied only to PUSCH closed loop #i3, and the adjustment notified by DCI #2 may be applied only to PUSCH closed loop #i1. On the other hand, in Opt-b, the adjustment notified by DCI #1 is applied only to PUSCH closed loop #i0, #i3, and the adjustment notified by DCI #2 is applied only to PUSCH closed loop #i1, #i3. good.

<Alt-2-1>
The new parameters sri-PUSCH-ClosedLoopIndex-SBFD and/or pucch-ClosedLoopIndex-r17-SBFD are added to the PUSCH and/or PUC for the corresponding SBFD operation for the SRI and/or PUCCH spatial relation info. Notify CH closed loop index It may be used for. For example, as shown in FIG. 22, in the SRI-PUSCH-PowerControl IE, sri-PUSCH-ClosedLoopIndex is used to notify the PUSCH closed-loop index for non-SBFD operation, and sri-PUSCH-ClosedLoopIndex is used to notify the PUSCH closed-loop index for SBFD operation. sri-PUSCH-ClosedLoopIndex-SBFD may be set. One SRI can be mapped to a PUSCH closed-loop index for SBFD operations and a PUSCH closed-loop index for non-SBFD operations.

If sri-PUSCH-ClosedLoopIndex-SBFD and/or pucch-ClosedLoopIndex-r17-SBFD are not configured, the UE determines whether the SRI and/or PUCCH spatial relation info is PUSC on SBFD. Notified to H and/or PUCCH You don't have to assume that.

<Alt-2-2>
In addition, when Alt-c is applied to problem 1 mentioned above, that is, when the PUSCH and/or PUCCH closed loop for SBFD operation and non-SBFD operation is a one-to-one mapping, the PUSCH and/or PUCCH closed loop for non-SBFD operation Or when the PUCCH closed loop is signaled by the existing sri-PUSCH-ClosedLoopIndex and/or pucch-ClosedLoopIndex-r17, it may implicitly signal the PUSCH and/or PUCCH closed loop index for SBFD operation.

For example, if twoPUSCH-PC-AdjustmentStates is not set and sri-PUSCH-ClosedLoopIndex is set as i0, it means that SRI uses PUSCH closed loop index #i0 for non-SBFD operation and It may implicitly mean that it is mapped to PUSCH closed loop index #i1 or #i2. Note that it is not known whether the PUSCH closed loop index for SBFD operation starts from i2 or i1.

On the other hand, if twoPUSCH-PC-AdjustmentStates is set and sri-PUSCH-ClosedLoopIndex is set as i0 or i1, it means that the SRI is the PUSCH closed loop index #i0 or #i1 for non-SBFD operation; It may implicitly mean that it is mapped to PUSCH closed loop index #i2 or #i3 for SBFD operation. For example, in the example shown in FIG. 23, SRI#m is associated with PUSCH closed-loop index #i0 for non-SBFD operation and PUSCH closed-loop index #i2 for SBFD operation, and SRI#n is associated with PUSCH closed-loop index #i2 for non-SBFD operation. PUSCH closed-loop index #i1 for SBFD operation and PUSCH closed-loop index #i3 for SBFD operation. Note that the specifications of SRI-PUSCH-PowerControl are not affected.

Similarly, for example, if twoPUCCH-PC-AdjustmentStates is not set and pucch-ClosedLoopIndex-r17 is set as i0, it means that the PUCCH resource is the PUCCH closed-loop index #i0 for non-SBFD operation; It may implicitly mean that it is mapped to PUCCH closed loop index #i1 or #i2 for SBFD operation. Note that it is not known whether the PUCCH closed loop index for SBFD operation starts from i2 or i1.

On the other hand, if twoPUSCH-PC-AdjustmentStates is set and pucch-ClosedLoopIndex-r17 is set as i0 or i1, it means that the PUCCH resource is configured as PUCCH closed loop index #i0 or #i1 for non-SBFD operation. , may implicitly mean being mapped to PUCCH closed loop index #i2 or #i3 for SBFD operation.

(Problem 3)
As problem 3, the mapping relationship between the Configured Grant (CG) PUSCH settings and the PUSCH closed loop index may be considered.

<Alt-1>
In Alt-1, the CG PUSCH configuration may be configured with one PUSCH closed-loop index for either SBFD operation or non-SBFD operation. For example, each candidate value of the powerControlLoopToUse field in the ConfiguredGrantConfig IE may be PUSCH closed loop for SBFD operation or PUSCH closed loop for non-SBFD operation. The explanation in Alt-2 of problem 2 can be reused by replacing sri-PUSCH-ClosedLoopIndex with powerControlLoopToUse.

That is, each candidate value of the powerControlLoopToUse field in the ConfiguredGrantConfig IE may be a PUSCH closed loop index for either non-SBFD operation or SBFD operation. For example, when Alt-a is applied to problem 1 described above, each candidate value of the powerControlLoopToUse field may remain {i0, i1}.

Alternatively, when Alt-b is applied to problem 1 described above, each candidate value of the powerControlLoopToUse field can be {i0, i1, i2, i3}.

<Alt-2>
In Alt-2, the CG PUSCH configuration may be configured with one PUSCH closed-loop index for SBFD operation and one PUSCH closed-loop index for non-SBFD operation. For example, a new parameter powerControlLoopToUse-SBFD field may be utilized to signal the corresponding PUSCH closed loop index for SBFD operation on CG PUSCH. For example, in the ConfiguredGrantConfig IE, even if powerControlLoopToUse for notifying the PUSCH closed-loop index for non-SBFD operation and powerControlLoopToUse-SBFD for notifying the PUSCH closed-loop index for SBFD operation are set, Good. One CG PUSCH can be mapped to a PUSCH closed-loop index for SBFD operation and a PUSCH closed-loop index for non-SBFD operation.

If powerControlLoopToUse-SBFD is not configured, the UE does not need to assume that CG PUSCH is notified for PUSCH on SBFD.

In addition, when Alt-c is applied to problem 1 mentioned above, that is, when the PUSCH closed loop for SBFD operation and non-SBFD operation is a one-to-one mapping, the PUSCH closed loop for non-SBFD operation is Once signaled, it may implicitly signal the PUSCH closed loop index for SBFD operation. Note that there is no impact on the specification for powerControlLoopToUse.

In proposal 2, the UE may set the transmit power in SBFD operation according to the closed loop for SBFD, and may set the transmit power in non-SBFD operation according to the closed loop for non-SBFD. Here, the closed loop for SBFD and/or the closed loop for non-SBFD may be defined by specifications, semi-statically configured by RRC settings, or dynamically notified by DCI notification or the like. Further, the closed loop for SBFD and/or the closed loop for non-SBFD may be specified, configured, notified, or applied explicitly or implicitly.

The UE may transmit an uplink channel with closed-loop transmission power for SBFD in SBFD operation, and may transmit an uplink channel with closed-loop transmission power for non-SBFD in non-SBFD operation. For example, related to problem 1, the total number of closed loops is configured, and the UE configures the transmit power in SBFD operation according to the closed loop for SBFD among the configured total number of closed loops. The transmit power in non-SBFD operation may be set according to the closed loop for non-SBFD.

Also, related to issue 2, the UE may set the transmit power in SBFD operation and set the transmit power in non-SBFD operation according to the mapping between the uplink transmit beam and the closed-loop index. Also, related to issue 3, the UE configures the transmit power in SBFD operation and configures the transmit power in non-SBFD operation according to the mapping between the uplink shared channel configuration and the closed loop index in the configured grant. It's okay.

On the other hand, the gNB may set the transmission power in the SBFD operation to the UE using the closed loop for SBFD, and may set the transmission power in the non-SBFD operation to the UE using the closed loop for non-SBFD. Here, the closed loop for SBFD and/or the closed loop for non-SBFD may be defined by specifications, semi-statically configured by RRC settings, or dynamically notified by DCI notification or the like. Further, the closed loop for SBFD and/or the closed loop for non-SBFD may be specified, configured, notified, or applied explicitly or implicitly.

The gNB may receive an uplink channel transmitted from the UE with a transmission power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE with transmission power for non-SBFD in non-SBFD operation. For example, in relation to problem 1, the total number of closed loops is set, and the gNB sets the transmission power in the SBFD operation according to the closed loop for SBFD among the set total number of closed loops. The transmit power in non-SBFD operation may be set according to the closed loop for non-SBFD.

Also, related to issue 2, the gNB may set the transmit power in SBFD operation and set the transmit power in non-SBFD operation according to the mapping between the uplink transmit beam and the closed-loop index. Also, related to issue 3, the gNB configures the transmit power in SBFD operation and configures the transmit power in non-SBFD operation according to the mapping between the uplink shared channel configuration and the closed loop index in the configured grant. It's okay.

Note that the UE may report the UE capability regarding whether to support separate PUSCH and/or PUCCH closed loops for SBFD and non-SBFD operations to the gNB. The gNB may determine whether to perform separate PUSCH and/or PUCCH closed-loop control for SBFD operation and non-SBFD operation based on the acquired UE capability. The UE may also report the UE capability to the gNB regarding whether one SRI is simultaneously mapped to the PUSCH closed loop for SBFD operation and non-SBFD operation. Additionally, the UE may report to the gNB the UE capability regarding whether one PUCCH spatial relationship info is mapped to the PUCCH closed loop of SBFD operation and non-SBFD operation at the same time.

Thus, in Proposal 2, different closed loops are applied to SBFD operations and non-SBFD operations. Therefore, it becomes possible to dynamically notify the UE of different PUSCH and/or PUCCH transmission powers in each of SBFD operation and non-SBFD operation, and it is possible to generate inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the

[Proposal 3]
In proposal 3, the UE transmits the uplink channel in SBFD operation with the transmit power set according to the transmit power formula for SBFD operation, and the UE transmits the uplink channel in SBFD operation with the transmit power set according to the transmit power formula for non-SBFD operation. The uplink channel in operation may be transmitted.

(Option 1)
In option 1, a scaling factor for PUSCH and/or PUCCH transmit power calculation for SBFD operation may be applied. For example, in the example shown in FIG. 24, the PUSCH and/or PUCCH transmission power for non-SBFD operation by existing NR may be increased by multiplication with a scaling factor.

For example, the transmission power of PUSCH (P _{PUSCH, b, f, c} (i, j, q _d , l)) may be expressed by the following formula (3).

In equation (3), the scaling factor β for calculating PUSCH transmission power for SBFD operation is multiplied by the second argument of the min function in equation (1) for calculating PUSCH transmission power described above.

In another example, the transmission power of PUSCH (P _{PUSCH, b, f, c} (i, j, q _d , l)) may be expressed by the following formula (4).

In formula (4), the output of the min function of the above-mentioned PUSCH transmission power calculation formula (1) is multiplied by the scaling factor β for calculating PUSCH transmission power for SBFD operation. Note that when the scaling factor β is greater than 1, equation (4) may not be applicable.

In still another example, the transmission power of PUSCH (P _{PUSCH, b, f, c} (i, j, q _d , l)) may be expressed by the following formula (5).

In equation (5), the output of the min function of the above-mentioned PUSCH transmission power calculation equation (1) is multiplied by the scaling factor β for calculating the PUSCH transmission power for SBFD operation, and the product and P _{CMAX,f , c} (i) is set.

Note that the above-mentioned equations (3) to (5) relate to the calculation of PUSCH transmission power, but the scaling factor β may be similarly applied to the calculation equation of PUCCH transmission power.

Here, the scaling factor β is defined by the specifications, semi-statically set by RRC settings, etc., dynamically notified by DCI notifications, or specified by a specific rule (for example, PUSCH on SBFD). RB size and/or PUSCH repetition number, etc.). Further, the scaling factor β may be explicitly or implicitly defined, set, notified, or applied.

(Option 2)
In option 2, a power offset for PUSCH and/or PUCCH transmit power calculation for SBFD operation may be applied. For example, in the example shown in FIG. 25, the PUSCH and/or PUCCH transmission power for non-SBFD operation by existing NR may be increased by addition with a power offset.

For example, the transmission power of PUSCH (P _{PUSCH, b, f, c} (i, j, q _d , l)) may be expressed by the following equation (6).

In formula (6), the power offset ∇ for calculating the PUSCH transmission power for SBFD operation is added to the second argument of the min function of the above-mentioned PUSCH transmission power calculation formula (1).

In another example, the transmission power of PUSCH (P _{PUSCH, b, f, c} (i, j, q _d , l)) may be expressed by the following formula (7).

In equation (7), the power offset ∇ for calculating the PUSCH transmission power for SBFD operation is added to the output of the min function of the above-mentioned PUSCH transmission power calculation equation (1). Note that when the power offset ∇ is larger than 0, equation (7) may not be applicable.

In still another example, the transmission power of PUSCH (P _{PUSCH, b, f, c} (i, j, q _d , l)) may be expressed by the following formula (8).

In equation (8), the power offset ∇ for calculating the PUSCH transmission power for SBFD operation is added to the output of the min function of the above-mentioned PUSCH transmission power calculation equation (1), and the sum and P _{CMAX,f , c} (i) is set.

Note that the above-mentioned equations (6) to (8) relate to the calculation of PUSCH transmission power, but the power offset ∇ may be similarly applied to the calculation equation of PUCCH transmission power.

Here, the power offset ∇ is defined by the specification, semi-statically set by RRC settings, etc., dynamically notified by DCI notification etc., or specified by a specific rule (for example, PUSCH on SBFD). RB size and/or PUSCH repetition number, etc.). Further, the power offset ∇ may be explicitly or implicitly defined, set, notified, or applied.

(Option 3)
In option 3, a reference RB size for PUSCH and/or PUCCH transmit power calculation for SBFD operation may be used. For example, in the example shown in FIG. 26, instead of the actual RB size of PUSCH, a reference RB size corresponding to the uplink frequency band portion in SBFD may be used for PUSCH transmission power calculation for SBFD operation.

Specifically, the actual RB size of PUSCH on SBFD is not applied as the parameters M _{RB, b, f, c} ^PUSCH in calculation formula (1) of PUSCH transmission power, and option 3-1 or 3-2 is may be applied.

<Option 3-1>
In option 3-1, the parameters M _{RB, b, f, c} ^PUSCH are independent of the actual RB size of PUSCH on SBFD, such as the RB size of other PUSCH repeats on non-SBFD, if present. It's okay. The parameters M _{RB, b, f, c} ^PUSCH are defined by the specifications, semi-statically set by RRC settings, etc., dynamically notified by DCI notifications, or determined by specific rules (e.g. PUSCH RB size and/or PUSCH repetition number on SBFD). Furthermore, the parameters M _{RB, b, f, c} ^PUSCH may be explicitly or implicitly defined, configured, notified, or applied.

<Option 3-2>
In option 3-2, the parameters M _{RB, b, f, c} ^PUSCH are fixed RB size offset based on the actual PUSCH RB size, scaling factor based on the actual PUSCH RB size, offset based on the actual PUSCH RB size The value may depend on the actual RB size of PUSCH on the SBFD. A fixed RB size offset may be specified by the specification, set semi-statically such as by RRC configuration, dynamically notified such as by DCI notification, or specified by a specific rule (e.g. PUSCH on SBFD). RB size and/or PUSCH repetition number, etc.). Additionally, the fixed RB size offset may be explicitly or implicitly defined, configured, notified, or applied.

For example, the gNB may directly notify or set the RB size offset value. In addition, “fixed The mapping relationship to "RB size offset" is defined by the specification, semi-statically set by RRC settings, dynamically notified by DCI notifications, or determined by specific rules (for example, on SBFD). may be determined by the UE according to the PUSCH RB size and/or the number of PUSCH repetitions, etc.).

In addition, the scaling factor based on the actual PUSCH RB size may be specified by the specification, semi-statically set by RRC settings, etc., dynamically notified by DCI notification, etc., or determined by specific rules (e.g. , PUSCH on SBFD, RB size and/or PUSCH repetition number, etc.). Additionally, the fixed RB size offset may be explicitly or implicitly defined, configured, notified, or applied.

For example, the gNB may directly notify or set the scaling factor value. In addition, “scaling factor” can be calculated from “actual PUSCH RB size”, “ratio of actual PUSCH RB size to BWP size (or UL subband size on SBFD symbol/slot)”, and/or “PUSCH repetition number”. The mapping relationship to and/or the number of PUSCH repetitions, etc.).

Also, as a variant, considering that the downlink/uplink subband size is cell-specific, the parameters in options 1 to 3, i.e. the scaling factor in option 1, the power offset in option 2, and/or The reference RB size for option 3 may also be cell-specific or common to multiple UEs in a cell. In this case, for example, one common parameter for improving uplink power in SBFD operation may be applied. Alternatively, two common parameters may be applied, one parameter to improve uplink power in SBFD operation and one parameter to reduce uplink power in SBFD operation.

Also, as a variation, proposal 3 may be applied with common PUSCH and/or PUCCH closed loop constraints for SBFD and non-SBFD operations. Alternatively,

suggestions

2 and 3 may be applied together.

In proposal 3, the UE may set the transmission power in SBFD operation according to the power calculation formula for SBFD, and may set the transmission power in non-SBFD operation according to the power calculation formula for non-SBFD. Here, the power calculation formula for SBFD may be defined by specifications, semi-statically set by RRC settings, or dynamically notified by DCI notification or the like. Further, the power calculation formula for SBFD may be specified, set, notified, or applied explicitly or implicitly.

The UE may transmit an uplink channel with SBFD transmission power in SBFD operation, and may transmit an uplink channel with non-SBFD transmission power in non-SBFD operation. For example, the power calculation formula for SBFD may be derived by multiplying the power calculation formula for non-SBFD by a scaling factor. Further, the power calculation formula for SBFD may be derived by adding an offset value to the power calculation formula for non-SBFD. Further, the power calculation formula for SBFD may be calculated by applying the reference resource block size instead of the actual resource block size to the power calculation formula for non-SBFD.

On the other hand, the gNB may set the transmission power in the SBFD operation to the UE using the power calculation formula for SBFD, and may set the transmission power in the non-SBFD operation to the UE using the power calculation formula for non-SBFD. Here, the power calculation formula for SBFD may be defined by specifications, semi-statically set by RRC settings, or dynamically notified by DCI notification or the like. Further, the power calculation formula for SBFD may be specified, set, notified, or applied explicitly or implicitly.

The gNB may receive an uplink channel transmitted from the UE with a transmission power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE with transmission power for non-SBFD in non-SBFD operation. For example, the power calculation formula for SBFD may be derived by multiplying the power calculation formula for non-SBFD by a scaling factor. Further, the power calculation formula for SBFD may be derived by adding an offset value to the power calculation formula for non-SBFD. Further, the power calculation formula for SBFD may be calculated by applying the reference resource block size instead of the actual resource block size to the power calculation formula for non-SBFD.

Note that the UE may report the UE capability regarding whether to support the PUSCH and/or PUCCH power calculation formula adjusted for SBFD to the gNB.

As described above, in Proposal 3, different transmission power calculation formulas are applied to SBFD operation and non-SBFD operation. Therefore, it is possible to apply different PUSCH and/or PUCCH transmission power calculation formulas to the UE in SBFD operation and non-SBFD operation, and it is possible to cause inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the

<Hardware configuration>
It should be noted that the block diagram used to explain the above embodiment shows blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't. For example, a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.

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

Note that in the following description, the word "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in FIG. 27, or may be configured not to include some of the devices.

Each function in the base station 10 and user terminal 20 is performed by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and controls communication by the communication device 1004. This is realized by controlling at least one of data reading and writing in the memory 1002 and the storage 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, the baseband signal processing section 104, call processing section 105, etc. described above may be implemented by the processor 1001.

Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 401 of the user terminal 20 may be realized by a control program stored in the memory 1002 and operated on the processor 1001, and other functional blocks may be similarly realized. Although the various processes described above have been described as being executed by one processor 1001, they may be executed by two or more processors 1001 simultaneously or sequentially. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.

The memory 1002 is a computer-readable recording medium, and includes at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be done. Memory 1002 may be called a register, cache, main memory, or the like. The memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, or a magneto-optical disk (for example, a compact disk, a digital versatile disk, or a Blu-ray disk). (registered trademark disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The storage medium mentioned above may be, for example, a database including at least one of memory 1002 and storage 1003, a server, or other suitable medium.

The communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of. For example, the above-described transmitting/receiving antenna 101, amplifier section 102, transmitting/receiving section 103, transmission path interface 106, etc. may be realized by the communication device 1004. The transmitter/receiver 103 may be implemented as a transmitter 103a and a receiver 103b that are physically or logically separated.

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

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

The base station 10 and the user terminal 20 also 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). It may be configured to include hardware, and a part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.

Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information may include physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented using broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Further, RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

Each aspect/embodiment described in this disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is an integer or decimal number, for example)), FRA (Future Radio Access), NR (new Radio), New radio access ( NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802 Systems that utilize .16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, and that are extended, modified, created, and defined based on these. The present invention may be applied to at least one of the next generation systems. Furthermore, a combination of a plurality of systems may be applied (for example, a combination of at least one of LTE and LTE-A and 5G).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular order presented.

In some cases, the specific operations performed by the base station in this disclosure may be performed by its upper node. In a network consisting of one or more network nodes including a base station, various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (e.g., MME or It is clear that this could be done by at least one of the following: (conceivable, but not limited to) S-GW, etc.). In the above example, there is one network node other than the base station, but it may be a combination of multiple other network nodes (for example, MME and S-GW).

Information etc. (*Refer to the item "Information, Signal") can be output from the upper layer (or lower layer) to the lower layer (or upper layer). It may be input/output via multiple network nodes.

The input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to other devices.

Judgment may be made using a value expressed by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (for example, a predetermined value). (comparison with a value).

Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. In addition, notification of prescribed information (for example, notification of "X") is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.

Although the present disclosure has been described in detail above, it is clear for those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as determined by the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and is not intended to have any limiting meaning on the present disclosure.

Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of

Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal. Also, the signal may be a message. Further, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, or the like.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources may be indicated by an index.

The names used for the parameters mentioned above are not restrictive in any respect. Furthermore, the mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (e.g. PUCCH, PDCCH, etc.) and information elements may be identified by any suitable designation, the various names assigned to these various channels and information elements are in no way exclusive designations. isn't it.

In this disclosure, "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," " "access point", "transmission point", "reception point", "transmission/reception point", "cell", "sector", "cell group", " The terms "carrier", "component carrier", etc. may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services may also be provided by a remote radio head).The term "cell" or "sector" refers to a portion or the entire coverage area of a base station and/or base station subsystem that provides communication services in this coverage. refers to

In the present disclosure, the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.

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

A mobile station is defined by a person skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

At least one of the base station and the mobile station may be called a transmitting device, receiving device, communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving body refers to a movable object, and the moving speed is arbitrary. Naturally, this also includes cases where the moving body is stopped. The mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships and other watercraft. , including, but not limited to, airplanes, rockets, artificial satellites, drones (registered trademarks), multicopters, quadcopters, balloons, and objects mounted thereon. Further, the mobile object may be a mobile object that autonomously travels based on a travel command. It may be a vehicle (e.g. car, airplane, etc.), an unmanned moving object (e.g. drone, self-driving car, etc.), or a robot (manned or unmanned). good. Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Additionally, the base station in the present disclosure may be replaced by a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the functions that the base station 10 described above has. Further, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be replaced with side channels.

Similarly, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station 10 may have the functions that the user terminal 20 described above has.

FIG. 28 shows an example of the configuration of the vehicle 1. As shown in FIG. 28, the vehicle 1 includes a drive unit 2, a steering unit 3, an accelerator pedal 4, a brake pedal 5, a shift lever 6, left and right front wheels 7, left and right rear wheels 8, an axle 9, an electronic control unit 10, various It includes sensors 21 to 29, an information service section 12, and a communication module 13.

The drive unit 2 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

The steering unit 3 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

The electronic control unit 10 is composed of a microprocessor 31, memory (ROM, RAM) 32, and communication port (IO port) 33. Signals from various sensors 21 to 27 provided in the vehicle are input to the electronic control unit 10. The electronic control unit 10 may also be called an ECU (Electronic Control Unit).

The signals from the various sensors 21 to 28 include a current signal from the current sensor 21 that senses the motor current, a front wheel and rear wheel rotation speed signal obtained by the rotation speed sensor 22, and a front wheel rotation speed signal obtained by the air pressure sensor 23. and a rear wheel air pressure signal, a vehicle speed signal obtained by the vehicle speed sensor 24, an acceleration signal obtained by the acceleration sensor 25, an accelerator pedal depression amount signal obtained by the accelerator pedal sensor 29, and a signal obtained by the brake pedal sensor 26. These include a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 27, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 28.

The information service unit 12 controls various devices such as a car navigation system, audio system, speakers, television, and radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and these devices. It is composed of one or more ECUs. The information service unit 12 provides various multimedia information and multimedia services to the occupants of the vehicle 1 using information acquired from an external device via the communication module 13 or the like.

The information service unit 12 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device (for example, (display, speaker, LED lamp, touch panel, etc.).

The driving support system unit 30 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden. The system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 30 transmits and receives various information via the communication module 13, and realizes a driving support function or an automatic driving function.

The communication module 13 can communicate with the microprocessor 31 and the components of the vehicle 1 via the communication port. For example, the communication module 13 communicates via the communication port 33 with the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, which are included in the vehicle 1. Data is transmitted and received between the axle 9, the microprocessor 31 and memory (ROM, RAM) 32 in the electronic control unit 10, and the sensors 21-28.

The communication module 13 is a communication device that can be controlled by the microprocessor 31 of the electronic control unit 10 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication. The communication module 13 may be located either inside or outside the electronic control unit 10. The external device may be, for example, a base station, a mobile station, or the like.

The communication module 13 receives signals from the various sensors 21 to 28 described above that are input to the electronic control unit 10, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 12. At least one of the information based on the information may be transmitted to an external device via wireless communication. The electronic control unit 10, various sensors 21-28, information service unit 12, etc. may be called an input unit that receives input. For example, the PUSCH transmitted by the communication module 13 may include information based on the above input.

The communication module 13 receives various information (traffic information, signal information, inter-vehicle distance information, etc.) transmitted from external devices, and displays it on the information service section 12 provided in the vehicle. The information service unit 12 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 13). may be called.

The communication module 13 also stores various information received from external devices into a memory 32 that can be used by the microprocessor 31. Based on the information stored in the memory 32, the microprocessor 31 controls the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, and left and right rear wheels provided in the vehicle 1. 8, the axle 9, sensors 21 to 28, etc. may be controlled.

(Summary of embodiments)
As described above, according to one aspect of the present disclosure, the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first transmission power setting, and the first transmission power is set according to the second transmission power setting. a control unit configured to set a second transmission power in a non-SBFD operation, transmitting an uplink channel with the first transmission power in the SBFD operation, and transmitting an uplink channel with the second transmission power in the non-SBFD operation; A terminal having a transmitting unit for transmitting data is provided.

According to the above configuration, different transmission power control parameters are applied to SBFD operation and non-SBFD operation. Therefore, it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. can be reduced.

In one embodiment, the first transmit power setting and the second transmit power setting may be defined by separate transmit power setting information elements for the SBFD operation and the non-SBFD operation. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

In one embodiment, the first transmit power setting and the second transmit power setting are a first transmit power parameter for the SBFD operation and a first transmit power parameter for the non-SBFD operation in the same transmit power setting information element. and a second transmission power parameter. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

In one embodiment, the uplink channel may include one or more of an uplink shared channel, an uplink control channel, and a random access channel. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

Further, according to one aspect of the present disclosure, the first transmission power setting sets the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation to the terminal, and the second transmission power setting sets the terminal to perform non-SBFD operation. a control unit configured to set a second transmission power to a terminal in the SBFD operation; and a receiving unit for receiving an uplink channel transmitted from the terminal.

Further, according to one aspect of the present disclosure, the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first transmission power setting, and the first transmission power in non-SBFD operation is set according to the second transmission power setting. transmitting an uplink channel with the first transmit power in the SBFD operation and transmitting an uplink channel with the second transmit power in the non-SBFD operation; A wireless communication method performed by a terminal is provided.

Further, according to one aspect of the present disclosure, the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first closed loop, and the second transmission power in non-SBFD operation is set according to the second closed loop. and a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation. is provided.

According to the above configuration, different closed loops are applied to the SBFD operation and the non-SBFD operation. Therefore, it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. can be reduced.

In one embodiment, a total number of closed loops is set, and the control unit sets a first transmission power in the SBFD operation according to the first closed loop of the set total number of closed loops, and The second transmission power in the non-SBFD operation may be set according to the second closed loop among the total number of closed loops. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

In one embodiment, the controller sets the first transmit power in the SBFD operation and the second transmit power in the non-SBFD operation according to a mapping between an uplink transmit beam and a closed-loop index. Good too. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

In one embodiment, the controller configures a first transmission power in the SBFD operation according to a mapping between an uplink shared channel configuration and a closed-loop index of a configured grant, and configures a first transmission power in the SBFD operation and a second transmission power in the non-SBFD operation. You may also set the power. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

Further, according to one aspect of the present disclosure, the first closed loop sets the first transmission power in the SBFD (Subband non-overlapping Full Duplex) operation to the terminal, and the second closed loop sets the second transmission power in the non-SBFD operation. a control unit that sets a transmission power to a terminal; and a controller that receives an uplink channel transmitted from the terminal with the first transmission power in the SBFD operation, and receives an uplink channel transmitted from the terminal with the second transmission power in the non-SBFD operation. A base station is provided having a receiving unit for receiving a transmitted uplink channel.

Further, according to one aspect of the present disclosure, the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first closed loop, and the second transmission power in non-SBFD operation is set according to the second closed loop. and transmitting an uplink channel with the first transmit power in the SBFD operation and transmitting an uplink channel with the second transmit power in the non-SBFD operation. A wireless communication method is provided.

Further, according to one aspect of the present disclosure, the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first power calculation formula, and the first transmission power in non-SBFD operation is set according to the second power calculation formula. a control unit that sets a transmission power of 2; and a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits the uplink channel with the second transmission power in the non-SBFD operation. A terminal having the following is provided.

According to the above configuration, different transmission power calculation formulas are applied to SBFD operation and non-SBFD operation. Therefore, it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. can be reduced.

In one embodiment, the first power calculation formula may be derived by multiplying the second power calculation formula by a scaling factor. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

In one embodiment, the first power calculation formula may be derived by adding an offset value to the second power calculation formula. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

In one embodiment, the first power calculation formula may be calculated by applying a reference resource block size to the second power calculation formula. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of

Further, according to one aspect of the present disclosure, the first power calculation formula sets the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation to the terminal, and the second power calculation formula sets the first transmission power in the non-SBFD operation. a control unit configured to set a second transmission power to a terminal in the SBFD operation; and a receiving unit for receiving an uplink channel transmitted from the terminal.

Further, according to one aspect of the present disclosure, the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first power calculation formula, and the first transmission power in non-SBFD operation is set according to the second power calculation formula. transmitting an uplink channel with the first transmit power in the SBFD operation and transmitting an uplink channel with the second transmit power in the non-SBFD operation; A wireless communication method performed by a terminal is provided.

(Supplementary information on the embodiment)
As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of operations. "Judgment" and "decision" include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a "judgment" or "decision." In addition, "judgment" and "decision" refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access. (accessing) (e.g., accessing data in memory) may include considering something as a "judgment" or "decision." In addition, "judgment" and "decision" refer to resolving, selecting, choosing, establishing, comparing, etc. as "judgment" and "decision". may be included. In other words, "judgment" and "decision" may include regarding some action as having been "judged" or "determined." Further, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

The terms "connected", "coupled", or any variations thereof, refer to any connection or coupling, direct or indirect, between two or more elements and to each other. It may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled." The bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access." As used in this disclosure, two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.

The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applied standard.

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

As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.

"Means" in the configurations of each of the above devices may be replaced with "unit", "circuit", "device", etc.

Where "include", "including" and variations thereof are used in this disclosure, these terms, like the term "comprising," are inclusive. It is intended that Furthermore, the term "or" as used in this disclosure is not intended to be exclusive or.

A radio frame may be composed of one or more frames in the time domain. Each frame or frames in the time domain may be called a subframe. A subframe may also be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.

The numerology may be a communication parameter applied to the transmission and/or reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception. It may also indicate at least one of a specific filtering process performed by the device in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

A slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol.

For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. It's okay. In other words, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. It may be. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that long TTI (for example, normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1 ms, and short TTI (for example, short TTI, etc.) It may also be read as a TTI having the above TTI length.

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

Additionally, the time domain of an RB may include one or more symbols, and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

Note that one or more RBs include physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. May be called.

Additionally, a resource block may be configured by one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (also referred to as partial bandwidth) refers to a subset of consecutive common resource blocks (RB) for a certain numerology in a certain carrier. good. Here, the common RB may be specified by an RB index based on a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

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

The "maximum transmit power" described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power ( It may also mean the rated UE maximum transmit power).

In this disclosure, when articles are added by translation, such as a, an, and the in English, the present disclosure may include that the nouns following these articles are plural.

In the present disclosure, the term "A and B are different" may mean "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" and "coupled" may also be interpreted similarly to "different."

10 Wireless communication system 100 Base station (gNB)
200 Terminal (UE)

Claims

a control unit that sets a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first power calculation formula, and sets a second transmission power in a non-SBFD operation according to a second power calculation formula;
a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation;
A terminal with
The terminal according to claim 1, wherein the first power calculation formula is derived by multiplying the second power calculation formula by a scaling factor.
The terminal according to claim 1, wherein the first power calculation formula is derived by adding an offset value to the second power calculation formula.
The terminal according to claim 1, wherein the first power calculation formula is calculated by applying a reference resource block size to the second power calculation formula.
The first power calculation formula sets the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation to the terminal, and the second power calculation formula sets the second transmission power in non-SBFD operation to the terminal. a control unit;
a receiving unit that receives an uplink channel transmitted from the terminal with the first transmission power in the SBFD operation, and receives an uplink channel transmitted from the terminal with the second transmission power in the non-SBFD operation; and,
A base station with
Setting a first transmission power in an SBFD (Subband non-overlapping Full Duplex) operation according to a first power calculation formula, and setting a second transmission power in a non-SBFD operation according to a second power calculation formula;
transmitting an uplink channel with the first transmit power in the SBFD operation and transmitting an uplink channel with the second transmit power in the non-SBFD operation;
A wireless communication method performed by a terminal, comprising: