Terminal and wireless communication method

Abstract

This terminal transmits, within a specified time based on time division duplexing, an upstream data channel conforming to a sub-band full-duplex communication method in which uplink sub-bands and downlink sub-bands are allocated non-overlappingly in a frequency direction. The terminal transmits the uplink data channel in a time domain to which the sub-band full-duplex communication method is applied, and executes an open-loop transmission power control on the uplink data channel without feedback from a reception side for each uplink data channel when an individual transmission power control for the uplink data channel is applied.

Description

Terminal and wireless communication method

[0001] The present invention relates to a terminal and a wireless communication method that supports SBFD.

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, 3GPP Release 19 is studying an extension of the duplex method (Non-Patent Document 1). Specifically, regarding Sub-Band non-overlapping Full Duplex (SBFD), which is a duplex method that enables simultaneous use of a downlink (DL) and an uplink (UL) within a carrier of a time division duplex (TDD) band, it has been agreed to study a method of indicating to a terminal (User Equipment, UE) the positions (time positions) of the UL sub-band and the DL sub-band (which may also be called SBFD sub-band) in the time direction (e.g., symbols).

[0004] In addition, two options have been agreed upon: UL and DL PRBs (Physical Resource Blocks) that can be used as SBFD subbands, specifically, UL usable PRBs, are determined based on the position where the active bandwidth portion (active UL BWP) in the SBFD symbol intersects with the UL subband, and DL usable PRBs are determined based on the active bandwidth portion (active DL BWP) in the SBFD symbol and the DL subband; and UL usable PRBs and DL usable PRBs are explicitly set in the active UL BWP and active DL BWP (Non-Patent Document 2).

[0005] Furthermore, it has been agreed to apply individual transmit power control (TPC) to UL physical channels using SBFD symbols and non-SBFD symbols, specifically, to the Physical Uplink Shared Channel (PUSCH) and the Physical Uplink Control Channel (PUCCH) (Non-Patent Document 3). Similar transmit power control may also be applied to the Sounding Reference Signal (SRS).

[0006] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 2023 “Final Report of 3GPP TSG RAN WG1 #116 v1.0.0”, 3GPP, April 2024 “Draft Report of 3GPP TSG RAN WG1 #117 v0.2.0”, 3GPP, May 2024

[0007] However, if individual transmit power control for UL physical channels can be applied using SBFD symbols and non-SBFD symbols determined by the above-mentioned options, a problem arises in that the UE cannot determine appropriate transmit power control for the UL physical channels, in particular for the PUSCH (uplink data channel), which is also used for scheduling grants and may be transmitted more frequently compared to the PUCCH.

[0008] Therefore, the following disclosure has been made in consideration of this situation, and aims to provide a terminal and a wireless communication method that can perform appropriate transmission power control of an uplink data channel even when individual transmission power control for an UL physical channel can be applied, while using SBFD symbols and non-SBFD symbols.

[0009] One aspect of the present disclosure is a terminal (UE200) that includes a transmitter (radio signal transmitter / receiver 210) that transmits an uplink data channel according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time period based on time division duplexing, and a control unit (controller 270) that transmits the uplink data channel in a time domain in which the subband full-duplex communication method is applied, and that, when individual transmission power control is applied to the uplink data channel, performs open-loop transmission power control on the uplink data channel without feedback from a receiving side for each of the uplink data channels.

[0010] One aspect of the present disclosure is a terminal including: a transmitter that transmits an uplink data channel according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time period based on time division duplex; and a controller that transmits the uplink data channel in a time domain in which the subband full-duplex communication method is applied, and that, when individual transmission power control is applied to the uplink data channel, performs closed-loop transmission power control on the uplink data channel based on feedback from a receiving side for each of the uplink data channels.

[0011] One aspect of the present disclosure is a terminal including: a transmitter that transmits an uplink data channel according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlappingly in the frequency direction within a specified time period based on time division duplex; and a controller that transmits the uplink data channel in a time domain in which the subband full-duplex communication method is applied, and that, when individual transmit power control is applied to the uplink data channel, performs open-loop transmit power control for each uplink data channel without feedback from a receiving side, and closed-loop transmit power control for each uplink data channel that assumes feedback from a receiving side.

[0012] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram showing example configurations of radio frames, subframes, and slots used in the wireless communication system 10. FIG. 3 is a diagram showing example configurations of TDD and XDD / SBFD. FIG. 4 is a functional block diagram of a gNB 100 and a UE 200. FIG. 5 is a diagram showing example configurations of UL subbands and DL subbands using SBFD. FIG. 6 is a diagram showing a formula for calculating the transmit power of a PUSCH. FIG. 7 is a diagram showing an example sequence related to UL power control of a PUSCH. FIG. 8 is a diagram showing example configurations of PUSCH-PowerControl and the like according to Operation Example 1-1. FIG. 9 is a diagram showing example configurations of PUSCH-PowerControl and the like according to Operation Example 1-2. FIG. 10 is a diagram showing an example configuration of ConfiguredGrantConfig according to Operation Example 1-3. FIG. 11 is a diagram showing example configurations of SRI-PUSCH-PowerControl and ConfiguredGrantConfig according to Operation Example 2. FIG. 12 is a diagram showing an example configuration of PUSCH-Config according to Operation Example 3-1. Fig. 13 is a diagram illustrating an example of the configuration of PUSCH-Power Control according to Operation Example 3-2. Fig. 14 is a diagram illustrating an example of the hardware configuration of the gNB 100 and the UE 200. Fig. 15 is a diagram illustrating an example of the configuration of a vehicle 2001.

[0013] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0014] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE 200, User Equipment, UE). Note that the wireless communication system 10 may also be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.

[0015] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1 .

[0016] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0017] The gNB 100 is a 5G-compliant radio base station that performs 5G-compliant radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional antenna beam (hereinafter referred to as beam BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and two NG-RAN nodes.

[0018] The type of DC may be Multi-RAT Dual Connectivity (MR-DC), which uses multiple radio access technologies, or NR-NR Dual Connectivity (NR-DC), which uses only NR. MR-DC may also be E-UTRA-NR Dual Connectivity (EN-DC), in which the eNB constitutes the master node (MN) and the gNB constitutes the secondary node (SN), or NR-E-UTRA Dual Connectivity (NE-DC), which is the reverse.

[0019] The gNB 100 can transmit multiple beams BM with different transmission directions (which may also be simply referred to as directions, or radiation directions, or coverages) in a space- and time-division manner. Note that the gNB 100 may transmit multiple beams BM simultaneously.

[0020] The wireless communication system 10 may also support multiple frequency ranges (FR). Specifically, the wireless communication system 10 may support the following frequency ranges:

[0021] ・FR1: 410 MHz to 7.125 GHz ・FR2-1: 24.25 GHz to 52.6 GHz FR1 may use a sub-carrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2-1 is a higher frequency than FR1 and may use a sub-carrier spacing (SCS) of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0022] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0023] Furthermore, the wireless communication system 10 also supports a frequency band higher than the FR2-1 frequency band. Specifically, the wireless communication system 10 supports a frequency band exceeding 52.6 GHz up to 71 GHz. Such a high frequency band may be referred to as FR2-2.

[0024] When using bands above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied.

[0025] Additionally, as mentioned above, in high frequency bands such as FR2-2, increased inter-carrier phase noise becomes an issue, which may necessitate the application of a larger (wider) SCS or a single-carrier waveform.

[0026] The larger the SCS, the shorter the symbol / cyclic prefix (CP) period and slot period (assuming a 14 symbol / slot configuration is maintained). Figure 2 shows an example of the configuration of radio frames, subframes, and slots used in the wireless communication system 10.

[0027] If the 14-symbol / slot configuration is maintained, the larger (wider) the SCS, the shorter the symbol period (and slot period). The time direction may be referred to as the time domain, symbol period, symbol length, or symbol time. The frequency direction may be referred to as the frequency domain, resource block, subcarrier, or BWP (Bandwidth part).

[0028] The frequency resources may include component carriers, subcarriers, resource blocks (RBs), resource block groups (RBGs), bandwidth parts (BWPs), etc. The time resources may include symbols, slots, minislots, subframes, radio frames, discontinuous reception (DRX) periods, etc.

[0029] The number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Also, the number of slots per subframe may differ depending on the SCS.

[0030] The wireless communication system 10 may use an SSB (SS / PBCH Block) that is configured from a synchronization signal (SS) and a downlink physical broadcast channel (PBCH).

[0031] SSBs are transmitted periodically from the network mainly to allow UE 200 to detect cell IDs and reception timings when starting communication. In NR, SSBs are also used to measure the reception quality of each cell. The SSB transmission periodicity may be specified as 5, 10, 20, 40, 80, 160 milliseconds, etc. Note that the initial access UE 200 may assume a transmission period of 20 milliseconds.

[0032] Furthermore, multiple duplexing methods may be used in the wireless communication system 10. Specifically, time division duplexing (TDD) and frequency division duplexing (FDD) may be used. The duplexing method may be interpreted as a method for realizing simultaneous transmission and reception (duplex communication) of downlink (DL) and uplink (UL).

[0033] Furthermore, the wireless communication system 10 may use another duplexing method that enables simultaneous use of DL and UL, specifically, XDD (Cross Division Duplex) / SBFD (Sub-Band non-overlapping Full Duplex).

[0034] Figure 3 shows an example of the configuration of TDD and XDD / SBFD. As shown in Figure 3, in TDD defined in 3GPP Releases 15 to 17, DL, UL, or F (flexible: can be set to DL or UL) can be set for each symbol and instructed to UE 200.

[0035] On the other hand, in XDD / SBFD, gNB100 can configure specific frequency resources (e.g., subbands) as DL and other frequency resources as UL at a specified time T, such as a symbol, and instruct UE200 accordingly.

[0036] XDD / SBFD allows simultaneous use of DL and UL within a carrier (CC) in the TDD band. Using the central portion of the frequency resources within the DL and UL carriers can avoid or mitigate potential cross-link interference (CLI) with adjacent carriers. XDD / SBFD may also be referred to as a type of full duplex, or FDD full duplex, or as sub-band (DL / UL) full duplex, as abbreviated as SBFD.

[0037] In SBFD, frequency resources for DL ​​(DL band) and frequency resources for UL (UL band) are allocated in a non-overlapping manner to the same duplex band on the same time period.

[0038] Specifically, XDD / SBFD is a scheme in which DL bands and UL bands are allocated non-overlappingly in the frequency direction within a specified time T based on time division duplex. The DL band may be interpreted as a DL subband, and the UL band may be interpreted as a UL subband. In the following, XDD / SBFD will be abbreviated simply as SBFD where appropriate.

[0039] (2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the UE 200 will be described. Fig. 4 is a functional block configuration diagram of the gNB 100 and the UE 200.

[0040] As shown in FIG. 4 , the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0041] It should be noted that Fig. 4 shows only the main functional blocks relevant to the description of the embodiment, and that the UE 200 (gNB 100) has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 shows the functional block configuration of the UE 200, and for the hardware configuration, please refer to Fig. 14.

[0042] The radio signal transmitting and receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting and receiving unit 210 can support Massive MIMO, which generates a more directional beam by controlling radio (RF) signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between a UE and two NG-RAN nodes.

[0043] Furthermore, the radio signal transceiver 210 can transmit and receive radio signals in accordance with SBFD, i.e., subband full-duplex (SBFD) in which uplink subbands (UL subbands) and downlink subbands (DL subbands) are allocated non-overlappingly in the frequency direction within a specified time based on time division duplex (TDD). Of course, the radio signal transceiver 210 may also support duplexing methods such as TDD and FDD (frequency division duplex).

[0044] In particular, in this embodiment, the radio signal transceiver 210 may transmit an uplink signal (specifically, an uplink data channel) according to SBFD, in which UL subbands or DL ​​subbands are allocated non-overlappingly in the frequency direction within a specified time (e.g., symbol) based on TDD. In this embodiment, the radio signal transceiver 210 may constitute a transmitter.

[0045] The uplink data channel here may refer to a data channel of the physical layer in the uplink (UL) direction. Specifically, it may refer to a PUSCH (Physical Uplink Shared Channel). However, it is not necessarily limited to this channel as long as it is a physical data channel in the uplink direction.

[0046] The radio signal transceiver 210 may transmit the above-mentioned uplink signal through a single transmission / reception point (TRP). Specifically, the radio signal transceiver 210 may transmit the PUSCH, the PUCCH, and the SRS through the single TRP. A TRP (Transmission Reception Point) may simply be interpreted as a transmitting antenna. A single TRP may mean that the uplink signal is transmitted from a transmission point in one geographical location.

[0047] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0048] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0049] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0050] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0051] The control signal and reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0052] DMRS is a reference signal (pilot signal) known between the base station and the terminal for estimating the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0053] In addition to the DMRS and PTRS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0054] In addition, in this embodiment, a reference signal for path loss measurement (which may be referred to as a path loss reference signal (PLRS)) may be included. The PLRS may refer to a reference signal (RS) used for path loss estimation of the PUSCH, the PUCCH, and the SRS. For example, the CSI-RS, the SSB, etc. may be used as the PLRS.

[0055] The channels include a control channel and a data channel. The control channel may include a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), a random access channel (RACH, downlink control information (DCI) including a random access radio network temporary identifier (RA-RNTI)), a physical broadcast channel (PBCH), etc.

[0056] Furthermore, the data channel includes a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH), etc. Data may refer to data transmitted via a data channel.

[0057] The control signal and reference signal processor 240 may transmit capability information (UE capability information) of the UE 200 to the network. In particular, in this embodiment, the control signal and reference signal processor 240 can transmit capability information related to SBFD. The capability information may include, for example, UE capability information related to transmit power control (TPC) when SBFD is applied.

[0058] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB 100 or another gNB).

[0059] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0060] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as the Medium Access Control layer (MAC), the Radio Link Control layer (RLC), and the Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0061] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 can execute control related to SBFD. Specifically, the control unit 270 can execute transmit power control (TPC) of an uplink signal when SBFD is applied.

[0062] Specifically, the control unit 270 can perform uplink power control (UL power control) for the PUSCH, the PUCCH, and the SRS. The UL power control may be applied separately to the SBFD symbols and the non-SBFD symbols, or may be applied separately to the PUSCH, the PUCCH, and the SRS. Such UL power control may be called separate UL power control.

[0063] The control unit 270 may control the transmission power of the PUSCH, the PUCCH, and the SRS in accordance with the UE behavior defined in 3GPP TS38.213. Specifically, the control unit 270 may set parameters for controlling the transmission power of the PUSCH, the PUCCH, and the SRS.

[0064] Specifically, the control unit 270 may set at least one of the values ​​of p0, α, and a power control adjustment state, which are parameters defined in 3GPP TS38.213. A specific example of transmission power control will be described later.

[0065] The control unit 270 may transmit an uplink data channel (PUSCH) in a time domain (e.g., a symbol) to which SBFD is applied, and, when separate UL power control is applied to the uplink data channel, may perform open-loop transmission power control for the uplink data channel without feedback from the receiving side for each uplink data channel. The open-loop transmission power control may also be called open-loop transmission power control (OLPC).

[0066] Specifically, a separate p0, α, and power control adjustment state for SBFD may be applied to semi-static OLPC. Alternatively, a separate p0 for SBFD may be configured for dynamic OLPC. Alternatively, a separate p0-PUSCH-Alpha for SBFD (e.g., sbfd-p0-PUSCH-Alpha-r19) may be configured by ConfiguredGrantConfig.

[0067] In this way, the control unit 270 may set the OLPC parameters semi-statically or dynamically for each uplink data channel (PUSCH).

[0068] The control unit 270 transmits an uplink data channel (PUSCH) in a time domain (e.g., a symbol) to which SBFD is applied, and when separate UL power control is applied to the uplink data channel, may execute closed-loop transmission power control for the uplink data channel, which is based on feedback from the receiving side for each uplink data channel. The closed-loop transmission power control may also be called closed-loop transmission power control (CLPC).

[0069] Specifically, control unit 270 may apply individual CLPC parameters to PUSCH transmission in SBFD symbols and non-SBFD symbols. For example, sbfd-sri-PUSCH-ClosedLoopIndex-r19 (this may be a tentative name; the same applies hereinafter) and sbfd-powerControlLoopToUse-r19 may be applied individually to SBFD symbols and non-SBFD symbols. In this way, control unit 270 may perform CLPC based on CLPC information elements (IEs) that are individually set for each uplink data channel in the time domain to which SBFD is applied.

[0070] Furthermore, when transmitting an uplink data channel (PUSCH) in a time domain (e.g., a symbol) to which SBFD is applied and when separate transmission power control (separate UL power control) is applied to the uplink data channel, the control unit 270 may execute OLPC and CLPC for the uplink data channel. That is, when separate transmission power control (separate UL power control) is applied to the uplink data channel (PUSCH) in an SBFD symbol and a non-SBFD symbol, the control unit 270 may execute both OLPC and CLPC. OLPC and CLPC may be executed exclusively on the time axis, but the control unit 270 may execute OLPC and CLPC in a composite manner in accordance with an instruction of a parameter related to OLPC or CLPC.

[0071] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation relating to the transmission power control of the uplink data channel (PUSCH) when SBFD is applied.

[0072] (3.1) Assumptions and Issues Regarding SBFD, 3GPP has agreed on the term "DL / UL usable PRB," which means a Physical Resource Block (PRB) that can be used as either DL or UL. Specifically, a UL subband frequency resource in an active UL BWP is called a UL usable PRB, and a DL subband frequency resource in an active DL BWP is called a DL usable PRB.

[0073] 5 shows an example of the configuration of UL subbands and DL subbands according to SBFD. As shown in FIG. 5, UL subbands (UL usable PRBs) may be configured in a UL BWP, and DL subbands (DL usable PRBs) may be configured in a DL BWP.

[0074] 6 shows a formula for calculating the transmission power of the PUSCH. A brief description will be given of the PUSCH transmission power control method defined in Chapter 7 of 3GPP TS38.213.

[0075] The PUSCH transmit power control shown in FIG. 6 may be applied when a UE transmits a PUSCH in an active UL BWP b of carrier f of serving cell c using a parameter set with index j and a PUSCH power control adjustment state with index l.

[0076] Specifically, when a first TCI-State or TCI-UL-State and a second TCI-State or TCI-UL-State are indicated to the UE and configured by a multi-panel scheme, the UE may decide to apply both the first TCI-State or TCI-UL-State and the second TCI-State or TCI-UL-State at PUSCH transmission opportunity i.

[0077] The UE may calculate the PUSCH transmit power (P_PUSCH,b,f,c,k̂(i,j,q_d,l)) for the kth indicated TCI-State or TCI-UL-State according to the formula shown in Figure 6. The formula may include multiple parameters, specifically, p0, α (Alpha), and PLRS-related parameters.

[0078] P CMAX,f,c,k (i) is the maximum output power set by the UE for the kth instructed TCI-State or TCI-UL-State.

[0079] The p0-related parameters (see the dotted box in the figure, same below) are parameters consisting of the sum of the components (P_O_NOMINAL,PUSCH,f,c)(j) and (P_O_UE_PUSCH,b,f,c)(j), where j∈{0,1,...,J-1}.

[0080] The PL-related parameters are the reference signal (RS) index q for the active DL BWP of carrier f of serving cell c. d is the DL path loss estimate in dB calculated by the UE using

[0081] 3GPP also agrees to support separate UL power control for transmitting PUSCH, PUCCH, and SRS in SBFD and non-SBFD symbols, which may be applied in a single TRP scenario.

[0082] However, if separate transmit power control for UL physical channels can be applied while using SBFD and non-SBFD symbols, a problem arises in that the UE is unable to determine the appropriate transmit power control for the UL physical channels, in particular the PUSCH (uplink data channel), which is also used for scheduling grants and may be transmitted more frequently compared to the PUCCH.

[0083] That is, the UE needs to appropriately support transmission power control (separate UL power control) for PUSCH transmission in SBFD symbols and non-SBFD symbols, assuming a framework of PUSCH spatial information.

[0084] (3.2) Operational Overview The following operational example may be executed if the following preconditions are met:

[0085] Single TRP scenario: Instead of setting a single (common) Transmission Configuration Indication (TCI) state for multiple UL / DL channels (including PUSCH) (Unified TCI state), an individual TCI-State is set for each channel.

[0086] No UL spatial filter is applied to SBFD and non-SBFD symbols.

[0087] However, these preconditions are not necessarily required. For example, the operation example may be performed in a multiple TRP scenario or when a UL spatial filter is applied.

[0088] Specifically, the following example operation may be performed.

[0089] (Operational Example 1): Separate open-loop transmit power control (OLPC) parameters are supported for PUSCH transmission in SBFD symbols and non-SBFD symbols.

[0090] (Operational Example 1-1): Individual p0 or α for semi-static OLPC. (Option 1-1): Individual p0-AlphaSets (e.g., sbfd-p0-AlphaSets-r19) in PUSCH-PowerControl, or individual sri-P0-PUSCH-AlphaSetId (e.g., sbfd-sri-P0-PUSCH-AlphaSetId-r19) in SRI-PUSCH-PowerControl is set.

[0091] (Option 1-2): An individual p0 or α in P0-PUSCH-AlphaSet (e.g., sbfd-p0-r19 or sbfd-alpha-r19) is set.

[0092] (Operation Example 1-2): Individual p0 for dynamic OLPC. (Option 2-1): An individual p0-PUSCH-SetList (for example, sbfd-p0-PUSCH-SetList-r19) is set by PUSCH-PowerControl.

[0093] (Option 2-2): An individual p0-List (e.g., sbfd-p0-List-r19) is set by P0-PUSCH-Set.

[0094] (Operation Example 1-3): An individual p0-PUSCH-Alpha (for example, sbfd-p0-PUSCH-Alpha-r19) is configured by ConfiguredGrantConfig.

[0095] (Operation Example 2): Separate closed-loop power control (CLPC) parameters are supported for PUSCH transmission in SBFD symbols and non-SBFD symbols.

[0096] (Operation example 2-1): An individual sri-PUSCH-ClosedLoopIndex (for example, sbfd-sri-PUSCH-ClosedLoopIndex-r19) is set by SRI-PUSCH-PowerControl.

[0097] (Operation example 2-2): An individual powerControlLoopToUse (for example, sbfd-powerControlLoopToUse-r19) is set by ConfiguredGrantConfig.

[0098] (Operation Example 3): Separate open-loop power control (OLPC) parameters and separate closed-loop power control (CLPC) parameters are supported for PUSCH transmission in SBFD symbols and non-SBFD symbols.

[0099] (Operation example 3-1): An individual PUSCH-PowerControl (for example, sbfd-PUSCH-PowerControl-r19) is set by PUSCH-Config.

[0100] (Operation example 3-2): An individual sri-PUSCH-MappingToAddModList (for example, sbfd-sri-PUSCH-MappingToAddModList-r19) is set by PUSCH-PowerControl.

[0101] (Operation example 3-3): Combination of any option of operation example 1 with any option of operation example 2. Note that operation examples 1-1, 1-2, 2-1 and operation examples 3-1 and 3-2 are applied to DG (dynamic grant) PUSCH, and operation example 1-3 and operation example 2-2 may also be applied to CG (configured grant) PUSCH.

[0102] 7 shows an example of a sequence for UL power control of a PUSCH. As shown in FIG. 7, the TCI-State may be indicated to the UE by the MAC-CE.

[0103] When SBFD is applied, the UE may perform UL power control of the PUSCH based on the TCI-State.

[0104] The UE may transmit a PUSCH having a transmission power adjusted by the UL power control to the network (gNB).

[0105] (3.3) Operational Example 1 (3.3.1) Operational Example 1-1: Individual p0 or α for Semi-Static OLPC Fig. 8 shows a configuration example of PUSCH-PowerControl etc. according to Operational Example 1-1. As shown in Fig. 8 (see underlined parts), individual open-loop transmit power control (OLPC) parameters may be supported for PUSCH transmission in SBFD symbols and non-SBFD symbols.

[0106] (Option 1-1): An individual p0-AlphaSets (e.g., sbfd-p0-AlphaSets-r19) in PUSCH-PowerControl or an individual sri-P0-PUSCH-AlphaSetId (e.g., sbfd-sri-P0-PUSCH-AlphaSetId-r19) in SRI-PUSCH-PowerControl may be configured.

[0107] (Option 1-2): An individual p0 or α in P0-PUSCH-AlphaSet (e.g., sbfd-p0-r19 or sbfd-alpha-r19) may be set.

[0108] In the case of PUSCH transmission in non-SBFD symbols where Option 1-1 is applied, the UE uses the PUSCH as legacy (as per the previous 3GPP specification), that is, based on p0-AlphaSets and sri-P0-PUSCH-AlphaSetId. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0109] If the DCI format includes an SRS resource indicator (SRI) field, the UE obtains, from the SRI-PUSCH-PowerControlId in SRI-PUSCH-PowerControl, a mapping between the set of SRI field values ​​in the DCI format and the set of indices provided by sri-P0-PUSCH-AlphaSetId that are mapped to the set of P0-PUSCH-AlphaSets in p0-AlphaSets, and determines the P0-PUSCH-AlphaSets that are mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0110] If the DCI format does not include the SRI field, the UE shall select the P0-PUSCH-AlphaSet from the value of the first P0-PUSCH-AlphaSet in p0-AlphaSets. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0111] For PUSCH transmission in an SBFD symbol to which Option 1-1 applies, if sbfd-p0-AlphaSets-r19 is set / present in PUSCH-PowerControl, sbfd-sri-P0-PUSCH-AlphaSetId-r19 is set / present in SRI-PUSCH-PowerControl, and the DCI format includes an SRI field, the UE shall obtain, from the SRI-PUSCH-PowerControlId in SRI-PUSCH-PowerControl, the mapping between the set of SRI field values ​​in the DCI format and the set of indices provided by sbfd-sri-P0-PUSCH-AlphaSetId-r19 that are mapped to the set of P0-PUSCH-AlphaSets in sbfd-p0-AlphaSets-r19, and the P0-PUSCH-AlphaSets that are mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0112] If the DCI format does not include the SRI field, the UE shall select P0-PUSCH-AlphaSet from the first P0-PUSCH-AlphaSet value in sbfd-p0-AlphaSets-r19. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0113] If sbfd-p0-AlphaSets-r19 is configured / present in PUSCH-PowerControl and sbfd-sri-P0-PUSCH-AlphaSetId-r19 is not configured / present in SRI-PUSCH-PowerControl and the DCI format contains an SRI field, the UE shall obtain from the SRI-PUSCH-PowerControlId of SRI-PUSCH-PowerControl between the set of values ​​of the SRI field in the DCI format and the set of indices provided by sri-P0-PUSCH-AlphaSetId that are mapped to the set of P0-PUSCH-AlphaSets in sbfd-p0-AlphaSets-r19, and the set of P0-PUSCH-AlphaSets that are mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,cThe value of (j) may be determined.

[0114] If the DCI format does not include the SRI field, the UE shall select P O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0115] If sbfd-p0-AlphaSets-r19 is not set / present in PUSCH-PowerControl, sbfd-sri-P0-PUSCH-AlphaSetId-r19 is set / present in SRI-PUSCH-PowerControl, and the DCI format contains an SRI field, the UE shall obtain, from the SRI-PUSCH-PowerControlId in SRI-PUSCH-PowerControl, a mapping between the set of values ​​of the SRI field in the DCI format and the set of indices provided by sbfd-sri-P0-PUSCH-AlphaSetId-r19, and shall use the PUSCH field mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0116] If the DCI format does not include the SRI field, the UE shall select the P0-PUSCH-AlphaSet from the value of the first P0-PUSCH-AlphaSet in p0-AlphaSets. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0117] If neither sbfd-p0-AlphaSets-r19 nor sbfd-sri-P0-PUSCH-AlphaSetId-r19 is configured / existent, the UE may act according to one of the following:

[0118] (Alt. 1): Based on the conventional p0-AlphaSets and sri-P0-PUSCH-AlphaSetId, O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0119] (Alt. 2): Default values ​​may be applied, e.g., PO_UE_PUSCH,b,f,c (j) default value 0, α b,f,c A default value of 1 for (j) may be applied.

[0120] For DG PUSCH transmission on non-SBFD symbols where Option 1-2 applies, the UE shall select P O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0121] For DG PUSCH transmission on SBFD symbols, the UE may make the decision based on P0-PUSCH-AlphaSet as per the previous 3GPP specifications. If sbfd-p0-r19 and / or sbfd-alpha-r19 are set by the determined P0-PUSCH-AlphaSet: O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined based on sbfd-p0-r19 and / or sbfd-alpha-r19 of the P0-PUSCH-AlphaSet.

[0122] If sbfd-p0-r19 or sbfd-alpha-r19 is not configured by the determined P0-PUSCH-AlphaSet, the UE may act according to one of the following:

[0123] ・(Alt. 1): P O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined based on p0 or α of the P0-PUSCH-AlphaSet.

[0124] (Alt. 2): Default values ​​may be applied, e.g., P O_UE_PUSCH,b,f,c (j) default value 0, α b,f,c A default value of 1 for (j) may be applied.

[0125] (3.3.2) Operation Example 1-2 Fig. 9 shows a configuration example of PUSCH-Power Control etc. according to Operation Example 1-2. As shown in Fig. 9 (see underlined part), parameters related to individual p0 setting of dynamic OLPC may be supported.

[0126] (Option 2-1): An individual p0-PUSCH-SetList (e.g., sbfd-p0-PUSCH-SetList-r19) is set by PUSCH-PowerControl.

[0127] (Option 2-2): An individual p0-List (e.g., sbfd-p0-List-r19) is set by P0-PUSCH-Set.

[0128] For PUSCH transmission in non-SBFD symbols where Option 2-1 is applied, the UE shall use PUSCH if the value of the OLPC field is "1", "01", or "10". O_UE_PUSCH,b,f,c The value of (j) may be determined legacy, i.e., based on p0-PUSCH-SetList.

[0129] If the value of the OLPC field is "0" or "00", the UE O_UE_PUSCH,b,f,c The value of (j) may be determined legacy, i.e., based on p0-AlphaSets.

[0130] For PUSCH transmission in an SBFD symbol to which Option 2-1 applies, if the value of the OLPC field is "1", "01", or "10" and sbfd-p0-PUSCH-SetList-r19 is set / exists in PUSCH-PowerControl, the UE shall O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0131] If the value of the OLPC field is '1' or '01', the UE shall select the P0-PUSCH-SetList as the first value of the P0-PUSCH-Set with the smallest P0-PUSCH-SetId in sbfd-p0-PUSCH-SetList-r19. O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0132] If the value of the OLPC field is "10", the UE shall set P0-PUSCH-SetList-r19 as the second value of the P0-PUSCH-Set with the smallest P0-PUSCH-SetId in sbfd-p0-PUSCH-SetList-r19. O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0133] If sbfd-p0-PUSCH-SetList-r19 is not configured (does not exist) in PUSCH-PowerControl, the UE may act according to one of the following:

[0134] (Alt. 1): The UE sets P0-PUSCH-SetList based on the conventional p0-PUSCH-SetList. O_UE_PUSCH,b,f,c The value of (j) may be determined in the same way as in the case of PUSCH transmission in non-SBFD symbols.

[0135] (Alt. 2): Default values ​​may be applied, e.g., P O_UE_PUSCH,b,f,c A default value of 0 for (j) may be applied.

[0136] (Alt. 3): Operation example 1-1 may be applied. That is, the UE selects PUSCH based on sbfd-sri-P0-PUSCH-AlphaSetId-r19 and / or sbfd-p0-AlphaSets-r19. O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0137] If the OLPC field value is '0' or '00', the UE will use P as legacy, i.e., based on p0-AlphaSets. O_UE_PUSCH,b,f,c The UE may determine the value of (j). In this case, Operation Example 1-1 may be applied. That is, the UE may use sbfd-sri-P0-PUSCH-AlphaSetId-r19 to replace sri-P0-PUSCH-AlphaSetId, or may use sbfd-p0-AlphaSets-r19 to replace p0-AlphaSets to determine p0.

[0138] For PUSCH transmission in non-SBFD symbols where Option 2-2 is applied, the UE shall transmit PUSCH if the OLPC field value is "1", "01", or "10". O_UE_PUSCH,b,f,c The value of (j) may be determined as a legacy, that is, based on the value of p0-List-r16 in P0-PUSCH-Set.

[0139] If the OLPC field value is "0" or "00", the UE O_UE_PUSCH,b,f,cThe value of (j) may be determined legacy, i.e., based on p0-AlphaSets.

[0140] For PUSCH transmission in an SBFD symbol to which Option 2-2 applies, if the OLPC field value is "1" or "01" or "10" and sbfd-p0-List-r19 is set / exists in P0-PUSCH-Set, the UE shall O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0141] If the OLPC field value is '1' or '01', the UE shall set the P0-PUSCH-SetId as the first value of sbfd-p0-List-r19 of the P0-PUSCH-Set with the lowest P0-PUSCH-SetId. O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0142] If the OLPC field value is "10", the UE shall set P0-PUSCH-SetId as the second value of sbfd-p0-List-r19 of the P0-PUSCH-Set with the lowest P0-PUSCH-SetId. O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0143] If sbfd-p0-List-r19 is not configured (does not exist) in P0-PUSCH-Set, the UE may act in one of the following ways:

[0144] (Alt. 1): The UE determines the P0-PUSCH-Set based on the value of p0-List-r16 in P0-PUSCH-Set as a legacy setting. O_UE_PUSCH,b,f,c The value of (j) may be determined in the same way as in the case of PUSCH transmission in non-SBFD symbols.

[0145] (Alt. 2): Default values ​​may be applied, e.g., P O_UE_PUSCH,b,f,c A default value of 0 for (j) may be applied.

[0146] (Alt. 3): Operation example 1-1 may be applied. That is, the UE selects PUSCH based on sbfd-sri-P0-PUSCH-AlphaSetId-r19 and / or sbfd-p0-AlphaSets-r19. O_UE_PUSCH,b,f,c The value of (j) may be determined.

[0147] If the OLPC field value is '0' or '00', the UE will use P as legacy, i.e., based on p0-AlphaSets. O_UE_PUSCH,b,f,c The UE may determine the value of (j). In this case, Operation Example 1-1 may be applied. That is, the UE may use sbfd-sri-P0-PUSCH-AlphaSetId-r19 to replace sri-P0-PUSCH-AlphaSetId and / or use sbfd-p0-AlphaSets-r19 to replace p0-AlphaSets to determine p0.

[0148] In addition, in the case of Option 2-1 / 2-2, OLPC of PUSCH in SBFD symbols and non-SBFD symbols may be indicated using separate OLPC fields in the DCI format. When PUSCH is transmitted in SBFD symbols, the SBFD OLPCI field may be applied. When PUSCH is transmitted in non-SBFD symbols, the non-SBFD OLPCI field may be applied.

[0149] Individual bits in the OLPC field of the DCI format may be used to indicate OLPC for PUSCHs in SBFD symbols and non-SBFD symbols. For example, for PUSCH transmission in SBFD symbols, the most significant bit / least significant bit (LSB / MSB) of the OLPC field may be applied. For PUSCH transmission in non-SBFD symbols, the MSB / LSB of the OLPC field may be applied.

[0150] (3.3.3) Operation Example 1-3 Fig. 10 shows a configuration example of ConfiguredGrantConfig according to Operation Example 1-3. As shown in Fig. 10 (see underlined portion), an individual p0-PUSCH-Alpha (for example, sbfd-p0-PUSCH-Alpha-r19) may be configured by ConfiguredGrantConfig.

[0151] Note that the UE may not assume that sbfd-p0-PUSCH-Alpha-r19 is configured / present via ConfiguredGrantConfig if CG PUSCH is restricted to only SBFD symbols or if it is restricted to only non-SBFD symbols.

[0152] If the CG PUSCH can be transmitted in SBFD symbols and non-SBFD symbols, the UE may operate as follows.

[0153] For CG PUSCH transmission in SBFD symbols, if sbfd-p0-PUSCH-Alpha-r19 is configured (present) in ConfiguredGrantConfig, the UE shall O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0154] If sbfd-p0-PUSCH-Alpha-r19 is not configured (not present) in ConfiguredGrantConfig, the UE may act according to one of the following:

[0155] (Alt. 1): Based on p0-PUSCH-Alpha, P O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0156] (Alt. 1): Default values ​​may be applied, e.g., P O_UE_PUSCH,b,f,c (j) default value 0, α b,f,c A default value of 1 for (j) may be applied.

[0157] For CG PUSCH transmission in non-SBFD symbols, the UE calculates P O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) may be determined.

[0158] (3.4) Operation Example 2 In this operation example, separate closed-loop transmission power control (CLPC) parameters are supported for PUSCH transmission in SBFD symbols and non-SBFD symbols.

[0159] (Operation example 2-1): An individual sri-PUSCH-ClosedLoopIndex (for example, sbfd-sri-PUSCH-ClosedLoopIndex-r19) is set by SRI-PUSCH-PowerControl.

[0160] (Operation example 2-2): An individual powerControlLoopToUse (for example, sbfd-powerControlLoopToUse-r19) is set by ConfiguredGrantConfig.

[0161] Note that the UE may not assume that sbfd-powerControlLoopToUse-r19 is configured / present by ConfiguredGrantConfig if CG PUSCH is restricted to only SBFD symbols or only non-SBFD symbols.

[0162] Fig. 11 shows example configurations of SRI-PUSCH-PowerControl and ConfiguredGrantConfig according to operation example 2. As shown in Fig. 11 (see underlined parts), sbfd-sri-PUSCH-ClosedLoopIndex-r19 and sbfd-powerControlLoopToUse-r19 may be used.

[0163] (3.4.1) Operation Example 2-1 In the case of PUSCH transmission in a non-SBFD symbol, the UE may determine the PUSCH power control adjustment state 1 as legacy, that is, based on the legacy sri-PUSCH-ClosedLoopIndex of SRI-PUSCH-PowerControl.

[0164] If the DCI format includes an SRI field, the UE may obtain, from the SRI-PUSCH-PowerControlId of the SRI-PUSCH-PowerControl, a mapping between the set of SRI field values ​​in the DCI format and the PUSCH power control adjustment state l value provided by the sri-PUSCH-ClosedLoopIndex, and determine the corresponding value to be mapped to the SRI field.

[0165] If the DCI format does not include an SRI field, the value of PUSCH power control adjustment state 1 may be set to 0.

[0166] For PUSCH transmission in an SBFD symbol, if the DCI format includes an SRI field and sbfd-sri-PUSCH-ClosedLoopIndex-r19 is configured or present in SRI-PUSCH-PowerControl, the UE may obtain, from SRI-PUSCH-PowerControlId of SRI-PUSCH-PowerControl, a mapping between the set of SRI field values ​​in the DCI format and the value of PUSCH power control adjustment state l provided by sbfd-sri-PUSCH-ClosedLoopIndex-r19, and determine the corresponding value to be mapped to the SRI field.

[0167] If sbfd-sri-PUSCH-ClosedLoopIndex-r19 is not configured (is not present) in SRI-PUSCH-PowerControl, the UE may act according to one of the following:

[0168] (Alt. 1): The UE determines the value of PUSCH power control adjustment state l based on sri-PUSCH-ClosedLoopIndex of SRI-PUSCH-PowerControl, i.e., it can be the same as DG PUSCH transmission on non-SBFD symbols.

[0169] (Alt. 2): A default value may be applied. For example, a default value of 0 / 1 for the PUSCH power control adjustment state l may be applied. Also, the default value (l=0 / 1) may be applied when the SRI field is not included in the DCI format.

[0170] (3.4.2) Operation Example 2-2 When a CG PUSCH can be transmitted using SBFD symbols and non-SBFD symbols, and when a CG PUSCH is transmitted using non-SBFD symbols, the value of PUSCH power control adjustment state 1 may be provided by powerControlLoopToUse. When a CG PUSCH is transmitted using SBFD symbols, if sbfd-powerControlLoopToUse-r19 is set / existed in ConfiguredGrantConfig, the value of PUSCH power control adjustment state 1 may be provided by sbfd-powerControlLoopToUse-r19.

[0171] If sbfd-powerControlLoopToUse-r19 is not configured or is not present in ConfiguredGrantConfig, the UE may act according to one of the following:

[0172] (Alt. 1): The PUSCH power control adjustment state l value may be provided by powerControlLoopToUse.

[0173] (Alt. 1): The default value 0 / 1 of PUSCH power control adjustment state 1 may be applied.

[0174] (3.5) Operation Example 3 (3.5.1) Operation Example 3-1 Fig. 12 shows a configuration example of PUSCH-Config according to Operation Example 3-1. As shown in Fig. 12 (see underlined portion), an individual PUSCH-PowerControl (for example, sbfd-PUSCH-PowerControl-r19) may be set by PUSCH-Config.

[0175] For PUSCH transmission in non-SBFD symbols, the UE shall O_UE_PUSCH,b,f,c (j), α b,f,c The values ​​of (j) and PUSCH power control adjustment state 1 may be determined as legacy. As described above, legacy may mean following the conventional 3GPP specifications.

[0176] For PUSCH transmission in SBFD symbols, if sbfd-PUSCH-PowerControl-r19 is set to PUSCH-Config, the UE shall O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l may be determined.

[0177] If sbfd-PUSCH-PowerControl-r19 is not configured in PUSCH-Config, or if parameters with specific values ​​(e.g., p0, alpha, closedLoopIndex) are not configured in sbfd-PUSCH-PowerControl-r19, the UE may operate according to one of the following:

[0178] (Alt. 1): The UE may set certain parameter values ​​(e.g., P O_UE_PUSCH,b,f,c (j), α b,f,c (j) or the value of PUSCH power control adjustment state l) (Alt. 2): A default value may be applied. For example, P O_UE_PUSCH,b,f,c (j) default value 0, αb,f,c A default value of 1 for (j) and a default value of 0 / 1 for PUSCH power control adjustment state 1 may be applied.

[0179] (3.5.2) Operation Example 3-2 Fig. 13 shows a configuration example of PUSCH-Power Control according to Operation Example 3-2. As shown in Fig. 13 (see underlined part), an individual sri-PUSCH-MappingToAddModList (for example, sbfd-sri-PUSCH-MappingToAddModList-r19) may be set in PUSCH-Power Control.

[0180] For PUSCH transmission on non-SBFD symbols, the UE uses PUSCH as legacy, i.e., based on the legacy SRI-PUSCH-PowerControl in sri-PUSCH-MappingToAddModList. O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l may be determined.

[0181] For PUSCH transmission in SBFD symbols, if sbfd-sri-PUSCH-MappingToAddModList-r19 is configured (present) in PUSCH-PowerControl, the UE shall O_UE_PUSCH,b,f,c (j), α b,f,c To determine the values ​​of (j) and PUSCH power control adjustment state l, a mapping may be obtained between the set of SRI field values ​​in the DCI format from the SRI-PUSCH-PowerControlId in sbfd-SRI-PUSCH-PowerControl-r19 in sbfd-sri-PUSCH-MappingToAddModList-r19.

[0182] If sbfd-sri-PUSCH-MappingToAddModList-r19 is not configured (does not exist) in PUSCH-Config, or if a parameter with a specific value (e.g., p0, alpha, closedLoopIndex) is not configured (does not exist) in SRI-PUSCH-PowerControl of sbfd-sri-PUSCH-MappingToAddModList-r19, the UE may operate in one of the following ways:

[0183] (Alt. 1): The UE determines certain parameter values ​​(e.g., P O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l).

[0184] (Alt. 2): Default values ​​may be applied, e.g., P O_UE_PUSCH,b,f,c (j) default value 0, α b,f,c A default value of 1 for (j) and a default value of 0 / 1 for PUSCH power control adjustment state 1 may be applied.

[0185] (3.6) Modifications The following modifications may be made to the above-described operational examples. For example, the options of operational examples 1-1 / 1-2 / 1-3 may be combined with the options of operational example 2. Operational example 3-2 can be combined with the options of operational examples 1-1 / 1-2 and / or operational example 2-1.

[0186] For example, in the case of PUSCH transmission in an SBFD symbol, when Operational Example 1-1 / 1-2 and / or Operational Example 2-1 are applied, the mapping from the SRI-PUSCH-PowerControlId of SRI-PUSCH-PowerControl between sets of SRI field values ​​in the DCI format may be replaced with the mapping from the SRI-PUSCH-PowerControlId of sbfd-SRI-PUSCH-PowerControl-r19 between sets of SRI field values ​​in the DCI format.

[0187] The total number of power control adjustment states for the PUSCH may be greater than 2. For example, two power control adjustment states for SBFD and two power control adjustment states for non-SBFD may be set separately.

[0188] In the case of Operation Example 2 and Operation Example 3, the value of closedLoopIndex may be one of the following.

[0189] (Alt. 1): The value of closedLoopIndex for SBFD / non-SBFD may be mapped to the index of the power control adjustment state for SBFD / non-SBFD only.

[0190] For example, indexes for two power control adjustment states for SBFD and two power control adjustment states for non-SBFD may be set. Candidate values ​​of closedLoopIndex for SBFD may be index #0 and index #1, which are mapped to the power control adjustment states for SBFD, respectively. Candidate values ​​of closedLoopIndex for non-SBFD may be index #0 and index #1, which are mapped to the power control adjustment states for non-SBFD, respectively.

[0191] (Alt. 2): The value of closedLoopIndex for SBFD / non-SBFD may be mapped to an index within the power control adjustment state for SBFD and non-SBFD.

[0192] For example, two indexes for power control adjustment states for SBFD and two indexes for power control adjustment states for non-SBFD may be set. Candidate values ​​for closedLoopIndex may be any of index #0, index #1, index #2, index #3, and index #4.

[0193] In addition, only one closedLoopIndex may be set (i.e., there is no separate setting of closedLoopIndex for SBFD as in operation examples 2 and 3), and may be mapped to the power control adjustment state for SBFD / non-SBFD, respectively.

[0194] Furthermore, up to three power control adjustment states may be set, up to two power control adjustment states may be used for non-SBFD, and up to one power control adjustment state may be set separately for SBFD. In this case, it is not necessary to individually set the closedLoopIndex for SBFD in Operation Example 2 or Operation Example 3. In the case of PUSCH transmission in an SBFD symbol, the index of an existing power control adjustment state for SBFD may be applied.

[0195] (3.7) UE Capability A UE may report the presence or absence of the following capabilities (UE Capability Information) regarding SBFD to the network. The UE Capability Information may be defined for each UE, frequency range (FR), frequency channel (FC), etc. Furthermore, RRC signaling and configuration for reporting the UE Capability Information may be defined.

[0196] Support for individual UL power control for PUSCH transmission in SBFD symbols and non-SBFD symbols Support for individual setting of p0-AlphaSets for SBFD in PUSCH-PowerControl Support for individual setting of sri-P0-PUSCH-AlphaSetId for SBFD in SRI-PUSCH-PowerControl Support for individual setting of p0 and alpha for SBFD in P0-PUSCH-AlphaSet Support for individual setting of p0-PUSCH-SetList for SBFD in PUSCH-PowerControl Support for individual setting of p0-List for SBFD in P0-PUSCH-Set Support for individual setting of sri-PUSCH-ClosedLoopIndex for SBFD in SRI-PUSCH-PowerControl Support for individual setting of powerControlLoopToUse for SBFD in ConfiguredGrantConfig Support for individual setting of PUSCH-PowerControl for SBFD Support for individual setting of sri-PUSCH-MappingToAddModList for SBFD in PUSCH-PowerControl PUSCH power control Support for the maximum number of adjustment states Support for the maximum number of individual PUSCH power control adjustment states for PUSCHs of SBFD symbols According to the above-described operation example, when SBFD is applied, the UE can perform OLPC or CLPC for each PUSCH even when individual OLPC or CLPC is applied to the PUSCH. Therefore, the UE can perform appropriate transmit power control for uplink data channels such as PUSCHs using SBFD symbols and non-SBFD symbols even when individual transmit power control for UL physical channels can be applied.

[0197] (4) Other Embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and that various modifications and improvements are possible.

[0198] For example, in the above-described embodiment, the term "subband" is used, but the subband may simply be called a band, or may be called by other similar terms such as auxiliary band, spare band, etc. Furthermore, XDD / SBFD may be a provisional name, and may be called by other similar terms as described above.

[0199] Also, in the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0200] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0201] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0202] The block diagram ( FIG. 4 ) used to explain the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0203] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0204] Furthermore, the above-described gNB 100 and UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 14 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 14, the devices may be configured as a computer 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.

[0205] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0206] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0207] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0208] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0209] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0210] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

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

[0212] 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 called, for example, a network device, a network controller, a network card, or a communication module.

[0213] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0214] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0215] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0216] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0217] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0218] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0219] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0220] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

[0221] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input and output via multiple network nodes.

[0222] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

[0223] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0224] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0225] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0226] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0228] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

[0230] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0231] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0232] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0233] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0234] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0235] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0237] A mobile station may also be referred to by those 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 terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0238] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0239] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel (or sidelink).

[0240] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0241] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0242] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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

[0245] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0246] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0247] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

[0248] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

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

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

[0251] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0253] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.

[0254] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0256] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

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

[0258] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0259] The above-described structures of the radio frame, subframe, slot, minislot, and symbol are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations may be changed in various ways.

[0260] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0261] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

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

[0263] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0264] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0265] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0266] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0267] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0268] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0269] 15 shows an example of the configuration of a vehicle 2001. As shown in Fig. 15, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0270] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0271] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0272] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0273] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0274] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0275] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0276] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0277] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0278] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Wireless signal transceiver 220 Amplifier 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transceiver 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a transmitter that transmits an uplink data channel according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex; and a controller that transmits the uplink data channel in a time domain in which the subband full-duplex communication method is applied, and that, when individual transmission power control for the uplink data channel is applied, performs open-loop transmission power control for the uplink data channel without feedback from the receiving side for each of the uplink data channels.

2. The terminal according to claim 1, wherein the control unit semi-statically or dynamically sets parameters of the open-loop transmission power control for each of the uplink data channels.

3. A terminal comprising: a transmitter that transmits an uplink data channel according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex; and a controller that transmits the uplink data channel in a time domain in which the subband full-duplex communication method is applied, and that, when individual transmission power control is applied to the uplink data channel, performs closed-loop transmission power control on the uplink data channel based on feedback from the receiving side for each uplink data channel.

4. The terminal according to claim 3, wherein the control unit executes the closed-loop transmission power control based on information elements of the closed-loop transmission power control that are individually set for each of the uplink data channels.

5. A terminal comprising: a transmitter that transmits an uplink data channel according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex; and a controller that transmits the uplink data channel in a time domain in which the subband full-duplex communication method is applied, and that, when individual transmission power control is applied to the uplink data channel, performs open-loop transmission power control for each uplink data channel without feedback from the receiving side, and closed-loop transmission power control for each uplink data channel that assumes feedback from the receiving side.

6. A wireless communication method in a terminal, comprising: a step of transmitting an uplink data channel according to a subband full-duplex communication method in which uplink subbands and downlink subbands are allocated non-overlapping in the frequency direction within a specified time based on time division duplex; and a step of transmitting the uplink data channel in a time domain in which the subband full-duplex communication method is applied, and, when individual transmission power control for the uplink data channel is applied, performing open-loop transmission power control for the uplink data channel without feedback from a receiving side for each of the uplink data channels.

Images