Terminals and wireless communication methods
By employing an independent transmit power control method in SBFD communication, the problem of PUSCH transmit power control for UE in both SBFD and non-SBFD symbols is solved, achieving appropriate power control and improving the efficiency and reliability of the communication system.
Patent Information
- Application Number
- CN202480090617.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-26
- Publication Date
- 2026-11-17
AI Technical Summary
In both SBFD and non-SBFD symbolic representations, it is difficult for the UE to properly determine the transmit power control of the UL physical channel, especially the PUSCH, particularly when scheduling authority is high and the PUCCH transmission frequency is high.
A terminal is adopted, which has a transmitting unit and a control unit, and can perform independent transmission power control in SBFD communication mode, including open-loop and closed-loop control, and perform appropriate power control for each uplink data channel.
This enables appropriate transmit power control of the UL physical channel in both SBFD and non-SBFD symbols, improving the efficiency and reliability of the communication system.
Smart Images

Figure CN123125970A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to terminals supporting SBFD and wireless communication methods. Background Technology
[0002] The 3rd Generation Partnership Project (3GPP, a registered trademark) standardized the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)) and also standardized the next generation, known as Beyond 5G, 5G Evolution, or 6G.
[0003] For example, in 3GPP Release 19, an extension of duplex mode is being studied (Non-Patent Document 1). Specifically, the following consensus has been reached: regarding SBFD (Sub-Band non-overlapping Full Duplex), a duplex mode that allows simultaneous use of downlink (DL) and uplink (UL) within a carrier in a time division duplex (TDD) band domain, a method is being studied for indicating the position (time position) of the UL subband and DL subband (also known as SBFD subband) in the time direction (e.g., symbol) for the terminal (User Equipment, UE).
[0004] Furthermore, the following consensus has been reached regarding the following options: For the PRB (Physical Resource Block) of UL and DL that can be used as SBFD subbands, specifically, the option that the UL usable PRB is determined based on the position of the intersection between the active UL BWP and the UL subband within the SBFD symbol, and the option that the DL usable PRB is determined based on the active DL BWP and the DL subband within the SBFD symbol; and the option that the UL usable PRB and DL usable PRB are explicitly set in the active UL BWP and active DL BWP (Non-Patent Document 2).
[0005] Furthermore, the following consensus has been reached: independent transmit power control (TPC) should be applied to UL physical channels using SBFD symbols and non-SBFD symbols (specifically, PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel)) (Non-Patent Document 3). The same transmit power control can also be applied to SRS (Sounding Reference Signal).
[0006] Existing technical documents
[0007] Non-patent literature
[0008] Non-patent literature 1: "New WID: Evolution of NR duplex operation: Sub-band fullduplex (SBFD)", RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 2023
[0009] Non-patent document 2: "Final Report of 3GPP TSG RAN WG1 #116 v1.0.0", 3GPP, April 2024
[0010] Non-patent document 3: “Draft Report of 3GPP TSG RAN WG1 #117 v0.2.0”, 3GPP, May 2024 Summary of the Invention
[0011] However, when SBFD and non-SBFD symbols, determined by the options described above, are available and independent transmit power control is applied to the UL physical channel, the following problem arises: the UE cannot determine appropriate transmit power control for the UL physical channel, especially for the PUSCH (uplink data channel), which is also used for scheduling grants and may have a higher transmission frequency compared to the PUCCH.
[0012] Therefore, the following disclosure is made in view of this situation, with the aim of providing a terminal and wireless communication method that can perform appropriate uplink data channel transmit power control even when SBFD symbols and non-SBFD symbols are available and independent transmit power control is applied to the UL physical channel.
[0013] One aspect of this disclosure is a terminal (UE200) comprising: a transmitting unit (wireless signal transceiver 210) that transmits an uplink data channel following a sub-band full-duplex communication mode, wherein the sub-band full-duplex communication mode allocates uplink sub-bands and downlink sub-bands in a non-overlapping frequency direction within a predetermined time period based on time division duplex; and a control unit (control unit 270) that, when transmitting the uplink data channel in the time domain using the sub-band full-duplex communication mode and applying independent transmit power control for the uplink data channel, performs open-loop transmit power control for each uplink data channel without feedback from the receiving side.
[0014] One aspect of this disclosure is a terminal comprising: a transmitting unit that transmits an uplink data channel following a sub-band full-duplex communication mode, wherein the sub-band full-duplex communication mode allocates uplink sub-bands and downlink sub-bands in a non-overlapping frequency direction within a predetermined time period based on time division duplex; and a control unit that, when transmitting the uplink data channel in the time domain using the sub-band full-duplex communication mode and applying independent transmit power control for the uplink data channel, performs closed-loop transmit power control for each uplink data channel based on feedback from the receiving side.
[0015] One aspect of this disclosure is a terminal comprising: a transmitting unit that transmits an uplink data channel following a sub-band full-duplex communication mode, wherein the sub-band full-duplex communication mode allocates uplink sub-bands and downlink sub-bands in a non-overlapping frequency direction within a predetermined time period based on time division duplex; and a control unit that, when transmitting the uplink data channel in the time domain using the sub-band full-duplex communication mode and applying independent transmit power control for the uplink data channel, performs open-loop transmit power control for each uplink data channel without feedback from the receiving side, and performs closed-loop transmit power control for each uplink data channel based on feedback from the receiving side. Attached Figure Description
[0016] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10.
[0017] Figure 2 This is a diagram illustrating an example of the structure of wireless frames, subframes, and time slots used in the wireless communication system 10.
[0018] Figure 3 This is a diagram showing structural examples of TDD and XDD / SBFD.
[0019] Figure 4This is the function block structure diagram of gNB100 and UE200.
[0020] Figure 5 This is a diagram illustrating a structural example of a UL sub-band and a DL sub-band based on SBFD.
[0021] Figure 6 This is a diagram showing the calculation formula for the transmission power of the PUSCH.
[0022] Figure 7 This is a diagram showing an example of timing related to PUSCH's UL power control.
[0023] Figure 8 This is a diagram showing a structural example of PUSCH-PowerControl, etc., in action example 1-1.
[0024] Figure 9 This is a diagram showing a structural example of PUSCH-PowerControl, etc., in action examples 1-2.
[0025] Figure 10 This is a diagram showing the structure example of ConfiguredGrantConfig in action examples 1-3.
[0026] Figure 11 This is a diagram illustrating the structure of SRI-PUSCH-PowerControl and ConfiguredGrantConfig in Action Example 2.
[0027] Figure 12 This is a diagram showing the structure example of PUSCH-Config in action example 3-1.
[0028] Figure 13 This is a diagram illustrating the structure of the PUSCH-PowerControl in action example 3-2.
[0029] Figure 14 This is a diagram illustrating an example of the hardware structure of gNB100 and UE200.
[0030] Figure 15 This is a diagram showing a structural example of vehicle 2001. Detailed Implementation
[0031] The embodiments are described below with reference to the accompanying drawings. Furthermore, the same or similar reference numerals are used to denote the same function and structure, and their descriptions are omitted where appropriate.
[0032] (1) Overall general structure of wireless communication system
[0033] Figure 1This is a schematic diagram of the overall structure of the wireless communication system 10 in this embodiment. The wireless communication system 10 is a 5G New Radio (NR) compliant wireless communication system, comprising a Next Generation Radio Access Network (NG-RAN20) and a terminal 200 (UE200, User Equipment). Alternatively, the wireless communication system 10 may also be a wireless communication system compliant with technologies such as Beyond 5G, 5G Evolution, or 6G.
[0034] NG-RAN20 includes a radio base station 100 (hereinafter referred to as gNB100). Furthermore, the specific structure of the wireless communication system 10, including the number of gNBs and UEs, is not limited to... Figure 1 The example shown.
[0035] NG-RAN20 actually contains multiple NG-RAN nodes, specifically multiple gNBs (or ng-eNBs), connected to a 5G-compliant core network (5GC, not shown). Additionally, NG-RAN20 and 5GC can be simply referred to as a "network".
[0036] The gNB100 is a 5G-compliant wireless base station that performs 5G-compliant wireless communication with the UE200. The gNB100 and UE200 can support massive MIMO (Multiple Input Multiple Output) by controlling the wireless signals transmitted from multiple antenna elements to generate antenna beams with higher directionality (hereinafter referred to as BM), carrier aggregation (CA) that uses multiple component carriers (CC), and dual connectivity (DC) that allows simultaneous communication between the UE and two NG-RAN nodes.
[0037] Furthermore, DCs can be of various types, including Multi-RATDual Connectivity (MR-DC) which utilizes multiple radio access technologies, and NR-NR Dual Connectivity (NR-DC) which utilizes only NR. Additionally, MR-DC can be E-UTRA-NR Dual Connectivity (EN-DC) where eNBs form the master node (MN) and gNBs form the slave node (SN), or it can be the opposite: NR-E-UTRA Dual Connectivity (NE-DC).
[0038] The gNB100 can transmit multiple beams (BMs) with different transmission directions (also referred to as direction, radiation direction, or coverage area, etc.) in both space-division and time-division configurations. Furthermore, the gNB100 can transmit multiple beams (BMs) simultaneously.
[0039] In addition, the wireless communication system 10 can also support multiple frequency ranges (FRs). Specifically, the following frequency ranges can be supported.
[0040] FR1: 410 MHz~7.125 GHz
[0041] ·FR2-1: 24.25 GHz~52.6 GHz
[0042] In FR1, a sub-carrier spacing (SCS) of 15, 30, or 60 kHz can be used, with a bandwidth (BW) of 5–100 MHz. FR2-1 operates at a higher frequency than FR1, and can use a sub-carrier spacing (SCS) of 60 or 120 kHz (which may also include 240 kHz), with a bandwidth (BW) of 50–400 MHz.
[0043] Alternatively, SCS can also be interpreted as a parameter set (numerology). The parameter set is defined in 3GPP TS 38.300 and corresponds to a subcarrier spacing in the frequency domain.
[0044] Furthermore, the wireless communication system 10 also supports frequency bands higher than FR2-1. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz and extending up to 71 GHz. Such high-frequency bands can also be referred to as FR2-2.
[0045] When using frequency bands exceeding 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread OFDM (DFT-S-OFDM) with larger sub-carrier spacing (SCS) can be applied.
[0046] Furthermore, in high-frequency bands like FR2-2, as mentioned above, the increase in inter-carrier phase noise becomes a problem. Therefore, it may be necessary to apply a larger (wider) SCS or a single-carrier waveform.
[0047] The larger the SCS, the shorter the symbol / CP (Cyclic Prefix) period and the slot period (while maintaining a 14 symbol / slot structure). Figure 2 An example of the structure of wireless frames, subframes, and time slots used in wireless communication system 10 is shown.
[0048] While maintaining a 14-symbol / slot structure, a larger (wider) SCS results in a shorter symbol period (and slot period). The time direction can also be referred to as the time domain, symbol period, symbol length, or symbol time, etc. Furthermore, the frequency direction can be referred to as the frequency domain, resource block, subcarrier, BWP (Bandwidth part), etc.
[0049] Frequency resources may include component carriers, subcarriers, resource blocks (RBs), resource block groups (RBGs), and BWPs (bandwidth parts). Time resources may include symbols, time slots, mini-time slots, subframes, radio frames, and DRX (Discontinuous Reception) periods.
[0050] Furthermore, the number of symbols constituting one time slot does not necessarily have to be 14 symbols (e.g., 28, 56 symbols). In addition, the number of time slots in each subframe can vary depending on the SCS.
[0051] In the wireless communication system 10, an SSB (SS / PBCH Block) consisting of a synchronization signal (SS) and a downlink physical broadcast channel (PBCH) can be used.
[0052] The SSB is primarily transmitted periodically from the network for UE200 to perform cell ID and receive timing checks at the start of communication. In NR, the SSB is also used for receiving quality measurements in each cell. The transmission period of the SSB can be specified as 5, 10, 20, 40, 80, 160 milliseconds, etc. Additionally, a transmission period of 20 milliseconds can be assumed for the initial UE200 access.
[0053] Furthermore, various duplex modes can be used in the wireless communication system 10. Specifically, time division duplex (TDD) and frequency division duplex (FDD) can be used. A duplex mode can be explained as a way to achieve simultaneous transmission and reception (duplex communication) of downlink (DL) and uplink (UL).
[0054] Furthermore, in the wireless communication system 10, other duplexing methods that can use both DL and UL simultaneously can be used. Specifically, XDD (Cross Division Duplex) / SBFD (Sub-Band non-overlapping Full Duplex) can be used.
[0055] Figure 3 Examples of TDD and XDD / SBFD structures are shown. Figure 3 As shown, in the TDD specified in 3GPP Releases 15-17, DL, UL or F (flexible: can be set to DL or UL) can be set for each symbol and indicated to UE200.
[0056] On the other hand, in XDD / SBFD, gNB100 can set DL on a specific frequency resource (e.g., subband) and UL on other frequency resources within a specified time T, and indicate this to UE200.
[0057] In XDD / SBFD, both DL and UL can be used simultaneously within a carrier (CC) in the TDD band domain. 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 can also be referred to as a type of full-duplex or FDD full-duplex, or, as described in SBFD, as full-duplex communication in sub-bands (DL / UL).
[0058] In SBFD, frequency resources for DL (DL band domain) and frequency resources for UL (UL band domain) are allocated non-overlapping within the duplex band domain at the same time.
[0059] Specifically, XDD / SBFD works as follows: within a specified time T based on time-division duplex, the DL and UL bands are allocated non-overlappingly in the frequency direction. The DL band can be interpreted as a DL sub-band, and the UL band can be interpreted as a UL sub-band. Hereinafter, XDD / SBFD will be appropriately abbreviated as SBFD.
[0060] (2) Functional block structure of wireless communication system
[0061] Next, the functional block structure of the wireless communication system 10 will be described. Specifically, the functional block structure of the UE200 will be described. Figure 4 This is the function block structure diagram of gNB100 and UE200.
[0062] like Figure 4 As shown, the UE200 includes a wireless signal transceiver unit 210, an amplifier unit 220, a modem unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transceiver unit 260, and a control unit 270.
[0063] In addition, Figure 4 This diagram only shows the main functional blocks associated with the implementation method. It should be noted that the UE200 (gNB100) also has other functional blocks (e.g., a power supply unit, etc.). Furthermore, Figure 4 This shows the functional block structure of UE200. For information on the hardware structure, please refer to [reference needed]. Figure 14 .
[0064] The radio transceiver unit 210 transmits and receives radio signals that comply with NR. The radio transceiver unit 210 can support massive MIMO (Massive MIMO) that generates beams with higher directionality by controlling radio (RF) signals transmitted from multiple antenna elements, carrier aggregation (CA) that uses multiple component carriers (CC), and dual connectivity (DC) that enables simultaneous communication between the UE and two NG-RAN nodes.
[0065] Furthermore, the wireless transceiver unit 210 can transmit and receive wireless signals following Subband Full-Duplex (SBFD) communication mode. SBFD communication mode involves allocating uplink subbands (UL subbands) and downlink subbands (DL subbands) in a non-overlapping frequency direction within a specified time period based on Time Division Duplex (TDD). Of course, the wireless transceiver unit 210 can also support duplex modes such as TDD and FDD (Frequency Division Duplex).
[0066] In particular, in this embodiment, the wireless transceiver unit 210 can transmit uplink signals (specifically, uplink data channels) conforming to SBFD, wherein the SBFD allocates UL subbands or DL subbands in a non-overlapping frequency direction within a predetermined time (e.g., symbol) based on TDD. In this embodiment, the wireless transceiver unit 210 can be configured as a transmitting unit.
[0067] The uplink data channel here can refer to the physical layer data channel in the uplink direction (UL). Specifically, it can refer to PUSCH (Physical Uplink Shared Channel). However, it is not necessarily limited to this channel as long as it is an uplink physical data channel.
[0068] The wireless transceiver unit 210 can transmit the aforementioned uplink signals via a single transceiver point (TRP). Specifically, the wireless transceiver unit 210 can transmit PUSCH, PUCCH, and SRS via a single TRP. A TRP (Transmission Reception Point) can be simply understood as a transmitting antenna. A single TRP can refer to transmitting uplink signals from a geographically located transmitting point.
[0069] The amplification unit 220 is composed of a power amplifier (PA) or a low-noise amplifier (LNA). The amplification unit 220 amplifies the signal output from the modem 230 to a predetermined power level. Furthermore, the amplification unit 220 amplifies the RF signal output from the wireless transceiver unit 210.
[0070] The modem 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication target (gNB100, etc.). The modem 230 can also apply CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) or DFT-S-OFDM (Discrete Fourier Transform - Spread - Frequency Division Multiplexing). Furthermore, DFT-S-OFDM can be used not only for the uplink (UL) but also for the downlink (DL).
[0071] The control signal and reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, as well as processing related to various reference signals transmitted and received by the UE200.
[0072] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, such as control signals from the Radio Resource Control (RRC) layer. Furthermore, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via the predetermined control channel.
[0073] The control signal and reference signal processing unit 240 performs processing of reference signals (RS) such as DMRS (Demodulation Reference Signal) and PTRS (Phase Tracking Reference Signal).
[0074] DMRS is a known reference signal (pilot signal) between the base station and the terminal used for estimating the fading channel used in data demodulation. PTRS is a terminal-specific reference signal used for estimating phase noise, a problem that arises in the high-frequency band.
[0075] In addition to DMRS and PTRS, the reference signal may also include CSI-RS (Channel State Information-Reference Signal), SRS (Sounding Reference Signal), and PRS (Positioning Reference Signal) for location information.
[0076] Furthermore, this embodiment may also include a reference signal for path loss measurement (path loss reference signal: also referred to as PLRS). PLRS can refer to a reference signal (RS) used for path loss estimation of PUSCH, PUCCH, and SRS. For example, CSI-RS, SSB, etc. can be used as PLRS.
[0077] In addition, the channels include control channels and data channels. The control channel may include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, including DCI (Downlink Control Information) containing RA-RNTI (Random Access Radio Network Temporary Identifier)), and PBCH (Physical Broadcast Channel), etc.
[0078] In addition, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data can refer to data transmitted via data channels.
[0079] control signals The reference signal processing unit 240 can send UE200's capability information to the network. In particular, in this embodiment, the control signal... The reference signal processing unit 240 can transmit capability information related to SBFD. This capability information may include, for example, UE capability information related to transmit power control (TPC) when SBFD is applied, which can be transmitted to the network.
[0080] The encoding / decoding unit 250 performs data segmentation / linking and channel encoding / decoding for each predetermined communication target (gNB100 or other gNB).
[0081] Specifically, the encoding / decoding unit 250 divides the data output from the data transceiver unit 260 into predetermined sizes and performs channel coding on the divided data. Furthermore, the encoding / decoding unit 250 decodes the data output from the modem unit 230 and concatenates the decoded data.
[0082] The data transceiver unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transceiver unit 260 performs the assembly / disassembly of PDUs / SDUs at multiple layers (such as the Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers). Furthermore, the data transceiver unit 260 performs error correction and retransmission control based on Hybrid Automatic Repeat Requests (HARQs).
[0083] The control unit 270 controls the functional blocks constituting the UE 200. In particular, in this embodiment, the control unit 270 is capable of performing control related to SBFD. Specifically, the control unit 270 is capable of performing transmit power control (TPC) of the uplink signal when SBFD is applied.
[0084] Specifically, the control unit 270 is capable of performing uplink power control (UL power control) for PUSCH, PUCCH, and SRS. UL power control can be applied independently to SBFD symbols and non-SBFD symbols, as well as independently to PUSCH, PUCCH, and SRS. Such UL power control can also be referred to as separate UL power control.
[0085] The control unit 270 can control the transmission power of PUSCH, PUCCH, and SRS according to the UE behavior specified in 3GPP TS 38.213. Specifically, the control unit 270 can set parameters for controlling the transmission power of PUSCH, PUCCH, and SRS.
[0086] Specifically, the control unit 270 can be set to at least one of the parameters specified in 3GPP TS 38.213, namely p0, α, and the power control adjustment state. Further examples regarding transmit power control will be described later.
[0087] When the control unit 270 transmits an uplink data channel (PUSCH) in the time domain (e.g., symbol) where SBFD is applied, and applies separate UL power control for that uplink data channel, it can perform open-loop transmit power control for each uplink data channel without feedback from the receiver. This open-loop transmit power control can also be referred to as open-loop transmit power control (OLPC).
[0088] Specifically, the independent p0, α, and power control adjustment states used for SBFD can be applied to a semi-static OLPC. Alternatively, an independent p0 for SBFD can be configured for dynamic OLPC. Or, an independent p0-PUSCH-Alpha for SBFD can be configured via ConfiguredGrantConfig (e.g., sbfd-p0-PUSCH-Alpha-r19).
[0089] In this way, the control unit 270 can set the parameters of OLPC semi-statically or dynamically for each uplink data channel (PUSCH).
[0090] When the control unit 270 transmits the uplink data channel (PUSCH) in the time domain (e.g., symbol) where SBFD is applied, and applies separate UL power control for that uplink data channel, it can also perform closed-loop power control based on feedback from the receiver for each uplink data channel. Closed-loop power control can also be referred to as Closed Loop Power Control (CLPC).
[0091] Specifically, the control unit 270 can apply independent CLPC parameters to PUSCH transmission in both SBFD and non-SBFD symbols. For example, parameters such as sbfd-sri-PUSCH-ClosedLoopIndex-r19 (which can be a temporary name, the same below) and sbfd-powerControlLoopToUse-r19 can be applied independently to both SBFD and non-SBFD symbols. In this way, the control unit 270 can perform CLPC in the time domain when SBFD is applied, based on the CLPC information elements (IEs) that are independently set for each uplink data channel.
[0092] Furthermore, the control unit 270 can also transmit the uplink data channel (PUSCH) in the time domain (e.g., symbols) where SBFD is applied, and perform OLPC and CLPC on the uplink data channel when separate UL power control is applied for that uplink data channel. That is, the control unit 270 can perform both OLPC and CLPC when applying separate UL power control for the independent uplink data channel (PUSCH) in both SBFD symbols and non-SBFD symbols. OLPC and CLPC can be performed exclusively on the time axis, but the control unit 270 can also perform OLPC and CLPC in combination according to the indication of parameters related to OLPC or CLPC.
[0093] (3) Operation of wireless communication system
[0094] Next, the operation of the wireless communication system 10 will be explained. Specifically, the operation related to the transmit power control of the uplink data channel (PUSCH) when SBFD is applied will be explained.
[0095] (3.1) Prerequisites and topics
[0096] Regarding SBFD, 3GPP has reached a consensus on "DL / DL usable PRB". "DL / UL usable PRB" refers to a Physical Resource Block (PRB) that can be used as a DL or UL. Specifically, the UL subband frequency resources within an activated UL BWP are called UL usable PRBs, and the DL subband frequency resources within an activated DL BWP are called DL usable PRBs.
[0097] Figure 5 Examples of UL and DL sub-band structures based on SBFD are shown. Figure 5 As shown, UL sub-bands (UL usable PRBs) can be set in UL BWPs, and DL sub-bands (DL usable PRBs) can be set in DL BWPs.
[0098] Figure 6 The formula for calculating the transmit power of the PUSCH is shown. A brief explanation of the PUSCH transmit power control method specified in Chapter 7 of 3GPP TS 38.213 is provided.
[0099] Figure 6 The PUSCH transmit power control shown can be applied to the following situation: The UE uses the parameter set of index j and the PUSCH power control adjustment state of index l to transmit PUSCH in the active UL BWP b of carrier f of serving cell c.
[0100] Specifically, when the UE is instructed to have a first TCI-State or TCI-UL-State and a second TCI-State or TCI-UL-State and set through 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 in the PUSCH transmission opportunity i.
[0101] UE can follow Figure 6 The calculation formula shown calculates the PUSCH transmission power (P_PUSCH,b,f,c,k^(i,j,q_d,l)) for the k-th indicated TCI-State or TCI-UL-State. This calculation formula may include multiple parameters, specifically, it may include p0, α (Alpha), and parameters associated with PLRS.
[0102] P CMAX,f,c,k(i) is the maximum output power set by the UE for the k-th indicated TCI-State or TCI-UL-State.
[0103] The parameter associated with p0 (refer to the dashed box in the figure, the same below) is a parameter consisting of the sum of component (P_O_NOMINAL,PUSCH,f,c)(j) and component P_O_UE_PUSCH,b,f,c)(j), j∈{0,1,...,J-1}.
[0104] The parameter associated with PL is indexed by the UE using the reference signal (RS). d The DL path loss estimate in dB units calculated for the active DL BWP of carrier f in serving cell c.
[0105] Furthermore, 3GPP has reached a consensus that separate UL power control is supported for transmitting PUSCH, PUCCH, and SRS in both SBFD and non-SBFD symbols. This separate UL power control can also be applied to a single TRP scenario.
[0106] However, when SBFD symbols and non-SBFD symbols are available and independent transmit power control is applied for the UL physical channel, the following problem arises: the UE cannot determine the appropriate transmit power control for the UL physical channel, especially the PUSCH (uplink data channel), which is also used for scheduling grants and may have a higher transmission frequency compared to PUCCH.
[0107] That is, the UE needs to appropriately support separate UL power control for PUSCH transmission in both SBFD and non-SBFD symbols, based on the framework of PUSCH spatial information.
[0108] (3.2) Action Summary
[0109] The following action examples can also be performed under the following preconditions.
[0110] • Single TRP scenario
[0111] Instead of setting a single (unified TCI state) for multiple UL / DL channels (including PUSCH), each channel has its own independent TCI-State.
[0112] • Do not apply the spatial filter of UL to SBFD symbols and non-SBFD symbols.
[0113] However, these prerequisites are not required. For example, this action example can be performed even when multiple TRP scenes or UL spatial filters are applied.
[0114] Specifically, the following actions can be performed.
[0115] • (Action Example 1): Support independent open-loop transmit power control (OLPC) parameters for PUSCH transmission in SBFD symbols and non-SBFD symbols.
[0116] (Action Example 1-1): For a semi-static OLPC, the independent p0 or α
[0117] • (Option 1-1): Set a separate p0-AlphaSets in PUSCH-PowerControl (e.g., sbfd-p0-AlphaSets-r19) or a separate sri-P0-PUSCH-AlphaSetId in SRI-PUSCH-PowerControl (e.g., sbfd-sri-P0-PUSCH-AlphaSetId-r19).
[0118] • (Options 1-2): Set the independent p0 or α in P0-PUSCH-AlphaSet (e.g., sbfd-p0-r19 or sbfd-alpha-r19).
[0119] (Action Example 1-2): Independent p0 for dynamic OLPC
[0120] • (Option 2-1): Set an independent p0-PUSCH-SetList via PUSCH-PowerControl (e.g., sbfd-p0-PUSCH-SetList-r19).
[0121] • (Option 2-2): Set a separate p0-List via P0-PUSCH-Set (e.g., sbfd-p0-List-r19).
[0122] • (Action Example 1-3): Set an independent p0-PUSCH-Alpha (e.g., sbfd-p0-PUSCH-Alpha-r19) through ConfiguredGrantConfig.
[0123] • (Action Example 2): Support independent closed-loop transmit power control (CLPC) parameters for PUSCH transmission in SBFD and non-SBFD symbols.
[0124] • (Action Example 2-1): Set an independent sri-PUSCH-ClosedLoopIndex via SRI-PUSCH-PowerControl (e.g., sbfd-sri-PUSCH-ClosedLoopIndex-r19).
[0125] • (Action Example 2-2): Set an independent powerControlLoopToUse using ConfiguredGrantConfig (e.g., sbfd-powerControlLoopToUse-r19).
[0126] • (Action Example 3): Support independent open-loop transmit power control (OLPC) parameters and independent closed-loop transmit power control (CLPC) parameters for PUSCH transmission in SBFD and non-SBFD symbols.
[0127] • (Action Example 3-1): Configure an independent PUSCH-PowerControl via PUSCH-Config (e.g., sbfd-PUSCH-PowerControl-r19).
[0128] • (Action Example 3-2): Configure a separate sri-PUSCH-MappingToAddModList (e.g., sbfd-sri-PUSCH-MappingToAddModList-r19) via PUSCH-PowerControl.
[0129] • (Action Example 3-3): A combination of any option from Action Example 1 and any option from Action Example 2.
[0130] In addition, action examples 1-1, 1-2, 2-1 and action examples 3-1 and 3-2 can be applied to DG (dynamic grant) PUSCH, and action examples 1-3 and 2-2 can be applied to CG (configured grant) PUSCH.
[0131] Figure 7 This shows a timing example related to PUSCH's UL power control. For example... Figure 7 As shown, TCI-State can be indicated to the UE via MAC-CE.
[0132] When SBFD is applied, the UE can perform UL power control of PUSCH based on this TCI-State.
[0133] The UE can send a PUSCH with the transmission power adjusted by the UL power control to the network (gNB).
[0134] (3.3) Example 1 of the action
[0135] (3.3.1) Action Example 1-1: Independent p0 or α for semi-static OLPC
[0136] Figure 8 This represents a structural example of PUSCH-PowerControl, etc., as shown in action example 1-1. For example... Figure 8 (Refer to the underlined part) As shown, independent open-loop transmit power control (OLPC) parameters can be supported for PUSCH transmission in SBFD symbols and non-SBFD symbols.
[0137] • (Option 1-1): You can set a separate p0-AlphaSets in PUSCH-PowerControl (e.g., sbfd-p0-AlphaSets-r19) or a separate sri-P0-PUSCH-AlphaSetId in SRI-PUSCH-PowerControl (e.g., sbfd-sri-P0-PUSCH-AlphaSetId-r19).
[0138] • (Options 1-2): You can set an independent p0 or α in P0-PUSCH-AlphaSet (e.g., sbfd-p0-r19 or sbfd-alpha-r19).
[0139] When using option 1-1 for PUSCH transmission in non-SBFD symbols, the UE can be configured in the traditional mode (as in previous 3GPP specifications), i.e., based on p0-AlphaSets and sri-P0-PUSCH-AlphaSetId, to determine P... O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0140] When the DCI format contains an SRI (SRS resource indicator) field, the UE can obtain the mapping between the set of SRI field values of the DCI format from the SRI-PUSCH-PowerControlId of SRI-PUSCH-PowerControl, and the set of indices provided by sri-P0-PUSCH-AlphaSetId of the P0-PUSCH-AlphaSet set mapped to p0-AlphaSets, and determine the P that is mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0141] If the DCI format does not include an SRI field, the UE can determine the P from the value of the first P0-PUSCH-AlphaSet in the p0-AlphaSets. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0142] When PUSCH is transmitted in the SBFD symbol of application option 1-1, if sbfd-p0-AlphaSets-r19 is set / exists in PUSCH-PowerControl, sbfd-sri-P0-PUSCH-AlphaSetId-r19 is set / exists in SRI-PUSCH-PowerControl, and the DCI format contains an SRI field, the UE can obtain the mapping between the set of SRI field values of the DCI format from SRI-PUSCH-PowerControl's SRI-PUSCH-PowerControlId and the set of indices provided by sbfd-sri-P0-PUSCH-AlphaSetId-r19, which is mapped to the P0-PUSCH-AlphaSet set of sbfd-p0-AlphaSets-r19, and determine the P value mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0143] If the DCI format does not include an SRI field, the UE can determine the P based on the value of the first P0-PUSCH-AlphaSet in sbfd-p0-AlphaSets-r19. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0144] If sbfd-p0-AlphaSets-r19 is configured / exists in PUSCH-PowerControl, but sbfd-sri-P0-PUSCH-AlphaSetId-r19 is not configured / exists in SRI-PUSCH-PowerControl, and the DCI format contains an SRI field, the UE can obtain a mapping between a series of values of the SRI field of the DCI format from the SRI-PUSCH-PowerControl's SRI-PUSCH-PowerControlId and a series of indices provided by sri-P0-PUSCH-AlphaSetId, which is mapped to the P0-PUSCH-AlphaSets-r19, and determine the P that is mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0145] If the DCI format does not include an SRI field, the UE can determine the P based on the value of the first P0-PUSCH-AlphaSet in sbfd-p0-AlphaSets-r19. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0146] If sbfd-p0-AlphaSets-r19 is not set / exists in PUSCH-PowerControl, but sbfd-sri-P0-PUSCH-AlphaSetId-r19 is set / exists in SRI-PUSCH-PowerControl, and the DCI format contains an SRI field, the UE can obtain the mapping between a series of values of the SRI field of the DCI format from the SRI-PUSCH-PowerControl's SRI-PUSCH-PowerControlId and a series of indices provided by sbfd-sri-P0-PUSCH-AlphaSetId-r19, and determine the P value mapped to the SRI field. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0147] If the DCI format does not include an SRI field, the UE can determine the P from the value of the first P0-PUSCH-AlphaSet in the p0-AlphaSets. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0148] If neither sbfd-p0-AlphaSets-r19 nor sbfd-sri-P0-PUSCH-AlphaSetId-r19 is set or exists, the UE can perform any of the following actions.
[0149] • (Alt.1): P can be determined based on previous p0-AlphaSets and sri-P0-PUSCH-AlphaSetId. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0150] • (Alt.2): Default values can also be applied. For example, P can also be applied. O_UE_PUSCH,b,f,c (j) default value 0, α b,f,c The default value for (j) is 1.
[0151] In the case of DG PUSCH transmission in non-SBFD symbolic applications of options 1-2, the UE can determine P based on the values of p0 and / or α in P0-PUSCH-AlphaSet. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0152] In the case of DG PUSCH transmission in SBFD symbols, the UE can determine it based on P0-PUSCH-AlphaSet as in previous 3GPP specifications. When sbfd-p0-r19 and / or sbfd-alpha-r19 are set by the determined P0-PUSCH-AlphaSet, P... O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) can be determined based on sbfd-p0-r19 and / or sbfd-alpha-r19 of P0-PUSCH-AlphaSet.
[0153] If sbfd-p0-r19 or sbfd-alpha-r19 is not set by the determined P0-PUSCH-AlphaSet, the UE may perform any of the following actions.
[0154] • (Alt.1): P O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j) can be determined based on p0 or α of P0-PUSCH-AlphaSet.
[0155] • (Alt.2): Default values can also be applied. For example, P can also be applied. O_UE_PUSCH,b,f,c (j) default value 0, α b,f,c The default value for (j) is 1.
[0156] (3.3.2) Action Examples 1-2
[0157] Figure 9 This represents a structural example of PUSCH-PowerControl, etc., as shown in action examples 1-2. For example... Figure 9 (See the underlined section) As shown, parameters related to independent p0 settings for dynamic OLPC can be supported.
[0158] • (Option 2-1): Set an independent p0-PUSCH-SetList via PUSCH-PowerControl (e.g., sbfd-p0-PUSCH-SetList-r19).
[0159] • (Option 2-2): Set a separate p0-List via P0-PUSCH-Set (e.g., sbfd-p0-List-r19).
[0160] In PUSCH transmission within non-SBFD symbolic elements in application option 2-1, the UE can transmit PUSCH when the value of the OLPC field is "1", "01", or "10". O_UE_PUSCH,b,f,c The value of (j) is set to the traditional method, that is, determined based on p0-PUSCH-SetList.
[0161] If the value of the OLPC field is "0" or "00", the UE can... O_UE_PUSCH,b,f,c The value of (j) is set in the traditional way, that is, determined based on p0-AlphaSets.
[0162] In the PUSCH transmission within the SBFD symbol of application option 2-1, 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 can determine P based on sbfd-p0-PUSCH-SetList-r19. O_UE_PUSCH,b,f,c The value of (j).
[0163] When the value of the OLPC field is "1" or "01", the UE can transmit P. O_UE_PUSCH,b,f,c The value of (j) is determined as the first value of the P0-PUSCH-Set with the smallest P0-PUSCH-SetId in sbfd-p0-PUSCH-SetList-r19.
[0164] When the value of the OLPC field is "10", the UE can... O_UE_PUSCH,b,f,cThe value of (j) is determined as the second value of the P0-PUSCH-Set with the smallest P0-PUSCH-SetId of sbfd-p0-PUSCH-SetList-r19.
[0165] If sbfd-p0-PUSCH-SetList-r19 is not set (does not exist) in PUSCH-PowerControl, the UE can perform any of the following actions.
[0166] (Alt.1): The UE can determine P based on the existing p0-PUSCH-SetList. O_UE_PUSCH,b,f,c The value of (j) can be set to be the same as the PUSCH transmission case in non-SBFD symbols.
[0167] • (Alt.2): Default values can also be applied. For example, P can also be applied. O_UE_PUSCH,b,f,c The default value for (j) is 0.
[0168] • (Alt. 3): Action Example 1-1 can also be applied. That is, the UE can also determine P based on sbfd-sri-P0-PUSCH-AlphaSetId-r19 and / or sbfd-p0-AlphaSets-r19. O_UE_PUSCH,b,f,c The value of (j).
[0169] When the OLPC field value is "0" or "00", the UE can be set to the traditional method, that is, to determine P based on p0-AlphaSets. O_UE_PUSCH,b,f,c The value of (j). In this case, Action Example 1-1 can also be applied. That is, the UE can replace sri-P0-PUSCH-AlphaSetId with sbfd-sri-P0-PUSCH-AlphaSetId-r19, or replace p0-AlphaSets with sbfd-p0-AlphaSets-r19 to determine p0.
[0170] In PUSCH transmission within non-SBFD symbolic elements in application option 2-2, the UE can transmit PUSCH when the OLPC field value is "1", "01", or "10". O_UE_PUSCH,b,f,c The value of (j) is set to the traditional method, that is, determined based on the value of p0-List-r16 of P0-PUSCH-Set.
[0171] When the OLPC field value is "0" or "00", the UE can... O_UE_PUSCH,b,f,c The value of (j) is set in the traditional way, that is, determined based on p0-AlphaSets.
[0172] In the PUSCH transmission within the SBFD symbol of application option 2-2, if the OLPC field value is "1", "01", or "10", and sbfd-p0-List-r19 is set / exists in P0-PUSCH-Set, the UE can determine P based on sbfd-p0-List-r19. O_UE_PUSCH,b,f,c The value of (j).
[0173] When the OLPC field value is "1" or "01", the UE can... O_UE_PUSCH,b,f,c The value of (j) is determined by the first value of sbfd-p0-List-r19 of the P0-PUSCH-Set with the lowest P0-PUSCH-SetId.
[0174] When the OLPC field value is "10", the UE can... O_UE_PUSCH,b,f,c The value of (j) is determined as the second value of sbfd-p0-List-r19 of the P0-PUSCH-Set with the lowest P0-PUSCH-SetId.
[0175] If sbfd-p0-List-r19 is not set (does not exist) in P0-PUSCH-Set, the UE can perform any of the following actions.
[0176] • (Alt.1): The UE can be set to the traditional method, where P is determined based on the value of p0-List-r16 of P0-PUSCH-Set. O_UE_PUSCH,b,f,c The value of (j) can be set to be the same as the PUSCH transmission case in non-SBFD symbols.
[0177] • (Alt.2): Default values can also be applied. For example, P can also be applied. O_UE_PUSCH,b,f,c The default value for (j) is 0.
[0178] • (Alt. 3): Action Example 1-1 can also be applied. That is, the UE can also determine P based on sbfd-sri-P0-PUSCH-AlphaSetId-r19 and / or sbfd-p0-AlphaSets-r19. O_UE_PUSCH,b,f,c The value of (j).
[0179] When the OLPC field value is "0" or "00", the UE can be set to the traditional method, that is, to determine P based on p0-AlphaSets. O_UE_PUSCH,b,f,cThe value of (j) can also be applied in this case. That is, the UE can replace sri-P0-PUSCH-AlphaSetId with sbfd-sri-P0-PUSCH-AlphaSetId-r19, and / or replace p0-AlphaSets with sbfd-p0-AlphaSets-r19 to determine p0.
[0180] Furthermore, in options 2-1 / 2-2, a separate OLPC field of the DCI format can be used to indicate the OLPC of PUSCH for both SBFD and non-SBFD symbols. In the case of PUSCH transmission in SBFD symbols, the SBFD OLPCI field can be applied. In the case of PUSCH transmission in non-SBFD symbols, the non-SBFD OLPCI field can be applied.
[0181] Independent bits of the OLPC field in the DCI format can be used to indicate the OLPC of PUSCH for both SBFD and non-SBFD symbols. For example, in the case of PUSCH transmission in SBFD symbols, the LSB / MSB (most significant bit / least significant bit) of the OLPC field can be applied. In the case of PUSCH transmission in non-SBFD symbols, the MSB / LSB of the OLPC field can be applied.
[0182] (3.3.3) Action Examples 1-3
[0183] Figure 10 This represents the structure instance of ConfiguredGrantConfig for actions 1-3. For example... Figure 10 (Refer to the underlined section) As shown, the independent p0-PUSCH-Alpha (e.g., sbfd-p0-PUSCH-Alpha-r19) can be set via ConfiguredGrantConfig.
[0184] Additionally, if the CG PUSCH is restricted to SBFD symbols only, or to non-SBFD symbols only, the UE may not assume that sbfd-p0-PUSCH-Alpha-r19 is configured / existing via ConfiguredGrantConfig.
[0185] When the CG PUSCH can be transmitted in both SBFD and non-SBFD symbols, the UE can perform the following actions.
[0186] In the CG PUSCH transmission within the SBFD symbol, if sbfd-p0-PUSCH-Alpha-r19 is set (existing) in ConfiguredGrantConfig, the UE can determine P based on sbfd-p0-PUSCH-Alpha-r19. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0187] If sbfd-p0-PUSCH-Alpha-r19 is not set (or does not exist) in ConfiguredGrantConfig, the UE can perform any of the following actions.
[0188] • (Alt.1): P can be determined based on p0-PUSCH-Alpha. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0189] • (Alt.1): Default values can also be applied. For example, P can also be applied. O_UE_PUSCH,b,f,c (j) default value 0, α b,f,c The default value for (j) is 1.
[0190] In the case of CG PUSCH transmission in non-SBFD symbolic form, the UE can determine P based on p0-PUSCH-Alpha. O_UE_PUSCH,b,f,c (j) and α b,f,c The value of (j).
[0191] (3.4) Example 2 of the action
[0192] In this example, independent closed-loop transmit power control (CLPC) parameters are supported for PUSCH transmission in both SBFD and non-SBFD symbols.
[0193] • (Action Example 2-1): Set an independent sri-PUSCH-ClosedLoopIndex via SRI-PUSCH-PowerControl (e.g., sbfd-sri-PUSCH-ClosedLoopIndex-r19).
[0194] • (Action Example 2-2): Set an independent powerControlLoopToUse using ConfiguredGrantConfig (e.g., sbfd-powerControlLoopToUse-r19).
[0195] Additionally, if the CG PUSCH is restricted to SBFD symbols only, or to non-SBFD symbols only, the UE may not assume that sbfd-powerControlLoopToUse-r19 is set / existing via ConfiguredGrantConfig.
[0196] Figure 11 This represents the structure example of SRI-PUSCH-PowerControl and ConfiguredGrantConfig in action example 2. For example... Figure 11 (Refer to the underlined section) As shown, you can use sbfd-sri-PUSCH-ClosedLoopIndex-r19 and sbfd-powerControlLoopToUse-r19.
[0197] (3.4.1) Action Example 2-1
[0198] In the case of PUSCH transmission in non-SBFD symbols, the UE can set PUSCH power control adjustment state l to the traditional mode, that is, to determine based on the traditional sri-PUSCH-ClosedLoopIndex of SRI-PUSCH-PowerControl.
[0199] When the DCI format includes an SRI field, the UE can obtain the mapping between the set of SRI field values of the DCI format and the PUSCH power control adjustment state value provided by sri-PUSCH-ClosedLoopIndex from SRI-PUSCH-PowerControlId, and determine the value to be mapped to the SRI field.
[0200] If the SRI field is not included in the DCI format, the value of PUSCH power control adjustmentstate l can be set to 0.
[0201] In PUSCH transmission within SBFD symbols, the DCI format includes an SRI field. If SRI-PUSCH-PowerControl is set or sbfd-sri-PUSCH-ClosedLoopIndex-r19 exists, the UE can obtain the mapping between the set of SRI field values for the DCI format and the value of the PUSCH power control adjustment state provided by sbfd-sri-PUSCH-ClosedLoopIndex-r19 from the SRI-PUSCH-PowerControlId, and determine the value mapped to the SRI field.
[0202] If sbfd-sri-PUSCH-ClosedLoopIndex-r19 is not set (or does not exist) in SRI-PUSCH-PowerControl, the UE can perform any of the following actions.
[0203] • (Alt.1): The UE determines the value of PUSCH power control adjustment state l based on sri-PUSCH-ClosedLoopIndex of SRI-PUSCH-PowerControl. That is, it can transmit the same DG PUSCH as in non-SBFD symbols.
[0204] • (Alt.2): Default values can also be applied. For example, the default value of 0 / 1 for PUSCH power control adjustment state l can also be applied. In addition, the default value (l = 0 / 1) can also be applied if the SRI field is not included in the DCI format.
[0205] (3.4.2) Action Example 2-2
[0206] When CG PUSCH can be transmitted via SBFD and non-SBFD symbols, and CG PUSCH is transmitted within non-SBFD symbols, the value of PUSCH power control adjustment state l can be provided by powerControlLoopToUse. During CG PUSCH transmission within SBFD symbols, if sbfd-powerControlLoopToUse-r19 is set / exists in ConfiguredGrantConfig, the value of PUSCH power control adjustment state l can be provided by sbfd-powerControlLoopToUse-r19.
[0207] If sbfd-powerControlLoopToUse-r19 is not set or does not exist in ConfiguredGrantConfig, the UE may perform any of the following actions.
[0208] • (Alt.1): The value of PUSCH power control adjustment state l can be provided by powerControlLoopToUse.
[0209] • (Alt.1): The default value of 0 / 1 for PUSCH power control adjustment state l can also be applied.
[0210] (3.5) Action Example 3
[0211] (3.5.1) Action Example 3-1
[0212] Figure 12 This represents the structure example of PUSCH-Config in action example 3-1. For example... Figure 12 (Refer to the underlined section) As shown, a separate PUSCH-PowerControl (e.g., sbfd-PUSCH-PowerControl-r19) can be configured via PUSCH-Config.
[0213] In the case of PUSCH transmission in non-SBFD symbols, the UE can, based on PUSCH-PowerControl, transmit P... O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l are determined in the conventional manner. As mentioned above, the conventional manner can refer to conforming to existing 3GPP specifications.
[0214] During PUSCH transmission within SBFD symbols, when sbfd-PUSCH-PowerControl-r19 is set in PUSCH-Config, the UE can determine P based on sbfd-PUSCH-PowerControl-r19. O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l.
[0215] If sbfd-PUSCH-PowerControl-r19 is not set in PUSCH-Config, or if a parameter with a specific value (e.g., p0, alpha, closedLoopIndex) is not set in sbfd-PUSCH-PowerControl-r19, the UE may perform any of the following actions.
[0216] • (Alt.1): The UE can determine specific parameter values based on the traditional PUSCH-PowerControl (e.g., P...). O_UE_PUSCH,b,f,c (j), α b,f,c (j) or the value of PUSCH power control adjustment state l).
[0217] • (Alt.2): Default values can also be applied. For example, P can also be applied. O_UE_PUSCH,b,f,c (j) default value 0, α b,f,c The default value of (j) is 1, and the default value of PUSCH power control adjustment state l is 0 / 1.
[0218] (3.5.2) Action Example 3-2
[0219] Figure 13 This represents the structure example of PUSCH-PowerControl in action example 3-2. For example... Figure 13 (Refer to the underlined section) As shown, a separate sri-PUSCH-MappingToAddModList can be set in PUSCH-PowerControl (e.g., sbfd-sri-PUSCH-MappingToAddModList-r19).
[0220] In the case of PUSCH transmission in non-SBFD symbols, the UE can be set to the traditional mode, i.e., the traditional SRI-PUSCH-PowerControl based on sri-PUSCH-MappingToAddModList, to determine P. O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l.
[0221] In the PUSCH transmission within the SBFD symbol, if sbfd-sri-PUSCH-MappingToAddModList-r19 is set (existing) in PUSCH-PowerControl, the UE can determine P based on sbfd-sri-PUSCH-MappingToAddModList-r19. O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l, therefore, the mapping between the set of SRI field values in the DCI format is obtained based on the SRI-PUSCH-PowerControlId of sbfd-SRI-PUSCH-PowerControl-r19 of sbfd-sri-PUSCH-MappingToAddModList-r19.
[0222] If sbfd-sri-PUSCH-MappingToAddModList-r19 is not set (does not exist) in PUSCH-Config, or if a parameter for a specific value (e.g., p0, alpha, closedLoopIndex) is not set (does not exist) in SRI-PUSCH-PowerControl of sbfd-sri-PUSCH-MappingToAddModList-r19, the UE may perform any of the following actions.
[0223] • (Alt.1): The UE can determine specific parameter values based on the previous sri-PUSCH-MappingToAddModList (e.g., P O_UE_PUSCH,b,f,c (j), α b,f,c (j) and the value of PUSCH power control adjustment state l.
[0224] • (Alt.2): Default values can also be applied. For example, P can also be applied. O_UE_PUSCH,b,f,c (j) default value 0, αb,f,c The default value of (j) is 1, and the default value of PUSCH power control adjustment state l is 0 / 1.
[0225] (3.6) Example of modification
[0226] In the above action examples, the following changes can also be applied. For example, the options of action example 1-1 / 1-2 / 1-3 can also be combined with the options of action example 2. Action example 3-2 can be combined with the options of action example 1-1 / 1-2 and / or action example 2-1.
[0227] For example, in the case of PUSCH transmission in SBFD symbols, if Action Example 1-1 / 1-2 and / or Action Example 2-1 are applied, the mapping of the SRI-PUSCH-PowerControlId from SRI-PUSCH-PowerControl between sets of SRI field values in DCI format can be replaced by the mapping of the SRI-PUSCH-PowerControlId from sbfd-SRI-PUSCH-PowerControl-r19 between sets of SRI field values in DCI format.
[0228] The total number of power control adjustment states for PUSCH can be greater than two. For example, two power control adjustment states for SBFD and two power control adjustment states for non-SBFD can be set separately.
[0229] In the cases of Action Example 2 and Action Example 3, the value of closedLoopIndex can be one of the following values.
[0230] (Alt.1) The value of closedLoopIndex for SBFD / non-SBFD can be mapped to the index of the power control adjustment state for SBFD / non-SBFD only.
[0231] For example, indices can be set for two power control adjustment states used by SBFD and two power control adjustment states not used by SBFD. Candidate values for the closedLoopIndex used by SBFD can be set to index#0 and index#1, respectively, and mapped to the power control adjustment states used by SBFD. Candidate values for the closedLoopIndex used by SBFD can be set to index#0 and index#1, respectively, and mapped to the power control adjustment states not used by SBFD.
[0232] • (Alt.2): The value of closedLoopIndex for SBFD / non-SBFD can be mapped to an index within the power control adjustment state for SBFD and non-SBFD.
[0233] For example, the indices of the two power control adjustment states used by SBFD and the two power control adjustment states not used by SBFD can be set. The candidate values of closedLoopIndex can be set to any one of index#0, index#1, index#2, index#3, and index#4.
[0234] Alternatively, you can set only one closedLoopIndex (i.e., without setting a separate closedLoopIndex for SBFD as in Action Examples 2 and 3) and map it to the power control adjustment state for SBFD / non-SBFD respectively.
[0235] Alternatively, a maximum of three power control adjustment states can be set, with a maximum of two power control adjustment states used for non-SBFD purposes, and a maximum of one power control adjustment state set independently for SBFD purposes. In this case, it is not necessary to set the closedLoopIndex of the SBFD for Action Example 2 or Action Example 3 independently. In the case of PUSCH transmission in SBFD symbols, the existing index of the power control adjustment state of SBFD can be applied.
[0236] (3.7) UE capabilities
[0237] Regarding SBFD, the UE can report to the network whether it has the following capabilities (UE Capability Information). This UE Capability Information can be specified for each UE, each frequency range (FR), and each frequency channel (FC). In addition, the signaling and settings of RRC used to report this UE Capability Information can also be specified.
[0238] • Supports independent UL power control for PUSCH transmission in both SBFD and non-SBFD symbols.
[0239] • Supports independent setting of p0-AlphaSets in SBFD of PUSCH-PowerControl
[0240] • Supports independent setting of sri-P0-PUSCH-AlphaSetId in SRI-PUSCH-PowerControl's SBFD.
[0241] • Supports independent setting of p0 and alpha in SBFD within P0-PUSCH-AlphaSet.
[0242] • Supports independent setting of p0-PUSCH-SetList in SBFD within PUSCH-PowerControl.
[0243] • Supports independent configuration of the p0-List of SBFD in P0-PUSCH-Set
[0244] • Supports independent setting of sri-PUSCH-ClosedLoopIndex in SBFD of SRI-PUSCH-PowerControl.
[0245] • Supports independent settings for powerControlLoopToUse in SBFD within ConfiguredGrantConfig.
[0246] • Supports independent settings for SBFD PUSCH-PowerControl
[0247] • Supports independent settings for sri-PUSCH-MappingToAddModList in SBFD for PUSCH-PowerControl.
[0248] • Supports a maximum number of PUSCH power control adjustment states
[0249] • The maximum number of independent PUSCH power control adjustment states supported for SBFD symbols
[0250] Based on the above example, when SBFD is applied, even if a separate OLPC or CLPC is applied to the PUSCH, the UE can still perform OLPC or CLPC for each PUSCH. Therefore, even when SBFD symbols and non-SBFD symbols can be used, and independent transmit power control is applied to the UL physical channel, the UE can still perform appropriate transmit power control for uplink data channels such as PUSCH.
[0251] (4) Other implementation methods
[0252] The above describes the implementation methods, but the present invention is not limited to the description of these implementation methods. It is obvious to those skilled in the art that various modifications and improvements can be made.
[0253] For example, in the above implementation, the term "sub-band" is used, but a sub-band can be simply referred to as a band, or it can be called an auxiliary band, a preparatory band, or other similar terms. Additionally, XDD / SBFD can be a temporary designation, or it can be referred to as other similar terms as described above.
[0254] Furthermore, in the above description, the terms configure, activate, update, indicate, enable, specify, and select can be interchanged. Similarly, the terms link, associate, correspond, and map can be interchanged, as can allocate, assign, monitor, and map.
[0255] Furthermore, specific, dedicated, UE specific, and UE dedicated can be used interchangeably. Similarly, common, shared, group-common, UE common, and UE shared can also be used interchangeably.
[0256] In this disclosure, the terms "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", "beamwidth", "beam angle", "antenna", "antenna element", and "panel" are used interchangeably.
[0257] Furthermore, the block structure diagram used in the description of the above embodiments ( Figure 4 The term "functional block" represents a module based on function. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within one or more of the aforementioned devices.
[0258] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that performs the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.
[0259] Furthermore, the aforementioned gNB100 and UE200 (the device) can also function as a computer for processing the wireless communication method disclosed herein. Figure 14 This is a diagram illustrating an example of the hardware structure of the device. (As shown...) Figure 14As shown, the device can also be configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.
[0260] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of this device can be configured as either a device comprising one or more of the illustrated components, or a device without any components.
[0261] The functional blocks of the device (refer to) Figure 4 This can be achieved through any hardware element or combination of hardware elements in the computer device.
[0262] Furthermore, the functions of the device are implemented by reading predetermined software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication of communication device 1004 or controls at least one of reading and writing data in memory 1002 and storage device 1003.
[0263] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc.
[0264] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one direction of memory 1002 in the storage device 1003 and the communication device 1004, and performs various processes accordingly. The program is used to cause the computer to perform at least a portion of the actions described in the above embodiments. Moreover, the various processes described above can be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 can also be implemented using more than one chip. Additionally, the program can be transmitted from a network via a telecommunications line.
[0265] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of the following: Read Only Memory (ROM), Erasable Programmable Memory (EPROM), Electrically Erasable Programmable Memory (EEPROM), Random Access Memory (RAM). The memory 1002 may be referred to as a register, cache memory, main memory (main storage device), etc. The memory 1002 may store programs (program code), software modules, etc., capable of executing the methods involved in one embodiment of this disclosure.
[0266] Storage device 1003 is a computer-readable recording medium, and may be composed of at least one of the following: optical discs such as CD-ROM (Compact Disc ROM), hard disk drives, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. Storage device 1003 may also be referred to as an auxiliary storage device. The aforementioned recording medium may be, for example, a database, server, or other suitable media that includes at least one of memory 1002 and storage device 1003.
[0267] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. For example, it may also be called a network device, network controller, network card, communication module, etc.
[0268] The communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of frequency division duplex (FDD) and time division duplex (TDD).
[0269] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).
[0270] Furthermore, devices such as processor 1001 and memory 1002 are connected via bus 1007 for communicating information. Bus 1007 can be configured as a single bus or as different buses between devices.
[0271] Furthermore, the device can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), which can be used to implement some or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.
[0272] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through 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 combinations thereof. In addition, RRC signaling may also be referred to as RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.
[0273] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (x being, 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 The system may include at least one of 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on these systems. Furthermore, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).
[0274] The processing steps, timing, and processes described in this disclosure can be rearranged without contradiction. For example, the elements of various steps are indicated using an illustrative order in the methods described in this disclosure, but are not limited to the specific order indicated.
[0275] In this disclosure, certain actions performed by the base station are sometimes also performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having a base station, it is obvious that various actions performed to communicate with a terminal can be performed by at least one of the base station and other network nodes besides the base station (e.g., considering an MME or S-GW, but not limited to these). The above illustration depicts a single other network node besides the base station, but it can also be a combination of multiple other network nodes (e.g., an MME and an S-GW).
[0276] Information and signals (such as information) can be output from higher (or lower) layers to lower (or higher) layers. They can also be input or output through multiple network nodes.
[0277] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input and output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.
[0278] The determination can be made by the value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparing numerical values (e.g., comparing with a predetermined value).
[0279] The various forms / implementations described in this disclosure can be used individually or in combination, and can be switched depending on the execution. Furthermore, the notification of predetermined information (e.g., a notification of "It is X") is not limited to being explicit, but can also be implicit (e.g., without notification of the predetermined information).
[0280] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.
[0281] In addition, software, commands, and information can also be sent and received via transmission media. For example, when using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.) to send software from a webpage, server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission media.
[0282] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description as a whole can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.
[0283] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.
[0284] The terms “system” and “network” as used in this disclosure are used interchangeably.
[0285] Furthermore, the information, parameters, etc., described in this disclosure may be represented using absolute values, relative values to predetermined values, or other corresponding information. For example, wireless resources may be indicated using indexes.
[0286] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters may sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any appropriate name, and therefore the various names assigned to these channels and information elements are non-limiting in any respect.
[0287] In this disclosure, the terms "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.
[0288] 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 also provide communication services through the base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0289] Terms such as “cell” or “sector” refer to a portion or the entire coverage area of at least one of the base stations and base station subsystems that provide communication services within that coverage area.
[0290] In this disclosure, the base station sending information to the terminal can also be replaced by the base station instructing the terminal on information-based control / actions.
[0291] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably.
[0292] For mobile stations, those skilled in the art sometimes also use the following terms: 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, handheld device, user agent, mobile client, client, or some other appropriate terms.
[0293] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Additionally, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. This mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.
[0294] Furthermore, the base station in this disclosure can also be replaced by a mobile station (user terminal, hereinafter the same). For example, various forms / implementations of this disclosure can also be applied to structures that replace communication between the base station and the mobile station with communication between multiple mobile stations (e.g., also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the structure can also be configured such that the mobile station has the functions of the base station. In addition, terms such as "uplink" and "downlink" can also be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel (or side link).
[0295] Similarly, the mobile station in this disclosure can be replaced by a base station. In this case, the base station can also be configured to have the functions of a mobile station.
[0296] A radio frame can consist of one or more frames in the time domain. Each frame in the time domain is called a subframe. A subframe can also consist of one or more time slots in the time domain. A subframe can have a fixed duration (e.g., 1 ms) independent of the parameter set (numerology).
[0297] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.
[0298] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.
[0299] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.
[0300] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.
[0301] For example, a single subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a single time slot or a single mini-time slot can also be called a TTI. That is, at least one of a subframe or TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Furthermore, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.
[0302] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.
[0303] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than the TTI.
[0304] Furthermore, when one time slot or one mini time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can become the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit of the schedule can be controlled.
[0305] A TTI with a duration of 1ms is also called a normal TTI (TTI in LTE Rel.8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.
[0306] Additionally, a long TTI (e.g., a normal TTI, a subframe, etc.) can be replaced with a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can be replaced with a TTI with a duration of less than a long TTI but more than 1 ms.
[0307] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.
[0308] Furthermore, the temporal domain of an RB can contain one or more symbols, which can be a single time slot, a single mini-time slot, a single subframe, or the length of a single TTI. A single TTI, a single subframe, etc., can each be composed of one or more resource blocks.
[0309] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.
[0310] Furthermore, a resource block can consist of one or more resource elements (REs). For example, one RE can be a radio resource area consisting of one subcarrier and one symbol.
[0311] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) represents a subset of contiguous common resource blocks (RBs) used for a specific parameter set on a given carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.
[0312] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within a single carrier.
[0313] At least one of the configured BWPs can be active, and the scenario of the UE transmitting or receiving predetermined signals / channels outside of the active BWP is not considered. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."
[0314] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc., can be varied in many ways.
[0315] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.
[0316] The reference signal can be simply called the Reference Signal (RS), or, depending on the standard applied, the pilot.
[0317] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least".
[0318] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.
[0319] Any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to "first" and "second" elements do not imply that only two elements can be used there, or that in some form the first element must precede the second element.
[0320] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.
[0321] In this disclosure, for example, in cases where articles are added through translation, such as in English (a, an, and the), this disclosure also includes cases where the noun following these articles is in a plural form.
[0322] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in storage), which are considered as actions of "determining" or "determining." Additionally, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.
[0323] In this disclosure, the phrase "A and B are different" can mean that A and B are not identical. Additionally, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."
[0324] Figure 15 An example of the structure of vehicle 2001 is shown. For example... Figure 15 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gear 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.
[0325] The drive unit 2002 may consist of, for example, an engine, a motor, or a hybrid power system of an engine and a motor.
[0326] The steering unit 2003 includes at least a steering wheel (also called a steering wheel), 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.
[0327] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2027 of the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).
[0328] The signals from various sensors 2021 to 2028 include current signals from current sensor 2021 that senses the current of the motor, speed signals of the front and rear wheels obtained by speed sensor 2022, air pressure signals of the front and rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal input signals obtained by accelerator pedal sensor 2029, brake pedal input signals obtained by brake pedal sensor 2026, gear lever operation signals obtained by gear lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.
[0329] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of vehicle 1.
[0330] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.
[0331] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 1 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 2028 in the vehicle 2001 via the communication port 2033.
[0332] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.
[0333] The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. Additionally, the communication module 2013 also transmits the following signals input to the electronic control unit 2010 via wireless communication to external devices: the front and rear wheel speed signals obtained by the speed sensor 2022; the front and rear wheel air pressure signals obtained by the air pressure sensor 2023; the vehicle speed signal obtained by the vehicle speed sensor 2024; the acceleration signal obtained by the acceleration sensor 2025; the accelerator pedal depressor signal obtained by the accelerator pedal sensor 2029; the brake pedal depressor signal obtained by the brake pedal sensor 2026; the gear shift lever operation signal obtained by the gear shift lever sensor 2027; and the detection signals for detecting obstacles, vehicles, pedestrians, etc., obtained by the object detection sensor 2028.
[0334] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle. Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gearshift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, and sensors 2021-2028 of the vehicle 2001 based on the information stored in the memory 2032.
[0335] Label Explanation
[0336] 10: Wireless Communication System
[0337] 20: NG-RAN
[0338] 100: gNB
[0339] 200:UE
[0340] 210: Wireless Signal Transceiver Unit
[0341] 220: Enlarged section
[0342] 230: Modulation and Demodulation Section
[0343] 240: Control Signal & Reference Signal Processing Unit
[0344] 250: Encoding / Decoding Section
[0345] 260: Data Transceiver Department
[0346] 270: Control Department
[0347] 1001: Processor
[0348] 1002: Memory
[0349] 1003: Storage device
[0350] 1004: Communication device
[0351] 1005: Input device
[0352] 1006: Output device
[0353] 1007: Bus
[0354] 2001: Vehicles
[0355] 2002: Drive Unit
[0356] 2003: Steering Unit
[0357] 2004: Accelerator Pedal
[0358] 2005: Brake Pedal
[0359] 2006: Gear Shift
[0360] 2007: Left and right front wheels
[0361] 2008: Left and right rear wheels
[0362] 2009: Axle
[0363] 2010: Electronic Control Department
[0364] 2012: Information Services Department
[0365] 2013: Communication Module
[0366] 2021: Current Sensor
[0367] 2022: Speed Sensor
[0368] 2023: Barometric Pressure Sensor
[0369] 2024: Vehicle Speed Sensor
[0370] 2025: Accelerometer
[0371] 2026: Brake Pedal Sensor
[0372] 2027: Gearshift Sensor
[0373] 2028: Object Detection Sensor
[0374] 2029: Accelerator Pedal Sensor
[0375] 2030: Driver Assistance Systems Department
[0376] 2031: Microprocessors
[0377] 2032: Memory (ROM, RAM)
[0378] 2033: Communication Port
Claims
1. A terminal having: The transmitting unit transmits uplink data channels following a sub-band full-duplex communication mode, wherein the sub-band full-duplex communication mode allocates uplink and downlink sub-bands non-overlappingly in the frequency direction within a specified time period based on time division duplex; and The control unit, when transmitting the uplink data channel in the time domain using the sub-band full-duplex communication mode and applying independent transmit power control for the uplink data channel, performs open-loop transmit power control for each uplink data channel without feedback from the receiving side.
2. The terminal according to claim 1, wherein, The control unit sets the parameters of the open-loop transmit power control semi-statically or dynamically for each of the uplink data channels.
3. A terminal having: The transmitting unit transmits uplink data channels following a sub-band full-duplex communication mode, wherein the sub-band full-duplex communication mode allocates uplink and downlink sub-bands non-overlappingly in the frequency direction within a specified time period based on time division duplex; and The control unit, when transmitting the uplink data channel in the time domain using the sub-band full-duplex communication mode and applying independent transmit power control for the uplink data channel, performs closed-loop transmit power control for each uplink data channel based on feedback from the receiving side.
4. The terminal according to claim 3, wherein, The control unit executes the closed-loop transmit power control based on the information elements of the closed-loop transmit power control independently set for each of the uplink data channels.
5. A terminal having: The transmitting unit transmits uplink data channels following a sub-band full-duplex communication mode, wherein the sub-band full-duplex communication mode allocates uplink and downlink sub-bands non-overlappingly in the frequency direction within a specified time period based on time division duplex; and The control unit, when transmitting the uplink data channel in the time domain using the sub-band full-duplex communication mode and applying independent transmit power control for the uplink data channel, performs open-loop transmit power control for each uplink data channel without feedback from the receiving side, and performs closed-loop transmit power control for each uplink data channel based on feedback from the receiving side.
6. A wireless communication method, which is a wireless communication method in a terminal, comprising the following steps: Uplink data channels are transmitted following a sub-band full-duplex communication mode, wherein the sub-band full-duplex communication mode allocates uplink and downlink sub-bands in a non-overlapping frequency direction within a specified time period based on time division duplex; and When transmitting the uplink data channel in the time domain using the sub-band full-duplex communication method and applying independent transmit power control for the uplink data channel, open-loop transmit power control without feedback from the receiving side is performed for each uplink data channel.
