Terminal, base station and wireless communication method

Abstract

According to one embodiment of the present disclosure, a terminal is provided, comprising: a control unit, which sets a first transmission power in a subband non-overlapping full duplex (SBFD) operation according to a first closed loop, and sets a second transmission power in a non-SBFD operation according to a second closed loop; and a transmission unit, which transmits an uplink channel at the first transmission power in the SBFD operation, and transmits the uplink channel at the second transmission power in the non-SBFD operation.

Description

Technical Field

[0001] The present disclosure relates to a terminal, a base station, and a wireless communication method. Background Art

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) is standardized for the purpose of further high-speed data rates, low latency, etc. In addition, LTE-Advanced (3GPP Rel. 10-14) is standardized for the purpose of further increasing the capacity and sophistication of LTE (Release (Rel.) 8, 9 of the Third Generation Partnership Project (3GPP)).

[0003] Successor systems to LTE (also called, for example, fifth-generation mobile communication system (5G), 5G+ (plus), sixth-generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also being studied.

[0004] Prior art literature

[0005] Patent Literature

[0006] Non-Patent Document 1: “Initial Views on Release 18 NR” RP-210293, 3GPP TSG RANMeeting #91-e Electronic Meeting, March 16 -26, 2021 Summary of the invention

[0007] In future wireless communication systems (eg, NR), it is envisioned that a plurality of user terminals (user terminals, User Equipment (UE)) communicate in an environment of ultra-high density and high traffic volume.

[0008] Assume that in such an environment, uplink (UL) resources are insufficient compared to downlink (DL) resources.

[0009] However, in the NR specifications to date, there has been insufficient research into methods for increasing uplink resources. If this method cannot be properly controlled, there is a concern that system performance may be reduced, such as increased latency and reduced coverage performance.

[0010] Therefore, one of the objects of the present disclosure is to provide a terminal, a base station, and a wireless communication method that improve resource utilization efficiency.

[0011] One method of the present disclosure relates to a terminal, comprising: a control unit, which sets a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first transmission power setting, and sets a second transmission power in a non-SBFD operation according to a second transmission power setting; and a transmission unit, which transmits an uplink channel at the first transmission power in the SBFD operation, and transmits the uplink channel at the second transmission power in the non-SBFD operation.

[0012] Another embodiment of the present disclosure relates to a terminal, comprising: a control unit, which sets a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first closed loop, and sets a second transmission power in a non-SBFD operation according to a second closed loop; and a transmission unit, which transmits an uplink channel at the first transmission power in the SBFD operation, and transmits the uplink channel at the second transmission power in the non-SBFD operation.

[0013] Another embodiment of the present disclosure relates to a terminal, comprising: a control unit, which 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; and a transmission unit, which transmits an uplink channel at the first transmission power in the SBFD operation, and transmits the uplink channel at the second transmission power in the non-SBFD operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a block diagram showing the functional structure of a base station (gNB) according to an embodiment of the present disclosure.

[0015] Figure 2 It is a block diagram showing a functional structure of a terminal (UE) according to an embodiment of the present disclosure.

[0016] Figure 3A as well as Figure 3B The figure shows an example of configuration of radio resources of XDD (Cross Division Duplex) or SBFD (Subband non-overlapping Full Duplex) according to an embodiment of the present disclosure.

[0017] Figure 4 is a diagram illustrating an XDD operation or a SBFD operation according to an embodiment of the present disclosure.

[0018] Figure 5A as well as Figure 5B is a diagram showing TDD and SBFD according to an embodiment of the present disclosure.

[0019] Figure 6A to Figure 6E is a diagram showing a pure time unit and a SBFD time unit according to an embodiment of the present disclosure.

[0020] Fig. 7A as well as Figure 7B is a diagram illustrating inter-link interference (CLI) according to an embodiment of the present disclosure.

[0021] Fig. 8A as well as Figure 8B is a diagram illustrating a PUSCH-Config information element (IE) according to an embodiment of the present disclosure.

[0022] Fig.9A as well as Fig. 9B is a diagram showing a PUSCH-Config IE according to an embodiment of the present disclosure.

[0023] Fig. 10A as well as Fig. 10B is a diagram showing a PUSCH-PowerControl IE according to an embodiment of the present disclosure.

[0024] Fig.11A as well as Fig. 11B is a diagram showing a PUCCH-PowerControl IE based on an embodiment of the present disclosure.

[0025] Fig. 12A as well as Fig. 12B is a diagram showing a RACH-ConfigGeneric IE according to an embodiment of the present disclosure.

[0026] Fig.13A as well as Fig. 13B is a diagram illustrating a RACH-ConfigGenericTwoStepRA-r16 IE according to an embodiment of the present disclosure.

[0027] Fig.14A as well as Fig. 14B is a diagram showing a PUSCH-ConfigCommon IE according to an embodiment of the present disclosure.

[0028] Fig.15 is a diagram showing a PUSCH-PowerControl IE according to an embodiment of the present disclosure.

[0029] Fig.16 is a diagram showing a closed-loop mapping according to an embodiment of the present disclosure.

[0030] Fig.17 is a diagram showing a closed-loop mapping according to an embodiment of the present disclosure.

[0031] Fig.18 is a diagram showing a SRI-PUSCH-PowerControl IE according to an embodiment of the present disclosure.

[0032] Fig.19 is a diagram showing a closed-loop mapping according to an embodiment of the present disclosure.

[0033] Fig. 20 is a diagram showing a closed-loop mapping according to an embodiment of the present disclosure.

[0034] Fig.21 is a diagram showing a closed-loop mapping according to an embodiment of the present disclosure.

[0035] Fig. 22 is a diagram showing a SRI-PUSCH-PowerControl IE according to an embodiment of the present disclosure.

[0036] Fig.23 is a diagram showing a closed-loop mapping according to an embodiment of the present disclosure.

[0037] Fig.24 is a diagram illustrating power adjustment according to an embodiment of the present disclosure.

[0038] Fig.25 is a diagram illustrating power adjustment according to an embodiment of the present disclosure.

[0039] Fig.26 is a diagram illustrating power adjustment according to an embodiment of the present disclosure.

[0040] Fig. 27 It is a block diagram showing the hardware structure of a base station and a terminal according to an embodiment of the present disclosure.

[0041] Fig.28 Detailed description of the invention is a block diagram showing a hardware structure of a vehicle according to an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0043] (Wireless Communication System)

[0044] The structure of a wireless communication system according to an embodiment of the present disclosure is described below. In the wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof. The wireless communication system is a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth generation mobile communication system New Radio (5GNR), and their subsequent wireless communication systems.

[0045] In addition, the wireless communication system can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple Radio Access Technologies (Radio Access Technology (RAT)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0046] In EN-DC, the base station (eNB) of LTE (E-UTRA) is the master node (MN), and the base station (gNB) of NR is the secondary node (SN). In NE-DC, the base station (gNB) of NR is the MN, and the base station (eNB) of LTE (E-UTRA) is the SN.

[0047] The wireless communication system can also support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity between MN and SN, both of which are NR base stations (gNB) (NR-NR Dual Connectivity (NR-NR Dual Connectivity (NN-DC)))).

[0048] The wireless communication system may also include a base station forming a macro cell C1 with a relatively wide coverage, and a base station configured in the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. A terminal (UE) may also be located in at least one cell. The configuration and number of each cell and terminal are not limited to a specific method.

[0049] The terminal may be connected 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).

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

[0051] Furthermore, the terminal may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0052] Multiple base stations can also be connected by wire (for example, optical fiber based on Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (for example, NR communication). For example, when NR communication between two base stations is used as a backhaul, the base station equivalent to the upper station can also be called an Integrated Access Backhaul (IAB) donor, and the base station equivalent to a relay station (relay) can also be called an IAB node.

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

[0054] The terminal may also be a terminal that supports at least one of communication modes such as LTE, LTE-A, 5G, and 6G.

[0055] In wireless communication systems, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) may also 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), etc. may also be used.

[0056] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system, other radio access schemes (eg, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used in the UL and DL radio access schemes.

[0057] In a wireless communication system, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each terminal, a broadcast channel (Physical Broadcast Channel (PBCH))), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. can also be used as a downlink channel.

[0058] In addition, in a wireless communication system, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each terminal, an uplink control channel (Physical Uplink Control Channel (PUCCH))), a random access channel (Physical Random Access Channel (PRACH)), etc. can also be used as uplink channels.

[0059] User data, high-layer control information, system information block (SIB), etc. are transmitted through PDSCH. User data, high-layer control information, etc. can also be transmitted through PUSCH. In addition, Master Information Block (MIB) can also be transmitted through PBCH.

[0060] The PDCCH may also transmit lower layer control information. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information of at least one of the PDSCH and the PUSCH.

[0061] In addition, the DCI for scheduling the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI for scheduling the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be rewritten as DL data, and the PUSCH may also be rewritten as UL data.

[0062] In the detection of PDCCH, control resource set (CORESET) and search space can also be used. CORESET corresponds to the resources for searching DCI. Search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. UE can also monitor the CORESET associated with a search space based on the search space setting.

[0063] A search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space (SS) set. In addition, the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" and the like in the present disclosure may also be rewritten mutually.

[0064] Through PUCCH, uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (e.g., also called hybrid automatic repeat request confirmation (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) can also be sent. Through PRACH, a random access preamble code for establishing a connection with a cell can also be sent.

[0065] In addition, in the present disclosure, various channels may be expressed without the word “Physical” at the beginning.

[0066] In wireless communication systems, synchronization signals (Synchronization Signal (SS)), downlink reference signals (Downlink Reference Signal (DL-RS)), etc. can also be sent. In wireless communication systems, cell-specific reference signals (Cell-specific Reference Signal (CRS)), channel state information reference signals (Channel State Information Reference Signal (CSI-RS)), demodulation reference signals (DeModulation Reference Signal (DMRS)), positioning reference signals (Positioning Reference Signal (PRS)), phase tracking reference signals (Phase Tracking Reference Signal (PTRS)), etc. can also be sent as DL-RS.

[0067] 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 also be referred to as SS / PBCH block, SS block (SS Block (SSB)), etc. In addition, SS, SSB, etc. may also be referred to as reference signals.

[0068] In addition, in wireless communication systems, as an uplink reference signal (UL-RS), a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may also be sent. In addition, DMRS may also be called a UE-specific reference signal (UE-specific Reference Signal).

[0069] (Device structure)

[0070] Next, the functional configuration examples of the base station (gNB) 100 and the terminal (UE) 200 that perform the processing and operations described below are described. The gNB 100 and the UE 200 include functions for implementing the embodiments described below. However, the gNB 100 and the UE 200 may each have only a part of the functions in the embodiments.

[0071] (gNB100)

[0072] Figure 1 is a diagram showing an example of the functional structure of gNB100. Figure 1 As shown, gNB100 has a receiving unit 101, a sending unit 102 and a control unit 103. Figure 1 The functional configuration shown is merely an example, and any functional divisions and names of functional units may be used as long as the operations according to the embodiments of the present invention can be implemented.

[0073] The receiving unit 101 includes a function of receiving various signals transmitted from the UE 200 and acquiring, for example, higher layer information based on 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.

[0074] The control unit 103 stores the preset setting information and various setting information sent to the UE 200 in the storage device, and reads it from the storage device as needed. In addition, the control unit 103 performs processing related to communication with the UE 200. The functional unit related to signal transmission in the control unit 103 may be included in the transmission unit 102, and the functional unit related to signal reception in the control unit 103 may be included in the reception unit 101.

[0075] (UE200)

[0076] Figure 2 2 is a diagram showing an example of a functional structure of UE 200. Figure 2 As shown, UE 200 has a sending unit 201 , a receiving unit 202 and a control unit 203 . Figure 2 The functional configuration shown is merely an example, and any functional divisions and names of functional units may be used as long as the operations according to the embodiments of the present invention can be implemented.

[0077] The transmitting unit 201 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 202 receives various signals wirelessly and obtains a higher layer signal based on the received physical layer signal. In addition, the receiving unit 202 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals, etc. transmitted from the gNB 100.

[0078] The control unit 203 stores various setting information received from the gNB 100 through the receiving unit 202 in the storage device, and reads it from the storage device as needed. In addition, the control unit 203 performs processing related to communication with the gNB 100. The functional unit related to signal transmission in the control unit 203 may be included in the transmitting unit 201, and the functional unit related to signal reception in the control unit 203 may be included in the receiving unit 202.

[0079] (SBFD operation)

[0080] If the time ratio of transmission and reception based on time division duplex (TDD) up to Rel.16 is considered (for example, DL:UL=4:1), consider the situation where the transmission opportunities of UL signals / channels become fewer relative to the reception opportunities of DL signals / channels. In such a situation, there is a concern that UE200 may not be able to frequently transmit UL signals / channels, resulting in transmission delays of important UL signals / channels. In addition, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also a concern about signal / channel congestion in the UL transmission opportunities. Furthermore, in TDD, since the time resources that can transmit UL signals / channels are limited, for example, the application of UL coverage enhancement technology based on repeated transmission (repetition) also becomes restrictive.

[0081] In future wireless communication systems (for example, Rel. 18 and later), introduction of a division duplex method combining TDD and frequency division duplex (FDD) for UL and DL is under study.

[0082] This division duplexing method may also be referred to as XDD (Cross Division Duplex) or Subband non-overlapping Full Duplex (SBFD). XDD or SBFD may also mean a duplexing method that frequency-division multiplexes DL and UL (capable of using DL and UL simultaneously) within one component carrier (CC) in the TDD band.

[0083] Figure 3A This is a diagram showing an example of TDD settings specified up to Rel.16. Figure 3A In the example shown, a TDD time slot or symbol is configured for a UE in a bandwidth such as one component carrier (CC) (also referred to as a cell or serving cell), a bandwidth part (BWP), etc.

[0084] exist Figure 3A In the example shown, the time ratio of the DL slot to the UL slot is 4: 1. In such a configuration of slots or symbols in conventional TDD, sufficient UL time resources cannot be secured, and there is a concern that UL transmission delay may occur and coverage performance may be degraded.

[0085] Figure 3B FIG. 1 is a diagram showing an example of the structure of SBFD. Figure 3BIn the example shown, resources for DL ​​reception and resources for UL transmission overlap in time within one component carrier (CC). According to such a resource structure, more UL resources can be secured, and the utilization efficiency of resources can be improved.

[0086] For example, Figure 3B As shown in the example, it is also possible to set the two ends of the frequency domain as DL resources, and use these DL resources to clamp the UL resources. In this way, the generation of cross link interference (CLI) with adjacent carriers can be avoided and mitigated. In addition, a protection area can also be set at the boundary between DL resources and UL resources.

[0087] Considering the complexity of processing self-interference, it is possible to consider using both DL resources and UL resources by only the base station 100. That is, in radio resources where DL and UL overlap in time, it is possible to set a certain UE 200 to use DL resources and other UEs 200 to use UL resources.

[0088] Figure 4 FIG. 1 is a diagram showing an example of SBFD operation. Figure 4 In the illustrated example, part of the DL resources constituting the TDD band is set as UL resources, and the DL and UL partially overlap in the time domain.

[0089] exist Figure 4 In the example shown, during the DL-only period, multiple UEs 200 (in Figure 4 Receive DL channel / signal for each of UE#1 and UE#2).

[0090] In addition, during the period when DL and UL overlap in time, a certain UE 200 (in Figure 4 In the example of UE#1) receiving DL channel / signal, other UE200 (in Figure 4 In the example of UE#2), the UL channel / signal is transmitted. During this period, the base station 100 performs simultaneous transmission and reception of DL and UL.

[0091] Furthermore, during the UL-only period, multiple UEs 200 (in Figure 4 UL channel / signal is sent to each of UE#1 and UE#2).

[0092] In the existing NR (for example, as specified up to Rel.15 / 16 / 17), the DL frequency resource and UL frequency resource in the carrier for UE are set as DL BWP and UL BWP respectively. In order to switch the DL / UL frequency resource to another DL / UL frequency resource, it is necessary to set multiple BWPs and a BWP adaptation mechanism.

[0093] In addition, in the existing NR, such as Figure 5A As shown, the time resource (a time unit such as a symbol or a time slot) in the TDD carrier used by the UE 200 is configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.

[0094] like Figure 5B As shown, the SBFD symbol may be a symbol that is notified or set as UL (or DL) on a certain frequency resource, or is notified or set as UL transmission (or DL ​​reception), and on the other hand, is notified or set as DL (or UL) on other frequency resources, or is notified or set as DL reception (or UL transmission). Alternatively, the SBFD symbol may be a symbol that is notified or set as UL (or DL) on a part of the frequency resources, or is notified or set as UL transmission (or DL ​​reception). Alternatively, the SBFD symbol may be a symbol that is notified or set as DL (or UL) on a part of the frequency resources, or is notified or set as DL reception (or UL transmission).

[0095] Here, the time unit is a symbol level, a slot / subslot level, or a group of symbols / slots / subslots. That is, the SBFD time unit may also be a SBFD symbol, a slot / subslot containing a SBFD symbol or overlapping, or a group of symbols / slots / subslots containing a SBFD symbol or overlapping.

[0096] A pure time unit may also be a non-SBFD symbol (i.e., a symbol that is not a SBFD symbol), a slot / subslot that does not contain a SBFD symbol or does not overlap, or a group of symbols / slots / subslots that does not contain a SBFD symbol or does not overlap, which may also be referred to as a non-SBFD time unit. Fig. 6A As shown, the pure time unit can also be referred to as a time unit consisting only of DL on the frequency resource. In addition, as Figure 6B As shown, it can also be referenced as a time unit consisting only of UL on the frequency resource.

[0097] In addition, for the SBFD time unit, the DL resources and UL resources may also have various configuration modes in the frequency domain. For example, the SBFD time unit of the frequency domain mode #1 may also have the following configuration modes: Figure 6C In addition, the SBFD time unit of frequency domain mode #2 can also have the following configuration mode: Fig.6D In addition, the SBFD time unit of frequency domain mode #3 can also have the following configuration mode: Fig. 6EThe configuration modes shown are merely examples, and other configuration modes may also be used. The frequency domain mode of the SBFD time unit may also refer to a resource repetition mode in the frequency domain for the SBFD time unit.

[0098] (PUSCH Transmit Power Control)

[0099] In Rel.15, the UE performs transmission power control (TPC) for each transmission opportunity i. Transmission opportunity i can also be a transmission opportunity for PUSCH, PUCCH, SRS, or PRACH. Transmission opportunity i can also be set by the subcarrier spacing in the frame with the system frame number (SFN) to the time slot index n corresponding to μ. s,f μ , the first codeword in the time slot (the index of the first codeword of transmission opportunity i) S, and the number of consecutive codewords L are defined.

[0100] The transmission power of PUSCH may be controlled based on a TPC command (also referred to as a value, an increase or decrease value, a correction value, etc.) indicated by a value of a specific field (also referred to as a TPC command field, a first field, etc.) in DCI.

[0101] For example, when the UE transmits a PUSCH on BWP b of carrier f of cell c using a parameter set with index j (e.g., an open loop parameter set) and an index l of a power control adjustment state, the transmit power (P PUSCH, b, f, c (i, j, q d, , l)) can also be expressed by the following formula (1).

[0102] [Mathematical formula 1]

[0103]

[0104] In formula (1), P CMAX, f, c (i) For example, the transmission power of UE 200 set for carrier f of cell c in transmission opportunity i (also referred to as maximum transmission power, for example). O_PUSCH, b, f, c (j) For example, a parameter related to the target received power set for BWP b of carrier f of cell c in transmission opportunity i (for example, also referred to as a parameter related to the transmission power offset, transmission power offset PO, target received power parameter, etc.).

[0105] M PUSCH RB, b, f, c(i) is, for example, the number of resource blocks (bandwidth) allocated to the PUSCH for transmission opportunity i in uplink BWP b of carrier f in cell c and subcarrier spacing μ. b, f, c (j) is a value provided by a higher layer parameter (for example, also referred to as msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

[0106] PL b, f, c (q d ) For example, the index q of the reference signal for the downlink BWP associated with the uplink BWP b of the carrier f of the cell c is used. d The path loss is calculated in the UE (path loss compensation).

[0107] Δ TF, b, f, c (i) is a transmission power adjustment component (Transmission Power Adjustment Component) for uplink BWP b of carrier f of cell c (for example, also referred to as offset, transmission format compensation, etc.).

[0108] f b, f, c (i, l) is the value of the TPC command of the power control adjustment state index l based on the uplink BWP of the carrier f of the cell c and the transmission opportunity i (for example, the cumulative value of the TPC command, the value based on the closed loop). For example, the cumulative value of the TPC command can also be expressed by a specific formula.

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

[0110] In addition, in NR, a DCI format (for example, DCI format 2_2) used in the transmission of a TPC command for at least one of PUCCH and PUSCH is supported. UE200 may also 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 the transmission of the TPC command may also be a structure that is not used in the scheduling of PDSCH or PUSCH (does not contain scheduling information).

[0111] In addition, TPC commands specified by DCI (e.g., at least one of DCI formats 0_0, 0_1, and 2_2) for each PUSCH or PUCCH transmission may also be accumulated (tpc-Accumulation). UE200 may also be configured by the network (e.g., base station 100) whether to perform TPC command accumulation. Base station 100 may also use high-layer signaling (e.g., tpc-Accumulation) to notify UE200 of the presence or absence of TPC command accumulation.

[0112] When TPC command accumulation is enabled, UE 200 may determine the transmission power by considering the TPC command notified by a specific DCI (or PDCCH). In addition, the TPC command may be included in one of the parameters of the power control adjustment state defined by a specific formula (eg, a part of a specific formula).

[0113] (PUCCH Transmit Power Control)

[0114] The transmission power of PUCCH may be controlled based on a TPC command (also referred to as a value, an increase or decrease value, a correction value, etc.) indicated by a value of a specific field (also referred to as a TPC command field, a first field, etc.) in DCI.

[0115] For example, the transmission power (P) of the PUCCH in the transmission opportunity (also called transmission period, etc.) i of the BWP b of the carrier f of the cell c using the index l of the power control adjustment state is PUCCH, b, f, c (i, q u , q d , l)) can also be expressed by formula (2).

[0116] [Mathematical formula 2]

[0117]

[0118] Here, the power control adjustment state may also be set to have multiple states (e.g., two states) or a single state through a high-level parameter. In addition, when multiple power control adjustment states are set, one of the multiple power control adjustment states may also be identified by an index l (e.g., l∈{0,1}). The power control adjustment state may also be referred to as a PUCCH power control adjustment state, a first or second state, etc.

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

[0120] In formula (2), P CMAX, f, c (i) For example, the transmission power (also referred to as maximum transmission power, etc.) of UE 200 set for use in carrier f of cell c in transmission opportunity i. O_PUCCH, b, f, c (q u ) is, for example, a parameter related to a target reception power set for BWP b of carrier f of cell c in transmission opportunity i (also referred to as a parameter related to a transmission power offset, a transmission power offset P0 or a target reception power parameter, etc.).

[0121] M PUCCH RB, b, f, c (i) For example, PL is the number of resource blocks (bandwidth) allocated to the PUCCH for transmission opportunity i in uplink BWPb for carrier f with subcarrier spacing μ and cell c. b, f, c (q d ) For example, the index q of the reference signal for the downlink BWP associated with the uplink BWP b of the carrier f of the cell c is used. d The path loss calculated in UE200.

[0122] Δ F_PUCCH (F) is a higher layer parameter provided for each PUCCH format. TF, b, f, c (i) is a transmission power adjustment component (Transmission Power Adjustment Component) (offset) for uplink BWP b of carrier f of cell c.

[0123] g b, f, c (i, l) is the value of the TPC command of the power control adjustment state index l of the uplink BWP of the carrier f based on the cell c and the transmission opportunity i (eg, the cumulative value of the TPC command). For example, the cumulative value of the TPC command can also be expressed by a specific formula.

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

[0125] In addition, equations (1) and (2) are merely examples and are not limited thereto. UE200 may control the transmission power of PUSCH and PUCCH based on at least one parameter illustrated by equations (1) and (2), and may include additional parameters or omit some parameters. In equations (1) and (2), the transmission power of PUSCH and PUCCH is controlled for each BWP of a certain carrier of a certain cell, but is not limited thereto. At least a part of the cell, carrier, BWP, and power control adjustment state may also be omitted.

[0126] (Closed-loop transmit power control)

[0127] In NR, the transmission power of UE 200 may be controlled using open-loop transmission power control and / or closed-loop transmission power control. UE 200 may correct an error of the open-loop control by closed-loop control using a TPC command received from base station 100.

[0128] For example, the transmission power of an uplink shared channel (eg, PUSCH), an uplink control channel (eg, PUCCH), a sounding reference signal (SRS), a random access channel (eg, PRACH), etc. becomes the target of transmission power control.

[0129] In NR, it is specified that for each carrier of the serving cell, a maximum of two closed loops are supported.

[0130] In NR, the transmission power of PUSCH in the transmission period i of the bandwidth part (Bandwidth Part: BWP) b of the carrier f of the serving cell c can also be expressed by the above equation (1). Here, the transmission period can also be any time unit such as a symbol, a time slot, a subframe, or a frame.

[0131] In formula (1), f b, f, c (i, l) is a value based on the TPC command (e.g., a cumulative value based on the TPC command). l is an index of the power control adjustment state. For example, if UE200 is configured to use high-layer signaling to maintain multiple (e.g., two) power control adjustment states for a specific channel (e.g., PUSCH, PUCCH, etc.), at least one of the multiple values ​​can be used as 1 (e.g., l∈{0,1}). In the absence of this setting, UE200 can also be assumed to use one value as 1 (e.g., l=0).

[0132] For example, when the RRC parameter "twoPUSCH-PC-AdjustmentStates" is set for PUSCH, UE200 can also determine that two power control states are applied in the transmission power control of the PUSCH. In addition, when the RRC parameter "twoPUCCH-PC-AdjustmentStates" is set for PUCCH, UE200 can also determine that two power control states are applied in the transmission power control of the PUCCH.

[0133] Although the parameters used for other uplink signals (for example, SRS, PRACH, etc.) are different, similarly to PUSCH and / or PUCCH, the transmission power can be determined using a plurality of power control adjustment states.

[0134] In the present disclosure, the closed loop and power control adjustment states can also be overwritten.

[0135] However, in NR, TPC commands can be collectively notified to multiple UEs. For example, Downlink Control Information (DCI) format 2_2 sent in the common search space is used to send TPC commands for at least one of PUCCH and PUSCH. DCI format 2_2 can also be called DCI for UE group common TPC commands. The TPC command notified through DCI format 2_2 can also be called a group common TPC command.

[0136] DCI format 2_2 may be scrambled by a cyclic redundancy check (CRC) using an identifier for TPC of a PUSCH (TPC-PUSCH-RNTI (Radio Network Temporary Identifier)) or may be scrambled by a CRC using an identifier for TPC of a PUCCH (TPC-PUCCH-RNTI).

[0137] [Topic]

[0138] Depending on the SBFD operation or dynamic TDD, inter-gNB link interference (CLI) and inter-UE CLI need to be considered. For inter-UE CLI, Fig. 7A As shown, the uplink signal of the aggressor UE may cause interference to the downlink reception in the victim UE. From the perspective of the victim UE, in order to reduce the interference to the reception in the victim UE, it may be desirable that the uplink transmission power of the aggressor UE be reduced.

[0139] On the other hand, for inter-gNB CLI, such as Figure 7B As shown, the downlink signal to the aggressor UE can interfere with the uplink signal from the victim UE to the gNB. From the perspective of the gNB of the victim UE, in order to improve the received signal power, it is desirable to increase the uplink transmit power of the victim UE.

[0140] In particular, in SBFD operation, different UEs perform uplink transmission and downlink reception in the same time unit such as the same symbol / time slot, which may generate inter-UE CLI and / or inter-gNB CLI. The transmit power control of the UE can be specified by the specification, semi-persistently set by RRC settings, etc., and / or dynamically notified by DCI notification. In the following Proposals 1 to 3, for the power control of uplink signals in SBFD symbols / time slots, it is proposed to apply different power controls for SBFD operation and non-SBFD operation via specifications, RRC settings and / or DCI notifications that support both SBFD operation and non-SBFD operation.

[0141] [Outline of the proposal]

[0142] As proposal 1, different transmission power settings may be applied to the SBFD operation and the non-SBFD operation.

[0143] Specifically, in option 1, for the transmit power control IEs such as PUSCH-PowerControl IE and PUCCH-PowerControl IE, different transmit power control IEs (for example, PUSCH-PowerControl and PUSCH-PowerControl-SBFD, PUCCH-PowerControl and PUCCH-PowerControl-SBFD, etc.) can also be set for SBFD operation and non-SBFD operation.

[0144] In addition, in option 2, for the fields related to power control in PUSCH-PowerControl IE, PUCCH-PowerControl IE, etc., different fields for transmit power control (for example, p0-NominalWithoutGrant and p0-NominalWithoutGrant-SBFD, p0-Set and p0-Set-SBFD, etc.) can also be set for SBFD operation and non-SBFD operation.

[0145] As a proposal 2, different closed loops may be applied for SBFD operation and non-SBFD operation.

[0146] Specifically, with respect to problem 1, for the closed loop of PUSCH and / or PUCCH in SBFD operation, in Alt-a, a maximum of two existing closed loops can be set, and each closed loop is applied to either SBFD operation or non-SBFD operation.

[0147] Furthermore, according to Alt-b, the set maximum number can be extended to X, and a maximum of two closed loops among the X can be set as non-SBFD operations, and the others can be applied to SBFD operations.

[0148] Furthermore, according to Alt-c, the closed loop for SBFD operation may not be explicitly set, but the closed loop for SBFD operation may be mapped corresponding to the setting for non-SBFD operation.

[0149] In addition, for problem point 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 can be mapped to non-SBFD operation or SBFD operation.

[0150] Furthermore, according to Alt-2, a single SRI / loop-closed index may be commonly mapped to the SBFD operation as well as the SBFD operation.

[0151] In addition, with respect to problem point 3, with respect to the closed loop index for the Configured Grant (CG) PUSCH, according to Alt-1, a single closed loop index can be mapped to the non-SBFD operation or the SBFD operation.

[0152] According to Alt-2, a single closed-loop index may be commonly mapped to the SBFD operation and the SBFD operation.

[0153] As proposal 3, a method for calculating the transmission power in SBFD operation may also be specified. According to option 1, a scaling factor for SBFD operation may also be specified, set, notified and / or applied.

[0154] According to Option 2, a power offset for SBFD operation may also be specified, set, notified and / or applied.

[0155] According to Option 3, a reference resource block (RB) size for SBFD operation may also be specified, set, notified and / or applied.

[0156] [Proposal 1]

[0157] In Proposal 1, the UE transmits an uplink channel in SBFD operation at a transmission power set according to the PUSCH and / or PUCCH transmission power setting for SBFD operation, and transmits an uplink channel in non-SBFD operation at a transmission power set according to the PUSCH and / or PUCCH transmission power setting for non-SBFD operation. That is, the PUSCH and / or PUCCH transmission power is semi-persistently set 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 via RRC setting, etc.

[0158] Specifically, according to option 1, different PUSCH and / or PUCCH transmit power settings (e.g., PUSCH-PowerControl IE and PUSCH-PowerControl-SBFD IE, and / or PUCCH-PowerControl IE and PUCCH-PowerControl-SBFD IE, etc.) may be specified, set, notified and / or applied for SBFD operation and non-SBFD operation.

[0159] In addition, according to option 2, for a specific parameter or field in the PUSCH and / or PUCCH transmit power setting (e.g., PUSCH-PowerControl IE and / or PUCCH-PowerControl IE, etc.), different settings (e.g., p0-NominalWithoutGrant and p0-NominalWithoutGrant-SBFD, and / or p0-Set and p0-Set-SBFD, etc.) may be defined, configured, notified, and / or applied in SBFD operation and non-SBFD operation. Furthermore, or alternatively, for power control related parameters in RACH-ConfigGeneric (e.g., preambleReceivedTargetPower), power control related parameters in RACH-ConfigGenericTwoStepRA (e.g., msgA-PreambleReceivedTargetPower), and / or power control related parameters in PUSCH-ConfigCommon (e.g., msg3-DeltaPreamble, p0-NominalWithGrant), different settings may be defined, configured, notified, and / or applied in SBFD operation and non-SBFD operation.

[0160] (Option 1)

[0161] In option 1, different PUSCH and / or PUCCH transmit power settings (e.g., PUSCH-PowerControl IE and PUSCH-PowerControl-SBFD IE, and / or PUCCH-PowerControl IE and PUCCH-PowerControl-SBFD IE, etc.) may also be specified, set, notified and / or applied for SBFD operation and non-SBFD operation.

[0162] In addition, hereinafter, PUSCH and / or PUCCH in SBFD operation means PUSCH and / or PUCCH overlapping with SBFD time units such as SBFD symbols and SBFD time slots. In addition, PUSCH and / or PUCCH in non-SBFD operation means PUSCH and / or PUCCH not overlapping with SBFD time units such as SBFD symbols and SBFD time slots.

[0163] Specifically, additional fields such as PUSCH-PowerControl-SBFD may also be set in the PUSCH-Config IE. For example, in the existing NR, Fig. 8A As shown in FIG. 1 , “pusch-PowerControl” is set in PUSCH-Config IE as PUSCH power control IE. On the other hand, according to option 1, Figure 8B As shown, "pusch-PowerControl-SBFD" is additionally set as a 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 can also be set in the PUSCH-Config IE. The UE may also send PUSCH with a transmission power based on the pusch-PowerControl-SBFD IE in SBFD operation, and send PUSCH with a transmission power based on the pusch-PowerControl IE in non-SBFD operation. As a result, different PUSCH transmission powers can be set for the UE in each of the SBFD operation and the non-SBFD operation, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation can be reduced.

[0164] In addition, additional fields such as PUCCH-PowerControl-SBFD may also be set in PUCCH-Config. For example, in the existing NR, Fig.9AAs shown in FIG. 1 , “pucch-PowerControl” is set in PUCCH-Config as the PUCCH power control IE. On the other hand, according to option 1, Fig. 9B As shown, "pucch-PowerControl-SBFD" is additionally set as the PUCCH power control IE for SBFD operation. That is, "pucch-PowerControl-SBFD" as the PUCCH power control IE for SBFD operation and "pucch-PowerControl" as the PUCCH power control IE for non-SBFD operation can also be set in the PUCCH-Config IE. The UE may also send PUCCH with a transmit power based on the pucch-PowerControl-SBFD IE in SBFD operation, and send PUCCH with a transmit power based on the pucch-PowerControl IE in non-SBFD operation. Thus, different PUCCH transmit powers can be set for the UE in each of the SBFD operation and the non-SBFD operation, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation can be reduced.

[0165] According to option 1, different PUSCH and / or PUCCH transmission powers can be set for the UE in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0166] (Option 2)

[0167] In option 2, for specific fields / parameters in the PUSCH-PowerControl IE and / or the PUCCH-PowerControl IE, different settings may be defined, configured, notified and / or applied in SBFD operation and non-SBFD operation.

[0168] Specifically, additional fields such as "p0-NominalWithoutGrant-SBFD" and "p0-AlphaSets-SBFD" may also be set in the PUSCH-PowerControl IE. For example, in the existing NR, Fig. 10A As shown in FIG. 1 , as the PUSCH power control field, "p0-NominalWithoutGrant", "p0-AlphaSets", etc. are set in the PUSCH-PowerControl IE. On the other hand, according to option 2, it is also possible to Fig. 10BAs shown, "p0-NominalWithoutGrant-SBFD" and "p0-AlphaSets-SBFD" are 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-AlphaSets" as PUSCH power control fields for non-SBFD operation can also be set in PUSCH-PowerControl IE. UE can also transmit PUSCH with the transmission power based on PUSCH power control fields such as "p0-NominalWithoutGrant-SBFD" and "p0-AlphaSets-SBFD" in SBFD operation, and transmit PUSCH with the transmission power based on "p0-NominalWithoutGrant" and "p0-AlphaSets" in non-SBFD operation. Therefore, different PUSCH transmission powers can be set for the UE in each of the SBFD operation and the non-SBFD operation, which can reduce the possibility of inter-UE CLI and / or inter-gNB CLI occurring during the SBFD operation.

[0169] In addition, additional fields such as "p0-Set-SBFD" may also be set in the PUCCH-PowerControl IE. For example, in the existing NR, Fig.11A As shown in FIG. 1 , “p0-Set” and the like are set in the PUCCH-PowerControl IE as the PUCCH power control field. On the other hand, according to option 2, Fig. 11B As shown, "p0-Set-SBFD" is additionally set as the PUCCH power control field for SBFD operation. That is, "p0-Set-SBFD" as the PUCCH power control field for SBFD operation and "p0-Set" as the PUCCH power control field for non-SBFD operation can also be set in the PUCCH-PowerControl IE. The UE can also send PUCCH by using the transmission power based on the PUCCH power control field such as "p0-Set-SBFD" in SBFD operation, and send PUCCH by using the transmission power based on the PUCCH power control field such as "p0-Set" in non-SBFD operation. As a result, different PUCCH transmission powers can be set for the UE in each of the SBFD operation and the non-SBFD operation, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0170] In addition, additional fields such as "preambleReceivedTargetPower-SBFD" may also be set in the RACH-ConfigGeneric IE. For example, in the existing NR, Fig. 12A As shown in FIG. 1 , "preambleReceivedTargetPower" etc. are set in RACH-ConfigGeneric IE as RACH power control fields. On the other hand, according to option 2, Fig. 12B As shown, "preambleReceivedTargetPower-SBFD" is additionally set as the RACH power control field for SBFD operation. That is, "preambleReceivedTargetPower-SBFD" as the RACH power control field for SBFD operation and "preambleReceivedTargetPower" as the RACH power control field for non-SBFD operation are set in the RACH-ConfigGeneric IE. The UE may also transmit PRACH in SBFD operation by using the transmit power based on PRACH power control fields such as "preambleReceivedTargetPower-SBFD", and transmit PRACH in non-SBFD operation by using the transmit power based on PRACH power control fields such as "preambleReceivedTargetPower". As a result, different PRACH transmit powers can be set for the UE in each of the SBFD operation and the non-SBFD operation, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0171] In addition, additional fields such as "msgA-PreambleReceivedTargetPower-SBFD" may also be set in the RACH-ConfigGenericTwoStepRA IE. For example, in the existing NR, Fig.13A As shown in FIG. 1 , "msgA-PreambleReceivedTargetPower" etc. are set in RACH-ConfigGenericTwoStepRA IE as the PRACH power control field. On the other hand, according to option 2, Fig. 13BAs shown, "msgA-PreambleReceivedTargetPower-SBFD" is additionally set as the 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 can also be set in RACH-ConfigGenericTwoStepRA IE. The UE can also send PRACH by using the transmission power based on the PRACH power control field such as "msgA-PreambleReceivedTargetPower-SBFD" in SBFD operation, and send PRACH by using the transmission power based on the PRACH power control field such as "msgA-PreambleReceivedTargetPower" in non-SBFD operation. As a result, different PRACH transmission powers can be set for the UE in each of the SBFD operation and the non-SBFD operation, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation can be reduced.

[0172] In addition, additional fields such as "msg3-DeltaPreamble-SBFD" and "p0-NominalWithGrant-SBFD" may also be set in the PUSCH-ConfigCommon IE. For example, in the existing NR, Fig.14A As shown in FIG. 1 , "msg3-DeltaPreamble", "p0-NominalWithGrant" and the like are set in PUSCH-ConfigCommon IE as PUSCH power control fields. On the other hand, according to option 2, Fig. 14BAs shown, "msg3-DeltaPreamble-SBFD" and "p0-NominalWithGrant-SBFD" are additionally set as PUSCH power control fields 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-NominalWithGrant" as PUSCH power control fields for non-SBFD operation can also be set in PUSCH-ConfigCommon IE. The UE may also transmit PUSCH in SBFD operation by using the transmit power based on PUSCH power control fields such as "msg3-DeltaPreamble-SBFD" and "p0-NominalWithGrant-SBFD", and transmit PUSCH in non-SBFD operation by using the transmit power based on PUSCH power control fields such as "msg3-DeltaPreamble" and "p0-NominalWithGrant". Thus, different PUSCH transmit powers can be set for the UE in SBFD operation and non-SBFD operation, respectively, and the possibility of inter-UE CLI and / or inter-gNB CLI during SBFD operation can be reduced.

[0173] In addition, the PUSCH and / or PUCCH power control fields are not limited to the above-mentioned fields. For other PUSCH / PUCCH power control fields such as "p0-NominalWithGrant", "p0-PUSCH-Alpha", "p0-AlphaSets", "delta-MCS", "deltaF-PUCCH-f0", "deltaF-PUCCH-f1", "deltaF-PUCCH-f2", "deltaF-PUCCH-f3", "deltaF-PUCCH-f4", etc., different settings for SBFD operation and non-SBFD operation may also be specified, set, notified and / or applied.

[0174] According to option 2, different PUSCH and / or PUCCH transmission powers can be set for the UE in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0175] In Proposal 1, the UE may also set the transmit power in SBFD operation according to the transmit power setting for SBFD, and may set the transmit power in non-SBFD operation according to the transmit power setting for non-SBFD. Here, the transmit power setting for SBFD and / or the transmit power setting for non-SBFD may also be specified by a specification, or semi-persistently set by RRC setting, etc., or dynamically notified by DCI notification, etc. In addition, the transmit power setting for SBFD and / or the transmit power setting for non-SBFD may also be explicitly or implicitly specified, set, notified, or applied. In addition, Option 1 and Option 2 may be used together or not.

[0176] The UE may also transmit an uplink channel at a transmit power based on a transmit power setting for SBFD in SBFD operation, and transmit an uplink channel at a transmit power based on a transmit power setting for non-SBFD in non-SBFD operation. For example, in Option 1, the transmit power setting for SBFD and the transmit power setting for non-SBFD may also be specified by different transmit power setting information elements for SBFD operation and non-SBFD operation (e.g., PUSCH-PowerControl-SBFD IE and PUSCH-PowerControl IE, PUCCH-PowerControl-SBFD IE and PUCCH-PowerControl IE, etc.). In this case, the UE may also determine the PUSCH and / or PUCCH transmit power according to the PUSCH-PowerControl-SBFD IE and / or PUCCH-PowerControl-SBFD IE in SBFD operation, and determine the PUSCH and / or PUCCH transmit power according to the PUSCH-PowerControl IE and / or PUCCH-PowerControl IE in non-SBFD operation.

[0177] In addition, in Option 2, the transmit power setting for SBFD and the transmit power setting for non-SBFD may also be specified by the transmit power parameters for SBFD operation and the transmit power parameters for non-SBFD operation in the same transmit power setting information element. For example, the UE may also determine the PUSCH transmit power according to p0-NominalWithoutGrant-SBFD, p0-AlphaSets-SBFD, etc. in the PUSCH-PowerControl IE in SBFD operation, and determine the PUSCH transmit power according to p0-NominalWithoutGrant, p0-AlphaSets, etc. in the PUSCH-PowerControl IE in non-SBFD operation. In addition, the UE may also determine the PUCCH transmit power according to p0-Set-SBFD, etc. in the PUCCH-PowerControl IE in SBFD operation, and determine the PUCCH transmit power according to p0-Set, etc. in the PUCCH-PowerControl IE in non-SBFD operation.

[0178] In addition, 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 also transmit PUSCH, PUCCH, and / or PRACH according to the PUSCH transmit power setting, the PUCCH transmit power setting, and / or the PRACH transmit power setting.

[0179] On the other hand, the gNB may also set the transmit power for the UE in SBFD operation according to the transmit power setting for SBFD, and set the transmit power for the UE in non-SBFD operation according to the transmit power setting for non-SBFD. Here, the transmit power setting for SBFD and / or the transmit power setting for non-SBFD may also be specified by the specification, or semi-persistently set by RRC setting, etc., or dynamically notified by MAC CE, etc. In addition, the transmit power setting for SBFD and / or the transmit power setting for non-SBFD may also be explicitly or implicitly specified, set, notified or applied.

[0180] The gNB may also receive an uplink channel transmitted from the UE at a transmit power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE at a transmit power for non-SBFD in non-SBFD operation. For example, in Option 1, the transmit power setting for SBFD and the transmit power setting for non-SBFD may also be specified by different transmit power setting information elements for SBFD operation and non-SBFD operation (e.g., PUSCH-PowerControl-SBFD IE and PUSCH-PowerControl IE, PUCCH-PowerControl-SBFD IE and PUCCH-PowerControl IE, etc.). In this case, the gNB may also set the PUSCH and / or PUCCH transmit power for SBFD operation to the UE according to the PUSCH-PowerControl-SBFD IE and / or PUCCH-PowerControl-SBFD IE, and set the PUSCH and / or PUCCH transmit power for non-SBFD operation to the UE according to the PUSCH-PowerControl IE and / or PUCCH-PowerControl IE.

[0181] In addition, in Option 2, the transmit power setting for SBFD and the transmit power setting for non-SBFD can also be specified by the transmit power parameters for SBFD operation and the transmit power parameters for non-SBFD operation in the same transmit power setting information element. For example, the gNB can also set the PUSCH transmit power in SBFD operation for the UE through p0-NominalWithoutGrant-SBFD, p0-AlphaSets-SBFD, etc. in the PUSCH-PowerControl IE, and set the PUSCH transmit power in non-SBFD operation for the UE through p0-NominalWithoutGrant, p0-AlphaSets, etc. in the PUSCH-PowerControl IE. In addition, the gNB can also set the PUCCH transmit power in SBFD operation for the UE through p0-Set-SBFD, etc. in the PUCCH-PowerControl IE, and set the PUCCH transmit power in non-SBFD operation for the UE through p0-Set, etc. in the PUCCH-PowerControl IE.

[0182] In addition, 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 also receive PUSCH, PUCCH, and / or PRACH sent from the UE through PUSCH transmit power setting, PUCCH transmit power setting, and / or PRACH transmit power setting.

[0183] In addition, the UE may also report to the gNB the UE capability related to whether different PUSCH and / or PUCCH transmit power settings are supported for SBFD operation and non-SBFD operation. The gNB may also determine whether to perform different PUSCH and / or PUCCH transmit power settings for SBFD operation and non-SBFD operation based on the obtained UE capability.

[0184] Thus, in Proposal 1, different transmit power settings are applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmit powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0185] [Proposal 2]

[0186] In Proposal 2, the UE transmits uplink channels in SBFD operation by using transmission power adjusted according to the PUSCH and / or PUCCH closed loop for SBFD operation, and transmits uplink channels in non-SBFD operation by using transmission power adjusted according to the PUSCH and / or PUCCH closed loop for non-SBFD operation. That is, the PUSCH and / or PUCCH transmission power is dynamically adjusted according to the closed loop for SBFD operation and the closed loop for non-SBFD operation via DCI notification, etc.

[0187] In Proposal 2, the configuration of PUSCH and / or PUCCH closed loop in the SBFD operation of the cell is studied as Problem 1. In addition, the mapping relationship between the uplink transmit beam (e.g., SRI and / or PUCCH spatial relation information (PUCCH spatialrelation info) etc.) and the PUSCH and / or PUCCH closed loop index is studied as Problem 2. In addition, the mapping relationship between the PUSCH configuration of the configured grant (e.g., configured grant (Configured Grant)) and the PUSCH closed loop index is studied as Problem 3.

[0188] (Problem 1)

[0189] As problem point 1, the setting of PUSCH and / or PUCCH closed loop in the SBFD operation of the cell can be studied.

[0190] <alt-a>

[0191] In Alt-a, it is also possible that up to two PUSCH and / or PUCCH loops are set for a cell, and one loop is applied for SBFD operation, and the other loop is applied for non-SBFD operation. That is, in Alt-a, up to two PUSCH and / or PUCCH loops can be set for a cell according to the restrictions of version 15 / 16 / 17. For example, the UE may also assume that twoPUSCH-PC-AdjustmentStates and / or twoPUCCH-PC-AdjustmentStates are always set in the PUSCH-PowerControl IE and / or PUCCH-PowerControl IE of a serving cell or BWP with SBFD operation.

[0192] Here, which of the maximum two closed loops is set for SBFD operation and / or non-SBFD operation may be specified by the specification, semi-persistently set by RRC setting, etc., dynamically notified by DCI notification, etc., or determined by the UE according to a specific rule. In addition, which of the maximum two closed loops is set for SBFD operation and / or non-SBFD operation may also be explicitly or implicitly specified, set, notified, or applied.

[0193] According to Alt-a, by applying the existing NR's maximum two closed-loop settings, it is possible to have a closed-loop for SBFD operation and a closed-loop for non-SBFD operation, and to dynamically control the UE-based PUSCH and / or PUCCH transmission power via DCI notification.

[0194] <alt-b>

[0195] In Alt-b, a maximum of X PUSCH and / or PUCCH loops may be set, and a maximum of two PUSCH and / or PUCCH loops out of the X may be set for non-SBFD operation. Typically, the value of X may be greater than 2. In addition, the number of PUSCH and / or PUCCH loops for SBFD operation may be less than 2, equal to 2, or greater than 2.

[0196] Here, the value of X may also be specified by the specification, or semi-persistently set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined by the UE according to specific rules. In addition, the value of X may also be specified, set, notified, or applied explicitly or implicitly. In addition, which of the maximum X closed loops is set for SBFD operation and / or non-SBFD operation may also be specified by the specification, or semi-persistently set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined by the UE according to specific rules. In addition, which of the maximum X closed loops is set for SBFD operation and / or non-SBFD operation may also be specified, set, notified, or applied explicitly or implicitly.

[0197] For example, Fig.15 As shown, the number of PUSCH loops for non-SBFD operation may be set by the existing twoPUSCH-PC-AdjustmentStates fields in the PUSCH-PowerControl IE, and the number of PUSCH loops for SBFD operation may be set by the new SBFD-PUSCH-PC-AdjustmentStates field in the PUSCH-PowerControl IE. For example, PUSCH loop indexes #0 and #1 may represent loops for non-SBFD operation, and PUSCH loop indexes #2 and #3 may represent loops for SBFD operation.

[0198] Similarly, the number of PUCCH loops for non-SBFD operation may be set by the existing twoPUCCH-PC-AdjustmentStates fields in the PUCCH-PowerControlIE, and the number of PUCCH loops for SBFD operation may be set by the new SBFD-PUCCH-PC-AdjustmentStates field in the PUCCH-PowerControlIE. For example, PUCCH loop indexes #0 and #1 may represent loops for non-SBFD operation, and PUCCH loop indexes #2 and #3 may represent loops for SBFD operation.

[0199] Here, the number of PUSCH and / or PUCCH closed loops used for SBFD operation may also be specified by specifications, or semi-persistently set through RRC settings, etc., or dynamically notified through DCI notifications, etc., or determined by the UE according to specific rules.

[0200] In addition, the number of PUSCH and / or PUCCH closed loops used for SBFD operation can be larger, equal, or smaller than the number of PUSCH and / or PUCCH closed loops used for non-SBFD operation. In addition, when twoPUSCH-PC-AdjustmentStates and / or twoPUCCH-PC-AdjustmentStates are not set, the UE may not assume that twoStates is set to SBFD-PUSCH-PC-AdjustmentStates and / or SBFD-PUCCH-PC-AdjustmentStates. In addition, when OneState is set to SBFD-PUSCH-PC-AdjustmentStates and / or SBFD-PUCCH-PC-AdjustmentStates, the UE may not assume that twoPUSCH-PC-AdjustmentStates and / or twoPUCCH-PC-AdjustmentStates are set.

[0201] According to Alt-b, the existing NR's maximum two closed-loop settings are applied to non-SBFD operations, so that a closed loop for SBFD operations and a closed loop for non-SBFD operations can be provided, and the UE-based PUSCH and / or PUCCH transmission power can be dynamically controlled via DCI.

[0202] <alt-c>

[0203] In Alt-c, the PUSCH and / or PUCCH loopback for SBFD operation may not be explicitly set, but may be implicitly set through a one-to-one mapping from a PUSCH and / or PUCCH loopback set for non-SBFD operation. That is, if a PUSCH and / or PUCCH loopback for non-SBFD operation is set, a PUSCH and / or PUCCH loopback for SBFD operation is determined corresponding to the set PUSCH and / or PUCCH loopback for non-SBFD operation based on a specific one-to-one mapping. The UE may also adjust the PUSCH and / or PUCCH transmit power in non-SBFD operation through the PUSCH and / or PUCCH loopback for non-SBFD operation, and adjust the PUSCH and / or PUCCH transmit power in SBFD operation through the PUSCH and / or PUCCH loopback for SBFD operation implicitly set according to the PUSCH and / or PUCCH loopback for non-SBFD operation.

[0204] For example, when twoPUSCH-PC-AdjustmentStates is not set, that is, when a single PUSCH loop index #i0 is set for non-SBFD operation, this may also implicitly mean that PUSCH loop index #i1 or #i2 is set for SBFD operation, and PUSCH loop index #i0 for non-SBFD operation may also be associated with PUSCH loop index #i1 or #i2 for SBFD operation. In addition, the term "#i1 or #i2" is used because it is uncertain whether the PUSCH loop for SBFD operation starts from i2 or i1.

[0205] In addition, for example, when twoPUSCH-PC-AdjustmentStates are set, that is, when PUSCH loop index #i0 and #i1 are set for non-SBFD operation, this may also implicitly mean that PUSCH loop index #i2 or #i3 is set for SBFD operation, such as Fig.16 As shown, the PUSCH loop closure index #i0 for non-SBFD operation may be associated with the PUSCH loop closure index #i1 for SBFD operation, and the PUSCH loop closure index #i1 for non-SBFD operation may be associated with the PUSCH loop closure index #i3 for SBFD operation.

[0206] Similarly, for example, when twoPUCCH-PC-AdjustmentStates is not set, that is, when a single PUCCH loop index #i0 is set for non-SBFD operation, this may also implicitly mean that PUCCH loop index #i1 or #i2 is set for SBFD operation, and PUCCH loop index #i0 for non-SBFD operation may also be associated with PUCCH loop index #i1 or #i2 for SBFD operation. In addition, the term "#i1 or #i2" is used because it is uncertain whether the PUCCH loop for SBFD operation starts from i2 or i1.

[0207] In addition, for example, when twoPUCCH-PC-AdjustmentStates are set, that is, when PUCCH closed-loop index #i0 and #i1 are set for non-SBFD operation, this may also implicitly mean that PUCCH closed-loop index #i2 or #i3 is set for SBFD operation, and the PUCCH closed-loop index #i0 for non-SBFD operation may also be associated with the PUCCH closed-loop index #i1 for SBFD operation, and the PUCCH closed-loop index #i1 for non-SBFD operation may also be associated with the PUCCH closed-loop index #i3 for SBFD operation.

[0208] Here, the one-to-one mapping may also be specified by a specification, or semi-persistently set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined by the UE according to specific rules. In addition, the one-to-one mapping may also be specified, set, notified or applied explicitly or implicitly. In addition, multiple different one-to-one mappings are specified, and which one-to-one mapping is applied may also be specified by a specification, or semi-persistently set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined by the UE according to specific rules. In addition, which one-to-one mapping is applied may also be specified, set, notified or applied explicitly or implicitly.

[0209] According to Alt-c, the existing closed loop setting is applied to the non-SBFD operation, and the closed loop for the SBFD operation and the closed loop for the non-SBFD operation can be provided, and the PUSCH and / or PUCCH transmission power based on the UE can be dynamically controlled via DCI.

[0210] (Question 2)

[0211] As problem point 2, the mapping between uplink transmission beam indexes such as SRI and / or PUCCH spatial relation information (PUCCH spatial relationinfo) and PUSCH and / or PUCCH closed-loop indexes can be studied.

[0212] <alt-1>

[0213] In Alt-1, an uplink transmit beam index such as an SRI and / or PUCCH spatial relation info may also be mapped to a PUSCH and / or PUCCH closed loop index for either non-SBFD operation or SBFD operation. For example, each candidate value of the sri-PUSCH-ClosedLoopIndex field in the SRI-PUSCH-PowerControl IE may also 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 also be a PUCCH closed loop index for either non-SBFD operation or SBFD operation.

[0214] Here, for example, when Alt-a is applied to the above-mentioned problem 1, the candidate values ​​of the sri-PUSCH-ClosedLoopIndex field and / or the pucch-ClosedLoopIndex-r17 field may still remain {i0, i1} unchanged. Fig.17 As shown, SRI#m may be mapped to PUSCH loop #i0 for non-SBFD operation, and SRI#n may be mapped to PUSCH loop #i1 for SBFD operation.

[0215] Alternatively, when Alt-b is applied to the above-mentioned problem 1, the candidate values ​​of the sri-PUSCH-ClosedLoopIndex field and / or the pucch-ClosedLoopIndex-r17 field may be {i0, i1, i2, i3}. For example, the candidate values ​​of the sri-PUSCH-ClosedLoopIndex field may be {i0, i1, i2, i3}. Fig.18 As shown, it can be {i0, i1, i2,i3}. In addition, for example, Fig.19 As shown, SRI#m may be mapped to PUSCH loop #i0 for non-SBFD operation, and SRI#n may be mapped to PUSCH loop #i3 for SBFD operation. In addition, when Alt-b is applied to the above-mentioned problem 1, the following several situations may be considered.

[0216] When twoPUSCH-PC-AdjustmentStates is not set and only one PUSCH closed loop is set for SBFD operation, the candidate value of sri-PUSCH-ClosedLoopIndex can be {i0, i1} or {i0, i2}. In addition, it is unknown whether the PUSCH closed loop for SBFD operation starts from i2 or i1.

[0217] When twoPUSCH-PC-AdjustmentStates is not set and two PUSCH closed loops are set for SBFD operation, the candidate value of sri-PUSCH-ClosedLoopIndex can be {i0, i1, i2} or {i0, i2, i3}. In addition, it is unknown whether the PUSCH closed loop for SBFD operation starts from i2 or i1.

[0218] In the case where twoPUSCH-PC-AdjustmentStates are set and, in addition, only one PUSCH closed loop is set for SBFD operation, candidate values ​​of sri-PUSCH-ClosedLoopIndex may become {i0, i1, i2}.

[0219] In the case where twoPUSCH-PC-AdjustmentStates is set and two PUSCH closed loops are set for SBFD operation, candidate values ​​of sri-PUSCH-ClosedLoopIndex may become {i0, i1, i2, i3}.

[0220] Similarly, for example, each candidate value of pucch-ClosedLoopIndex-r17 may be {i0, i1, i2, i3}. In this case, the following several cases are also considered.

[0221] When twoPUCCH-PC-AdjustmentStates is not set and only one PUCCH closed loop is set for SBFD operation, the candidate value of pucch-ClosedLoopIndex-r17 can be {i0, i1} or {i0, i2}. In addition, it is unknown whether the PUCCH closed loop for SBFD operation starts from i2 or i1.

[0222] When twoPUCCH-PC-AdjustmentStates is not set and two PUCCH loops are set for SBFD operation, the candidate value of pucch-ClosedLoopIndex-r17 can be {i0, i1, i2} or {i0, i2, i3}. In addition, it is unknown whether the PUCCH loop for SBFD operation starts from i2 or i1.

[0223] In the case where twoPUCCH-PC-AdjustmentStates are set and, in addition, only one PUCCH closed loop is set for SBFD operation, candidate values ​​of pucch-ClosedLoopIndex-r17 may become {i0, i1, i2}.

[0224] In the case where twoPUCCH-PC-AdjustmentStates is set and, in addition, two PUCCH closed loops are set for SBFD operation, candidate values ​​of pucch-ClosedLoopIndex-r17 may become {i0, i1, i2, i3}.

[0225] In addition, the following various modifications are conceivable.

[0226] Variation #1

[0227] In the case where the SRI is mapped to the PUSCH closed-loop index for non-SBFD operation, the UE may not assume that the SRI is notified for the PUSCH on SBFD.

[0228] Variation #2

[0229] In the case where the SRI is mapped to the PUSCH closed-loop index for SBFD operation, the UE may not assume that the SRI is notified for the PUSCH on non-SBFD.

[0230] Variation #3

[0231] The UE may not assume a DCI format for scheduling a PUSCH on non-SBFD and another DCI format for scheduling a PUSCH on SBFD based on the SRI field that notifies the same TPC loop index.

[0232] Variation #4

[0233] The UE may not assume a DCI format for scheduling a PUSCH on non-SBFD and another DCI format for scheduling a PUSCH on non-SBFD based on the SRI field for notifying different TPC loop indexes.

[0234] Variation #5

[0235] The UE may not assume the DCI format for scheduling the PUSCH on SBFD and other DCI formats for scheduling the PUSCH on SBFD based on the SRI field that notifies different TPC loop indexes.

[0236] Variation #6

[0237] When two PUCCH resources are configured or notified by the same PUCCH spatial relation information (PUCCH spatial relationinfo), the UE may not assume a DCI format for notifying a PUCCH resource on non-SBFD and another DCI format for notifying a PUCCH resource on SBFD.

[0238] Variation #7

[0239] When two PUCCH resources are configured or notified by different PUCCH spatial relation information (PUCCH spatial relationinfo), the UE may not assume a DCI format for notifying a PUCCH resource on non-SBFD and another DCI format for notifying a PUCCH resource on non-SBFD.

[0240] Variation #8

[0241] When two PUCCH resources are configured or notified by different PUCCH spatial relation information (PUCCH spatial relationinfo), the UE may not assume a DCI format for notifying PUCCH resources on SBFD and another DCI format for notifying PUCCH resources on SBFD.

[0242] In addition, variations #3 to #8 may be applied to any situation where the PUSCH and / or PUCCH closed loop is for SBFD operation or non-SBFD operation, transparent or non-transparent.

[0243] According to Alt-1, it is possible to provide an example of mapping between uplink transmission beam indices such as SRI and / or PUCCH spatial relation information (PUCCH spatialrelation info) and PUSCH and / or PUCCH closed loop indices.

[0244] <alt-2>

[0245] In Alt-2, an uplink transmit beam index such as an SRI and / or PUCCH spatial relation info may also be mapped to a PUSCH and / or PUCCH closed-loop index for non-SBFD operation and a PUSCH and / or PUCCH closed-loop index for SBFD operation. Fig. 20 As shown, SRI#m may be mapped to PUSCH loop #i0 for non-SBFD operation and PUSCH loop #i3 for SBFD operation, and SRI#n may be mapped to PUSCH loop #i1 for non-SBFD operation and PUSCH loop #i2 for SBFD operation.

[0246] For example, it is conceivable that the SRI is notified in the DCI format 0_1 / 0_2 for scheduling PUSCH, or that the PUCCH resources based on specific PUCCH spatial relation information (PUCCH spatial relation info) are notified or determined for PUCCH. In these cases, when PUSCH and / or PUCCH are on SBFD, the associated PUSCH and / or PUCCH closed-loop index for SBFD operation can also be applied to the power calculation of PUSCH and / or PUCCH. On the other hand, when PUSCH and / or PUCCH are on non-SBFD, the associated PUSCH and / or PUCCH closed-loop index for non-SBFD operation can also be applied to the power calculation of PUSCH and / or PUCCH.

[0247] For example, for DCI format 0_1 / 0_2 with a TPC adjustment command field, the following Opt-a and Opt-b may also be performed. In Opt-a, when the scheduled PUSCH is on SBFD, the notified adjustment may also be applied only to the PUSCH closed-loop index for SBFD operation associated with the notified SRI. On the other hand, when the scheduled PUSCH is on non-SBFD, the notified adjustment may also be applied only to the PUSCH closed-loop index for non-SBFD operation associated with the notified SRI.

[0248] Furthermore, in Opt-b, the notified adjustment may be applied to the PUSCH closed loop index for SBFD operation and the PUSCH closed loop index for non-SBFD operation associated with the notified SRI, regardless of whether the scheduled PUSCH is on SBFD or non-SBFD.

[0249] In addition, for example, for DCI format 1_1 / 1_2 in which a TPC adjustment command field exists, the following Opt-a and Opt-b may also be performed. In Opt-a, in the case where the notified PUCCH is on SBFD, the notified adjustment may also be applied only to the PUCCH closed-loop index for SBFD operation associated with the PUCCH spatial relation information (PUCCH spatial relation info) of the notified PUCCH resource. On the other hand, in the case where the notified PUCCH is on non-SBFD, the notified adjustment may also be applied only to the PUCCH closed-loop index for non-SBFD operation associated with the PUCCH spatial relation information (PUCCH spatialrelation info) of the notified PUCCH resource.

[0250] In addition, in Opt-b, the notified adjustment can also be applied to the PUCCH closed-loop index for SBFD operation and the PUCCH closed-loop index for non-SBFD operation associated with the PUCCH spatial relation information (PUCCH spatial relationinfo) of the notified PUCCH resource, regardless of whether the notified PUCCH is on SBFD or non-SBFD.

[0251] For example, in Fig.21 In the example shown, 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 loop #i3, and the adjustment notified by DCI#2 may be applied only to PUSCH loop #i1. On the other hand, in Opt-b, the adjustment notified by DCI#1 may be applied only to PUSCH loop #i0 and #i3, and the adjustment notified by DCI#2 may be applied only to PUSCH loop #i1 and #i3.

[0252] <alt-2-1>

[0253] The new parameters sri-PUSCH-ClosedLoopIndex-SBFD and / or pucch-ClosedLoopIndex-r17-SBFD may also be used to notify the PUSCH and / or PUCCH closed loop index for the corresponding SBFD operation for SRI and / or PUCCH spatial relation info. Fig. 22 As shown, in the SRI-PUSCH-PowerControl IE, sri-PUSCH-ClosedLoopIndex for notifying the PUSCH closed loop index for non-SBFD operation and sri-PUSCH-ClosedLoopIndex-SBFD for notifying the PUSCH closed loop index for SBFD operation can also be set. One SRI can be mapped to the PUSCH closed loop index for SBFD operation and the PUSCH closed loop index for non-SBFD operation.

[0254] When sri-PUSCH-ClosedLoopIndex-SBFD and / or pucch-ClosedLoopIndex-r17-SBFD is not set, the UE may not assume that SRI and / or PUCCH spatial relation information (PUCCH spatial relationinfo) is notified for PUSCH and / or PUCCH on SBFD.

[0255] <alt-2-2>

[0256] In addition, when Alt-c is applied to the above-mentioned problem point 1, that is, when there is a one-to-one mapping of PUSCH and / or PUCCH closed loops for SBFD operation and non-SBFD operation, if the PUSCH and / or PUCCH closed loops for non-SBFD operation are notified through the existing sri-PUSCH-ClosedLoopIndex and / or pucch-ClosedLoopIndex-r17, then this can also implicitly notify the PUSCH and / or PUCCH closed loop indexes for SBFD operation.

[0257] For example, when twoPUSCH-PC-AdjustmentStates is not set and sri-PUSCH-ClosedLoopIndex is set to i0, this may implicitly mean that SRI is mapped to PUSCH closed loop index #i0 for non-SBFD operation and PUSCH closed loop index #i1 or #i2 for SBFD operation. In addition, it is unknown whether the PUSCH closed loop index for SBFD operation starts from i2 or i1.

[0258] On the other hand, when twoPUSCH-PC-AdjustmentStates is set, and in addition, sri-PUSCH-ClosedLoopIndex is set to i0 or i1, this may implicitly mean that SRI is mapped to PUSCH closed loop index #i0 or #i1 for non-SBFD operation, and PUSCH closed loop index #i2 or #i3 for SBFD operation. Fig.23 In the example shown, SRI#m can be associated with PUSCH loop index #i0 for non-SBFD operation and PUSCH loop index #i2 for SBFD operation, and SRI#n can be associated with PUSCH loop index #i1 for non-SBFD operation and PUSCH loop index #i3 for SBFD operation. In addition, for SRI-PUSCH-PowerControl, there is no impact on the specification.

[0259] Similarly, for example, when twoPUCCH-PC-AdjustmentStates is not set, and in addition, pucch-ClosedLoopIndex-r17 is set to i0, this may implicitly mean that the PUCCH resource is mapped to the PUCCH closed loop index #i0 for non-SBFD operation and the PUCCH closed loop index #i1 or #i2 for SBFD operation. In addition, it is not known whether the PUCCH closed loop index for SBFD operation starts from i2 or i1.

[0260] On the other hand, when twoPUSCH-PC-AdjustmentStates is set, and in addition, pucch-ClosedLoopIndex-r17 is set to i0 or i1, this may implicitly mean that the PUCCH resources are mapped to PUCCH closed loop index #i0 or #i1 for non-SBFD operation, and PUCCH closed loop index #i2 or #i3 for SBFD operation.

[0261] (Question 3)

[0262] As problem point 3, the mapping relationship between the configured grant (Configured Grant (CG)) PUSCH configuration and the PUSCH closed-loop index can be studied.

[0263] <alt-1>

[0264] In Alt-1, the CG PUSCH setting may also be set by a 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 also be a PUSCH closed loop for SBFD operation or a PUSCH closed loop for non-SBFD operation. The description in Alt-2 of Problem 2 may also be reused by replacing sri-PUSCH-ClosedLoopIndex with powerControlLoopToUse.

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

[0266] Alternatively, when Alt-b is applied to the above-mentioned problem 1, the candidate values ​​of the powerControlLoopToUse field can be {i0, i1, i2, i3}.

[0267] <alt-2>

[0268] In Alt-2, the CG PUSCH setting can also be set by a PUSCH closed-loop index for SBFD operation and a PUSCH closed-loop index for non-SBFD operation. For example, the new parameter powerControlLoopToUse-SBFD field can also be used to notify the corresponding PUSCH closed-loop index for SBFD operation for CG PUSCH. For example, in the ConfiguredGrantConfig IE, 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 can also be set. 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.

[0269] When powerControlLoopToUse-SBFD is not set, the UE may not assume that the CG PUSCH is notified for the PUSCH on SBFD.

[0270] In addition, when Alt-c is applied to the above-mentioned problem point 1, that is, when the PUSCH loop for SBFD operation and the PUSCH loop for non-SBFD operation are mapped one-to-one, if the PUSCH loop for non-SBFD operation is notified through the existing powerControlLoopToUse, then this situation can also implicitly notify the PUSCH loop index for SBFD operation. In addition, for powerControlLoopToUse, there is no impact on the specification.

[0271] In Proposal 2, the UE may also set the transmit power in SBFD operation according to the closed loop for SBFD, and may also 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 also be specified by the specification, or semi-persistently set by RRC setting, or dynamically notified by DCI notification, etc. In addition, the closed loop for SBFD and / or the closed loop for non-SBFD may also be explicitly or implicitly specified, set, notified, or applied.

[0272] The UE may also transmit the uplink channel at the transmission power based on the closed loop for SBFD in the SBFD operation, and may also transmit the uplink channel at the transmission power based on the closed loop for non-SBFD in the non-SBFD operation. For example, in association with Problem 1, the total number of closed loops may be set, and the UE may set the transmission power in the SBFD operation based on the closed loop for SBFD among the set total number of closed loops, and may set the transmission power in the non-SBFD operation based on the closed loop for non-SBFD among the set total number of closed loops.

[0273] In addition, in association with problem point 2, the UE may also set the transmit power in the SBFD operation based on the mapping between the uplink transmit beam and the closed loop index, and set the transmit power in the non-SBFD operation. In addition, in association with problem point 3, the UE may also set the transmit power in the SBFD operation based on the mapping between the uplink shared channel setting for which permission has been set and the closed loop index, and set the transmit power in the non-SBFD operation.

[0274] On the other hand, the gNB may also set the transmit power in SBFD operation for the UE through the closed loop for SBFD, and may also set the transmit power in non-SBFD operation for the UE through the closed loop for non-SBFD. Here, the closed loop for SBFD and / or the closed loop for non-SBFD may also be specified by the specification, or semi-persistently set through RRC settings, or dynamically notified through DCI notifications, etc. In addition, the closed loop for SBFD and / or the closed loop for non-SBFD may also be explicitly or implicitly specified, set, notified, or applied.

[0275] The gNB may receive an uplink channel transmitted from the UE at a transmission power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE at a transmission power for non-SBFD in non-SBFD operation. For example, in connection with Problem Point 1, the total number of closed loops may be set, and the gNB may set the transmission power in SBFD operation based on the closed loops for SBFD among the total number of closed loops set, and may set the transmission power in non-SBFD operation based on the closed loops for non-SBFD among the total number of closed loops set.

[0276] In addition, in association with problem point 2, the gNB may also set the transmit power in SBFD operation based on the mapping between the uplink transmit beam and the closed loop index, and set the transmit power in non-SBFD operation. In addition, in association with problem point 3, the gNB may also set the transmit power in SBFD operation based on the mapping between the uplink shared channel setting for which permission has been set and the closed loop index, and set the transmit power in non-SBFD operation.

[0277] In addition, the UE may also report to the gNB the UE capability related to whether different PUSCH and / or PUCCH closed loops are supported for SBFD operation and non-SBFD operation. The gNB may also determine whether to perform different PUSCH and / or PUCCH closed loop control for SBFD operation and non-SBFD operation based on the obtained UE capability. In addition, the UE may also report to the gNB the UE capability related to whether an SRI is mapped to the PUSCH closed loop of SBFD operation and non-SBFD operation at the same time. In addition, the UE may also report to the gNB the UE capability related to whether a PUCCH spatial relation information (PUCCH spatial relation info) is mapped to the PUCCH closed loop of SBFD operation and non-SBFD operation at the same time.

[0278] Thus, in Proposal 2, different closed loops are applied to SBFD operation and non-SBFD operation. Thus, different PUSCH and / or PUCCH transmission powers can be dynamically notified to the UE in each of the SBFD operation and non-SBFD operation, thereby reducing the possibility of inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0279] [Proposal 3]

[0280] In Proposal 3, the UE may transmit uplink channels in SBFD operation using a transmission power set according to the transmission power calculation formula for SBFD operation, and may transmit uplink channels in non-SBFD operation using a transmission power set according to the transmission power calculation formula for non-SBFD operation.

[0281] (Option 1)

[0282] In Option 1, the scaling factor for PUSCH and / or PUCCH transmit power calculation for SBFD operation may also be applied. Fig.24 In the example shown, the PUSCH and / or PUCCH transmit power for non-SBFD operation based on the existing NR can also be increased by multiplying with the scaling factor.

[0283] For example, the transmit power of PUSCH (P PUSCH, b, f, c (i, j, q d, , l)) can also be expressed by the following formula (3).

[0284] [Mathematical formula 3]

[0285]

[0286] In equation (3), the scaling factor β used for calculating the PUSCH transmission power for SBFD operation is multiplied by the second variable of the min function of the above-mentioned PUSCH transmission power calculation equation (1).

[0287] In another example, the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d, , l)) can also be expressed by the following formula (4).

[0288] [Formula 4]

[0289]

[0290] In equation (4), the scaling factor β used for calculating the PUSCH transmission power for SBFD operation is multiplied by the output of the min function of the above-mentioned PUSCH transmission power calculation equation (1). In addition, when the scaling factor β is greater than 1, equation (4) may be set to be inapplicable.

[0291] In another example, the transmission power (P PUSCH, b, f, c (i, j, q d, , l)) can also be expressed by the following formula (5).

[0292] [Mathematical formula 5]

[0293]

[0294] In equation (5), the scaling factor β used for calculating the PUSCH transmit power for SBFD operation is multiplied by the output of the min function of the PUSCH transmit power calculation equation (1) above, and then the product is P CMAX, f, c The smaller value in (i) is set.

[0295] In addition, although the above-mentioned equations (3) to (5) are related to the calculation of PUSCH transmission power, the scaling factor β can also be applied to the calculation equation of PUCCH transmission power.

[0296] Here, the scaling factor β may also be specified by a specification, or semi-persistently set by RRC settings, or dynamically notified by DCI notifications, or determined by the UE according to specific rules (e.g., PUSCH RB size and / or PUSCH repetition number on SBFD, etc.). In addition, the scaling factor β may also be explicitly or implicitly specified, set, notified, or applied.

[0297] (Option 2)

[0298] In option 2, the power offset used for PUSCH and / or PUCCH transmit power calculation for SBFD operation may also be applied. Fig.25 In the example shown, the PUSCH and / or PUCCH transmission power for non-SBFD operation based on the existing NR can also be increased by adding the power offset.

[0299] For example, the transmit power of PUSCH (P PUSCH, b, f, c (i, j, q d, , l)) can also be expressed by the following formula (6).

[0300] [Mathematical formula 6]

[0301]

[0302] In equation (6), the power offset used for calculating the PUSCH transmit power for SBFD operation is The second variable of the min function in the above-mentioned PUSCH transmission power calculation formula (1) is added.

[0303] In another example, the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d, , l)) can also be expressed by the following formula (7).

[0304] [Formula 7]

[0305]

[0306] In equation (7), the power offset used for calculating the PUSCH transmit power for SBFD operation is Add the output of the min function of the above PUSCH transmission power calculation formula (1). When is greater than 0, equation (7) can also be set to be inapplicable.

[0307] In another example, the transmission power (P PUSCH, b, f, c (i, j, q d, , l)) can also be expressed by the following formula (8).

[0308] [Mathematical formula 8]

[0309]

[0310] In equation (8), the power offset used to calculate the PUSCH transmit power for SBFD operation is The output of the min function of the above PUSCH transmission power calculation formula (1) is added, and the sum is then added to P CMAX, f, c The smaller value in (i) is set.

[0311] In addition, although the above equations (6) to (8) are related to the calculation of PUSCH transmission power, the power offset The same can also be applied to the calculation formula of PUCCH transmission power.

[0312] Here, the power offset It can also be specified by the specification, semi-persistently set by RRC settings, dynamically notified by DCI notification, or determined by the UE according to specific rules (for example, PUSCH RB size and / or PUSCH repetition number on SBFD). It may also be specified, set, notified or applied explicitly or implicitly.

[0313] (Option 3)

[0314] In option 3, the reference RB size used for PUSCH and / or PUCCH transmit power calculation for SBFD operation can also be used. Fig.26 In the example shown, the reference RB size corresponding to the uplink frequency band portion in SBFD may be used in the calculation of the PUSCH transmission power for SBFD operation instead of the actual RB size of the PUSCH.

[0315] Specifically, the parameter M in the calculation formula (1) for PUSCH transmission power is RB, b, f, c PUSCH , it is also possible to not apply the actual RB size of the PUSCH on SBFD and apply option 3-1 or 3-2.

[0316] <Option 3-1>

[0317] In option 3-1, regarding parameter M RB, b, f, c PUSCH For example, if it exists, it can also be the RB size of other PUSCH repetitions on non-SBFD, etc., independent of the actual RB size of PUSCH on SBFD. RB, b, f, c PUSCH It may also be specified by the specification, semi-persistently set by RRC settings, dynamically notified by DCI notification, or determined by the UE according to specific rules (e.g., PUSCH RB size and / or PUSCH repetition number on SBFD, etc.). RB, b, f, c PUSCH It may also be specified, set, notified or applied explicitly or implicitly.

[0318] <Option 3-2>

[0319] In option 3-2, parameter M RB, b, f, c PUSCH It may also be a fixed RB size offset based on the actual PUSCH RB size, a scaling factor based on the actual PUSCH RB size, an offset value based on the actual PUSCH RB size, etc., depending on the actual RB size of the PUSCH on SBFD. The fixed RB size offset may also be specified by a specification, or semi-persistently set by RRC settings, etc., or dynamically notified by DCI notifications, etc., or determined by the UE according to specific rules (e.g., PUSCH RB size and / or PUSCH repetition number on SBFD, etc.). In addition, the fixed RB size offset may also be explicitly or implicitly specified, set, notified, or applied.

[0320] For example, the gNB may also directly notify or set the RB size offset value. In addition, the mapping relationship 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" to "fixed RB size offset" may also be specified by the specification, or semi-persistently set by RRC settings, or dynamically notified by DCI notification, or determined by the UE according to specific rules (e.g., PUSCH RB size on SBFD and / or PUSCH repetition number, etc.).

[0321] In addition, the scaling factor based on the actual PUSCH RB size may also be specified by the specification, or semi-persistently set by RRC settings, or dynamically notified by DCI notifications, or determined by the UE according to specific rules (e.g., PUSCH RB size and / or PUSCH iteration number on SBFD, etc.). In addition, the fixed RB size offset may also be explicitly or implicitly specified, set, notified or applied.

[0322] For example, the gNB may also directly notify or set the scaling factor value. In addition, the mapping relationship 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" to "scaling factor" may also be specified by the specification, or semi-persistently set by RRC settings, or dynamically notified by DCI notifications, or determined by the UE according to specific rules (e.g., PUSCH RB size on SBFD and / or PUSCH repetition number, etc.).

[0323] In addition, as a variation, considering that the downlink / uplink subband size is cell-specific, the parameters in options 1 to 3, i.e., the scaling factor of option 1, the power offset of option 2, and / or the reference RB size of option 3, may also be cell-specific, and may also be common to multiple UEs in the cell. In this case, for example, a common parameter for increasing the uplink power in SBFD operation may also be applied. Alternatively, two common parameters, a parameter for increasing the uplink power in SBFD operation and a parameter for reducing the uplink power in SBFD operation, may also be applied.

[0324] In addition, as a variation, Proposal 3 may be applied together with the restriction of PUSCH and / or PUCCH closed loop common to SBFD operation and non-SBFD operation. Alternatively, Proposal 2 and Proposal 3 may be applied together.

[0325] In Proposal 3, the UE may also set the transmit power in SBFD operation according to the power calculation formula for SBFD, and set the transmit power in non-SBFD operation according to the power calculation formula for non-SBFD. Here, the power calculation formula for SBFD may also be specified by the specification, or semi-persistently set by RRC settings, or dynamically notified by DCI notifications. In addition, the power calculation formula for SBFD may also be explicitly or implicitly specified, set, notified, or applied.

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

[0327] On the other hand, the gNB may also set the transmit power in SBFD operation for the UE according to the power calculation formula for SBFD, and set the transmit power in non-SBFD operation for the UE according to the power calculation formula for non-SBFD. Here, the power calculation formula for SBFD may also be specified by the specification, or semi-continuously set by RRC settings, or dynamically notified by DCI notifications. In addition, the power calculation formula for SBFD may also be explicitly or implicitly specified, set, notified, or applied.

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

[0329] In addition, the UE may also report to the gNB the UE capability related to whether it supports the power calculation formula for PUSCH and / or PUCCH adjusted for SBFD.

[0330] Thus, in Proposal 3, different transmit power calculation formulas are applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmit power calculation formulas can be applied to UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0331] <Hardware Structure>

[0332] In addition, the block diagram used in the description of the above-mentioned embodiment shows a block of a functional unit. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented by a device that is physically or logically combined, or two or more physically or logically separated devices can be directly or indirectly connected (for example, by wire, wireless, etc.) and implemented by these multiple devices. The functional block can also be implemented by combining the above-mentioned one device or the above-mentioned multiple devices with software.

[0333] Functions include judging, deciding, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that implements a sending function is called a transmitting unit or a transmitter. As described above, the implementation method is not particularly limited.

[0334] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 27 1 is a diagram showing an example of the hardware structure of a base station and a user terminal involved in one embodiment of the present disclosure. The above-mentioned base station 10 and user terminal 20 can also 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.

[0335] In the following description, the term "device" can be rewritten as circuit, device, unit, etc. The hardware configuration of the base station 10 and the user terminal 20 can be configured as Fig. 27 Each device shown in the figure may include one or more devices, and may be configured not to include some devices.

[0336] The functions of the base station 10 and the user terminal 20 are realized by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls the communication based on the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0337] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, etc. For example, the above-mentioned baseband signal processing unit 104, call processing unit 105, etc. may also be implemented by the processor 1001.

[0338] In addition, the processor 1001 reads the program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and performs various processes according to them. As a program, a program that enables a computer to perform at least a part of the operations described in the above-mentioned embodiments can be used. For example, the control unit 401 of the user terminal 20 can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001, and the same can be implemented for other functional blocks. The above-mentioned various processes are described as being performed by one processor 1001, but can also be performed simultaneously or sequentially by more than two processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via an electrical communication line.

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

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

[0341] The communication device 1004 is hardware (transmitting and receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, etc. In order to realize at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex), the communication device 1004 can also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the above-mentioned transmitting and receiving antenna 101, the amplifier unit 102, the transmitting and receiving unit 103, the transmission path interface 106, etc. can also be realized by the communication device 1004. The transmitting and receiving unit 103 can also be realized by physically or logically separating the transmitting unit 103a and the receiving unit 103b.

[0342] The input device 1005 is an input device that receives input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that performs output to the outside (for example, a display, a speaker, an LED light, etc.). In addition, the input device 1005 and the output device 1006 may also be an integrated structure (for example, a touch panel).

[0343] In addition, the processor 1001, the memory 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured as a single bus or may be configured as different buses between the devices.

[0344] In addition, the base station 10 and the user terminal 20 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and a part or all of each functional block may be implemented by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0345] The notification of information is not limited to the methods / implementations described in the present disclosure, and may also be performed by other methods. For example, the notification of information may also be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), high-level signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals or a combination thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, and the like.

[0346] The various modes and embodiments described in the present disclosure may also be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG)) (xG (x is, for example, an integer or a decimal)), 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.16 (WiMAX (registered trademark)), IEEE At least one of 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), a system using other appropriate systems, and a next-generation system expanded, modified, produced, and specified based on them. In addition, multiple systems can also be combined (for example, a combination of at least one of LTE and LTE-A and 5G, etc.) for application.

[0347] The processing procedures, sequences, flow charts, etc. of each method / implementation described in this disclosure may be reversed in order as long as they are not contradictory. For example, for the method described in this disclosure, various step elements are presented in an illustrative order, but are not limited to the specific order presented.

[0348] In the present disclosure, a specific operation is performed by a base station, and sometimes it is performed by its upper node according to the situation. Obviously, in a network composed of one or more network nodes having a base station, various operations performed for communication with a terminal may also be performed by at least one of the base station and other network nodes other than the base station (for example, consider MME or S-GW, etc., but not limited to these). In the above, the case where there is one other network node other than the base station is illustrated, and it may also be a combination of multiple other network nodes (for example, MME and S-GW).

[0349] Information, etc. (see the item "Information, signal") can also be output from a higher layer (or lower layer) to a lower layer (or higher layer). It can also be input and output via multiple network nodes.

[0350] The input and output information can be stored in a specific location (e.g., a memory) or managed using a management table. The input and output information can be overwritten, updated, or added. The output information can also be deleted. The input information can also be sent to other devices.

[0351] The determination may be made by a value represented by a bit (0 or 1), by a true or false value (Boolean value: true or false), or by comparison of numerical values ​​(for example, comparison with a specific value).

[0352] The various methods / implementations described in this disclosure may be used alone or in combination, and may be switched during execution. In addition, notification of specific information (e.g., notification of "it is X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the specific information).

[0353] The present disclosure has been described in detail above, but it is obvious to 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 a modification and variation without departing from the subject matter and scope of the present disclosure determined according to the records of the claims. Therefore, the description of the present disclosure is for the purpose of illustration and does not have any restrictive meaning to the present disclosure.

[0354] Whether software is called software, firmware, middle-ware, microcode, hardware description language, or other names, it should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, program, sub-program, software module, application, software application, software package, routine, sub-routine, object, executable files, execution thread, procedure, function, etc.

[0355] In addition, software, instructions, information, etc. may also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[0356] Information, signals, etc. described in the present disclosure may also be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be mentioned throughout the above description may also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0357] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may also be replaced with terms having the same or similar meanings. For example, at least one of a channel and a code element may also be a signal (signaling). In addition, a signal may also be a message. In addition, a component carrier (CC) may also be referred to as a carrier frequency, a cell, a frequency carrier, etc.

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

[0359] In addition, the information, parameters, etc. described in the present disclosure may be expressed by absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, a wireless resource may also be indicated by an index.

[0360] The names used for the above parameters are not limiting in all respects. Furthermore, sometimes the mathematical formulas, etc., using these parameters are different from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore, the various names assigned to these various channels and information elements are not limiting in all respects.

[0361] In the present disclosure, terms such as "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", "carrier", and "component carrier" can be used interchangeably. Base stations may also be referred to by terms such as macro cell, small cell, femto cell, and pico cell.

[0362] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station for indoor use (remote radio head (RRH))). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of ​​at least one of a base station and a base station subsystem that provides communication services within the coverage area.

[0363] In the present disclosure, the base station sending information to the terminal can also be rewritten as the base station instructing the terminal to control and operate based on the information.

[0364] In the present disclosure, terms such as “mobile station (MS)”, “user terminal (user terminal)”, “user device (UE: User Equipment)”, and “terminal” can be used interchangeably.

[0365] There are also cases where a mobile station is referred to by those skilled in the art as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a hand set, a user agent, a mobile client, a client, or several other appropriate terms.

[0366] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. In addition, at least one of the base station and the mobile station may also be a device carried in a mobile body, a mobile body, etc. The mobile body refers to a movable object, and the moving speed is arbitrary. In addition, of course, it also includes the situation where the mobile body stops. The mobile body includes, for example, vehicles, transport vehicles, cars, automatic two-wheeled vehicles, bicycles, networked cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers, rickshaws, ships (ships and other watercrafts other than these), airplanes, rockets, artificial satellites, drones (registered trademarks), multi-rotor aircraft, quadcopters, balloons, and objects carried on them, and are not limited to these. In addition, the mobile body may also be a mobile body that travels autonomously based on an operating instruction. It may be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile body that moves in an unmanned manner (e.g., a drone, an autonomous driving vehicle, etc.), or a robot (man- or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move when performing communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0367] In addition, the base station in the present disclosure may also be rewritten as a user terminal. For example, the various methods / implementations of the present disclosure may also be applied to a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple user terminals (for example, it may also be referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, it may also be set as a structure in which the user terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" may also be rewritten as terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. may also be rewritten as side channels.

[0368] Likewise, the user terminal in the present disclosure may be rewritten as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0369] Fig.28 The following is a structural example of a vehicle 1. As shown in FIG39 , 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 sensors 21 to 29, an information service unit 12, and a communication module 13.

[0370] The drive unit 2 is constituted by, for example, an engine, a motor, or a mixture of an engine and a motor.

[0371] The steering unit 3 is configured to include at least a steering wheel (also referred to as a handlebar), and steers at least one of the front wheels and the rear wheels based on an operation of the steering wheel operated by a user.

[0372] The electronic control unit 10 includes a microprocessor 31, a memory (ROM, RAM) 32, and a 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 referred to as an ECU (Electronic Control Unit).

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

[0374] The information service unit 12 is composed of various devices such as a car navigation system, an audio system, a speaker, a television, and a radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 12 uses information obtained from an external device via the communication module 13 and the like to provide various multimedia information and multimedia services to the occupants of the vehicle 1.

[0375] The information service unit 12 may include input devices for accepting input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.), and may also include output devices for implementing output to the outside (e.g., display, speaker, LED light, touch panel, etc.).

[0376] The driving assistance system unit 30 is composed of various devices for providing functions for preventing accidents or reducing the driver's driving load, such as millimeter wave radar, LiDAR (Light Detection and Ranging), camera, locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) mapping, autonomous driving vehicle (AV) mapping, etc.), gyroscope system (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, AI processor, and one or more ECUs that control these devices. In addition, the driving assistance system unit 30 sends and receives various information via the communication module 13 and realizes the driving assistance function or the autonomous driving function.

[0377] 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 sends and receives data between the drive unit 2, the steering unit 3, the accelerator pedal 4, the brake pedal 5, the shift lever 6, the left and right front wheels 7, the left and right rear wheels 8, the axle 9, the microprocessor 31 and the memory (ROM, RAM) 32 in the electronic control unit 10, and the sensors 21 to 28 via the communication port 33.

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

[0379] The communication module 13 may also transmit at least one of the signals from the various sensors 21-28 input to the electronic control unit 10, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 12 to an external device via wireless communication. The electronic control unit 10, the various sensors 21-28, the information service unit 12, etc. may also be referred to as an input unit that receives input. For example, the PUSCH transmitted through the communication module 13 may also include information based on the above input.

[0380] The communication module 13 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from an external device, and displays it to the information service unit 12 provided in the vehicle. The information service unit 12 may also be referred to as an output unit that outputs information (for example, outputs information to a display, a speaker, etc. based on the PDSCH received by the communication module 13 (or data / information decoded from the PDSCH)).

[0381] In addition, the communication module 13 stores various information received from the external device in the memory 32 that can be used by the microprocessor 31. The microprocessor 31 can also control the drive unit 2, the steering unit 3, the accelerator pedal 4, the brake pedal 5, the shift lever 6, the left and right front wheels 7, the left and right rear wheels 8, the axle 9, the sensors 21 to 28, etc., which are provided in the vehicle 1, based on the information stored in the memory 32.

[0382] (Summary of implementation methods)

[0383] As described above, according to one embodiment of the present disclosure, there is provided a terminal comprising: a control unit, which sets a first transmission power in a SBFD (Subband non-overlapping FullDuplex) operation according to a first transmission power setting, and sets a second transmission power in a non-SBFD operation according to a second transmission power setting; and a transmission unit, which transmits an uplink channel at the first transmission power in the SBFD operation, and transmits an uplink channel at the second transmission power in the non-SBFD operation.

[0384] According to the above structure, different transmission power control parameters are applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmission powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0385] In one embodiment, the first transmit power setting and the second transmit power setting may also be specified by different transmit power setting information elements for the SBFD operation and the non-SBFD operation. According to this embodiment, different PUSCH and / or PUCCH transmit powers can be set for the UE in the SBFD operation and the non-SBFD operation, respectively, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during the SBFD operation can be reduced.

[0386] In one embodiment, the first transmit power setting and the second transmit power setting may also be specified by the first transmit power parameter for the SBFD operation and the second transmit power parameter for the non-SBFD operation in the same transmit power setting information element. According to this embodiment, different PUSCH and / or PUCCH transmit powers can be set for the UE in the SBFD operation and the non-SBFD operation, respectively, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during the SBFD operation can be reduced.

[0387] In one embodiment, the uplink channel may also include one or more of an uplink shared channel, an uplink control channel, and a random access channel. According to this embodiment, different PUSCH and / or PUCCH transmission powers can be set for the UE in SBFD operation and non-SBFD operation, respectively, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation can be reduced.

[0388] In addition, according to one embodiment of the present disclosure, the following base station is provided, which includes: a control unit, which sets a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation for a terminal through a first transmission power setting, and sets a second transmission power in a non-SBFD operation for the terminal through a second transmission power setting; and a receiving unit, which receives an uplink channel sent from the terminal through the first transmission power in the SBFD operation, and receives an uplink channel sent from the terminal through the second transmission power in the non-SBFD operation.

[0389] According to the above structure, different transmission power control parameters can be applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmission powers can be set for UE in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0390] In addition, according to one embodiment of the present disclosure, there is provided a wireless communication method performed by a terminal, comprising: setting a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first transmission power setting, and setting a second transmission power in a non-SBFD operation according to a second transmission power setting; and sending an uplink channel using the first transmission power in the SBFD operation, and sending an uplink channel using the second transmission power in the non-SBFD operation.

[0391] According to the above structure, different transmission power control parameters are applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmission powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0392] In addition, according to one embodiment of the present disclosure, a terminal is provided, comprising: a control unit, which sets a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first closed loop, and sets a second transmission power in a non-SBFD operation according to a second closed loop; and a transmission unit, which transmits an uplink channel using the first transmission power in the SBFD operation, and transmits an uplink channel using the second transmission power in the non-SBFD operation.

[0393] According to the above structure, different closed loops are applied for SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmission powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0394] In one embodiment, the total number of closed loops may be set, and the control unit may set the first transmission power in the SBFD operation according to the first closed loop in the total number of closed loops, and may set the second transmission power in the non-SBFD operation according to the second closed loop in the total number of closed loops. According to this embodiment, different PUSCH and / or PUCCH transmission powers can be set for the UE in the SBFD operation and the non-SBFD operation, respectively, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during the SBFD operation can be reduced.

[0395] In one embodiment, the control unit may set the first transmit power in the SBFD operation and the second transmit power in the non-SBFD operation according to the mapping between the uplink transmit beam and the closed-loop index. According to this embodiment, different PUSCH and / or PUCCH transmit powers can be set for the UE in the SBFD operation and the non-SBFD operation, respectively, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during the SBFD operation can be reduced.

[0396] In one embodiment, the control unit may set the first transmission power in the SBFD operation and the second transmission power in the non-SBFD operation according to the mapping between the uplink shared channel setting and the closed loop index that has been set. According to this embodiment, different PUSCH and / or PUCCH transmission powers can be set for the UE in the SBFD operation and the non-SBFD operation, respectively, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during the SBFD operation can be reduced.

[0397] In addition, according to one embodiment of the present disclosure, a base station is provided, comprising: a control unit, which sets a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation for a terminal through a first closed loop, and sets a second transmission power in a non-SBFD operation for the terminal through a second closed loop; and a receiving unit, which receives an uplink channel sent from the terminal through the first transmission power in the SBFD operation, and receives an uplink channel sent from the terminal through the second transmission power in the non-SBFD operation.

[0398] According to the above structure, different closed loops are applied for SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmission powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0399] In addition, according to one embodiment of the present disclosure, there is provided a wireless communication method performed by a terminal, comprising: setting a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first closed loop, and setting a second transmission power in a non-SBFD operation according to a second closed loop; and transmitting an uplink channel using the first transmission power in the SBFD operation, and transmitting an uplink channel using the second transmission power in the non-SBFD operation.

[0400] According to the above structure, different closed loops are applied for SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmission powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0401] In addition, according to one embodiment of the present disclosure, a terminal is provided, comprising: a control unit, which 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; and a transmission unit, which transmits an uplink channel at the first transmission power in the SBFD operation, and transmits an uplink channel at the second transmission power in the non-SBFD operation.

[0402] According to the above structure, different transmit power calculation formulas are applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmit powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0403] In one embodiment, the first power calculation formula may also be derived by multiplying the second power calculation formula by a scaling factor. According to this embodiment, different PUSCH and / or PUCCH transmit powers can be set for the UE in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0404] In one embodiment, the first power calculation formula may also be derived by adding an offset value to the second power calculation formula. According to this embodiment, different PUSCH and / or PUCCH transmit powers can be set for the UE in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0405] In one embodiment, the first power calculation formula may also be calculated by applying a reference resource block size to the second power calculation formula. According to this embodiment, different PUSCH and / or PUCCH transmit powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, and the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation can be reduced.

[0406] In addition, according to one embodiment of the present disclosure, the following base station is provided, which comprises: a control unit, which sets a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation for a terminal through a first power calculation formula, and sets a second transmission power in a non-SBFD operation for the terminal through a second power calculation formula; and a receiving unit, which receives an uplink channel sent from the terminal through the first transmission power in the SBFD operation, and receives an uplink channel sent from the terminal through the second transmission power in the non-SBFD operation.

[0407] According to the above structure, different transmit power calculation formulas are applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmit powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0408] In addition, according to one embodiment of the present disclosure, there is provided a wireless communication method performed by a terminal, comprising: setting a first transmission power in a SBFD (Subband non-overlapping FullDuplex) 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; and transmitting an uplink channel using the first transmission power in the SBFD operation, and transmitting an uplink channel using the second transmission power in the non-SBFD operation.

[0409] According to the above structure, different transmit power calculation formulas are applied to SBFD operation and non-SBFD operation. Therefore, different PUSCH and / or PUCCH transmit powers can be set for UEs in SBFD operation and non-SBFD operation, respectively, which can reduce the possibility of generating inter-UE CLI and / or inter-gNB CLI during SBFD operation.

[0410] (Supplementary information on implementation methods)

[0411] The terms "determining" and "determining" used in the present disclosure may include a variety of actions. For example, "determining" and "determining" may include situations where judging, calculating, computing, processing, deriving, investigating, looking up (for example, searching in a table, database or other data structure), ascertaining, etc. are considered to have been "judged" or "determined". In addition, "determining" and "determining" may include situations where receiving (for example, receiving information), transmitting (for example, sending information), inputting, outputting, accessing (for example, accessing data in a memory) are considered to have been "judged" or "determined". In addition, "judgment" and "decision" may include situations where resolving, selecting, choosing, establishing, comparing, etc. are considered as "judgment" and "decision". That is, "judgment" and "decision" may include situations where some actions are considered as "judgment" and "decision". In addition, "judgment (decision)" can also be rewritten as "assuming", "expecting", "considering", etc.

[0412] The terms "connected", "coupled", or all variations thereof, mean all connections or combinations, direct or indirect, between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may also be rewritten as "access". As used in the present disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, and as several non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, and light (both visible and invisible) region.

[0413] A reference signal may also be referred to as RS (Reference Signal) for short, and may also be referred to as a pilot depending on the applied standard.

[0414] The phrase “based on” used in the present disclosure does not mean “based only on” unless otherwise specified. In other words, the phrase “based on” means both “based only on” and “based at least on”.

[0415] Any reference to an element using the terms "first", "second", etc. used in the present disclosure does not fully define the amount or order of these elements. These terms can be used in the present disclosure as a convenient method to distinguish between two or more elements. Therefore, reference to the first and second elements does not mean that only two elements can be used or that the first element must take precedence over the second element in some form.

[0416] The “unit” in the structure of each of the above-mentioned devices may be replaced by a “section”, a “circuit”, a “device”, or the like.

[0417] In the present disclosure, when the terms "include", "including", and variations thereof are used, these terms, like the term "comprising", have an inclusive meaning. Furthermore, the term "or" used in the present disclosure does not mean an exclusive OR.

[0418] A radio frame may also be composed of one or more frames in the time domain. One or more frames in the time domain may also be referred to as subframes. Further, a subframe may also be composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) that is not dependent on a parameter set (numerology).

[0419] The parameter set may also be a communication parameter applied in at least one of the transmission and reception of a certain signal or channel. For example, the parameter set may also represent at least one of the subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, wireless frame structure, specific filter processing performed by the transmitter and receiver in the frequency domain, specific windowing processing performed by the transmitter and receiver in the time domain, etc.

[0420] A time slot may also 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 time slot may also be a time unit based on a parameter set.

[0421] A time slot may also contain multiple mini-slots. Each mini-slot may also be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may also be composed of a smaller number of symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as a PDSCH (or PUSCH) mapping type B.

[0422] Radio frames, subframes, time slots, mini-time slots and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots and symbols may also be referred to by other corresponding names.

[0423] For example, a subframe may also be referred to as a transmission time interval (TTI), multiple consecutive subframes may also be referred to as TTI, and a time slot or a mini time slot may also be referred to as TTI. That is, at least one of a subframe and a TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may also be referred to as a time slot, a mini time slot, etc. instead of a subframe.

[0424] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) in TTI units. In addition, the definition of TTI is not limited to this.

[0425] TTI can also be a transmission time unit for a data packet (transport block), code block, code word, etc. that has been channel-coded, and can also be a processing unit for scheduling, link adaptation, etc. In addition, when TTI is given, the time interval (for example, the number of symbols) to which a transport block, code block, code word, etc. is actually mapped can also be shorter than the TTI.

[0426] In addition, when a time slot or a mini time slot is called a TTI, one or more TTIs (i.e., one or more time slots or one or more mini time slots) may also be the minimum time unit of scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit of scheduling may also be controlled.

[0427] A TTI having a time length of 1 ms may also be referred to as a normal TTI (TTI in LTE Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub time slot, a time slot, etc.

[0428] In addition, a long TTI (eg, normal TTI, subframe, etc.) may be rewritten as a TTI having a time length exceeding 1 ms, and a short TTI (eg, shortened TTI, etc.) may be rewritten as a TTI having a TTI length shorter than that of a long TTI and longer than 1 ms.

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

[0430] In addition, the time domain of an RB may also include one or more symbols, and may also be the length of a time slot, a mini-time slot, a subframe, or a TTI. A TTI, a subframe, etc. may also be composed of one or more resource blocks, respectively.

[0431] In addition, one or more RBs may also be referred to as a physical resource block (PRB: Physical RB), a sub-carrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, etc.

[0432] In addition, a resource block may also be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0433] A bandwidth part (BWP) (also called partial bandwidth, etc.) can also represent a subset of contiguous common RBs (common resource blocks) for a parameter set in a certain carrier. Here, common RBs can also be identified by the index of the RB based on the common reference point of the carrier. PRBs can also be defined in a BWP and numbered within the BWP.

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

[0435] At least one of the set BWPs may also be activated, and the UE may not assume that it will send or receive a specific signal / channel outside the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be rewritten as "BWP".

[0436] The above structures of radio frames, subframes, time slots, mini-time slots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

[0437] The "maximum transmit power" recorded in the present disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0438] In the present disclosure, when an article is added by translation like a, an, and the in English, for example, the present disclosure may also include a case where the noun following the article is in plural form.

[0439] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same way as "different".

[0440] Description of Reference Numerals

[0441] 10 Wireless Communication Systems

[0442] 100 base stations (gNB)

[0443] 200 Terminal (UE)

Claims

1. A terminal having: A control unit, which sets a first transmission power in a SBFD operation, i.e., a sub-band non-overlapping full-duplex operation, according to a first closed loop, and sets a second transmission power in a non-SBFD operation according to a second closed loop; and The transmitting unit transmits an uplink channel using the first transmitting power in the SBFD operation and transmits an uplink channel using the second transmitting power in the non-SBFD operation.

2. The terminal according to claim 1, wherein: The total number of closed loops set, The control unit sets a first transmission power in the SBFD operation according to the first closed loop among the total number of closed loops that are set, and sets a second transmission power in the non-SBFD operation according to the second closed loop among the total number of closed loops that are set.

3. The terminal according to claim 1, wherein: The control unit sets a first transmit power in the SBFD operation and sets a second transmit power in the non-SBFD operation according to a mapping between an uplink transmit beam and a closed-loop index.

4. The terminal according to claim 1, wherein: The control unit sets the first transmission power in the SBFD operation and sets the second transmission power in the non-SBFD operation according to a mapping between the uplink shared channel configuration for which permission has been set and the closed loop index.

5. A base station, comprising: A control unit, which sets a first transmission power in a SBFD operation, i.e., a sub-band non-overlapping full-duplex operation, for a terminal through a first closed loop, and sets a second transmission power in a non-SBFD operation for the terminal through a second closed loop; and The receiving unit receives an uplink channel transmitted from the terminal using the first transmission power in the SBFD operation, and receives an uplink channel transmitted from the terminal using the second transmission power in the non-SBFD operation.

6. A wireless communication method performed by a terminal, comprising: According to the first closed loop, a first transmission power in SBFD operation, i.e., sub-band non-overlapping full-duplex operation, is set, and according to the second closed loop, a second transmission power in non-SBFD operation is set; and An uplink channel is transmitted with the first transmission power in the SBFD operation, and an uplink channel is transmitted with the second transmission power in the non-SBFD operation.

Images