WO2024023994A1 - Terminal, station de base et procédé de communication sans fil - Google Patents

Terminal, station de base et procédé de communication sans fil Download PDF

Info

Publication number
WO2024023994A1
WO2024023994A1 PCT/JP2022/029015 JP2022029015W WO2024023994A1 WO 2024023994 A1 WO2024023994 A1 WO 2024023994A1 JP 2022029015 W JP2022029015 W JP 2022029015W WO 2024023994 A1 WO2024023994 A1 WO 2024023994A1
Authority
WO
WIPO (PCT)
Prior art keywords
sbfd
pusch
pucch
transmission power
transmission
Prior art date
Application number
PCT/JP2022/029015
Other languages
English (en)
Japanese (ja)
Inventor
大輔 栗田
浩樹 原田
チーピン ピ
ジン ワン
ラン チン
チャオピン チェン
ヨン リ
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2022/029015 priority Critical patent/WO2024023994A1/fr
Publication of WO2024023994A1 publication Critical patent/WO2024023994A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/08—Closed loop power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/38—TPC being performed in particular situations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA

Definitions

  • the present disclosure relates to a terminal, a base station, and a wireless communication method.
  • LTE Long Term Evolution
  • 3GPP Rel. 10-14 LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).
  • LTE Long Term Evolution
  • 5G 5th generation mobile communication system
  • 5G+ 6th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • 3GPP Rel.15 3GPP Rel.15
  • uplink (UL) resources are insufficient compared to downlink (DL) resources.
  • one of the purposes of the present disclosure is to provide a terminal, a base station, and a wireless communication method that improve resource utilization efficiency.
  • One aspect of the present disclosure is to set a first transmission power in a SBFD (Subband non-overlapping Full Duplex) operation according to a first transmission power setting, and set a second transmission power in a non-SBFD operation according to a second transmission power setting. and a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation.
  • Other aspects of the present disclosure set a first transmit power in SBFD (Subband non-overlapping Full Duplex) operation according to a first closed loop, and set a second transmit power in non-SBFD operation according to a second closed loop.
  • the present invention relates to a terminal having a control unit, and a transmitting unit that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation.
  • Another aspect of the present disclosure is to set the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation according to a first power calculation formula, and set the second transmission power in non-SBFD operation according to a second power calculation formula.
  • a control unit that sets power; and a transmitting unit that transmits an uplink channel with the first transmission power in the SBFD operation and transmits the uplink channel with the second transmission power in the non-SBFD operation.
  • FIG. 1 is a block diagram showing the functional configuration of a base station (gNB) according to an embodiment of the present disclosure.
  • FIG. 2 is a block diagram showing the functional configuration of a terminal (UE) according to an embodiment of the present disclosure.
  • 3A and 3B are diagrams illustrating an example of arrangement of radio resources of XDD (Cross Division Duplex) or SBFD (Subband non-overlapping Full Duplex) according to an embodiment of the present disclosure.
  • FIG. 4 is a diagram illustrating XDD or SBFD operation according to an embodiment of the present disclosure.
  • 5A and 5B are diagrams illustrating TDD and SBFD according to one embodiment of the present disclosure.
  • 6A-6E are diagrams illustrating pure time units and SBFD time units according to one embodiment of the present disclosure.
  • FIGS. 7A and 7B are diagrams illustrating cross-link interference (CLI) according to one embodiment of the present disclosure.
  • 8A and 8B are diagrams illustrating a PUSCH-Config information element (IE) according to one embodiment of the present disclosure.
  • 9A and 9B are diagrams illustrating the PUSCH-Config IE according to an embodiment of the present disclosure.
  • 10A and 10B are diagrams illustrating the PUSCH-PowerControl IE according to an embodiment of the present disclosure.
  • 11A and 11B are diagrams illustrating the PUCCH-PowerControl IE according to one embodiment of the present disclosure.
  • 12A and 12B are diagrams illustrating the RACH-ConfigGeneric IE according to one embodiment of the present disclosure.
  • FIG. 13A and 13B are diagrams illustrating the RACH-ConfigGenericTwoStepRA-r16 IE according to an embodiment of the present disclosure.
  • 14A and 14B are diagrams illustrating the PUSCH-ConfigCommon IE according to an embodiment of the present disclosure.
  • FIG. 15 is a diagram illustrating the PUSCH-PowerControl IE according to an embodiment of the present disclosure.
  • FIG. 16 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure.
  • FIG. 17 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure.
  • FIG. 18 is a diagram illustrating the SRI-PUSCH-PowerControl IE according to an embodiment of the present disclosure.
  • FIG. 19 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure.
  • FIG. 20 is a diagram illustrating closed-loop mapping according to an embodiment of the present disclosure.
  • FIG. 21 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure.
  • FIG. 22 is a diagram illustrating the SRI-PUSCH-PowerControl IE according to an embodiment of the present disclosure.
  • FIG. 23 is a diagram illustrating closed-loop mapping according to one embodiment of the present disclosure.
  • FIG. 24 is a diagram illustrating power adjustment according to one embodiment of the present disclosure.
  • FIG. 25 is a diagram illustrating power adjustment according to one embodiment of the present disclosure.
  • FIG. 26 is a diagram illustrating power adjustment according to one embodiment of the present disclosure.
  • FIG. 27 is a block diagram showing the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure.
  • FIG. 28 is a block diagram showing the hardware configuration of a vehicle according to an embodiment of the present disclosure.
  • Wireless communication system The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
  • communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof.
  • Wireless communication systems include Long Term Evolution (LTE), which is specified by the Third Generation Partnership Project (3GPP), and 5th generation mobile communication system Ne. w Radio (5G NR), realizing communication using these successor wireless communication systems, etc. It may be a system that
  • the wireless communication system may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), N Dual connectivity between R and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
  • RATs Radio Access Technologies
  • MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), N Dual connectivity between R and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • EN-DC E-UTRA-NR Dual Connectivity
  • NE-DC N Dual connectivity between R and LTE
  • the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)).
  • the NR base station (gNB) is the MN
  • the LTE (E-UTRA) base station (eNB) is the SN.
  • a wireless communication system has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) where both the MN and SN are NR base stations (gNB)). ) may be supported.
  • dual connectivity NR-NR Dual Connectivity (NN-DC) where both the MN and SN are NR base stations (gNB)
  • gNB NR base stations
  • the wireless communication system may include a base station forming a macro cell C1 with relatively wide coverage, and a base station forming a small cell C2 that is located within the macro cell C1 and narrower than the macro cell C1.
  • a terminal may be located within at least one cell. The arrangement, number, etc. of each cell and terminal are not limited to a specific aspect.
  • a terminal may connect to at least one of the plurality of base stations.
  • the terminal may use at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
  • Macro cell C1 may be included in FR1
  • small cell C2 may be included in FR2.
  • FR1 may be in a frequency band below 6 GHz (sub-6 GHz)
  • FR2 may be in a frequency band above 24 GHz (above-24 GHz).
  • the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
  • the terminal may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.
  • TDD time division duplex
  • FDD frequency division duplex
  • the plurality of base stations may be connected by wire (for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication).
  • wire for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication for example, when NR communication is used as a backhaul between two base stations, the base station that corresponds to the upper station is called the Integrated Access Backhaul (IAB) donor, and the base station that corresponds to the relay station is called the integrated access backhaul (IAB) donor. , may be called an IAB node.
  • IAB Integrated Access Backhaul
  • IAB integrated access backhaul
  • a base station may be connected to the core network via another base station or directly.
  • the core network may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the terminal may be a terminal compatible with at least one of communication systems such as LTE, LTE-A, 5G, and 6G.
  • an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used.
  • OFDM orthogonal frequency division multiplexing
  • CP-OFDM Cyclic Prefix OFDM
  • DFT-s-OFDM Discrete Fourier Transform Spread OFDM
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a wireless access method may also be called a waveform. Note that in the wireless communication system, other wireless access methods (for example, other single carrier transmission methods, other multicarrier transmission methods) may be used as the UL and DL wireless access methods.
  • downlink channels include a physical downlink shared channel (PDSCH) shared by each terminal, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical Downlink Control Channel (PDCCH)) etc. may be used.
  • PDSCH physical downlink shared channel
  • PBCH physical broadcast channel
  • PDCCH physical Downlink Control Channel
  • uplink channels include a physical uplink shared channel (PUSCH) shared by each terminal, a physical uplink control channel (PUCCH), and a random access channel ( Physical Random Access Channel (PRACH) or the like may be used.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • PRACH Physical Random Access Channel
  • User data, upper layer control information, System Information Block (SIB), etc. are transmitted via the PDSCH.
  • User data, upper layer control information, etc. may be transmitted via PUSCH.
  • a Master Information Block (MIB) may be transmitted via the PBCH.
  • Lower layer control information may be transmitted by PDCCH.
  • the lower layer control information may include, for example, downlink control information (DCI) that includes scheduling information for at least one of PDSCH and PUSCH.
  • DCI downlink control information
  • DCI that schedules PDSCH may be called DL assignment, DL DCI, etc.
  • DCI that schedules PUSCH may be called UL grant, UL DCI, etc.
  • PDSCH may be replaced with DL data
  • PUSCH may be replaced with UL data.
  • a control resource set (CONTROL REsource SET (CORESET)) and a search space (search space) may be used to detect the PDCCH.
  • CORESET corresponds to a resource for searching DCI.
  • the search space corresponds to a search area and a search method for PDCCH candidates.
  • One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.
  • One search space may correspond to PDCCH candidates that correspond to one or more aggregation levels.
  • One or more search spaces may be referred to as a search space (SS) set.
  • search space search space
  • search space set search space setting
  • search space set setting search space set setting
  • CORESET search space set setting
  • CORESET setting etc. in the present disclosure may be read interchangeably.
  • PUCCH provides channel state information (CSI), delivery confirmation information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK /NACK, etc.) and scheduling request (Scheduling Request).
  • CSI channel state information
  • delivery confirmation information for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK /NACK, etc.
  • Scheduling Request scheduling request
  • Uplink Control Information (UCI) including at least one of SR) may be transmitted.
  • a random access preamble for establishing a connection with a cell may be transmitted by PRACH.
  • a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted.
  • DL-RS includes a cell-specific reference signal (CRS) and a channel state information reference signal (CSI-RS).
  • demodulation reference signal (DeModulation Reference signal A positioning reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.
  • DMRS positioning reference signal
  • PRS positioning reference signal
  • PTRS phase tracking reference signal
  • the synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).
  • a signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS/PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.
  • a measurement reference signal Sounding Reference Signal (SRS)
  • a demodulation reference signal DMRS
  • UL-RS uplink reference signal
  • DMRS may be referred to as a UE-specific reference signal (UE-specific Reference Signal).
  • the gNB 100 and the UE 200 include functions that implement the embodiments described below. However, the gNB 100 and the UE 200 may each have only some of the functions in the embodiment.
  • FIG. 1 is a diagram showing an example of the functional configuration of the gNB 100.
  • the gNB 100 includes a receiving section 101, a transmitting section 102, and a control section 103.
  • the functional configuration shown in FIG. 1 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the receiving unit 101 includes a function of receiving various signals transmitted from the UE 200 and acquiring, for example, information on a higher layer from the received signals.
  • the transmitting unit 102 includes a function of generating a signal to be transmitted to the UE 200 and transmitting the signal by wire or wirelessly.
  • the control unit 103 stores preset setting information and various setting information to be transmitted to the UE 200 in a storage device, and reads them from the storage device as necessary. Further, the control unit 103 executes processing related to communication with the UE 200.
  • a functional unit related to signal transmission in the control unit 103 may be included in the transmitting unit 102, and a functional unit related to signal reception in the control unit 103 may be included in the receiving unit 101.
  • FIG. 2 is a diagram showing an example of the functional configuration of the UE 200.
  • the UE 200 includes a transmitter 201, a receiver 202, and a controller 203.
  • the functional configuration shown in FIG. 2 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.
  • the transmitter 201 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal.
  • the receiving unit 202 wirelessly receives various signals and obtains higher layer signals from the received physical layer signals. Further, the receiving unit 202 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signal, reference signal, etc. transmitted from the gNB 100.
  • the control unit 203 stores various setting information received from the gNB 100 by the receiving unit 202 in a storage device, and reads it from the storage device as necessary. Further, the control unit 203 executes processing related to communication with the gNB 100.
  • a functional unit related to signal transmission in the control unit 203 may be included in the transmitting unit 201, and a functional unit related to signal reception in the control unit 203 may be included in the receiving unit 202.
  • the division duplex method may be called XDD (Cross Division Duplex) or subband non-overlapping Full Duplex (SBFD).
  • XDD or SBFD may refer to a duplex method in which DL and UL are frequency division multiplexed within one component carrier (CC) of the TDD band (DL and UL can be used simultaneously).
  • CC component carrier
  • FIG. 3A shows Rel. 16 is a diagram illustrating an example of TDD settings defined up to No. 16.
  • FIG. 3A TDD slots or symbols are configured for the UE in the bandwidth of one component carrier (CC) (cell, may also be called serving cell), bandwidth portion (BWP), etc. .
  • CC component carrier
  • BWP bandwidth portion
  • the time ratio of DL slots and UL slots is 4:1.
  • FIG. 3B is a diagram showing an example of the configuration of the SBFD.
  • the resources used for DL reception and the resources used for UL transmission overlap in time. According to such a resource configuration, more UL resources can be secured, and resource utilization efficiency can be improved.
  • both ends of the frequency domain may be set as DL resources, and a UL resource may be sandwiched between these DL resources.
  • a guard area may be set at the boundary between the DL resource and the UL resource.
  • FIG. 4 is a diagram showing an example of SBFD operation.
  • part of the DL resources of the TDD band is set as the UL resource, and the DL and UL are configured to partially overlap in the time domain.
  • each of the plurality of UEs 200 receives a DL channel/signal.
  • one UE 200 receives the DL channel/signal
  • another UE 200 receives the DL channel/signal.
  • the base station 100 performs simultaneous transmission and reception of DL and UL.
  • each of the plurality of UEs 200 (UE#1 and UE#2 in FIG. 4) transmits a UL channel/signal.
  • DL frequency resources and UL frequency resources in the UE carrier are configured as DL BWP and UL BWP, respectively.
  • Multiple BWP configurations and BWP adaptation mechanisms are required to switch one DL/UL frequency resource to another DL/UL frequency resource.
  • the time resources (time units such as symbols and slots) in the TDD carrier for UE 200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration. Ru.
  • SBFD symbols may be advertised or configured as UL (or DL) on some frequency resources, or advertised or configured for UL transmission (or DL reception) while on other frequency resources, as shown in FIG. 5B.
  • On the frequency resource it may be notified or set as DL (or UL), or it may be a symbol notified or set for DL reception (or UL transmission).
  • the SBFD symbol may be a symbol that is notified or configured as UL (or DL) in a part of the frequency resource, or a symbol that is notified or configured for UL transmission (or DL reception).
  • the SBFD symbol may be notified or set as DL (or UL) in a part of the frequency resource, or may be a symbol notified or set for DL reception (or UL transmission).
  • the time unit may be a symbol level, a slot/subslot level, or a group of symbols/slots/subslots. That is, an SBFD time unit may be an SBFD symbol, a slot/subslot that includes or overlaps the SBFD symbol, or a group of symbols/slots/subslots that includes or overlaps the SBFD symbol.
  • a pure time unit is a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol), a slot/subslot that does not contain or overlap an SBFD symbol, or a symbol/slot/subslot that does not contain or overlap an SBFD symbol. It may be a group of subslots and may be referred to as a non-SBFD time unit.
  • a pure time unit may be referred to as a time unit consisting only of DL on a frequency resource, as shown in FIG. 6A, or as a time unit consisting of only DL on a frequency resource, as shown in FIG. 6B. It may also be referred to as a time unit consisting of.
  • DL resources and UL resources may have various arrangement patterns in the frequency domain.
  • the SBFD time units of frequency domain pattern #1 may have an arrangement pattern as shown in FIG. 6C.
  • the SBFD time units of frequency domain pattern #2 may have an arrangement pattern as shown in FIG. 6D.
  • the SBFD time units of frequency domain pattern #3 may have an arrangement pattern as shown in FIG. 6E.
  • the frequency domain pattern for the SBFD time unit may mean a resource repetition pattern in the frequency domain for the SBFD time unit.
  • Transmission opportunity i may be a PUSCH, PUCCH, SRS, or PRACH transmission opportunity.
  • Transmission opportunity i has a slot index n s, f ⁇ for subcarrier interval setting ⁇ in a frame having a system frame number (SFN), and the first symbol in the slot (the first symbol of transmission opportunity i). index) S and the number L of consecutive symbols.
  • SFN system frame number
  • the transmission power of the PUSCH is controlled based on the TPC command (also referred to as a value, increase/decrease value, correction value, etc.) indicated by the value of a predetermined field (also referred to as a TPC command field, first field, etc.) in the DCI.
  • TPC command also referred to as a value, increase/decrease value, correction value, etc.
  • a predetermined field also referred to as a TPC command field, first field, etc.
  • PUSCH transmission opportunity For example, if a UE transmits PUSCH on BWP b of carrier f in cell c with a parameter set (e.g., open loop parameter set) with index j, index l of power control adjustment state, then PUSCH transmission opportunity
  • the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d , l)) in i may be expressed by the following formula (1).
  • P CMAX,f,c (i) is, for example, the transmission power (for example, also referred to as maximum transmission power) of UE 200 set for carrier f of cell c in transmission opportunity i.
  • P O_PUSCH, b, f, c (j) is, for example, a parameter related to the target received power set for BWP b of carrier f of cell c in transmission opportunity i (e.g., a parameter related to transmit power offset, a transmit power offset (also referred to as PO, target received power parameter, etc.).
  • M PUSCH RB,b,f,c (i) is, for example, the number of resource blocks (bandwidth) allocated to PUSCH for transmission opportunity i in uplink BWP b of cell c and carrier f with subcarrier spacing ⁇ .
  • ⁇ b,f,c (j) are values provided by upper layer parameters (eg, also referred to as msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).
  • PL b, f, c (q d ) is, for example, a path loss (path loss compensation) calculated by the UE using an index q d of a reference signal for downlink BWP associated with uplink BWP b of carrier f of cell c. It is.
  • ⁇ TF,b,f,c (i) is a Transmission Power Adjustment Component (eg, also referred to as offset, transmission format compensation, etc.) for uplink BWP b of carrier f of cell c.
  • a Transmission Power Adjustment Component eg, also referred to as offset, transmission format compensation, etc.
  • f b,f,c (i,l) is a TPC command-based value (e.g., cumulative value of TPC commands, closed loop value).
  • the cumulative value of TPC commands may be expressed by a predetermined formula.
  • the TPC command may be determined based on the value of a predetermined field (also referred to as a TPC command field, first field, etc.) in the DCI used for PUSCH or PDSCH scheduling. These DCIs may be referred to as DCI formats 0_0, 0_1.
  • the power control information may be called a TPC command (also referred to as a value, increase/decrease value, correction value, etc.).
  • NR supports the DCI format (for example, DCI format 2_2) used for transmitting at least one TPC command of PUCCH and PUSCH.
  • UE 200 may control the transmission power of at least one of PUCCH and PUSCH based on the value indicated by the TPC command in the DCI format.
  • the DCI format used for transmitting TPC commands may have a configuration that is not used for PDSCH or PUSCH scheduling (does not include scheduling information).
  • TPC commands specified by DCI for example, at least one of DCI formats 0_0, 0_1, and 2_2) for each PUSCH or PUCCH transmission may be accumulated (tpc-Accumulation).
  • the UE 200 may be configured by the network (for example, the base station 100) as to whether or not to store TPC commands.
  • the base station 100 may notify the UE 200 of whether TPC commands are accumulated using upper layer signaling (eg, TPC-Accumulation).
  • the UE 200 may determine the transmission power in consideration of the TPC commands notified on a predetermined DCI (or PDCCH). Further, the TPC command may be included in one of the parameters of the power control adjustment state defined by a predetermined formula (for example, as part of the predetermined formula).
  • the transmission power of the PUCCH is controlled based on the TPC command (also referred to as a value, increase/decrease value, correction value, etc.) indicated by the value of a predetermined field (also referred to as a TPC command field, first field, etc.) in the DCI.
  • TPC command also referred to as a value, increase/decrease value, correction value, etc.
  • a predetermined field also referred to as a TPC command field, first field, etc.
  • PUCCH transmission power (P PUCCH, b, f, c (i, q u , q d , l)) may be expressed by equation (2).
  • the power control adjustment state may be set to have a plurality of states (for example, two states) or a single state by upper layer parameters. Further, when a plurality of power control adjustment states are set, one of the plurality of power control adjustment states may be identified by an index l (for example, l ⁇ 0,1 ⁇ ).
  • the power control adjustment state may be referred to as a PUCCH power control adjustment state, a first state, a second state, or the like.
  • the PUCCH transmission opportunity i is a predetermined period during which the PUCCH is transmitted, and may be composed of one or more symbols, one or more slots, etc., for example.
  • P CMAX,f,c (i) is, for example, the transmission power (also referred to as maximum transmission power) of the UE 200 set for carrier f of cell c in transmission opportunity i.
  • P O_PUCCH,b,f,c (q u ) is, for example, a parameter related to the target received power (for example, a parameter related to the transmit power offset, a parameter related to the transmit power (also referred to as offset P0 or target received power parameter).
  • M PUCCH RB,b,f,c (i) is, for example, the number of resource blocks (bandwidth) allocated to PUCCH for transmission opportunity i in uplink BWP b of cell c and carrier f with subcarrier spacing ⁇ .
  • PL b, f, c (q d ) is, for example, a path loss calculated by the UE 200 using the index q d of the reference signal for downlink BWP associated with uplink BWP b of carrier f of cell c.
  • ⁇ F_PUCCH (F) is an upper layer parameter given for each PUCCH format.
  • ⁇ TF,b,f,c (i) is the Transmission Power Adjustment Component (offset) for uplink BWP b of carrier f of cell c.
  • g b, f, c (i, l) is the TPC command-based value (e.g., cumulative value of TPC commands) of the uplink BWP power control adjustment state index l of carrier f of cell c and transmission opportunity i .
  • the cumulative value of TPC commands may be expressed by a predetermined formula.
  • transmission power is determined for uplink channels (for example, at least one of PUSCH and PUCCH) based on parameters notified from the network (for example, base station 100).
  • equations (1) and (2) are merely examples, and are not limited thereto.
  • the UE 200 only needs to control the transmission power of the PUSCH and PUCCH based on at least one parameter illustrated in equations (1) and (2), and may include additional parameters or some parameters. may be omitted.
  • the transmission power of PUSCH and PUCCH is controlled for each BWP of a certain carrier in a certain cell, but the invention is not limited to this. At least some of the cells, carriers, BWPs, and power control adjustment states may be omitted.
  • the transmission power of UE 200 is controlled using open loop transmission power control and/or closed loop transmission power control.
  • UE 200 corrects open-loop control errors using closed-loop control using TPC commands received from base station 100.
  • uplink shared channels e.g., PUSCH
  • uplink control channels e.g., PUCCH
  • sounding reference signals SRS
  • random access channels e.g., PRACH
  • NR specifies that a maximum of two closed loops are supported for each carrier in the serving cell.
  • the transmission power of the PUSCH in the transmission period i for the bandwidth part (BWP) b of the carrier f of the serving cell c may be expressed by the above equation (1).
  • the transmission period may be, for example, any time unit such as a symbol, slot, subframe, or frame.
  • f b, f, c (i, l) are values based on TPC commands (for example, cumulative values based on TPC commands).
  • the UE 200 may determine that two power control states are applied to the transmission power control of the PUSCH. Furthermore, when the RRC parameter "two PUCCH-PC-AdjustmentStates" is set for the PUCCH, the UE may determine that two power control states are applied to the transmission power control of the PUCCH.
  • Uplink signals can also determine transmit power using multiple power control adjustment states, similar to PUSCH and/or PUCCH, although the parameters utilized are different. .
  • closed loop and power control adjustment state may be read interchangeably.
  • TPC commands can be notified to multiple UEs at once.
  • DCI Downlink Control Information
  • DCI format 2_2 transmitted in the common search space is used to transmit a TPC command for at least one of PUCCH and PUSCH.
  • DCI format 2_2 may be called DCI for UE group common TPC command.
  • the TPC command notified by DCI format 2_2 may be called a group common TPC command.
  • the DCI format 2_2 may be cyclic redundancy check (CRC) scrambled by the PUSCH TPC identifier (TPC-PUSCH-RNTI (Radio Network Temporary Identifier)). PUCCH TPC identifier (TPC -PUCCH-RNTI).
  • CRC cyclic redundancy check
  • inter-gNB cross-link interference (CLI) and inter-UE CLI need to be considered.
  • the aggressor UE's uplink signal may cause interference to downlink reception at the victim UE, as shown in FIG. 7A. From the victim UE's perspective, it may be desirable to reduce the uplink transmit power of the aggressor UE to reduce interference to reception at the victim UE.
  • the downlink signal to the aggressor UE may cause interference to the uplink signal from the victim UE to the gNB.
  • the victim UE's gNB From the perspective of the victim UE's gNB, it may be desirable to increase the victim UE's uplink transmit power in order to improve the received signal power.
  • SBFD operation different UEs will perform uplink transmission and downlink reception in the same time unit, such as the same symbol/slot, which may result in inter-UE CLI and/or inter-gNB CLI.
  • the transmit power control of the UE is defined by specifications, may be configured semi-statically by RRC configuration, etc., and/or may be dynamically notified by DCI notification.
  • Proposals 1 to 3 below discuss the power control of uplink signals in SBFD symbols/slots through specifications that support both SBFD and non-SBFD operations, and RRC configuration and/or DCI notification. A separate power control application is proposed for SBFD operation.
  • transmission power control IEs such as PUSCH-PowerControl IE and PUCCH-PowerControl IE
  • separate transmission power control IEs for example, PUSCH-PowerControl IE
  • fields related to power control in PUSCH-PowerControl IE, PUCCH-PowerControl IE, etc. are set to separate transmission power control fields for SBFD operation and non-SBFD operation (for example, p0-NominalWithGrant and p0-NominalWithGrant).
  • SBFD subcarrier-PowerControl
  • non-SBFD operation for example, p0-NominalWithGrant and p0-NominalWithGrant.
  • tGrant -SBFD, p0-Set and p0-Set-SBFD may be set.
  • the maximum number to be configured is expanded to X, and at most two closed loops among the X can be configured for non-SBFD operation, and the others can be applied for SBFD operation.
  • the closed loop for SBFD operation is not explicitly set, and the closed loop for SBFD operation can be mapped in response to the setting for non-SBFD operation.
  • a single SRI/closed loop index can be commonly mapped for SBFD and SBFD operations.
  • a single closed-loop index can be commonly mapped for SBFD and SBFD operations.
  • a method for calculating transmission power in SBFD operation may be defined.
  • scaling factors for SBFD operation may be defined, configured, notified and/or applied.
  • a power offset for SBFD operation may be defined, configured, notified and/or applied.
  • a reference resource block (RB) size for SBFD operation may be defined, configured, notified and/or applied.
  • the UE transmits the uplink channel in SBFD operation with the transmit power set according to the PUSCH and/or PUCCH transmit power setting for SBFD operation, and according to the PUSCH and/or PUCCH transmit power setting for non-SBFD operation. Transmit the uplink channel in non-SBFD operation with the configured transmit power. That is, the PUSCH and/or PUCCH transmission power is semi-statically set via RRC configuration or the like according to the PUSCH and/or PUCCH transmission power setting for SBFD operation and the PUSCH and/or PUCCH transmission power setting for non-SBFD operation. .
  • separate PUSCH and/or PUCCH transmit power settings for SBFD and non-SBFD operations may be defined, configured, notified and/or applied.
  • SBFD operation and non-SBFD operation are settings (eg, p0-NominalWithoutGrant and p0-NominalWithoutGrant-SBFD, and/or p0-Set and p0-Set-SBFD, etc.) may be defined, configured, notified, and/or applied.
  • power control related parameters in RACH-ConfigGeneric e.g. preambleReceivedTargetPower
  • power control related parameters in RACH-ConfigGenericTwoStepRA e.g.
  • msgA-PreambleReceivedTargetPower er
  • power control related parameters in PUSCH-ConfigCommon for example, msg3 -DeltaPreamble, p0-NominalWithGrant
  • separate settings may be prescribed, configured, notified, and/or applied for SBFD and non-SBFD operations.
  • Option 1 provides separate PUSCH and/or PUCCH transmit power settings for SBFD and non-SBFD operations (e.g., PUSCH-PowerControl IE and PUSCH-PowerControl-SBFD IE, and/or PUCCH-PowerControl IE and PUCCH-Power Control - SBFD IE, etc.) may be defined, configured, notified and/or applied.
  • SBFD and non-SBFD operations e.g., PUSCH-PowerControl IE and PUSCH-PowerControl-SBFD IE, and/or PUCCH-PowerControl IE and PUCCH-Power Control - SBFD IE, etc.
  • PUSCH and/or PUCCH in SBFD operation means PUSCH and/or PUCCH that overlaps with SBFD time units such as SBFD symbols and SBFD slots.
  • PUSCH and/or PUCCH in non-SBFD operation means PUSCH and/or PUCCH that do not overlap with SBFD time units such as SBFD symbols and SBFD slots.
  • additional fields such as PUSCH-PowerControl-SBFD may be set in the PUSCH-Config IE.
  • PUSCH-PowerControl-SBFD may be additionally set as the PUSCH power control IE for SBFD operation. That is, "pusch-PowerControl-SBFD” as a PUSCH power control IE for SBFD operation and "pusch-PowerControl” as a PUSCH power control IE for non-SBFD operation may be set in the PUSCH-Config IE. .
  • the UE may transmit the PUSCH using the transmission power of the push-PowerControl-SBFD IE in SBFD operation, and may transmit the PUSCH using the transmission power of the push-PowerControl IE in non-SBFD operation.
  • This makes it possible to set different PUSCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.
  • PUCCH-PowerControl-SBFD may be set in PUCCH-Config.
  • PUCCH-Config IE in the existing NR, as shown in FIG. 9A, "pucch-PowerControl” is set as the PUCCH power control IE in PUCCH-Config.
  • PUCCH-Config IE in the existing NR, as shown in FIG. 9A, "pucch-PowerControl” is set as the PUCCH power control IE in PUCCH-Config.
  • PUCCH-PowerControl-SBFD may be additionally set as the PUCCH power control IE for SBFD operation. That is, "pucch-PowerControl-SBFD" as a PUCCH power control IE for SBFD operation and "pucch-PowerControl" as a PUCCH power control IE for non-SBFD operation may be set in the PUCCH-Config IE. .
  • the UE may transmit the PUCCH using the transmission power from the pucch-PowerControl-SBFD IE in SBFD operation, and may transmit the PUCCH using the transmission power from the pucch-PowerControl IE during non-SBFD operation.
  • This makes it possible to set different PUCCH transmission powers to the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.
  • option 1 it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, resulting in inter-UE CLI and/or inter-gNB CLI during SBFD operation. The possibility can be reduced.
  • additional fields such as "p0-NominalWithoutGrant-SBFD” and "p0-AlphaSets-SBFD” may be set in the PUSCH-PowerControl IE.
  • “p0-NominalWithoutGrant”, “p0-AlphaSets”, etc. are set as PUSCH power control fields in the PUSCH-PowerControl IE.
  • “p0-NominalWithoutGrant-SBFD” and “p0-AlphaSets-SBFD” may be additionally set as PUSCH power control fields for SBFD operation.
  • p0-NominalWithoutGrant-SBFD and “p0-AlphaSets-SBFD” as PUSCH power control fields for SBFD operation
  • p0-NominalWithoutGrant and “p0-AlphaS” as PUSCH power control fields for non-SBFD operation.
  • ets may be set in the PUSCH-PowerControl IE.
  • the UE transmits the PUSCH with the transmission power according to the PUSCH power control field such as "p0-NominalWithoutGrant-SBFD”, “p0-AlphaSets-SBFD” in SBFD operation, and "p0-NominalWithoutGrant”, "p0-AlphaSets-SBFD” in non-SBFD operation.
  • -AlphaSets PUSCH may be transmitted using the transmission power. This makes it possible to set different PUSCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.
  • additional fields such as "p0-Set-SBFD” may be set in the PUCCH-PowerControl IE.
  • "p0-Set” etc. are set as the PUCCH power control field in the PUCCH-PowerControl IE.
  • “p0-Set-SBFD” may be additionally set as a PUCCH power control field for SBFD operation. That is, "p0-Set-SBFD” as a PUCCH power control field for SBFD operation and "p0-Set” as a PUCCH power control field for non-SBFD operation may be set in the PUCCH-PowerControl IE. .
  • the UE transmits the PUCCH with the transmit power according to the PUCCH power control field such as "p0-Set-SBFD", and in non-SBFD operation, the UE transmits the PUCCH with the transmit power according to the PUCCH power control field such as "p0-Set”. may also be sent.
  • This makes it possible to set different PUCCH transmission powers to the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing UE-to-UE CLI and/or gNB-to-gNB CLI during SBFD operation. Can be done.
  • additional fields such as "preambleReceivedTargetPower-SBFD” may be set in the RACH-ConfigGeneric IE.
  • “preambleReceivedTargetPower” and the like are set as the RACH power control field in the RACH-ConfigGeneric IE.
  • “preambleReceivedTargetPower-SBFD” may be additionally set as the RACH power control field for SBFD operation.
  • preambleReceivedTargetPower-SBFD as a RACH power control field for SBFD operation
  • preambleReceivedTargetPower as a RACH power control field for non-SBFD operation
  • RACH-ConfigGeneric It may be set in IE.
  • the UE transmits the PRACH with the transmit power according to the PRACH power control field such as "preambleReceivedTargetPower-SBFD" in SBFD operation, and transmits PRACH with the transmit power according to the PRACH power control field such as "preambleReceivedTargetPower" in non-SBFD operation. to send H You can also do this.
  • additional fields such as "msgA-PreambleReceivedTargetPower-SBFD” may be set in the RACH-ConfigGenericTwoStepRA IE.
  • a PRACH power control field such as "msgA-PreambleReceivedTargetPower” is set in the RACH-ConfigGenericTwoStepRA IE.
  • “msgA-PreambleReceivedTargetPower-SBFD” may be additionally set as a PRACH power control field for SBFD operation.
  • msgA-PreambleReceivedTargetPower-SBFD as the RACH power control field for SBFD operation
  • msgA-PreambleReceivedTargetPower as the RACH power control field for non-SBFD operation
  • PRACH by transmit power by control field may also be sent.
  • additional fields such as "msg3-DeltaPreamble-SBFD” and "p0-NominalWithGrant-SBFD” may be set in the PUSCH-ConfigCommon IE.
  • “msg3-DeltaPreamble”, "p0-NominalWithGrant”, etc. are set as PUSCH power control fields in the PUSCH-ConfigCommon IE.
  • “msg3-DeltaPreamble-SBFD” and "p0-NominalWithGrant-SBFD” may be additionally set as the PUSCH power control field for SBFD operation.
  • the UE transmits the PUSCH with the transmission power according to the PUSCH power control field such as "msg3-DeltaPreamble-SBFD” and “p0-NominalWithGrant-SBFD” in SBFD operation, and "msg3-DeltaPreamble” and "p0 NominalWithGrant-SBFD” in non-SBFD operation.
  • PUSCH may be transmitted using the transmission power according to the PUSCH power control field such as "-NominalWithGrant”. This makes it possible to set different PUSCH transmission powers for the UE in SBFD operation and non-SBFD operation, reducing the possibility of causing inter-UE CLI and/or inter-gNB CLI during SBFD operation. Can be done.
  • the PUSCH and/or PUCCH power control field is not limited to the above-mentioned fields, and may include "p0-NominalWithGrant”, “p0-PUSCH-Alpha”, “p0-AlphaSets", “delta-MCS”, and “deltaF-PUCCH”.
  • -f0 “deltaF-PUCCH-f1”, “deltaF-PUCCH-f2”, “deltaF-PUCCH-f3”, “deltaF-PUCCH-f4”, etc. also for other PUSCH/PUCCH power control fields.
  • separate settings for SBFD and non-SBFD operations may be defined, configured, notified, and/or applied.
  • option 2 it becomes possible to configure different PUSCH and/or PUCCH transmission powers for the UE in SBFD operation and non-SBFD operation, resulting in inter-UE CLI and/or inter-gNB CLI during SBFD operation. The possibility can be reduced.
  • the UE may set the transmission power in SBFD operation according to the transmission power setting for SBFD, and may set the transmission power in non-SBFD operation according to the transmission power setting for non-SBFD.
  • the transmission power setting for SBFD and/or the transmission power setting for non-SBFD is defined by the specifications, semi-statically set by RRC settings, etc., or dynamically notified by DCI notification etc. It's okay.
  • the transmission power setting for SBFD and/or the transmission power setting for non-SBFD may be specified, set, notified, or applied explicitly or implicitly.
  • option 1 and option 2 may or may not be used together.
  • the UE may transmit the uplink channel with the transmission power according to the SBFD transmission power setting in SBFD operation, and may transmit the uplink channel with the transmission power according to the non-SBFD transmission power setting in non-SBFD operation.
  • the transmit power settings for SBFD and the transmit power settings for non-SBFD are separate transmit power settings information elements for SBFD and non-SBFD operations (e.g., PUSCH-PowerControl-SBFD IE and PUSCH -PowerControl IE, PUCCH-PowerControl-SBFD IE, PUCCH-PowerControl IE, etc.).
  • the UE determines the PUSCH and/or PUCCH transmission power according to the PUSCH-PowerControl-SBFD IE and/or the PUCCH-PowerControl-SBFD IE in the SBFD operation, and in the non-SBFD operation, the UE determines the PUSCH-PowerControl-SBFD IE and/or the PUCCH-PowerControl-SBFD IE.
  • the PUSCH and/or PUCCH transmission power may be determined according to the PUCCH-PowerControl IE.
  • the transmit power setting for SBFD and the transmit power setting for non-SBFD are the transmit power parameter for SBFD operation and the transmit power parameter for non-SBFD operation in the same transmit power setting information element.
  • p0-Nominal Without Grant in IE PUSCH transmission power may be determined according to p0-AlphaSets or the like.
  • the UE determines PUCCH transmission power according to p0-Set-SBFD, etc. in PUCCH-PowerControl IE, and in non-SBFD operation, determines PUCCH transmission power according to p0-Set, etc. in PUCCH-PowerControl IE. You may.
  • the uplink channel may also include one or more of an uplink shared channel, an uplink control channel, and a random access channel.
  • the UE may transmit the PUSCH, PUCCH and/or PRACH according to the PUSCH transmission power setting, the PUCCH transmission power setting and/or the PRACH transmission power setting.
  • the gNB may set the transmission power for SBFD operation to the UE according to the transmission power setting for SBFD, and may set the transmission power for non-SBFD operation to the UE according to the transmission power setting for non-SBFD.
  • the transmission power setting for SBFD and/or the transmission power setting for non-SBFD is either specified by the specifications, semi-statically set by RRC settings, or dynamically notified by MAC CE etc. It's okay.
  • the transmission power setting for SBFD and/or the transmission power setting for non-SBFD may be specified, set, notified, or applied explicitly or implicitly.
  • the gNB may receive an uplink channel transmitted from the UE with a transmission power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE with transmission power for non-SBFD in non-SBFD operation.
  • the transmit power settings for SBFD and the transmit power settings for non-SBFD are separate transmit power settings information elements for SBFD and non-SBFD operations (e.g., PUSCH-PowerControl-SBFD IE and PUSCH -PowerControl IE, PUCCH-PowerControl-SBFD IE, PUCCH-PowerControl IE, etc.).
  • the gNB sets the PUSCH and/or PUCCH transmission power for SBFD operation to the UE according to the PUSCH-PowerControl-SBFD IE and/or the PUCCH-PowerControl-SBFD IE, and UCCH-PowerControl IE Accordingly, the PUSCH and/or PUCCH transmission power for non-SBFD operation may be set in the UE.
  • the transmit power setting for SBFD and the transmit power setting for non-SBFD are the transmit power parameter for SBFD operation and the transmit power parameter for non-SBFD operation in the same transmit power setting information element.
  • the gNB sets the PUSCH transmission power in the SBFD operation to the UE using p0-NominalWithoutGrant-SBFD, p0-AlphaSets-SBFD, etc. in the PUSCH-PowerControl IE, and p0 in the PUSCH-PowerControl IE.
  • PUSCH transmission power in SBFD operation may be set in the UE.
  • the gNB sets the PUCCH transmission power in SBFD operation to the UE using p0-Set-SBFD etc. in the PUCCH-PowerControl IE, and sets the PUCCH transmission power in non-SBFD operation to the UE using p0-Set etc. in the PUCCH-PowerControl IE. You may.
  • the uplink channel may also include one or more of an uplink shared channel, an uplink control channel, and a random access channel.
  • the gNB may receive the PUSCH, PUCCH, and/or PRACH transmitted from the UE according to the PUSCH transmission power setting, the PUCCH transmission power setting, and/or the PRACH transmission power setting.
  • the UE may report the UE capability regarding whether to support separate PUSCH and/or PUCCH transmission power settings for SBFD operation and non-SBFD operation to the gNB.
  • the gNB may determine whether to perform separate PUSCH and/or PUCCH transmission power settings for SBFD operation and non-SBFD operation based on the acquired UE capability.
  • the UE transmits the uplink channel in SBFD operation with the transmission power adjusted by the PUSCH and/or PUCCH closed loop for SBFD operation, and the transmission adjusted by the PUSCH and/or PUCCH closed loop for non-SBFD operation. Transmit uplink channel in non-SBFD operation by power. That is, PUSCH and/or PUCCH transmit power is dynamically adjusted according to closed loop for SBFD operation and closed loop for non-SBFD operation via DCI notification or the like.
  • the setting of PUSCH and/or PUCCH closed loop in cell SBFD operation is considered as Problem 1.
  • the mapping relationship between uplink transmission beams eg, SRI and/or PUCCH spatial relation info, etc.
  • PUSCH and/or PUCCH closed loop index is considered as issue 2.
  • the mapping relationship between the PUSCH configuration of a configured grant eg, Configured Grant
  • the PUSCH closed loop index is considered as issue 3.
  • up to two PUSCH and/or PUCCH closed loops may be configured for a cell, one closed loop applied for SBFD operation and the other closed loop applied for non-SBFD operation. That is, in Alt-a, up to two PUSCH and/or PUCCH closed loops may be configured for a cell according to the restrictions of Release 15/16/17.
  • the UE may determine that twoPUSCH-PC-AdjustmentStates and/or twoPUCCH-PC-AdjustmentStates are PUSCH-PowerControl IE and/or PUCCH-PowerCo of a serving cell or BWP with SBFD operation. Assuming that it is always set in ntrol IE Good too.
  • which closed loop among up to two closed loops is set for SBFD operation and/or non-SBFD operation is determined by the specifications, or is set semi-statically by RRC settings, etc. It may be dynamically notified by DCI notification or the like, or it may be determined by the UE according to predetermined rules. Furthermore, which closed loop of up to two closed loops is configured for SBFD operation and/or non-SBFD operation may be explicitly or implicitly defined, configured, notified, or applied.
  • a total of up to X PUSCH and/or PUCCH closed loops may be configured, and up to 2 of the X PUSCH and/or PUCCH closed loops may be configured for non-SBFD operation.
  • the value of X may be greater than two.
  • the number of PUSCH and/or PUCCH closed loops for SBFD operation may be smaller than 2, may be equal to 2, or may be larger than 2.
  • the value of X may be explicitly or implicitly defined, set, notified, or applied.
  • which closed loops among up to It may be dynamically notified, such as by notification, or may be determined by the UE according to predetermined rules.
  • which closed loop among up to X closed loops is set for SBFD operation and/or non-SBFD operation may be explicitly or implicitly defined, set, notified, or applied.
  • the number of PUSCH closed loops for non-SBFD operation is set by the existing twoPUSCH-PC-AdjustmentStates field in the PUSCH-PowerControl IE
  • the number of PUSCH closed loops for SBFD operation is set by the PUSCH- May be set by the new SBFD-PUSCH-PC-AdjustmentStates field in the PowerControl IE.
  • PUSCH closed loop index #0, #1 may indicate a closed loop for non-SBFD operation
  • PUSCH closed loop index #2, #3 may indicate a closed loop for SBFD operation.
  • the number of PUCCH closed loops for non-SBFD operation is set by the existing two PUCCH-PC-AdjustmentStates field in the PUCCH-PowerControl IE
  • the number of PUCCH closed loops for SBFD operation is set by the existing two PUCCH-PC-AdjustmentStates field in the PUCCH-PowerControl IE.
  • New SBFD in It may be set by the PUCCH-PC-AdjustmentStates field.
  • PUCCH closed loop index #0, #1 may indicate a closed loop for non-SBFD operation
  • PUCCH closed loop index #2, #3 may indicate a closed loop for SBFD operation.
  • the number of PUSCH and/or PUCCH closed loops for SBFD operation is defined by the specifications, semi-statically set by RRC settings, etc., dynamically notified by DCI notification, etc., or determined by a predetermined number. It may be determined by the UE according to rules.
  • the number of PUSCH and/or PUCCH closed loops for SBFD operation may be greater than, equal to, or smaller than the number of PUSCH and/or PUCCH closed loops for non-SBFD operation.
  • the UE determines whether twoStates is SBFD-PUSCH-PC-AdjustmentStates and/or SBF Must be set in D-PUCCH-PC-AdjustmentStates.
  • OneState is set to SBFD-PUSCH-PC-AdjustmentStates and/or SBFD-PUCCH-PC-AdjustmentStates
  • the UE sets twoPUSCH-PC-AdjustmentStates and/or two PUCCH-PC-AdjustmentStates must be set. There is no need to assume that
  • the PUSCH and/or PUCCH closed loop for SBFD operation is not explicitly configured, but one-to-one mapping from the PUSCH and/or PUCCH closed loop configured for non-SBFD operation.
  • PUSCH and/or PUCCH closed loop for SBFD operation is not explicitly configured, but one-to-one mapping from the PUSCH and/or PUCCH closed loop configured for non-SBFD operation.
  • the UE adjusts the PUSCH and/or PUCCH transmit power by the PUSCH and/or PUCCH closed loop for non-SBFD operation, and in SBFD operation, the UE adjusts the PUSCH and/or PUCCH transmit power implicitly from the PUSCH and/or PUCCH closed loop for non-SBFD operation.
  • the PUSCH and/or PUCCH transmission power may be adjusted according to the PUSCH and/or PUCCH closed loop for SBFD operation configured as follows.
  • PUSCH closed-loop index #i0 for non-SBFD operation
  • PUSCH closed-loop index #i1 or #i2 is set for SBFD operation.
  • PUSCH closed-loop index #i0 for non-SBFD operation may be associated with PUSCH closed-loop index #i1 or #i2 for SBFD operation. Note that the wording "#i1 or #i2" is used because it is not certain whether the PUSCH closed loop for SBFD operation starts from i2 or i1.
  • PUSCH closed-loop index #i0 and #i1 are set for non-SBFD operation
  • PUSCH closed-loop index #i2 or #i3 is set for SBFD operation.
  • PUSCH closed loop index #i0 for non-SBFD operation is associated with PUSCH closed loop index #i1 for SBFD operation
  • the PUSCH closed-loop index #i1 for operation may be associated with the PUSCH closed-loop index #i3 for SBFD operation.
  • PUCCH closed loop index #i0 for non-SBFD operation may be associated with PUCCH closed loop index #i1 or #i2 for SBFD operation. Note that the wording "#i1 or #i2" is used because it is not certain whether the PUCCH closed loop for SBFD operation starts from i2 or i1.
  • PUCCH closed-loop index #i0 and #i1 are set for non-SBFD operation
  • PUCCH closed-loop index #i2 or #i3 is set for SBFD operation.
  • Implicitly means that the PUCCH closed-loop index #i0 for non-SBFD operation is associated with the PUCCH closed-loop index #i1 for SBFD operation, and the PUCCH closed-loop index #i1 for non-SBFD operation may be associated with PUCCH closed loop index #i3 for SBFD operation.
  • the one-to-one mapping may be defined by specifications, semi-statically configured by RRC configuration, etc., dynamically notified by DCI notification, etc., or determined by the UE according to predetermined rules. . Additionally, one-to-one mapping may be explicitly or implicitly defined, configured, notified, or applied. In addition, multiple different one-to-one mappings are defined, and which one-to-one mapping is applied is either defined by the specifications, semi-statically set by RRC settings, or dynamically notified by DCI notifications, etc. or may be determined by the UE according to predetermined rules. Further, which one-to-one mapping is applied may be explicitly or implicitly defined, set, notified, or applied.
  • the existing closed-loop configuration can be applied to provide a closed-loop for SBFD operation and a closed-loop for non-SBFD operation, and PUSCH and/or PUCCH transmission by the UE via DCI. It becomes possible to dynamically control power.
  • mapping between uplink transmit beam indexes such as SRI and/or PUCCH spatial relation info and PUSCH and/or PUCCH closed loop indexes may be considered.
  • one SRI and/or uplink transmit beam index such as PUCCH spatial relation info is mapped to one PUSCH and/or PUCCH closed loop index for either non-SBFD operation or SBFD operation. It's okay.
  • each candidate value of the sri-PUSCH-ClosedLoopIndex field in the SRI-PUSCH-PowerControl IE may be a PUSCH closed-loop index for either non-SBFD operation or SBFD operation.
  • each candidate value of the pucch-ClosedLoopIndex-r17 field in the PUCCH-PowerControlSetInfo-r17 IE may be a PUCCH closed-loop index for either non-SBFD operation or SBFD operation.
  • each candidate value of the sri-PUSCH-ClosedLoopIndex field and/or the pucch-ClosedLoopIndex-r17 field is still the same as that of ⁇ i0, i1 ⁇ . You can leave it as is.
  • SRI #m may be mapped to PUSCH closed loop #i0 for non-SBFD operation
  • SRI #n may be mapped to PUSCH closed loop #i1 for SBFD operation.
  • each candidate value of the sri-PUSCH-ClosedLoopIndex field and/or pucch-ClosedLoopIndex-r17 field is set to ⁇ i0, i1, i2, i3 ⁇ . It can be.
  • each candidate value of the sri-PUSCH-ClosedLoopIndex field can be ⁇ i0, i1, i2, i3 ⁇ , as shown in FIG.
  • SRI #m may be mapped to PUSCH closed loop #i0 for non-SBFD operation
  • SRI #n may be mapped to PUSCH closed loop #i3 for SBFD operation.
  • Alt-b is applied to problem 1 mentioned above, the following several cases can be considered.
  • the candidate value of sri-PUSCH-ClosedLoopIndex is ⁇ i0, i1 ⁇ or ⁇ i0, i2 ⁇ . Note that it is not known whether the PUSCH closed loop for SBFD operation starts from i2 or i1.
  • the candidate value of sri-PUSCH-ClosedLoopIndex is ⁇ i0, i1, i2 ⁇ or ⁇ i0, i2, i3 ⁇ . Note that it is not known whether the PUSCH closed loop for SBFD operation starts from i2 or i1.
  • the candidate value of sri-PUSCH-ClosedLoopIndex is ⁇ i0, i1, i2 ⁇ . sell.
  • the candidate value of sri-PUSCH-ClosedLoopIndex is ⁇ i0, i1, i2, i3 ⁇ . sell.
  • each candidate value of pucch-ClosedLoopIndex-r17 can be ⁇ i0, i1, i2, i3 ⁇ . In this case as well, the following several cases may be considered.
  • the candidate value of pucch-ClosedLoopIndex-r17 is ⁇ i0, i1 ⁇ or ⁇ i0, i2 ⁇ . Note that it is not known whether the PUCCH closed loop for SBFD operation starts from i2 or i1.
  • the candidate value of pucch-ClosedLoopIndex-r17 is ⁇ i0, i1, i2 ⁇ or ⁇ i0, i2, i3 ⁇ . Note that it is not known whether the PUCCH closed loop for SBFD operation starts from i2 or i1.
  • the candidate value of pucch-ClosedLoopIndex-r17 is ⁇ i0, i1, i2 ⁇ . sell.
  • the candidate value of pucch-ClosedLoopIndex-r17 is ⁇ i0, i1, i2, i3 ⁇ . sell.
  • ⁇ Modification #1 If the SRI is mapped to the PUSCH closed loop index for non-SBFD operation, the UE may not assume that the SRI is signaled for PUSCH on the SBFD.
  • the UE may not assume that the SRI is signaled for PUSCH on non-SBFD.
  • ⁇ Modification #3 The UE does not have to assume DCI formats that schedule PUSCH on non-SBFD and other DCI formats that schedule PUSCH on SBFD due to the SRI field reporting the same TPC loop index.
  • ⁇ Modification #4 The UE does not have to assume DCI formats for scheduling PUSCH on non-SBFD and other DCI formats for scheduling PUSCH on non-SBFD due to the SRI field reporting different TPC loop indexes.
  • ⁇ Modification #5 The UE does not have to assume the DCI format for scheduling PUSCH on SBFD and other DCI formats for scheduling PUSCH on SBFD due to the SRI field reporting different TPC loop indexes.
  • the UE assumes a DCI format that notifies the PUCCH resource on a non-SBFD and another DCI format that notifies the PUCCH resource on a non-SBFD. You don't have to.
  • Modifications #3 to #8 may be applicable to cases where any PUSCH and/or PUCCH closed loop is for SBFD operation or non-SBFD operation, or is transparent or non-transparent.
  • an example mapping between uplink transmit beam index, such as SRI and/or PUCCH spatial relation info, and PUSCH and/or PUCCH closed loop index may be provided.
  • the uplink transmit beam index such as one SRI and/or PUCCH spatial relation info is one PUSCH and/or PUCCH closed loop index for non-SBFD operation and one PUSCH and/or PUCCH closed loop index for SBFD operation.
  • PUCCH closed loop index For example, as shown in FIG. 20, SRI #m is mapped to PUSCH closed loop #i0 for non-SBFD operation and PUSCH closed loop #i3 for SBFD operation, and SRI #n is mapped to PUSCH closed loop #i1 for non-SBFD operation. and PUSCH closed loop #i2 for SBFD operation.
  • a case can be assumed in which SRI is notified in DCI format 0_1/0_2 for scheduling PUSCH, or a case in which PUCCH resources are notified or determined for PUCCH according to specific PUCCH spatial relation info.
  • the PUSCH and/or PUCCH is on the SBFD
  • the associated PUSCH and/or PUCCH closed-loop index for SBFD operation may be applied to the PUSCH and/or PUCCH power calculation.
  • the PUSCH and/or PUCCH is on a non-SBFD
  • the associated PUSCH and/or PUCCH closed-loop index for non-SBFD operation may be applied to the PUSCH and/or PUCCH power calculation.
  • Opt-a and Opt-b may be executed for DCI format 0_1/0_2 in which the TPC adjustment command field exists.
  • the notified adjustment may be applied only to the PUSCH closed-loop index for the SBFD operation associated with the notified SRI.
  • the notified adjustment may be applied only to the PUSCH closed-loop index for non-SBFD operations associated with the notified SRI.
  • the advertised adjustment is the PUSCH closed-loop index for SBFD operations associated with the advertised SRI and PUSCH closed loop index for operation.
  • Opt-a and Opt-b may be executed for DCI format 1_1/1_2 in which the TPC adjustment command field exists.
  • Opt-a when the notified PUCCH is on SBFD, the notified adjustment is applied only to the PUCCH closed loop index for SBFD operation related to the PUCCH spatial relation info of the notified PUCCH resource. Good too.
  • the notified PUCCH is on a non-SBFD, the notified adjustment may be applied only to the PUCCH closed loop index for non-SBFD operations associated with the PUCCH spatial relation info of the notified PUCCH resource. good.
  • the notified adjustment is made on the PUCCH for SBFD operation related to the PUCCH spatial relation info of the notified PUCCH resource. It may be applied to the closed loop index and the PUCCH closed loop index for non-SBFD operations.
  • the TPC adjustment command field exists in DCI #1 and DCI #2.
  • the adjustment notified by DCI #1 may be applied only to PUSCH closed loop #i3, and the adjustment notified by DCI #2 may be applied only to PUSCH closed loop #i1.
  • the adjustment notified by DCI #1 is applied only to PUSCH closed loop #i0, #i3, and the adjustment notified by DCI #2 is applied only to PUSCH closed loop #i1, #i3. good.
  • sri-PUSCH-ClosedLoopIndex-SBFD and/or pucch-ClosedLoopIndex-r17-SBFD are added to the PUSCH and/or PUC for the corresponding SBFD operation for the SRI and/or PUCCH spatial relation info.
  • sri-PUSCH-ClosedLoopIndex is used to notify the PUSCH closed-loop index for non-SBFD operation
  • sri-PUSCH-ClosedLoopIndex is used to notify the PUSCH closed-loop index for SBFD operation.
  • sri-PUSCH-ClosedLoopIndex-SBFD may be set.
  • One SRI can be mapped to a PUSCH closed-loop index for SBFD operations and a PUSCH closed-loop index for non-SBFD operations.
  • the UE determines whether the SRI and/or PUCCH spatial relation info is PUSC on SBFD. Notified to H and/or PUCCH You don't have to assume that.
  • sri-PUSCH-ClosedLoopIndex is set as i0
  • SRI uses PUSCH closed loop index #i0 for non-SBFD operation and It may implicitly mean that it is mapped to PUSCH closed loop index #i1 or #i2. Note that it is not known whether the PUSCH closed loop index for SBFD operation starts from i2 or i1.
  • SRI is the PUSCH closed loop index #i0 or #i1 for non-SBFD operation; It may implicitly mean that it is mapped to PUSCH closed loop index #i2 or #i3 for SBFD operation.
  • SRI#m is associated with PUSCH closed-loop index #i0 for non-SBFD operation and PUSCH closed-loop index #i2 for SBFD operation
  • SRI#n is associated with PUSCH closed-loop index #i2 for non-SBFD operation.
  • PUCCH resource is the PUCCH closed-loop index #i0 for non-SBFD operation; It may implicitly mean that it is mapped to PUCCH closed loop index #i1 or #i2 for SBFD operation. Note that it is not known whether the PUCCH closed loop index for SBFD operation starts from i2 or i1.
  • pucch-ClosedLoopIndex-r17 is set as i0 or i1
  • the PUCCH resource is configured as PUCCH closed loop index #i0 or #i1 for non-SBFD operation.
  • the CG PUSCH configuration may be configured with one PUSCH closed-loop index for either SBFD operation or non-SBFD operation.
  • each candidate value of the powerControlLoopToUse field in the ConfiguredGrantConfig IE may be PUSCH closed loop for SBFD operation or PUSCH closed loop for non-SBFD operation.
  • the explanation in Alt-2 of problem 2 can be reused by replacing sri-PUSCH-ClosedLoopIndex with powerControlLoopToUse.
  • each candidate value of the powerControlLoopToUse field in the ConfiguredGrantConfig IE may be a PUSCH closed loop index for either non-SBFD operation or SBFD operation.
  • each candidate value of the powerControlLoopToUse field may remain ⁇ i0, i1 ⁇ .
  • each candidate value of the powerControlLoopToUse field can be ⁇ i0, i1, i2, i3 ⁇ .
  • the CG PUSCH configuration may be configured with one PUSCH closed-loop index for SBFD operation and one PUSCH closed-loop index for non-SBFD operation.
  • a new parameter powerControlLoopToUse-SBFD field may be utilized to signal the corresponding PUSCH closed loop index for SBFD operation on CG PUSCH.
  • the ConfiguredGrantConfig IE even if powerControlLoopToUse for notifying the PUSCH closed-loop index for non-SBFD operation and powerControlLoopToUse-SBFD for notifying the PUSCH closed-loop index for SBFD operation are set, Good.
  • One CG PUSCH can be mapped to a PUSCH closed-loop index for SBFD operation and a PUSCH closed-loop index for non-SBFD operation.
  • the UE may set the transmit power in SBFD operation according to the closed loop for SBFD, and may set the transmit power in non-SBFD operation according to the closed loop for non-SBFD.
  • the closed loop for SBFD and/or the closed loop for non-SBFD may be defined by specifications, semi-statically configured by RRC settings, or dynamically notified by DCI notification or the like. Further, the closed loop for SBFD and/or the closed loop for non-SBFD may be specified, configured, notified, or applied explicitly or implicitly.
  • the UE may transmit an uplink channel with closed-loop transmission power for SBFD in SBFD operation, and may transmit an uplink channel with closed-loop transmission power for non-SBFD in non-SBFD operation.
  • the total number of closed loops is configured, and the UE configures the transmit power in SBFD operation according to the closed loop for SBFD among the configured total number of closed loops.
  • the transmit power in non-SBFD operation may be set according to the closed loop for non-SBFD.
  • the UE may set the transmit power in SBFD operation and set the transmit power in non-SBFD operation according to the mapping between the uplink transmit beam and the closed-loop index. Also, related to issue 3, the UE configures the transmit power in SBFD operation and configures the transmit power in non-SBFD operation according to the mapping between the uplink shared channel configuration and the closed loop index in the configured grant. It's okay.
  • the gNB may set the transmission power in the SBFD operation to the UE using the closed loop for SBFD, and may set the transmission power in the non-SBFD operation to the UE using the closed loop for non-SBFD.
  • the closed loop for SBFD and/or the closed loop for non-SBFD may be defined by specifications, semi-statically configured by RRC settings, or dynamically notified by DCI notification or the like.
  • the closed loop for SBFD and/or the closed loop for non-SBFD may be specified, configured, notified, or applied explicitly or implicitly.
  • the gNB may receive an uplink channel transmitted from the UE with a transmission power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE with transmission power for non-SBFD in non-SBFD operation.
  • the total number of closed loops is set, and the gNB sets the transmission power in the SBFD operation according to the closed loop for SBFD among the set total number of closed loops.
  • the transmit power in non-SBFD operation may be set according to the closed loop for non-SBFD.
  • the gNB may set the transmit power in SBFD operation and set the transmit power in non-SBFD operation according to the mapping between the uplink transmit beam and the closed-loop index. Also, related to issue 3, the gNB configures the transmit power in SBFD operation and configures the transmit power in non-SBFD operation according to the mapping between the uplink shared channel configuration and the closed loop index in the configured grant. It's okay.
  • the UE may report the UE capability regarding whether to support separate PUSCH and/or PUCCH closed loops for SBFD and non-SBFD operations to the gNB.
  • the gNB may determine whether to perform separate PUSCH and/or PUCCH closed-loop control for SBFD operation and non-SBFD operation based on the acquired UE capability.
  • the UE may also report the UE capability to the gNB regarding whether one SRI is simultaneously mapped to the PUSCH closed loop for SBFD operation and non-SBFD operation.
  • the UE may report to the gNB the UE capability regarding whether one PUCCH spatial relationship info is mapped to the PUCCH closed loop of SBFD operation and non-SBFD operation at the same time.
  • proposal 3 the UE transmits the uplink channel in SBFD operation with the transmit power set according to the transmit power formula for SBFD operation, and the UE transmits the uplink channel in SBFD operation with the transmit power set according to the transmit power formula for non-SBFD operation.
  • the uplink channel in operation may be transmitted.
  • a scaling factor for PUSCH and/or PUCCH transmit power calculation for SBFD operation may be applied.
  • the PUSCH and/or PUCCH transmission power for non-SBFD operation by existing NR may be increased by multiplication with a scaling factor.
  • the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d , l)) may be expressed by the following formula (3).
  • equation (3) the scaling factor ⁇ for calculating PUSCH transmission power for SBFD operation is multiplied by the second argument of the min function in equation (1) for calculating PUSCH transmission power described above.
  • the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d , l)) may be expressed by the following formula (4).
  • the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d , l)) may be expressed by the following formula (5).
  • equation (5) the output of the min function of the above-mentioned PUSCH transmission power calculation equation (1) is multiplied by the scaling factor ⁇ for calculating the PUSCH transmission power for SBFD operation, and the product and P CMAX,f , c (i) is set.
  • the scaling factor ⁇ is defined by the specifications, semi-statically set by RRC settings, etc., dynamically notified by DCI notifications, or specified by a specific rule (for example, PUSCH on SBFD). RB size and/or PUSCH repetition number, etc.). Further, the scaling factor ⁇ may be explicitly or implicitly defined, set, notified, or applied.
  • a power offset for PUSCH and/or PUCCH transmit power calculation for SBFD operation may be applied.
  • the PUSCH and/or PUCCH transmission power for non-SBFD operation by existing NR may be increased by addition with a power offset.
  • the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d , l)) may be expressed by the following equation (6).
  • the power offset ⁇ for calculating the PUSCH transmission power for SBFD operation is added to the second argument of the min function of the above-mentioned PUSCH transmission power calculation formula (1).
  • the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d , l)) may be expressed by the following formula (7).
  • equation (7) the power offset ⁇ for calculating the PUSCH transmission power for SBFD operation is added to the output of the min function of the above-mentioned PUSCH transmission power calculation equation (1). Note that when the power offset ⁇ is larger than 0, equation (7) may not be applicable.
  • the transmission power of PUSCH (P PUSCH, b, f, c (i, j, q d , l)) may be expressed by the following formula (8).
  • the power offset ⁇ for calculating the PUSCH transmission power for SBFD operation is added to the output of the min function of the above-mentioned PUSCH transmission power calculation equation (1), and the sum and P CMAX,f , c (i) is set.
  • the power offset ⁇ is defined by the specification, semi-statically set by RRC settings, etc., dynamically notified by DCI notification etc., or specified by a specific rule (for example, PUSCH on SBFD). RB size and/or PUSCH repetition number, etc.). Further, the power offset ⁇ may be explicitly or implicitly defined, set, notified, or applied.
  • a reference RB size for PUSCH and/or PUCCH transmit power calculation for SBFD operation may be used.
  • a reference RB size corresponding to the uplink frequency band portion in SBFD may be used for PUSCH transmission power calculation for SBFD operation.
  • the actual RB size of PUSCH on SBFD is not applied as the parameters M RB, b, f, c PUSCH in calculation formula (1) of PUSCH transmission power, and option 3-1 or 3-2 is may be applied.
  • the parameters M RB, b, f, c PUSCH are independent of the actual RB size of PUSCH on SBFD, such as the RB size of other PUSCH repeats on non-SBFD, if present. It's okay.
  • the parameters M RB, b, f, c PUSCH are defined by the specifications, semi-statically set by RRC settings, etc., dynamically notified by DCI notifications, or determined by specific rules (e.g. PUSCH RB size and/or PUSCH repetition number on SBFD).
  • the parameters M RB, b, f, c PUSCH may be explicitly or implicitly defined, configured, notified, or applied.
  • the parameters M RB, b, f, c PUSCH are fixed RB size offset based on the actual PUSCH RB size, scaling factor based on the actual PUSCH RB size, offset based on the actual PUSCH RB size The value may depend on the actual RB size of PUSCH on the SBFD.
  • a fixed RB size offset may be specified by the specification, set semi-statically such as by RRC configuration, dynamically notified such as by DCI notification, or specified by a specific rule (e.g. PUSCH on SBFD). RB size and/or PUSCH repetition number, etc.). Additionally, the fixed RB size offset may be explicitly or implicitly defined, configured, notified, or applied.
  • the gNB may directly notify or set the RB size offset value.
  • “fixed The mapping relationship to "RB size offset” is defined by the specification, semi-statically set by RRC settings, dynamically notified by DCI notifications, or determined by specific rules (for example, on SBFD). may be determined by the UE according to the PUSCH RB size and/or the number of PUSCH repetitions, etc.).
  • the scaling factor based on the actual PUSCH RB size may be specified by the specification, semi-statically set by RRC settings, etc., dynamically notified by DCI notification, etc., or determined by specific rules (e.g. , PUSCH on SBFD, RB size and/or PUSCH repetition number, etc.).
  • the fixed RB size offset may be explicitly or implicitly defined, configured, notified, or applied.
  • scaling factor can be calculated from “actual PUSCH RB size”, “ratio of actual PUSCH RB size to BWP size (or UL subband size on SBFD symbol/slot)”, and/or “PUSCH repetition number”. The mapping relationship to and/or the number of PUSCH repetitions, etc.).
  • the parameters in options 1 to 3 may also be cell-specific or common to multiple UEs in a cell.
  • one common parameter for improving uplink power in SBFD operation may be applied.
  • two common parameters may be applied, one parameter to improve uplink power in SBFD operation and one parameter to reduce uplink power in SBFD operation.
  • proposal 3 may be applied with common PUSCH and/or PUCCH closed loop constraints for SBFD and non-SBFD operations.
  • suggestions 2 and 3 may be applied together.
  • the UE may set the transmission power in SBFD operation according to the power calculation formula for SBFD, and may set the transmission power in non-SBFD operation according to the power calculation formula for non-SBFD.
  • the power calculation formula for SBFD may be defined by specifications, semi-statically set by RRC settings, or dynamically notified by DCI notification or the like. Further, the power calculation formula for SBFD may be specified, set, notified, or applied explicitly or implicitly.
  • the UE may transmit an uplink channel with SBFD transmission power in SBFD operation, and may transmit an uplink channel with non-SBFD transmission power in non-SBFD operation.
  • the power calculation formula for SBFD may be derived by multiplying the power calculation formula for non-SBFD by a scaling factor.
  • the power calculation formula for SBFD may be derived by adding an offset value to the power calculation formula for non-SBFD.
  • the power calculation formula for SBFD may be calculated by applying the reference resource block size instead of the actual resource block size to the power calculation formula for non-SBFD.
  • the gNB may set the transmission power in the SBFD operation to the UE using the power calculation formula for SBFD, and may set the transmission power in the non-SBFD operation to the UE using the power calculation formula for non-SBFD.
  • the power calculation formula for SBFD may be defined by specifications, semi-statically set by RRC settings, or dynamically notified by DCI notification or the like. Further, the power calculation formula for SBFD may be specified, set, notified, or applied explicitly or implicitly.
  • the gNB may receive an uplink channel transmitted from the UE with a transmission power for SBFD in SBFD operation, and may receive an uplink channel transmitted from the UE with transmission power for non-SBFD in non-SBFD operation.
  • the power calculation formula for SBFD may be derived by multiplying the power calculation formula for non-SBFD by a scaling factor.
  • the power calculation formula for SBFD may be derived by adding an offset value to the power calculation formula for non-SBFD.
  • the power calculation formula for SBFD may be calculated by applying the reference resource block size instead of the actual resource block size to the power calculation formula for non-SBFD.
  • the UE may report the UE capability regarding whether to support the PUSCH and/or PUCCH power calculation formula adjusted for SBFD to the gNB.
  • each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices.
  • the functional block may be realized by combining software with the one device or the plurality of devices.
  • Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't.
  • a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.
  • a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 27 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment of the present disclosure.
  • the base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc. .
  • the word “apparatus” can be read as a circuit, a device, a unit, etc.
  • the hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in FIG. 27, or may be configured not to include some of the devices.
  • Each function in the base station 10 and user terminal 20 is performed by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and controls communication by the communication device 1004. This is realized by controlling at least one of data reading and writing in the memory 1002 and the storage 1003.
  • the processor 1001 operates an operating system to control the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like.
  • CPU central processing unit
  • the baseband signal processing section 104, call processing section 105, etc. described above may be implemented by the processor 1001.
  • the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes in accordance with these.
  • programs program codes
  • software modules software modules
  • data etc.
  • the program a program that causes a computer to execute at least part of the operations described in the above embodiments is used.
  • the control unit 401 of the user terminal 20 may be realized by a control program stored in the memory 1002 and operated on the processor 1001, and other functional blocks may be similarly realized.
  • Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.
  • the memory 1002 is a computer-readable recording medium, and includes at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be done.
  • Memory 1002 may be called a register, cache, main memory, or the like.
  • the memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.
  • the storage 1003 is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, or a magneto-optical disk (for example, a compact disk, a digital versatile disk, or a Blu-ray disk). (registered trademark disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, etc.
  • Storage 1003 may also be called an auxiliary storage device.
  • the storage medium mentioned above may be, for example, a database including at least one of memory 1002 and storage 1003, a server, or other suitable medium.
  • the communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example.
  • the communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.
  • FDD frequency division duplex
  • TDD time division duplex
  • the transmitter/receiver 103 may be implemented as a transmitter 103a and a receiver 103b that are physically or logically separated.
  • the input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
  • each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses for each device.
  • the base station 10 and the user terminal 20 also include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). It may be configured to include hardware, and a part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the notification of information may include physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented using broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
  • Each aspect/embodiment described in this disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is an integer or decimal number, for example)), FRA (Future Radio Access), NR (new Radio), New radio access ( NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802 Systems that utilize .16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, and that are extended, modified, created, and defined based on these.
  • the present invention may be
  • the specific operations performed by the base station in this disclosure may be performed by its upper node.
  • various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (e.g., MME or It is clear that this could be done by at least one of the following: (conceivable, but not limited to) S-GW, etc.).
  • MME mobile phone
  • S-GW network node
  • Information can be output from the upper layer (or lower layer) to the lower layer (or upper layer). It may be input/output via multiple network nodes.
  • the input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to another device.
  • Judgment may be made using a value expressed by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (for example, a predetermined value). (comparison with a value).
  • notification of prescribed information is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.
  • Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.
  • software, instructions, information, etc. may be sent and received via a transmission medium.
  • a transmission medium For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.
  • wired technology coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.
  • wireless technology infrared, microwave, etc.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of
  • At least one of the channel and the symbol may be a signal.
  • the signal may be a message.
  • a component carrier may also be called a carrier frequency, a cell, a frequency carrier, or the like.
  • system and “network” are used interchangeably.
  • radio resources may be indicated by an index.
  • Base Station BS
  • wireless base station fixed station
  • NodeB NodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • a base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.
  • a base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services may also be provided by a remote radio head).
  • RRHs small indoor base stations
  • Communication services may also be provided by a remote radio head).
  • the term "cell” or “sector” refers to a portion or the entire coverage area of a base station and/or base station subsystem that provides communication services in this coverage. refers to
  • the base station transmitting information to the terminal may be read as the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station is defined by a person skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc.
  • the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like.
  • the moving body refers to a movable object, and the moving speed is arbitrary. Naturally, this also includes cases where the moving object is stopped.
  • the mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships and other watercraft.
  • the mobile object may be a mobile object that autonomously travels based on a travel command. It may be a vehicle (e.g. car, airplane, etc.), an unmanned moving object (e.g. drone, self-driving car, etc.), or a robot (manned or unmanned). good.
  • the base station and the mobile station includes devices that do not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be replaced by a user terminal.
  • communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.).
  • D2D Device-to-Device
  • V2X Vehicle-to-Everything
  • each aspect/embodiment of the present disclosure may be applied.
  • the user terminal 20 may have the functions that the base station 10 described above has.
  • words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
  • uplink channels, downlink channels, etc. may be replaced with side channels.
  • the user terminal in the present disclosure may be replaced with a base station.
  • the base station 10 may have the functions that the user terminal 20 described above has.
  • FIG. 28 shows an example of the configuration of the vehicle 1.
  • the vehicle 1 includes a drive unit 2, a steering unit 3, an accelerator pedal 4, a brake pedal 5, a shift lever 6, left and right front wheels 7, left and right rear wheels 8, an axle 9, an electronic control unit 10, various It includes sensors 21 to 29, an information service section 12, and a communication module 13.
  • the drive unit 2 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.
  • the steering unit 3 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
  • a steering wheel also referred to as a steering wheel
  • the electronic control unit 10 is composed of a microprocessor 31, memory (ROM, RAM) 32, and communication port (IO port) 33. Signals from various sensors 21 to 27 provided in the vehicle are input to the electronic control unit 10.
  • the electronic control unit 10 may also be called an ECU (Electronic Control Unit).
  • the signals from the various sensors 21 to 28 include a current signal from the current sensor 21 that senses the motor current, a front wheel and rear wheel rotation speed signal obtained by the rotation speed sensor 22, and a front wheel rotation speed signal obtained by the air pressure sensor 23. and a rear wheel air pressure signal, a vehicle speed signal obtained by the vehicle speed sensor 24, an acceleration signal obtained by the acceleration sensor 25, an accelerator pedal depression amount signal obtained by the accelerator pedal sensor 29, and a signal obtained by the brake pedal sensor 26.
  • These include a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 27, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 28.
  • the information service unit 12 controls various devices such as a car navigation system, audio system, speakers, television, and radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and these devices. It is composed of one or more ECUs.
  • the information service unit 12 provides various multimedia information and multimedia services to the occupants of the vehicle 1 using information acquired from an external device via the communication module 13 or the like.
  • the information service unit 12 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device (for example, (display, speaker, LED lamp, touch panel, etc.).
  • an input device for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • an output device for example, (display, speaker, LED lamp, touch panel, etc.).
  • the driving support system unit 30 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden.
  • the system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 30 transmits and receives various information via the communication module 13, and realizes a driving support function or an automatic driving function.
  • the communication module 13 can communicate with the microprocessor 31 and the components of the vehicle 1 via the communication port.
  • the communication module 13 communicates via the communication port 33 with the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, left and right rear wheels 8, which are included in the vehicle 1.
  • Data is transmitted and received between the axle 9, the microprocessor 31 and memory (ROM, RAM) 32 in the electronic control unit 10, and the sensors 21-28.
  • the communication module 13 is a communication device that can be controlled by the microprocessor 31 of the electronic control unit 10 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication.
  • the communication module 13 may be located either inside or outside the electronic control unit 10.
  • the external device may be, for example, a base station, a mobile station, or the like.
  • the communication module 13 receives signals from the various sensors 21 to 28 described above that are input to the electronic control unit 10, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 12. At least one of the information based on the information may be transmitted to an external device via wireless communication.
  • the electronic control unit 10, various sensors 21-28, information service unit 12, etc. may be called an input unit that receives input.
  • the PUSCH transmitted by the communication module 13 may include information based on the above input.
  • the communication module 13 receives various information (traffic information, signal information, inter-vehicle distance information, etc.) transmitted from external devices, and displays it on the information service section 12 provided in the vehicle.
  • the information service unit 12 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 13). may be called.
  • the communication module 13 also stores various information received from external devices into a memory 32 that can be used by the microprocessor 31. Based on the information stored in the memory 32, the microprocessor 31 controls the drive unit 2, steering unit 3, accelerator pedal 4, brake pedal 5, shift lever 6, left and right front wheels 7, and left and right rear wheels provided in the vehicle 1. 8, the axle 9, sensors 21 to 28, etc. may be controlled.
  • the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first transmission power setting, and the first transmission power is set according to the second transmission power setting.
  • a control unit configured to set a second transmission power in a non-SBFD operation, transmitting an uplink channel with the first transmission power in the SBFD operation, and transmitting an uplink channel with the second transmission power in the non-SBFD operation;
  • a terminal having a transmitting unit for transmitting data is provided.
  • the first transmit power setting and the second transmit power setting may be defined by separate transmit power setting information elements for the SBFD operation and the non-SBFD operation. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of
  • the first transmit power setting and the second transmit power setting are a first transmit power parameter for the SBFD operation and a first transmit power parameter for the non-SBFD operation in the same transmit power setting information element. and a second transmission power parameter.
  • the uplink channel may include one or more of an uplink shared channel, an uplink control channel, and a random access channel. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of
  • the first transmission power setting sets the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation to the terminal, and the second transmission power setting sets the terminal to perform non-SBFD operation.
  • a control unit configured to set a second transmission power to a terminal in the SBFD operation; and a receiving unit for receiving an uplink channel transmitted from the terminal.
  • the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first transmission power setting
  • the first transmission power in non-SBFD operation is set according to the second transmission power setting. transmitting an uplink channel with the first transmit power in the SBFD operation and transmitting an uplink channel with the second transmit power in the non-SBFD operation;
  • a wireless communication method performed by a terminal is provided.
  • the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first closed loop
  • the second transmission power in non-SBFD operation is set according to the second closed loop.
  • a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits an uplink channel with the second transmission power in the non-SBFD operation. is provided.
  • a total number of closed loops is set, and the control unit sets a first transmission power in the SBFD operation according to the first closed loop of the set total number of closed loops, and The second transmission power in the non-SBFD operation may be set according to the second closed loop among the total number of closed loops.
  • the controller sets the first transmit power in the SBFD operation and the second transmit power in the non-SBFD operation according to a mapping between an uplink transmit beam and a closed-loop index. Good too. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of
  • the controller configures a first transmission power in the SBFD operation according to a mapping between an uplink shared channel configuration and a closed-loop index of a configured grant, and configures a first transmission power in the SBFD operation and a second transmission power in the non-SBFD operation. You may also set the power.
  • the first closed loop sets the first transmission power in the SBFD (Subband non-overlapping Full Duplex) operation to the terminal
  • the second closed loop sets the second transmission power in the non-SBFD operation.
  • a control unit that sets a transmission power to a terminal; and a controller that receives an uplink channel transmitted from the terminal with the first transmission power in the SBFD operation, and receives an uplink channel transmitted from the terminal with the second transmission power in the non-SBFD operation.
  • a base station is provided having a receiving unit for receiving a transmitted uplink channel.
  • the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first closed loop
  • the second transmission power in non-SBFD operation is set according to the second closed loop. and transmitting an uplink channel with the first transmit power in the SBFD operation and transmitting an uplink channel with the second transmit power in the non-SBFD operation.
  • a wireless communication method is provided.
  • the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first power calculation formula
  • the first transmission power in non-SBFD operation is set according to the second power calculation formula.
  • a control unit that sets a transmission power of 2; and a transmitter that transmits an uplink channel with the first transmission power in the SBFD operation and transmits the uplink channel with the second transmission power in the non-SBFD operation.
  • the first power calculation formula may be derived by multiplying the second power calculation formula by a scaling factor. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of
  • the first power calculation formula may be derived by adding an offset value to the second power calculation formula. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of
  • the first power calculation formula may be calculated by applying a reference resource block size to the second power calculation formula. According to the present embodiment, it becomes possible to set different PUSCH and/or PUCCH transmission powers to the UE in each of SBFD operation and non-SBFD operation, which causes inter-UE CLI and/or inter-gNB CLI during SBFD operation. It is possible to reduce the possibility of
  • the first power calculation formula sets the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation to the terminal
  • the second power calculation formula sets the first transmission power in the non-SBFD operation.
  • a control unit configured to set a second transmission power to a terminal in the SBFD operation; and a receiving unit for receiving an uplink channel transmitted from the terminal.
  • the first transmission power in SBFD (Subband non-overlapping Full Duplex) operation is set according to the first power calculation formula
  • the first transmission power in non-SBFD operation is set according to the second power calculation formula. transmitting an uplink channel with the first transmit power in the SBFD operation and transmitting an uplink channel with the second transmit power in the non-SBFD operation;
  • a wireless communication method performed by a terminal is provided.
  • determining may encompass a wide variety of operations.
  • “Judgment” and “decision” include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a “judgment” or “decision.”
  • judgment and “decision” refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access.
  • (accessing) may include considering something as a “judgment” or “decision.”
  • judgment and “decision” refer to resolving, selecting, choosing, establishing, comparing, etc. may be included.
  • judgment and “decision” may include regarding some action as having been “judged” or “determined.”
  • judgment (decision) may be read as “assuming", “expecting”, “considering”, etc.
  • connection refers to any connection or coupling, direct or indirect, between two or more elements and to each other. It may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled.”
  • the bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection” may be replaced with "access.”
  • two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.
  • the reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applied standard.
  • RS Reference Signal
  • the phrase “based on” does not mean “based solely on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to elements using the designations "first,” “second,” etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.
  • a radio frame may be composed of one or more frames in the time domain. Each frame or frames in the time domain may be called a subframe. A subframe may also be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
  • the numerology may be a communication parameter applied to the transmission and/or reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception. It may also indicate at least one of a specific filtering process performed by the device in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • SCS subcarrier spacing
  • TTI transmission time interval
  • the numerology may also indicate at least one of a specific filtering process performed by the device in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • a slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain.
  • a slot may be a unit of time based on numerology.
  • a slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot.
  • PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A.
  • PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.
  • Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol.
  • one subframe may be called a transmission time interval (TTI)
  • TTI transmission time interval
  • multiple consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI. It's okay.
  • at least one of the subframe and 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. It may be.
  • the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
  • TTI refers to, for example, the minimum time unit for scheduling in wireless communication.
  • a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis.
  • radio resources frequency bandwidth, transmission power, etc. that can be used by each user terminal
  • the TTI may be a transmission time unit of a channel-coded data packet (transport block), code block, codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.
  • one slot or one minislot is called a TTI
  • one or more TTIs may be the minimum time unit for scheduling.
  • the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.
  • a TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
  • TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • long TTI for example, normal TTI, subframe, etc.
  • short TTI for example, short TTI, etc. It may also be read as a TTI having the above TTI length.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of the numerology, and may be 12, for example.
  • the number of subcarriers included in an RB may be determined based on numerology.
  • the time domain of an RB may include one or more symbols, and may be one slot, one minislot, one subframe, or one TTI in length.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs include physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. May be called.
  • PRBs physical resource blocks
  • SCGs sub-carrier groups
  • REGs resource element groups
  • PRB pairs RB pairs, etc. May be called.
  • a resource block may be configured by one or more resource elements (REs).
  • REs resource elements
  • 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
  • Bandwidth Part (also referred to as partial bandwidth) refers to a subset of consecutive common resource blocks (RB) for a certain numerology in a certain carrier. good.
  • the common RB may be specified by an RB index based on a common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within that BWP.
  • the BWP may include a UL BWP (UL BWP) and a DL BWP (DL BWP).
  • UL BWP UL BWP
  • DL BWP DL BWP
  • One or more BWPs may be configured within one carrier for a UE.
  • At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP.
  • “cell”, “carrier”, etc. in the present disclosure may be replaced with "BWP”.
  • radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples.
  • the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB The number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.
  • the "maximum transmit power” described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power ( It may also mean the rated UE maximum transmit power).
  • a and B are different may mean “A and B are different from each other.” Note that the term may also mean that "A and B are each different from C”. Terms such as “separate” and “coupled” may also be interpreted similarly to “different.”
  • Wireless communication system 100 Base station (gNB) 200 Terminal (UE)
  • gNB Base station
  • UE Terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon un aspect, la présente invention concerne un terminal comprenant : une unité de commande qui règle une première puissance d'émission pour une opération de transmission bidirectionnelle simultanée sans chevauchement de sous-bandes (SBFD) conformément à un premier réglage de puissance d'émission, et règle une seconde puissance d'émission pour une opération non SBFD conformément à un second réglage de puissance d'émission ; et une unité d'émission qui effectue une émission par un canal de liaison montante avec la première puissance d'émission dans l'opération SBFD, et effectue une émission par le canal de liaison montante avec la seconde puissance d'émission dans l'opération non SBFD.
PCT/JP2022/029015 2022-07-27 2022-07-27 Terminal, station de base et procédé de communication sans fil WO2024023994A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/029015 WO2024023994A1 (fr) 2022-07-27 2022-07-27 Terminal, station de base et procédé de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/029015 WO2024023994A1 (fr) 2022-07-27 2022-07-27 Terminal, station de base et procédé de communication sans fil

Publications (1)

Publication Number Publication Date
WO2024023994A1 true WO2024023994A1 (fr) 2024-02-01

Family

ID=89705673

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/029015 WO2024023994A1 (fr) 2022-07-27 2022-07-27 Terminal, station de base et procédé de communication sans fil

Country Status (1)

Country Link
WO (1) WO2024023994A1 (fr)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
MODERATOR (CATT): "Summary #2 of [109-e-R18-Duplex-03] Email discussion on subband non-overlapping full duplex", 3GPP TSG RAN WG1 #109-E R1-2205520, 20 May 2022 (2022-05-20), XP052192146 *
SAMSUNG: "Subband non-overlapping full duplex for NR duplex evolution", 3GPP TSG RAN WG1 #109-E R1-2203904, 29 April 2022 (2022-04-29), XP052153242 *
VIVO: "Potential enhancements on dynamic/flexible TDD", 3GPP TSG RAN WG1 #109-E R1-2203559, 29 April 2022 (2022-04-29), XP052153034 *

Similar Documents

Publication Publication Date Title
WO2024023994A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024023987A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024023984A1 (fr) Terminal, station de base et procédé de communication sans fil
CN118251950A (zh) 终端、无线通信方法以及基站
WO2023209918A1 (fr) Station de base et procédé de communication sans fil
WO2023209919A1 (fr) Station de base et procédé de communication sans fil
WO2023209915A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024095486A1 (fr) Terminal et procédé de communication
WO2023209917A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209911A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209910A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024095487A1 (fr) Terminal et procédé de communication
WO2023209913A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024100746A1 (fr) Terminal, station de base et procédé de communication
WO2024034096A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034097A1 (fr) Terminal, station de base, et procédé de communication sans fil
WO2024034107A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034099A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209916A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024084839A1 (fr) Terminal et procédé de communication
WO2023209920A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024084829A1 (fr) Terminal et procédé de communication
WO2024181544A1 (fr) Terminal et procédé de communication
WO2024034108A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024034100A1 (fr) Terminal, station de base, et procédé de communication sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22953088

Country of ref document: EP

Kind code of ref document: A1