Terminal, wireless communication system, and wireless communication method

Abstract

The present invention provides a terminal, a wireless communication system, and a wireless communication method that appropriately control transmission power when transmitting a signal for each different symbol type. This terminal comprises: a control unit that controls the transmission power of a signal in random access on the basis of either a first configuration for a first symbol type or a second configuration for a second symbol type; and a communication unit that transmits the signal on the basis of the transmission power.

Description

Terminal, wireless communication system, and wireless communication method

[0001] This disclosure relates to terminals, wireless communication systems, and wireless communication methods.

[0002] 3GPP (registered trademark) has standardized the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)), and is also working on standardizing the next generation of mobile communication systems, known as Beyond 5G, 5G Evolution, or 6G.

[0003] Release 18 discusses a duplexing scheme that enables simultaneous use of downlink (DL) and uplink (UL) by utilizing multiple subbands that make up a time-division duplex (TDD) band. Such a duplexing scheme is called subband non-overlapping full duplex (SBFD). Symbols to which SBFD is applied may also be called SBFD symbols. Furthermore, in SBFD symbols, the subband used for DL ​​may be called the DL subband, and the subband used for UL may be called the UL subband.

[0004] Furthermore, for Release 19, extensions are being considered regarding UL transmission and DL reception across SBFD and non-SBFD symbols within different slots (Non-Patent Document 1).

[0005] “New WID: Evolution of NR duplex operation: subband full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 20233GPP TS 38.214 V18.3.0 (2024-06)3GPP TS 38.300 V18.2.0 (2024-06)3GPP TS 38.331 V18.1.0 (2024-03)3GPP TR 38.858 V18.1.0 (2024-03)

[0006] There is room for consideration regarding the control of transmission power when transmitting signals for each of different types of symbols such as SBFD symbols and non-SBFD symbols.

[0007] One aspect of the present disclosure contributes to providing a terminal, a wireless communication system, and a wireless communication method that can appropriately control the transmission power when transmitting signals for each of different types of symbols.

[0008] A terminal according to one aspect of the present disclosure includes a control unit that controls the transmission power of a signal in random access based on either a first setting for a first symbol type or a second setting for a second symbol type, and a communication unit that transmits the signal based on the transmission power.

[0009] It is an overall schematic configuration diagram of a wireless communication system. It is a diagram showing the frequency range used in the wireless communication system. It is a diagram showing a configuration example of a wireless frame, subframe, slot, and symbol used in the wireless communication system. It is a diagram showing an example of the TDD setting defined up to Rel-16. It is a diagram showing an example of the SBFD configuration. It is a diagram showing an example of the SBFD operation. It is a diagram showing an example of an existing TDD setting. It is a diagram showing an example of TDD including the SBFD setting. It is a diagram showing pure time units and SBFD time units. It is a diagram showing pure time units and SBFD time units. It is a diagram showing pure time units and SBFD time units. It is a diagram showing pure time units and SBFD time units. It is a diagram showing pure time units and SBFD time units. It is a sequence diagram showing an example of the CBRA procedure. It is a sequence diagram showing another example of the CBRA procedure. It is a sequence diagram showing an example of the CFRRA procedure. It is a diagram showing an example of the RACH setting options. It is a table showing the relationship of the example shown in Proposal 3. It is a block diagram showing an example of the configuration of a base station. It is a block diagram showing an example of the configuration of a terminal. It is a diagram showing an example of the hardware configuration of a base station and a terminal. It is a diagram showing an example of the configuration of a vehicle.

[0010] Hereinafter, embodiments will be described based on the drawings. Note that the same or similar reference numerals are assigned to the same functions and configurations, and the description thereof will be omitted as appropriate.

[0011] <Configuration of Wireless Communication System> The wireless communication system 10 shown in FIG. 1 is a wireless communication system according to a scheme called 5G. On the other hand, the wireless communication system 10 may be a wireless communication system according to a scheme called Beyond 5G, 5G Evolution or 6G.

[0012] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO) that generates a more directional beam by controlling wireless signals transmitted from a plurality of antenna elements, Carrier Aggregation (CA) that bundles and uses a plurality of Component Carriers (CCs), Dual Connectivity (DC) that performs simultaneous communication with two base stations, etc. In this specification, "and / or" may sometimes be simply described as " / ".

[0013] As shown in FIG. 1, the wireless communication system 10 includes a base station 100 (hereinafter also referred to as gNodeB (gNB) 100) that constitutes a Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as user equipment (UE) 200) that performs wireless communication with the gNB 100. The NG-RAN 20 is connected to a core network (CN) not shown. The CN is composed of a plurality of network functions (NFs). The NFs are, for example, Access and Mobility Management Function (AMF), Network Data Analytics Function (NWDAF). The AMF performs, for example, registration of the UE 200. The NWDAF performs, for example, optimization of the CN. Note that the specific configuration of the wireless communication system 10, for example, the number of gNBs 100 and UEs 200 is not limited to the example shown in FIG. 1. Also, the NG-RAN 20 and the CN may simply be expressed as "network".

[0014] gNB100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration, having a Distributed Unit (DU) with the function of connecting to UE200 and a Central Unit (CU) with the function of connecting to the network. In this case, gNB100 may be interpreted as DU, as CU, or as DU and CU. When gNB100 is interpreted as DU, it may be called gNB-DU. When gNB100 is interpreted as CU, it may be called gNB-CU. When gNB100 is interpreted as DU and CU, the DU portion may be called gNB-DU and the CU portion may be called gNB-CU.

[0015] Furthermore, the wireless communication system 10 may support multiple frequency ranges (FRs). That is, as shown in Figure 2, it may support the following FRs: • FR1: 410 MHz to 7.125 GHz • FR2-1: 24.25 GHz to 52.6 GHz • FR2-2: Over 52.6 GHz to 71 GHz

[0016] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used. In FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.

[0017] Note that SCS may also be interpreted as numerology. Numerology is defined in §5.1 of Non-Patent Document 3, etc., and corresponds to a single subcarrier interval in the frequency domain.

[0018] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.

[0019] Figure 3 shows an example of the configuration of wireless frames (system frames), subframes, and slots used in the wireless communication system 10. As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

[0020] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it could be 28 or 56 symbols, etc.). In addition, the number of slots per subframe may differ depending on the SCS.

[0021] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).

[0022] The wireless communication system 10 may support coverage enhancement (CE) to broaden the coverage of the cell (or physical channel) formed by the gNB100. Coverage enhancement may provide mechanisms to improve the reception success rate of various physical channels, such as repetition (repeated transmission) of PRACH (physical random access channel).

[0023] For example, the UE200 receives information related to random access procedures from the gNB100 as a downlink signal (DL: Downlink) (e.g., SIB1 (System Information Block Type 1)).

[0024] Furthermore, for example, UE200 transmits PRACH to gNB100 using a RACH occasion, or RACH (transmit) opportunity (RO: RACH Occasion), which is a resource for transmitting a random access preamble as a UL signal. For example, UE200 replicates PRACH to gNB100 as a UL signal.

[0025] The UL signal may include, for example, UL data signals and control information. For example, the UL signal may include information about the processing capabilities of the UE200 (e.g., UE capability). The UL signal may also include reference signals.

[0026] The channels used to transmit UL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, the UE200 transmits control information using PUCCH and transmits UL data signals using PUSCH. Note that PUSCH is an example of an uplink shared channel, and PUCCH is an example of an uplink control channel. Shared channels may also be called data channels.

[0027] The reference signals included in the UL signal may include, for example, at least one of the following: DMRS (Demodulation Reference Signal), PTRS (Phase Tracking Reference Signal), CSI-RS (Channel State Information - Reference Signal), SRS (Sounding Reference Signal), and PRS (Positioning Reference Signal) for position information. For example, reference signals such as DMRS and PTRS are used to demodulate the UL data signal and are transmitted using PUSCH.

[0028] Meanwhile, the gNB100, in response to the operation of the UE200, transmits information related to the RACH procedure to the UE200 as a DL signal (e.g., SIB1, etc.).

[0029] For example, gNB100 receives PRACH from UE200 as a UL signal. For example, gNB100 receives PRACH from UE200 as a repetition signal.

[0030] The channels used to transmit DL signals include, for example, a data channel and a control channel. For example, the data channel may include a Physical Downlink Shared Channel (PDSCH), and the control channel may include a Physical Downlink Control Channel (PDCCH). For example, gNB100 transmits control information to UE200 using the PDCCH and transmits DL data signals using the PDSCH. Note that PDSCH is an example of a Downlink Shared Channel, and PDCCH is an example of a Downlink Control Channel. Note that PDCCH may be interpreted as Downlink Control Information (DCI), control information, etc., transmitted in the PDCCH.

[0031] The reference signals included in the DL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRSRS, and PRS for location information. For example, reference signals such as DMRS and PTRS are used to demodulate the DL data signal and are transmitted using PDSCH.

[0032] Next, we will explain SBFD, CG (Configured Grant), PUSCH / SPS (Semi-Persistent Scheduling), and PDSCH.

[0033] <SBFD Operation> Considering the transmission / reception time ratio (e.g., DL:UL = 4:1) in Time Division Duplex (TDD) up to Rel-16, there may be cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE200 may not be able to transmit UL signals / channels frequently, raising concerns about transmission delays for important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, in TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of UL coverage extension techniques such as repetition transmission.

[0034] In future wireless communication systems (e.g., Rel-18 and beyond), the introduction of a time-frequency division duplex method combining TDD and frequency division duplex (FDD) for UL and DL is being considered.

[0035] Examples of such time-frequency division duplexing methods include XDD (Cross Division Duplex) or Subband non-overlapping Full Duplex (SBFD). XDD or SBFD may also refer to a duplexing method that frequency-division multiplexes DL and UL within one component carrier (CC) of the TDD band (allowing simultaneous use of DL and UL).

[0036] Figure 4A shows an example of a TDD configuration as defined up to Rel-16. In the example shown in Figure 4A, a TDD slot or symbol is set in the UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) or bandwidth portion (BWP).

[0037] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. With such conventional TDD slot or symbol settings, sufficient UL time resources cannot be secured, which may lead to UL transmission delays and reduced coverage performance.

[0038] Figure 4B shows an example of an SBFD configuration. In the example shown in Figure 4B, within a single component carrier (CC), the resources used for receiving DL and the resources used for transmitting UL overlap in time. With such a resource configuration, more UL resources can be secured, and the efficiency of resource utilization can be improved.

[0039] For example, as shown in the example in Figure 4B, the ends of the frequency domain may be set as DL resources, and UL resources may be sandwiched between these DL resources. This can help avoid and mitigate cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resources and the UL resources.

[0040] Considering the complexity of handling self-interference, it is conceivable that only the gNB100 would use both DL and UL resources simultaneously. In other words, for wireless resources where DL and UL overlap in time, one UE200 may use the DL resource and another UE200 may use the UL resource.

[0041] Figure 5 shows an example of SBFD operation. In the example shown in Figure 5, a portion of the DL resources in the TDD band are set as UL resources, and the DL and UL are configured to partially overlap in the time domain.

[0042] In the example shown in Figure 5, during the DL-only period, each of the multiple UE200s (UE1 and UE2 in Figure 5) receives the DL channel / signal.

[0043] Furthermore, during periods when DL and UL overlap in time, one UE200 (UE1 in the example in Figure 5) receives the DL channel / signal, while another UE200 (UE2 in the example in Figure 5) transmits the UL channel / signal. During this period, the gNB100 performs simultaneous transmission and reception of DL and UL.

[0044] Furthermore, during UL-only periods, each of the multiple UE200 units (UE1 and UE2 in Figure 5) transmits a UL channel / signal.

[0045] In existing NRs (e.g., those defined up to Rel-15 / 16 / 17), DL frequency resources and UL frequency resources in the UE carrier are configured as DL BWPs and UL BWPs, respectively. Switching between DL / UL frequency resources requires the configuration of multiple BWPs and a BWP adaptation mechanism.

[0046] Figure 6A shows an example of an existing TDD configuration. In Figure 6A, slots / symbols marked with "D" are DL slots / symbols, slots / symbols marked with "U" are UL slots / symbols, and slots / symbols marked with "F" are flexible (hereinafter also referred to as FL) slots / symbols. The same notation may be used in the following figures as well.

[0047] In existing NRs, as shown in Figure 6A, the time resources (time units such as symbols and slots) in the TDD carrier for UE200 are configured in the TDD settings as at least one of DL, UL, and Flexible (FL).

[0048] Figure 6B shows an example of an existing TDD setting. In Figure 6B, slots / symbols or subbands marked with "D" are DL slots / symbols or DL ​​subbands, and slots / symbols or subbands marked with "U" are UL slots / symbols or UL subbands. Similar notation may be used in the following figures.

[0049] The SBFD symbol may be a symbol that is notified or set as UL (or DL) on one frequency resource (subband), or notified or set for UL transmission (or DL ​​reception), while on another frequency resource (subband), it may be a symbol that is notified or set as DL (or UL) or notified or set for DL ​​reception (or UL transmission), as shown in Figure 6B. Alternatively, the SBFD symbol may be a symbol that is notified or set as UL (or DL) on a portion of the frequency resource, or notified or set for UL transmission (or DL ​​reception). Alternatively, the SBFD symbol may be a symbol that is notified or set as DL (or UL) on a portion of the frequency resource, or notified or set for DL ​​reception (or UL transmission).

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

[0051] A pure time unit may be a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol, also called a non-SBFD symbol), a slot / subslot that does not contain or overlap SBFD symbols, or a group of symbols / slots / subslots that do not contain or overlap SBFD symbols, and may also be called a non-SBFD time unit. For example, a pure time unit may be referred to as a time unit consisting only of DLs on a frequency resource, as shown in Figure 7A, or as a time unit consisting only of ULs on a frequency resource, as shown in Figure 7B.

[0052] Furthermore, with respect to the SBFD time unit, DL resources and UL resources may have various arrangement patterns in the frequency domain. For example, the SBFD time unit of frequency domain pattern #1 may have the arrangement pattern shown in Figure 7C. The SBFD time unit of frequency domain pattern #2 may have the arrangement pattern shown in Figure 7D. The SBFD time unit of frequency domain pattern #3 may have the arrangement pattern shown in Figure 7E. These arrangement patterns are merely examples, and other arrangement patterns may be used. The frequency domain pattern of the SBFD time unit may mean the resource recency pattern in the frequency domain for the SBFD time unit.

[0053] As mentioned above, SBFD may be applied to each slot / symbol. In addition, each slot / symbol may be set to DL, UL, or Flexible (FL) which can be used as DL or UL, and then SBFD may be applied.

[0054] SBFD is a type of (full-duplex) duplexing system based on time-division duplexing (TDD), enabling the simultaneous use of multiple subbands that make up the TDD band. SBFD can also be described as a duplexing system where multiple subbands are defined within the TDD band, or a duplexing system where UL and DL are allocated non-overlapping in the frequency direction within the TDD time unit, or as a full-duplexing system using subbands.

[0055] Symbols to which SBFD applies are also called SBFD symbols. "SBFD applies" may be interpreted as SBFD being applied in at least part of the scheduling. That is, "symbols to which SBFD applies" may be interpreted as symbols to which SBFD applies in scheduling where SBFD is applied (SBFD symbols). Also, "time units to which SBFD does not apply" may be interpreted as symbols to which SBFD does not apply in scheduling where SBFD is applied (non-SBFD symbols).

[0056] Furthermore, UEs that support SBFD operation (SBFD-aware UEs) are described as SBFD-aware UEs or SBFD-capable UEs, while UEs that do not support SBFD operation are described as Legacy UEs. For example, when SBFD is applied to a DL symbol, an SBFD-aware UE can recognize the UL subband (and DL subband) in this SBFD symbol, but a Legacy UE will recognize this SBFD symbol as a regular DL symbol.

[0057] <Random Access Procedures> Random access procedures for NRs are performed for various purposes, such as initial access, beam fault recovery, and handover. Random access procedures include CBRA (Contention Based Random Access) procedures as collision-type random access procedures and CFRA (Contention Free Random Access) procedures as non-collision-type random access procedures. In CBRA procedures, since the UE200 starts spontaneously, collisions may occur if multiple UE200s start the random access procedure simultaneously. On the other hand, with CFRA, the gNB100 can instruct connected UE200s to execute the random access procedure in a way that avoids collisions between multiple UE200s.

[0058] In NR, a random access procedure may be performed by selecting the SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block, or by selecting CSI-RS. The SS / PBCH block may also be called the SSB or synchronization signal, and CSI-RS may be called the reference signal.

[0059] Figure 8 is a sequence diagram showing an example of the CBRA procedure.

[0060] gNB100 transmits an SSB for each beam, for example, and UE200 monitors the SSB for each beam. UE200 selects an SSB from among several SSBs whose received power (RSRP: Reference Signal Received Power) is greater than (or equal to) a threshold, and uses the RO associated with the selected SSB to transmit a random access preamble to gNB100 via PRACH (step S101). The random access preamble (sometimes abbreviated as RA preamble or RA Preamble) may be appropriately referred to as Preamble, PRACH preamble, Message1, Msg1, etc.

[0061] gNB100 sends a response message to Msg1 as a second message to UE200 via PDSCH (step S102). This response message (second message) may be appropriately referred to as Random Access Response (RAR), RA Response, Message2, Msg2, etc. After sending Msg1, UE200 may monitor PDCCH, which is used for scheduling PDSCH including Msg2. Msg2 may include an uplink grant (UL Grant) (RAR uplink grant) used for scheduling PUSCH, which includes a third message transmitted by UE200.

[0062] UE200 transmits a PUSCH scheduled by the RAR uplink grant as a third message (step S103). For example, UE200 transmits a Radio Resource Control (RRC) connection request, an RRC connection re-establishment request, etc., to gNB100 via the PUSCH. The third message may be appropriately named Message3, Msg3, RRC Connection Request, etc.

[0063] gNB100 transmits a contention resolution message as the fourth message via PDSCH (step S104). This contention resolution message (fourth message) may be appropriately referred to as message 4, Msg4, etc. After transmitting Msg3, UE200 may monitor the PDCCH used for scheduling the PDSCH containing Msg4. Msg4 may include a contention resolution ID (UE contention resolution ID). The contention resolution ID may be used to resolve a collision in which multiple UE200s transmit signals using the same radio resource. If the contention resolution ID contained in the Msg4 received by UE200 is the same value as the ID used to identify UE200, UE200 may determine that the contention resolution was successful and set the value of TC-RNTI (Temporary Cell - Radio Network Temporary Identifier) ​​in the C-RNTI (Cell - Radio Network Temporary Identifier) ​​field. When the value of TC-RNTI is set in the C-RNTI field, UE200 may consider the RRC connection to be complete. Msg4 may be referred to as RRC Connection Setup, etc.

[0064] Once the RRC connection is established, UE200 may send an Ack (Acknowledgement) via PUCCH (PUCCH resource) indicated by the PUCCH resource instruction field included in the PDCCH that scheduled Msg4, in order to notify gNB100 that the RRC connection has been established. After the RRC connection is established, UE200 may also send UE capability to gNB100. The random access procedure described above may also be referred to as the Type 1 RACH procedure, the 4-step RACH procedure, Type 1 RACH, the 4-step RACH, etc.

[0065] Figure 9 is a sequence diagram showing another example of the CBRA procedure.

[0066] UE200 sends a message containing the RA preamble and data to gNB100 (step S201). For example, UE200 selects an RO (Robot Operator) and sends the RA preamble with that RO, and also sends the data with the PUSCH resource associated with that RO, similar to the RO selection in the 4-step RACH procedure. This message may be appropriately referred to as MessageA, MsgA, etc. The RA preamble and data here may correspond to Msg1 and Msg3 in the 4-step RACH procedure, respectively. MsgA contains one RA preamble (referred to as MsgA PRACH) and one data (referred to as MsgA PUSCH), and MsgA PRACH and MsgA PUSCH are transmitted using time-division multiplexing. More specifically, MsgA PRACH is a preamble with a preamble index within an MsgA RACH occasion (RO), and MsgA PUSCH is a PUSCH with a PUSCH resource unit (PRU) within an MsgA PUSCH occasion (PO) according to the MsgA PUSCH setting. Note that in this procedure, the resource for transmitting data is not limited to a PUSCH resource, but may be any channel resource for transmitting data (or control information).

[0067] gNB100 sends a response message to UE200 as a second message (step S202). This response message (second message) may be appropriately referred to as MessageB, MsgB, etc. The contents of MessageB may correspond, for example, to Msg2 and Msg4 in the 4-step RACH procedure. MsgB includes one PDSCH (and one PDCCH that schedules the PDSCH). From the perspective of the physical layer, the contents of Msg2 and Msg4 are simply integrated into MsgB.

[0068] Once the RRC connection is established, UE200 may send an Ack via PUCCH (PUCCH resource) to notify gNB100 that the RRC connection is complete. Furthermore, after the RRC connection is established, UE200 may send UE capability to gNB100. The above-described random access procedure may also be referred to as the Type 2 RACH procedure, 2-step RACH procedure, Type 2 RACH, 2-step RACH, etc. 2-step RACH is supported to reduce RACH delay.

[0069] Figure 10 is a sequence diagram showing an example of the CFRA procedure.

[0070] UE200 is requested by gNB100 to send an RA preamble (Msg1). Here, gNB100 allocates the RA preamble (Msg1) via dedicated signaling (step S301). A PDCCH for such dedicated signaling may be called a PDCCH order. UE200 may monitor the PDCCH (PDCCH order) for performing the resource allocation of Msg1.

[0071] UE200 transmits the above-mentioned Msg1 to gNB100 (step S302).

[0072] gNB100 sends the above-described Msg2 to UE200 (step S303). Once the RRC connection is complete, UE200 may send an Ack via PUCCH (PUCCH resource) to notify gNB100 that the RRC connection is complete. After the RRC connection is established, UE200 may also send UE capability to gNB100.

[0073] In this embodiment, in order to extend coverage in random access procedures, UE200 may repeatedly transmit Msg1 (and therefore PRACH) in, for example, the 4-step RACH procedure shown in Figure 8 and the CFRA procedure shown in Figure 10 described above. However, in this disclosure, Msg1 (and therefore PRACH) may also be repeatedly transmitted in the 2-step RACH procedure shown in Figure 9 described above.

[0074] In the random access described above, the UE determines the random access opportunity to send a preamble to initiate random access, and from among the determined ROs, it determines which ROs are valid (and which are invalid). The random access opportunity may also be called a RACH Occasion.

[0075] Next, we will explain the power control of PRACH and Msg3 transmitted by UE200 in the random access procedure shown in Figure 8, and MsgA transmitted by UE200 in the random access procedure shown in Figure 9. Note that Msg3 and MsgA are transmitted via PUSCH, and may therefore be written as Msg3 PUSCH and MsgA PUSCH, respectively.

[0076] <Power Control of PRACH> The UE determines the transmit power of PRACH. Based on the DL RS of cell c in a given transmit opportunity i, the transmit power of the active UL of cell c's carrier f in BWP is P ＰＲＡＣＨ，ｂ，ｆ，ｃ (i) is expressed as b indicates the BWP of the active UL. For example, P ＰＲＡＣＨ，ｂ，ｆ，ｃ (i) is calculated by the following formula (1).

[0077] PC ＭＡＸ，ｆ，ｃ (i) indicates the maximum output power set for UE with respect to the carrier f of cell c within transmission opportunity i.

[0078] PL ｂ，ｆ，ｃ This shows the path loss of carrier f's active UL BWPb based on the DL RS (reference signal) associated with the active DL BWP PRACH transmission of cell c.

[0079] P ＰＲＡＣＨ，ｔａｒｇｅｔ，ｆ，ｃis the target received power of the PRACH provided by the parameters of the upper layer. The target received power of the PRACH is represented as PREAMBLE_RECEIVED_TARGET_POWER. For example, the transmission power of the PRACH is calculated based on PREAMBLE_RECEIVED_TARGET_POWER from the upper layer.

[0080] And PREAMBLE_RECEIVED_TARGET_POWER is calculated based on the set preambleReceivedTargetPower and power ramping.

[0081] <Power Control of Msg3 PUSCH and MsgA PUSCH> The UE transmits PUSCH on the UL BWPb of carrier f of serving cell c using the setting of the PUSCH power control adjustment state with index l and the parameter set with index j. In this case, the UE calculates the transmission power by the following formula (2).

[0082] P Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j) is a parameter composed of the component PO_NOMINAL,PUSCH,b,f,c(j) and the component P Ｏ＿ＵＥ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j).

[0083] Here, for example, when the UE establishes a dedicated RRC connection using the type 1 random access procedure, the following relationship exists for P Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (j). ・When j = 0, P Ｏ＿ＵＥ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (0) = 0, and PO_NOMINAL,PUSCH,b,f,c(0) = P Ｏ＿ＰＲＥ +Δ ＰＲＥＡＭＢＬＥ，Ｍｓｇ３ .

[0084] Note that P Ｏ＿ＰＲＥ is provided by preambleReceivedTargetPower. Also, Δ ＰＲＥＡＭＢＬＥ，Ｍｓｇ３ may be provided by msg3-DeltaPreamble or deltaPreamble.

[0085] Here, for example, if UE establishes a dedicated RRC connection using a Type 2 random access procedure, P Ｏ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ The following relationship exists for (j): • When j = 0, P Ｏ＿ＵＥ＿ＰＵＳＣＨ，ｂ，ｆ，ｃ (0) = 0, and PO_NOMINAL_PUSCH, b, f, c(0) = P Ｏ＿ＰＲＥ +Δ ＭｓｇＡ，ＰＵＳＣＨ That is the case.

[0086] Note P Ｏ＿ＰＲＥ This is provided by msgA-preambleReceivedTargetPower or preambleReceivedTargetPower. Also, Δ ＭｓｇＡ，ＰＵＳＣＨ This may be provided by msgA-DeltaPreamble or deltaPreamble.

[0087] Note that α in equation (2) ｂ，ｆ，ｃ Regarding (j), the following cases exist. Case 1: PO_NOMINAL_PUSCH, b, f, c(0) = P Ｏ＿ＰＲＥ +Δ ＭｓｇＡ，ＰＵＳＣＨ And if msgA-Alpha is provided, α ｂ，ｆ，ｃ (0) is the value of msgA-Alpha. Case 2: PO_NOMINAL, PUSCH, b, f, c(0) = P Ｏ＿ＰＲＥ +Δ ＰＲＥＡＭＢＬＥ，Ｍｓｇ３ And if msg3-Alpha is provided, α ｂ，ｆ，ｃ (0) is the value of msg3-Alpha.

[0088] In other words, α in equation (2) in determining the transmission power of Msg3 PUSCH ｂ，ｆ，ｃ (j) may be determined based on msg3-Alpha. In determining the transmit power of MsgA PUSCH, α in equation (2) ｂ，ｆ，ｃ (j) may be determined based on msgA-Alpha.

[0089] Thus, in determining the transmission power for Msg3 PUSCH transmission, at least one of the following parameters may be used: preambleReceivedTargetPower, msg3-DeltaPreamble, deltaPreamble, and msg3-Alpha. Similarly, in determining the transmission power for MsgA PUSCH transmission, at least one of the following parameters may be used: msgA-preambleReceivedTargetPower, preambleReceivedTargetPower, msgA-DeltaPreamble, deltaPreamble, and msgA-Alpha.

[0090] Note that preambleReceivedTargetPower is a parameter included in RACH-ConfigGeneric.

[0091] msg3-DeltaPreamble is a parameter included in PUSCH-ConfigCommon.

[0092] deltaPreamble is a parameter included in FeatureCombinationPreamble.

[0093] msg3-Alpha is included in PUSCH-PowerControl. Note that PUSCH-PowerControl is included in PUSCH-Config.

[0094] msgA-PreambleReceivedTargetPower is included in RACH-ConfigGenericTwoStepRA. msgA-DeltaPreamble is included in MsgA-PUSCH-Config. msgA-Alpha is included in MsgA-PUSCH-Resource. Note that MsgA-PUSCH-Resource may also be included in MsgA-PUSCH-Config. Furthermore, RACH-ConfigGenericTwoStepRA and MsgA-PUSCH-Config may also be included in MsgA-ConfigCommon.

[0095] <Consideration of Duplex Extension for Rel-19> As mentioned above, for Rel-18, consideration has been given to enabling the simultaneous existence of downlink and uplink (full duplex, more specifically subband non-overlapping full duplex) on the gNB side within the conventional TDD band. Regarding SBFD, the impact on specifications, performance evaluation results, implementation feasibility, and impact on RF requirements are summarized in Non-Patent Document 5.

[0096] Non-patent document 1 focuses on the expansion of subband non-overlapping full duplex (SBFD) operation on the gNB side within a TDD carrier. The objectives of the study toward Rel-19 are as follows: (1) In RRC_CONNECTED mode, consider the specification for semi-static indication of the time position of the SBFD subband to the UE. The indication of the time position of the SBFD subband in SIB is not excluded. (2) In RRC_CONNECTED mode, consider the specification for semi-static indication of the frequency domain position of the SBFD subband to the UE. The indication of the frequency domain position of the SBFD subband in SIB is not excluded. (3) Consider the specification for SBFD operations to support random access of SBFD symbols by the UE in RRC CONNECTED mode. (4) Consider SBFD operations to support random access by the UE in RRC_IDLE / INACTIVE mode, and define the specification if appropriate. Confirm whether to proceed with standardization work in RAN#104. (5) Consider the specification for the operation and procedure of UE transmission / reception and measurement of SBFD symbols and / or non-SBFD symbols for SBFD-aware UEs. DL and / or flexible symbols as shown by TDD-UL-DL-ConfigCommon. Transmit / receive operation in the SBFD subband configured as (symbol) UL transmission only within the UL subband DL reception only within the DL subband (excluding CLI measurements by UE outside the DL subband) Note: When flexible symbols are used, it is not expected that the legacy uplink symbols will be converted to downlink / SBFD symbols. Enhanced frequency domain resource allocation in the following SBFD symbols Frequency domain resource allocation of PDSCH / CSI-RS spanning two DL subbands in the SBFD symbol SBFD subband and RBG (Resource Block)Handling of boundary inconsistencies between Group, CSI Report subband, CSI-RS resources, and PRG (Precoding Resource block Group) - Enhancements to physical channels / signals and procedures spanning SBFD and non-SBFD symbols in different slots, where each transmit / receive in a slot includes either all SBFD symbols or all non-SBFD symbols, including: Resource allocation in the frequency domain when different available frequency resources are used in different slots during SBFD and non-SBFD symbol transmit / receive - CSI reports of related CSI-RS instances occurring in both SBFD and non-SBFD symbols in different slots - SRS, PUCCH and PUSCH configuration in SBFD and non-SBFD symbols (resources, frequency hopping parameters, UL power control parameters and / or beam / spatial relationships, etc.) - Collision handling between DL receive in the DL subband and UL transmit in the UL subband in SBFD symbols (6) Based on TR 38.858 (Non-Patent Literature 5), the following is assumed: - SBFD on the gNB side - Half-duplex operation on the UE side Operation) ・FR1 and FR2-1 ・SBFD operation option 4 (for example, the time and frequency positions of the subband for SBFD operation are known to the SBFD-enabled UE) ・Coexistence of non-SBFD-enabled UEs (including legacy UEs) and SBFD-enabled UEs in a cell where SBFD is being operated on the gNB side ・SBFD scheme in a single configuration DL and UL BWP pair with aligned center frequencies ・One UL subband for SBFD operation in SBFD symbols (excluding legacy UL symbols / slots) within a TDD carrier ・The mechanism for SBFD operation must also consider the coexistence of adjacent channels between the two operators

[0097] <Transmission / reception spanning SBFD and non-SBFD symbols> Section 6.1.2 of Non-Patent Document 5 examines whether or not to support transmission / reception spanning SBFD and non-SBFD symbols.

[0098] For UL transmit / DL receive operations spanning SBFD and non-SBFD symbols in different slots (where each transmit / receive within a slot is either all SBFD or all non-SBFD symbols), the following options should be considered for SBFD-enabled UEs: Option 1: Transmit / receive is restricted to either SBFD symbols only or non-SBFD symbols only. Option 2: Transmit / receive can be performed using both SBFD and non-SBFD symbols.

[0099] UL transmission / DL reception spanning SBFD and non-SBFD symbols includes the following information: • PDSCH / PUSCH / PUCCH repetition • SPS (Semi-Persistent Scheduling) PDSCH / CG PUSCH (Configured Grant PUSCH) • TBoMS (Transport Block processing over Multiple Slots) • Multiple PUSCH / PDSCH scheduled by a single DCI • Periodic / semi-persistent SRS / CSI-RS / PUCCH • PDCCH

[0100] Option 1 can be achieved by configuring or scheduling the gNB so that all transmit / receive occasions are limited to either SBFD symbols or non-SBFD symbols. Alternatively, Option 1 can be achieved by additional instructions or rules to determine whether a transmit / receive occasion is valid within one symbol type and invalid within another. Frequency resources, power control, and beam / spatial relationships for all transmit / receive occasions may be the same in Option 1, but may be different in Option 2. If they are different, additional specification work may be required. Option 1 may increase or not increase transmit / receive latency if transmit / receive is delayed in other symbol types, and may degrade performance if transmit / receive is dropped in other symbol types. Option 2 may or may not reduce transmit / receive latency and improve coverage.

[0101] <Definition of Terms> The following explains the definitions of terms related to SBFD.

[0102] SBFD symbol: A symbol set in the SBFD subband. Non-SBFD symbol: A symbol not set in the SBFD subband. DL (or semistatic D) symbol: A symbol indicated as DL by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated. UL (or semistatic U) symbol: A symbol indicated as UL by tdd-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated. Flexible (or semistatic F, or flexible) symbol: A symbol indicated as flexible by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated. SBFD DL symbol: A symbol designated as Downlink (DL) by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, in which the SBFD subband is set within the symbol. SBFD Flexible (FL) symbol: A symbol designated as Flexible by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, in which the SBFD subband is set within the symbol.

[0103] The parameters for configuring the resources of the Sounding Reference Signal (SRS) may include an SRS Config. The SRS Config is a parameter that defines a list of SRS-ResourceSets and a list of SRS-Resources. The SRS-ResourceSets included in the list may include an identifier for the SRS-ResourceSet (srs-ResourceSetId), a list of identifiers for the SRS-Resource (srs-ResourceIdList), etc. The SRS-Resources included in the list include an identifier for the SRS-Resource (srs-ResourceId), the SRS resource in the frequency domain (e.g., resourceMapping), etc. resourceMapping includes the start position (startPosition), the number of symbols (nrofSymbols), the repetition factor, etc. The SRS Config may also be a parameter defined in §6.3.2 “Radio resource control information elements” of Non-Patent Literature 4.

[0104] <Agreements in 3GPP> The following two options were considered for determining the valid RO in the SBFD symbol. Note that in the following, a valid RO may be referred to as a valid RO. Option 1: Single PRACH setting Option 2: Additional PRACH setting for SBFD Note that in Option 1, a single expandable RACH setting may be used. Furthermore, the RO in the UL subband of the SBFD symbol may be valid for SBFD-aware UEs. Option 2 may use two separate RACH settings, including a legacy RACH setting and an additional RACH setting. Furthermore, the RO in the UL subband of the SBFD symbol may be valid for SBFD-aware UEs.

[0105] The following points were agreed upon: For SBFD-aware UEs in the RRC_CONNECTED state, two options are supported: Option 1 of the RACH configuration with Alt 1-1 and Option 2 of the RACH configuration. Option 1 of the RACH configuration with Alt 1-1 uses a single RACH configuration and operates only based on the existing parameters of that single RACH configuration. Option 2 of the RACH configuration uses two distinct RACH configurations. These two distinct configurations include one legacy RACH configuration and one additional RACH configuration. It is not supported for both options to be available to a UE at the same time.

[0106] Figure 11 shows examples of RACH setting options. Figure 11 shows examples of RACH settings for each of the two options. For each option in Figure 11, the horizontal axis represents the time axis, and the vertical axis represents the frequency axis. For each option in Figure 11, the RO set to SBFD symbols and non-SBFD symbols is shown.

[0107] As shown in Option 1 of Figure 11, in Option 1, the ROs of both SBFD symbols and non-SBFD symbols are set by the legacy RACH configuration. As shown in Option 2 of Figure 11, in Option 2, the RO of SBFD symbols is set by an additional RACH configuration, and the RO of non-SBFD symbols is set by the legacy RACH configuration.

[0108] An additional RO is defined as follows: • For RACH configuration option 1, an additional RO includes ROs within SBFD symbols configured as DL by tdd-UL-DL-ConfigurationCommon, ROs spanning SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon, and ROs spanning SBFD symbols configured as DL. • For RACH configuration option 2, an additional RO is an RO configured by an additional RACH configuration.

[0109] With regard to enabling RO for option 1 of a RACH configuration with Alt 1-1, an RO spanning SBFD symbols configured as flexible and SBFD symbols configured as DL by tdd-UL-DL-ConfigurationCommon is treated the same as an RO within an SBFD symbol configured as DL by tdd-UL-DL-ConfigurationCommon. Here, the RO includes at least one DL symbol configured by tdd-UL-DL-ConfigurationCommon.

[0110] Option 2 of the RACH settings enables additional RO in any of the following cases: • The RO is within an SBFD symbol. • The network sets the RO to be enabled when the RO starts with an SBFD symbol and ends with a non-SBFD symbol within the same slot or across different slots. • The RO is after the last downlink non-SBFD symbol. ｇａｐ Starts at the symbol's position. The RO is N after the latest SSB. ｇａｐ Starts at the symbol's position; the RO does not overlap with the SSB in the time domain.

[0111] As described above, in Option 1 of the RACH configuration with Alt 1-1 (i.e., a single RACH configuration), legacy ROs and additional ROs correspond to the following ROs: • Legacy ROs are valid legacy ROs that include ULs or flexible symbols. • Additional ROs are ROs within SBFD DL symbols, or ROs that span SBFD DL symbols and SBFD flexible symbols.

[0112] As described above, in RACH configuration option 2 (i.e., additional RACH configuration for SBFD), legacy RO and additional RO correspond to the following ROs: - Legacy RO is an active RO configured by the legacy RACH configuration. - Additional RO is an RO within an SBFD symbol, or an RO that is enabled when the network starts with an SBFD symbol and ends with a non-SBFD symbol in the same or different slots, as configured by the additional RACH configuration.

[0113] Individual UL power control for PUSCH / PUCCH / SRS symbols, both SBFD and non-SBFD symbols, was agreed upon. In the case of PUSCH, the discussion regarding individual power control primarily concerned PUSCH symbols other than Msg3 PUSCH. On the other hand, individual PUSCH power control for Msg3 PUSCH symbols, both SBFD and non-SBFD symbols, was not discussed.

[0114] Furthermore, it was agreed that separate power control of PRACH for SBFD symbols and non-SBFD symbols would be supported. In other words, it was agreed that power control of PRACH in SBFD symbols and power control of PRACH in non-SBFD symbols would be supported as separate controls.

[0115] This section explains related technologies concerning the power control described above.

[0116] <Related Technology 1> Related Technology 1 involves individually controlling the power for transmitting Msg3 PUSCH using SBFD symbols and non-SBFD symbols.

[0117] - Alt-1: The delta preamble power parameters for Msg3 PUSCH in SBFD symbols and the delta preamble power parameters for Msg3 PUSCH in non-SBFD symbols will be treated separately. For example, separate delta preamble power parameters will be set to calculate PREAMBLE_RECEIVED_TARGET_POWER.

[0118] - Example: In "PUSCH-configCommon", a new parameter "msg3-DetaPreamble-sbfd-r19" is set. In this case, "msg3-DeltaPreamble" is used for Msg3 PUSCH transmissions within non-SBFD symbols, and the new parameter "msg3-DeltaPreamble-sbfd-r19" is used for Msg3 PUSCH transmissions within SBFD symbols.

[0119] - Example: Common PUSCH settings are configured separately for SBFD and non-SBFD. For example, a new parameter "PUSCH-configCommon-sbfd-r19" is set for SBFD. In this case, "msg3-DeltaPreamble" in "PUSCH-configCommon" for non-SBFD is used for Msg3 PUSCH transmission within non-SBFD symbols, and "msg3-DeltaPreamble" (or "msg3-DeltaPreamble-sbfd-r19") in "PUSCH-configCommon-sbfd-r19" for SBFD is used for "Msg3 PUSCH transmission within SBFD symbols.

[0120] - For Msg3 PUSCH transmission in Alt-2:SBFD symbol, a (target) power offset may be set or indicated.

[0121] - Example: For Msg3 PUSCH transmission in SBFD symbols, the following formula (3) may be applied. Note that the SBFD offset in the formula may be set or indicated by gNB. For example, the value (dB) of the SBFD offset may be positive (e.g., +1 / 2 / 3dB) or negative (e.g., -1 / 2 / 3dB).

[0122] <Related Technology 2> Related Technology 2 is separate transmit power control for SBFD symbols and non-SBFD symbols. Firstly, separate PRACH power parameters may be set or instructed for PRACH transmission in SBFD symbols and for PRACH transmission in non-SBFD symbols. For example, a separate preamble target power parameter may be set to calculate PREAMBLE_RECEIVED_TARGET_POWER.

[0123] Example 1: "preambleReceivedTargetPower" (or "msgA-PreambleReceivedTargetPower" for two-step random access) may be used for PRACH transmission in non-SBFD symbols, and a new parameter, "preambleReceivedTargetPower-sbfd-r19" (or "msgA-PreambleReceivedTargetPower-sbfd-r19" for two-step random access), may be set and used for PRACH transmission in SBFD symbols.

[0124] Example 2: The "preambleReceivedTargetPower" setting in the RACH configuration for non-SBFD may be used for PRACH transmission in non-SBFD symbols, and the "preambleReceivedTargetPower" (or preambleReceivedTargetPower-sbfd-r19, or msgA-PreambleReceivedTargetPower or msgA-PreambleReceivedTargetPower-sbfd-r19 in the RACH configuration for SBFD) may also be used for PRACH transmission in SBFD symbols.

[0125] Next, a (target) power offset may be set or instructed for PRACH transmission in SBFD symbols. For example, the conventional power calculation rules may be used for PRACH transmission in non-SBFD symbols, and the above-mentioned (target) power offset may be added (reduced) based on the conventional power calculation rules for PRACH transmission in SBFD symbols.

[0126] - Example: For PRACH transmission in SBFD symbol, the following equation (4) may be applied. Note that SBFD_offset in equation (4) may be set or indicated by gNB. The value of SBFD_offset (dB) may be positive (e.g., +1 / 2 / 3dB) or negative (e.g., -1 / 2 / 3dB).

[0127] <Related Technology 3> In a first embodiment, the delta preamble power parameter for MsgA PUSCH in an SBFD symbol and the delta preamble power parameter for MsgA PUSCH in a non-SBFD symbol may be set / indicated individually. For example, the individual delta preamble power parameter may be set to calculate PREAMBLE_RECEIVED_TARGET_POWER.

[0128] Example 1: msgA-DeltaPreamble or deltaPreamble may be used for MsgA PUSCH transmission in non-SBFD symbol, and a new parameter, msgA-DelaPreamble-sbfd-r19 or delaPreambl-sbfd-r19, may be set and used for MsgA PUSCH transmission in SBFD symbol. Note that the contents of Example 1 may also apply when individual MsgA settings are not made between SBFD and non-SBFD.

[0129] Example 2: In the MsgA settings for non-SBFD, msgA-DeltaPreamble or deltaPreamble may be used for MsgA PUSCH transmission in non-SBFD symbols, or msgA-DeltaPreamble or deltaPreamble (or msgA-DeltaPreamble-sbfd-r19 or DeltaPreamble-sbfd-r19) in the MsgA settings for SBFD may be used for MsgA PUSCH transmission in SBFD symbols. Note that the contents of Example 2 may also apply when separate MsgA settings are made between SBFD and non-SBFD.

[0130] Next, in a second embodiment, a (target) power offset may be set or specified for MsgA PUSCH transmission in SBFD symbols. For example, the conventional power calculation rules may be used for MsgA PUSCH transmission in non-SBFD symbols, and the above-mentioned (target) power offset may be added (reduced) based on the conventional power calculation rules for MsgA PUSCH transmission in SBFD symbols.

[0131] - Example: For MsgA PUSCH transmission in SBFD symbol, the following formula (5) may be applied. Note that the SBFD offset in the formula may be set or indicated by gNB. The value of SBFD_offset (dB) may be positive (e.g., +1 / 2 / 3dB) or negative (e.g., -1 / 2 / 3dB).

[0132] <Points to Consider> In RAN1, as mentioned above, individual UL power control for PUSCH / PUCCH / SRS for SBFD symbols and non-SBFD symbols was agreed upon. In the case of PUSCH, the discussion regarding individual power control mainly concerned PUSCHs other than Msg3 PUSCH. On the other hand, individual PUSCH power control for Msg3 PUSCH for SBFD symbols and non-SBFD symbols was not discussed.

[0133] Furthermore, it was agreed that separate power control of PRACH for SBFD symbols and non-SBFD symbols would be supported. In other words, it was agreed that power control of PRACH in SBFD symbols and power control of PRACH in non-SBFD symbols would be supported as separate controls.

[0134] However, there is room for further consideration regarding how to specifically control the transmission power when transmitting signals using different symbol types, namely SBFD symbols and non-SBFD symbols.

[0135] For example, there is room for consideration regarding how to apply individual power control parameters based on the type of symbol, the type of RO (RACH Occasion), the type of signal to be transmitted, etc. Here, the type of symbol includes SBFD symbols and non-SBFD symbols. The type of signal to be transmitted includes PRACH, Msg3 PUSCH, MsgA PUSCH, etc. in random access. The type of RO includes legacy RO, additional RO, etc.

[0136] For example, if the parameters for individual power control applied based on whether the RO (RACH Occasion) is a legacy RO or an additional RO are not appropriate, the transmission power to the RO may not be appropriate. In this case, communication quality may deteriorate or interference with other communication systems may occur.

[0137] Furthermore, if the parameters for individual power control applied based on, for example, the type of symbol and / or the type of signal being transmitted are not appropriate, the transmission power for the type of symbol and / or signal being transmitted may not be appropriate. In this case, communication quality may deteriorate or interference with other communication systems may occur.

[0138] Therefore, this embodiment will explain how to specifically control the transmission power when transmitting signals using both SBFD symbols and non-SBFD symbols. Exemplarily, it will explain how individual power control parameters applied based on the symbol type, RO (RACH Occasion) type, and the type of signal to be transmitted are applied.

[0139] Furthermore, applying parameters related to power control may also mean determining the power using those parameters and transmitting a signal based on the determined power.

[0140] The following is an overview of the proposals described below: • Proposal 1: Separate PRACH power control for SBFD and non-SBFD systems. • Proposal 2: Separate Msg3 PUSCH power control for SBFD and non-SBFD systems. • Proposal 3: Msg3 PUSCH power control when separate parameters are set for SBFD and non-SBFD systems. • Proposal 4: Separate MsgA PUSCH power control for SBFD and non-SBFD systems. • Proposal 5: MsgA PUSCH power control when separate parameters are set for SBFD and non-SBFD systems.

[0141] "Legacy RO" refers to the enabled RO in UL symbols or flexible symbols, as set by the legacy RACH configuration based on legacy RO enabling rules.

[0142] "Additional RO" represents the effective RO set by the legacy PRACH setting in the SBFD DL symbol when no additional PRACH setting for SBFD is configured.

[0143] Alternatively, "Additional RO" represents the effective RO set by the legacy PRACH setting, spanning both SBFD DL symbols and SBFD flexible symbols, when no additional PRACH setting for SBFD is configured.

[0144] Alternatively, "Additional RO" represents the valid RO in SBFD symbols that is set by the SBFD-specific PRACH setting when an additional PRACH setting for SBFD is configured.

[0145] Alternatively, "Additional RO" refers to an RO configured by the SBFD-oriented PRACH configuration when an additional PRACH configuration for SBFD is configured, and the network configures the RO to be valid if it starts with an SBFD symbol and ends with a non-SBFD symbol, either within the same slot or across different slots.

[0146] <Proposal 1> Proposal 1 describes separate PRACH power control for SBFD and non-SBFD applications.

[0147] <Proposal 1-1> Proposal 1-1 describes the separate settings for preambleReceivedTargetPower for SBFD and preambleReceivedTargetPower for non-SBFD symbols. Furthermore, Proposal 1-1 describes the separate settings for msgA-PreambleReceivedTargetPower for SBFD and msgA-PreambleReceivedTargetPower for non-SBFD symbols. Note that msgA-PreambleReceivedTargetPower is a parameter for 2-step RACH.

[0148] In the following explanation, preambleReceivedTargetPower may be replaced with msgA-PreambleReceivedTargetPower as appropriate.

[0149] In Proposal 1-1, either Alt. 1 or Alt. 2 is applied.

[0150] Alt. 1 of Proposal 1-1: For PRACH transmission in SBFD symbols, the SBFD-specific preambleReceivedTargetPower is applied. For PRACH transmission in non-SBFD symbols, the non-SBFD-specific preambleReceivedTargetPower is applied. In this case, PRACH transmission in SBFD symbols is performed based on the power determined using the SBFD-specific preambleReceivedTargetPower. Also, in this case, PRACH transmission in non-SBFD symbols is performed based on the power determined using the non-SBFD-specific preambleReceivedTargetPower.

[0151] Furthermore, in Alt. 1, the msgA-PreambleReceivedTargetPower for SBFD may be applied to PRACH transmissions in SBFD symbols. Similarly, the msgA-PreambleReceivedTargetPower for non-SBFD symbols may be applied to PRACH transmissions in non-SBFD symbols.

[0152] In Alt. 1, if preambleReceivedTargetPower for SBFD is not set, the preambleReceivedTargetPower for non-SBFD is applied to PRACH in SBFD symbols. For example, if preambleReceivedTargetPower for SBFD is not set, the preambleReceivedTargetPower for non-SBFD is applied instead of the preambleReceivedTargetPower for SBFD.

[0153] Furthermore, if msgA-PreambleReceivedTargetPower for SBFD is not set in Alt. 1, either Alt. 1-1 or Alt. 1-2 below will be applied.

[0154] Alt. 1-1: The preambleReceivedTargetPower for SBFD may be applied to the MsgA PRACH in the SBFD symbol. That is, if the msgA-PreambleReceivedTargetPower for SBFD is not set, the preambleReceivedTargetPower for SBFD will be applied instead. In this case, the MsgA PRACH in the SBFD symbol will be sent based on the power determined using the preambleReceivedTargetPower for SBFD.

[0155] Alt. 1-2: The msgA-PreambleReceivedTargetPower for non-SBFD may be applied to the MsgA PRACH in SBFD symbols. That is, if the msgA-PreambleReceivedTargetPower for SBFD is not set, the msgA-PreambleReceivedTargetPower for non-SBFD is applied instead. In this case, the MsgA PRACH in the SBFD symbol is sent based on the power determined using the msgA-PreambleReceivedTargetPower for non-SBFD.

[0156] Alt. 2 of Proposal 1-1: For PRACH transmission in additional RO, the preambleReceivedTargetPower for SBFD is applied. For PRACH transmission in legacy RO, the preambleReceivedTargetPower for non-SBFD is applied. In this case, PRACH transmission in additional RO is performed based on the power determined using the preambleReceivedTargetPower for SBFD. Also, in this case, PRACH transmission in legacy RO is performed based on the power determined using the preambleReceivedTargetPower for non-SBFD.

[0157] In Alt. 2, if preambleReceivedTargetPower for SBFD is not set, the preambleReceivedTargetPower for non-SBFD will be applied to PRACH in the additional RO. For example, if preambleReceivedTargetPower for SBFD is not set, the preambleReceivedTargetPower for non-SBFD will be applied instead of the preambleReceivedTargetPower for SBFD.

[0158] Furthermore, if msgA-PreambleReceivedTargetPower for SBFD is not set in Alt. 2, either Alt. 2-1 or Alt. 2-2 below will be applied.

[0159] Alt. 2-1: The preambleReceivedTargetPower for SBFD may be applied to the MsgA PRACH in the additional RO. In this case, the MsgA PRACH in the additional RO is transmitted based on the power determined using the preambleReceivedTargetPower for SBFD.

[0160] Alt. 2-2: The msgA-PreambleReceivedTargetPower for non-SBFD may be applied to the MsgA PRACH in the additional RO. In this case, the MsgA PRACH in the additional RO is transmitted based on the power determined using the msgA-PreambleReceivedTargetPower for non-SBFD.

[0161] In addition, if preambleReceivedTargetPower for SBFD is not set in Alt. 2-1 above, preambleReceivedTargetPower for non-SBFD may be applied to the MsgA PRACH in the additional RO. In this case, the MsgA PRACH in the additional RO will be transmitted based on the power determined using preambleReceivedTargetPower for non-SBFD.

[0162] <Proposal 1-2> Proposal 1-2 describes the power offset of PRACH for SBFD. In Proposal 1-2, either Alt. 1 or Alt. 2 will be applied.

[0163] Alternative 1 of Proposal 1-2: For PRACH transmission in SBFD symbols, a power offset for SBFD is applied. In this case, PRACH transmission in SBFD symbols is performed based on the power determined using the SBFD power offset. The PRACH transmission power is determined by the following equation (6). In the following equation, the power offset is represented as SBFD_offset.

[0164] In Alt. 1, if no power offset is set for SBFD, the default value is applied to PRACH in the SBFD symbol. Here, the default value may be 0 or any other value.

[0165] Alternative 2 of Proposal 1-2: For PRACH transmission in Additional RO, the power offset for SBFD is applied. For PRACH in Legacy RO, the PRACH power is determined in the same way as in Legacy. In this case, PRACH transmission in Additional RO is performed based on the power determined using the power offset for SBFD.

[0166] In Alt. 2, if no power offset is set for SBFD, the default value will be applied to the power offset for PRACH in the additional RO. Here, the default value may be 0 or any other value.

[0167] <Proposal 1-3> Proposal 1-3 describes an example in which the setting of the maximum output power for SFBD and the setting of the maximum output power for non-SBFD are supported separately. In Proposal 1-3, either option 1 or option 2 shown below is applied as an example. Note that the maximum output power is P in equation (6). ＣＭＡＸｆ，ｃ (i) is used in the decision.

[0168] <Option 1 of Proposal 1-3> For PRACH transmission in SBFD symbols, the maximum output power set for SBFD is applied. Similarly, for PRACH transmission in non-SBFD symbols, the maximum output power set for non-SBFD is applied. In this case, PRACH transmission in SBFD symbols is performed based on the power determined using the maximum output power set for SBFD. Also, in this case, PRACH transmission in non-SBFD symbols is performed based on the power determined using the maximum output power set for non-SBFD.

[0169] In addition, in Option 1 of Proposal 1-3, if no maximum output power is set for SBFD, the maximum output power for non-SBFD will be applied to PRACH in the SBFD symbol.

[0170] <Option 2 of Proposal 1-3> For PRACH transmission in the Additional RO, the maximum output power set for SBFD is applied. Also, for PRACH transmission in the Legacy RO, the maximum output power set for non-SBFD is applied. In this case, PRACH transmission in the Additional RO is performed based on the power determined using the maximum output power set for SBFD. Also, in this case, PRACH transmission in the Legacy RO is performed based on the power determined using the maximum output power set for non-SBFD.

[0171] In addition, in Option 2 of Proposal 1-3, if no maximum output power is set for SBFD, the maximum output power for non-SBFD will be applied to PRACH in the additional RO.

[0172] In Proposal 1, the UE controls the transmit power of PRACH based on either the settings for SBFD or the settings for non-SBFD, and transmits PRACH based on the transmit power. Here, SBFD is an example of the first symbol type, and non-SBFD is an example of the second symbol type. PRACH is an example of a signal in random access. Controlling the transmit power of PRACH includes determining the transmit power of PRACH and setting the determined transmit power. This allows for appropriate control of the transmit power when transmitting signals for both SBFD and non-SBFD symbols.

[0173] <Proposal 2> This section describes an example in which the power control parameters for Msg3 for SBFD and the power control parameters for Msg3 for non-SBFD are set separately. Note that the Msg3 power control parameter is at least one of "msg3-Alpha", "msg3-DeltaPreamble", or "DeltaPreamble". The following describes examples corresponding to each parameter. Note that "DeltaPreamble" may also be written as "deltaPreamble".

[0174] <Example 1 of Proposal 2> Separate settings for msg3-Alpha for SBFD and msg3-Alpha for non-SBFD are configured in PUSCH-PowerControl.

[0175] In Example 1 of Proposal 2, the msg3-Alpha for SBFD is applied to the Msg3 PUSCH in the SBFD symbol. The msg3-Alpha for non-SBFD is applied to the Msg3 PUSCH in the non-SBFD symbol. In this case, the Msg3 PUSCH in the SBFD symbol is transmitted based on the power determined using the msg3-Alpha for SBFD. Also, in this case, the Msg3 PUSCH in the non-SBFD symbol is transmitted based on the power determined using the msg3-Alpha for non-SBFD.

[0176] In Example 1 of Proposal 2, if msg3-Alpha for SBFD is not set, either Alt. 1-1 or Alt. 1-2 below will be applied as an example of a parameter that will be applied instead of msg3-Alpha for SBFD.

[0177] Alt. 1-1: The msg3-Alpha for non-SBFD signals may be applied to the Msg3 PUSCH in SBFD symbols. In this case, the Msg3 PUSCH in SBFD symbols is transmitted based on the power determined using the msg3-Alpha for non-SBFD signals.

[0178] Alt. 1-2: The default value is applied to Msg3 PUSCH in SBFD symbols instead of msg3-Alpha. Here, the default value may be 1 or any other value.

[0179] <Example 2 of Proposal 2> Separate settings for msg3-DeltaPreamble for SBFD and msg3-DeltaPreamble for non-SBFD are configured in PUSCH-ConfigCommon.

[0180] In Example 2 of Proposal 2, the msg3-DeltaPreamble for SBFD is applied to the Msg3 PUSCH in SBFD symbols. The msg3-DeltaPreamble for non-SBFD is applied to the Msg3 PUSCH in non-SBFD symbols. In this case, the Msg3 PUSCH in SBFD symbols is transmitted based on the power determined using the msg3-DeltaPreamble for SBFD. Also, in this case, the Msg3 PUSCH in non-SBFD symbols is transmitted based on the power determined using the msg3-DeltaPreamble for non-SBFD.

[0181] In Example 2 of Proposal 2, if msg3-DeltaPreamble for SBFD is not set, either Alt. 2-1 or Alt. 2-2 below will be applied as an example of a parameter that will be applied instead of msg3-DeltaPreamble for SBFD.

[0182] Alt. 2-1: The msg3-DeltaPreamble for non-SBFD may be applied to the Msg3 PUSCH in SBFD symbols. In this case, the Msg3 PUSCH in SBFD symbols is transmitted based on the power determined using the msg3-DeltaPreamble for non-SBFD.

[0183] Alt. 2-2: The default value is applied to Msg3 PUSCH in SBFD symbols instead of msg3-DeltaPreamble. Here, the default value may be 0 or any other value.

[0184] <Example 3 of Proposal 2> Separate settings for DeltaPreamble for SBFD and DeltaPreamble for non-SBFD are configured in FeatureCombinationPreambles.

[0185] In Example 3 of Proposal 2, the DeltaPreamble for SBFD is applied to the Msg3 PUSCH in the SBFD symbol. The DeltaPreamble for non-SBFD is applied to the Msg3 PUSCH in the non-SBFD symbol. In this case, the Msg3 PUSCH in the SBFD symbol is transmitted based on the power determined using the DeltaPreamble for SBFD. Also, in this case, the Msg3 PUSCH in the non-SBFD symbol is transmitted based on the power determined using the DeltaPreamble for non-SBFD.

[0186] In Example 3 of Proposal 2, if a DeltaPreamble for SBFD is not set, one of the following Alt. 3-1, Alt. 3-2, or Alt. 3-3 will be applied as an example of a parameter that will be applied instead of the DeltaPreamble for SBFD.

[0187] Alt. 3-1: A DeltaPreamble for non-SBFD may be applied to Msg3 PUSCH in SBFD symbols. In this case, Msg3 PUSCH in SBFD symbols is transmitted based on the power determined using the DeltaPreamble for non-SBFD.

[0188] Alt. 3-2: The msg3-DeltaPreamble for SBFD may be applied to the Msg3 PUSCH in the SBFD symbol. In this case, the Msg3 PUSCH in the SBFD symbol is transmitted based on the power determined using the msg3-DeltaPreamble for SBFD.

[0189] In addition, if msg3-DeltaPreamble for SBFD is not set in Alt. 3-2, the msg3-DeltaPreamble for non-SBFD may be applied to Msg3 PUSCH in SBFD symbols.

[0190] Alt. 3-3: The default value is applied to Msg3 PUSCH in the SBFD symbol instead of DeltaPreamble. Here, the default value may be 1 or any other value.

[0191] In Proposal 2, the UE controls the transmit power of Msg3 PUSCH based on either the settings for SBFD or non-SBFD, and transmits Msg3 PUSCH based on the transmit power. Here, SBFD is an example of the first symbol type, and non-SBFD is an example of the second symbol type. Msg3 PUSCH is an example of a signal in random access. Controlling the transmit power of Msg3 PUSCH includes determining the transmit power of Msg3 PUSCH and setting the determined transmit power. This allows for appropriate control of the transmit power when transmitting signals for both SBFD and non-SBFD symbols.

[0192] <Proposal 3> Proposal 3 assumes that separate settings are made for preambleReceivedTargetPower for SBFD and for non-SBFD symbols.

[0193] In the above-mentioned scenario, we will explain how power control for Msg3 PUSCH is provided depending on whether preambleReceivedTargetPower for SBFD or preambleReceivedTargetPower for non-SBFD symbols is applied. Note that power control for Msg3 PUSCH is provided by P Ｏ＿ＰＲＥ This is expressed as follows. For example, in Proposal 3, one of the following Alt. 0, Alt. 1, Alt. 2, Alt. 2', Alt. 3, or Alt. 3' is applied.

[0194] Proposal 3 Alt. 0:P Ｏ＿ＰＲＥ This is always provided by preambleReceivedTargetPower for non-SBFD. In other words, in Alt. 0, P Ｏ＿ＰＲＥRegardless of the symbol type of Msg3 PUSCH, and regardless of the PRACH type, it is provided by preambleReceivedTargetPower for non-SBFD.

[0195] Alternative 1 of Proposal 3: If Msg3 PUSCH is within an SBFD symbol, preambleReceivedTargetPower for SBFD is applied regardless of the PRACH type.

[0196] Note that in Proposal 3, Alt. 1, if Msg3 PUSCH is within an SBFD symbol, P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for SBFD. Also, in Alt. 1 of Proposal 3, if Msg3 PUSCH is in a non-SBFD symbol, P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for non-SBFD applications.

[0197] Alt. 2 of Proposal 3: If the PRACH of a RACH attempt is within an SBFD symbol, preambleReceivedTargetPower for SBFD is applied regardless of the symbol type of Msg3 PUSCH.

[0198] Furthermore, in Alt. 2 of Proposal 3, if the PRACH of the RACH trial is within the SBFD symbol, then for the corresponding Msg3 PUSCH, P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for SBFD. Also, in Alt. 2 of Proposal 3, if the PRACH of the RACH trial is in a non-SBFD symbol, then for the corresponding Msg3 PUSCH, P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for non-SBFD applications.

[0199] Alt. 2' of Proposal 3: Alt. 2' is a variation of Alt. 2. If the PRACH of the RACH trial is within an additional RO, preambleReceivedTargetPower for SBFD is applied regardless of the symbol type of Msg3 PUSCH.

[0200] Furthermore, in Proposal 3, Alt. 2', if the PRACH of the RACH trial is within the additional RO, then for the corresponding Msg3 PUSCH, P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for SBFD. Also, in Alt. 2' of Proposal 3, if the PRACH of the RACH trial is in legacy RO, then for the corresponding Msg3 PUSCH, P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for non-SBFD applications.

[0201] Alt. 3 of Proposal 3: If the PRACH of the RACH trial is within an SBFD symbol and Msg3 PUSCH is within an SBFD symbol, then preambleReceivedTargetPower for SBFD is applied.

[0202] Note that in Proposal 3, Alt. 3, if PRACH in the RACH trial is within the SBFD symbol, and Msg3 PUSCH is within the SBFD symbol, then P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for SBFD.

[0203] Furthermore, in Alt. 3 of Proposal 3, if PRACH in the RACH trial is within an SBFD symbol, and Msg3 PUSCH is not within an SBFD symbol, then P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for non-SBFD applications.

[0204] Furthermore, in Alt. 3 of Proposal 3, if the PRACH of the RACH trial is within a non-SBFD symbol, then for Msg3 PUSCH within or outside the SBFD symbol, P Ｏ＿ＰＲＥThis is provided by preambleReceivedTargetPower for non-SBFD applications.

[0205] Alt. 3' of Proposal 3: Alt. 3' is a variation of Alt. 3. If the PRACH of the RACH trial is within an additional RO and Msg3 PUSCH is within an SBFD symbol, then preambleReceivedTargetPower for SBFD is applied.

[0206] Note that in Proposal 3, Alt. 3', if the PRACH of the RACH trial is within the additional RO, and Msg3 PUSCH is within the SBFD symbol, then P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for SBFD.

[0207] Furthermore, in Alt. 3' of Proposal 3, if PRACH in the RACH trial is within an additional RO, and Msg3 PUSCH is within a non-SBFD symbol, then P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for non-SBFD applications.

[0208] Furthermore, in Proposal 3, Alt. 3', if the PRACH of the RACH trial is within a legacy RO, then for Msg3 PUSCH within an SBFD symbol or a non-SBFD symbol, P Ｏ＿ＰＲＥ This is provided by preambleReceivedTargetPower for non-SBFD applications.

[0209] Figure 12 is a table showing the relationships between the examples shown in Proposal 3. Figure 12 associates the PRACH type, the symbol type of Msg3 PUSCH, and the parameters for each of the above-described Examples 1 to 3. As shown in Figure 12, the applicable parameters may be determined based on the PRACH type and the symbol type of Msg3.

[0210] <Variations of Proposal 3> Proposal 3 may be extended to parameters other than preambleReceivedTargetPower.

[0211] For example, the "P" in proposal 3 mentioned above. Ｏ＿ＰＲＥ " is "Δ ＰＲＥＡＭＢＬＥ，Ｍｓｇ３ This may be replaced with `preambleReceivedTargetPower`, and `msg3-DeltaPreamble` and / or `DeltaPreamble` may be replaced with `msg3-DeltaPreamble` and / or `DeltaPreamble`.

[0212] For example, the "P" in proposal 3 mentioned above. Ｏ＿ＰＲＥ " is "α ｂ，ｆ，ｃ (0) may be replaced, and "preambleReceivedTargetPower" may be replaced with "msg3-Alpha".

[0213] In Proposal 3, the parameter preambleReceivedTargetPower and the "P" determined by preambleReceivedTargetPower are used. Ｏ＿ＰＲＥ Using the example shown, the method of applying parameters according to the type of signal (e.g., PRACH, Msg3 PUSCH), the type of symbol (e.g., SBFD symbol, non-SBFD symbol), etc. is demonstrated. This allows for appropriate control of the transmission power when transmitting signals using both SBFD and non-SBFD symbols.

[0214] <Proposal 4> This section describes an example in which the power control parameters for MsgA for SBFD and the power control parameters for MsgA for non-SBFD are set separately. Note that the MsgA power control parameter is at least one of "msgA-Alpha", "msgA-DeltaPreamble", and "deltaPreamble". The following describes examples corresponding to each parameter. Note that "deltaPreamble" may also be written as "DeltaPreamble".

[0215] <Example 1 of Proposal 4> Separate settings are configured for msgA-DeltaPreamble for SBFD and for msgA-DeltaPreamble for non-SBFD.

[0216] In Example 1 of Proposal 4, the msgA-DeltaPreamble for SBFD is applied to the MsgA PUSCH in the SBFD symbol. The msgA-DeltaPreamble for non-SBFD is applied to the MsgA PUSCH in the non-SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the msgA-DeltaPreamble for SBFD. Also in this case, the MsgA PUSCH in the non-SBFD symbol is transmitted based on the power determined using the msgA-DeltaPreamble for non-SBFD.

[0217] In Example 1 of Proposal 4, if msgA-DeltaPreamble for SBFD is not set, one of the following Alt. 1-1 to Alt. 1-4 will be applied as an example of a parameter that will be applied instead of msgA-DeltaPreamble for SBFD.

[0218] Alt. 1-1: A msgA-DeltaPreamble for non-SBFD may be applied to the MsgA PUSCH in an SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the msgA-DeltaPreamble for non-SBFD.

[0219] Alt. 1-2: If an msg3-DeltaPreamble for SBFD is configured, the msg3-DeltaPreamble for SBFD may be applied to the MsgA PUSCH in the SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the msg3-DeltaPreamble for SBFD.

[0220] Alt. 1-3: If a deltaPreamble for SBFD is set, the deltaPreamble for SBFD may be applied to the MsgA PUSCH in the SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the deltaPreamble for SBFD.

[0221] Alt. 1-4: The default value is applied to MsgA PUSCH in SBFD symbols instead of msgA-DeltaPreamble. Here, the default value may be 0 or any other value.

[0222] <Example 2 of Proposal 4> Separate settings are configured for deltaPreamble for SBFD and deltaPreamble for non-SBFD.

[0223] In Example 2 of Proposal 4, the deltaPreamble for SBFD is applied to the MsgA PUSCH in the SBFD symbol. The deltaPreamble for non-SBFD is applied to the MsgA PUSCH in the non-SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the deltaPreamble for SBFD. Also, in this case, the MsgA PUSCH in the non-SBFD symbol is transmitted based on the power determined using the deltaPreamble for non-SBFD.

[0224] In Example 2 of Proposal 4, if deltaPreamble for SBFD is not set, one of the following Alt. 2-1 to Alt. 2-4 will be applied as an example of a parameter that will be applied instead of deltaPreamble for SBFD.

[0225] Alt. 2-1: A deltaPreamble for non-SBFD may be applied to the MsgA PUSCH in an SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the deltaPreamble for non-SBFD.

[0226] Alt. 2-2: If an msgA-DeltaPreamble for SBFD is configured, the msgA-DeltaPreamble for SBFD may be applied to the MsgA PUSCH in the SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the msgA-DeltaPreamble for SBFD.

[0227] Alt. 2-3: If an msg3-DeltaPreamble for SBFD is configured, the msg3-DeltaPreamble for SBFD may be applied to the MsgA PUSCH in the SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the msg3-DeltaPreamble for SBFD.

[0228] Alt. 2-4: The default value is applied to MsgA PUSCH in SBFD symbols instead of deltaPreamble. Here, the default value may be 0 or any other value.

[0229] <Example 3 of Proposal 4> Separate settings are configured for msgA-Alpha for SBFD and for msgA-Alpha for non-SBFD.

[0230] In Example 3 of Proposal 4, the msgA-Alpha for SBFD is applied to the MsgA PUSCH in the SBFD symbol. The msgA-Alpha for non-SBFD is applied to the MsgA PUSCH in the non-SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the msgA-Alpha for SBFD. Also in this case, the MsgA PUSCH in the non-SBFD symbol is transmitted based on the power determined using the msgA-Alpha for non-SBFD.

[0231] In Example 3 of Proposal 4, if msgA-Alpha for SBFD is not set, one of the following Alt. 3-1 to Alt. 3-3 will be applied as an example of a parameter to be applied instead of msgA-Alpha for SBFD.

[0232] Alt. 3-1: The msgA-Alpha for non-SBFD may be applied to the MsgA PUSCH in the SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using the msgA-Alpha for non-SBFD.

[0233] Alt. 3-2: If msg3-Alpha for SBFD is configured, msg3-Alpha for SBFD may be applied to the MsgA PUSCH in the SBFD symbol. In this case, the MsgA PUSCH in the SBFD symbol is transmitted based on the power determined using msg3-Alpha for SBFD.

[0234] Alt. 3-3: The default value is applied to MsgA PUSCH in SBFD symbols instead of msgA-Alpha. Here, the default value may be 1 or any other value.

[0235] In Proposal 4, the UE controls the transmit power of the MsgA PUSCH based on either the settings for SBFD or the settings for non-SBFD, and transmits the MsgA PUSCH based on the transmit power. Here, SBFD is an example of the first symbol type, and non-SBFD is an example of the second symbol type. The MsgA PUSCH is an example of a signal in random access. The control of the MsgA PUSCH transmit power includes determining the transmit power of the MsgA PUSCH and setting the determined transmit power. This allows for appropriate control of the transmit power when transmitting signals for both SBFD and non-SBFD symbols.

[0236] <Proposal 5> Proposal 5 assumes that separate settings are made for msgA-PreambleReceivedTargetPower for SBFD and for non-SBFD symbols.

[0237] In the above-mentioned scenario, we will explain how power control of the MsgA PUSCH is provided depending on whether msgA-PreambleReceivedTargetPower for SBFD or msgA-PreambleReceivedTargetPower for non-SBFD symbols is applied. Note that power control of the MsgA PUSCH is provided by P Ｏ＿ＰＲＥ This is expressed as follows. For example, in Proposal 5, one of the following Alt. 0, Alt. 1, Alt. 2, Alt. 2', Alt. 3, or Alt. 3' is applied.

[0238] Proposal 5 Alt. 0:P Ｏ＿ＰＲＥ This is always provided by msgA-PreambleReceivedTargetPower for non-SBFD. In other words, in Alt. 0, P Ｏ＿ＰＲＥ This is provided by msgA-preambleReceivedTargetPower for non-SBFD, regardless of the symbol type of MsgA PUSCH and regardless of the PRACH type.

[0239] Alternative 1 of Proposal 5: If MsgA PUSCH is within an SBFD symbol, regardless of the PRACH type, msgA-PreambleReceivedTargetPower for SBFD is applied.

[0240] Note that in Proposal 5, Alt. 1, if MsgA PUSCH is within an SBFD symbol, P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for SBFD. Also, in Alt. 1 of Proposal 5, if MsgA PUSCH is in a non-SBFD symbol, P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for non-SBFD applications.

[0241] Alt. 2 of Proposal 5: If MsgA PRACH is within an SBFD symbol, msgA-PreambleReceivedTargetPower for SBFD is applied regardless of the symbol type of MsgA PUSCH.

[0242] Furthermore, in Alt. 2 of Proposal 5, if MsgA PRACH is within an SBFD symbol, then P is applied to the corresponding MsgA PUSCH. Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for SBFD. Also, in Alt. 2 of Proposal 5, if MsgA PRACH is in a non-SBFD symbol, the corresponding MsgA PUSCH is provided with P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for non-SBFD applications.

[0243] Alt. 2' of Proposal 5: Alt. 2' is a variation of Alt. 2. If MsgA PRACH is within an additional RO, msgA-PreambleReceivedTargetPower for SBFD is applied regardless of the symbol type of MsgA PUSCH.

[0244] Furthermore, in Proposal 5, Alt. 2', if MsgA PRACH is within an additional RO, then P is applied to the corresponding MsgA PUSCH. Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for SBFD. Also, in Alt. 2' of Proposal 5, if MsgA PRACH is in legacy RO, P is provided for the corresponding MsgA PUSCH. Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for non-SBFD applications.

[0245] Alt. 3 of Proposal 5: If MsgA PRACH is within an SBFD symbol and MsgA PUSCH is within an SBFD symbol, then msgA-PreambleReceivedTargetPower for SBFD is applied.

[0246] Note that in Proposal 5, Alt. 3, if MsgA PRACH is within an SBFD symbol, and MsgA PUSCH is within an SBFD symbol, P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for SBFD.

[0247] Furthermore, in Alt. 3 of Proposal 5, if MsgA PRACH is within an SBFD symbol and MsgA PUSCH is not within an SBFD symbol, P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for non-SBFD applications.

[0248] Furthermore, in Alt. 3 of Proposal 5, if MsgA PRACH is within a non-SBFD symbol, then for MsgA PUSCH within an SBFD symbol or a non-SBFD symbol, P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for non-SBFD applications.

[0249] Alt. 3' of Proposal 5: Alt. 3' is a variation of Alt. 3. If MsgA PRACH is in an additional RO and MsgA PUSCH is in an SBFD symbol, then msgA-PreambleReceivedTargetPower for SBFD is applied.

[0250] Furthermore, in Proposal 5, Alt. 3', if MsgA PRACH is within an additional RO and MsgA PUSCH is within an SBFD symbol, P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for SBFD.

[0251] Furthermore, in Proposal 5, Alt. 3', if MsgA PRACH is in an additional RO and MsgA PUSCH is in a non-SBFD symbol, P Ｏ＿ＰＲＥThis is provided by msgA-PreambleReceivedTargetPower for non-SBFD applications.

[0252] Furthermore, in Proposal 5, Alt. 3', if MsgA PRACH is in a legacy RO, then for MsgA PUSCH in an SBFD symbol or a non-SBFD symbol, P Ｏ＿ＰＲＥ This is provided by msgA-PreambleReceivedTargetPower for non-SBFD applications.

[0253] <Variations of Proposal 5> Proposal 5 may be extended to parameters other than msgA-PreambleReceivedTargetPower.

[0254] For example, the "P" in proposal 5 mentioned above. Ｏ＿ＰＲＥ " is "Δ ＭｓｇＡ＿ＰＵＳＣＨ This can be replaced with msgA-PreambleReceivedTargetPower, and msgA-DeltaPreamble and / or DeltaPreamble may be replaced with msgA-PreambleReceivedTargetPower.

[0255] For example, the "P" in proposal 5 mentioned above. Ｏ＿ＰＲＥ " is "α ｂ，ｆ，ｃ (0) may be replaced, and "msgA-PreambleReceivedTargetPower" may be replaced with "msgA-Alpha".

[0256] In Proposal 5, the parameter msgA-PreambleReceivedTargetPower and the "P" determined by msgA-PreambleReceivedTargetPower are used. Ｏ＿ＰＲＥ Using the example shown, the method of applying parameters according to the type of signal, the type of symbol, etc., was demonstrated. This allows for appropriate control of the transmission power when transmitting signals with both SBFD symbols and non-SBFD symbols.

[0257] <Variations> Any two or more combinations of each Alt and each option in Proposals 1 to 5 described above may be applied. In addition, any two or more of each Alt and each option in Proposals 1 to 5 described above may be switched dynamically or semi-persistently.

[0258] Proposals 1 to 5 described above may be applied to a UE in connected mode or to a UE in RRC idle mode.

[0259] Proposals 1 to 5 described above may be applied to CBRA or to CFRA.

[0260] Depending on at least one of the following differences, different proposals may be applied, different Alts of a proposal may be applied, or different options of a proposal may be applied: • RA type (e.g., CBRA, CFRA, type 1 RACH, type 2 RACH) • RACH triggering method (e.g., RACH initialized by PDCCH order, MAC entity, and RRC) • RACH purpose (e.g., RACH for initial access, RACH for SI request, RACH for SpCell BFR, RACH for reconfiguration with synchronization) • PRACH transmission method (e.g., multiple repetitions or single repetition) • Whether the RACH is an initial transmission or a retransmission

[0261] (Combination with Options) In proposals 1 to 3 of this disclosure, which proposal applies, or which option or alternative is used, may be determined by: - ​​Setting by higher-level parameters - Determining by relevant higher-level parameters - Indicated in MAC CE or DCI - Determining based on UE capabilities - Stated in the specification - Determining based on conditions stated in the specification - Determining by the higher-level parameters / MAC CE / DCI configuration and reported UE capabilities (combination of the above determinations)

[0262] In each proposal of this disclosure, multiple options and alternatives may be combined into a single option / alternative. Throughout the proposals, the measured RS (reference signal) will be the QCL source RS in the active TCI state / indicated TCI state.

[0263] (Signals from NW to UE) In this disclosure, the UE may receive the following types of information from the network (NW). Throughout the proposal, the network (NW) may also be referred to as a gNB. • Information via upper-layer signaling (e.g., RRC messages / LPP (LTE propositioning protocol) messages) • MAC CE subheader with a new LCID extending the existing MAC CE (e.g., introducing a new octet) • DCI DCI field: Existing DCI field or newly introduced DCI field RNTI: Existing RNTI or DCI with a scrambled CRC by the newly introduced RNTI DCI format: Existing DCI format or newly introduced DCI format • Combinations of the above information

[0264] In this disclosure, the UE may receive information from the network (NW) in the following periodic forms: Option 1: Receive information periodically; Option 2: Receive information semi-persistently (triggered by instructions from the UE or gNB); Option 3: Receive information aperiodically (triggered by instructions from the UE or gNB).

[0265] In this disclosure, the UE may receive information from the network (NW) as the following QCL rules: • QCL Type A • QCL Type B • QCL Type C • QCL Type D

[0266] In this disclosure, the QCL resource RS for each QCL type may be configured as follows: • SSB (SS / PBCH Block) • CSI-RS with / without repetition • TRS (tracking reference signal) • PDCCH / PDSCH DMRS

[0267] In this disclosure, information from the network (NW) is set / presented as follows: • Common to UE / Dedicated to UE • Cell-specific / Common to cell • Per UE / CC / BWP / Bandwidth / Cell / CG

[0268] (Signals from UE to NW) In this disclosure, the UE may report the following types of information to the network (NW). Throughout the proposal, the network (NW) may also be referred to as gNB. - Information via upper layer signaling (e.g., RRC messages / LPP messages) - MAC CE subheader with a new LCID, extending an existing MAC CE (e.g., introduction of a new octet) - UCI on PUCCH or PUSCH - Combinations of the above information

[0269] In this disclosure, the UE may report information to the network (NW) in the following periodic forms: Option 1: Send information periodically Option 2: Send information semi-persistently (triggered by instructions from the UE or gNB) Option 3: Send information aperiodically (triggered by instructions from the UE or gNB)

[0270] <UE capability> The UE capability, which indicates the capabilities of a terminal, may include the following information indicating the capabilities of the terminal. For example, the following new UE capability and report signaling (and RRC settings) may be defined. Note that the information indicating the capabilities of a terminal may correspond to the information defining the capabilities of the terminal. The UE may report the following information indicating the capabilities of the terminal to the gNB: - The capabilities of the terminal for each proposal - The capabilities of each option in each proposal, or each combination of options - The capabilities of each alternative in each proposal, or each combination of alternatives The UE may report the above information indicating the capabilities of the terminal for each frequency to the gNB: - Capabilities for each UE / FR1 / FR2 / FR2-1 / FR2-2 / FR3 / SCS / band / BC / FC / FSPC, etc. The UE may report the above information indicating the capabilities of the terminal for each cell to the gNB: - Capabilities for each UE / cell / TDD / FDD, etc.

[0271] The capabilities of the UE described above and the configuration of this proposal are closely related, and if the functionality of each option in each proposal depends on the capabilities of the UE, the gNB may select or permit the functionality of each option based on the capabilities reported by the UE.

[0272] Next, the configurations of gNB100 and UE200 will be described. Note that the configurations of gNB100 and UE200 described below are examples of functions related to this embodiment. gNB100 and UE200 may have functions not shown. Furthermore, the function classification and / or the name of the function unit are not limited, as long as the function performs the operations related to this embodiment.

[0273] <Base Station Configuration> Figure 13 is a block diagram showing an example of the configuration of a base station 100 (gNodeB (gNB) 100) according to this embodiment. The gNB 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The gNB 100 communicates wirelessly with the UE 200 (see Figure 14).

[0274] The transmitter 101 transmits downlink (DL) signals to the UE200. For example, the transmitter 101 transmits DL signals (e.g., RRC, SIB, MAC CE, DCI, notification, acknowledgment, etc., as described above) under the control of the control unit 103.

[0275] The DL signal may include, for example, downlink data signals and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating the scheduling of signal transmission for the UE200 (e.g., UL grants). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). Finally, the DL signal may include reference signals.

[0276] The channels used to transmit DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, gNB100 transmits downlink control information to UE200 using the PDCCH and transmits downlink data signals using the PDSCH.

[0277] The reference signals included in the DL signal may include, for example, at least one of the following: Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS). For example, reference signals such as DMRS and PTRS are used for demodulating the downlink data signal and are transmitted using PDSCH.

[0278] The receiving unit 102 receives uplink (UL) signals transmitted from the UE200. For example, the receiving unit 102 receives UL signals (e.g., the requests and notifications mentioned above) under the control of the control unit 103.

[0279] The transmitting unit 101 and the receiving unit 102 may together be referred to as the communication unit.

[0280] The control unit 103 controls the communication operation of the gNB100, including the transmission process of the transmission unit 101 and the reception process of the reception unit 102.

[0281] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101. The control unit 103 also outputs the data and control information received from the reception unit 102 to the upper layer.

[0282] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals received from the UE200 (e.g., data and control information, etc.) and / or data and control information, etc. acquired from higher layers. Information regarding the allocated resources may be included in the control information transmitted to the UE200.

[0283] <Terminal Configuration> Figure 14 is a block diagram showing an example of the configuration of the UE200 according to this embodiment. The UE200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The UE200 communicates with, for example, the gNB100 wirelessly.

[0284] The transmitter 202 transmits the UL signal to the gNB100. For example, the transmitter 202 transmits the UL signal under the control of the control unit 203. For example, the transmitter 202 may transmit MsgA PRACH in a valid MsgA RO determined by the control unit 203, or MsgA PUSCH in a valid MsgA PO determined by the control unit 203.

[0285] The UL signal may include, for example, data signals for the uplink and control information (e.g., UCI). It may also include, for example, information regarding the processing capability of the UE200 (e.g., UE capability). Furthermore, the UL signal may include reference signals.

[0286] The channels used to transmit UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes PUCCH (Physical Uplink Control Channel). For example, UE200 transmits uplink control information to gNB100 using PUCCH and transmits uplink data signals using PUSCH.

[0287] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (e.g., PUSCH).

[0288] The receiving unit 201 and the transmitting unit 202 may together be referred to as the communication unit.

[0289] The control unit 203 controls the communication operation of the UE200, including the receiving process in the receiving unit 201 and the transmitting process in the transmitting unit 202.

[0290] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202. The control unit 203 also outputs data and control information received from the receiving unit 201 to the upper layer.

[0291] For example, the control unit 203 controls the transmission of information to be fed back to the gNB100. The information to be fed back to the gNB100 may include, for example, HARQ-ACK, Channel State Information (CSI), or Scheduling Request (SR). The information to be fed back to the gNB100 may be included in the UCI.

[0292] Here, for example, the control unit 203 of UE200 controls the transmission power of the signal in random access based on either a first setting for a first symbol type (e.g., SBFD) or a second setting for a second symbol type (e.g., non-SBFD). The communication unit transmits the signal based on the transmission power controlled by the control unit 203. The signal in random access includes at least one of PRACH, MsgA PRACH, Msg3 PUSCH, and MsgA PUSCH.

[0293] <Hardware Configuration, etc.> The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0294] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0295] For example, a base station, terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the communication method of the present disclosure. Figure 15 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The gNB100 and UE200 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0296] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of gNB100 and UE200 may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0297] Each function in the gNB100 and UE200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0298] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit 103 and control unit 203 described above may be implemented by the processor 1001.

[0299] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 203 of the UE200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0300] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

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

[0302] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 may be implemented by the communication device 1004.

[0303] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0305] Furthermore, gNB100 and UE200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0306] (Supplement to Embodiments) While embodiments of the present disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present disclosure, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, base stations and terminals have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. Software operated by a processor in a base station according to embodiments of this disclosure, and software operated by a processor in a terminal according to embodiments of this disclosure, may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disks (HDDs), removable disks, CD-ROMs, databases, servers, or any other suitable storage medium.

[0307] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0308] <Applicable Systems> The embodiments described herein may be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as at least one of the next-generation systems that are extended, modified, created, or defined based on these. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0309] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, as long as there is no contradiction. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0310] <Base Station Operation> The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides the base station, but it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0311] <Direction of Input / Output> Information, etc. (see the section on <Information, Signals>) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may also occur via multiple network nodes.

[0312] <Handling of Input / Output Information, etc.> Input and output information, etc. may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, etc. may be overwritten, updated, or appended to. Output information, etc. may be deleted. Input information, etc. may be transmitted to other devices.

[0313] <Determination Method> The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0314] <Variations of Embodiments, etc.> Each embodiment / appearance described in this disclosure may be used individually, in combination, or switched between during implementation. Furthermore, notification of predetermined information (for example, notification that "it is X") is not limited to explicit notification, but may also be implicit (for example, by not providing notification of the predetermined information).

[0315] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0316] <Software> Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0317] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0318] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

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

[0320] <Systems and Networks> The terms “systems” and “networks” as used in this disclosure are interchangeable.

[0321] <Parameters, Channel Names> Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0322] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0324] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0325] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

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

[0327] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0328] <Base Station / Mobile Station> At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of a base station and a mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes cases where the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0329] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the embodiments of this disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminal may have the functions that the base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0330] Similarly, the term "terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the terminal described above.

[0331] Figure 16 shows an example of the configuration of vehicle 2001. As shown in Figure 16, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, 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. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0332] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0333] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0334] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0335] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0336] The Information Services Unit 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

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

[0338] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029 provided in the vehicle 2001.

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

[0340] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0341] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0342] <Meaning and Interpretation of Terms> As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in tables, databases or other data structures), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having "judgmented" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having "judgmented" or "decided" about some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0343] The terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0345] <Meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on".

[0346] <"First", "Second"> Any reference to elements using the designations "first", "second", etc. as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to first and second elements do not imply that only two elements may be adopted, or that the first element must precede the second element in any way.

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

[0348] <Open Format> Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.

[0349] <Time units such as TTI, frequency units such as RB, and radio frame configuration> A radio frame may consist of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0350] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, 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 configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

[0352] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called PDSCH (or PUSCH) mapping type B.

[0353] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0354] For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0355] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0356] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0357] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0358] A TTI with a time length of 1 ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0359] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0361] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0362] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0363] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0364] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0365] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE.

[0366] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0367] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

[0368] <Maximum Transmit Power> The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0369] <Articles> In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may also include the fact that the noun following these articles is plural.

[0370] <"Different"> In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0371] One aspect of this disclosure is useful for wireless communication systems.

[0372] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2024-195445, filed on November 7, 2024, are incorporated herein by reference.

[0373] 10 Wireless communication system 20 NG-RAN 100 Base station (gNB) 200 Terminal (UE) 101, 202 Transmitter 102, 201 Receiver 103, 203 Control unit

Claims

1. A terminal comprising: a control unit that controls the transmission power of a signal in random access based on either a first setting for a first type of symbol or a second setting for a second type of symbol; and a communication unit that transmits the signal based on the transmission power.

2. The terminal according to claim 1, wherein the control unit controls the transmission power of the signal in the first symbol based on the first setting.

3. The terminal according to claim 1, wherein the control unit controls the transmission power of the signal in the first symbol based on the second setting if the first setting is not set.

4. The terminal according to claim 1, wherein the control unit controls the transmission power of the signal in the first symbol based on a third setting for the first symbol type, which is different from the first setting, if the first setting is not set.

5. A wireless communication system comprising: a terminal that controls the transmission power of a signal in random access based on either a first setting for a first type of symbol or a second setting for a second type of symbol, and transmits the signal based on the transmission power; and a base station that receives the signal.

6. A wireless communication method in which a terminal controls the transmission power of a signal in random access based on either a first setting for a first type of symbol or a second setting for a second type of symbol, and transmits the signal based on the transmission power.

Images